John Andersen wrote:

On Sun, May 25, 2008 at 1:04 PM, Dominique Leuenberger wrote:

...

...

...

...

On 25-05-2008 at 09:57, Sampsa Riikonen wrote: Dear List,

I had my wireless working OK few months ago in my hp tx1000 laptop. The wireless card in this pc is broadcom bcm4312.

.. now it suddenly stopped working (maybe because upgrading regularly with the updater applet?).

In yast => network devices => etc. => wireless => configure => hardware, the list of kernel modules does not offer anything (just a blank line) .. it used to offer ndiswrapper.

I suppose this might be because of the bcm43xx driver. Well, I have blaclisted it in several files.. Why would you prefer ndiswrapper ove the native bcm43xx driver? I'd say there is no need to wrap if you have a correctly working, native linux driver available.

ndiswrapper is meant for wlan cards that do not have linux drivers (yet).

Dominique

Maybe he likes it ndiswrapper because it works and bcm does not work with his card. You know, basic stuff like that? For many, the need to be pure is less important than the need to get on line.

I don't think his question is about "being pure", whatever that means, but why someone go to all the trouble of running a wrapper around a windoze driver, when there is a perfectly good native linux driver. I've got an HP compaq v6000 laptop, running hardy heron with the native linux bcm driver, and since everything works perfectly, with no need to futz around with windoze drivers and ndiswrapper, I'd tend to have the same question. Joe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

John Andersen wrote:

On Sun, May 25, 2008 at 8:32 PM, Joe Sloan wrote:

...

John Andersen wrote:

...

...

...

...

> On 25-05-2008 at 09:57, Sampsa Riikonen > wrote: Dear List,

I had my wireless working OK few months ago in my hp tx1000 laptop. The wireless card in this pc is broadcom bcm4312.

.. now it suddenly stopped working (maybe because upgrading regularly with the updater applet?).

In yast => network devices => etc. => wireless => configure => hardware, the list of kernel modules does not offer anything (just a blank line) .. it used to offer ndiswrapper.

I suppose this might be because of the bcm43xx driver. Well, I have blaclisted it in several files.. Why would you prefer ndiswrapper ove the native bcm43xx driver? I'd say there is no need to wrap if you have a correctly working, native linux driver available.

ndiswrapper is meant for wlan cards that do not have linux drivers (yet).

Dominique Maybe he likes it ndiswrapper because it works and bcm does not work with his card. You know, basic stuff like that? For many,

On Sun, May 25, 2008 at 1:04 PM, Dominique Leuenberger wrote: the need to be pure is less important than the need to get on line.

I don't think his question is about "being pure", whatever that means, but why someone go to all the trouble of running a wrapper around a windoze driver, when there is a perfectly good native linux driver.

I've got an HP compaq v6000 laptop, running hardy heron with the native linux bcm driver, and since everything works perfectly, with no need to futz around with windoze drivers and ndiswrapper, I'd tend to have the same question.

Joe --

"HE" didn't want to be pure, but Dominique seemed to want him to be.

"HE" just wanted it to work, and the BCM driver was not working for him with his chipset. Ndiswrapper has worked for him in the past.

If he could get rid of the non-working but "perfectly good" (says you) BCM driver he could get the ndiswrapper working again and be back to an operational machine before the BCM driver improved the hell out of it.

Even the BCM driver needs to load firmware, so there is really no point in getting all high and mighty about free software when it comes to wifi drivers from broadcom.

I'm not sure who's getting "high and mighty", but that's beside the point. It sounds like the OP needed to load the bcm firmware. So, maybe it's just me, but my first thought would be "load the bcm firmware", rather than "install a wrapper program to enable to use of a wireless driver written for a different platform". In my experience, things work better when they are all of a piece. Joe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Mon, 2008-05-26 at 08:16 +0200, Dominique Leuenberger wrote:

...

...

...

On 26.05.2008 at 03:11, "John Andersen" wrote: On Sun, May 25, 2008 at 1:04 PM, Dominique Leuenberger wrote:

...

...

On 25-05-2008 at 09:57, Sampsa Riikonen wrote: Dear List,

I had my wireless working OK few months ago in my hp tx1000 laptop. The wireless card in this pc is broadcom bcm4312.

.. now it suddenly stopped working (maybe because upgrading regularly with the updater applet?).

In yast => network devices => etc. => wireless => configure => hardware, the list of kernel modules does not offer anything (just a blank line) .. it used to offer ndiswrapper.

I suppose this might be because of the bcm43xx driver. Well, I have blaclisted it in several files..

Why would you prefer ndiswrapper ove the native bcm43xx driver? I'd say there is no need to wrap if you have a correctly working, native linux driver available.

ndiswrapper is meant for wlan cards that do not have linux drivers (yet).

Dominique

Maybe he likes it ndiswrapper because it works and bcm does not work with his card. You know, basic stuff like that? For many, the need to be pure is less important than the need to get on line.

That's a nice 'maybe' sentence you can produce here, without any real content. He did not write so far that bcm does not work. I simply suggested to use the native driver that is working for so many people.

It's 'purely' amazing what an attitude of 'stcuk-upness' some people have on this list. I'm really sorry for everybody that has to read such mailing lists. And for sure our new fellows will be scared away when they have to go through the ML archives, in hope to find some help.

Can't we just stick to the topics of the questions? Answer our fellow friends, give them advises? You can follow almost every thread here and they carry on for ever, with all sort comments that are not at all related to what the original question was.

Think about this for a few minutes!

lspci gives.. --------------------- 03:00.0 Network controller: Broadcom Corporation BCM4312 802.11a/b/g (rev 02) ---------------------- And according to linuxwireless.org .. "The 802.11a part of the 4309 and 4312 is not supported" ----------------------- So I suppose I must use ndiswrapper. As you can see from my previous e-mail, the ndiswrapper installs correctly, but yast does not offer me any kernel modules. .. just wondering if it is because of that bcm43xx that refuses to disappear or what? Sampsa -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Joe Sloan wrote:

Sampsa Riikonen wrote:

...

lspci gives.. --------------------- 03:00.0 Network controller: Broadcom Corporation BCM4312 802.11a/b/g (rev 02) ---------------------- And according to linuxwireless.org .. "The 802.11a part of the 4309 and 4312 is not supported"

Ah, that's a shame. I have the 4311 which works fine.

You'd probably want to uninstall the bcm43xx driver, and go with the ndiswrapper workaround. While not advisable universally, yours seems to be one of those cases where ndiswrapper is the way to go.

Joe

Hi, blacklisted linux driver in /etc/modprobe.d/blacklist by adding blacklist bcm43xx at end of file. Having installed the windows driver (in this case from /tmp/linksys/lsbcmnds.inf, but after change of hardware followed the same recipe for a Dlink driver) using ndiswrapper as follows: ndiswrapper -i /tmp/linksys/lsbcmnds.inf then type ndiswrapper -l you should see the following # ndiswrapper -l Installed ndis drivers: lsbcmnds driver present, xyzhardware present then enable the wireless network interface -- type modprobe ndiswrapper 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). Good luck! Peter -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Mon, 2008-05-26 at 05:13 -0500, Rajko M. wrote:

On Sunday 25 May 2008 02:57:47 pm Sampsa Riikonen wrote:

...

Dear List,

I had my wireless working OK few months ago in my hp tx1000 laptop. The wireless card in this pc is broadcom bcm4312.

.. now it suddenly stopped working (maybe because upgrading regularly with the updater applet?).

In yast => network devices => etc. => wireless => configure => hardware, the list of kernel modules does not offer anything (just a blank line) .. it used to offer ndiswrapper.

Have you tried to write in that line 'ndiswrapper'.

...

I suppose this might be because of the bcm43xx driver. Well, I have blaclisted it in several files.. ------------------- linux-q5nk:/home/sampsa # grep -i "bcm" /etc/modprobe.d/blacklist blacklist bcm43xx blacklist bcm43xx linux-q5nk:/home/sampsa # grep -i "bcm" /etc/modprobe.conf.local blacklist bcm43xx --------------------- But when I.. ---------------------- linux-q5nk:/home/sampsa # modprobe -l *bcm43* /lib/modules/2.6.22.17-0.1-default/kernel/drivers/net/wireless/bcm43xx/bcm4 3xx.ko linux-q5nk:/home/sampsa # rmmod bcm43xx ERROR: Module bcm43xx does not exist in /proc/modules

The above means that bcm43xx is not loaded. Blacklisting device will not remove it from hard disk, it will not load it.

Here is my desktop result for 'modprobe -l *bcm43*' /lib/modules/2.6.22.17-0.1-default/kernel/drivers/net/wireless/bcm43xx/bcm43xx.ko where desktop is using completely different network adapter.

...

----------------------- Ndiswrapper also tells me that.. ------------------------ linux-q5nk:/home/sampsa # ndiswrapper -l bcmwl5 : driver installed device (14E4:4312) present (alternate driver: bcm43xx)

Ndiswrapper tells you that you have alternative, not that it is loaded by kernel.

...

------------------------- Then I try.. -------------------------- linux-q5nk:/home/sampsa # modprobe -r bcm43xx

The modprobe is not verbose. There was nothing to remove and it did nothing, silently.

...

linux-q5nk:/home/sampsa # modprobe -l *bcm43* /lib/modules/2.6.22.17-0.1-default/kernel/drivers/net/wireless/bcm43xx/bcm4 3xx.ko

And again it is listing where on hard disk you can find bcm43xx .

Try lsmod | grep bcm it should list you nothing, and 'lsmod' is looking only for modules that are actually loaded and used by kernel.

Thank you and sorry for the confusion.. I always thought that modprobe shows the _installed_ modules. :/ So it seems that the bcm43xx driver is not in use in my laptop.

...

--------------------------- So what the **ll I am supposed to do to get rid of this annoying driver?! And what should I do to get ndiswrapper back to the list of available kernel modules in yast? I am running suse 10.3, 32-bit version.

Write 'ndiswrapper' in YaST where usually goes module name and that should take care of problem.

I type ndiswrapper in yast, but the next time I visit the same "hardware" section, the line is empty.

See also: http://en.opensuse.org/Ndiswrapper

Thanks, I will read it carefully.. Regards, Sampsa -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Mon, 2008-05-26 at 05:48 -0500, Rajko M. wrote:

On Monday 26 May 2008 05:28:40 am Sampsa Riikonen wrote:

...

...

Try lsmod | grep bcm it should list you nothing, and 'lsmod' is looking only for modules that are actually loaded and used by kernel.

Thank you and sorry for the confusion.. I always thought that modprobe shows the _installed_ modules. :/

Yes, 'modprobe' shows installed modules. They are installed on the hard disk. Though, installed module has to be loaded from hard disk to memory (RAM) before kernel can use it. and that is what shows 'lsmod'.

The only confusion was words install vs. load . I have feeling that 'modprobe' manual is using word 'install' for loading module in memory.

...

So it seems that the bcm43xx driver is not in use in my laptop.

...

...

--------------------------- So what the **ll I am supposed to do to get rid of this annoying driver?! And what should I do to get ndiswrapper back to the list of available kernel modules in yast? I am running suse 10.3, 32-bit version.

Write 'ndiswrapper' in YaST where usually goes module name and that should take care of problem.

I type ndiswrapper in yast, but the next time I visit the same "hardware" section, the line is empty.

I had the same problem, but it was a year ago, so I'm not sure. Try to load ndiswrapper with: modprobe ndiswrapper

check that is loaded with lsmod

than go to YaST. It should be listed now.

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 -------------------- Cheers, Sampsa

-- Regards, Rajko http://en.opensuse.org/Portal needs helpful hands.

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

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

On 05/27/2008 11:27 AM, Rajko M. wrote:

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

I believe it comes from /lib/modules/{kernel-version}/modules.alias

First option is: Edit above file and replace DRIVERS=="?*" with DRIVERS=="ndiswrapper" and see would this help. You probably have 2 adapters, so check which one is wireless. Editing wrong one will kill your wired connection too. To be on safe side, copy 70-persistent-net.rules to your home directory, so that you have backup copy. I would reboot after this change, just to make sure that if it works, it will do that next time when computer is turned on.

Second option is: http://lists.berlios.de/pipermail/bcm43xx-dev/2008-April/007355.html It is a bit longer, but it should work. With openSUSE 11.0 kernel is required version and it should be much easier to use instructions.

Thanks for that link. I noticed in the home/schmolle1980/openSUSE_10.3_update repository he has a compat-wireless-kmp, compat-wireless-scripts, and b43-compat-wireless-firmware packages, which after reading the info from your link, and after installing the above packages, I was finally able to get rid of ndiswrapper from my daughter's Compaq Presario V6133CL, which has a 4311 Broadcom wireless. I was never able to get bcm43xx to work, even if I cut the firmware from the working Windows driver. All that is needed is to set the Yast Network card module to use b43 for that card, make sure blacklist bcm43xx is in /etc/modprobe.d/blacklist, reboot (or modprobe -r ndiswrapper, but that did not unload the module here). The card even works better with this driver, with a better signal level. Thanks again. -- Joe Morris Registered Linux user 231871 running openSUSE 10.3 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org