Summary: | net-wireless/wimax-1.5: comman "wimaxcu ron" reported ERROR: Turning the SW Radio ON unsuccessfull - Device is UnInitialized. | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Dmitry <exdiff> |
Component: | [OLD] Unspecified | Assignee: | Alexey Shvetsov <alexxy> |
Status: | VERIFIED TEST-REQUEST | ||
Severity: | normal | CC: | hypnos75, marsoft, mobile+disabled, roman.olesyuk, sungeneral, xmw |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Dmitry
2010-08-05 09:10:37 UTC
Hello Dmitry, have you tried `rfkill unblock 0` and `rfkill unblock 1`. You need write access on /dev/rfkill , so either be root or adjust the permissions. I have no idea if this is preserved during reboot or set in the regular bootup process. Michael I do this from root user and have write priveleges to /dev/rfkill. This is regular process. Reboot does not change any thing. If I install old wimax-1.4.3 wimaxcu unblock wimax, but not find any networks(trying to use "wimaxcu reset fabric" don't have any effect, wimax network guaranteed founded by HTC max 4G). Sorry, I wasn;t precise enough. Please take al look ar `rfkill list` (the device should be shown in status soft-blocked. Now run `rfkill unblock 0 ; rfkill unblock 1`and take another look at `rfkill list`. The devices should be unblocked now. Hard locks is a hardware switch in the chassis, soft lock is a new (?!) software interface to disable devices. Maybe wima doesn't handle this correctly, but the rfkil unblock sequence above can fix this. Michael Hello! Same issue here. After `rfkill unblock 1` device doesn't get unblocked. From dmesg: i2400m_usb 1-1.5:1.0: 'RF Control' (0x4602) command failed: -84 - invalid state (3) Roman, I have this messages in dmesg output too. I have this bug too. Also, after switching WiFi off, trying to switch WiMAX on, and switching WiFi back on, I cannot use it: $ sudo iwlist wlan0 scan wlan0 Interface doesn't support scanning: Network is down $ sudo ifconfig wlan0 up SIOCSIFFLAGS: Unknown error 132 $ uname -a Linux nee 2.6.35-gentoo-r4 #1 SMP PREEMPT Wed Aug 25 06:53:13 MSD 2010 i686 Intel(R) Atom(TM) CPU N270 @ 1.60GHz GenuineIntel GNU/Linux * fix: just checked, here are real messages: $ sudo iwlist wlan0 scan wlan0 Interface doesn't support scanning: Network is down $ sudo ifconfig wlan0 up SIOCSIFFLAGS: Invalid argument $ sudo /etc/init.d/wimax restart ... $ sudo iwlist wlan0 scan wlan0 Interface doesn't support scanning : Device or resource busy And even rmmod-ing wifi and wimax drivers and modprobe-ing them again doesn't help. hm. Try this one. 1) Check the firmware version. Must be 1.5 2) Check for proper NDnSAgentAgentConfig_forDriver.xml and NDnSAgentDefaultConfig.xml in /usr/share/wimax if it doesn't work try 3) rename /lib/firmware/i2400m-fw-usb-1.5.sbcf to /lib/firmware/i2400m-fw-usb-1.4.sbcf (In reply to comment #8) I tried all steps - nothing i2400m_usb 1-6:1.0: 'RF Control' (0x4602) command failed: -84 - invalid state (3) (In reply to comment #8) > hm. Try this one. > 1) Check the firmware version. Must be 1.5 $ ls /lib/firmware/i24* /lib/firmware/i2400m-fw-usb-1.5.sbcf $ eix -Ic i2400 [I] net-wireless/i2400m-fw (1.5.0@01.09.2010): Intel i2400m firmware > 2) Check for proper NDnSAgentAgentConfig_forDriver.xml and > NDnSAgentDefaultConfig.xml in /usr/share/wimax > 2) Check for proper NDnSAgentAgentConfig_forDriver.xml and > NDnSAgentDefaultConfig.xml in /usr/share/wimax What package must provide these files? It seems that I have some of them remained from wimax-1.4, and they aren't owned by any ebuild now. $ ls /usr/share/wimax/NDnS* -1 /usr/share/wimax/NDnSAgentConfig_forDriver.xml /usr/share/wimax/NDnSAgentConfig_forDriver.xml.1 /usr/share/wimax/NDnSAgentConfig_forDriver.xml.bak /usr/share/wimax/NDnSAgentDefaultConfig.xml.1 /usr/share/wimax/NDnSAgentDefaultConfig.xml.bak $ equery b /usr/share/wimax/NDnSAgentConfig_forDriver.xml * Searching for /usr/share/wimax/NDnSAgentConfig_forDriver.xml ... $ eix -I wimax [I] net-wireless/wimax (1.5[1]@01.09.2010): Intel WiMAX daemon used to interface to the hardware [I] net-wireless/wimax-tools (1.4.3@01.09.2010): Tools to use Intel's WiMax cards [1] "local" /usr/local/portage ## local ebuild for wimax includes patch from bug 335476 > if it doesn't work try > 3) rename /lib/firmware/i2400m-fw-usb-1.5.sbcf to > /lib/firmware/i2400m-fw-usb-1.4.sbcf > I'll try it now, although I doubt it can help. Also I'll try to remove/move /usr/share/wimax/NDnS* as they aren't owned by any ebuild. Nothing changed, even after reboot. $ sudo rfkill unblock 2 ->in dmesg: <7>[292386.458242] i2400m_usb 1-8:1.0: __pm_runtime_resume()! <7>[292386.458257] usb 1-8: __pm_runtime_resume()! <7>[292386.458265] usb 1-8: __pm_runtime_resume() returns -22! <7>[292386.458276] i2400m_usb 1-8:1.0: __pm_runtime_resume() returns 0! <7>[292386.459205] i2400m_usb 1-8:1.0: __pm_runtime_resume()! <7>[292386.459218] i2400m_usb 1-8:1.0: __pm_runtime_resume() returns 1! <7>[292386.459452] i2400m_usb 1-8:1.0: __pm_runtime_suspend()! <7>[292386.459465] i2400m_usb 1-8:1.0: __pm_runtime_suspend() returns 0! <3>[292386.459508] i2400m_usb 1-8:1.0: 'RF Control' (0x4602) command failed: -84 - invalid state (3) $ ls ls /usr/share/wimax/NDnS* ls: cannot access /usr/share/wimax/NDnS*: No such file or directory ## (but with these old files nothing changed too) $ ls /lib/firmware/i2400* /lib/firmware/i2400m-fw-usb-1.4.sbcf ## it is renamed 1.5; nothing changes when I rename it. * i think that we have kernel driver problem 2.6.35-gentoo-r8 - 2.6.35-gentoo-r9 - 100% in my configuration does not work i tried to downgrade service version\firmware version - nothing Dmitry: Your issue has nothing to do with rfkill -- this is the daemon not finalizing initializing the card. can you dump thje contents of your /etc/modprobe.d/i2400m.conf? Thanks (In reply to comment #13) > Dmitry: > > Your issue has nothing to do with rfkill -- this is the daemon not finalizing > initializing the card. But on previous kernel/firmware we were able to "rfkill unblock" wmx0 even without starting wimax daemon, which did just what "wimaxcu ron" did through daemon (IMHO), and now we cannot do any of that. > > can you dump thje contents of your /etc/modprobe.d/i2400m.conf? $ cat /etc/modprobe.d/i2400m.conf # Disable IDLE mode. There is a bug somewhere that is still being # chased by which the device crashes one exiting or trying to exit from # IDLE mode. options i2400m passive_mode=1 > > Thanks > i2400m.conf looks ok So this is a 5150 -- can you double check that you are running the 1.5 daemon with the 1.5 firmware? Frankly, I am confused with all the renaming going on below :( A way to check that is $ grep i2400 /var/log/messages | grep "firmware" | head Sep 26 04:32:28 localhost kernel: i2400m_usb 2-3:1.0: firmware: requesting i2400m-fw-usb-1.5.sbcf Sep 26 14:48:43 localhost kernel: i2400m_usb 2-3:1.0: firmware i2400m-fw-usb-1.5.sbcf: cached Sep 26 14:48:43 localhost kernel: i2400m_usb 2-3:1.0: firmware i2400m-fw-usb-1.5.sbcf: loading from cache Sep 26 14:48:45 localhost kernel: i2400m_usb 2-3:1.0: firmware interface version 9.3.2 Sep 26 15:29:36 localhost kernel: i2400m_usb 2-3:1.0: firmware: requesting i2400m-fw-usb-1.4.sbcf It has to say '9.3.2' >What package must provide these files? NDnSAgent* - config's for connection, if i'm not mistaken. I found solution about renaming, here http://icelord.net/wordpress/archives/2259 >i tried to downgrade service version\firmware version - nothing it helps for me, it starts to work after i replaced NDnSAgent* files. > A way to check that is $ grep i2400 /var/log/messages | grep "firmware" | head Oct 2 23:38:54 godumobile kernel: i2400m_usb 1-8:1.0: firmware interface version 9.3.2 Oct 2 23:59:59 godumobile kernel: i2400m_usb 1-8:1.0: firmware interface version 9.3.2 also after starting wimaxd console starts to lag. > I found solution about renaming, here
> http://icelord.net/wordpress/archives/2259
sorry my mistake it's a bug about wimax-compat
seems the same bug, for me http://www.linuxwimax.org/bugzilla/show_bug.cgi?id=13 Please test with latest wimax and reopen Kernel 2.6.36-gentoo, wimax-1.5.1, wimax-tools-1.4.4 Problem persists. # /etc/init.d/wicd stop * Stopping wicd ... [ok] # iwconfig wlan0 tx off # /etc/init.d/wimax start * Starting WiMAX Network Service ... [ok] # wimaxcu ron ERROR: Turning the SW Radion ON unsuccessfull - Device is UnInitialized. (in dmesg: <7>[ 8497.880684] i2400m_usb 1-8:1.0: __pm_runtime_resume()! <7>[ 8497.880696] i2400m_usb 1-8:1.0: __pm_runtime_resume() returns 1! <7>[ 8497.880915] i2400m_usb 1-8:1.0: __pm_runtime_suspend()! <7>[ 8497.880927] i2400m_usb 1-8:1.0: __pm_runtime_suspend() returns 0! <7>[ 8497.938797] i2400m_usb 1-8:1.0: __pm_runtime_resume()! <7>[ 8497.938809] usb 1-8: __pm_runtime_resume()! <7>[ 8497.938816] usb 1-8: __pm_runtime_resume() returns -22! <7>[ 8497.938826] i2400m_usb 1-8:1.0: __pm_runtime_resume() returns 0! <7>[ 8497.942717] i2400m_usb 1-8:1.0: __pm_runtime_resume()! <7>[ 8497.942735] usb 1-8: __pm_runtime_resume()! <7>[ 8497.942747] usb 1-8: __pm_runtime_resume() returns -22! <7>[ 8497.942762] i2400m_usb 1-8:1.0: __pm_runtime_resume() returns 0! <7>[ 8497.942918] i2400m_usb 1-8:1.0: __pm_runtime_suspend()! <7>[ 8497.942935] i2400m_usb 1-8:1.0: __pm_runtime_suspend() returns 0! <7>[ 8497.955217] i2400m_usb 1-8:1.0: __pm_runtime_resume()! <7>[ 8497.955236] usb 1-8: __pm_runtime_resume()! <7>[ 8497.955249] usb 1-8: __pm_runtime_resume() returns -22! <7>[ 8497.955264] i2400m_usb 1-8:1.0: __pm_runtime_resume() returns 0! <7>[ 8497.955423] i2400m_usb 1-8:1.0: __pm_runtime_suspend()! <7>[ 8497.955439] i2400mus -:.:_p_utm_upn( eun !<7>[ 8497.956688] i2400m_usb 1-8:1.0: __pm_runtime_resume()! <7>[ 8497.956704] usb 1-8: __pm_runtime_resume()! <7>[ 8497.956715] usb 1-8: __pm_runtime_resume() returns -22! <7>[ 8497.956730] i2400m_usb 1-8:1.0: __pm_runtime_resume() returns 0! <7>[ 8497.956911] i2400m_usb 1-8:1.0: __pm_runtime_suspend()! <7>[ 8497.956927] i2400m_usb 1-8:1.0: __pm_runtime_suspend() returns 0! <7>[ 8499.487521] sd 4:0:0:0: __pm_runtime_resume()! <7>[ 8499.487538] sd 4:0:0:0: __pm_runtime_resume() returns 1! ) # wimaxcu roff ERROR: Turning the SW Radion OFF unsuccessfull - Device is UnInitialized. (in dmesg: <7>[ 8508.203374] i2400m_usb 1-8:1.0: __pm_runtime_resume()! <7>[ 8508.203393] usb 1-8: __pm_runtime_resume()! <7>[ 8508.203405] usb 1-8: __pm_runtime_resume() returns -22! <7>[ 8508.203420] i2400m_usb 1-8:1.0: __pm_runtime_resume() returns 0! <7>[ 8508.203925] i2400m_usb 1-8:1.0:__mrniessed) 7[80.091 20mub1810 _mrniessed)rtrs0 <7>[ 8508.204359] i2400m_usb 1-8:1.0: __pm_runtime_resume()! <7>[ 8508.204379] usb 1-8: __pm_runtime_resume()! <7>[ 8508.204394] usb 1-8: __pm_runtime_resume() returns -22! <7>[ 8508.204414] i2400m_usb 1-8:1.0: __pm_runtime_resume() returns 0! <7>[ 8508.204565] i2400m_usb 1-8:1.0: __pm_runtime_suspend()! <7>[ 8508.204581] i2400m_usb 1-8:1.0: __pm_runtime_suspend() returns 0! <7>[ 8508.267161] i2400m_usb 1-8:1.0: __pm_runtime_resume()! <7>[ 8508.267180] usb 1-8: __pm_runtime_resume()! <7>[ 8508.267192] usb 1-8: __pm_runtime_resume() returns -22! <7>[ 8508.267207] i2400m_usb 1-8:1.0: __pm_runtime_resume() returns 0! <7>[ 8508.267330] i2400m_usb 1-8:1.0: __pm_runtime_suspend()! <7>[ 8508.267347] i2400m_usb 1-8:1.0: __pm_runtime_suspend() returns 0! <7>[ 8508.281550] i2400m_usb 1-8:1.0: __pm_runtime_resume()! <7>[ 8508.281568] usb 1-8: __pm_runtime_resume()! <7>[ 8508.281580] usb 1-8: __pm_runtime_resume() returns -22! <7>[ 8508.281595] i2400m_usb 1-8:1.0: __pm_runtime_resume() returns 0! <7>[ 8508.281711] i2400m_usb 1-8:1.0: __pm_runtime_suspend()! <7>[ 8508.281727] i2400m_usb 1-8:1.0: __pm_runtime_suspend() returns 0! <7>[ 8508.284339] i2400m_usb 1-8:1.0: __pm_runtime_resume()! <7>[ 8508.284361] usb 1-8: __pm_runtime_resume()! <7>[ 8508.284377] usb 1-8: __pm_runtime_resume() returns -22! <7>[ 8508.284397] i2400m_usb 1-8:1.0: __pm_runtime_resume() returns 0! <7>[ 8508.284578] i2400m_usb 1-8:1.0: __pm_runtime_suspend()! <7>[ 8508.284594] i2400m_usb 1-8:1.0: __pm_runtime_suspend() returns 0! ) # /etc/init.d/wimax stop * Starting WiMAX Network Service ... [ok] # iwconfig wlan0 tx on # ifconfig wlan0 up SIOCSIFFLAGS: Invalid argument (in dmesg: <7>[ 8531.487174] sd 4:0:0:0: __pm_runtime_resume()! <7>[ 8531 eun !0:00 ircd Werrdtce. etrig02000 3[83.660 wan00:20.:Lae imaevrin .422<> 57090]ilg 000:00 tr W ro o up 3[83.672 wan00:20.:Sau:0x0224 on:5<> 57090]ilg 000:00 ec ie dt1 aa ln 3[83.690 wan00:20.:H_RO_A_OKFI 001)00007 x000000000 9 3[83.693 wan00:20.:p bik bik iik iik hm 3[83.699 wan00:20.:01C001BE01BE0082000004800<> 57096]ilg 000:00 S aus 3[83.691 wan00:20.:(2dbt fCRITCAECN sCRITPROI_E)<> 57098]ilg 000:00 CRH_FCNI_E:00400 3[83.706 wan00:20.: S_N_OLSIG X00f0<> 57002]ilg 000:00 S_N:00000 3[83.709 wan00:20.: S_N_AK X0000<> 57005]ilg 000:00 S_HITSAU:00000 3[83.702 wan00:20.: CRGI_N X0000<> 57008]ilg 000:00 S_EE:00000 3[83.715 wan00:20.: S_PCTL X8435<> 57002]ilg 000:00 CRH_E:00004 3[83.718 wan00:20.: S_ERMRG X0000<> 57005]ilg 000:00 S_ERMG:09000 3[83.711 wan00:20.: S_T_PRG X0200<> 57008]ilg 000:00 S_I_E:00004 3[83.724 wan00:20.: S_PUOERG X0004<> 57002]ilg 000:00 S_PDIE_E:00000 3[83.727 wan00:20.: CRUOEDVG1 X0000<> 57005]ilg 000:00 S_CD_R_P:00000 3[83.721 wan00:20.: CRLDRG X0008<> 57008]ilg 000:00 CRDA_N_B_E:08068 3[83.734 wan00:20.: S_I_HCE_IS X7020<> 57002]ilg 000:00 S_N_L_F:00800 3[83.738 wan00:20.: CRH_E_ARG X010a<> 57005]ilg 000:00 CRDGHE_E_E:0ff00 3[83.748 wan00:20.:SatILEetLgDm:dslyls 0etis<> 57006]ilg 000:00 V_OT00061:x001210 3[83.747 wan00:20.:ETLG:0014300007:29<> 57001]ilg 000:00 V_OT00064:x001b08 3[83.756 wan00:20.:ETLG:0014700000:42<> 57006]ilg 000:00 V_OT00065:x000008 3[83.754 wan00:20.:ETLG:0014700000:44<> 57000]ilg 000:00 V_OT00066:x000508 3[83.763 wan00:20.:ETLG:0014700000:44<> 57003]ilg 000:00 V_OT00067:x000708 3[83.763 wan00:20.:ETLG:0014600000:44<> 57003]ilg 000:00 V_OT00068:x000d08 3[83.763 wan00:20.:ETLG:0014600000:44<> 57003]ilg 000:00 V_OT00069:x000f08 3[83.763 wan00:20.:ETLG:0014400001:44<> 57003]ilg 000:00 V_OT00060:x000508 3[83.763 wan00:20.:ETLG:0015400001:44<> 57003]ilg 000:00 V_OT00060:x000708 3[83.763 wan00:20.:ETLG:0015200001:44<> 57003]ilg 000:00 V_OT00061:x000908 3[83.763 wan00:20.:ETLG:0010800000:15 <> 57003]ilg 000:00 omn EL_XNfie:F ro 3[83.719 wan00:20.:ErrstignwRO -)<3>[ 8538.071136] iwlagn 0000:02:00.0: Error sending POWER_TABLE_CMD: time out after 500ms. <3>[ 8538.071154] iwlagn 0000:02:00.0: set power fail, ret = -110 <4>[ 8538.071595] ------------[ cut here ]------------ <4>[ 8538.071648] WARNING: at drivers/net/wireless/iwlwifi/iwl-core.c:1944 iwl_mac_add_interface+0x48/0xf0 [iwlcore]() <4>[ 8538.071664] Hardware name: 1001HAG <4>[ 8538.071673] Modules linked in: cpufreq_ondemand ledtrig_heartbeat vfat fat snd_hda_codec_realtek iwlagn i2400m_usb uvcvideo atl1c snd_hda_intel iwlcore i2400m videodev eeepc_laptop snd_hda_codec v4l1_compat joydev shpchp iTCO_wdt sparse_keymap iTCO_vendor_support snd_hwdep pci_hotplug <4>[ 8538.071789] Pid: 25904, comm: ifconfig Not tainted 2.6.36-gentoo #1 <4>[ 8538.071801] Call Trace: <4>[ 8538.071826] [<c153087f>] ? printk+0x18/0x21 <4>[ 8538.071852] [<c103c3bd>] warn_slowpath_common+0x6d/0xa0 <4>[ 8538.071893] [<f8337d38>] ? iwl_mac_add_interface+0x48/0xf0 [iwlcore] <4>[ 8538.071932] [<f8337d38>] ? iwl_mac_add_interface+0x48/0xf0 [iwlcore] <4>[ 8538.071955] [<c103c40d>] warn_slowpath_null+0x1d/0x20 <4>[ 8538.071995] [<f8337d38>] iwl_mac_add_interface+0x48/0xf0 [iwlcore] <4>[ 8538.072078] [<c1501321>] ieee80211_open+0x291/0x800 <4>[ 8538.072103] [<c13f3d76>] __dev_open+0x96/0xe0 <4>[ 8538.072124] [<c1532f27>] ? _raw_spin_unlock_bh+0x17/0x20 <4>[ 8538.072145] [<c13f307d>] __dev_change_flags+0x7d/0x150 <4>[ 8538.072168] [<c11c10a7>] ? selinux_capable+0x37/0x50 <4>[ 8538.072190] [<c13f3c9e>] dev_change_flags+0x1e/0x60 <4>[ 8538.072210] [<c1457227>] devinet_ioctl+0x5f7/0x6b0 <4>[ 8538.072230] [<c13f7d28>] ? dev_ioctl+0xc8/0x700 <4>[ 8538.072250] [<c10b58b3>] ? unlock_page+0x43/0x50 <4>[ 8538.072275] [<c145879a>] inet_ioctl+0x9a/0xc0 <4>[ 8538.072297] [<c13e4120>] sock_ioctl+0x60/0x240 <4>[ 8538.072318] [<c13e40c0>] ? sock_ioctl+0x0/0x240 <4>[ 8538.072338] [<c10fa49d>] do_vfs_ioctl+0x7d/0x590 <4>[ 8538.072366] [<c11bf9a9>] ? selinux_file_ioctl+0x39/0x50 <4>[ 8538.072386] [<c10faa0f>] sys_ioctl+0x5f/0x80 <4>[ 8538.072406] [<c10ea7a9>] ? sys_open+0x29/0x40 <4>[ 8538.072428] [<c1002e8c>] sysenter_do_call+0x12/0x22 <4>[ 8538.072446] ---[ end trace 7954ece6c02a9366 ]--- [ 690.797250] iwlagn 0000:02:00.0: Microcode SW error detected. Restarting 0x2000000. [ 690.797268] iwlagn 0000:02:00.0: Loaded firmware version: 8.24.2.2 [ 690.797297] iwlagn 0000:02:00.0: Start IWL Error Log Dump: [ 690.797310] iwlagn 0000:02:00.0: Status: 0x00021264, count: 5 [ 690.797509] iwlagn 0000:02:00.0: Desc Time data1 data2 line [ 690.797529] iwlagn 0000:02:00.0: HW_ERROR_CAL_LOCK_FAIL (0x0012) 0000000672 0x00000000 0x00000000 494 [ 690.797542] iwlagn 0000:02:00.0: pc blink1 blink2 ilink1 ilink2 hcmd [ 690.797558] iwlagn 0000:02:00.0: 0x18C00 0x18B6E 0x18B6E 0x008C2 0x00000 0x4080010 [ 690.797571] iwlagn 0000:02:00.0: CSR values: [ 690.797581] iwlagn 0000:02:00.0: (2nd byte of CSR_INT_COALESCING is CSR_INT_PERIODIC_REG) [ 690.797599] iwlagn 0000:02:00.0: CSR_HW_IF_CONFIG_REG: 0X00480301 [ 690.797616] iwlagn 0000:02:00.0: CSR_INT_COALESCING: 0X0000ff40 [ 690.797633] iwlagn 0000:02:00.0: CSR_INT: 0X00000000 [ 690.797650] iwlagn 0000:02:00.0: CSR_INT_MASK: 0X00000000 [ 690.797667] iwlagn 0000:02:00.0: CSR_FH_INT_STATUS: 0X00000000 [ 690.797682] iwlagn 0000:02:00.0: CSR_GPIO_IN: 0X00000000 [ 690.797698] iwlagn 0000:02:00.0: CSR_RESET: 0X00000000 [ 690.797715] iwlagn 0000:02:00.0: CSR_GP_CNTRL: 0X080403c5 [ 690.797732] iwlagn 0000:02:00.0: CSR_HW_REV: 0X00000044 [ 690.797749] iwlagn 0000:02:00.0: CSR_EEPROM_REG: 0X00000000 [ 690.797766] iwlagn 0000:02:00.0: CSR_EEPROM_GP: 0X90000804 [ 690.797783] iwlagn 0000:02:00.0: CSR_OTP_GP_REG: 0X00020000 [ 690.797800] iwlagn 0000:02:00.0: CSR_GIO_REG: 0X00080046 [ 690.797817] iwlagn 0000:02:00.0: CSR_GP_UCODE_REG: 0X00000004 [ 690.797832] iwlagn 0000:02:00.0: CSR_GP_DRIVER_REG: 0X00000000 [ 690.797849] iwlagn 0000:02:00.0: CSR_UCODE_DRV_GP1: 0X00000000 [ 690.797865] iwlagn 0000:02:00.0: CSR_UCODE_DRV_GP2: 0X00000000 [ 690.797882] iwlagn 0000:02:00.0: CSR_LED_REG: 0X00000018 [ 690.797899] iwlagn 0000:02:00.0: CSR_DRAM_INT_TBL_REG: 0X880367e6 [ 690.797916] iwlagn 0000:02:00.0: CSR_GIO_CHICKEN_BITS: 0X27800200 [ 690.797933] iwlagn 0000:02:00.0: CSR_ANA_PLL_CFG: 0X00880300 [ 690.797950] iwlagn 0000:02:00.0: CSR_HW_REV_WA_REG: 0X0001001a [ 690.797967] iwlagn 0000:02:00.0: CSR_DBG_HPET_MEM_REG: 0Xffff0000 [ 690.798041] iwlagn 0000:02:00.0: Start IWL Event Log Dump: display last 20 entries [ 690.798076] iwlagn 0000:02:00.0: EVT_LOGT:0000016377:0x00000122:1005 [ 690.798100] iwlagn 0000:02:00.0: EVT_LOGT:0000016378:0x00000074:1209 [ 690.798125] iwlagn 0000:02:00.0: EVT_LOGT:0000016409:0x0000010b:0481 [ 690.798150] iwlagn 0000:02:00.0: EVT_LOGT:0000016412:0x0000000b:0482 [ 690.798174] iwlagn 0000:02:00.0: EVT_LOGT:0000016421:0x00000000:0483 [ 690.798199] iwlagn 0000:02:00.0: EVT_LOGT:0000016422:0x00000000:0484 [ 690.798222] iwlagn 0000:02:00.0: EVT_LOGT:0000016428:0x00000005:0484 [ 690.798222] iwlagn 0000:02:00.0: EVT_LOGT:0000016432:0x00000006:0484 [ 690.798222] iwlagn 0000:02:00.0: EVT_LOGT:0000016437:0x00000007:0484 [ 690.798222] iwlagn 0000:02:00.0: EVT_LOGT:0000016441:0x00000008:0484 [ 690.798222] iwlagn 0000:02:00.0: EVT_LOGT:0000016446:0x0000000d:0484 [ 690.798222] iwlagn 0000:02:00.0: EVT_LOGT:0000016451:0x0000000e:0484 [ 690.798222] iwlagn 0000:02:00.0: EVT_LOGT:0000016455:0x0000000f:0484 [ 690.798222] iwlagn 0000:02:00.0: EVT_LOGT:0000016459:0x00000010:0484 [ 690.798222] iwlagn 0000:02:00.0: EVT_LOGT:0000016465:0x00000015:0484 [ 690.798222] iwlagn 0000:02:00.0: EVT_LOGT:0000016469:0x00000016:0484 [ 690.798222] iwlagn 0000:02:00.0: EVT_LOGT:0000016473:0x00000017:0484 [ 690.798222] iwlagn 0000:02:00.0: EVT_LOGT:0000016477:0x00000018:0484 [ 690.798222] iwlagn 0000:02:00.0: EVT_LOGT:0000016482:0x00000019:0484 [ 690.798222] iwlagn 0000:02:00.0: EVT_LOGT:0000017043:0x00000000:0125 [ 690.798222] iwlagn 0000:02:00.0: Command REPLY_RXON failed: FW Error [ 690.798222] iwlagn 0000:02:00.0: Error setting new RXON (-5) [ 691.298139] iwlagn 0000:02:00.0: Error sending REPLY_CT_KILL_CONFIG_CMD: time out after 500ms. [ 691.298156] iwlagn 0000:02:00.0: REPLY_CT_KILL_CONFIG_CMD failed [ 691.798126] iwlagn 0000:02:00.0: Error sending POWER_TABLE_CMD: time out after 500ms. [ 691.798145] iwlagn 0000:02:00.0: set power fail, ret = -110 ... ) So it seems that this problem maybe related to wifi firmware too. I can use wifi again only after reboot; even rmmod&modprobe doesn't help. Please reopen this bug. I can confirm that the WiMAX radio won't turn on with the following setup -- HW: Intel 5350 (in Thinkpad X301) Kernel: tuxonice-sources-2.6.35-r8 WiMAX: wimax-1.5.1 WiMAX tools: wimax-tools-1.4.4 Firmware: i2400m-fw-1.5.0 Not only can wimaxcu and rfkill not remove the soft block on the wimax radio, rfkill does not report that the wimax is hard-blocked when I activate the hardware kill switch. Naively, this suggests that the radio power logic in the i2400m-usb driver is not correct. One bright side for me is that my WiFi seems to work no matter what I try to do to the WiMAX. Please re-open the bug, or mark it as upstream so we can bother the Intel people. (In reply to comment #21) > I can confirm that the WiMAX radio won't turn on with the following setup -- > > HW: Intel 5350 (in Thinkpad X301) > Kernel: tuxonice-sources-2.6.35-r8 > WiMAX: wimax-1.5.1 > WiMAX tools: wimax-tools-1.4.4 > Firmware: i2400m-fw-1.5.0 > > Not only can wimaxcu and rfkill not remove the soft block on the wimax radio, > rfkill does not report that the wimax is hard-blocked when I activate the > hardware kill switch. Naively, this suggests that the radio power logic in the > i2400m-usb driver is not correct. > > One bright side for me is that my WiFi seems to work no matter what I try to do > to the WiMAX. > > Please re-open the bug, or mark it as upstream so we can bother the Intel > people. > Can you post bugreport to http://linuxwimax.org/bugzilla/? seems like fw bug to solve the problem after the installation, you must do: sed -e "s:<ModeOfOperationProduction>1</ModeOfOperationProduction>:<ModeOfOperationProduction>0</ModeOfOperationProduction>:g" -i "/etc/wimax/config.xml" , or modify the ebuild. I can confirm. Strange, but this really works! |