[SOLVED] SIOCSIFFLAGS: Operation not permitted

Message

joser · Post by **joser** » Tue Oct 05, 2010 1:19 am

Hi everyone,
I'm working on a MSI wind u210 (Ralink rt3090). When I get up
my wireless card it through the following error

ifconfig wlan0 up
SIOCSIFFLAGS: Operation not permitted

I try with the kernel drivers, the staging drivers and downloaded
from the Ralink page without success.

The weird thing is, some kernels before (until linux-2.6.32-gentoo-r7),
it works perfect with the Ralink drivers downloaded from their page.

Thanks!

d2_racing · Post by **d2_racing** » Tue Oct 05, 2010 3:04 am

Hi, can you post this :

Code: Select all

# iwconfig
# ifconfig
# iwlist scan
# dmesg | tail
# cd /usr/src/linux && cat .config | grep -i kill

joser · Post by **joser** » Tue Oct 05, 2010 4:31 am

The information you request me:

#iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 Ralink STA ESSID:"" Nickname:""
Mode:Auto Frequency=2.412 GHz
Link Quality=10/100 Signal level:0 dBm Noise level:-143 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

sit0 no wireless extensions.

#ifconfig -a
eth0 Link encap:Ethernet HWaddr 40:61:86:15:23:00
inet addr:192.168.0.100 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::4261:86ff:fe15:2300/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1521 errors:0 dropped:0 overruns:0 frame:0
TX packets:1668 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1166575 (1.1 MiB) TX bytes:243807 (238.0 KiB)
Interrupt:42 Base address:0x2000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

wlan0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:16

#iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wlan0 Interface doesn't support scanning : Network is down

sit0 Interface doesn't support scanning.

#dmesg | tail
[ 8.536764] [drm] Initialized radeon 2.5.0 20080528 for 0000:01:05.0 on minor 0
[ 11.332822] bootmisc used greatest stack depth: 4080 bytes left
[ 12.880585] r8169 0000:03:00.0: eth0: link up
[ 12.880594] r8169 0000:03:00.0: eth0: link up
[ 19.003664] dhcpcd-run-hook used greatest stack depth: 3240 bytes left
[ 19.206047] Adding 530108k swap on /dev/sda6. Priority:-1 extents:1 across:530108k
[ 23.458040] eth0: no IPv6 routers present
[ 635.448843] rt2860 0000:02:00.0: firmware file rt3090.bin request failed (-2)
[ 635.448847] ERROR! NICLoadFirmware failed, Status[=0x00000001]
[ 635.448854] rt28xx Initialized fail!

#cd /usr/src/linux && cat .config | grep -i kill
CONFIG_RFKILL=y
CONFIG_RFKILL_LEDS=y
CONFIG_RFKILL_INPUT=y
# CONFIG_TOSHIBA_BT_RFKILL is not set

roarinelk · Post by **roarinelk** » Tue Oct 05, 2010 6:23 am

joser wrote:The information you request me:

[ 635.448843] rt2860 0000:02:00.0: firmware file rt3090.bin request failed (-2)
[ 635.448847] ERROR! NICLoadFirmware failed, Status[=0x00000001]
[ 635.448854] rt28xx Initialized fail!

There's your problem: missing firmware blob.

joser · Post by **joser** » Tue Oct 05, 2010 10:42 am

Yeah!, your right. I Realized some days ago about that.
I founded in my /lib/firmware directory a file rt3090*.bin but it seems not to be working.

Today after reading your answer (from roarinelk) I went to /lib/firmware and rename a file
named rt2860.bin to rt3090.bin and seems to be working.

I will test it during the day and go back to tell you if its working OK.
Thank you.

joser · Post by **joser** » Wed Oct 06, 2010 11:51 pm

Thank you guys, I tested it for several days and it works perfect.

The post can be set as SOLVED.

d2_racing · Post by **d2_racing** » Thu Oct 07, 2010 3:36 am

Nice then

solamour · Post by **solamour** » Mon Oct 28, 2013 2:39 am

I was having the exactly same problem, and "sys-kernel/linux-firmware" was the answer. Thanks.

Sad thing is, I did solve the problem after reading this post a long time ago, but a while later, I completely forgot what I did, so I had to do the same fumbling and search. I hope I don't forget this time.
__
sol