Bug 19352 - i2400m_usb invalid state
Summary: i2400m_usb invalid state
Status: RESOLVED OBSOLETE
Alias: None
Product: Drivers
Classification: Unclassified
Component: network-wireless (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: Iñaky Pérez-González
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-30 06:55 UTC by Roman Sergeev
Modified: 2012-08-13 16:45 UTC (History)
2 users (show)

See Also:
Kernel Version: 2.6.35-r9
Subsystem:
Regression: No
Bisected commit-id:


Attachments
lsusb -v (3.38 KB, text/plain)
2010-09-30 06:55 UTC, Roman Sergeev
Details
logs (44.68 KB, text/plain)
2010-09-30 06:56 UTC, Roman Sergeev
Details
kernel config (75.20 KB, text/plain)
2010-09-30 07:00 UTC, Roman Sergeev
Details
detailed logs (49.77 KB, text/plain)
2010-09-30 14:00 UTC, Roman Sergeev
Details
wimaxd.log (1.57 KB, application/octet-stream)
2010-09-30 17:31 UTC, Roman Sergeev
Details

Description Roman Sergeev 2010-09-30 06:55:49 UTC
Created attachment 32002 [details]
lsusb -v

can't turn on device

rfkill list
0: eeepc-wlan: Wireless LAN
	Soft blocked: no
	Hard blocked: no
2: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no
4: i2400m-usb:1-6:1.0: WiMAX
	Soft blocked: yes
	Hard blocked: no

rfkill unblock 4
Sep 30 13:52:06 myhost kernel: [ 3603.870294] i2400m_usb 1-6:1.0: 'RF Control' (0x4602) command failed: -84 - invalid state (3)
Comment 1 Roman Sergeev 2010-09-30 06:56:29 UTC
Created attachment 32012 [details]
logs
Comment 2 Roman Sergeev 2010-09-30 07:00:15 UTC
Created attachment 32022 [details]
kernel config
Comment 3 Roman Sergeev 2010-09-30 14:00:04 UTC
Created attachment 32052 [details]
detailed logs
Comment 4 Iñaky Pérez-González 2010-09-30 16:34:11 UTC
Was the wimaxd daemon running at the time you tried this?
Comment 5 Roman Sergeev 2010-09-30 17:06:03 UTC
(In reply to comment #4)
> Was the wimaxd daemon running at the time you tried this?

no

but if i run wimaxd and when do rfkill - same result:

Oct  1 00:20:32 myhost wimaxd: daemon starts
Oct  1 00:20:32 myhost wimaxd: pdifile is created
Oct  1 00:20:32 myhost wimaxd: wimaxd event: AppSrv is ready
Oct  1 00:21:04 myhost kernel: [  130.655888] i2400m_usb 1-6:1.0: 'RF Control' (0x4602) command failed: -84 - invalid state (3)
Comment 6 Iñaky Pérez-González 2010-09-30 17:10:16 UTC
I see -- the daemon is failing to initialize the device properly, that's why the thing is failing.

Can you post the contents of /etc/modprobe.d/i2400m.conf?
Comment 7 Roman Sergeev 2010-09-30 17:13:06 UTC
# 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
Comment 8 Iñaky Pérez-González 2010-09-30 17:20:51 UTC
that looks like it should...

can you do the following

$ killall -9 wimaxd
$ rm -f /var/log/wimax/*
$ wimaxd -i wmx0 -b
$ wimaxcu ron
$ kilall -9 wimaxd

Attach the /var/log/wimax/wimaxd.log file? [you can ignore system_log and wimaxcu.log]
Comment 9 Roman Sergeev 2010-09-30 17:31:17 UTC
Created attachment 32082 [details]
wimaxd.log
Comment 10 Roman Sergeev 2010-10-04 17:54:49 UTC
wifi does not work too in this device
\with new drivers\

https://bugzilla.kernel.org/show_bug.cgi?id=19742
Comment 11 Roman Sergeev 2010-10-23 20:07:20 UTC
hi
i found something strange
i try to downgrade kernel version (2.6.34-r12) what use previous wimax driver
and i have a same error

firmware used i2400m-usb-1.4

Note You need to log in before you can comment on or make changes to this bug.