On Thursday 09 June 2005 11:05 pm, Peter N. Spotts wrote:
procedure, the instructions don't say precisely where to put ndiswrapper -m so that it starts up on boot. I'm trying to avoid having to go su then do a modprobe ndiswrapper every time I want to use my wireless link. I'd like to get ndiswrapper going somewhere between pcmcia startup and network startup so that when the ntd daemon starts farther down the line, it actually picks up the external time servers rather than giving me a "failed" status. Perhaps there's even a way to get ndiswrapper to show up in the system services section of yast2, where it can be associated with run-levels?
Peter, although I dont use the ndiswrapper anymore I still have a howto I put together a year ago which will answer your problem I hope. The excerpt follows: The instructions say if it all works then do ndiswrapper -m which should modify your modules.conf file. This is to make it install during boot, but that only works on pre 2.6 kernels, the later kernels use modprobe.conf for such things. I'm sure someone knows how to setup the modprobe.conf file but my solution is to use an editor to change the /etc/sysconfig/kernel file and set the line: MODULES_LOADED-ON-BOOT="ndiswrapper" If it is all working you should be able to do rcnetwork restart and see the NICs shut down and restart with the wlan0 getting its IP from your router. The ultimate proof of all this is if it fires up when you reboot. If you need to take down the eth0 with ifconfig, be sure you do ifconfig eth0 down THEN ifconfig wlan0 up in that sequence. I used it on suse 9.2 very effectively and I assume it will still work on 9.3. It was on LinuxQuestions.org in the network section. The whole thing might still be there. Good luck, RA