View previous topic :: View next topic |
Author |
Message |
jpsmith98 n00b
Joined: 21 May 2004 Posts: 2
|
Posted: Tue May 25, 2004 5:07 am Post subject: DWL-122 Installation problems (SIOCSIFFLAGS: No such device) |
|
|
I'm a linux newbie, so bear with me.
I've tried installing my DWL-122 usb wireless device to my Inspiron 5100 and everything works fine until I try
Code: | ifconfig wlan0 up
SIOCSIFFLAGS: No such device |
When I do ifconfig wlan0 it shows all of the proper information (I am using a static IP). I have also looked at dmesg and it says that it has associated prism2_usb with the device. I am also able to ping the IP I set for the device from itself as well, if that's any help. If you need any more information to help me, please ask. Thanks in advance. |
|
Back to top |
|
|
UberLord Retired Dev
Joined: 18 Sep 2003 Posts: 6835 Location: Blighty
|
|
Back to top |
|
|
jpsmith98 n00b
Joined: 21 May 2004 Posts: 2
|
Posted: Tue May 25, 2004 8:49 am Post subject: |
|
|
Here's the output from those 2 commands.
Code: |
bash-2.05b# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:0B:DB:95:FE:DE
inet addr:192.168.1.3 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:920 errors:0 dropped:0 overruns:0 frame:0
TX packets:1524 errors:0 dropped:0 overruns:0 carrier:12
collisions:0 txqueuelen:1000
RX bytes:742696 (725.2 Kb) TX bytes:170082 (166.0 Kb)
Interrupt:10
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:10 errors:0 dropped:0 overruns:0 frame:0
TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:840 (840.0 b) TX bytes:840 (840.0 b)
wlan0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
inet addr:192.168.1.103 Bcast:192.168.1.255 Mask:255.255.255.0
BROADCAST NOTRAILERS 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)
bash-2.05b# iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
wlan0 no wireless extensions.
|
And here's the important bit from dmesg.
Code: |
usb.c: USB device 2 (vend/prod 0x2001/0x3700) is not claimed by any active driver.
prism2usb_init: prism2_usb.o: 0.2.1-pre17 Loaded
prism2usb_init: dev_info is: prism2_usb
usb.c: registered new driver prism2_usb
|
|
|
Back to top |
|
|
UberLord Retired Dev
Joined: 18 Sep 2003 Posts: 6835 Location: Blighty
|
|
Back to top |
|
|
NiXZe Tux's lil' helper
Joined: 22 May 2003 Posts: 77 Location: Uppsala Sweden
|
Posted: Fri Jun 04, 2004 3:35 pm Post subject: |
|
|
UberLord wrote: | I'm guessing that you didn't/don't have wireless support compiled into your kernel before (or now) when you built wireless-tools and/or the prism module.
1. Ensure Wireless support is compiled into kernel - install kernel and reboot
2. Re emerge wireless-tools and the prism module |
i don't think this is the problem in this case since he can use ping, (not directly anyway)?
what is your output from route? and waht is it that you have tried to do and not to do?
is there any servers on the local subnet that you can access (more then ping) or have you only tried to get on the net? _________________ What? Where? Oh! this one, it's Gentoo.
If you don't have anything constructive to say, you might want to consider staying quiet instead.
To many destructive comments, which in no way will help making the Gentoo community better. |
|
Back to top |
|
|
|