Dell True Mobile 1300 on Inspiron 8500 w/SuSE 8.2
I tried the bcmwl5driverloader driver from Linuxant.com. Finally got it to partially work. Initially I was getting a boot error eth1 ERROR: command 'iwconfig eth1 mode Automatic' returned Error for wireless request "Set Mode" (8B06) : SET failed on device eth1 ; Invalid argument. I then ran iwlist scan which showed up the following eth1 Scan completed : Cell 01 - Address: 00:30:AB:14:FD:90 ESSID:"Wireless" Mode:Managed Frequency:2.442GHz Quality:1/1 Signal level:-26 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 I went into Yast network devices and configured the wireless card for Managed and ESSID of Wireless. On reboot, the error went away, but still could not connect to the network. ifconfig resulted in eth0 Link encap:Ethernet HWaddr 00:0B:DB:97:5D:66 inet6 addr: fe80::20b:dbff:fe97:5d66/64 Scope:Link UP 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:100 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Interrupt:11 Base address:0xe000 Memory:faffe000-fafff080 eth1 Link encap:Ethernet HWaddr 00:90:4B:B2:5F:A4 inet addr:10.0.208.38 Bcast:10.0.223.255 Mask:255.255.240.0 inet6 addr: fe80::290:4bff:feb2:5fa4/64 Scope:Link UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:85 errors:0 dropped:0 overruns:0 frame:0 TX packets:8 errors:1 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:11650 (11.3 Kb) TX bytes:1110 (1.0 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:144 errors:0 dropped:0 overruns:0 frame:0 TX packets:144 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:11476 (11.2 Kb) TX bytes:11476 (11.2 Kb) 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) I can ping the 10.0.208.38, but cannot ping the 10.0.208.4 dns server and cannot get to the internet. If I recconnect the regular eth0 cable, everything works. Does anyone have any suggestions on this? Art
First you need to turn off eth0, as I assume you will be using eth1 on the same subnet so 2 interfaces with similar IP numbers will confuse. ifconfig eth0 down and then change in the ifup config file to manual Now how is eth1 getting its IP ifconfig eth1 192.168.0.45 up will get you going if you know a static number then you will need the route to the gateway for this interface route add default gw 192.168.0.1 if this works then add to the config files David On Friday 17 October 2003 6:08 pm, Art Fore wrote:
I tried the bcmwl5driverloader driver from Linuxant.com. Finally got it to partially work. Initially I was getting a boot error
eth1 ERROR: command 'iwconfig eth1 mode Automatic' returned Error for wireless request "Set Mode" (8B06) : SET failed on device eth1 ; Invalid argument.
I then ran iwlist scan which showed up the following
eth1 Scan completed : Cell 01 - Address: 00:30:AB:14:FD:90 ESSID:"Wireless" Mode:Managed Frequency:2.442GHz Quality:1/1 Signal level:-26 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
I went into Yast network devices and configured the wireless card for Managed and ESSID of Wireless. On reboot, the error went away, but still could not connect to the network.
ifconfig resulted in
eth0 Link encap:Ethernet HWaddr 00:0B:DB:97:5D:66 inet6 addr: fe80::20b:dbff:fe97:5d66/64 Scope:Link UP 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:100 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Interrupt:11 Base address:0xe000 Memory:faffe000-fafff080
eth1 Link encap:Ethernet HWaddr 00:90:4B:B2:5F:A4 inet addr:10.0.208.38 Bcast:10.0.223.255 Mask:255.255.240.0 inet6 addr: fe80::290:4bff:feb2:5fa4/64 Scope:Link UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:85 errors:0 dropped:0 overruns:0 frame:0 TX packets:8 errors:1 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:11650 (11.3 Kb) TX bytes:1110 (1.0 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:144 errors:0 dropped:0 overruns:0 frame:0 TX packets:144 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:11476 (11.2 Kb) TX bytes:11476 (11.2 Kb)
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)
I can ping the 10.0.208.38, but cannot ping the 10.0.208.4 dns server and cannot get to the internet. If I recconnect the regular eth0 cable, everything works.
Does anyone have any suggestions on this?
Art
Tried the ifconfig eth0 down and ifconfig eth1 up. Still when I ping the DNS server I get no reply, unless I do it before the two ifconfig lines. The address for both cards comes from DHCP. Art david stevenson wrote:
First you need to turn off eth0, as I assume you will be using eth1 on the same subnet so 2 interfaces with similar IP numbers will confuse. ifconfig eth0 down and then change in the ifup config file to manual Now how is eth1 getting its IP ifconfig eth1 192.168.0.45 up will get you going if you know a static number then you will need the route to the gateway for this interface route add default gw 192.168.0.1 if this works then add to the config files David
On Friday 17 October 2003 6:08 pm, Art Fore wrote:
I tried the bcmwl5driverloader driver from Linuxant.com. Finally got it to partially work. Initially I was getting a boot error
eth1 ERROR: command 'iwconfig eth1 mode Automatic' returned Error for wireless request "Set Mode" (8B06) : SET failed on device eth1 ; Invalid argument.
I then ran iwlist scan which showed up the following
eth1 Scan completed : Cell 01 - Address: 00:30:AB:14:FD:90 ESSID:"Wireless" Mode:Managed Frequency:2.442GHz Quality:1/1 Signal level:-26 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
I went into Yast network devices and configured the wireless card for Managed and ESSID of Wireless. On reboot, the error went away, but still could not connect to the network.
ifconfig resulted in
eth0 Link encap:Ethernet HWaddr 00:0B:DB:97:5D:66 inet6 addr: fe80::20b:dbff:fe97:5d66/64 Scope:Link UP 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:100 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Interrupt:11 Base address:0xe000 Memory:faffe000-fafff080
eth1 Link encap:Ethernet HWaddr 00:90:4B:B2:5F:A4 inet addr:10.0.208.38 Bcast:10.0.223.255 Mask:255.255.240.0 inet6 addr: fe80::290:4bff:feb2:5fa4/64 Scope:Link UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:85 errors:0 dropped:0 overruns:0 frame:0 TX packets:8 errors:1 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:11650 (11.3 Kb) TX bytes:1110 (1.0 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:144 errors:0 dropped:0 overruns:0 frame:0 TX packets:144 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:11476 (11.2 Kb) TX bytes:11476 (11.2 Kb)
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)
I can ping the 10.0.208.38, but cannot ping the 10.0.208.4 dns server and cannot get to the internet. If I recconnect the regular eth0 cable, everything works.
Does anyone have any suggestions on this?
Art
On Friday 17 October 2003 1:08 pm, Art Fore wrote:
I can ping the 10.0.208.38, but cannot ping the 10.0.208.4 dns server and cannot get to the internet. If I recconnect the regular eth0 cable, everything works.
Does anyone have any suggestions on this?
How do you know it is hooking up to the wireless network? I found a problem with the True Mobile 1300 under Windows talking with an older wireless gateway. Have you tried it under windows just the prove the card will work? Greg Engel
Works perfect under windows. Art Greg Engel wrote:
On Friday 17 October 2003 1:08 pm, Art Fore wrote:
I can ping the 10.0.208.38, but cannot ping the 10.0.208.4 dns server and cannot get to the internet. If I recconnect the regular eth0 cable, everything works.
Does anyone have any suggestions on this?
How do you know it is hooking up to the wireless network? I found a problem with the True Mobile 1300 under Windows talking with an older wireless gateway. Have you tried it under windows just the prove the card will work?
Greg Engel
Another interesting thing I discovered, in Windows or Linux, with network cable connected, the network card ccmes up with 10.0.208.36 and the wireless with 10.0.208.38. In windows, the Wireless is interrupt 5 and the network card is interrupt 11, while in Linux, they are both the same. This does not make sense at all. In windows, when I disconnet the network cable, it comes up and tells you it is disconnected, but network and internet access goes along uninterrupted. Art Art Fore wrote:
Works perfect under windows.
Art
Greg Engel wrote:
On Friday 17 October 2003 1:08 pm, Art Fore wrote:
I can ping the 10.0.208.38, but cannot ping the 10.0.208.4 dns server and cannot get to the internet. If I recconnect the regular eth0 cable, everything works.
Does anyone have any suggestions on this?
How do you know it is hooking up to the wireless network? I found a problem with the True Mobile 1300 under Windows talking with an older wireless gateway. Have you tried it under windows just the prove the card will work?
Greg Engel
participants (3)
-
Art Fore -
david stevenson -
Greg Engel