Total shot in the dark, but have you tried booting with: pci=noacpi noapic
Some laptops apparently won't power up the wireless unless you do this. David Looney Lan Barnes wrote: > Forwarded in case someone at Kplug is a lot smarter than I am (which is > a slam-dunk). > > > > ------------------------------------------------------------------------ > > Subject: > [Ndiswrapper-general] "probe of 0000:02:00.0 failed with error -22" > From: > Lan Barnes <[EMAIL PROTECTED]> > Date: > Sat, 1 Apr 2006 14:34:45 -0800 > To: > [EMAIL PROTECTED] > > To: > [EMAIL PROTECTED] > > Return-Path: > <[EMAIL PROTECTED]> > X-Original-To: > [EMAIL PROTECTED] > Delivered-To: > [EMAIL PROTECTED] > Received: > from localhost (localhost.localdomain [127.0.0.1]) by > linus.falleagle.net (Postfix) with ESMTP id F05C0FE56 for > <[EMAIL PROTECTED]>; Sat, 1 Apr 2006 16:54:01 -0800 (PST) > Received: > from falleagle.net [68.15.17.93] by localhost with IMAP > (fetchmail-6.2.5.5) for [EMAIL PROTECTED] (single-drop); Sat, 01 Apr > 2006 16:54:01 -0800 (PST) > Received: > from mail.linuxgeek.net ([unix socket]) by supermicro (Cyrus v2.2.12) > with LMTPA; Sat, 01 Apr 2006 16:49:09 -0800 > X-Sieve: > CMU Sieve 2.2 > Received: > from localhost (localhost [127.0.0.1]) by mail.linuxgeek.net (Postfix) > with ESMTP id 8AEBC24C0 for <[EMAIL PROTECTED]>; Sat, 1 Apr 2006 > 16:49:09 -0800 (PST) > Received: > from mail.linuxgeek.net ([127.0.0.1]) by localhost (mail.linuxgeek.net > [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 29437-01 for > <[EMAIL PROTECTED]>; Sat, 1 Apr 2006 16:49:09 -0800 (PST) > Received: > from lists-outbound.sourceforge.net (lists-outbound.sourceforge.net > [66.35.250.225]) by mail.linuxgeek.net (Postfix) with ESMTP id 46A1D23FA > for <[EMAIL PROTECTED]>; Sat, 1 Apr 2006 16:49:09 -0800 (PST) > Received: > from sc8-sf-list2-b.sourceforge.net (sc8-sf-list2-b.sourceforge.net > [10.3.1.8]) by sc8-sf-spam1.sourceforge.net (Postfix) with ESMTP id > CEADA35A0E; Sat, 1 Apr 2006 14:31:03 -0800 (PST) > Received: > from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91] > helo=mail.sourceforge.net) by sc8-sf-list2.sourceforge.net with esmtp > (Exim 4.30) id 1FPoc1-0004fF-LX for > [EMAIL PROTECTED]; Sat, 01 Apr 2006 14:30:29 -0800 > Received: > from fed1rmmtao02.cox.net ([68.230.241.37]) by mail.sourceforge.net with > esmtp (Exim 4.44) id 1FPoc1-00035i-D3 for > [EMAIL PROTECTED]; Sat, 01 Apr 2006 14:30:29 -0800 > Received: > from linus.falleagle.net ([70.181.175.248]) by fed1rmmtao02.cox.net > (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id > <[EMAIL PROTECTED]> for > <[EMAIL PROTECTED]>; Sat, 1 Apr 2006 17:30:23 -0500 > Received: > from linus.family.net (localhost.localdomain [127.0.0.1]) by > linus.falleagle.net (Postfix) with ESMTP id 89455FEE1 for > <[EMAIL PROTECTED]>; Sat, 1 Apr 2006 14:34:45 > -0800 (PST) > Received: > (from [EMAIL PROTECTED]) by linus.family.net (8.13.4/8.13.4/Submit) id > k31MYjXa006663 for [EMAIL PROTECTED]; Sat, 1 Apr > 2006 14:34:45 -0800 > X-Authentication-Warning: > linus.family.net: lbarnes set sender to [EMAIL PROTECTED] using -f > Message-ID: > <[EMAIL PROTECTED]> > MIME-Version: > 1.0 > Content-Type: > text/plain; charset=us-ascii > Content-Disposition: > inline > User-Agent: > Mutt/1.4.2.1i > X-Operating-System: > Linux linus 2.6.14-1.1656_FC4 > X-Spam-Score: > 1.0 (+) > X-Spam-Report: > Spam Filtering performed by sourceforge.net. See > http://spamassassin.org/tag/ for more details. Report problems to > http://sf.net/tracker/?func=add&group_id=1&atid=200001 1.0 > FORGED_RCVD_HELO Received: contains a forged HELO > Sender: > [EMAIL PROTECTED] > Errors-To: > [EMAIL PROTECTED] > X-BeenThere: > [EMAIL PROTECTED] > X-Mailman-Version: > 2.0.9-sf.net > Precedence: > bulk > List-Unsubscribe: > <https://lists.sourceforge.net/lists/listinfo/ndiswrapper-general>, > <mailto:[EMAIL PROTECTED]> > List-Id: > <ndiswrapper-general.lists.sourceforge.net> > List-Post: > <mailto:[EMAIL PROTECTED]> > List-Help: > <mailto:[EMAIL PROTECTED]> > List-Subscribe: > <https://lists.sourceforge.net/lists/listinfo/ndiswrapper-general>, > <mailto:[EMAIL PROTECTED]> > List-Archive: > <http://sourceforge.net/mailarchive/forum.php?forum=ndiswrapper-general> > X-Virus-Scanned: > by amavisd-new at linuxgeek.net > X-Spam-Status: > No, score=x required=3 WHITELISTED > X-Spam-Score: > - > > > 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. > > > > ------------------------------------------------------------------------ > > -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
