Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
My computer came fitted with a WinModem, the Intel-v92-Ham.
Normally unusable under linux, but fortunately some nice people at Intel made some drivers for it, which SuSE packaged with their distro and I installed
The driver consists of two kernel modules, hamcore.o and ham.o. both must be loaded for the modem to work. The device file is /dev/ham
When I start WVDial (or any other dialer) to connect to the net, there is a long pause and plenty of CPU/Hard disc activity. Then WVDial says 'cannot use /dev/ham, device not recognised'. In the error log, I have 'insmod: install block-major-hamcore failed'
However, when I (as root) I say:
#modprobe hamcore
#modprobe ham
WVDial works fine, there is no pause before the modem starts up and all is nice.
There is a script with the driver, called hamboot. This is supposed to load the two modules at boot time, but it doesn't
Now, although I can cope with loading the modules by hand every time I connect, I really want to do it automatically or at boot time. Any ideas?
Just reading the man page here about insmod actually sounds like maybe the command you are looking for. It sounds like it "installs" the modules rather than just probing them?
That's good, I didn't realize that I could just sit the commands at the bottom of the script and they would execute. I somehow presumed boot scripts to be much more complex.
I have tried insmod, but don't understand what it does. It seems to have exactly the same effect as modprobe. The modules unload again after reboot.
so you know, that script you have that came with the drivers might need to be setup in the /etc/init.d directory, with the proper symlinks from /etc/rc.d/rc3.d in order to work (but I dunno for sure - I haven't used this stuff).
PS - I think modprobe actually does call insmod. It's kind of a wrapper that loads dependent modules in additon to the one you specify as an argument to modprobe on the command line.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.