December 2004 - openSUSE Autoinstall - openSUSE Mailing Lists

PXE config line limited to 256 chars
by Hao Luo 09 Dec '04

09 Dec '04

Hi, all This is my pxe config file: DEFAULT test LABEL test KERNEL test/yast-SLES8.1-GA-i386z APPEND load_ramdisk=1 initrd=csm/yast-SLES8.1-GA-i386.gz ramdisk_size=65536 autoyast=nfs://172.20.3.2//netinstall/csm/1.4.1 /autoyast.SLES8.1/172.20.3.25.xml install=nfs://172.20.3.2 /netinstall/Linux/SLES/8.1/i386/GA/ ip=172.20.3.25 netmask=255.255.255.0 acpi=oldboot netdevice=eth0 As I know, pxe cmd line passed to autoyast will be cut by kernel to no more than 256 chars, but last line in my config file is far more than 256 chars, how can I pass the line to autoyast without being cut? Info file is not exactly what I want because I have to prepare different initrd for different machine. Yours Sincerely, Luo Hao IBM China Software Development Laboratory Tel:86-10-82782244-3420 Mail:luohao@cn.ibm.com Address: North Area, 8/F, Ying Chuang Building No.1, East Road, Shangdi, Haidian District Beijing 100085, PRC

3 3

PXE install?
by Steve Glines 09 Dec '04

09 Dec '04

Has anyone successfully performed a PXE install of SLES9 on a system with SCSI disks? The lab I'm building works flawlessly with IDE disks but fails when I use SCSI disks. In the logs it says: modprobe -s -k scsi_hostadapter fail=2 when I run the command alone I get needs modprobe.old. Is there anyone with a clue here? Cheers -- Steve Glines voice: 978-952-6340 www.is-cs.com fax: 978-952-8524 145 Foster Street cell: 617-549-7274 Littleton MA 01460 I'm a complex person. I have a real and an imaginary part.

3 4

Cannot find installation server
by Clormann, Stefanie 09 Dec '04

09 Dec '04

Hello, I am try ing to install SLES9 via a http installation server via port 8080. But yast ist simply ignoring the port. My isolinux.cfg has the following entry: label workstation kernel linux append initrd=initrd AutoYaST=http://192.168.12.1:8080/profile/autoinst.xml UseDHCP=1 Install=http://192.168.12.2:8080/autoyast/sles9-i386/CD1/ What am I missing? I am using the original boot cd that comes with sles9. (First CD.)

1 0

custom kernel selection
by Brian Corriveau 09 Dec '04

09 Dec '04

One more question for today: I am trying to use the <kernel>my-kernel</kernel> (I've also tried just kernel like the package name) in my control file in the software part. When running auto installation I can see the kernel rpm being installed, but at the end I am informed that the kernel package failed to install and then it has trouble installing the bootloader correctly. Here is what I get when I create_packages. Is there someting missing here that I need to add or add to my kernel rpm spec file to make this work? ##---------------------------------------- =Pkg: kernel 2.4.21_Z_01_01 6 x86_64 +Req: /bin/sh -Req: +Prq: /bin/sh -Prq: +Prv: /boot/vmlinuz.boot my-kernel kernel-2.4.21_Z_01_01 -Prv: =Grp: System Environment/Kernel =Lic: GPL =Src: kernel 2.4.21_Z_01_01 6 src =Tim: 1099525554 =Loc: 1 kernel-2.4.21_Z_01_01-6.x86_64.rpm =Siz: 3079829 7714275 ##---------------------------------------- thanks Brian

2 1

Re: [suse-autoinstall] PXE install?
by Steve Glines 09 Dec '04

09 Dec '04

I don't think dhcp is the problem because I can load both Red Hat and Debian just fine this way. The Red hat kernel and initrd is a little bigger than Suse's and they are being fed off the same server. Since Suse never sees the disks at all I'm not sure what you mean by the /dev's. When Red hat boots it sees /dev/cciss/c?d? if that's what you mean. SG Marcin Kurc wrote: > I have installed many DL{360,380,...} g2 and g3, all of them worked > just fine. You might have to adjust your dhcp timeout, since it takes > a while for the NIC to initialize. Also, I assume you are using > /dev/cciss/c?d? device and not /dev/sd? > > -marcin > > > >>>> Steve Glines <sglines(a)is-cs.com> 12/08/04 3:39 pm >>> > > J.H.M. Dassen (Ray) wrote: > > >> On Wed, Dec 08, 2004 at 13:05:35 -0500, Steve Glines wrote: >> >> >>> Has anyone successfully performed a PXE install of SLES9 on a >>> system with SCSI disks? >>> >>> The lab I'm building works flawlessly with IDE disks but fails >>> when I use SCSI disks. >> >> >> It seems quite unlikely that the problem you're having is actually > > related > >> to PXE as such. You may want to test with a manual install first, >> debug > > that > >> and then base your PXE setup on those experiences. >> >> If it turns out that your SCSI controller or your SCSI disks aren't >> detected, try booting with the following kernel parameter: >> acpi=oldboot (see >> http://support.novell.com/cgi-bin/search/searchtid.cgi?/en/2004/08/wessels_… >> > > >> for more information). >> >> HTH, > > > Thanks - I would never have thought of that. I'll try it. > > For the record the target install is on a standard production HP > ProLiant system (indeed the lab is at HP). Booting from a CD works > just fine but when I do a PXE boot it can't find any disks. Using the > exact same PXE install with an old Pavilion with IDE disks works just > fine. > > I'll report any success or failure. > > SG > > -- Steve Glines voice: 978-952-6340 www.is-cs.com fax: 978-952-8524 145 Foster Street cell: 617-549-7274 Littleton MA 01460 I'm a complex person. I have a real and an imaginary part.

1 0

Re: [suse-autoinstall] PXE install?
by Marcin Kurc 09 Dec '04

09 Dec '04

I have installed many DL{360,380,...} g2 and g3, all of them worked just fine. You might have to adjust your dhcp timeout, since it takes a while for the NIC to initialize. Also, I assume you are using /dev/cciss/c?d? device and not /dev/sd? -marcin >>>Steve Glines <sglines(a)is-cs.com> 12/08/04 3:39 pm >>> J.H.M. Dassen (Ray) wrote: >On Wed, Dec 08, 2004 at 13:05:35 -0500, Steve Glines wrote: > >>Has anyone successfully performed a PXE install of SLES9 on a system >>with SCSI disks? >> >>The lab I'm building works flawlessly with IDE disks but fails when I >>use SCSI disks. > > >It seems quite unlikely that the problem you're having is actually related >to PXE as such. You may want to test with a manual install first, debug that >and then base your PXE setup on those experiences. > >If it turns out that your SCSI controller or your SCSI disks aren't >detected, try booting with the following kernel parameter: >acpi=oldboot >(see >http://support.novell.com/cgi-bin/search/searchtid.cgi?/en/2004/08/wessels_… >for more information). > >HTH, Thanks - I would never have thought of that. I'll try it. For the record the target install is on a standard production HP ProLiant system (indeed the lab is at HP). Booting from a CD works just fine but when I do a PXE boot it can't find any disks. Using the exact same PXE install with an old Pavilion with IDE disks works just fine. I'll report any success or failure. SG -- Steve Glines voice: 978-952-6340 www.is-cs.com fax: 978-952-8524 145 Foster Street cell: 617-549-7274 Littleton MA 01460 I'm a complex person. I have a real and an imaginary part. -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Turn off IPv6 at install-time?
by Johannes Klug 08 Dec '04

08 Dec '04

Hello! Is it possible to turn ipv6 completely off at install-time? TIA, Johannes Klug

1 0

Re: [suse-autoinstall] PXE install fails with SCSI disks
by Steve Glines 07 Dec '04

07 Dec '04

Hi Anas, Thanks for the help. I've made all the fixes you and Marcin Kurc suggested but the system still refuses to see the scsi disks. Here is the data. The target system is an HP Proliant ML350 G3 with a single 40GB SCSI disk. The script shown in sles9/CD1/docu/RELEASE-NOTES.en.html doesn't work so I've modified it thus (feel free to reuse it): #From the top directory umask 0 mkdir -p sles9/CD1 # now copy the contents of SLES CD1 into this directory echo "Mount CD1" read x mount /dev/cdrom sleep 10 cp -r /cdrom/* sles9/CD1 eject mkdir -p core9/CD1 # now copy the contents of SLES CD2 into this directory echo "Mount CD2" read x sleep 10 mount /dev/cdrom cp -r /cdrom/* core9/CD1 eject mkdir -p core9/CD2 # now copy the contents of SLES CD3 into this directory echo "Mount CD3" read x sleep 10 mount /dev/cdrom cp -r /cdrom/* core9/CD2 eject mkdir -p core9/CD3 # now copy the contents of SLES CD4 into this directory echo "Mount CD4" read x sleep 10 mount /dev/cdrom cp -r /cdrom/* core9/CD3 eject mkdir -p core9/CD4 now copy the contents of SLES CD5 into this directory echo "Mount CD5" read x sleep 10 mount /dev/cdrom cp -r /cdrom/* core9/CD4 eject mkdir -p core9/CD5 now copy the contents of SLES CD6 into this directory echo "Mount CD6" read x sleep 10 mount /dev/cdrom cp -r /cdrom/* core9/CD5 eject ln -s sles9/CD1/boot boot ln -s sles9/CD1/content content ln -s sles9/CD1/control.xml control.xml ln -s sles9/CD1/media.1 media.1 mkdir -p yast echo "/sles9/CD1 /sles9/CD1 /core9/CD1 /core9/CD1" > yast/instorder echo "/sles9/CD1 /sles9/CD1 /core9/CD1 /core9/CD1" > yast/order --------------------------------- After PXE booting the system stalls when it can't find a hard disk. When I look in /var/log/boot.log I find: kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter errorno=2 If I run "/sbin/modprobe -s -k scsi_hostadapter" directly from a shell I get "Kernel requires old modprobe no /sbin/modprobe.old." ------------------------------------------- Here is the current line from my default file: label suse kernel suse.kernel append initrd=suse.root ramdisk_size=65536 \ install=http://10.0.3.11/suse ---------------------------------------------- Here is the output of "find . -type d": . ./sles9 ./sles9/CD1 ./sles9/CD1/SLES-LICENSE ./sles9/CD1/SLES-LICENSE/cz ./sles9/CD1/SLES-LICENSE/de ./sles9/CD1/SLES-LICENSE/en_US ./sles9/CD1/SLES-LICENSE/es ./sles9/CD1/SLES-LICENSE/fr ./sles9/CD1/SLES-LICENSE/it ./sles9/CD1/SLES-LICENSE/nl ./sles9/CD1/SLES-LICENSE/pl ./sles9/CD1/SLES-LICENSE/pt_BR ./sles9/CD1/boot ./sles9/CD1/boot/loader ./sles9/CD1/docu ./sles9/CD1/docu/de ./sles9/CD1/docu/en ./sles9/CD1/docu/es ./sles9/CD1/docu/fr ./sles9/CD1/docu/HOWTOs ./sles9/CD1/docu/it ./sles9/CD1/docu/ja ./sles9/CD1/docu/ko ./sles9/CD1/docu/pt_BR ./sles9/CD1/docu/zh_CN ./sles9/CD1/dosutils ./sles9/CD1/dosutils/dparam ./sles9/CD1/dosutils/ext2tool ./sles9/CD1/dosutils/ext2tool/ext2fs ./sles9/CD1/dosutils/ext2tool/linux ./sles9/CD1/dosutils/ext2tool/src ./sles9/CD1/dosutils/ext2tool/sys ./sles9/CD1/dosutils/fips ./sles9/CD1/dosutils/fips/fips15 ./sles9/CD1/dosutils/fips/fips15/restorrb ./sles9/CD1/dosutils/fips/fips15/source ./sles9/CD1/dosutils/fips/fips20 ./sles9/CD1/dosutils/fips/fips20/restorrb ./sles9/CD1/dosutils/fips/fips20/source ./sles9/CD1/dosutils/gtar109 ./sles9/CD1/dosutils/gzip ./sles9/CD1/dosutils/install ./sles9/CD1/dosutils/lfn ./sles9/CD1/dosutils/loadlin ./sles9/CD1/dosutils/loadlin/doc ./sles9/CD1/dosutils/loadlin/src ./sles9/CD1/dosutils/ltools ./sles9/CD1/dosutils/pkunzip ./sles9/CD1/dosutils/putty ./sles9/CD1/dosutils/rawrite ./sles9/CD1/dosutils/rawwritewin ./sles9/CD1/dosutils/tightvnc ./sles9/CD1/dosutils/untgz ./sles9/CD1/dosutils/weirdx ./sles9/CD1/dosutils/weirdx/config ./sles9/CD1/dosutils/xfs186 ./sles9/CD1/dosutils/xfs32-11 ./sles9/CD1/dosutils/zipzp715 ./sles9/CD1/media.1 ./sles9/CD1/suse ./sles9/CD1/suse/i586 ./sles9/CD1/suse/noarch ./sles9/CD1/suse/nosrc ./sles9/CD1/suse/setup ./sles9/CD1/suse/setup/descr ./sles9/CD1/suse/src ./sles9/CD1/yast ./sles9/CD1/yast/core9 ./sles9/CD1/yast/core9/media.1 ./sles9/CD1/yast/core9/suse ./sles9/CD1/yast/core9/suse/setup ./sles9/CD1/yast/core9/suse/setup/descr ./core9 ./core9/CD1 ./core9/CD1/media.1 ./core9/CD1/suse ./core9/CD1/suse/i586 ./core9/CD1/suse/i686 ./core9/CD1/suse/noarch ./core9/CD1/suse/setup ./core9/CD1/suse/setup/descr ./core9/CD2 ./core9/CD2/media.2 ./core9/CD2/suse ./core9/CD2/suse/i586 ./core9/CD2/suse/i686 ./core9/CD2/suse/noarch ./core9/CD3 ./core9/CD3/media.3 ./core9/CD3/suse ./core9/CD3/suse/i586 ./core9/CD3/suse/i686 ./core9/CD3/suse/noarch ./core9/CD3/suse/src ./core9/CD4 ./core9/CD4/media.4 ./core9/CD4/suse ./core9/CD4/suse/nosrc ./core9/CD4/suse/src ./core9/CD5 ./core9/CD5/media.5 ./core9/CD5/suse ./core9/CD5/suse/nosrc ./core9/CD5/suse/src ./yast Marcin Kurc wrote: > > for graphical install you can say 'textmode=0' after 'install*' > please send me your 'default' file and output of 'find . -type d' in the > suse top directory > > > > thanks, > > Marcin Kurc > Linux Impact Team > Novell, Inc > > (973) 493-6235 > >>>>Steve Glines <sglines(a)is-cs.com> 09/01/04 3:37 pm >>> > Thanks - I missed that one and was following the instructions that came > with SUSE 9.1 Pro. It still boots into the non-X format via PXE and X > when I do a CDROM install. Is there a way to make it boot into Graphics > mode. The lab I'm building is supposed to simulate the experience of > installing via CDROM. By the way this is going to go into HP's main > learning lab. The Red Hat version is being used 30-50 times a day. > > Now I'm getting "Network error 404 not found." > > Cheers > Steve > > Marcin Kurc wrote: > >> >>it is not a problem with PXE, your installation tree is not configured >>correctly >>You should either use SLES9 system to build the tree or configure it >>according to the docu/RELEASE-NOTES.en.html which can be found on cd #1 >> >>Also, you need to point you install to top dir not CD1 i.e. >>'install=_/http://10.0.3.11/suse/_' >> >> >> >>thanks, >> >>Marcin Kurc >>Linux Impact Team >>Novell, Inc >> >>(973) 493-6235 >> >>>>>Steve Glines <sglines(a)is-cs.com> 09/01/04 2:30 pm >>> >>I’m building a PXE install lab for SUSE and other flavors of Linux. >> >>The DHCP and tftp servers are working. Note: I can fully install Red Hat >>from this lab but SUSE (SLES9 rc5) shows the following symptoms: >> >>1.a cdrom install on the target system runs to completion in graphics >>mode. System is an HP PC with SCSI disk. >>2.PXE install runs in non X-window mode (text) and fails to load scsi >>controllers – cannot find any disks. Fails even when modules are >>manually added. >> >>Here is the content of /tftpboot/pxelinux.cfg/default: >> >>default suse >>prompt 1 >>display boot.msg >>timeout 200 >> >>label redhat >> kernel redhat.kernel >> append initrd=redhat.root ramdisk_size=65536 >> >>label suse >> kernel suse.kernel >> append initrd=suse.root ramdisk_size=65536\ >>install=http://10.0.3.11/suse/CD1/ >> >>The file suse.kernel was copied from /boot/loader/linux in CD1 while >>suse.root was taken from /boot/loader/initrd in the same CD. >> >>I copied the contents of each CD into their own directories – I have CD1 >> – CD6 in the directory specified by http://10.0.3.11/suse/CD[1-6]. >> >>My test target system is a Celeron with 256MB Ram and an IDE disk; this >>setup fully installs SLES9. The only material change from this to the >>production lab is that the target system in the production lab has a >>SCSI disk and 1GB of ram. -- Steve Glines voice: 978-952-6340 www.is-cs.com fax: 978-952-8524 145 Foster Street cell: 617-549-7274 Littleton MA 01460 I'm a complex person. I have a real and an imaginary part.

3 6

Custom Package Selection
by Brian Corriveau 07 Dec '04

07 Dec '04

Hi, I'm trying to load a target with a customized minimal set of packages. I followed the instructions on Config and Installation Options 5.2 but I get to the Configure Software Selections part and a window pops up saying "Cannot set base selection", and when I ok that I get "Error while configuring software selections". I'm suspicious of the examples 4.20 and 4.21 because it seems like the =Sel should be 'My' and the category should be Base-System and not addon in order to be picked up in 4.21 by the <base>My</base>. I've tried the examples and variations and I always get the same errors. Here's what it looks like <software> <addons config:type="list"> <addon>Base-System</addon> <addon>YaST2</addon> </addons> <base>My</base> </software> If I replace My with Minimal it works fine. What am I missing? Is there some way to know in greater detail what is going wrong? The My.sel has a large list of packages from a previous inhouse installation. Could that be interacting in a bad way so that I would see the errors I'm getting? Maybe I need to cull out any overlap between My and Base-System? One more easy one, how do I select a valid =Ord value for my Selection? Thanks a lot, Brian

2 5

RE: [suse-autoinstall] has anyone been able to use AutoYast with PXE boot on a tg3 based machine?
by Benjamin Shi 07 Dec '04

07 Dec '04

Try pxe boot with pxelinux.0, we have bcm5700 on tyan working with autoyast just fine. -----Original Message----- From: Joe Landman [mailto:landman@scalableinformatics.com] Sent: Saturday, December 04, 2004 12:01 PM To: 'suse-autoinstall(a)suse.com' Subject: [suse-autoinstall] has anyone been able to use AutoYast with PXE boot on a tg3 based machine? Hi folks: Not directly autoyast, but one of the supporting utils ... My machines have Broadcom chips that map into the tg3 driver. I set up autoyast as per the howto posted here recently (thanks!), and tried the boot. It probes for an RTL8139 and hangs. They units are Tyan S2882 based, and work fine when booting by DVD. From what I read, the issue are the drivers compiled into grub (pxegrub to be precise). Has anyone a working rpm or build of grub with the relevant patches, or a pointer to them? This is on a SuSE 9.2 AMD64 unit. Thanks! Joe -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1