Skip to Content.
Sympa Menu

sm-discuss - Re: [SM-Discuss] ipw2200

sm-discuss AT lists.ibiblio.org

Subject: Public SourceMage Discussion List

List archive

Chronological Thread  
  • From: "Jeremy Blosser (emrys)" <jblosser-smgl AT firinn.org>
  • To: sm-discuss AT lists.ibiblio.org
  • Subject: Re: [SM-Discuss] ipw2200
  • Date: Mon, 13 Feb 2006 09:22:52 -0600

On Feb 12, Dave Josephsen [dave AT sourcemage.org] wrote:
> On Tue, Feb 07, 2006 at 09:34:27AM -0600, dave AT sourcemage.org wrote:
> > On Tue, Feb 07, 2006 at 08:09:34AM +0100, Arwed von Merkatz wrote:
> > > On Mon, Feb 06, 2006 at 08:09:31PM -0800, David Brown wrote:
> > > > > Does anyone have this working with static dev? I have a thinkpad
> > > > > and an
> > > > > hp pavillion, both running static dev, same version of hotplug on
> > > > > both.
> > > > > The thinkpad loads the firmware and driver just fine, the
> > > > > pavillion, not
> > > > > so much. I can't really figure out the difference between the two,
> > > > > and
> > > > > quite honestly I don't have a good picture of all the pieces here,
> > > > > so
> > > > > forgive my ignorance.
> > > >
> > > > is udevd running? even if you have a static dev udevd should still be
> > > > running because now it's the process that loads the firmware.
> > >
> > > For static /dev you actually want hotplug, not udev. udev won't care
> > > that /dev isn't a ramfs and just happily add and remove devices, that's
> > > not what you want on a static dev system. The hotplug init script only
> > > disables hotplug if the user uses a 2.6.15 kernel _and_ udev, not for
> > > static ones.
>
> Ok, So I've gone up to 2.6.15, and back to 2.6.13 (I need to use 13,
> because there's a reboot oops for my hardware at 2.6.15) and I've recast
> init so that I'm now running udev. No matter what combination of
> variables I use, the output of modprobe is always the same:

Multiple reports of this problem and an apparently simple fix:

http://www.linuxquestions.org/questions/showthread.php?threadid=368853

They're adding "acpi=noirq" to the boot parameters.

> ieee80211: 802.11 data/management/control stack, 1.1.9
> ieee80211: Copyright (C) 2004-2005 Intel Corporation
> <jketreno AT linux.intel.com>
> ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.0.10
> ipw2200: Copyright(c) 2003-2005 Intel Corporation
> bus pci: add driver ipw2200
> pci: Matched Device 0000:06:06.0 with Driver ipw2200
> ACPI: PCI Interrupt 0000:06:06.0[A] -> GSI 18 (level, low) -> IRQ 18
> ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
> ipw2200: Error allocating IRQ 18
> ACPI: PCI interrupt for device 0000:06:06.0 disabled
> ipw2200: probe of 0000:06:06.0 failed with error -22
>
> I'm currently at ipw2200 1.0.10, udev 84, hotplug 2004_09_23, kernel
> 2.6.13. Any ideas would be greatly appreciated!

Attachment: pgpKr0bdHG1w3.pgp
Description: PGP signature




Archive powered by MHonArc 2.6.24.

Top of Page