On Mon, 2008-05-26 at 22:27 -0500, Rajko M. wrote:
On Monday 26 May 2008 06:30:01 am Sampsa Riikonen wrote:
On Mon, 2008-05-26 at 05:48 -0500, Rajko M. wrote: ... Things just got a bit more annoying..
I have removed bcm43xx, but ---------------- fl-laina-13:/home/sampsa # lsmod | grep bcm bcm43xx 419676 0 ieee80211softmac 34432 1 bcm43xx ieee80211 35400 2 bcm43xx,ieee80211softmac firmware_class 13568 2 bcm43xx,uvcvideo ---------------- So I remove it again.. --------------- fl-laina-13:/home/sampsa # rmmod bcm43xx fl-laina-13:/home/sampsa # fl-laina-13:/home/sampsa # lsmod | grep bcm fl-laina-13:/home/sampsa # ----------------- So it is gone. Then I start yast => network devices At this moment, I try again in a terminal.. ----------------- fl-laina-13:/home/sampsa # lsmod | grep bcm bcm43xx 419676 0 ieee80211softmac 34432 1 bcm43xx ieee80211 35400 2 bcm43xx,ieee80211softmac firmware_class 13568 2 bcm43xx,uvcvideo ------------------- And there it is again! And keep in mind that it has been blacklisted.
So it seems that it is yast that insists in loading this kernel module. How can I convince it not to do it?!?
Btw, now the bcm43xx shows in the kernel modules list (while ago it didn't?) and ndiswrapper does not, althought it is loaded into the kernel ------------------- fl-laina-13:/home/sampsa # lsmod | grep ndis ndiswrapper 174328 0 usbcore 124268 6 ndiswrapper,uvcvideo,usbhid,ohci_hcd,ehci_hcd --------------------
OK. I updated laptop to the latest in openSUSE 10.3 and my wireless is still fine. I have static IP, not DHCP and network setup method is with NetworkManager. In "Network Card Setup", tab "Hardware" under "Module Name" I have ndiswrapper and bcm43xx. Currently used ndiswrapper. The bcm43xx probably comes from: /etc/udev/rules.d/70-persistent-net.rules
Now this file looks like.. ----------- # This file was automatically generated by the /lib/udev/write_net_rules # program run by the persistent-net-generator.rules rules file. # # You can modify it, as long as you keep each rule on a single line. # PCI device 0x10de:0x0269 (forcedeth) SUBSYSTEM=="net", DRIVERS=="?*", ATTR{address}=="00:1b:24:c4:a9:d0", NAME="eth0" # PCI device 0x14e4:0x4312 (bcm43xx) SUBSYSTEM=="net", DRIVERS=="?*", ATTR{address}=="00:00:00:1a:73:c3", NAME="eth1" # PCI device 0x14e4:0x4312 (ndiswrapper) SUBSYSTEM=="net", DRIVERS=="ndiswrapper", ATTR{address}=="00:1a:73:c3:79:ea", ATTR{type}=="1", NAME="wlan0" ---------------- But yast still does not offer me the ndiswrapper kernel module! By the way, to make ndiswrapper load into the kernel automatically, I had to use peter's advice. The command "ndiswrapper -m" told me that it is already written in the system configuration (where? .. could not find any trace of it in /etc/modprobe*), but even so, it did not load into the kernel at the boot time. So here is a quote from Peter:
I still had to add the following step: for module to be loaded at boot time so go into YAST and select system ==> /etc/sysconfig editor
scroll down to SYSTEM==>KERNEL==>MODULES_LOADED_ON_BOOT
add ndiswrapper to the list (if there are any entries just leave a space and type ndiswrapper).
This is all very messy. I mean, something has changed since I last read the ndiswrapper instructions.. earlier ndiswrapper was able to write the system configuration in a correct way to load itself at the boot time. And then yast.. now ndiswrapper is loaded into the kernel but it does not show in the kernel modules list in "network devices". Sometime ago it worked ok. In my ex workplace, a lot of otherwise unix using people were sticking in using wintendo in their laptops, because, according to them "linux does not work with wireless" (an urban legend I keep hearing all the time). Can't really blame those poor souls.. Regards, Sampsa -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org