I didn't modify rc.config b4, the problem is the system not properly shutdown, then I think some file is corrupt. Anywhere, I try SuSEconfig, and restart, it not help. And also trying rpm --verify -a|tee verify_file it still running at the moment. :( I run /etc/rc.d/init.d/network status, it give me this: eth0: error fetching interface information: Device not found I don't understand about eth0. Is it a file? In the module.conf file, I found a line is # YaST2: Realtek Semiconductor Co., Ltd. RT8029(AS) alias eth0 ne2k-pci Can you tell more about network device driver in linux. Thanks Louis ----- Original Message ----- From: "Mark Gray" <markgray@iago.nac.net> To: "Louis" <louis@allsofts.com> Sent: Monday, July 31, 2000 5:11 PM Subject: Re: [SLE] upgrate to 2.2.16

"Louis" <louis@allsofts.com> writes:

...

Forget to tell you, this error is not because I install new kernel. B4 I install new kernel, these error is already happen.

Ahh! The sequence of events becomes clearer.

...

When bootup, I got this failed msg: Setting up dummy0 deviceSIOCSIFADDR: No such device dummy0: unknown interface: No Such device SIOCSIFNETMASK: No such device dummy0: unknow interface: No such device failed

Setting up network device eth0 SIOCSIFADDR: No such device eth0: unknown interface: No such device SIOCSIFBRDADDR: No such device eth0: unknown interface: No such device SIOCSIFNETMASK: No such device done

It appears that you have a problem with your configuration. Did you set up your network using yast? Do you always remember to run SuSEconfig after you make changes to /etc/rc.config whether by hand or using yast or yast2? (Making a change to /etc/rc.config without rerunning SuSEconfig can seriously upset your system (I found this out the hard way :-) and yast itself does not always remember to do this for you.)

It could also be that you have a clobbered configuration file or startup script that is not executing properly. I would run a:

rpm --verify -vv <package name>

over every package that I suspected, it might even be a good idea to check out how messed up /etc/rc.config might have gotten. Have you been running tripwire in your cron jobs? It would have reported any "suspicious" file changes to you using mail to root if you had.

If this does not quickly isolate what has gone wrong, try a:

rpm --verify -a|tee verify_file

This will verify every package you have installed on your system and the output could be useful to figure out what has gone wrong. (The output will appear on the screen as well as be written to the file verify_file for your later perusal and will take quite a while if you install a lot of packages like I do.

Hope this Helps.

-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq