I've been playing with ndiswrapper and the Broadcom drivers. The version of
ndiswrapper that comes with SuSE 10.0 is 1.2-2.
The 32-bit Windows driver is:
bcmwl5.inf
bcmwl5.sys
When using these drivers, ndiswrapper -l shows
bcmwl5 driver present, hardware present
But, the 32-bit Windows driver does not work with a 64-bit kernel (and that
is very clearly documented in the FAQ).
The BCMWL564.SYS, the 64-bit driver shows:
bcmwl5 driver present
But does not show the hardware. After the modprobe, dmesg shows nothing, and
YaSt does not detect it.
In researching some documents, there is some indication that the 1.2-2
ndiswrapper may be broken and that either I should go back to 1.1 (I think
used in an earlier version) or 1.13 from Sourceforge.
I have also tried Linuxant's DriverLoader.
Note that I installed and built ndiswrapper kernel source since the binary
module.
Has anyone had success on a recent laptop with the Broadcom wireless chips
in 64-bit mode. I have seen some success stories.
--
Jerry Feldman
On Tue, 2006-04-18 at 15:39 -0400, Jerry Feldman wrote:
Has anyone had success on a recent laptop with the Broadcom wireless chips in 64-bit mode. I have seen some success stories.
I'm running 64bit linux with the Broadcom wireless. This is on an HP nx6125. Here's what dmesg gives me when I load the driver: ndiswrapper version 1.13 loaded (preempt=no,smp=no) ndiswrapper (load_pe_images:573): fixing KI_USER_SHARED_DATA address in the driver ndiswrapper: driver bcmwl5 (Broadcom,02/11/2005, 3.100.64.0) loaded lspci -v: 02:02.0 Network controller: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller (rev 02) Subsystem: Hewlett-Packard Company nx6125 Flags: bus master, fast devsel, latency 64, IRQ 50 Memory at d0010000 (32-bit, non-prefetchable) [size=8K] This under Gentoo though, but it did work in SUSE 10.0 (unfortunately a bunch of other things didn't, so I'm holding out for 10.1...) It may be that ndiswrapper is too old. I did notice that my wireless performance and stability improved quite substantially with each new version of ndiswrapper and the kernel.
Solved.
Thanks to Lawrence Ferreira and Hans du Plooy. The problem was that I did not run ndiswrapper -d
Here are the steps:
First, get the Windows driver.
On SuSE 10.0 you need to install the km_ndiswrapper sources as well as the kernel sources. Once that was done, build the ndiswrapper module.
Here are the steps:
first, identify the chip:
you can run lspci:
02:02.0 Network controller: Broadcom Corporation: Unknown device 4319 (rev 02)
This shows me the chip.
The run pcitweak -l:
PCI: 02:02:0: chip 14e4,4319 card 103c,1358 rev 02 class 02,80,00 hdr 00
This shows me the pciid.
Then (as root)
# ndiswrapper -i bcmwl5.inf
# ndiswrapper -d 14e4,4319 bcmwl5
# ndiswrapper -l
Installed ndis drivers:
bcmwl5 driver present, hardware present
# modprobe ndiwwrapper
At this point run dmesg:
ndiswrapper version 1.2 loaded (preempt=no,smp=no)
ndiswrapper: driver bcmwl5 (Broadcom,02/11/2005, 3.100.64.0) loaded
ACPI: PCI Interrupt 0000:02:02.0[A] -> GSI 22 (level, low) -> IRQ 217
ndiswrapper: using irq 217
wlan0: ndiswrapper ethernet device 00:14:a5:4d:9e:40 using driver bcmwl5, configuration file 14E4:4319.5.conf
wlan0: encryption modes supported: WEP, WPA with TKIP, WPA with AES/CCMP
wlan0: no IPv6 routers present
In the past, I performed all the correct steps other than "ndiswrapper -d"
--
Jerry Feldman
Nice... nice... It was my pleasure to help you... Do not forget to run: ndiswrapper -m (to write the configuration for modprobe) That's it... _________________________________________________________ Lawrence Ferreira AIX, HP-UX and SuSE Linux Enterprise Server Administrator LINUX User (openSUSE-10.0 & SLES9) #271016 LPIC-1 - Linux Certified Professional Jerry Feldman wrote:
Solved. Thanks to Lawrence Ferreira and Hans du Plooy. The problem was that I did not run ndiswrapper -d
Here are the steps: First, get the Windows driver. On SuSE 10.0 you need to install the km_ndiswrapper sources as well as the kernel sources. Once that was done, build the ndiswrapper module.
Here are the steps: first, identify the chip: you can run lspci: 02:02.0 Network controller: Broadcom Corporation: Unknown device 4319 (rev 02) This shows me the chip. The run pcitweak -l: PCI: 02:02:0: chip 14e4,4319 card 103c,1358 rev 02 class 02,80,00 hdr 00 This shows me the pciid.
Then (as root) # ndiswrapper -i bcmwl5.inf # ndiswrapper -d 14e4,4319 bcmwl5 # ndiswrapper -l Installed ndis drivers: bcmwl5 driver present, hardware present # modprobe ndiwwrapper At this point run dmesg: ndiswrapper version 1.2 loaded (preempt=no,smp=no) ndiswrapper: driver bcmwl5 (Broadcom,02/11/2005, 3.100.64.0) loaded ACPI: PCI Interrupt 0000:02:02.0[A] -> GSI 22 (level, low) -> IRQ 217 ndiswrapper: using irq 217 wlan0: ndiswrapper ethernet device 00:14:a5:4d:9e:40 using driver bcmwl5, configuration file 14E4:4319.5.conf wlan0: encryption modes supported: WEP, WPA with TKIP, WPA with AES/CCMP wlan0: no IPv6 routers present
In the past, I performed all the correct steps other than "ndiswrapper -d"
On Wednesday 19 April 2006 12:12 pm, Lawrence Ferreira wrote:
Nice... nice...
It was my pleasure to help you...
Do not forget to run: ndiswrapper -m (to write the configuration for modprobe) Of course. I probably should have been more detailed in my description, but I think that most people should get the gist of it. The problem is that most of the websites that document ndiswrapper do not mentioned the -d option.
In any case, while it was not critical for me to get wireless up on my
laptop, we have a Linux installfest next month and I do know of at least
one person who may need some help. And, since we have a meeting 2nite, I
like to be able to log into MIT's network. It makes my IQ go up a few
points :-)
--
Jerry Feldman
On Wednesday 19 April 2006 19:27, Jerry Feldman wrote:
Of course. I probably should have been more detailed in my description, but I think that most people should get the gist of it. The problem is that most of the websites that document ndiswrapper do not mentioned the -d option.
Very true. With SuSE 10.0, I didn't need it, and ndiswrapper worked. But being the adventurous soul that I am, I blew it away and installed 10.1.rc1. Just for fun, so to speak. The only thing I couldn't get to work was the wireless. Tried all the commands I knew from the last installation. None worked. But the -d did it for 10.1. So I'll leave it for now. Thanks for putting all the info out there. Just what I needed. Mike -- Powered by SuSE 10.0 Kernel 2.6.13 KDE 3.4 Kmail 1.8 For Mondo/Mindi backup support go to http://www.mikenjane.net/~mike 9:04pm up 14 days 1:50, 4 users, load average: 1.00, 1.13, 1.18
On Wednesday 19 April 2006 18:12, Lawrence Ferreira wrote:
Nice... nice...
It was my pleasure to help you...
He's not the only one you helped. I'd like to add my thanks also. I didn't know about the -d command, and after that, everything works. Thanks again. Mike -- Powered by SuSE 10.0 Kernel 2.6.13 KDE 3.4 Kmail 1.8 For Mondo/Mindi backup support go to http://www.mikenjane.net/~mike 9:02pm up 14 days 1:48, 4 users, load average: 1.01, 1.20, 1.21
On Wednesday 19 April 2006 18:12, Lawrence Ferreira wrote:
Nice... nice...
It was my pleasure to help you...
He's not the only one you helped. I'd like to add my thanks also. I didn't know about the -d command, and after that, everything works.
Thanks again. It is one of those things that should have been mentioned on the large number of references. When I first saw Lawrence's post, I had done everything that he proposed except the ndiswrapper -d. it just goes to
On Wednesday 19 April 2006 3:03 pm, Mike wrote:
prove that some of us know-it-alls are not as knowledgable as we like
everyone else to believe.
In any case, I'll get my know-it-all hat back on when I go to MIT
tonight :-)
--
Jerry Feldman
On Wed, 2006-04-19 at 12:01 -0400, Jerry Feldman wrote:
Solved. Thanks to Lawrence Ferreira and Hans du Plooy. The problem was that I did not run ndiswrapper -d
No problem. I used the README.SUSE (I think) that comes with ndiswrapper in SUSE. I didn't have to do ndiswrapper -d, I was actually surprised at how easily I got it going. Maybe I was just lucky :-) Hans
On Wed, 2006-04-19 at 12:01 -0400, Jerry Feldman wrote:
Solved. Thanks to Lawrence Ferreira and Hans du Plooy. The problem was that I did not run ndiswrapper -d
No problem. I used the README.SUSE (I think) that comes with ndiswrapper in SUSE. I didn't have to do ndiswrapper -d, I was actually surprised at how easily I got it going. Maybe I was just lucky :-) The issue appeared to be that the 32-bit driver that I got from the HP Windows service pack (SP32158.exe) was able to detect the chip. Apparently
On Wednesday 19 April 2006 7:48 pm, Hans du Plooy wrote:
the 64-bit driver did not so that the chip address had to be entered. And,
it passed its first test last night at MIT. It came up very nicely. And, as
I mentioned, being at MIT automatically gives us a few additional geek
points.
--
Jerry Feldman
participants (4)
-
Hans du Plooy -
Jerry Feldman -
Lawrence Ferreira -
Mike