Incorrect Intel firmware file name

Bug #453064 reported by Pär Lindfors
56
This bug affects 11 people
Affects Status Importance Assigned to Milestone
linux-backports-modules-2.6.31 (Ubuntu)
Invalid
Undecided
Unassigned
Karmic
Won't Fix
Undecided
Unassigned
linux-backports-modules-2.6.32 (Ubuntu)
Fix Released
Low
Andy Whitcroft
Karmic
Invalid
Undecided
Unassigned

Bug Description

/lib/firmware/2.6.31-14-generic/lbm-iwlwifi-5000-1.ucode is API v2 and
should be named lbm-iwlwifi-5000-2.ucode. As you see the -1 LBM
package matches the -2 file in linux-firmware:

$ sha1sum /lib/firmware/{,"2.6.31-14-generic/"}*iwlwifi-5000-*
f06ff86c8baa8616de584f8b0fff072a9aab6a44 /lib/firmware/iwlwifi-5000-1.ucode
b1dc5068cd536a97af7e3c0090a5a632d09ab2f3 /lib/firmware/iwlwifi-5000-2.ucode
b1dc5068cd536a97af7e3c0090a5a632d09ab2f3 /lib/firmware/2.6.31-14-generic/lbm-iwlwifi-5000-1.ucode

Also confirmed this by downloading the firmware iwlwifi-5000-2.ucode
from Intel:

b1dc5068cd536a97af7e3c0090a5a632d09ab2f3 iwlwifi-5000-2.ucode

WiFi works, but the file name problem case the following kernel error
messages:

[ 137.691196] iwlagn 0000:03:00.0: firmware: requesting lbm-iwlwifi-5000-2.ucode
[ 138.136768] iwlagn 0000:03:00.0: lbm-iwlwifi-5000-2.ucode firmware file req failed: -2
[ 138.136828] iwlagn 0000:03:00.0: firmware: requesting lbm-iwlwifi-5000-1.ucode
[ 138.290188] iwlagn 0000:03:00.0: Loaded firmware lbm-iwlwifi-5000-1.ucode, which is deprecated. Please use API v2 instead.
[ 138.290254] iwlagn 0000:03:00.0: loaded firmware version 8.24.2.12
[ 138.466569] Registered led device: iwl-phy0::radio
[ 138.466595] Registered led device: iwl-phy0::assoc
[ 138.466625] Registered led device: iwl-phy0::RX
[ 138.466643] Registered led device: iwl-phy0::TX

After renaming lbm-iwlwifi-5000-1.ucode to lbm-iwlwifi-5000-2.ucode
the above messages is replaced by:

[ 30.302953] iwlagn 0000:03:00.0: firmware: requesting lbm-iwlwifi-5000-2.ucode
[ 30.400389] iwlagn 0000:03:00.0: loaded firmware version 8.24.2.12
[ 30.576366] Registered led device: iwl-phy0::radio
[ 30.576389] Registered led device: iwl-phy0::assoc
[ 30.576407] Registered led device: iwl-phy0::RX
[ 30.576423] Registered led device: iwl-phy0::TX

ProblemType: Bug
Architecture: amd64
Date: Fri Oct 16 14:24:08 2009
DistroRelease: Ubuntu 9.10
Package: linux-backports-modules-2.6.31-14-generic 2.6.31-14.16
ProcEnviron:
 LANGUAGE=
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.47-generic
SourcePackage: linux-backports-modules-2.6.31
Uname: Linux 2.6.31-14-generic x86_64
XsessionErrors: (polkit-gnome-authentication-agent-1:2123): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

Revision history for this message
Pär Lindfors (paran) wrote :
Pär Lindfors (paran)
tags: added: bitesize
Revision history for this message
Greg Oliver (oliver-greg) wrote :

Same Here.... I have an email into intel to find out if having that message actually makes the driver use v1 features though, since my wireless with the 5300 is the most stable on 5GHz that I have ever had with linux... The v1 firmware, while not having as fast of speed with 40mhz fat channels, is solid on keeping the connection in this combo currently...

greg@ghost-linux:~$ find /lib/firmware/ -iname *iwl*5000* -exec ls -la {} \;
-rw-r--r-- 1 root root 353240 2009-10-14 19:54 /lib/firmware/2.6.31-14-generic/lbm-iwlwifi-5000-1.ucode
-rw-r--r-- 1 root root 345008 2009-10-17 17:55 /lib/firmware/iwlwifi-5000-1.ucode
-rw-r--r-- 1 root root 353240 2009-10-17 17:55 /lib/firmware/iwlwifi-5000-2.ucode

-Greg

Revision history for this message
Jonathon Fernyhough (jfernyhough) wrote :

Confirmed. A simple rename (I used a symlink) of /lib/firmware/2.6.31-14-generic/lbm-iwlwifi-5000-1.ucode to lbm-iwlwifi-5000-2.ucode fixes the problem. I imagine this will be the same for lbm-iwlwifi-5150-1.ucode

Changed in linux-backports-modules-2.6.31 (Ubuntu):
status: New → Confirmed
Revision history for this message
strowger (strowger) wrote :

Adding this symlink fixes things for me:

rwxrwxrwx 1 root root 34 2009-11-04 11:01 /lib/firmware/2.6.31-14-generic/lbm-iwlwifi-5000-2.ucode -> /lib/firmware/iwlwifi-5000-2.ucode

It may be co-incidence, but without the symlink I was experiencing very unstabie connections - Thinkpad R500, Karmic amd64 - whereas with it things are stable. Without the symlink I get logged:

[ 40.952984] iwlagn 0000:03:00.0: firmware: requesting lbm-iwlwifi-5000-2.ucode
[ 42.076259] iwlagn 0000:03:00.0: lbm-iwlwifi-5000-2.ucode firmware file req failed: -2
[ 42.077434] iwlagn 0000:03:00.0: firmware: requesting lbm-iwlwifi-5000-1.ucode
[ 42.290014] iwlagn 0000:03:00.0: Loaded firmware lbm-iwlwifi-5000-1.ucode, which is deprecated. Please use API v2 instead.

I then have frequent disconnections of the wireless, accompanied by:

iwlagn 0000:03:00.0: Microcode SW error detected. Restarting 0x2000000

As well as numerous Kernel oops'es.

[Without the backports installed I, I experience frequent lockups unless I disable wireless]

Revision history for this message
Greg Oliver (oliver-greg) wrote : Re: [Bug 453064] Re: Incorrect Intel firmware file name
Download full text (4.0 KiB)

On Wed, Nov 4, 2009 at 6:16 AM, strowger <email address hidden> wrote:
> Adding this symlink fixes things for me:
>
> rwxrwxrwx 1 root root 34 2009-11-04 11:01
> /lib/firmware/2.6.31-14-generic/lbm-iwlwifi-5000-2.ucode ->
> /lib/firmware/iwlwifi-5000-2.ucode
>
> It may be co-incidence, but without the symlink I was experiencing very
> unstabie connections - Thinkpad R500, Karmic amd64 - whereas with it
> things are stable. Without the symlink I get logged:
>
> [   40.952984] iwlagn 0000:03:00.0: firmware: requesting lbm-iwlwifi-5000-2.ucode
> [   42.076259] iwlagn 0000:03:00.0: lbm-iwlwifi-5000-2.ucode firmware file req failed: -2
> [   42.077434] iwlagn 0000:03:00.0: firmware: requesting lbm-iwlwifi-5000-1.ucode
> [   42.290014] iwlagn 0000:03:00.0: Loaded firmware lbm-iwlwifi-5000-1.ucode, which is deprecated. Please use API v2 instead.
>
> I then have frequent disconnections of the wireless, accompanied by:
>
> iwlagn 0000:03:00.0: Microcode SW error detected.  Restarting 0x2000000
>
> As well as numerous Kernel oops'es.
>
> [Without the backports installed I, I experience frequent lockups unless
> I disable wireless]
>
> --
> Incorrect Intel firmware file name
> https://bugs.launchpad.net/bugs/453064
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “linux-backports-modules-2.6.31” package in Ubuntu: Confirmed
>
> Bug description:
> /lib/firmware/2.6.31-14-generic/lbm-iwlwifi-5000-1.ucode is API v2 and
> should be named lbm-iwlwifi-5000-2.ucode. As you see the -1 LBM
> package matches the -2 file in linux-firmware:
>
> $ sha1sum /lib/firmware/{,"2.6.31-14-generic/"}*iwlwifi-5000-*
> f06ff86c8baa8616de584f8b0fff072a9aab6a44  /lib/firmware/iwlwifi-5000-1.ucode
> b1dc5068cd536a97af7e3c0090a5a632d09ab2f3  /lib/firmware/iwlwifi-5000-2.ucode
> b1dc5068cd536a97af7e3c0090a5a632d09ab2f3  /lib/firmware/2.6.31-14-generic/lbm-iwlwifi-5000-1.ucode
>
> Also confirmed this by downloading the firmware iwlwifi-5000-2.ucode
> from Intel:
>
> b1dc5068cd536a97af7e3c0090a5a632d09ab2f3  iwlwifi-5000-2.ucode
>
>
> WiFi works, but the file name problem case the following kernel error
> messages:
>
> [  137.691196] iwlagn 0000:03:00.0: firmware: requesting lbm-iwlwifi-5000-2.ucode
> [  138.136768] iwlagn 0000:03:00.0: lbm-iwlwifi-5000-2.ucode firmware file req failed: -2
> [  138.136828] iwlagn 0000:03:00.0: firmware: requesting lbm-iwlwifi-5000-1.ucode
> [  138.290188] iwlagn 0000:03:00.0: Loaded firmware lbm-iwlwifi-5000-1.ucode, which is deprecated. Please use API v2 instead.
> [  138.290254] iwlagn 0000:03:00.0: loaded firmware version 8.24.2.12
> [  138.466569] Registered led device: iwl-phy0::radio
> [  138.466595] Registered led device: iwl-phy0::assoc
> [  138.466625] Registered led device: iwl-phy0::RX
> [  138.466643] Registered led device: iwl-phy0::TX
>
> After renaming lbm-iwlwifi-5000-1.ucode to lbm-iwlwifi-5000-2.ucode
> the above messages is replaced by:
>
> [   30.302953] iwlagn 0000:03:00.0: firmware: requesting lbm-iwlwifi-5000-2.ucode
> [   30.400389] iwlagn 0000:03:00.0: loaded firmware version 8.24.2.12
> [   30.576366] Registered led device: iwl-phy0::radio
> [   30.576389] Registered led devi...

Read more...

Revision history for this message
Pär Lindfors (paran) wrote :

"<email address hidden>" <email address hidden> writes:
> There is a bug in LBM - it is based on comapt-wireless 2.6.32-rc4..
> Ubuntu needs to change this immediately.. Kernel oops's are common in
> that release across many wireless drivers.. It has been fixed in
> rc5.. I cannot use lbm because of it..

This bug is about intel firmware file names. Please report your problem
as a new bug.

Revision history for this message
xir (simonbennie) wrote :

id like to confirm that this is an issue on the acer timeline 3810T with backports installed.

Also the fix suggested works, could we look at getting this ajusted in backports to stop the sleek boot process being interrupted?

Revision history for this message
nh2 (nh2) wrote :

Confirmed with 9.10 on a Dell Latitude 2100. Seems to be easy to fix.

Jonathan Davies (jpds)
affects: linux-backports-modules-2.6.31 (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
status: Confirmed → Triaged
importance: Undecided → Low
Revision history for this message
Marcel Engels (marcel-engels) wrote :

Same problem here with a HP 4710s laptop (Intel 5100AGN) with Ubuntu Karmic 64 bits.
Normal emailing, surfing the web works okay. I also use XBMC (media center) and when streaming movie wireless from the laptop to xbox/xbmc it randomly stops the connection. Doing a dmesg | grep error gives a Microcode SW error.
Checked with dmesg | grep iwlagn also gives the 'Please use API V2' message.
Symbolic link fixed it.
While this may be a Low importance to the majority of users, it was definitely medium/high to me.
This should be fixed in backports or wherever it should, not a symbolic link.

Peter Antoniac (pan1nx)
Changed in linux (Ubuntu):
milestone: none → lucid-updates
Revision history for this message
Andy Whitcroft (apw) wrote :

Ok the standard firmware files on my lucid install are these:

  b1dc5068cd536a97af7e3c0090a5a632d09ab2f3 /lib/firmware/iwlwifi-5000-2.ucode
  f06ff86c8baa8616de584f8b0fff072a9aab6a44 /lib/firmware/iwlwifi-5000-1.ucode

And the lucid lbm (which is based on 2.6.33) contains this:

  b1dc5068cd536a97af7e3c0090a5a632d09ab2f3 ./firmware/iwlwifi/iwlwifi-5000-ucode-8.24.2.12/iwlwifi-5000-2.ucode

Those appear to be correctly named based on the reporters checksums. This seems to have been fixed when we stopped mangling names for LBM in lucid. Closing Fix Released for Lucid.

affects: linux (Ubuntu) → linux-backports-modules-2.6.32 (Ubuntu)
Changed in linux-backports-modules-2.6.31 (Ubuntu):
status: New → Invalid
Changed in linux-backports-modules-2.6.32 (Ubuntu Karmic):
status: New → Invalid
Changed in linux-backports-modules-2.6.31 (Ubuntu Karmic):
status: New → Triaged
Changed in linux-backports-modules-2.6.32 (Ubuntu):
assignee: nobody → Andy Whitcroft (apw)
status: Triaged → Fix Committed
status: Fix Committed → Fix Released
Revision history for this message
Andy Whitcroft (apw) wrote :

This is an LBM issue, so regigged this to be open for Karmic, but closed for Lucid.

Revision history for this message
Rolf Leggewie (r0lf) wrote :

karmic has seen the end of its life and is no longer receiving any updates. Marking the karmic task for this ticket as "Won't Fix".

Changed in linux-backports-modules-2.6.31 (Ubuntu Karmic):
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.