[opensuse-autoinstall] Installation Problems with pxeboot and dhcpcd
Hallo, i get trouble with automatic installation. pxeboot get an ip address by dhcp server and is downloading the linux kernel and initrd. After booting the install kernel the dhcpcd failed because of deactivating the networkcard. The network module is succesfully loaded. If i do installing by dvd and typing in: install=http... and autoyast=http... everything is working well. The installloader get an Ip by dhcp server. The linux kernel and initrd are the same on dvd and in the /tftpboot folder. Please give me some hints. Greeting Georg -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
on Friday 07 August 2009 Georg Wallner wrote:
i get trouble with automatic installation. pxeboot get an ip address by dhcp server and is downloading the linux kernel and initrd. After booting the install kernel the dhcpcd failed because of deactivating the networkcard. The network module is succesfully loaded.
If i do installing by dvd and typing in: install=http... and autoyast=http... everything is working well. The installloader get an Ip by dhcp server.
how is you pxe config for the installation? Do you have "netsetup=0" by accident in it maybe? Try netsetup=1, even though that should not be needed if you have your installation source in the network. -- 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
Hallo, Am Freitag, 7. August 2009 12:30:01 schrieb Uwe Gansert:
on Friday 07 August 2009 Georg Wallner wrote:
i get trouble with automatic installation. pxeboot get an ip address by dhcp server and is downloading the linux kernel and initrd. After booting the install kernel the dhcpcd failed because of deactivating the networkcard. The network module is succesfully loaded.
If i do installing by dvd and typing in: install=http... and autoyast=http... everything is working well. The installloader get an Ip by dhcp server.
how is you pxe config for the installation? Do you have "netsetup=0" by accident in it maybe? Try netsetup=1, even though that should not be needed if you have your installation source in the network.
netsetup=1 doesn't help. The difference is, that the Yast Manual Installation Menu starts immediately. But, even dhcpcd nor manual IP setting works. Ciao, Georg -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
Basic info Which Suse Version ? Which hardware is used ? > even dhcpcd nor manual IP setting works Basic troubleshooting - Do you have more then one network in your server ? - Is the correct network driver loaded ? And is the correct card used ? - Are you able to do a manual installation meaning configuring the network by hand ( Select driver , set IP a.s.o ) After this is sorted out and you can set an IP but the automatic installation still fails: - Do you use a info file ? Thus you might should set something like "netwait: 5:" since some cards needs some time to be configured. I was not able to install a Suse 10.3 on a new DELL machine because the Broadcom Card was named a litte bit different. happy weekend Hajo >-----Original Message----- >From: Georg Wallner [mailto:Georg.Wallner@ead-systeme.de] >Sent: Friday, August 07, 2009 2:35 PM >To: opensuse-autoinstall@opensuse.org >Subject: Re: [opensuse-autoinstall] Installation Problems with pxeboot >and dhcpcd > >Hallo, > >Am Freitag, 7. August 2009 12:30:01 schrieb Uwe Gansert: >> on Friday 07 August 2009 Georg Wallner wrote: >> > i get trouble with automatic installation. >> > pxeboot get an ip address by dhcp server and is downloading the >linux >> > kernel and initrd. After booting the install kernel the dhcpcd >failed >> > because of deactivating the networkcard. The network module is >> > succesfully loaded. >> > >> > If i do installing by dvd and typing in: install=http... and >> > autoyast=http... everything is working well. The installloader get >an Ip >> > by dhcp server. >> >> how is you pxe config for the installation? Do you have "netsetup=0" >by >> accident in it maybe? >> Try netsetup=1, even though that should not be needed if you have your >> installation source in the network. > >netsetup=1 doesn't help. The difference is, that the Yast Manual >Installation >Menu starts immediately. But, even dhcpcd nor manual IP setting works. > >Ciao, Georg > >-- >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
Hallo, Am Freitag, 7. August 2009 15:01:38 schrieb Hans-Joachim Ehlers:
Basic info
Which Suse Version ? SuSE 10.3 32bit Which hardware is used ? Giga-byte RTL 8111/8168B PCI Express Ethernet Controller On Board Realtek Semiconduktor
even dhcpcd nor manual IP setting works
Basic troubleshooting - Do you have more then one network in your server ? No just Onboard, it is activated on pxeboot too. - Is the correct network driver loaded ? Yes, i think so. It is the same driver which is loaded during manual installaiton. And is the correct card used ? Just onboard card. - Are you able to do a manual installation meaning configuring the network by hand ( Select driver , set IP a.s.o ) I can do the autmatic installation, by starting with a start dvd 10.3-32bit. When i get the installation prompt, i write: install=http://192.168.0.1/suse/distribution/10.3/repo/oss autoyast=http://192.168.0.1/autoinstall/workstation-10.3-32bit.xml
After that the automatic installation works well. My /tftpboot/pxelinux.cfg/default configuration line for 10.3-32bit installation looks like following: # Install 32bit OpenSuSE 10.3 Client label ws.10.3-32bit kernel linux-10.3-32 append initrd=initrd-10.3-32 ramdisk_size=65536 vga=0x0317 splash=silent showopts autoyast=http://192.168.0.1/autoinstall/workstation-10.3-32bit.xml install=http://192.168.0.1/suse/distribution/10.3/repo/oss
After this is sorted out and you can set an IP but the automatic installation still fails: - Do you use a info file ? Thus you might should set something like "netwait: 5:" since some cards needs some time to be configured.
I was not able to install a Suse 10.3 on a new DELL machine because the Broadcom Card was named a litte bit different.
What do you mean with "named a little bit different"?
happy weekend Hajo
Happy weekend too Georg -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
... >> Which Suse Version ? >SuSE 10.3 32bit >> Which hardware is used ? >Giga-byte RTL 8111/8168B PCI Express Ethernet Controller >> - Is the correct network driver loaded ? >Yes, i think so. It is the same driver which is loaded during manual >installaiton. Does the driver from the initrd has the same version as the one from the DVD ? ... >> - Are you able to do a manual installation meaning configuring the >> network by hand ( Select driver , set IP a.s.o ) What I was trying to say was: Can you after a failed network installation - YAST simply say it does not find the installation source or what so ever - * Unload any network driver. * Select from yast the correct driver * Load the driver * Configure the network and installation source * Ping the adapter from another machine. With these steps we will simple check whether or not a network driver gets loaded and activated. In case it will work: - Either YAST loads the wrong adapter during initial boot or - you need to set the netwait option on the command line to give the adapter some time to initialize. In case YAST loads the wrong adapter you can supply an "insmod: Mydriver" on the command line as well. NOTE: I do not know the correct syntax for giving "info" file options on the "append" section of the kernel command line. So I use an info file since ages. In case it will not work at all. - Check on the command line during a network installation if ifconfig will show an interface (eth) at all - I think on TTY4 (press F4) is the command line during installation - In case you see a eth device check that the value for in/out trffic is larger then zero . - Test with dhcpcd - Machine can not be pinged from another node on the network but an eth device exist- check for dmesg error on the command line as well. Then I would say that the network driver from the initrd is different or missing then that from the DVD. Thus you have to find out the driver file and version from the initrd on your boot server and compare this information with the version on the DVD AS WELL as from an installed system which has been installed via DVD. In the past I had an issue where I had to update the initrd with another driver. ... >> Broadcom Card was named a litte bit different. >What do you mean with "named a little bit different"? I do not have the details anymore. But basicly the broadcom driver ( I think it was tg3) was loaded during network installation without any error but no eth device got configured due to the fact that the name of the device changed from something like ABC1000x ( PCI-e ) to ABC1000e ( PCI Express ) hth Hajo -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
participants (3)
-
Georg Wallner -
Hans-Joachim Ehlers -
Uwe Gansert