From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1GeDL9-0004ey-Oa for garchives@archives.gentoo.org; Sun, 29 Oct 2006 16:16:52 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.8/8.13.6) with SMTP id k9TGEdO8020312; Sun, 29 Oct 2006 16:14:39 GMT Received: from fire-eyes.org (adsl-68-250-9-164.dsl.sfldmi.ameritech.net [68.250.9.164]) by robin.gentoo.org (8.13.8/8.13.6) with ESMTP id k9TGB1ju017500 for ; Sun, 29 Oct 2006 16:11:01 GMT Received: from [192.168.1.2] (helo=[0.0.0.0]) by fire-eyes.org with esmtp (Exim 4.63) (envelope-from ) id 1GeDFU-0006YQ-Rh for gentoo-user@lists.gentoo.org; Sun, 29 Oct 2006 11:11:01 -0500 Message-ID: <4544D294.5020500@fire-eyes.org> Date: Sun, 29 Oct 2006 11:11:00 -0500 From: fire-eyes User-Agent: Thunderbird 2.0a1 (X11/20061023) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: ipw2200 + Intel Pro Wireless 2915 a/b/g: "ipw2200: Firmware error detected. Restarting." References: <453F68BC.7080504@fire-eyes.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Spam-Score: -1.4 (-) X-Spam-Report: Spam detection software, running on the system "fire-eyes", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: 7v5w7go9ub0o wrote: > Hope that you get a more useful response.... FWIW, I Had precisely these > symptoms on my Sony 2200 laptop - and can't tell you why - but it is > rock sold now. I think there were two things going on: > > 1. This might be a "kill" switch? Some of my problems were certainly due > to the kill switch. I finally noticed that the little wireless LEDs > were off. I had turned them off while using the windows OS - given that > it is susceptable to the wonderful new driver attacks - and had failed > to turn it on when booting up hardened Linux (which I believe is NOT > susectable to the driver buffer overflows). > > 2. I also suggest a step by step walk-through of the following page > (check your kernel config). > > http://gentoo-wiki.com/HARDWARE_ipw2200 > > P.S. Contrary to their suggestion, I emerged the latest driver/firmware > from portage. [...] Content analysis details: (-1.4 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.4 ALL_TRUSTED Passed through trusted hosts only via SMTP X-Archives-Salt: 9e3f22b2-090d-4998-897c-93385d5eae4f X-Archives-Hash: cc758eb7eed6c1c0856a379b519c47ff 7v5w7go9ub0o wrote: > Hope that you get a more useful response.... FWIW, I Had precisely these > symptoms on my Sony 2200 laptop - and can't tell you why - but it is > rock sold now. I think there were two things going on: > > 1. This might be a "kill" switch? Some of my problems were certainly due > to the kill switch. I finally noticed that the little wireless LEDs > were off. I had turned them off while using the windows OS - given that > it is susceptable to the wonderful new driver attacks - and had failed > to turn it on when booting up hardened Linux (which I believe is NOT > susectable to the driver buffer overflows). > > 2. I also suggest a step by step walk-through of the following page > (check your kernel config). > > http://gentoo-wiki.com/HARDWARE_ipw2200 > > P.S. Contrary to their suggestion, I emerged the latest driver/firmware > from portage. Thanks for the reply. I don't have a physical switch, but perhaps there is a software switch. This laptop has never run windows, so I can't say that is a factor. I had not seen that wiki, i'll give it a look. I also use the drivers from portage, the in-kernel ones are just too old and always have been. -- gentoo-user@gentoo.org mailing list