ndiswrapper

Same here, only 0.4 works.
All version after 0.4 crash my kernel.

Same chipset: bcmwl5.sys

Broadcom makes several similar but different chips.
In my experience with the truemobile 1300 and 1350
(same chip, different revision number), there is
a significant difference in stability under
ndiswrapper.

You should identify the brand and model and post your
lspci -v output related to the device.

--Donald Teed


On Thu, 26 Aug 2004, Serge Tchesmeli wrote:

> Same here, only 0.4 works.
> All version after 0.4 crash my kernel.
>
> Same chipset: bcmwl5.sys
>
>
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
> 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
> Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
> http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
> _______________________________________________
> Ndiswrapper-general mailing list
> Ndiswrapper-general@...
> https://lists.sourceforge.net/lists/listinfo/ndiswrapper-general
>
>
>

----- Original Message ----- 
From: "Donald Teed" <dteed@...>
To: "Serge Tchesmeli" <tchesmeli.serge@...>
Cc: "Mark Janssen" <maniac@...>; 
<ndiswrapper-general@...>; <maniac-ndiswrapper@...>
Sent: Thursday, August 26, 2004 5:09 PM
Subject: Re: [Ndiswrapper-general] Ndiswrapper versions after 0.4 not working 
for me (currently testing 0.10)


>
> Broadcom makes several similar but different chips.
> In my experience with the truemobile 1300 and 1350
> (same chip, different revision number), there is
> a significant difference in stability under
> ndiswrapper.
>
> You should identify the brand and model and post your
> lspci -v output related to the device.
>
> --Donald Teed

I allready do that in a previous post:

Card: Belkin F5D7000


02:0b.0 Network controller: Broadcom Corporation BCM94306 802.11g (rev 03)
        Subsystem: Belkin: Unknown device 7000
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B-
        Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
<TAbort- <MAbort- >SERR- <PERR-
        Latency: 32
        Interrupt: pin A routed to IRQ 177
        Region 0: Memory at e5000000 (32-bit, non-prefetchable) [size=8K]

On Thu, 2004-08-26 at 17:09, Donald Teed wrote:
> Broadcom makes several similar but different chips.
> In my experience with the truemobile 1300 and 1350
> (same chip, different revision number), there is
> a significant difference in stability under
> ndiswrapper.
>=20
> You should identify the brand and model and post your
> lspci -v output related to the device.

It's built-in to the acer ferrari 3000lmi laptop...
Details:
0000:00:09.0 Network controller: Broadcom Corporation BCM4306 802.11b/g
Wireless LAN Controller (rev 03)
        Subsystem: Unknown device 185f:1220
        Flags: bus master, fast devsel, latency 64, IRQ 11
        Memory at d0004000 (32-bit, non-prefetchable) [size=3D8K]

lspci -n gives: 0000:00:09.0 0280: 14e4:4320 (rev 03)


--=20
Mark Janssen -- maniac(at)maniac.nl -- GnuPG Key Id: 357D2178
Unix / Linux, Open-Source and Internet Consultant @ SyConOS IT
Maniac.nl Unix-God.Net|Org MarkJanssen.org|nl SyConOS.com|nl

On Thu, 26 Aug 2004, Serge Tchesmeli wrote:

> Card: Belkin F5D7000
>
>
> 02:0b.0 Network controller: Broadcom Corporation BCM94306 802.11g (rev 03)
> Subsystem: Belkin: Unknown device 7000
> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
> Stepping- SERR- FastB2B-
>       Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
> <TAbort- <MAbort- >SERR- <PERR-
> Latency: 32
> Interrupt: pin A routed to IRQ 177
> Region 0: Memory at e5000000 (32-bit, non-prefetchable) [size=8K]

Yay - someone else with the cursed Broadcom chip in a rev 3.
But your subsystem is different than mine.

I've got the Dell truemobile 1350 mini-PCI part, showing as:

02:03.0 Class 0280: 14e4:4320 (rev 03)

02:03.0 Network controller: Broadcom Corporation: Unknown device 4320 (rev 03)
         Subsystem: Dell Computer Corporation: Unknown device 0003
         Flags: bus master, fast devsel, latency 32, IRQ 7
         Memory at fafee000 (32-bit, non-prefetchable) [size=8K]

In my case, it will load no problem with a vanilla kernel
and in Slackware 9.  But Xandros, with a kernel patched with
what not and loading their own initrd, is unstable with ndiswrapper.
Xandros are seeing what happens when some kernel options
are peeled back.

What linux distro do you run, and what kernel does it have?

If you do get it loading without an error, it should show
the MAC address of the device from a iwconfig command.
I'd like to know if you can boot from battery power (no AC)
and whether that causes the system to lock up when
the ndiswrapper module loads.

You might want to try the Dell drivers linked on the ndiswrapper
supported chipsets list.  Like yours, this is a mini-PCI part,
so using the same driver might be meaningful.

--Donald Teed

> On Thu, 26 Aug 2004, Serge Tchesmeli wrote:
>
>> Card: Belkin F5D7000
>>
>>
>> 02:0b.0 Network controller: Broadcom Corporation BCM94306 802.11g (rev 03)
>> Subsystem: Belkin: Unknown device 7000
>> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
>> Stepping- SERR- FastB2B-
>>       Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
>> <TAbort- <MAbort- >SERR- <PERR-
>> Latency: 32
>> Interrupt: pin A routed to IRQ 177
>> Region 0: Memory at e5000000 (32-bit, non-prefetchable) [size=8K]
>
> Yay - someone else with the cursed Broadcom chip in a rev 3.
> But your subsystem is different than mine.
>
> I've got the Dell truemobile 1350 mini-PCI part, showing as:
>
> 02:03.0 Class 0280: 14e4:4320 (rev 03)
>
> 02:03.0 Network controller: Broadcom Corporation: Unknown device 4320 (rev 
> 03)
>         Subsystem: Dell Computer Corporation: Unknown device 0003
>         Flags: bus master, fast devsel, latency 32, IRQ 7
>         Memory at fafee000 (32-bit, non-prefetchable) [size=8K]
>
> In my case, it will load no problem with a vanilla kernel
> and in Slackware 9.  But Xandros, with a kernel patched with
> what not and loading their own initrd, is unstable with ndiswrapper.
> Xandros are seeing what happens when some kernel options
> are peeled back.
>
> What linux distro do you run, and what kernel does it have?


I run a slackware 10.0. Kernel is a 2.6.8.1 compiled by me. I habe joined the 
.config file for option.

>
> If you do get it loading without an error, it should show
> the MAC address of the device from a iwconfig command.

Can't load on 0.10 and 0.9. Kernel crash on modprobe ndiswrapper.
Here the debug log:

Aug 24 21:17:09 gateway kernel: bad: scheduling while atomic!
Aug 24 21:17:09 gateway kernel:  [<c04bc114>] schedule+0x480/0x485
Aug 24 21:17:09 gateway kernel:  [<f8b1167b>] call_init+0xa5/0xb4 
[ndiswrapper]
Aug 24 21:17:09 gateway kernel:  [<c012584c>] __mod_timer+0x12b/0x17d
Aug 24 21:17:09 gateway kernel:  [<c04bc554>] schedule_timeout+0x63/0xb7
Aug 24 21:17:09 gateway kernel:  [<c012629c>] process_timeout+0x0/0x9
Aug 24 21:17:09 gateway kernel:  [<f8b13746>] ndis_init_one_pci+0x112/0x20e 
[ndiswrapper]
Aug 24 21:17:09 gateway kernel:  [<c033d12f>] 
pci_device_probe_static+0x52/0x61
Aug 24 21:17:09 gateway kernel:  [<c033d179>] __pci_device_probe+0x3b/0x4e
Aug 24 21:17:09 gateway kernel:  [<c033d1b8>] pci_device_probe+0x2c/0x4a
Aug 24 21:17:09 gateway kernel:  [<c03b6b19>] bus_match+0x3f/0x6a
Aug 24 21:17:09 gateway kernel:  [<c03b6c2b>] driver_attach+0x56/0x80
Aug 24 21:17:09 gateway kernel:  [<c03b70d6>] bus_add_driver+0xa5/0xc3
Aug 24 21:17:09 gateway kernel:  [<c03b7611>] driver_register+0x2f/0x33
Aug 24 21:17:09 gateway kernel:  [<c033d3f7>] pci_register_driver+0x5c/0x84
Aug 24 21:17:09 gateway kernel:  [<f8b13d84>] start_driver+0x23b/0x273 
[ndiswrapper]
Aug 24 21:17:09 gateway kernel:  [<f8b14724>] misc_ioctl+0xea/0x1fb 
[ndiswrapper]
Aug 24 21:17:09 gateway kernel:  [<c014b335>] remove_vm_struct+0x78/0x97
Aug 24 21:17:09 gateway kernel:  [<c016f792>] dput+0x22/0x212
Aug 24 21:17:09 gateway kernel:  [<c0159443>] __fput+0xbd/0x124
Aug 24 21:17:09 gateway kernel:  [<c016b022>] sys_ioctl+0xf7/0x24d
Aug 24 21:17:09 gateway kernel:  [<c0157cd8>] sys_close+0x63/0x96
Aug 24 21:17:09 gateway kernel:  [<c0105f7f>] syscall_call+0x7/0xb

It load with 0.8, i can config with iwconfig but crash on ifconfig.


> I'd like to know if you can boot from battery power (no AC)
> and whether that causes the system to lock up when
> the ndiswrapper module loads.
>

This is not a notebook, so i can't boot on battery. This is a PCI card, not 
PCMCIA.

> You might want to try the Dell drivers linked on the ndiswrapper
> supported chipsets list.  Like yours, this is a mini-PCI part,
> so using the same driver might be meaningful.

Ok i will try, but you know this is my internet gateway and i can't reboot it 
when i want. I will try soon and report you.
(sorry my english i'm french).

On Thu, 26 Aug 2004, Serge Tchesmeli wrote:

> This is not a notebook, so i can't boot on battery. This is a PCI card, not 
> PCMCIA.

The other guy responding on this thread  ( Mark Janssen <maniac@...> )
and cc'ed on the emails said:

]  It's built-in to the acer ferrari 3000lmi laptop...

So I thought you two were working together.

My response is more true of that laptop from Acer.
Sorry that i got these two emails mixed up.

>> You might want to try the Dell drivers linked on the ndiswrapper
>> supported chipsets list.  Like yours, this is a mini-PCI part,
>> so using the same driver might be meaningful.
>
> Ok i will try, but you know this is my internet gateway and i can't reboot it 
> when i want. I will try soon and report you.

If it isn't a mini-PCI part, then you are probably best to stick
with the Windows drivers from something more similar,
or those that come from Belkin.

However, Mark Janssen might want to try out the Dell driver...

> On Thu, 26 Aug 2004, Serge Tchesmeli wrote:
>
>> This is not a notebook, so i can't boot on battery. This is a PCI card, 
>> not PCMCIA.
>
> The other guy responding on this thread  ( Mark Janssen 
> <maniac@...> )
> and cc'ed on the emails said:
>
> ]  It's built-in to the acer ferrari 3000lmi laptop...
>
> So I thought you two were working together.
>
> My response is more true of that laptop from Acer.
> Sorry that i got these two emails mixed up.


No matters :) i think i have mixed some mail too lol :)

> If it isn't a mini-PCI part, then you are probably best to stick
> with the Windows drivers from something more similar,
> or those that come from Belkin.
>
> However, Mark Janssen might want to try out the Dell driver...
>

Ok. I fact i think isn't a drivers problem but ndiswrapper one, because the 
first time bcmw5l.sys was missing in /etc/ndiswrapper/bcmw5l/ path and kernel 
was crashing on modprobe. So i think it's really a ndiswrapper trouble, 
perhaps certain kernel option.

0.4 work well.

On Thu, 26 Aug 2004, Serge Tchesmeli wrote:

> Ok. I fact i think isn't a drivers problem but ndiswrapper one, because the 
> first time bcmw5l.sys was missing in /etc/ndiswrapper/bcmw5l/ path and kernel 
> was crashing on modprobe. So i think it's really a ndiswrapper trouble, 
> perhaps certain kernel option.
>
> 0.4 work well.

Hopefully you still have a way to reboot without it loading
the module.  If you rebuild the module with:

make DEBUG=3 install

then it will spit out lots of debugging information to
whereever the dmesg type output goes (/var/log/messages probably
in Slackware).  I think the developers like to see that detail reported.

On Thu, 2004-08-26 at 18:47, Donald Teed wrote:

> Yay - someone else with the cursed Broadcom chip in a rev 3.
> But your subsystem is different than mine.

> In my case, it will load no problem with a vanilla kernel
> and in Slackware 9.  But Xandros, with a kernel patched with
> what not and loading their own initrd, is unstable with ndiswrapper.
> Xandros are seeing what happens when some kernel options
> are peeled back.
>=20
> What linux distro do you run, and what kernel does it have?

I'm running debian sid, but that  shouldn't matter, because I run
vanilla kernels (2.6.7 currently) without any relevant patches.

> If you do get it loading without an error, it should show
> the MAC address of the device from a iwconfig command.
> I'd like to know if you can boot from battery power (no AC)
> and whether that causes the system to lock up when
> the ndiswrapper module loads.

I usually bootup on battery... and plug in AC later on. This doesn't
cause any problems.

> You might want to try the Dell drivers linked on the ndiswrapper
> supported chipsets list.  Like yours, this is a mini-PCI part,
> so using the same driver might be meaningful.

I'll have a try... but last time (IIRC) they didn't work for me

--=20
Mark Janssen -- maniac(at)maniac.nl -- GnuPG Key Id: 357D2178
Unix / Linux, Open-Source and Internet Consultant @ SyConOS IT
Maniac.nl Unix-God.Net|Org MarkJanssen.org|nl SyConOS.com|nl

On Fri, 27 Aug 2004, Mark Janssen wrote:

> I'm running debian sid, but that  shouldn't matter, because I run
> vanilla kernels (2.6.7 currently) without any relevant patches.

In Slackware with vanilla 2.6.7 I'm able to load the driver without
an error.  You said you are coming from 0.4 version.  The readme
said you must reinstall drivers if coming from the
older version.  Perhaps to make sure it is clean, erase
everything under /etc/ndiswrapper and then install
the Windows driver with ndiswrapper -i
Also check on any duplicate loadndiswrapper executables
in your path.  That has caught some people coming
from older versions.

--Donald Teed