Carl-Daniel Hailfinger <c-d.hailfinger.devel.20 To: opensuse@opensuse.org 05@gmx.net> cc: Subject: Re: [opensuse] RC1 reordering nics 09/09/2005 09:07 AM Please respond to opensuse Hi, meister@netz00.com schrieb:
I managed to install RC1, but after the installation my nics have the wrong order. At install time, I did a FTP install, the order was correct. At boot time the order _is_ correct, the kernel loads the modules in the right order and they are named correct. But if the network comes up SuSE reorders the nics! Where is this information stored? Any hints? Oh, and I want this to be added to the most anoying bugs!
#Define "wrong order". What is the first nic? Simply give each of them #a PERSISTENT_NAME like "wlan" and "wired" or something like that. #The kernel decides which nic gets which eth* name and that depends #on pci bus ordering and modprobe ordering, among other things. #Regards, #Carl-Daniel If I am using yast would the PERSISTENT_NAME be the field "Module Name"? Uriel --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org The information contained in this e-mail message is intended only for the personal and confidential use of the recipient(s) named above. This message may be an attorney-client communication and/or work product and as such is privileged and confidential. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Uriel_Carrasquilla@ncci.com wrote:
meister@netz00.com schrieb: ...
Define "wrong order". What is the first nic? Simply give each of them a PERSISTENT_NAME like "wlan" and "wired" or something like that. The kernel decides which nic gets which eth* name and that depends on pci bus ordering and modprobe ordering, among other things.
If I am using yast would the PERSISTENT_NAME be the field "Module Name"?
No, that's to force the driver to use for that NIC. ("module" = "linux kernel driver", more or less ;)) PERSISTENT_NAME is a variable to put into the ifcfg file for the interface, in /etc/sysconfig/network/ifcfg-eth0.... (for example) As an example, here's the content of my /etc/sysconfig/network/ifcfg-eth-id-00:04:23:a7:bf:f4 (that weird number is the hardware identifier of the NIC (i.e. the MAC address)) - --->8---snip---------------------------------- BOOTPROTO='dhcp' MTU='' NAME='Intel PRO/1000 MT Server Adapter' REMOTE_IPADDR='' STARTMODE='auto' UNIQUE='rBUF.zpcgp5it344' USERCONTROL='no' _nm_name='bus-pci-0000:01:08.0' - --->8---snip---------------------------------- Just add PERSISTENT_NAME in there with your favourite text editor, like this: - --->8---snip---------------------------------- BOOTPROTO='dhcp' MTU='' NAME='Intel PRO/1000 MT Server Adapter' REMOTE_IPADDR='' STARTMODE='auto' UNIQUE='rBUF.zpcgp5it344' USERCONTROL='no' _nm_name='bus-pci-0000:01:08.0' PERSISTENT_NAME="wired" - --->8---snip---------------------------------- PS: omg, is this lotus notes that fscks up your mails to an almost unreadable point ? ;) cheers - -- -o) Pascal Bleser http://linux01.gwdg.de/~pbleser/ /\\ <pascal.bleser@skynet.be> <guru@unixtech.be> _\_v ===> FOSDEM 2006 -- February 2006 in Brussels <=== -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFDIZr+r3NMWliFcXcRAu8YAJwPoChBImqipHYYMLIPiZ39v7FIKwCeJXj7 IQtYXJbdCoCXeRkjhcSnA+k= =6dJd -----END PGP SIGNATURE-----
participants (2)
-
Pascal Bleser
-
Uriel_Carrasquilla@ncci.com