http://bugzilla.novell.com/show_bug.cgi?id=543069
User peters-novell@techwiz.ca added comment
http://bugzilla.novell.com/show_bug.cgi?id=543069#c7
Peter Sjoberg changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|WORKSFORME |
--- Comment #7 from Peter Sjoberg 2009-10-15 12:50:18 MDT ---
Done some more testing and I think the issue is around "manual install". When
PXE booting and having "IPAPPEND 2" it uses the MAC ($BOOTIF) for network
interface when it should use the nic (eth1)
I removed netdevice=bootif (an load_ramdisk which I got from
http://en.opensuse.org/SuSE_install_with_PXE_boot#Building_PXE_boot) and
nothing changed as long as I still have ipappend there
If I remove ipappend it will use the wrong nic and fail (I'm building from
eth1).
I tried to see where it fails and it seems like when I append "rescue" it
doesn't start the network (F9 & "ifconfig -a" shows no nic up)
It's something wrong around the logic on what nic to choose, when I remove
"ipappend 2" it gets confused and ends up starting dhcp on eth0, get an ip and
puts it on eth1 - where it then tries to mount the nfs share and fails since
it's in the wrong network.
On the good news list, I found that there is a difference between "rescue" and
"rescue=1", the later works!
I tested this back and forth a few times and for some reason adding "=1" makes
a difference so even if the rest isn't fixed I can at least boot rescue even
when I don't know what interface I pxe boot from
I do wonder what ways you tried (besides "rescue=1") since just about every way
I tried it fails when I pxe boot from eth1 (eth0 works for most cases)
/ps
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.