July 2004 - openSUSE Autoinstall - openSUSE Mailing Lists

AY on SuSE 9.1: only textmode
by Frank Steiner 13 Jul '04

13 Jul '04

Hi, I'm trying to start autoyast via pxe. To do so, I just took over the config that worked for SuSE 9.0, but for SuSE 9.1, yast will always start in textmode only when kernel and initrd are loaded over net. This is even for the very basic process when I don't invoke autoyast at all. I.e., I use pxelinux.cfg: label linux kernel linux append initrd=initrd and use the linux and the initrd file from the SuSE 9.1 DVD from boot/loader/ Then after loading the ramdisk, yast2 starts, I see the graphical interface for second, then it is gone. After a while the textmode yast2 comes up, and on Ctrl-Alt-F8 I see a warning from X: Server is already active for display 0 and the usual X stuff around. y2start.log just tells me that X didn't start. However, when I boot from the DVD, yast2 comes up in graphics mode. So the textmode just seems to be fored when booting the kernel and the initrd via PXE. Any hints?? Has anyone seen a similar effect? With SuSE 9.0 there was no problem! cu, Frank -- Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/ Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/ LMU, Amalienstr. 17 Phone: +49 89 2180-4049 80333 Muenchen, Germany Fax: +49 89 2180-99-4049

1 0

Problems with a custom Autoinstall
by Kevin Stallard 12 Jul '04

12 Jul '04

I'm working from 9.1 Professional. I'm attempting to create a custom, autoinstalling CD that will be used to install my distribution on multiple machines. The control file parses without any problems, and the disks are partitioned correctly, but when I get to the software installation step, I hit a snag. I get the message "Could not set base selection "swos"" When I reach the software installation portion of the install. my autoinst.xml file (root of the CD) contains the following information from the software install section. " <software> <base>swos</base> </software> " in suse/setup/descr , I have swos.sel listen in both directory.yast and selections. swos.sel: # SuSE-Linux-Package-Selection 3.0 -- (c) 2002 SuSE Linux AG # generated on Wed Apr 7 13:41:25 UTC 2004 =Ver: 3.0 =Sel: swos =Sum: Base swos System =Cat: base =Vis: true =Ord: 01 +Ins: <my list of software packages to install (including base system) -Ins: I'm guessing that the autoinst.xml file is being read since the disk partitions are set up properly, but I don't know what I'm missing in this step. Any help you can provide would be gratefully appreciated. -K -- Kevin Stallard <kstallard(a)lancope.com>

1 0

Hardware clock and UTC/localtime
by Wenk, Moritz 12 Jul '04

12 Jul '04

Hello, what is the keyword to tell autoyast that the hardware clock is set to local time? "localtime" does not work for me any more with SuSE 9.0 (worked for SLES 8)... <general> <clock> <hwclock>localtime</hwclock> <timezone>US/Eastern</timezone> </clock> Regards, i. A. Moritz Wenk Software Developer Produkt Management International PLATINUM Server MAXDATA Computer GmbH & Co. KG Elbestraße 12 - 16 D-45768 Marl Telefon: +49 2365 952-2715 Telefax: +49 2365 952-2279 http://www.maxdata.com

2 1

autoyast, SuSE 9.0 and 3Ware SATA controller
by Wenk, Moritz 12 Jul '04

12 Jul '04

Hello, I want to install SuSE 9.0 with autoyast on a system with a 3Ware SATA-Controller (8506). The RAID-Disk shown by the 3ware controller is already partitioned when autoyast takes control and the partitons should be kept by autoyast. Here is the problem: when yast starts and scans the partiton table, it shows an error message saying that parted could not read the partition table. (on the console, parted can read and print the partition table...) The error message does not go away although the autoyast xml file contains <report> <errors> <log config:type="boolean" >true</log> <show config:type="boolean" >false</show> <timeout config:type="integer" >20</timeout> </errors> <messages> <log config:type="boolean" >true</log> <show config:type="boolean" >false</show> <timeout config:type="integer" >20</timeout> </messages> <warnings> <log config:type="boolean" >true</log> <show config:type="boolean" >false</show> <timeout config:type="integer" >20</timeout> </warnings> </report> After clicking away the error message autoyast continues without any more errors. The problem seems to be fixed in SuSE 9.1. The problem does only to occur in context with the 3ware controller. Is it possible to suppress the error message? Regards, i. A. Moritz Wenk Software Developer Produkt Management International PLATINUM Server MAXDATA Computer GmbH & Co. KG Elbestraße 12 - 16 D-45768 Marl Telefon: +49 2365 952-2715 Telefax: +49 2365 952-2279 http://www.maxdata.com

1 0

compiling a ycp file to create a ybc executable
by Dustin Nielson 12 Jul '04

12 Jul '04

What is the process for creating a ybc executable from a ycp script file?

2 1

what options to use with mkcramfs to create root
by Dustin Nielson 10 Jul '04

10 Jul '04

What is the recommended version of mkcramfs to use and what syntax would be recommended to create a new root file?

1 0

Additional rpm packages are not found on media? (error 11283)
by Stephan A. Rickauer 08 Jul '04

08 Jul '04

Hi there, the last two days I was busy with searching the solution for the following problem. Generally spoken, it looks like I AM the problem, but see yourself (it is really straight forward): I use autoyast2 (SuSE 9.1) to autoinstall a client successfully via http by handing the following boot arguments over to grub (one line): autoyast=http://myServerIP/path_to_xml/file.xml install=http://myServerIP/suse-9.1 As I said, everything works fine (from booting up, via getting an IP, until the kde logon screen appears). Great. => BUT: Now I wanted to add my own rpms that are neither part of the standard suse installation nor an update to existing ones. So I added the following lines to my xml control file, within the "software" section: <packages config:type="list"> <package>apt</package> <package>apt-libs</package> </packages> Fine, Autoyast also shows "2" additional packages ... Of course I copied both rpms to suse/noarch/ and recreated the package database by saying: create_package_descr -d /myPath/suse \ -l english \ -x /myPath/suse/setup/descr/EXTRA_PROV \ -o /myPath/suse/setup/descr A quick look at /myPath/suse/setup/descr/packages shows that my additional packages are listed there. Great. But now, during client's software installation, exactly these two (mine) packages are not found: "Package 'blabla' was not found on the medium. Error: 11283". Obviously, I did something wrong or missed a crucial step. As I said, I did not find any information by googling around nor did I find help in the documentation. The rpms are there, the package db is up to date ... what else could it be? May someone enlighten me. -- Stephan A. Rickauer ---------------------------- Institut für Neuroinformatik IT-Koordinator Universität / ETH Zürich Winterthurerstr. 190 CH-8057 Zürich Tel: +41 1 635 30 50 Sek: +41 1 635 30 52 Fax: +41 1 635 30 53 http://www.ini.unizh.ch

2 1

RE: [suse-autoinstall] sles8 sp3 LILO confirmation dialog - need unattended install
by Thorson, Jon (TLR Corp) 07 Jul '04

07 Jul '04

This works perfectly. Thank you very much! -j > -----Original Message----- > From: Anas Nashif [mailto:nashif@suse.de] > Sent: Wednesday, July 07, 2004 11:34 AM > To: Thorson, Jon (TLR Corp) > Cc: suse-autoinstall(a)suse.com > Subject: Re: [suse-autoinstall] sles8 sp3 LILO confirmation > dialog - need unattended install > > > Does adding this help? > > <report> > <errors> > <log config:type="boolean">true</log> > <show config:type="boolean">true</show> > <timeout config:type="integer">0</timeout> > </errors> > <messages> > <log config:type="boolean">true</log> > <show config:type="boolean">false</show> > <timeout config:type="integer">0</timeout> > </messages> > <warnings> > <log config:type="boolean">true</log> > <show config:type="boolean">true</show> > <timeout config:type="integer">0</timeout> > </warnings> > </report> > > If no, please send me you control file you use for installation. > > > anas > > > Thorson, Jon (TLR Corp) wrote: > > I'm trying to do a new of install sles8 sp3 via autoyast. > My drives > > are configured for LVM which means I'll have to use LILO as the > > bootloader. Everything installs fine, except after the > bootloader is > > installed, I get a dialog box telling me that the LILO > sector has been > > written and that I can revert using some nifty option from > the command > > line. That's all well and good, but it sits there waiting > for me to > > hit enter. > > > > I've gone through the mail list archives trying to find away to get > > rid of this dialog box. I saw references to a newer > driverupdate than > > what SP3 has so I installed that, but still get the dialog > box. There > > was also mention of a workaround being documented in an FAQ > somewhere, > > but I didn't see anything in the autoinstall FAQ. > > > > Unattended installation is mandatory for the project I'm > working on, > > so this dialog box is quickly becoming the bane of my existence. > > > > Any help would be appreciated. > > > > Thanks. > > > > -j > > >

1 0

sles8 sp3 LILO confirmation dialog - need unattended install
by Thorson, Jon (TLR Corp) 07 Jul '04

07 Jul '04

I'm trying to do a new of install sles8 sp3 via autoyast. My drives are configured for LVM which means I'll have to use LILO as the bootloader. Everything installs fine, except after the bootloader is installed, I get a dialog box telling me that the LILO sector has been written and that I can revert using some nifty option from the command line. That's all well and good, but it sits there waiting for me to hit enter. I've gone through the mail list archives trying to find away to get rid of this dialog box. I saw references to a newer driverupdate than what SP3 has so I installed that, but still get the dialog box. There was also mention of a workaround being documented in an FAQ somewhere, but I didn't see anything in the autoinstall FAQ. Unattended installation is mandatory for the project I'm working on, so this dialog box is quickly becoming the bane of my existence. Any help would be appreciated. Thanks. -j

2 1

Autoinstallation from HDisk
by Werner Hack 07 Jul '04

07 Jul '04

Anas Nashif wrote: > > Werner Hack wrote: > > > > I try to install a PC from local HDisk using a selfmade BootCD. > > But I can not manage it to work > > Could you help me please and give me some hints. > > > > I copied the SuSE DVD Distribution to 'serverdir'. > > Booting from CD is working fine, the autoyast-file is read. > > But then I get an error message : > > > >>Could not set base selection: default > >>Error while configuring software selections > > > > This is my isolinux.cfg file on CD: > > > >>default Server > >>label Server > >> kernel linux > >> append textmode=1 initrd=initrd load_ramdisk=1 > >> rootimage=root insmod=reiserfs > >> serverdir=/install/autoyast/SuSE/ > >> partition=hdb9 > >> autoyast=device://hdb9/install/autoyast/profiles/server.xml > > > > > > > Use 'install=hd://hdb9/install/autoyast/SuSE/' > or (even 'install=hd:///install/autoyast/SuSE/') instead. 'rootimage=' > and insmod are not necessary. > If I am doing this I get a very early error message : Could not find the SuSE Installation Source Activating manual setup program On console window I see this message : /dev/hdb9 is not a SuSE Linux installation media : Looking for a network server ... : Automatic setup not possible Hm, strange - network installation for other workstations from the same source directory is working fine. Am I missing any configuration parameter for autoinstallation from HDisk ? The curious thing is : If I continue installation manually after abortion of automatic setup, installation source is found on HDisk ... BUT later on : No profile for this machine could be found or retrieved (you remember: autoyast=device://hdb9/install/autoyast/profiles/server.xml) > > (append-line is written in one line) > > On console window I can mount the partition manually and access the files. > > > > This is the content of my CD: > > ./initrd > > ./isolinux.bin > > ./isolinux.cfg > > ./linux > > ./root > > > > > Look on virtual console nr. 3 and see whats going on there.. > > > > All files (linux, initrd, root) are taken from SuSE DVD without any changes. > > > > Any idea what's going wrong ? > > Any advice will be appreciated. > > > Anas > > > > > Thanks in advance. > > Regards, > > Werner Hack > > --

1 0