| View previous topic :: View next topic |
| Author |
Message |
borec
n00b
Joined: 17 Oct 2005
Posts: 20
Location: Kraków, Poland, EU
|
 Posted: Fri Jan 06, 2006 9:38 am Post subject: [solved] Kernel 2.6.15 + ndiswrapper = bug ? |
 |
|
I've been using ndiswrapper with Windows 64bit driver for Broadcom wifi card (bcmwl5).
Everything was working perfect until I upgraded kernel from 2.6.14.4 to 2.6.15 (I use gentoo-sources).
Now, when I try to load ndiswapper module I get:
| Quote: | ndiswrapper version 1.2 loaded (preempt=no,smp=no)
ndiswrapper: driver bcmwl5 (Broadcom,02/11/2005, 3.100.64.0) loaded
GSI 22 sharing vector 0xD9 and IRQ 22
ACPI: PCI Interrupt 0000:00:0b.0[A] -> GSI 17 (level, low) -> IRQ 22
----------- [cut here ] --------- [please bite here ] ---------
Kernel BUG at include/linux/gfp.h:80
invalid operand: 0000 [1]
CPU 0
Modules linked in: ndiswrapper
Pid: 6146, comm: loadndisdriver Tainted: P 2.6.15-gentoo #1
RIP: 0010:[<ffffffff8011c0b1>] <ffffffff8011c0b1>{dma_alloc_pages+21}
RSP: 0018:ffff810010e7b9c0 EFLAGS: 00010202
RAX: 0000000000000005 RBX: 0000000000000001 RCX: 00000000000004d1
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 00000000000004d5
RBP: 00000000000004d5 R08: ffff810010e7bb38 R09: 0000000000000008
R10: 000000000000000d R11: ffffffff880070ac R12: 00000000ffffffff
R13: ffff81001dc81870 R14: 0000000000001000 R15: ffff810010e7ba18
FS: 00002aaaaadecae0(0000) GS:ffffffff80527800(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 00002aaaaac512e0 CR3: 000000001cae3000 CR4: 00000000000006e0
Process loadndisdriver (pid: 6146, threadinfo ffff810010e7a000, task ffff810010ed30e0)
Stack: 000000000000000d ffffffff8011c2e9 ffff810010e7bb30 0000000000000001
0000000000001000 0000000000000001 ffff810010e7bb30 ffff810010e7bb38
0000000000000001 ffffffff880070e3
Call Trace:<ffffffff8011c2e9>{dma_alloc_coherent+105} <ffffffff880070e3>{:ndiswrapper:NdisMAllocateSharedMemory+55}
<ffffffff88007062>{:ndiswrapper:NdisMAllocateMapRegisters+53}
<ffffffff8801592a>{:ndiswrapper:lin_to_win6+30} <ffffffff80226162>{__pci_bus_find_cap+33}
<ffffffff880113a6>{:ndiswrapper:miniport_init+105} <ffffffff88002d78>{:ndiswrapper:ndiswrapper_add_pci_device+459}
<ffffffff80227f84>{pci_device_probe+86} <ffffffff802b7864>{driver_probe_device+65}
<ffffffff802b7965>{__driver_attach+58} <ffffffff802b792b>{__driver_attach+0}
<ffffffff802b6f9e>{bus_for_each_dev+67} <ffffffff802b73e1>{bus_add_driver+116}
<ffffffff802b7ccd>{driver_register+56} <ffffffff80227e13>{__pci_register_driver+135}
<ffffffff88003524>{:ndiswrapper:wrapper_ioctl+983} <ffffffff80171674>{do_ioctl+72}
<ffffffff801718c5>{vfs_ioctl+589} <ffffffff8017190e>{sys_ioctl+60}
<ffffffff8010e57a>{system_call+126}
Code: 0f 0b 68 e6 f8 3d 80 c2 50 00 48 63 d0 48 6b d2 28 48 81 c2
RIP <ffffffff8011c0b1>{dma_alloc_pages+21} RSP <ffff810010e7b9c0>
<3>ndiswrapper (wrapper_init:1531): loadndiswrapper failed (11); check system log for messages from 'loadndisdriver'
Unable to handle kernel NULL pointer dereference at 0000000000000000 RIP:
<ffffffff803ada63>{wait_for_completion+98}
PGD 10eb4067 PUD 11328067 PMD 0
Oops: 0002 [2]
CPU 0
Modules linked in: ndiswrapper
Pid: 6142, comm: modprobe Tainted: P 2.6.15-gentoo #1
RIP: 0010:[<ffffffff803ada63>] <ffffffff803ada63>{wait_for_completion+98}
RSP: 0018:ffff81001aa1dc38 EFLAGS: 00010002
RAX: ffffffff8802c510 RBX: ffffffff8802c508 RCX: 0000000000000000
RDX: ffff81001aa1dc80 RSI: ffff81001aa1dc60 RDI: ffff81001aa1dc90
RBP: ffff81001aa1dca8 R08: ffff81001aa1c000 R09: 0000000000000000
R10: ffffffff802b7f4e R11: ffffffff802b7f4e R12: ffffffff80454bb0
R13: ffffc20002541858 R14: 0000000000000018 R15: ffff81001998bd50
FS: 00002aaaaaf00d50(0000) GS:ffffffff80527800(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 0000000000000000 CR3: 0000000010eee000 CR4: 00000000000006e0
Process modprobe (pid: 6142, threadinfo ffff81001aa1c000, task ffff81001125a340)
Stack: 0000000000000000 ffff81001125a340 ffffffff8012ab01 0000000000000000
0000000000000000 ffffffff80192b8d 0000000000000001 ffff81001125a340
ffffffff8012ab01 ffffffff8802c510
Call Trace:<ffffffff8012ab01>{default_wake_function+0} <ffffffff80192b8d>{sysfs_hash_and_remove+46}
<ffffffff8012ab01>{default_wake_function+0} <ffffffff802b7519>{bus_remove_driver+128}
<ffffffff802b7cde>{driver_unregister+13} <ffffffff80227e45>{pci_unregister_driver+16}
<ffffffff80177b9f>{generic_delete_inode+0} <ffffffff8800425a>{:ndiswrapper:loader_exit+83}
<ffffffff88013997>{:ndiswrapper:module_cleanup+6} <ffffffff8802f0eb>{:ndiswrapper:wrapper_init+235}
<ffffffff80143b51>{sys_init_module+5498} <ffffffff80149ee4>{generic_file_read+178}
<ffffffff8802f000>{:ndiswrapper:wrapper_init+0} <ffffffff8013e8bb>{autoremove_wake_function+0}
<ffffffff80161de9>{vfs_read+173} <ffffffff8016211e>{sys_read+69}
<ffffffff8010e57a>{system_call+126}
Code: 48 89 11 48 89 4a 08 65 48 8b 04 25 00 00 00 00 48 c7 00 02
RIP <ffffffff803ada63>{wait_for_completion+98} RSP <ffff81001aa1dc38>
CR2: 0000000000000000] |
I tried with ndiswrapper 1.2, 1.5 and 1.7 - every version gives me the same message.
Kernel 2.6.14.4 works fine with 1.2 and 1.5 (not tested with 1.7).
Any clue?
PS I'm running Gentoo ~amd64 on AMD Turion 64bit based system.
_________________
I don't trust anything that bleeds for five days and doesn't die.
Last edited by borec on Mon Jan 09, 2006 12:02 am; edited 1 time in total |
|
| Back to top |
|
 |
mikkoloo
Apprentice
Joined: 04 Nov 2003
Posts: 159
Location: .se and .nl
|
| Posted: Sat Jan 07, 2006 5:00 pm Post subject: |
|
|
I got almost the same hardware as you and i get the same stuff. last time i just re-emerged ndiswrapper and it was fine but that doesnt help this time..
edit: i reversed to 2.6.14-r7 and it works fine using ndiswrapper 1.7.
_________________
----
AMD 64 4000+, nforce4 mobo, 2GB RAM, 200Gb SATA HDD, xfx Geforce 7900GT XE
----
HP pavilion zv5470EA: AMD 64 3400+, 512 Mb RAM, 80 Gb HDD, nvidia GeForce4 440 Go 64M, Cabletron RoamAbout 802.11 DS (orinoco gold) WiFi. Creative Webcam Pro (ov511) |
|
| Back to top |
|
|
alby.to
n00b
Joined: 29 Sep 2005
Posts: 12
Location: Italy - Turin
|
| Posted: Sun Jan 08, 2006 2:31 pm Post subject: |
|
|
Shit... I'm getting the same. And, guess what? I've got a Turion with broadcom... Using the same xp64 driver. I tried with ndiswrapper 1.7, 1.5, 1.2 and it's all the same.
I'll stick with 2.6.14-ck8...
_________________
* AthlonXP 3200+ - 1024M 333 - ABIT NF7 - GF 4200Ti 128 - 2x120G ATA133 - Cinergy 600 TV - SBLive! 1024
* Athlon64 3000+ - 2048M 400 - ASUS K8N-E Dlx - GF 6600GT 256 - 2x250G SATA - Audigy 2 ZS
* Aspire 5024WLMi - Turion ML-34 - 1024M - ATI X700 - 100G |
|
| Back to top |
|
|
borec
n00b
Joined: 17 Oct 2005
Posts: 20
Location: Kraków, Poland, EU
|
| Posted: Sun Jan 08, 2006 2:44 pm Post subject: |
|
|
What about native linux Broadcom drivers? Installation instruction is somewhere on this forum. Anybody tried that? I will try it soon when I find some free time.
_________________
I don't trust anything that bleeds for five days and doesn't die. |
|
| Back to top |
|
|
lxnay
Retired Dev
Joined: 09 Apr 2004
Posts: 661
Location: Italy
|
| Posted: Sun Jan 08, 2006 5:09 pm Post subject: |
|
|
the same here. We have to wait a working version of ndiswrapper for 2.6.15 kernel...
_________________
http://www.sabayon.org |
|
| Back to top |
|
|
mikkoloo
Apprentice
Joined: 04 Nov 2003
Posts: 159
Location: .se and .nl
|
| Posted: Sun Jan 08, 2006 10:39 pm Post subject: |
|
|
will that broadcom driver support every broadcom chipset? that would be great, there are a lot of laptops out there with that one for example. i love ndiswrapper for making my hardware possible to work, but native drivers is of course to prefer. whichever does the job best people will use.
_________________
----
AMD 64 4000+, nforce4 mobo, 2GB RAM, 200Gb SATA HDD, xfx Geforce 7900GT XE
----
HP pavilion zv5470EA: AMD 64 3400+, 512 Mb RAM, 80 Gb HDD, nvidia GeForce4 440 Go 64M, Cabletron RoamAbout 802.11 DS (orinoco gold) WiFi. Creative Webcam Pro (ov511) |
|
| Back to top |
|
|
borec
n00b
Joined: 17 Oct 2005
Posts: 20
Location: Kraków, Poland, EU
|
| Posted: Sun Jan 08, 2006 10:44 pm Post subject: |
|
|
| mikkoloo wrote: | | will that broadcom driver support every broadcom chipset? that would be great, there are a lot of laptops out there with that one for example. i love ndiswrapper for making my hardware possible to work, but native drivers is of course to prefer. whichever does the job best people will use. |
Here is the list of supported hardware. The driver supports 43xx chipsets.
_________________
I don't trust anything that bleeds for five days and doesn't die. |
|
| Back to top |
|
|
alby.to
n00b
Joined: 29 Sep 2005
Posts: 12
Location: Italy - Turin
|
| Posted: Sun Jan 08, 2006 11:29 pm Post subject: |
|
|
| lxnay wrote: | | the same here. We have to wait a working version of ndiswrapper for 2.6.15 kernel... |
I've just tried ndiswrapper-1.8rc1 from the homepage and it works perfectly...
Ciao!
_________________
* AthlonXP 3200+ - 1024M 333 - ABIT NF7 - GF 4200Ti 128 - 2x120G ATA133 - Cinergy 600 TV - SBLive! 1024
* Athlon64 3000+ - 2048M 400 - ASUS K8N-E Dlx - GF 6600GT 256 - 2x250G SATA - Audigy 2 ZS
* Aspire 5024WLMi - Turion ML-34 - 1024M - ATI X700 - 100G |
|
| Back to top |
|
|
borec
n00b
Joined: 17 Oct 2005
Posts: 20
Location: Kraków, Poland, EU
|
| Posted: Mon Jan 09, 2006 12:02 am Post subject: |
|
|
It works for me too 
_________________
I don't trust anything that bleeds for five days and doesn't die. |
|
| Back to top |
|
|
sanmartin
Tux's lil' helper
Joined: 10 Aug 2005
Posts: 138
Location: Massachusetts
|
| Posted: Thu Jan 12, 2006 2:14 am Post subject: |
|
|
| borec wrote: | | mikkoloo wrote: | | will that broadcom driver support every broadcom chipset? that would be great, there are a lot of laptops out there with that one for example. i love ndiswrapper for making my hardware possible to work, but native drivers is of course to prefer. whichever does the job best people will use. |
Here is the list of supported hardware. The driver supports 43xx chipsets. |
I've got a laptop in that list, but where do I find the driver? Is it in the kernel somewhere or is it a separate package? I wanna try it so I don't have to compile ndiswrapper myself. I'm lazy.
edit: I suppose I should search before I speak. I'll post my experience if anyone's interested.
edit2: Looks like it only has the ~ppc keyword, so... nevermind. I'll just wait for the new ndiswrapper.
Last edited by sanmartin on Thu Jan 12, 2006 2:22 am; edited 2 times in total |
|
| Back to top |
|
|
|
Networking & Security
