Re: Cannot connect to network now...
On Mon, Nov 22, 2004 at 07:13:59PM -0000, Brian Coiley wrote:
> "Brian Coiley" <bcap@clara.co.uk> wrote in message
> news:33rql-1rI-19@gated-at.bofh.it...
> > 9. After much fiddling around with configuration, managed to get startx
> > to do something using VESA, but just shows a grey screen with a black
> cross
> > in the middle, and entire system is locked up.
Is it really locked up? Try CTRL-ALT-F1 to go to the first text
console. (CTRL-ALT-F7 to go back usually.) Or right click with your
mouse to see if a context menu comes up. I may be wildly off with my
guess here, but it reminds me of a simple window manager. If that's
the case you may want to install kde or gnome to get some more
extensive graphics.
I got a rather empty screen like yours once when I somehow failed to
notice that I had uninstalled kde... ;-)
> OK, here's some more info: considerable rummaging around revealed the
> command "dhclient". Executing this resulted in the somewhat discouraging
> message "Unrecognized Kernel Version" or something like that. More
> rummaging around revealed that dhclient is in fact a script, wrapping 2.0
> and 2.2 versions of the dhclient thingy. No sign of a 2.6 version! Anyway,
> I ran the 2.2 version and guess what? I immediately got a DHCP lease and
> started nattering to the network!
2.0 and 2.2 should be the version numbers of dhclient and have nothing
to do with a kernel version. The error message seems strange. Googling
may possibly give some hints. BTW, on the Debian servers I only see
version 2.0. What does the following command show?
dpkg-query -l dhc* | grep ii
In my case:
ii dhcp-client 2.0pl5-19.1 DHCP Client
> So what's gone wrong? Presumably the 2.6 kernel broke something re DHCP,
> but what, and how do I fix it (other than by doing the above whenever I
> boot)?
I also don't always get a dhcp lease when I boot up. I just have one
computer connected to a DSL router. The router needs some time to
start up. The computer is faster and starts to request a dhcp lease
before the router is fully up and running, so it doesn't work. When
that's the case I have to run the dhclient command manually as
well. Could this be your problem?
--
Maurits van Rees | http://maurits.vanrees.org/ [Dutch/Nederlands]
"Let your advance worrying become advance thinking and planning."
- Winston Churchill
Reply to: