[opensuse-autoinstall]
hm i can´t belive that the this part is not relevant in stage1. <net-udev config:type="list"> <rule> <rule>ATTR{address}</rule> <value>customermac</value> <name>eth2</name> </rule> <rule> <rule>ATTR{address}</rule> <value>dhcpmac</value> <name>eth0</name> </rule> </net-udev> so i did an installation with and without this part. With this part after stage1 and the reboot the system came up and would begin with stage2, but the error "cannot access installation media" occurs. I could access console and could see the following in boot.msg: eth1 renamed to eth2 by udev eth0 renamed to eth3 by udev with ifconfig i saw the following: eth0 HWaddr dhcpmac eth1 HWaddr othermac eth2 HWaddr dhcpmac eth3 HWaddr othermac So eth0 and eth2 had the same mac? and the interface with my customermac was not present, but it should be eth2. with dhcp-test eth0 i got an ip for eth0 from my dhcpserver, over eth2 not. The /etc/udev/rules.d/70-persistant-net.rules file looked like this: # Generated by autoyast # program run by the persistent-net-generator.rules rules file. # # You can modify it, as long as you keep each rule on a single line. SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="customermac", NAME="eth2" SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="dhcpmac", NAME="eth0" # PCI device 0x8086:0x105e (e1000e) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="ohtermac", ATTR{type}=="1", KERNEL=="eth*", NAME="eth3" # PCI device 0x14e4:0x164c (bnx2) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="ohtermac", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1" Without the net-udev part everything worked, but i had no persistant eth0 and eth2. any ideas? on Monday 18 January 2010 Stefan.Dursch@gmx.de wrote:
These are the relevant parts of my networking section:
this is not relevant in your case. The <networking> configuration happens later. Yast2 ist configuring the network with the data of the XML file in stage2. You don't reach that point currently.
When i boot up via dhcp i get the dhcprequest over eth2, Installation starts, everything looks good, but after first reboot it goes:
so you get a networking config in stage1 but the same config does not work in stage2?
So for second stage i get no network and yast fails with "cannot access installation media" In the logfile i can see save_network.ycp writes befor the reboot a file ifcfg-eth2 like this: BOOTPROTO='dhcp4' LLADDR=dhcpmac STARTMODE='oneboot'
the <networking> section is read from the XML file and configured in the second stage. In your case the installation network can not be started for some reason (it worked in stage1) because the eth2 interface gets no IP address from the dhcp server. Can you see something in the log of the dhcp server? -- ciao, Uwe Gansert Uwe Gansert SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Business: http://www.suse.de/~ug -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org -- GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
Hi, Sorry to step in without thoroughly reading previous posts in this thread (too many letters at once ;-) ) but this caught my eye:
/etc/udev/rules.d/70-persistant-net.rules file looked like this: # Generated by autoyast # program run by the persistent-net-generator.rules rules file. # # You can modify it, as long as you keep each rule on a single line. SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="customermac", NAME="eth2" SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="dhcpmac", NAME="eth0"
# PCI device 0x8086:0x105e (e1000e) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="ohtermac", ^^^^^^^^^ ATTR{type}=="1", KERNEL=="eth*", NAME="eth3"
# PCI device 0x14e4:0x164c (bnx2) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="ohtermac", ^^^^^^^^^ ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"
In case this is not just a copy-paste error - how did such udev rules file get generated? There are two devices which share the same MAC address, living in the same (eth*) namespace - is this intended? fB. -- \\\\\ Katarina Machalkova \\\\\\\__o YaST developer __\\\\\\\'/_ & hedgehog painter
Hi Stefan Just guessing, this might the same issue I had last summer: http://lists.opensuse.org/opensuse-autoinstall/2009-05/msg00018.html http://lists.opensuse.org/opensuse-autoinstall/2009-06/msg00004.html 1) linuxrc dhcp-boots from mac1 as eth2 2) main installation and reboot (called stage1?) 3) udev renames: mac1 from eth2->eth0 / mac2 from eth0->eth2 4) stage2 fails to bring up networking with pre-udev config from stage1, because it tries eth2, which now is mac2, on another vlan 5) yast needs some rpms from the network (and fails) This means step 3) is too early, because stage2 wants the same network configuration as stage1. Half a year later and I still can't explain it any better, sorry ;-) (Opening a Novell bugreport for this is also still on my TODO... *sigh*) Regards, Michael -----Ursprüngliche Nachricht----- Von: Stefan.Dursch@gmx.de [mailto:Stefan.Dursch@gmx.de] Gesendet: Dienstag, 19. Januar 2010 16:52 An: opensuse-autoinstall@opensuse.org Betreff: [opensuse-autoinstall] hm i can´t belive that the this part is not relevant in stage1. <net-udev config:type="list"> <rule> <rule>ATTR{address}</rule> <value>customermac</value> <name>eth2</name> </rule> <rule> <rule>ATTR{address}</rule> <value>dhcpmac</value> <name>eth0</name> </rule> </net-udev> so i did an installation with and without this part. With this part after stage1 and the reboot the system came up and would begin with stage2, but the error "cannot access installation media" occurs. I could access console and could see the following in boot.msg: eth1 renamed to eth2 by udev eth0 renamed to eth3 by udev with ifconfig i saw the following: eth0 HWaddr dhcpmac eth1 HWaddr othermac eth2 HWaddr dhcpmac eth3 HWaddr othermac So eth0 and eth2 had the same mac? and the interface with my customermac was not present, but it should be eth2. with dhcp-test eth0 i got an ip for eth0 from my dhcpserver, over eth2 not. The /etc/udev/rules.d/70-persistant-net.rules file looked like this: # Generated by autoyast # program run by the persistent-net-generator.rules rules file. # # You can modify it, as long as you keep each rule on a single line. SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="customermac", NAME="eth2" SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="dhcpmac", NAME="eth0" # PCI device 0x8086:0x105e (e1000e) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="ohtermac", ATTR{type}=="1", KERNEL=="eth*", NAME="eth3" # PCI device 0x14e4:0x164c (bnx2) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="ohtermac", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1" Without the net-udev part everything worked, but i had no persistant eth0 and eth2. any ideas? on Monday 18 January 2010 Stefan.Dursch@gmx.de wrote:
These are the relevant parts of my networking section:
this is not relevant in your case. The <networking> configuration happens later. Yast2 ist configuring the network with the data of the XML file in stage2. You don't reach that point currently.
When i boot up via dhcp i get the dhcprequest over eth2, Installation starts, everything looks good, but after first reboot it goes:
so you get a networking config in stage1 but the same config does not work in stage2?
So for second stage i get no network and yast fails with "cannot access installation media" In the logfile i can see save_network.ycp writes befor the reboot a file ifcfg-eth2 like this: BOOTPROTO='dhcp4' LLADDR=dhcpmac STARTMODE='oneboot'
the <networking> section is read from the XML file and configured in the second stage. In your case the installation network can not be started for some reason (it worked in stage1) because the eth2 interface gets no IP address from the dhcp server. Can you see something in the log of the dhcp server? -- ciao, Uwe Gansert Uwe Gansert SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Business: http://www.suse.de/~ug -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org -- GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
participants (3)
-
Katarina Machalkova -
Michael.Leu＠mgb.ch -
Stefan.Dursch＠gmx.de