After installing Ubuntu 7.10 and trying to set up wired ethernet connection, only item in the "network" screen was "modem". After restart, 3 items showed up in Network: "modem", "wired" and "wireless". Set up "wired" using static IP address; firefox says "server not found".
Restarted PC and this time the only item in Network was "modem". Each time I fail to connect and restart, a different combination of items shows up in Netrwork. I have both an ethernet cable and a Linksys WUSB11 adapter plugged in. What's going on ?

let's try to use the shell. Go to Applications > Accessories > Terminal

type the following:
this will give you a list of network adapters available on your computer. the output of the above command should look like this:
so as you see, i have three adapters the first is eth0 (wired ethernet connection) ... lo is a local loopback adapter used for testing and other software ... wlan0 is a wireless card.

could you describe what you get when you type the command above ? well go from there ...

The place to start in figuring out your network configuration is with the ifconfig command Log in as root and issue this command:

ifconfig

You can display what hardware is being recognized with the lspci command:

lspci

-------------------------
Steve Stites

Hi there,

I'm having the same problem as the original poster of this issue. I can't connect via wireless:

Ubuntu 7.4
Dell Inspiron 1150 laptop

uname -a
Linux mandolin 2.6.20-16-generic #2 SMP Tue Dec 18 05:45:12 UTC 2007 i686 GNU/Linux

Below is output of "ifconfig" and "lspci". Seems the system "sees" the Broadcom Wireless LAN controller. But I can't do anything (even "ping") via wireless. If I disconnect my wired cable, I'm off the network.


$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:0F:1F:1A:9E:2B
inet addr:192.168.1.101 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::20f:1fff:fe1a:9e2b/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:895 errors:0 dropped:0 overruns:0 frame:0
TX packets:882 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:587880 (574.1 KiB) TX bytes:169483 (165.5 KiB)
Interrupt:7

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:2 errors:0 dropped:0 overruns:0 frame:0
TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:100 (100.0 b) TX bytes:100 (100.0 b)


$ lspci
00:00.0 Host bridge: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02)
00:00.1 System peripheral: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02)
00:00.3 System peripheral: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02)
00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)
00:02.1 Display controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 01)
00:1d.1 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 01)
00:1d.2 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 01)
00:1d.7 USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller (rev 01)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 81)
00:1f.0 ISA bridge: Intel Corporation 82801DBM (ICH4-M) LPC Interface Bridge (rev 01)
00:1f.1 IDE interface: Intel Corporation 82801DBM (ICH4-M) IDE Controller (rev 01)
00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 01)
00:1f.6 Modem: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Modem Controller (rev 01)
02:01.0 Ethernet controller: Broadcom Corporation BCM4401 100Base-T (rev 01)
02:02.0 Network controller: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 03)
02:04.0 CardBus bridge: Texas Instruments PCI1510 PC card Cardbus Controller
$

$

your operating system sees the card in the pci slot but it doesn't have a driver for it.

If ubuntu had the driver for it then it would should up in the ifconfig output. the first wireless card configured will show up as "wlan0"

Do you know what type of wireless card you've got? if you don't, copy the service pack # from the bottom of your laptop and go to http://support.dell.com then go to warranty info > original system config.
That should show a list of hardware originally installed on the laptop when it was bought.

Please post what model of a wireless card you've got or research installing the driver under ubuntu 7.4

Hi there,

The DELL web site wasn't much help. It gave less detail than "lspci". So I did a little internet search. I found the following page very useful:

https://help.ubuntu.com/community/Wi...b6ce95ea5548c6

I followed the instructions and got wireless working!

Many thanks.

HI

Use this

vi /etc/resolv.conf

And write your domain ip address



# this is your domain ip address xxx.xxx.xxx.xxx
nameserver xxx.xxx.xxx.xxx

You're asking a newbie to use vi? You sadist! :P
Better make that

sudo gedit /etc/resolv.conf

What neriok is referring to, is to manually set your DNS server address, so that Firefox will be able to locate the ip address of the website you are trying to visit. But that won't help with your unreliable device listings.

Thanx to Waelaltaqi, Jailbait, etc who replied to my thread. After erasing and reinstalling Ubuntu 7,10 the following" lspci"
After various bridge,IDE,USB, SMbus, and Multimedia entries, there is one like this:
00:0f:0 Ethernet Controller: Accton Technology Corp SMC2-1211TX (rev 10)

The "ifconfig" response included 3 entries:
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: 16 errors: 0 dropped:0 overruns:0 frame:0
TX packets: 16 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
There was no "lo" on the left side but it appears to be running since I can ping it.

wlan0 Link encap:Ethernet HWaddr 00:16:B6:5A:62:CD
UP BROADCAST MULTICAST MTU:1500 Metric 1
RX packets 296 errors:0 dropped:0 overruns:0 frame:0
TX packets 128 errors:0 dropped:0 overruns:0 Carrier:0
collisions:0 txqueuelen:1000
RX bytes:23757 (23.2KB) TX bytes:14708 (14.3KB)
I assume the wlan0 is configured correctly and (now) I am connected to the internet
using the wireless mode (WUSB54G). I believe this happened automatically using UBUNTU driver rt2500USB not the Linksys54G .inf file driver. What's this all about ?

wmaster0 Link encap: UNSPEC HWaddr 00-16-B6-5A-62-CD-(followed by ten "00"
entries)
UP BROADCAST RUNNING 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.0KB) TX bytes:0 (0.0KB)
I presume this wmaster entry is the eth0 that ususally shows up at the top of this listing.
The "IPV6" entry in the listing resulting from "gedit /etc/modprobe.d/aliases" is now in the
"off" position.
So,Jailbait, etc I still have no eth0 wired connection which I prefer for various reasons. Any ideas ?

I do not know what wmaster0 is about but Google is your friend. You can see that the wmaster0 has the same HWADDR as your wlan0, so they are probably related. If you have a normal ethernet device then it should be listed as eth0 or eth1, nothing else. You can get extra information about your (wireless) device by running "lspci -v". There should be two devices of course, on wired and one wireless device. If a device does not work, you may check the "dmesg" output, e.g. "dmesg | less" to see what is going on. There is likely to be some irq mapping message or detection message regarding eth0, if it is working. Sometimes it is said to work to pass this option to the kernel: routeirq=pci. You can try this out in Grub while in the boot menu at startup, by editing the bootentry (select the linux line, press 'e', go to the kernel line, press 'e', add the option, enter, then press 'b' to boot), or by adding "#kopt=routeirq=pci" to your /boot/grub/menu.lst (at the end, or in the proper section) and then running sudo grub-update. Good luck.

Btw: I don't know what this .inf business is all about, but if you're trying to use a windows driver for linux, you're a bit out of luck I guess.

Edit:

I see that your wifi device is usb, so that prolly means it won't show up in lspci. Just check your dmesg. There should be an eth0 device nonetheless, or sometimes you end up having a eth1 which may cause dhclient to use the wrong interface, but you're trying to go static so that's a bit irrelevant here. Make sure that IF you have an ethernet device, your routing is set up correctly ie. check the output of 'route' (it's a bit hard to decode). You're not at that stage yet, and your settings may be correct. If your device shows up, and your routing is set up correctly, you should be able to ping any address such as 209.85.135.99. If you can ping 209.85.135.99 but you cannot ping www.google.com, then your DNS is not set up and you need to edit resolv.conf. But all in due course.