>
> >>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.   Anyway, I have no connection to
> >>the internet on that laptop and so I am having lots of trouble
> >>updating the thing.   I don't even have admin access.   I know it's a
> >>bug with KDE, and it's been reported, but I can't make any sense of the 
> >>advice
> >>people give.   Either it doesn't seem to work, or there isn't enough
> >>information for a newbie to follow the instructions.
> >>
> >>When I try to do something to change the network settings, I can't
> >>seem to log in as the administrator to do that.   I don't even know
> >>where to start to get it going, especially since I can't get admin
> >>access.
> >>Selam
> >>
> >>
> >
> >To get admin access, you need to log in as root, for which you will need
> >the root password you set up when asked.
> >
> >Since you talk of a bug in KDE, you would probably do better not to use
> >the graphical screen, so:
> >
> >press <Ctrl>+<Alt>+<F1>
> >that should take you out of the graphical screen and display the first
> >virtual terminal (a black and white screen).  If you don't see a login
> >prompt, press return a couple of times until it appears.
> >
> >In response to the login prompt, enter "root"
> >In response to the password prompt, enter the root password you set up
> >
> >
> I can't say about [K]Ubuntu, but both Knoppix and Kanotix don't have
> root set up for login. Instead, you have to use "sudo".

What I'm having trouble with is that since the network is down, I am
trying to see if I can get it going.   Well, the trouble is when I go
the Settings, it says I can't change the setting unless i'm in the
Administrator mode.   The network setting don't really tell me how to
activate it.   But when I go to wireless (it's a laptop), there is a
button there for that.   When I click the administrator mode button,
it asks for the root password.   Once typed in, absolutely nothing
happens.   It is a bug as I've seen the bug report see link below.

https://bugzilla.ubuntu.com/show_bug.cgi?id=8681

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.

Plus someone on that report indicated that it was a problem with KDE
and not the kubuntu itself, as there have been similar problems with
other distros with KDE.   Either way I'm going to try to the above
steps as much as possible.......


> 
> I _think_ you can use sudo to change root's password, so that root then
> becomes available:
> 
> "sudo passwd root"
> 
> Faithful John may also be trying to log into X/KDE as root. I believe
> Kubuntu may be Debian-based, and if so, may have inherited Debian's
> restrictions concerning logging into X/KDE as root (which is to say, you
> can't do it in the default setup).
> 
> F.  John may also be trying to use some KDE-ified GUI for tinkering with
> the network settings. I suggest not using those, and instead using the
> command-line tools, as Oliver outlines below.
> 
> >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? 

> >
> >To start with, you need a stanza in /etc/network/interfaces to describe
> >the connection.  It will look something like this:
> >
> >auto eth0
> >iface eth0 inet static
> >        address 192.168.1.18
> >        netmask 255.255.255.0
> >        network 192.168.1.0
> >        broadcast 192.168.1.255
> >        gateway 192.168.1.14
> >


Don't see that at all.  Instead, I see:

# 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



> >The address and gateway addresses and the prefix of network and
> >broadcast will depend on your local setup.  "address" is the address of
> >the machine you are setting up and "gateway" is the machine that is
> >connected to the internet.  If you want to use DHCP to get an address
> >automatically, it will be different - sorry, I haven't got an example
> >here.
> >

Yes I would like to get an address automatically.  Couldn't find a
DHCP file, if there is any.

> >
> For DHCP, the stanza would like like this:
> 
> auto eth0
> iface eth0 inet auto
> 
> >If you have that, try typing
> >
> > ifup eth0
> >
> >
> I would suggest using the Debian init script:
> 
> /etc/init.d/networking restart
> 
> >That may either work or show other errors - see how far you get.
> >
> >Oliver Elphick
> >
> >
> 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.

Reply via email to