e1000 Problem after Kernel Update
Hi, I have updated my 9.1 with a new Kernel. (2.6.5-7.111-default to 2.6.5-7.151-default). After reebot there was only one Network Interface avaliable. Setting up network interfaces: lo lo IP address: 127.0.0.1/8 doneWaiting for mandatory devices: eth-id-00:e0:81:62:29:19 eth-id-00:e0:81:62:29:1a 19 eth1 device: Intel Corp. 82801BD PRO/100 VE (LOM) Ethernet Controller (rev 82) eth1 configuration: eth-id-00:e0:81:62:29:1a eth1 IP address: 213.203.202.82/24 doneWaiting for mandatory devices: eth-id-00:e0:81:62:29:19 18 17 16 13 12 11 10 9 7 6 5 4 3 2 1 0 eth0 interface could not be set up failedSetting up service network . . . . . . . . . . . . . . . .failed In Yast both Interfaces are avaliable. But originaly eth0 was the RPO/100 Card and the Intel e1000 was eth1. So the routing table is false. Some Applications i.e. Confixx dosent also like that (because of eth0 <-> eth1 change). Can anybody help me. Can I go back to 2.6.5-7.111-default ? Please let me know if you need further Information. Thanks Hans
On Friday 10 June 2005 11:47, Hans Ophüls wrote:
Hi,
I have updated my 9.1 with a new Kernel. (2.6.5-7.111-default to 2.6.5-7.151-default). After reebot there was only one Network Interface avaliable.
And the security question is...? Paul -- Paul Reeves http://www.fleetriver.com
I have updated my 9.1 with a new Kernel. (2.6.5-7.111-default to 2.6.5-7.151-default). After reebot there was only one Network Interface avaliable.
And the security question is...?
Sorry, if this is not the right list to post. But I updated the Kernel for security reasons only. So, in my opinion it is related to security, because the question is should I update or not. Meanwhile I have reproduced this behavior on a second box. Installed Suse 9.1 from CD. Update to 2.6.5-7.151. Result: the eth0 and eth1 are interchanged. Regards, Hans
Meanwhile I have reproduced this behavior on a second box. Installed Suse 9.1 from CD. Update to 2.6.5-7.151. Result: the eth0 and eth1 are interchanged. I made a similar experience: Network cards now are identified by there MAC-Adress, like ifcfg-eth-id-00:0a:e6:e6:8f:fb. Have a look into /etc/sysconfig/network to find the values for your machine. These values should replace eth0/eth1 in /etc/sysconfig/SuSEfirewall2
Hope it helps Enrique
Regards, Hans
-- Dirk Enrique Seiffert CaribeNet S.A. - Cartagena - Colombia www.caribenet.com
Hello, Am Freitag, 10. Juni 2005 21:42 schrieb Dirk Enrique Seiffert:
Result: the eth0 and eth1 are interchanged.
I made a similar experience: Network cards now are identified by there MAC-Adress, like ifcfg-eth-id-00:0a:e6:e6:8f:fb. Have a look into /etc/sysconfig/network to find the values for your machine. These values should replace eth0/eth1 in /etc/sysconfig/SuSEfirewall2
Additionally, you can use a "stable" name. Just add something like PERSISTENT_NAME='cable' to /etc/sysconfig/network/ifconfig-* Please note that you should not use "eth0" or any other existing device name as persistent name - it will make trouble. (However, eth42 should work as long as you don't really have that much network cards.) Regards, Christian Boltz -- Sorry, mit java kenne ich mich gar nicht aus, das ist mir einfach zu unportabel. [Thorsten Kukuk in suse-linux]
participants (5)
-
Christian Boltz -
Dirk Enrique Seiffert -
Hans Ophüls -
Hans Ophüls (hop)
-
Paul Reeves