More dsl0/eth0 woes. Help?
Okay. It's down to this. Can anyone help me please KILL and make stay dead dsl0 foreve leaving my eth0 configuration in peace and harmony? Please?
On Tue, Jul 16, 2002 at 04:52:37PM +0200, Nick Selby wrote:
Okay. It's down to this. Can anyone help me please KILL and make stay dead dsl0 foreve leaving my eth0 configuration in peace and harmony?
Please?
O.K. I'm on slightly shaky ground here, but if you look in /etc/sysconfig/network/ is there a file called ifcfg-dsl0 (or something like that) ? If there is, try renaming it to <your choice> and restart the network. I'm not at all sure about this. F.x. I don't know if one needs to run SuSEconfig after such a change, or if 'rcnetwork restart' is sufficient... In any case, AFAIK everything network related is in that dir since 8.0, so go looking... HTH Jon Clausen
On Tuesday 16 July 2002 16.52, Nick Selby wrote:
Okay. It's down to this. Can anyone help me please KILL and make stay dead dsl0 foreve leaving my eth0 configuration in peace and harmony?
Please?
In SuSE 8.0, all configuration files live in /etc/sysconfig/network/ My guess is that you have a file there ifcfg-dsl0 that you could remove. possibly there is also a provider file in /etc/sysconfig/network/providers/ that you could kill. Just a thought, since I don't have dsl, but that's where I'd look if I were in your shoes. //Anders
On Tuesday 16 July 2002 17:07, Anders Johansson wrote:
In SuSE 8.0, all configuration files live in /etc/sysconfig/network/
Right. I went there and renamed ifcfg-dsl0 .
My guess is that you have a file there ifcfg-dsl0 that you could remove. possibly there is also a provider file in /etc/sysconfig/network/providers/ that you could kill.
Did that. Now I have solved the dsl0 problem but the eth0 STILL fails on network restart AND on a full reboot. I tried deleting the ethernet configuration from Yast and reconfiguring. Nada. So now I guess my only problem is that eth0 FAILS on startup.
On Tuesday 16 July 2002 17.21, Nick Selby wrote:
So now I guess my only problem is that eth0 FAILS on startup.
Do you get any interesting error messages in /var/log/boot.msg or /var/log/messages when you boot? You're running DHCP, right? You could try setting DHCLIENT_DEBUG="yes" in /etc/sysconfig/network/dhcp and see if that generates some more enlightening error messages in /var/log/messages //Anders
On Tuesday 16 July 2002 17:30, Anders Johansson wrote:
On Tuesday 16 July 2002 17.21, Nick Selby wrote:
So now I guess my only problem is that eth0 FAILS on startup.
Do you get any interesting error messages in /var/log/boot.msg or /var/log/messages when you boot?
Only this: <notice>/etc/init.d/rc5.d/S05network start Setting up network interfaces: lo done eth0 failed Starting syslog services<notice>'/etc/init.d/rc5.d/S05network start' exits with status 0 <notice>/etc/init.d/rc5.d/S06syslog start <notice>startproc: execve (/sbin/syslogd) [ /sbin/syslogd ], [ PWD=/ HOSTNAME=linux CONSOLE=/dev/console PREVLEVEL=N AUTOBOOT=YES REDIRECT=/dev/tty1 MACHTYPE=i386-suse-linux LINES=34 SHLVL=2 COLUMNS=105 BOOT_IMAGE=linux SHELL=/bin/bash HOSTTYPE=i386 OSTYPE=linux HOME=/ TERM=linux PATH=/sbin:/bin:/usr/sbin:/usr/bin RUNLEVEL=5 INIT_VERSION=sysvinit-2.82 _=/sbin/startproc DAEMON=/sbin/syslogd ] <notice>startproc: execve (/sbin/klogd) [ /sbin/klogd -c 1 ], [ PWD=/ HOSTNAME=linux CONSOLE=/dev/console PREVLEVEL=N AUTOBOOT=YES REDIRECT=/dev/tty1 MACHTYPE=i386-suse-linux LINES=34 SHLVL=2 COLUMNS=105 BOOT_IMAGE=linux SHELL=/bin/bash HOSTTYPE=i386 OSTYPE=linux HOME=/ TERM=linux PATH=/sbin:/bin:/usr/sbin:/usr/bin RUNLEVEL=5 INIT_VERSION=sysvinit-2.82 _=/sbin/startproc DAEMON=/sbin/klogd ] done
You're running DHCP, right? You could try setting DHCLIENT_DEBUG="yes" in /etc/sysconfig/network/dhcp and see if that generates some more enlightening error messages in /var/log/messages
Did that and nothing particularly enlightening showed up there on a reboot. Thanks, Anders, nick
participants (3)
-
Anders Johansson
-
Jon Clausen
-
Nick Selby