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. >>>> >What I'm having trouble with is that since the network is down, I am >trying to see if I can get it going. > > >The problem is that the stuff I do understand to do (or can sorta >figure out), doesn't seem to work. And the other stuff, doesn't tell >me enough to do anything with. I'm a newbie, so telling me to change >this file to this, without telling me where or how to do so is >unhelpful. >
>>Oliver Elphick wrote: >> >>>Now type >>> >>> ifconfig >>> >>>which will show you what network connections there are. There should >>>always be one called "lo", which is the loopback interface (for the >>>machine to talk to itself. If that is the only one, you need to set up >>>the network connection; unfortunately, just what you need to do to >>>accomplish that depends on what went wrong. >>> >>> > >So I did that, and this is what I see: > >lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > 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 > > > > > >>For DHCP, the stanza would like like this: >> >>auto eth0 >>iface eth0 inet auto >> >> >>I would suggest using the Debian init script: >> >>/etc/init.d/networking restart >> >> >>You might also run "lspci" to make sure the NIC is being identified; if >>it says "unknown device" or something similar, you may be up a creek >>without a paddle. Did Kubuntu work with the network when run as a LiveCD >>rather than as a hard drive installation? >> >> > >Not sure how to run "lspci"... >thanks for all the help guys. > > At a command prompt, type "lspci" and then press the Enter key. You'll see stuff like this: enjae[westk]:/home/westk> lspci 0000:00:00.0 Host bridge: Advanced Micro Devices [AMD] AMD-760 [IGD4-1P] System Controller (rev 12) 0000:00:01.0 PCI bridge: Advanced Micro Devices [AMD] AMD-760 [IGD4-1P] AGP Bridge 0000:00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 40) 0000:00:07.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) 0000:00:07.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 16) 0000:00:07.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 16) 0000:00:07.4 SMBus: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 40) 0000:00:07.5 Multimedia audio controller: VIA Technologies, Inc. VT82C686 AC97 Audio Controller (rev 50) 0000:00:09.0 Ethernet controller: Lite-On Communications Inc LNE100TX (rev 20) 0000:01:05.0 VGA compatible controller: ATI Technologies Inc Rage 128 PF/PRO AGP 4x TMDS Notice that my ethernet controller is a "Lite-On" LNE100TX. What is yours? -- Kent -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
