corrupted firmware-linux-nonfree 0.26
in [Debian]
|
Prev: Key logger
Next: lenny iso signed with key 64E6EA7D
From: Paul Scott on 7 Jul 2010 17:30 On 07/07/2010 02:05 PM, Paul Scott wrote: > On 07/07/2010 01:46 PM, Sven Joachim wrote: >> On 2010-07-07 22:17 +0200, Florian Kulzer wrote: >>> >>> http://git.kernel.org/?p=linux/kernel/git/dwmw2/linux-firmware.git;a=tree >>> >>> Make sure to use the "raw" link to the right of the names of the files >>> that you need. According to the "history" links, these two files were >>> added to the kernel in 2008 and have not been changed since. That at least got me a copy of the file. Thanks. >> >> They are also identical to the files in the Debian >> firmware-linux-nonfree package. > > Are you sure this is true for agere_sta_fw.bin? My wireless is currently > broken with version 0.26 of firmware-linux-nonfree. It worked with the > previous version. Is there another step after upgrading > firmware-linux-nonfree to get the agere driver installed. > > There are some threads out there about corrupted agere*.bin files > because of a file transfer problem.. Installing the above version of agere_sta_fw.bin elimated the eth2: Lucent/Agere firmware doesn't support manual roaming message but the card still doesn't associate. Hopefully the relevant part of the log follows: Thanks, Paul Jul 7 14:27:35 gotojoy kernel: [49983.980204] pcmcia_socket pcmcia_socket1: pccard: PCMCIA card inserted into slot 1 Jul 7 14:27:35 gotojoy kernel: [49983.980989] pcmcia 1.0: pcmcia: registering new device pcmcia1.0 Jul 7 14:27:35 gotojoy kernel: [49984.092535] orinoco_cs 1.0: Hardware identity 0001:0001:0004:0000 Jul 7 14:27:35 gotojoy kernel: [49984.092646] orinoco_cs 1.0: Station identity 001f:0001:0006:0010 Jul 7 14:27:35 gotojoy kernel: [49984.092667] orinoco_cs 1.0: Firmware determined as Lucent/Agere 6.16 Jul 7 14:27:35 gotojoy kernel: [49984.113189] orinoco_cs 1.0: firmware: requesting agere_sta_fw.bin Jul 7 14:27:35 gotojoy kernel: [49984.528188] orinoco_cs 1.0: Hardware identity 0001:0001:0004:0000 Jul 7 14:27:35 gotojoy kernel: [49984.528317] orinoco_cs 1.0: Station identity 001f:0002:0009:0030 Jul 7 14:27:35 gotojoy kernel: [49984.528339] orinoco_cs 1.0: Firmware determined as Lucent/Agere 9.48 Jul 7 14:27:35 gotojoy kernel: [49984.528355] orinoco_cs 1.0: Ad-hoc demo mode supported Jul 7 14:27:35 gotojoy kernel: [49984.528366] orinoco_cs 1.0: IEEE standard IBSS ad-hoc mode supported Jul 7 14:27:35 gotojoy kernel: [49984.528381] orinoco_cs 1.0: WEP supported, 104-bit key Jul 7 14:27:35 gotojoy kernel: [49984.528394] orinoco_cs 1.0: WPA-PSK supported Jul 7 14:27:35 gotojoy NetworkManager: <info> Found wlan radio killswitch rfkill6 (at /sys/devices/pci0000:00/0000:00:11.0/1.0/ieee80211/phy4/rfkill6) (driver <unknown>) Jul 7 14:27:35 gotojoy kernel: [49984.781996] udev: renamed network interface eth1 to eth2 Jul 7 14:27:35 gotojoy NetworkManager: SCPlugin-Ifupdown: devices added (path: /sys/devices/pci0000:00/0000:00:11.0/1.0/net/eth2, iface: eth2) Jul 7 14:27:35 gotojoy NetworkManager: SCPlugin-Ifupdown: device added (path: /sys/devices/pci0000:00/0000:00:11.0/1.0/net/eth2, iface: eth2): no ifupdown configuration found. Jul 7 14:27:35 gotojoy NetworkManager: <info> (eth2): driver supports SSID scans (scan_capa 0x01). Jul 7 14:27:35 gotojoy NetworkManager: <info> (eth2): new 802.11 WiFi device (driver: 'orinoco_cs') Jul 7 14:27:36 gotojoy NetworkManager: <info> (eth2): exported as /org/freedesktop/NetworkManager/Devices/5 Jul 7 14:27:36 gotojoy NetworkManager: <info> (eth2): now managed Jul 7 14:27:36 gotojoy NetworkManager: <info> (eth2): device state change: 1 -> 2 (reason 2) Jul 7 14:27:36 gotojoy NetworkManager: <info> (eth2): bringing up device. Jul 7 14:27:36 gotojoy kernel: [49984.908781] ADDRCONF(NETDEV_UP): eth2: link is not ready Jul 7 14:27:36 gotojoy NetworkManager: <info> (eth2): preparing device. Jul 7 14:27:36 gotojoy NetworkManager: <info> (eth2): deactivating device (reason: 2). Jul 7 14:27:36 gotojoy NetworkManager: <info> (eth2): supplicant interface state: starting -> ready Jul 7 14:27:36 gotojoy NetworkManager: <info> (eth2): device state change: 2 -> 3 (reason 42) Jul 7 14:27:36 gotojoy wpa_supplicant[1147]: Failed to initiate AP scan. -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/4C34F1D8.6070602(a)ultrasw.com
From: Paul Scott on 7 Jul 2010 17:40 On 07/07/2010 02:25 PM, Sven Joachim wrote: > On 2010-07-07 23:05 +0200, Paul Scott wrote: > >> On 07/07/2010 01:46 PM, Sven Joachim wrote: >>> On 2010-07-07 22:17 +0200, Florian Kulzer wrote: >>>> >>>> http://git.kernel.org/?p=linux/kernel/git/dwmw2/linux-firmware.git;a=tree >>>> >>>> Make sure to use the "raw" link to the right of the names of the files >>>> that you need. According to the "history" links, these two files were >>>> added to the kernel in 2008 and have not been changed since. >>> >>> They are also identical to the files in the Debian >>> firmware-linux-nonfree package. >> >> Are you sure this is true for agere_sta_fw.bin? > > Yes. I downloaded the firmware-linux-nonfree package, cloned the > linux-firmware git tree and compared the files. Here are the sha1sums: > > 0c58a68058e2ef23e3e7f3546c40afb536d924d4 agere_ap_fw.bin > 0fff9e1b61ab735e698d6390ffd60d0247ae1a0b agere_sta_fw.bin Admitting I don't know the whole process well enough: Is it possible that the installing of firmware-linux-nonfree somehow doesn't properly download the agere*.bin as described in this thread? https://bugs.launchpad.net/ubuntu/+source/linux/+bug/315489 As I mention in my email at 2:30 putting agere_sta_fw.bin in /lib/firmware does change the behavior of my wireless card. Thanks, Paul -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/4C34F436.6040300(a)ultrasw.com
From: Sven Joachim on 7 Jul 2010 18:00 On 2010-07-07 23:40 +0200, Paul Scott wrote: > Admitting I don't know the whole process well enough: Is it possible > that the installing of firmware-linux-nonfree somehow doesn't properly > download the agere*.bin as described in this thread? > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/315489 If you use apt to install the package, it will detect if the package is corrupt and refuse to install it. If you download the package with a browser and use dpkg to install it, then such corruption may go unnoticed, however. > As I mention in my email at 2:30 putting agere_sta_fw.bin in > /lib/firmware does change the behavior of my wireless card. You can run "debsums firmware-linux-nonfree" and reinstall the package if necessary. Sven -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/87630rx8d3.fsf(a)turtle.gmx.de
From: Florian Kulzer on 7 Jul 2010 18:10
On Wed, Jul 07, 2010 at 14:30:00 -0700, Paul Scott wrote: > On 07/07/2010 02:05 PM, Paul Scott wrote: > >On 07/07/2010 01:46 PM, Sven Joachim wrote: > >>On 2010-07-07 22:17 +0200, Florian Kulzer wrote: > > >>>http://git.kernel.org/?p=linux/kernel/git/dwmw2/linux-firmware.git;a=tree [...] > That at least got me a copy of the file. Thanks. > >> > >>They are also identical to the files in the Debian > >>firmware-linux-nonfree package. [...] > Installing the above version of agere_sta_fw.bin elimated the > eth2: Lucent/Agere firmware doesn't support manual roaming > message but the card still doesn't associate. > > Hopefully the relevant part of the log follows: [ snip: As far as I can tell, everything looks normal until NetworkManager joins the party. ] > Jul 7 14:27:35 gotojoy NetworkManager: SCPlugin-Ifupdown: devices added (path: /sys/devices/pci0000:00/0000:00:11.0/1.0/net/eth2, iface: eth2) > Jul 7 14:27:35 gotojoy NetworkManager: SCPlugin-Ifupdown: device added (path: /sys/devices/pci0000:00/0000:00:11.0/1.0/net/eth2, iface: eth2): no ifupdown configuration found. > Jul 7 14:27:35 gotojoy NetworkManager: <info> (eth2): driver supports SSID scans (scan_capa 0x01). > Jul 7 14:27:35 gotojoy NetworkManager: <info> (eth2): new 802.11 WiFi device (driver: 'orinoco_cs') > Jul 7 14:27:36 gotojoy NetworkManager: <info> (eth2): exported as /org/freedesktop/NetworkManager/Devices/5 > Jul 7 14:27:36 gotojoy NetworkManager: <info> (eth2): now managed > Jul 7 14:27:36 gotojoy NetworkManager: <info> (eth2): device state change: 1 -> 2 (reason 2) > Jul 7 14:27:36 gotojoy NetworkManager: <info> (eth2): bringing up device. > Jul 7 14:27:36 gotojoy kernel: [49984.908781] ADDRCONF(NETDEV_UP): eth2: link is not ready > Jul 7 14:27:36 gotojoy NetworkManager: <info> (eth2): preparing device. > Jul 7 14:27:36 gotojoy NetworkManager: <info> (eth2): deactivating device (reason: 2). > Jul 7 14:27:36 gotojoy NetworkManager: <info> (eth2): supplicant interface state: starting -> ready > Jul 7 14:27:36 gotojoy NetworkManager: <info> (eth2): device state change: 2 -> 3 (reason 42) > Jul 7 14:27:36 gotojoy wpa_supplicant[1147]: Failed to initiate AP scan. I would kill NetworkManager and test whether your card can associate with the AP if you set it up directly in /etc/network/interfaces. (Check the output of"iwconfig eth2"). Also, try if "iwlist scan eth2" (as root) does list your AP correctly. -- Regards, | Florian | -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/20100707214649.GA6062(a)isar.localhost |