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

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

Faithful John wrote:

>>>>>>Hi all,
>>>>>>I'm a relative newbie who's been using the debian sarge.   I recently
>>>>>>have been trying to install kubuntu on my friends laptop.   She wants
>>>>>>to use linux as a primary system (she doesn't like micro$oft).
>>>>>>Anyway, when I was installing kubuntu off a disc, the network
>>>>>>connections did not set up properly.
>>>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?
>>>Instead, I see [in /etc/network/interfaces]:
>>># This file describes the network interfaces available on your system
>>># and how to activate them.  For more information, see interfaces(5).
>>># The loopback network interface
>>>auto lo
>>>iface lo inet loopback
>>>#This is a list of hotpluggable network interfaces.
>>># They will be activated automatically by the hotplug subsystem.
>>>mapping hotplug
>>>            script grep
>>>            map eth0
>0000:02:01.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M
>[Tornado] (rev 78)
>So it is a 3Com 3c905C-TX/TX-M ethernet controller.

Okay. We're going to assume that the 3c59x kernel is loading properly.
(You can run "lsmod" and look for it; if it's not there, you may want to
run "modconf" and see if you can find it (probably somewhere around
/kernel/drivers/net or thereabouts) which will install it.)

You'll need to edit "/etc/network/interfaces". Add the following two
lines to the bottom of the file:

auto eth0
iface eth0 inet dhcp

Save the file.

Now run "/etc/init.d/networking restart" to restart networking. This
script will look in the file you just editted, and see that your first
(and probably only) ethernet card, "eth0", should be started
automatically at bootup (via this script), and that it should look for a
DHCP-assigned address.

Now you should be able to run "ifconfig", and see something like this:

eth0      Link encap:Ethernet  HWaddr 00:00:E8:11:83:F7
          inet addr:  Bcast: 
          inet6 addr: fe80::200:e8ff:fe11:83f7/64 Scope:Link
          RX packets:303816 errors:110 dropped:0 overruns:0 frame:110
          TX packets:84413 errors:130143 dropped:0 overruns:0 carrier:130143
          collisions:0 txqueuelen:1000
          RX bytes:395042640 (376.7 MiB)  TX bytes:9063977 (8.6 MiB)
          Interrupt:5 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:5309 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5309 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:273273 (266.8 KiB)  TX bytes:273273 (266.8 KiB)

At this point, your network should be working, and you should be able to
ping, ftp, telnet, www-browse, etc.


Reply to: