en:users:drivers:carl9170
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision Last revision Both sides next revision | ||
|
en:users:drivers:carl9170 [2015/01/26 09:49] 127.0.0.1 external edit |
en:users:drivers:carl9170 [2015/01/30 12:59] Christian Lamparter [Recovery FAQ] Fix formatting |
||
|---|---|---|---|
| Line 40: | Line 40: | ||
| A [[http://git.kernel.org/?p=linux/kernel/git/chr/carl9170fw.git;a=commitdiff;h=39be7dc384e0dd45dc36b4b517fd9fae874b06f0|known problem]] is that hardware can not support [[http://en.wikipedia.org/wiki/IEEE_802.11n-2009#Frame_aggregation|frame aggregation]] and [[http://en.wikipedia.org/wiki/Wireless_Multimedia_Extensions|QoS]] at the same time, meaning the device is not suitable for any serious 802.11n setup. Also the hardware crypto has some serious trouble with encrypting/deciphering at high throughput, therefore if possible use 'nohwcrypt=1' as a workaround. | A [[http://git.kernel.org/?p=linux/kernel/git/chr/carl9170fw.git;a=commitdiff;h=39be7dc384e0dd45dc36b4b517fd9fae874b06f0|known problem]] is that hardware can not support [[http://en.wikipedia.org/wiki/IEEE_802.11n-2009#Frame_aggregation|frame aggregation]] and [[http://en.wikipedia.org/wiki/Wireless_Multimedia_Extensions|QoS]] at the same time, meaning the device is not suitable for any serious 802.11n setup. Also the hardware crypto has some serious trouble with encrypting/deciphering at high throughput, therefore if possible use 'nohwcrypt=1' as a workaround. | ||
| - | |Hardware|--colspan=2--Problem|--colspan=2--Solution?| | + | |Hardware|Problem|Solution?| |
| - | |**BCM4313**|--colspan=2--//Hardware incompatibility//|--colspan=2--//replace hardware//| | + | |**BCM4313**|//Hardware incompatibility//|//replace hardware//| |
| - | |**Any Intel N Wifi Link**|--colspan=2--//Aggregation stalls//|--colspan=2--//driver workaround//| | + | |**Any Intel N Wifi Link**|//Aggregation stalls//|//driver workaround//| |
| - | |**RT28xx/RT3xxx**|--colspan=2--//Random disconnects//|--colspan=2--//?//| | + | |**RT28xx/RT3xxx**|//Random disconnects//|//?//| |
| See [[en/users/Drivers/carl9170|Contact]], if you want to report issues with specific setups. | See [[en/users/Drivers/carl9170|Contact]], if you want to report issues with specific setups. | ||
| Line 101: | Line 101: | ||
| Alternately you can download the GPLv2 Firmware binary from here (rename to carl9170-1.fw): | Alternately you can download the GPLv2 Firmware binary from here (rename to carl9170-1.fw): | ||
| - | |--colspan=2--**for Kernel**|--colspan=2--**Firmware Version**|--colspan=2--**Download Link**| | + | |**for Kernel**|**Firmware Version**|**Download Link**| |
| - | |--colspan=2--//Linux 2.6.x and 3.0//|--colspan=2--//1.9.2//|--colspan=2--//[[carl9170-1.fw-1.9.2|carl9170-1.fw-1.9.2]]//| | + | |//Linux 2.6.x and 3.0//|//1.9.2//|//[[carl9170-1.fw-1.9.2|carl9170-1.fw-1.9.2]]//| |
| - | |--colspan=2--//Linux 3.1 and newer//|--colspan=2--//1.9.9//|--colspan=2--//[[carl9170-1.fw-1.9.9|carl9170-1.fw-1.9.9]]//| | + | |//Linux 3.1 and newer//|-//1.9.9//|//[[carl9170-1.fw-1.9.9|carl9170-1.fw-1.9.9]]//| |
| Line 111: | Line 111: | ||
| ==== General FAQ ==== | ==== General FAQ ==== | ||
| - | **Can I use newer carl9170 firmwares with any old carl9170 driver, or vice versa?** | + | * ** Can I use newer carl9170 firmwares with any old carl9170 driver, or vice versa? ** |
| - | * Depends on the combination. But the driver will evaluate, if it can safely support the firmware, or reject it. **Can I use the new carl9170 firmware with driver like otus or ar9170usb?** | + | * Depends on the combination. But the driver will evaluate, if it can safely support the firmware, or reject it. |
| - | * No. **Does the driver support the original firmwares?** | + | |
| - | * No. **I don't need HT, how do I disable it?** | + | * **Can I use the new carl9170 firmware with driver like otus or ar9170usb?** |
| - | * Through a module parameter. 'noht=1' **How can I disable the hardware crypto?** | + | * No. |
| - | * Through a module parameter. 'nohwcrypt=1' | + | |
| + | * **Does the driver support the original firmwares?** | ||
| + | * No. | ||
| + | |||
| + | * **I don't need HT, how do I disable it?** | ||
| + | * Through a module parameter. 'noht=1' | ||
| + | |||
| + | * **How can I disable the hardware crypto?** | ||
| + | * Through a module parameter. 'nohwcrypt=1' | ||
| ==== Recovery FAQ ==== | ==== Recovery FAQ ==== | ||
| Line 125: | Line 133: | ||
| * You can easily test this by physically unplugging and replugging the device. If your connection is coming back, then you are done! If not, you have to find out how your distribution is doing network link hotplugging. **All of a sudden, the device stops working for a few seconds (but recovers)** | * You can easily test this by physically unplugging and replugging the device. If your connection is coming back, then you are done! If not, you have to find out how your distribution is doing network link hotplugging. **All of a sudden, the device stops working for a few seconds (but recovers)** | ||
| * You should check if the driver has issued a device restart. There should be a "restart device (//#number//)" message in your system's logs. | * You should check if the driver has issued a device restart. There should be a "restart device (//#number//)" message in your system's logs. | ||
| - | | //#// | | meaning | | + | |
| - | |1| |//a fatal firmware error has occurred; the previous "FW" message contains more details//| | + | | ** #number ** | **meaning** | |
| - | |2| |//excessive flood of (non-fatal) firmware errors; check previous messages.//| | + | |1| //a fatal firmware error has occurred; the previous "FW" message contains more details//| |
| - | |3| |//Hardware watchdog triggered, because the firmware has crash silently.//| | + | |2| //excessive flood of (non-fatal) firmware errors; check previous messages.//| |
| - | |4| |//stuck tx queues. this is almost always a driver bug, so please file a report.//| | + | |3| //Hardware watchdog triggered, because the firmware has crash silently.//| |
| - | |5| |//your system wasn't able to process requests fast enough; as a result the device has become unresponsive.//| | + | |4| //stuck tx queues. this is almost always a driver bug, so please file a report.//| |
| - | |6| |//command timeout. Either fw/driver bugs or a bad cable/hw malfunction.//| | + | |5| //your system wasn't able to process requests fast enough; as a result the device has become unresponsive.// | |
| - | |7| |//RF/PHY has become too unstable. Check for radars or microwave ovens?//| | + | |6| //command timeout. Either fw/driver bugs or a bad cable/hw malfunction.//| |
| - | |8| |//lost command response. related to 6/command timeout//| | + | |7| //RF/PHY has become too unstable. Check for radars or microwave ovens?//| |
| - | |9| |//unexpected/invalid command response. also related to 6/command timeout//| | + | |8| //lost command response. related to 6/command timeout//| |
| - | |10| |//firmware restart was requested by user (through DebugFS)//| | + | |9| //unexpected/invalid command response. also related to 6/command timeout//| |
| + | |10| //firmware restart was requested by user (through DebugFS)//| | ||
en/users/drivers/carl9170.txt · Last modified: 2015/01/30 13:01 by Christian Lamparter
Page Tools
