[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#495685: [#495685] firmware-iwlwifi: microcode error



On Thu, Oct 16, 2008 at 12:16:54AM +0200, Stefano Sabatini wrote:
> In data marted? 2008-10-14 20:49:17 +0200, Stefano Sabatini ha scritto:
> > In data luned? 2008-10-06 19:45:36 +0200, Didier Raboud ha scritto:
> > > Le mardi 19 ao?t 2008 19:02:56 Stefano Sabatini, vous avez ?crit?:
> > > > Package: firmware-iwlwifi
> > > > Version: 0.12
> > > > Severity: grave
> > > > Justification: renders package unusable
> > > >
> > > >
> > > > I got this when I try to load iwl3945:
> > > >
> > > > When I try the command:
> > > > modprobe iwl3945
> > > >
> > > > it hangs for half a minute, then I get this error:
> > > >
> > > > iwl3945: Detected Intel PRO/Wireless 3945ABG Network Connection
> > > > iwl3945: iwlwifi-3945-1.ucode firmware file req failed: Reason -2
> > > > iwl3945: Could not read microcode: -2
> > > > ACPI: PCI interrupt for device 0000:10:00.0 disabled
> > > > iwl3945: probe of 0000:10:00.0 failed with error -2
> > > >
> > > > I'm using firmware-iwlwifi 0.12, with a linux-2.6.24 i686 debian
> > > > custom kernel.
> > > >
> > > > Regards.
> > > 
> > > Hi, 
> > > 
> > > a new firmware-iwlwifi package is available in unstable. Please try this new 
> > > package and update your linux-image to get the latest iwlwifi driver and 
> > > report back if the problem is still alive.
> > > 
> > > N.B. I don't get any error with the firmware...
> > > 
> > > Regards, 
> > 
> > Updated to iwlwifi-firmware 0.13.
> > 
> > stefano@geppetto ~> uname -a
> > Linux geppetto 2.6.26-1-686 #1 SMP Thu Oct 9 15:18:09 UTC 2008 i686 GNU/Linux
> > 
> > 
> > stefano@geppetto ~> sudo modprobe -r iwl3945
> > stefano@geppetto ~> sudo modprobe iwl3945
> > 
> > with dmesg I get:
> > [  332.178973] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.26ks
> > [  332.178973] iwl3945: Copyright(c) 2003-2008 Intel Corporation
> > [  332.178973] ACPI: PCI Interrupt 0000:10:00.0[A] -> GSI 17 (level, low) -> IRQ 17
> > [  332.178973] PCI: Setting latency timer of device 0000:10:00.0 to 64
> > [  332.178973] iwl3945: Detected Intel Wireless WiFi Link 3945ABG
> > [  332.218972] iwl3945: Tunable channels: 13 802.11bg, 23 802.11a channels
> > [  332.218972] phy0: Selected rate control algorithm 'iwl-3945-rs'
> > 
> > stefano@geppetto ~> sudo iwconfig
> > lo        no wireless extensions.
> > 
> > eth1      no wireless extensions.
> > 
> > wmaster0  no wireless extensions.
> > 
> > wlan0     IEEE 802.11  ESSID:""  
> >           Mode:Managed  Frequency:2.412 GHz  Access Point: Not-Associated   
> >           Tx-Power=0 dBm   
> >           Retry min limit:7   RTS thr:off   Fragment thr=2352 B   
> >           Encryption key:off
> >           Link Quality:0  Signal level:0  Noise level:0
> >           Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
> >           Tx excessive retries:0  Invalid misc:0   Missed beacon:0
> > 
> > So the module looks correctly loaded.
> > 
> > stefano@geppetto ~> sudo iwlist wlan0 scanning
> > 
> > Here it hangs for 30 seconds more or less, then I get this:
> > 
> > wlan0     Interface doesn't support scanning : Network is down
> > 
> > From dmesg:
> > [  372.025418] firmware: requesting iwlwifi-3945-1.ucode
> > [  432.097666] iwl3945: iwlwifi-3945-1.ucode firmware file req failed: Reason -2
> > [  432.097676] iwl3945: Could not read microcode: -2
> > 
> > stefano@geppetto ~> locate  iwlwifi-3945-1.ucode
> > /lib/firmware/iwlwifi-3945-1.ucode
> > 
> > Hints will be highly appreciated.
> 
> And the problem was...
> 
> udevd was dead, so it couldn't load the firmware. It took me a good
> guessing effort for realizing that firmware is loaded by udev, I was
> indeed experiencing the same loading firmware problem with another
> module and finally I read something about the firmware being loaded by
> udev.
> 
> Please improve the behaviour of the module so that it will check for
> the presence of udevd and tell explicitely if it isn't present rather
> than hang forever trying to load the firmware.
> 
> Anyway, bug report has to be considered closed, now I have to
> understand why udevd was dying...

Thanks for the followup!

> Thanks, regards.


-- 
dann frazier




Reply to: