Bug 4005 - Intel Wireless 5100 AGN [Shiloh] wifi connect error
: Intel Wireless 5100 AGN [Shiloh] wifi connect error
Status: RESOLVED WONTFIX
Product: Desktop Bugs
Classification: ROSA Desktop
Component: Main Packages
: Fresh
: All Linux
: Normal normal
: ---
Assigned To: ROSA Linux Bugs
: ROSA Linux Bugs
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-04-28 03:12 MSD by Vladimir Potapov
Modified: 2014-10-09 12:15 MSD (History)
3 users (show)

See Also:
RPM Package: kernel
ISO-related:
Bad POT generating:
Upstream:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vladimir Potapov 2014-04-28 03:12:28 MSD
http://forum.rosalab.ru/viewtopic.php?f=39&t=3363

[root@ThinkPad-X200]# lspci | grep Wireless
03:00.0 Network controller: Intel Corporation PRO/Wireless 5100 AGN [Shiloh] Network Connection
[root@ThinkPad-X200]# uname -a
Linux ThinkPad-X200 3.10.34-nrj-desktop-2rosa #1 SMP PREEMPT Tue Apr 1 14:19:33 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

dmesg

[ 9680.045515] iwlwifi 0000:03:00.0: Failing on timeout while stopping DMA channel 2 [0x5a5a5a5a]
[ 9680.045515] iwlwifi 0000:03:00.0: Failing on timeout while stopping DMA channel 5 [0x5a5a5a5a]
[ 9680.045515] iwlwifi 0000:03:00.0: Failing on timeout while stopping DMA channel 7 [0x5a5a5a5a]
[ 9686.611007] [sched_delayed] sched: RT throttling activated
[ 9688.507035] iwlwifi 0000:03:00.0: L1 Disabled; Enabling L0S
[ 9688.636573] cfg80211: World regulatory domain updated:
[ 9688.636577] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 9688.636580] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 9688.636581] cfg80211:   (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 9688.636583] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 9688.636585] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 9688.636586] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 9688.658579] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
[ 9694.378112] iwlwifi 0000:03:00.0: Failed to load firmware chunk!
[ 9694.378124] iwlwifi 0000:03:00.0: Could not load the [0] uCode section
[ 9694.378136] iwlwifi 0000:03:00.0: Failed to start RT ucode: -110
[ 9695.053138] iwlwifi 0000:03:00.0: Failing on timeout while stopping DMA channel 0 [0x5a5a5a5a]
[ 9695.053138] iwlwifi 0000:03:00.0: Failing on timeout while stopping DMA channel 2 [0x5a5a5a5a]
[ 9695.053138] iwlwifi 0000:03:00.0: Failing on timeout while stopping DMA channel 5 [0x5a5a5a5a]
[ 9695.053138] iwlwifi 0000:03:00.0: Failing on timeout while stopping DMA channel 7 [0x5a5a5a5a]
[ 9704.020274] iwlwifi 0000:03:00.0: Unable to initialize device.
[ 9775.748254] iwlwifi 0000:03:00.0: L1 Disabled; Enabling L0S
[ 9775.895622] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
[ 9781.606080] iwlwifi 0000:03:00.0: Failed to load firmware chunk!
[ 9781.606087] iwlwifi 0000:03:00.0: Could not load the [0] uCode section
[ 9781.606094] iwlwifi 0000:03:00.0: Failed to start RT ucode: -110
Comment 1 Postnikov Dmitry 2014-04-28 12:09:02 MSD
Download firmware from http://wireless.kernel.org/en/users/Drivers/iwlwifi?action=AttachFile&do=get&target=iwlwifi-5000-ucode-5.4.A.11.tar.gz

Unpack nay folder. Go to folder /iwlwifi-5000-ucode-5.4.A.11 and put command:
cp iwlwifi-*.ucode /lib/firmware
reboot
Comment 2 Eugene Shatokhin 2014-04-28 13:08:49 MSD
(In reply to comment #1)
> Download firmware from
> http://wireless.kernel.org/en/users/Drivers/
> iwlwifi?action=AttachFile&do=get&target=iwlwifi-5000-ucode-5.4.A.11.tar.gz

Вот это, похоже, новее: 
http://wireless.kernel.org/en/users/Drivers/iwlwifi?action=AttachFile&do=get&target=iwlwifi-5000-ucode-8.83.5.1-1.tgz

И iwlwifi-5000-5.ucode там отличается от того, что у нас, что интересно.
Comment 3 Eugene Shatokhin 2014-04-30 13:30:06 MSD
Reported the problem upstream:
https://bugzilla.kernel.org/show_bug.cgi?id=75141
Comment 4 FirstLevel 2014-10-08 21:31:42 MSD
Please could You check the problem for new release 2014.1
Comment 5 Eugene Shatokhin 2014-10-09 12:15:04 MSD
(In reply to comment #4)
> Please could You check the problem for new release 2014.1

The upstream maintainers claimed it is a firmware problem and refused to fix the issue, unfortunately.