I have a netgear wn111 v2 usb wifi N network adapter. It is supported by either ar9170usb (a,b,g) or with the newer carl9170 (a,b,g,n). Carl9170 is automatically loaded but appears to be missing carl9170.fw as the adapter will not work. More details here - http://linuxwireless.org/en/users/Drivers/carl9170.fw Firmware source code is available at http://git.kernel.org/?p=linux/kernel/git/chr/carl9170fw.git If I rmmod carl9170 and modprobe ar9170usb the adapter is recognised and works fine, albeit without the N. locate 9170 /lib/firmware/ar9170-1.fw /lib/firmware/ar9170-2.fw locate carl no results If I remove the adapter and rmmod both ar9170usb and carl9170 then reattach it, it attempts to load both drivers and it won't work. dmesg | tail usbcore: deregistering interface driver ar9170usb usb 1-5: new high speed USB device using ehci_hcd and address 14 usb 1-5: New USB device found, idVendor=0846, idProduct=9001 usb 1-5: New USB device strings: Mfr=16, Product=32, SerialNumber=48 usb 1-5: Product: USB2.0 WLAN usb 1-5: Manufacturer: ATHER usb 1-5: SerialNumber: 12345 usb 1-5: reset high speed USB device using ehci_hcd and address 14 usbcore: registered new interface driver carl9170 usb 1-5: firmware not found. usbcore: registered new interface driver ar9170usb If I add blacklist carl9170 to /etc/modprobe.d/blacklist-mga then remove the adapter and rmmod both drivers, when I reattach it does connect. dmesg | tail usbcore: deregistering interface driver ar9170usb usbcore: deregistering interface driver carl9170 usb 1-5: new high speed USB device using ehci_hcd and address 15 usb 1-5: New USB device found, idVendor=0846, idProduct=9001 usb 1-5: New USB device strings: Mfr=16, Product=32, SerialNumber=48 usb 1-5: Product: USB2.0 WLAN usb 1-5: Manufacturer: ATHER usb 1-5: SerialNumber: 12345 usb 1-5: reset high speed USB device using ehci_hcd and address 15 usbcore: registered new interface driver ar9170usb usb 1-5: ar9170.fw firmware file not found, trying old firmware... ath: EEPROM regdomain: 0x0 ath: EEPROM indicates default country code should be used ath: doing EEPROM country->regdmn map search ath: country maps to regdmn code: 0x3a ath: Country alpha2 being used: US ath: Regpair used: 0x3a ieee80211 phy10: Selected rate control algorithm 'minstrel_ht' cfg80211: Calling CRDA for country: US Registered led device: ar9170-phy10::tx Registered led device: ar9170-phy10::assoc usb 1-5: Atheros AR9170 is registered as 'phy10' cfg80211: Regulatory domain changed to country: US cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm) cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm) cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) cfg80211: (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) cfg80211: (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm) ADDRCONF(NETDEV_UP): wlan0: link is not ready ADDRCONF(NETDEV_UP): wlan0: link is not ready wlan0: authenticate with ########### (try 1) wlan0: authenticated wlan0: associate with ########### (try 1) wlan0: RX AssocResp from ############ (capab=0x431 status=0 aid=1) wlan0: associated ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready It has selected the wrong regulatory domain though as I am UK not US so it will be missing a few channels.
tmb, if you have have any other person for firmware "bug".. :)
CC: (none) => tmb
CC: (none) => thierry.vignaudAssignee: bugsquad => tmbSource RPM: (none) => kernel-firmware
pinging because this bug still has the status "NEW" and nothing happened to it since more than 4 months ago @ Thomas Please set status to ASSIGNED if you think this bug was assigned correctly. If for workflow reasons you can't do that, then please put OK on the whiteboard instead.
CC: (none) => marja11
Thanks marja, happy christmas :)
ping (sorry!)
I'm on it. Just for reference, this would add support for the following wireless devices: http://wireless.kernel.org/en/users/Drivers/carl9170#available_devices which includes AVM FRITZ!WLAN USB Stick N and the 2.4 version of that, which is really widespread here in germany.
Status: NEW => ASSIGNEDCC: (none) => doktor5000Assignee: tmb => doktor5000
Thanks Florian! This could have been a deal breaker for many people, not able to use their wifi.
Imported for cauldron and available there, should also get automatically pulled in by next kernel update for Mageia 1, thanks to Thomas Backlund :) The package is called carl9170-firmware.
upcoming cauldron kernel-3.2.5-1.mga2 (currently building) will pull in carl9170-firmware same fix is queued in svn for next mga1 kernel
Thankyou both :)
Blocks: (none) => 4490
So marking as resolved.
Status: ASSIGNED => RESOLVEDResolution: (none) => FIXED
Reopeining as it depends on 4490 being pushed...
Status: RESOLVED => REOPENEDResolution: FIXED => (none)
Reassigning to Thomas, as i can't do anything more here.
Assignee: doktor5000 => tmb
This message is a reminder that Mageia 1 is nearing its end of life. In approximately 25 days from now, Mageia will stop maintaining and issuing updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '1'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 1's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 1 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- Mageia Bugsquad
Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- Mageia Bugsquad
Status: REOPENED => RESOLVEDResolution: (none) => WONTFIX