Patrick Shanahan wrote:
* Peter Breger <[EMAIL PROTECTED]> [02-18-07 09:29]:
... boot.msg has something to say, here is a short summary of what it
has to say on network matters (sorry, cannot actually use file text cut
and paste but have to retype laboriously in this mail on another Windows
PC, [] encloses my own comment)
setting up network interfaces:
lo IP address: 127.0.0.1/8 done
eth0 device: 3Com [and all kinds of bla bla on hardware card]
eth0 configuration: eth-bus-pci-0000:00:0f.0
eth0 (DHCP) . . . . . no IP address yet ... backgrounding.
Warning: could not set up default route via interface.
Command ip route replace to default via 192.168.1.1 returned: .RTNETLINK
answers Network is unreachable
Configuration line. default 192.168.1.1 - -
[then all kinds of other bla bla until it gets back to matter on hand]
eth0 dhcpcd is still waiting for data
waiting
eth0 interface could not be set up until now.
I have similar problems on occasion, my router looses dhcp and my local
network goes down including access outside.
Unplug the power cord from your router for > 2 minutes. Reconnect and
issue as root, rcnetwork restart.
ping an outside connection to check status, ping yahoo.com
Thanks Patrick,
but the router is correctly keeping all other PCs happy on the network,
I cannot interrupt other peoples use of network by fiddling with the
router everytime I switch on my Linux pc . (You just try and boot the
family of the net...Teenage wrath will be unleashed instantaneously on
unsuspecting dad ... ;-) ) It is the boot process on the Linux that is
at fault, being the only process which is not successful. Manual YaST
setup succeeds. (Same as simultaneous use on other computers running
windows does not show any problems at all).
Peter
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
