Hi,
I have a ubiquiti sr71-usb wireless adapter, 'lsusb' shows it as:
'Atheros Communications, Inc. AR9170 802.11n', the adapter works with
the ar9170.fw firmware but I'm trying to make it work with the
carl9170.fw, until now I have tried the following:
I have put the carl9170.fw in /lib/firmware (debian default for
firmware files) without the ar9170.fw, dmesg shows that the system its
looking for a firmware with the exact name as 'ar9170.fw' or if it
doesn't find that one it tries to finds the legacy ones(ar9170-1.fw &
ar9170-2.fw), so it ignores carl9170.fw because is not named
ar9170.fw, changing the name of carl9170.fw to ar9170.fw shows the
following:
dmesg | grep 9170
[ 2.329719] usb 2-2: New USB device found, idVendor=0cf3, idProduct=9170
[ 8.817173] usb 2-2: firmware: requesting ar9170.fw
[ 9.862192] ar9170usb: probe of 2-2:1.0 failed with error -110
[ 9.862227] usbcore: registered new interface driver ar9170usb
The kernel is debian stock one:Linux laptop 2.6.32-5-686 #1 SMP Fri
Dec 10 16:12:40 UTC 2010 i686 GNU/Linux
Any ideas how can I make carl9170.fw work in debian squeeze?
Thanks,
Der
Thanks for your quick replies.
I have install compat-wireless-2010-12-23 with 'driver-select
carl9170' because the whole thing didn't want to compile for me, the
usb wifi card is working fine now with the carl9170 but now my
internal intel card isn't coming up, if tried to load the iwlagn or
iwlcore driver and get the following:
FATAL: Error inserting iwlagn
(/lib/modules/2.6.32-5-686/kernel/drivers/net/wireless/iwlwifi/iwlagn.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
dmesg outputs the following:
7.368050] iwlcore: disagrees about version of symbol
ieee80211_start_tx_ba_cb_irqsafe
[ 7.368053] iwlcore: Unknown symbol ieee80211_start_tx_ba_cb_irqsafe
[ 7.368292] iwlcore: disagrees about version of symbol ieee80211_alloc_hw
[ 7.368293] iwlcore: Unknown symbol ieee80211_alloc_hw
[ 7.368356] iwlcore: disagrees about version of symbol ieee80211_register_hw
[ 7.368358] iwlcore: Unknown symbol ieee80211_register_hw
[ 7.368537] iwlcore: disagrees about version of symbol
__ieee80211_get_radio_led_name
[ 7.368539] iwlcore: Unknown symbol __ieee80211_get_radio_led_name
[ 7.368602] iwlcore: disagrees about version of symbol ieee80211_wake_queue
[ 7.368604] iwlcore: Unknown symbol ieee80211_wake_queue
[ 7.368657] iwlcore: disagrees about version of symbol ieee80211_get_tkip_key
[ 7.368658] iwlcore: Unknown symbol ieee80211_get_tkip_key
[ 7.368713] iwlcore: disagrees about version of symbol
__ieee80211_get_tx_led_name
[ 7.368714] iwlcore: Unknown symbol __ieee80211_get_tx_led_name
[ 7.368791] iwlcore: disagrees about version of symbol ieee80211_find_sta
[ 7.368793] iwlcore: Unknown symbol ieee80211_find_sta
[ 7.368876] iwlcore: disagrees about version of symbol
ieee80211_tx_status_irqsafe
[ 7.368877] iwlcore: Unknown symbol ieee80211_tx_status_irqsafe
[ 7.368992] iwlcore: disagrees about version of symbol
__ieee80211_get_rx_led_name
[ 7.368994] iwlcore: Unknown symbol __ieee80211_get_rx_led_name
[ 7.369100] iwlcore: disagrees about version of symbol
ieee80211_stop_tx_ba_cb_irqsafe
[ 7.369102] iwlcore: Unknown symbol ieee80211_stop_tx_ba_cb_irqsafe
[ 7.369245] iwlcore: disagrees about version of symbol ieee80211_rx
[ 7.369246] iwlcore: Unknown symbol ieee80211_rx
[ 7.369308] iwlcore: disagrees about version of symbol ieee80211_wake_queues
[ 7.369310] iwlcore: Unknown symbol ieee80211_wake_queues
[ 7.369440] iwlcore: disagrees about version of symbol ieee80211_stop_queue
[ 7.369442] iwlcore: Unknown symbol ieee80211_stop_queue
[ 7.369494] iwlcore: disagrees about version of symbol ieee80211_stop_queues
[ 7.369496] iwlcore: Unknown symbol ieee80211_stop_queues
[ 7.369558] iwlcore: disagrees about version of symbol
__ieee80211_get_assoc_led_name
[ 7.369560] iwlcore: Unknown symbol __ieee80211_get_assoc_led_name
[ 7.369617] iwlcore: disagrees about version of symbol
ieee80211_scan_completed
[ 7.369619] iwlcore: Unknown symbol ieee80211_scan_completed
[ 7.369834] iwlcore: disagrees about version of symbol ieee80211_hdrlen
[ 7.369835] iwlcore: Unknown symbol ieee80211_hdrlen
[ 7.369928] iwlcore: Unknown symbol ieee80211_beacon_get
Linux laptop 2.6.32-5-686 #1 SMP Fri Dec 10 16:12:40 UTC 2010 i686 GNU/Linux
How can I make both cards work at the same time?
Thanks,
Der
- Hide quoted text -
On Thu, Dec 23, 2010 at 6:34 PM, Der Engel <[email protected]> wrote:
> Hi,
>
> I have a ubiquiti sr71-usb wireless adapter, 'lsusb' shows it as:
> 'Atheros Communications, Inc. AR9170 802.11n', the adapter works with
> the ar9170.fw firmware but I'm trying to make it work with the
> carl9170.fw, until now I have tried the following:
>
> I have put the carl9170.fw in /lib/firmware (debian default for
> firmware files) without the ar9170.fw, dmesg shows that the system its
> looking for a firmware with the exact name as 'ar9170.fw' or if it
> doesn't find that one it tries to finds the legacy ones(ar9170-1.fw &
> ar9170-2.fw), so it ignores carl9170.fw because is not named
> ar9170.fw, changing the name of carl9170.fw to ar9170.fw shows the
> following:
>
> dmesg | grep 9170
> [ 2.329719] usb 2-2: New USB device found, idVendor=0cf3, idProduct=9170
> [ 8.817173] usb 2-2: firmware: requesting ar9170.fw
> [ 9.862192] ar9170usb: probe of 2-2:1.0 failed with error -110
> [ 9.862227] usbcore: registered new interface driver ar9170usb
>
> The kernel is debian stock one:Linux laptop 2.6.32-5-686 #1 SMP Fri
> Dec 10 16:12:40 UTC 2010 i686 GNU/Linux
>
> Any ideas how can I make carl9170.fw work in debian squeeze?
>
> Thanks,
> Der
Looks like the vendor-id/product-id is not considered in your kernel,
check [1] if your device is listed as supported devices.
I am not sure if the squeeze kernel has support for carl9170.
An easy way is to use compat-wireless (stable or bleeding edge) which
offers you newer wireless hardware support and features.
The wiki in [2] has informations and instructions for you.
- Sedat -
[1] http://wireless.kernel.org/en/users/Devices
[2] http://wireless.kernel.org/en/users/Download/stable/
On Thu, Dec 23, 2010 at 2:05 PM, Walter Goldens
<[email protected]> wrote:
>
>> Any ideas how can I make carl9170.fw work in debian
>> squeeze?
>
> Download and install compat-wireless. Then blacklist ar9170 and call carl9170 instead.
>
> Walter
>
>
>
>
On Thu, Dec 23, 2010 at 6:34 PM, Der Engel <[email protected]> wrote:
> Hi,
>
> I have a ubiquiti sr71-usb wireless adapter, 'lsusb' shows it as:
> 'Atheros Communications, Inc. AR9170 802.11n', the adapter works with
> the ar9170.fw firmware but I'm trying to make it work with the
> carl9170.fw, until now I have tried the following:
>
> I have put the carl9170.fw in /lib/firmware (debian default for
> firmware files) without the ar9170.fw, dmesg shows that the system its
> looking for a firmware with the exact name as 'ar9170.fw' or if it
> doesn't find that one it tries to finds the legacy ones(ar9170-1.fw &
> ar9170-2.fw), so it ignores carl9170.fw because is not named
> ar9170.fw, changing the name of carl9170.fw to ar9170.fw shows the
> following:
>
> dmesg | grep 9170
> [ 2.329719] usb 2-2: New USB device found, idVendor=0cf3, idProduct=9170
> [ 8.817173] usb 2-2: firmware: requesting ar9170.fw
> [ 9.862192] ar9170usb: probe of 2-2:1.0 failed with error -110
> [ 9.862227] usbcore: registered new interface driver ar9170usb
>
> The kernel is debian stock one:Linux laptop 2.6.32-5-686 #1 SMP Fri
> Dec 10 16:12:40 UTC 2010 i686 GNU/Linux
>
> Any ideas how can I make carl9170.fw work in debian squeeze?
>
> Thanks,
> Der
Looks like the vendor-id/product-id is not considered in your kernel,
check [1] if your device is listed as supported devices.
I am not sure if the squeeze kernel has support for carl9170.
An easy way is to use compat-wireless (stable or bleeding edge) which
offers you newer wireless hardware support and features.
The wiki in [2] has informations and instructions for you.
- Sedat -
[1] http://wireless.kernel.org/en/users/Devices
[2] http://wireless.kernel.org/en/users/Download/stable/
This is because of driver-select. To make a long story short, download and install the entire compat-wireless suit (without driver select). If the current version fails to compile download the one from the day before and so on until you find a version which compiles entirely. Then you'll have support for all of your wireless cards.
Walter
> Any ideas how can I make carl9170.fw work in debian
> squeeze?
Download and install compat-wireless. Then blacklist ar9170 and call carl9170 instead.
Walter
Thank you, I'll try and search for a version that compiles.
The reason I went with bleeding-edge and not the stable version is
because the stable versions are hosted at orbit-lab.org and all the
download links are broken so I couldn't find another place from where
to download it.
Der
On Fri, Dec 24, 2010 at 7:00 AM, Sedat Dilek <[email protected]> wrote:
> On Fri, Dec 24, 2010 at 12:29 PM, Walter Goldens
> <[email protected]> wrote:
>> This is because of driver-select. To make a long story short, download and install the entire compat-wireless suit (without driver select). If the current version fails to compile download the one from the day before and so on until you find a version which compiles entirely. Then you'll have support for all of your wireless cards.
>>
>>
>> Walter
>>
>
> I always wonder why people start with bleeding-edge version of compat-wireless.
> A daily bleeding-edge version might be broken, try a previous version
> (as Walter recommended).
> Check also the automated reports of Luis which are sent to this ML.
> There are "half-baked" version around...
>
> "Der" did you try a stable .36 or stable .37-rcX of c-w?
>
> So you asked for carl9170 and not in combination with iwlwifi!
> For a new topic open a new thread, please.
> As Walter pointed out, do a full compilation of c-w.
>
>
> - Sedat -
>
On Fri, Dec 24, 2010 at 12:29 PM, Walter Goldens
<[email protected]> wrote:
> This is because of driver-select. To make a long story short, download and install the entire compat-wireless suit (without driver select). If the current version fails to compile download the one from the day before and so on until you find a version which compiles entirely. Then you'll have support for all of your wireless cards.
>
>
> Walter
>
I always wonder why people start with bleeding-edge version of compat-wireless.
A daily bleeding-edge version might be broken, try a previous version
(as Walter recommended).
Check also the automated reports of Luis which are sent to this ML.
There are "half-baked" version around...
"Der" did you try a stable .36 or stable .37-rcX of c-w?
So you asked for carl9170 and not in combination with iwlwifi!
For a new topic open a new thread, please.
As Walter pointed out, do a full compilation of c-w.
- Sedat -
Was there ever a solution for this?
I continue to get the "Unknown symbol in module" error. I've got squeeze with
2.6.32-5 kernel
and I've tried a variety of compat-wireless versions including the latest 3.0
stable.
I've tried by building with out a specified driver-select (which took awhile)
and I've tried with specifying carl9170.
On 07/01/2011 03:25 PM, ant2ne wrote:
> Was there ever a solution for this?
>
> I continue to get the "Unknown symbol in module" error.
Please be specific and quote the error messages as is. Also please give
the exact command so that others have a chance to tell you if you are
doing something wrong. If you are using insmod, please try modprobe, as
only modprobe can load other modules that provide the required symbols.
Please see the kernel log using the dmesg command. It should have more
detailed information about the unresolved symbols.
If you just installed compat-wireless, please reboot, as it would unload
the old wireless modules and load the new ones. If you cannot reboot,
you'll need to run "make unload" in the compat-wireless directory.
> I've got squeeze with
> 2.6.32-5 kernel
> and I've tried a variety of compat-wireless versions including the latest 3.0
> stable.
Do they all have the same problem?
--
Regards,
Pavel Roskin