August 2003 - openSUSE Autoinstall - openSUSE Mailing Lists

RE: [suse-autoinstall] partition problems with AutoYast / boot pr oblems with Intel onboard pro/100 VE
by Berge, Harry ten 27 Aug '03

27 Aug '03

Maybe I have an answer to your first question: AFAIK the autoinstaller will create new partitions at the END of the disk. You mention that you have already 2 partitions at the end of the disk.... A possible solution is to do the partitioning yourself in a script and leave the disk untouched by the autoinstaller. Regards Harry > -----Original Message----- > From: Ralf.Pichler(a)t-online.de [SMTP:Ralf.Pichler@t-online.de] > Sent: Tuesday, August 26, 2003 10:38 PM > To: suse-autoinstall(a)suse.com > Subject: [suse-autoinstall] partition problems with AutoYast / boot > problems with Intel onboard pro/100 VE > > Hello Ansa, > > I am new on the AutoYast mailinglist and today i want to contact you > with following problem: > > goal is to autoinstall SUSE 8.2 in a 3GB primary ext2 partition for "/" > and 300 MB for an additonal 300MB swap (as primary) keeping the already > existing logical 300 MB swap and 2500MB ext2 at the end of the harddisk. > > I use a grub bootfloppy with the image from your website. It loads the > kernel via tftp and makes the rest via nfs. Yast2 starts and reads the > autoinst.xml. > > Result: No space left on Harddisk. > > I made the section "region_entry config" by hand based on a start > autoinst from yast2. > > To create the two additional partitions with parted is no problem, but > yast2 has problems to do this. > > What could be the reason? > > My second problem is when booting with a compiled grub bootloader from > floppy on a second PC. Here I build grub from the spec file with the > option "--enable-eepro100" for supporting an Intel 82801 BD PRO/100 VE > onboard network card. When booting with this floppy, the module EEPRO100 > can't be loaded. > Did I enable the correct network device in the spec file or which is the > right one? > > > With regards and thanks for your affords, > > Ralf Pichler > -- > ________________________________ > Ralf Pichler > Gräfelfinger Straße 151 > 81375 München > > phone: +49-89-74 02 93 45 > mobil: +49-170-90 80 44 3 > email: ralf.pichler(a)t-online.de > > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Re: [suse-autoinstall] Additional package not in ISO-image, updated also
by silverio.santos＠equant.com 25 Aug '03

25 Aug '03

That was it! Thanks Silvério Santos Richard Bos <radoeka(a)xs4all.nl> 19.08.2003 13:08 To: suse-autoinstall(a)suse.com Please respond to richard.bos cc: bcc: Subject: Re: [suse-autoinstall] Additional package not in ISO-image, updated also Op dinsdag 19 augustus 2003 10:27, schreef silverio.santos(a)equant.com: > Hi, > > I found a strange behaviour of AutoInstall regarding addition and update of > RPMs, which have not been in the original distribution. > > Completing what I wrote below, packages are not prepared for > CD-image-creation, when: > - I copy a freshly downloaded and updated package, deleting the original > one (happened to autoyast2-installation) > - I add any new RPM to the respective architecture folder (e.g. i386) > Of course the create_package_descr is run after every change. > > Does anybody know how AutoInst compiles the list of files to prepare for > CD-creation and if any, where the (temporary) file is located? I would like > to learn more how AutoInst works, to understamd why it is unable to behave > the expected way. > > Silvério Santos What happens if you remove and re-add the Software source (in yast). Normally yast uses some kind of caching... -- Richard Bos Without a home the journey is endless -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Manual remote installation
by Christian Tröster 23 Aug '03

23 Aug '03

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I want to install a new SuSE to a server with remote access only. There are already 3 partitions (hda1 to 3) which I want to be untouched and a fourth partition hda4 to which the installation shoud go. The existing partitions hold the 'old' setup on hda1 and hda3 and a swap partition on hda2. For the setup I have remote access to to server through ssh only and a possibility to force a reboot via a web interface. My plan was to copy the /boot-Directory of the first SuSE cd to the new partition. Setup a new lilo entry for <mount point>/boot/loader/linux with several kernel parameters so I can gain ssh access and start a manual installation as if I was in front of the server. Unfortunatelly it didn't work :) I tried to setup everything as described in http://sdb.suse.de/en/sdb/html/remote_install.htm locally with two other computers to see how far I would come. But in spite of the supplied kernel parameters linuxrc still required someone pressing enter at the 'server'. I didn't figure out why, but i didn't work. The lilo entry was as follows. Perhaps it helps or someone could find an error. > image=/mnt/hda4/boot/loader/linux > label=suse_cdrom > ramdisk=65536 > initrd=/mnt/hda4/boot/loader/initrd > root=/dev/hda4 > append="showopts manual=1 usessh=1 sshpassword=password acpi=off > ip=192.168.0.42 netmask=255.255.255.0 insmod=8139too" Is it possible to perform a manual setup this way and if not could autoyast help? It would be nice if someone could give me a few hints. TIA. Bye, Christian - -- | mailto:c.troester@gmx.de | http://www.fen-net.de/~na2929 | -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE/R+8uCXo2j/oAbHQRAqznAJ9IlmuWmHEg9mIDCMxEWrD83NyQewCfeB6j Kp8ROMeoafAcA369g/GN8Yo= =mkjw -----END PGP SIGNATURE-----

1 0

Problems while partitioning
by Michael Binder 22 Aug '03

22 Aug '03

Hi, Im new on this list and not very well informed about autoyast. My problem is that a xml-stream that runs with SuSE 8.1 without any problems doesn't run with SuSE 8.2. it aborts at partitioning! any idea? thanks, Michael

1 0

Two Questions
by Hirayama, Pat 21 Aug '03

21 Aug '03

Greetings, I had a couple of questions I'm wrestling with right now. 1. create_package_descr -- So, if I have an installation repository setup, and then I add/update some packages, if I run create_package_descr, that should allow the new/updated packages to appear in YaST Software Installation? 2. When I use AutoYaST with a control file, as the system gets to the point that it will read the control file, it goes through and looks at hardware, and loads what modules it needs to. So, I was wondering if it was possible to PREVENT a specific module from loading? I have found that when I have a Dell with a PERC3/DC RAID controller, SuSE installer wants to load both a QLogic driver, and a Megaraid driver, which is a problem, since they are the same card. My workaround at the moment is to run a manual setup, answering yes/no to whichever modules to load. This defeats the purpose of having a hands-off autoinstallation routine. Any thoughts? Thank you! -p Pat Hirayama IT / Server Operations Fred Hutchinson Cancer Research Center phirayam(a)fhcrc.org

3 2

RE: [suse-autoinstall] Two Questions
by Hirayama, Pat 21 Aug '03

21 Aug '03

Sorry. This is SuSE 8.2 ftp version. -p -----Original Message----- From: Anas Nashif [mailto:nashif@suse.de] Sent: Thursday, August 21, 2003 8:52 AM To: Hirayama, Pat Cc: suse-autoinstall(a)lists.suse.com Subject: Re: [suse-autoinstall] Two Questions What version are you installing, SLES or 8.2? Anas Hirayama, Pat wrote: > That doesn't appear to help, as the setup program seems to want to load the > other module regardless. So, it just locks the system up a little faster. > > -p > > -----Original Message----- > From: Anas Nashif [mailto:nashif@suse.de] > Sent: Wednesday, August 20, 2003 7:02 PM > To: Hirayama, Pat > Cc: suse-autoinstall(a)lists.suse.com > Subject: Re: [suse-autoinstall] Two Questions > > Hirayama, Pat wrote: > <<snip>> > >>2. When I use AutoYaST with a control file, as the system gets to the > > point > >>that it will read the control file, it goes through and looks at hardware, >>and loads what modules it needs to. So, I was wondering if it was > > possible > >>to PREVENT a specific module from loading? I have found that when I have > > a > >>Dell with a PERC3/DC RAID controller, SuSE installer wants to load both a >>QLogic driver, and a Megaraid driver, which is a problem, since they are > > the > >>same card. My workaround at the moment is to run a manual setup, > > answering > >>yes/no to whichever modules to load. This defeats the purpose of having a >>hands-off autoinstallation routine. Any thoughts? >> > > > What about loading the right module before yast2 even starts with > insmod=<module name> as a kernel parameter, would this help? > > Anas > > >>Thank you! >> >> -p >> >> >>Pat Hirayama >>IT / Server Operations >>Fred Hutchinson Cancer Research Center >>phirayam(a)fhcrc.org >> >> > > > >

1 0

RE: [suse-autoinstall] Two Questions
by Hirayama, Pat 21 Aug '03

21 Aug '03

That doesn't appear to help, as the setup program seems to want to load the other module regardless. So, it just locks the system up a little faster. -p -----Original Message----- From: Anas Nashif [mailto:nashif@suse.de] Sent: Wednesday, August 20, 2003 7:02 PM To: Hirayama, Pat Cc: suse-autoinstall(a)lists.suse.com Subject: Re: [suse-autoinstall] Two Questions Hirayama, Pat wrote: <<snip>> > > 2. When I use AutoYaST with a control file, as the system gets to the point > that it will read the control file, it goes through and looks at hardware, > and loads what modules it needs to. So, I was wondering if it was possible > to PREVENT a specific module from loading? I have found that when I have a > Dell with a PERC3/DC RAID controller, SuSE installer wants to load both a > QLogic driver, and a Megaraid driver, which is a problem, since they are the > same card. My workaround at the moment is to run a manual setup, answering > yes/no to whichever modules to load. This defeats the purpose of having a > hands-off autoinstallation routine. Any thoughts? > What about loading the right module before yast2 even starts with insmod=<module name> as a kernel parameter, would this help? Anas > Thank you! > > -p > > > Pat Hirayama > IT / Server Operations > Fred Hutchinson Cancer Research Center > phirayam(a)fhcrc.org > >

2 1

Bootlogo
by Robison, Jonathon (M.) 21 Aug '03

21 Aug '03

The bootlogo file in /boot/loader - anyone know what graphic format that is? I'd like to replace it with a company logo. I know the gfxboot needs gfx-devel package, and I've succeeded in altering that, but I am having trouble with bootlogo. -jmr

1 0

Where are my partitions ?
by Alexander Luedtke 21 Aug '03

21 Aug '03

Hi folks, I'm trying to use autoyast, nearly everything works, at the moment I've only one problem: I want three partitions /dev/hda1 - swap 256 MB /dev/hda2 / reiserfs 25 GB /dev/hda3 /export - rest of drive what I get is that the swap partition is using the hole hda drive (eg. 76 GB !) here is my config: <partitioning config:type="list"> <drive> <device>/dev/hda</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <partition_type>primary</partition_type> <size>+256M</size> </partition> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <partition_type>primary</partition_type> <size>+25GB</size> </partition> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <mount>/export</mount> <partition_id config:type="integer">131</partition_id> <partition_type>primary</partition_type> <size>max</size> </partition> </partitions> <use>all</use> </drive> </partitioning> Can anybody help me ? greetings Alex -- Alexander Lüdtke Systemadministrator Adresse: TUM - Garching Boltzmannstr. 3 85747 Garching b. München Lehrstuhl: Frau Prof. Feldmann Zimmer: 01.08.036 Tel: ++49 (89) 289 - 18039

2 1

RE: [suse-autoinstall] Switching from floppies to disk
by Robison, Jonathon (M.) 20 Aug '03

20 Aug '03

What about the info file? I want to enforce the load structure, thus I have to have different CD's with different info files pointing to different xml files. i.e. one info file points to "laptop_developer.xml". Another points to "laptop_user.xml" etc. etc. Those xml files also have a lot of embedded scripts and config files to set up our krb5 authentication as well as the pam_mount login mounting system. I can't let user's do a "normal, choose what you want" install. For developers, I hand them the CD with the info file for developers. Users get the CD with the info file pointing to the regular user.xml. At least that's what I planned on doing. What I am hoping for is someone to tell me "edit these files ... put everything in from all 5 floppies into one subdirectory somewhere . . . now run mkisofs with these switches . . . burn the iso to CD." Or am I misunderstanding how this all works? (It wouldn't be the first time) --Jonathon -----Original Message----- From: Anas Nashif [mailto:nashif@suse.de] Sent: Wed 8/20/2003 12:11 PM To: Robison, Jonathon (M.) Cc: suse-autoinstall(a)lists.suse.com Subject: Re: [suse-autoinstall] Switching from floppies to disk Robison, Jonathon (M.) wrote: > I have created an install server, and the necessary floppies (1 boot, > 4 module). The info file is working on the module1 floppy, and > installing from the http server, as desired. > > Can someone guide me on what I would need to do to combine all of > these floppies into one image? I have some of those "Business Card" > CD's, capable of holding 50M. If you have this, then there is no need to create floppies at all, just create a bootable CD using the kernel and initrd available on the first CD in "boot/loader". Anas

3 2