Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations biv343 on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

eth1 will not start

Status
Not open for further replies.

axman505

Technical User
Jun 20, 2001
489
US
I recently upgraded to the 2.4.20-20 kernal build for redhat 8, and now i receive the follwoing issue when trying to start eth1:

[root@Alpha devices]# service network restart
Shutting down interface eth0: [ OK ]
Shutting down loopback interface: [ OK ]
Disabling IPv4 packet forwarding: [ OK ]
Setting network parameters: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface eth0: [ OK ]
Bringing up interface eth1: Error for wireless request "Set Encode" (8B2A) :
SET failed on device eth1 ; No such device.
Error for wireless request "Set ESSID" (8B1A) :
SET failed on device eth1 ; No such device.
SIOCGIFFLAGS: No such device
Failed to bring up eth1.
[FAILED]


Somehow it thinkgs its wireless, but its not. Any suggestions??

Thanks
 
take a look in /etc/modules.conf - check that eth1 is loading the correct module.

take a look in /etc/networks/ (i think the files is eth1.conf - it's something similar anyway) this is where the config file for eth1 is kept, check that the data there is correct.

<marc> i wonder what will happen if i press this...[pc][ul][li]please give feedback on what works / what doesn't[/li][li]need some help? how to get a better answer: faq581-3339[/li][/ul]
 
the modules.conf loads the same modeule for both eth0 and eth1. They are the exact same network card. Also, /etc/sysconfig/networking/devices/ has conf files for both eth0 and eth1, they are also both indentical, excpet for the part that says eth0 or eth1.

Any other thoughts?
 
Sorry axman, I'm not a kernel hacker (yet!), thought the conf files would be a good place to start tho.

If no other system config has changed, and you're using identical NICs, I'd suggest you recompile the original kernel and report a kernel bug!

<marc> i wonder what will happen if i press this...[pc][ul][li]please give feedback on what works / what doesn't[/li][li]need some help? how to get a better answer: faq581-3339[/li][/ul]
 
eth0 is 192.168.0.10
eth1 is 192.168.0.200
 
Do you still have the old kernel to boot from? You didn't upgrade your kernel, did you? Red Hat recommends that you never upgrade a kernel RPM package, you should always install the new kernel alongside the old one using rpm -ivh kernel-x.x.x.rpm. That way you can boot into the onld kernel if something goes wrong. Well anyway, if you still have the old kernel laying around, boot off it and let us know if you are still having the same problems with your NICs.


ChrisP
RHCE, LPIC-1, CCNA, CNE, MCSE, +10 others
 
Also, try running kudzu and see if that will fix it.


ChrisP
RHCE, LPIC-1, CCNA, CNE, MCSE, +10 others
 
both kernals have the same problem. The weird thing is that it doesnt always do it. Like right now, its working fine, but if i reboot, there is the chance with will have the error again. It doesnt really make much sense
 
I thought you said that it started after you upgraded your kernel?

Did you try kudzu?

Run lspci and see if the kernel is detecting the cards correctly.



ChrisP
RHCE, LPIC-1, CCNA, CNE, MCSE, +10 others
 
sometime, it can be hardware...have you tried using different pci slot for your network card. if you try this, linux might detect your nic as eth2

Tk.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top