ioctl[...]: No such device
Thu Jul 6 21:38:32 PDT 2006
Quoting John - <JohnRChamplin at columbus.rr.com>:
> Thanks for the quick answer, Pavel. I agree that the problem's
> probably just bringing the interface up. I'm not using WEP or WPA yet.
> Here's the information you asked for, including complete error
> root@~# ifconfig
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:4 errors:0 dropped:0 overruns:0 frame:0
> TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:280 (280.0 b) TX bytes:280 (280.0 b)
"ifconfig -a" would show all interfaces, including those that are down.
> root@~# iwconfig wlan0
> wlan0 No such device
iwconfig without arguments will show all interfaces. Do you have the driver
loaded at all? Did it find the hardware? "dmesg" shows kernel messages,
including those from the driver.
> I fear that these two items may not be particularly informative. So
> what next?
Load the driver are try again. Try to bring the interface up using ifconfig.
Check the kernel messages.
Generally, describe what your are doing. I have no idea from your message if
"iwconfig wlan0" stopped working after you tried to bring wlan0 up or after you
loaded the driver or after clean reboot.
When reporting problems with software, mention versions of the software involved
(hostap, kernel). In this case, the hardware version of the card may be useful
as well. If the driver detects the card, it should print some information,
such as the firmware versions. That would be useful too.
More information about the Hostap