Tiny Core Extensions > TCE Q&A Forum
cannot get wifi iwlagn to work
maro:
The more important information for your sort of problem is in the 'dmesg' output, so please post that as well.
EDIT: Futhermore please double-check that the firmware is installed (e.g. via find /usr/local -name iwlwifi-5000-*.ucode) before you use 'sudo ifconfig wlan0 up'.
slamet:
Ah sorry, somehow that attachment did not upload. My bad. Attached are the dmesg output and the "find /usr/local -name iwlwifi*". Thanks.
Arslan S.:
is there a hard switch on your notebook ? if there is check if it is on state
maro:
--- Quote from: Arslan S. on January 04, 2011, 10:11:07 AM ---is there a hard switch on your notebook ? if there is check if it is on state
--- End quote ---
I initially thought the same, in particular when reading the 'RF_KILL bit toggled to disable radio' message in the 'dmesg' output. But with a bit of google-ing I saw this thread and that indicates to me that there might be some other messages possible (e.g. like 'Radio disabled by HW RF Kill switch').
OTOH, I just managed to get the same "ifconfig: SIOCSIFFLAGS: Unknown error 132" error if I try to bring up the interface but have not enabled the WiFi by pressing a button on the notebook (which then lights up a blue LED in my case). It might be that for other OS (e.g. M$) this enabling is done by default. Another indication for this state would be 'Tx-Power=off' in the 'iwconfig' output (compared to 'Tx-Power=12 dBm' after the enabling button was pressed).
@slamet: If all these pointers are not leading to success I'd like to get a "fuller picture" and wonder if you could attach the complete 'dmesg' output (i.e. from booting til after the 'sudo ifconfig ... up'). It might be even worthwhile to use boot code 'printk.time=1' to get timestamps on the messages. Furthermore I wonder if you could also attach the output of 'lsmod', 'ifconfig -a' and 'iwconfig' (all of those after the 'sudo ifconfig ... up' failure).
slamet:
Yes, on MS Windows, the "switch" is turned "on" by the OS. (This machine is a Win7 machine.) Once it's on, I can turn it on or off by pushing this "switch". Not exactly a hardware switch, but more like something to signal to the OS, I think - not my favourite HP laptop. The "switch" is software controlled.
I think it worked almost similarly on KUbuntu 10.10 which was able to get the wifi working on this exact machine. I have since lost my KUbuntu set up and have not bothered to reinstall it since I like Tiny Core better, so I would like to invest the time to get it working within my limited technical skill, if possible.
Attached are the requested output messages. With regard to the boot code, my Tiny never go to "boot" prompt mode once it is installed, so I don't know how to do it. But all of these commands were done within a minute of each other.
Thanks again for all your help.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version