[driverloader] driverloader w/ WPC54G - Connects to router but nothing else...

Antonio Howe antonioh at shaw.ca
Fri Mar 19 17:07:50 EST 2004


Hello,

I spent the last few days trying to get driverloader running on my machine, 
with very little luck. Last night I installed Mandrake 10 with the 2.6.3 
kernel, and have finally managed to get driverloader installed and 
(apparently) running properly, but am unable to connect to anything. I can't 
even ping the router. 

Driverloader recognises my WPC54G wireless card, and the card even connects to 
my router. At least I'm assuming it is connecting to my router because it 
shows an IP address when I run "ifconfig" (eth1 is my wireless card. I only 
have eth0 enabled so that I can send this email).

eth0      Link encap:Ethernet  HWaddr 08:00:46:13:84:42
          inet addr:192.168.1.153  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::a00:46ff:fe13:8442/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:7489 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6595 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:6329130 (6.0 Mb)  TX bytes:610373 (596.0 Kb)
          Interrupt:9 Base address:0xe000

eth1      Link encap:Ethernet  HWaddr 00:06:25:43:86:D3
          inet addr:192.168.1.151  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::206:25ff:fe43:86d3/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:14 errors:0 dropped:0 overruns:0 frame:0
          TX packets:30 errors:10 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:5574 (5.4 Kb)  TX bytes:4596 (4.4 Kb)

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:571 errors:0 dropped:0 overruns:0 frame:0
          TX packets:571 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:181331 (177.0 Kb)  TX bytes:181331 (177.0 Kb)

Here is what I get when I run "iwlist scan"

lo        Interface doesn't support scanning : Operation not supported

eth0      Interface doesn't support scanning : Operation not supported

sit0      Interface doesn't support scanning : Invalid argument

eth1      Scan completed :
          Cell 01 - Address: 00:0C:41:AA:CF:B2
                    ESSID:"Wireless"
                    Mode:Managed
                    Frequency:2.437GHz
                    Quality:1/1  Signal level:-50 dBm  Noise level:-200 dBm
                    Encryption key:off
                    Bit Rate:1Mb/s
                    Bit Rate:2Mb/s
                    Bit Rate:5.5Mb/s
                    Bit Rate:11Mb/s
                    Bit Rate:18Mb/s
                    Bit Rate:24Mb/s
                    Bit Rate:36Mb/s
                    Bit Rate:54Mb/s
                    Extra:bcn_int=100

I have checked over the settings on my router (Linksys WRT54G) and as far as I 
can tell nothing should be blocking the connection from my wireless card. 
Encyption is disabled (for now), DHCP is setup, and obviously working fine 
because it has provided my wireless card with an IP address. 

One peculiar thing I did notice when in drakconf was that my wireless card is 
listed as "eth1: Intel Corporation|82815 815 Chipset Host Bridge and Memory 
Controller Hub" This is the same no matter which winxp driver set I use. 
I felt this was not really an issue though, seeing as the router is providing 
the card with an IP address.

One thing I am not sure of though is whether I should be setting this up in 
drakconf as a wireless connection or a lan connection. I have attempted 
wireless, but the driver is not listed as an option. When I setup lan it is 
offered.

Anyways, this email is probably a little jumbled. I've been working on this 
for hours and i think my brains fried.

I'm hoping you guys have come across this already, any information and help 
would be GREATLY appreciated. If there is anything more you need to know 
about my system let me know and I'll get right back to you.

Thanks,

Antonio Howe


More information about the driverloader mailing list