Forwarded in case someone at Kplug is a lot smarter than I am (which is
a slam-dunk).
--
Lan Barnes [EMAIL PROTECTED]
Linux Guy, SCM Specialist 858-354-0616
Tcl/Tk Enthusiast
--- Begin Message ---
I have a Toshiba Satellite 45-S120 laptop running FC4. Previously under
FC3 I had an Airlink 101 (AWL C4030) working using the old madwifi.
Upgrading to FC4 broke that. Not trusting the Airlink, I bought a D-Link
DWL-G650. Neither the madwifi rpm's or compiles of various tips of
madwifi-ng made it work (I realize this isn't a madwifi list, but bear
with me -- this info may help you help me).
For the record, both cards failed madwifi with this output:
Feb 12 23:10:38 gypsy kernel: ath_hal: no version for "struct_module"
found: kernel tainted.
Feb 12 23:10:38 gypsy kernel: ath_hal: module license 'Proprietary'
taints kernel.
Feb 12 23:10:38 gypsy kernel: ath_hal: 0.9.14.9 (AR5210, AR5211, AR5212,
RF5111, RF5112, RF2413)
Feb 12 23:10:39 gypsy kernel: wlan: 0.8.6.0 (EXPERIMENTAL)
Feb 12 23:10:39 gypsy kernel: ath_rate_sample: 1.2
Feb 12 23:10:39 gypsy kernel: ath_pci: 0.9.6.0 (EXPERIMENTAL)
Feb 12 23:10:39 gypsy kernel: PCI: Enabling device 0000:02:00.0 (0000 ->
0002)
Feb 12 23:10:39 gypsy kernel: ACPI: PCI Interrupt 0000:02:00.0[A] ->
Link [LNKC] -> GSI 11 (level, low) -> IRQ 11
Feb 12 23:10:39 gypsy kernel: ath_attach: unable to attach hardware:
'Hardware didn't respond as expected' (HAL status 3)
Feb 12 23:10:39 gypsy kernel: ACPI: PCI interrupt for device
0000:02:00.0 disabled
OK, so on to ndiswrappers. I searched the driver list and found the
drivers for both cards. Here is my Airlink dir:
[EMAIL PROTECTED] atheros]# ls -l ndis5x/
total 664
-rw-rw-rw- 1 root root 320032 May 31 2003 ar52119x.sys
-rw-rw-rw- 1 root root 320032 May 31 2003 ar5211.sys
-r--r--r-- 1 root root 26 May 31 2003 net5211.cat
-rw-rw-rw- 1 root root 16699 May 31 2003 net5211.inf
Here is my D-Link driver set:
[EMAIL PROTECTED] ~]# ll d-lDriver
total 828
-rw-rw-rw- 1 root root 405056 Jun 24 2004 ar52119x.sys
-rw-rw-rw- 1 root root 405056 Jun 24 2004 ar5211.sys
-rw-rw-rw- 1 root root 26 May 27 2004 net5211.cat
-rw-rw-rw- 1 root root 21392 Jun 24 2004 net5211.inf
I followed the wiki procedure for installing ndiswrappers. All went
without error until the 'modprobe ndiswrappers' step. Then both cards
failed with this general ugliness:
Airlink:
PCI: Enabling device 0000:02:00.0 (0000 -> 0002)
ACPI: PCI Interrupt 0000:02:00.0[A] -> Link [LNKC] -> GSI 11 (level,
low) -> IRQ 11
ndiswrapper (NdisWriteErrorLogEntry:246): log: C0001391, count: 4,
return_address: dfcdcaec
ndiswrapper (NdisWriteErrorLogEntry:249): code: 3538089608
ndiswrapper (NdisWriteErrorLogEntry:249): code: 1
ndiswrapper (NdisWriteErrorLogEntry:249): code: 0
ndiswrapper (NdisWriteErrorLogEntry:249): code: 0
ndiswrapper (miniport_init:228): couldn't initialize device: C0000001
ndiswrapper (pnp_start_device:490): Windows driver couldn't initialize
the device (C0000001)
ndiswrapper: probe of 0000:02:00.0 failed with error -22
D-Link
PCI: Enabling device 0000:02:00.0 (0000 -> 0002)
ACPI: PCI Interrupt 0000:02:00.0[A] -> Link [LNKC] -> GSI 11 (level,
low) -> IRQ 11
PCI: Setting latency timer of device 0000:02:00.0 to 64
ndiswrapper (NdisWriteErrorLogEntry:246): log: C0001389, count: 4,
return_address: dfcdcb84
ndiswrapper (NdisWriteErrorLogEntry:249): code: 3524884104
ndiswrapper (NdisWriteErrorLogEntry:249): code: 40
ndiswrapper (NdisWriteErrorLogEntry:249): code: 3477274624
ndiswrapper (NdisWriteErrorLogEntry:249): code: 3477274624
ndiswrapper (miniport_init:228): couldn't initialize device: C000009A
ndiswrapper (pnp_start_device:490): Windows driver couldn't initialize
the device (C0000001)
ndiswrapper: probe of 0000:02:00.0 failed with error -22
I see no difference.
My first question is, does anybody get this, because I sure don't?
I an wondering if there is some BIOS setting on the Toshiba, or some FC4
kernel setting, or some Toshiba mojo that I'm not getting right.
Oh, and FWIW, the D-Link card installed perfectly and worked right away
on the Win XP laptop that my work sent me home with. So I'm thinking the
cards are OK and I'm betting that ndiswrappers (and maybe madwifi) is
OK.
I really would be grateful for any help or insight. I'm an SCM analyst
and database app programmer, and all this is obviously over my head.
Thanks to the core and volunteers for all the work you've done on
ndiswrappers.
--
Lan Barnes [EMAIL PROTECTED]
Linux Guy, SCM Specialist 858-354-0616
Tcl/Tk Enthusiast
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Ndiswrapper-general mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/ndiswrapper-general
--- End Message ---
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
