[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Newbie --Admin access problem on KDE... HELP!!

Faithful John,

This is what I have really enjoyed about Linux in general and debian in particular -- learning how to do this stuff. And trust me Google is your friend. I have learned how to do so much stuff using google its ridiculous... on to your problem.

Faithful John wrote:

So I did that, and this is what I see:

lo      Link encap:Local Loopback
       inet addr:   Mask:
       inet 6 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
        RX bytes:1264  (1.2 KiB)    TX  bytes:1264  (1.2 KiB)

So I need network connection, right?  How do I do that?

Right. the loopback is configured, but you have no outgoing connection.

IMO the easiest way to do this is add the following lines to /etc/network/interfaces. you'll have to be root at a command line and use an editor such as vi, nano, etc. In debian if you type editor I think its mapped to nano and is straightforward.

auto eth0
iface eth0 inet dhcp

the first line says to automatically configure eth0 (the first ethernet device) the second line says how to configure it. in this case as an internet connection using dhcp.

save those changes then type:

ifup -a

it should warn you that iface lo is already configured.

type ifconfig and you should get something like:

eth0      Link encap:Ethernet  HWaddr 00:E0:18:8A:A2:86
          inet addr:  Bcast:  Mask:
          inet6 addr: fe80::2e0:18ff:fe8a:a286/64 Scope:Link
          RX packets:711757 errors:0 dropped:0 overruns:0 frame:0
          TX packets:516430 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:378357529 (360.8 MiB)  TX bytes:50068281 (47.7 MiB)
          Interrupt:185 Base address:0xd000

lo        Link encap:Local Loopback
          inet addr:  Mask:
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:12309807 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12309807 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:2284340742 (2.1 GiB)  TX bytes:2284340742 (2.1 GiB)

and you should be up and running. of course, the NIC has to be plugged in... and you're address is unlikely to be 192.168.xxx.xxx unless you're on a home or local network.

If not working see below.

I will switch to the linux and tell you, but I thought I'd tell you
what I already know about the computer (from what I learned from the
windows XP half... if that is useful).   It says it's "3Com 3C920
Integrated Fast Ethernet Controller (3C905C-TX Compatible)"  it also
has an external D-Link Air Wireless card (DWL-650).

I googled that interface and couldn't find (just a quick check, didn't dig a lot) it specifically, but it appears that 3com devices have good support. So if the above didn't work, then maybe you don't have the driver loaded automatically. type lsmod and check the output. lsmod lists all the currently loaded modules in the kernel. you're looking for something like "3c5xxx..." listed as one of the modules. That's the 3com driver. if you can't find it, then you're network card isn't being detected and you have bigger problems. In that case, send us the outputs of both lspci and lsmod. oh, and I'm clueless about wireless, but its a similar situation -- making sure the right drivers are loaded and setting up a configuration for it in interfaces, I guess.


Reply to: