July 2004 - openSUSE Autoinstall - openSUSE Mailing Lists

[Fwd: Re: [suse-autoinstall] Additional rpm packages are not found on media? (error 11283)]
by Stephan A. Rickauer 03 Sep '04

03 Sep '04

Hard to believe, but it works! Thanks Jan. However, it would be really helpful to know, why it has to be i586 and not "noarch". Furthermore, I'd like to specify my own subdirs, like "uni" or something similar ... isn't that possible? 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 ------------------------ Jan-Marc Pilawa wrote: > Schon probiert die rpms in i586 abzulegen? Meine habe ich dort angelegt und > genau das getan, was in der Mail beschrieben stand. > > Mit freundlichen Gruessen / Sincerely > > Jan Pilawa > -------- Original Message -------- Subject: Re: [suse-autoinstall] Additional rpm packages are not found on media? (error 11283) Date: Thu, 8 Jul 2004 14:22:12 +0200 From: Jan-Marc Pilawa <j.pilawa(a)tu-bs.de> Organization: Rechenzentrum To: Stephan A. Rickauer References: <40ED38D7.7020101(a)ini.phys.ethz.ch> Schon probiert die rpms in i586 abzulegen? Meine habe ich dort angelegt und genau das getan, was in der Mail beschrieben stand. Mit freundlichen Gruessen / Sincerely Jan Pilawa -- + Kontakt ----------------------------------------------------+ + Systembetreuung Rechenzentrum TU Braunschweig + + Hans-Sommer-Str. 65, D-38092 Braunschweig + + Tel: +49 531 391-5548 E-Mail: j.pilawa(a)tu-bs.de ____________+

3 6

autoyast with suse 9.1
by Todd Merritt 09 Aug '04

09 Aug '04

I've read the documentation at http://www.suse.de/~nashif/autoinstall/9.1/html/, and several other sites I found explaining how to create an autoyast.xml file from a complete installation. The instructions for 9.1 don't specify what rpms need to be installed and when I run yast2 autoyast I get: No such client module autoyast I tried installing the modules I found referenced from documents on 8.x (yast-config-autoinst), but I still get the same message. Can somebody point me in the right direction ? Thanks, Todd

5 5

Installing with Fibre attached drive onto local scsi device
by Aaron Amauba 02 Aug '04

02 Aug '04

Sorry if this question has already been addressed here on the lists. I am new to the SAN enviornment and am haveing a difficult time installing SLES8 onto a machine while it is attached to the SAN. At installation time (I use autoyast via NFS) the fibre attached LUN is being seen first and is being assigned /dev/sda. How do I force the local scsi device to be seen as /dev/sda? I looked in linuxrc in initrd, but it wasnt a script. Thanks in advance. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

1 1

RE: [suse-autoinstall] How do you get SUSE's autoinstall mode to work, and how do you get useful error messages out?
by Ness, Todd 29 Jul '04

29 Jul '04

I had a brand new GX270 that needed the BIOS updated before the graphics would do more than 640x480 8 bit color. Oh and it is so nice of Dell to make that have to run under DOS or windows only for the BIOS update. So, find a win98 bootable floppy and update your BIOS before wasting any more time. Todd -----Original Message----- From: volker_blum(a)web.de [mailto:volker_blum@web.de] Sent: Thursday, July 29, 2004 3:12 AM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] How do you get SUSE's autoinstall mode to work, and how do you get useful error messages out? Hi, I am trying to use SUSE 9.1 on a brand new Dell GX270 computer; short summary, there are all sorts of weird issues. Maybe someone here has seen anything like it? - I cannot get the graphical installation mode (autoinstall?) to work. I do get the (grub?) boot menu on the DVD all right. After choosing "installation" in any incarnation, the kernel is loaded all right (I suppose), but switching to X (?) appears to fail. Anyway, I get a blue screen with no text except for an "OK" request - only that none of the keys on the keyboard except the F1, F9, F10 and ESC keys work,, ah yes, and no mouse ... i.e. it is impossible to configure anything at all. - Space oddity - I did get the graphical installation mode exactly once, and never again (yes, there are only three switches to try in grub, on one and the same DVD and the same computer ... this is not reproducible). The graphics was dreadful, but it found the mouse and keyboard all right, and I could set up some things ... except then one partition (and only one ... hda6) could not be formatted (reiser) with no understandable error message. This leaves me somewhat stumped. (a) How could I get back to the graphical installation mode, which seemed to detect my (USB) Mouse and (PS/2) keyboard all right? (b) Once I get there - in what way could I get a useful error message out of the system so as to know what went wrong with formatting that one partition - is the disk bad, is it some minor corrigible error, should I use a different file system? (c) Finally, maybe this all is a kernel problem together with my newish hardware ... is autoyast based on 2.6 or 2.4? This is approximately the 10th SUSE Linux version (since 5.2?) which I have installed sometime, somewhere ... and this time I am really unsure what to do - downgrade to 9.0? Thanks VB -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1

How do you get SUSE's autoinstall mode to work, and how do you get useful error messages out?
by Volker Blum 29 Jul '04

29 Jul '04

Hi, I am trying to use SUSE 9.1 on a brand new Dell GX270 computer; short summary, there are all sorts of weird issues. Maybe someone here has seen anything like it? - I cannot get the graphical installation mode (autoinstall?) to work. I do get the (grub?) boot menu on the DVD all right. After choosing "installation" in any incarnation, the kernel is loaded all right (I suppose), but switching to X (?) appears to fail. Anyway, I get a blue screen with no text except for an "OK" request - only that none of the keys on the keyboard except the F1, F9, F10 and ESC keys work,, ah yes, and no mouse ... i.e. it is impossible to configure anything at all. - Space oddity - I did get the graphical installation mode exactly once, and never again (yes, there are only three switches to try in grub, on one and the same DVD and the same computer ... this is not reproducible). The graphics was dreadful, but it found the mouse and keyboard all right, and I could set up some things ... except then one partition (and only one ... hda6) could not be formatted (reiser) with no understandable error message. This leaves me somewhat stumped. (a) How could I get back to the graphical installation mode, which seemed to detect my (USB) Mouse and (PS/2) keyboard all right? (b) Once I get there - in what way could I get a useful error message out of the system so as to know what went wrong with formatting that one partition - is the disk bad, is it some minor corrigible error, should I use a different file system? (c) Finally, maybe this all is a kernel problem together with my newish hardware ... is autoyast based on 2.6 or 2.4? This is approximately the 10th SUSE Linux version (since 5.2?) which I have installed sometime, somewhere ... and this time I am really unsure what to do - downgrade to 9.0? Thanks VB

2 2

Partitioning
by Thomas Mack 29 Jul '04

29 Jul '04

Obviously, I don't understand partitioning very well. On SuSE 9.0 autoinstall, I have one disk for normal linux installation: this worked somehow ok. I added another disk (/dev/hdb) that is partitioned already, and it should just mount its partition to some directory. So I added this one. But it now ends up in some "unknown error", aborting the installation. What is happening? Neither in http://www.suse.de/~nashif/autoinstall/9.0/html/index.html nor in the profile reference http://www.suse.de/~nashif/autoinstall/8.1/profile/index.html I found any hint on what might be wrong with it, nor did I find any note on how to do it correctly. The whole partitioning scheme now looks like this: <partitioning config:type="list"> <drive> <device>/dev/hda</device> <initialize config:type="boolean">false</initialize> <partitions config:type="list"> <partition> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <partition_nr config:type="integer">2</partition_nr> <size>3GB</size> </partition> <partition> <filesystem config:type="symbol">ext2</filesystem> <mount>/var/cache/openafs</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">3</partition_nr> <size>1gb</size> </partition> <partition> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <filesystem config:type="symbol">reiser</filesystem> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">5</partition_nr> <size>max</size> </partition> </partitions> <use>2,3,4,5,6,7</use> </drive> <drive> <device>/dev/hdb</device> <initialize config:type="boolean">false</initialize> <partitions config:type="list"> <partition> <format config:type="boolean">false</create> <partition_nr config:type="integer">1</partition_nr> <mount>/scratch</mount> </partition> </partitions> </drive> </partitioning> If anyone can help...? Thanks for any hint, Thomas Mack TU Braunschweig, Institut f. Informationssysteme

1 0

SuSE 9.1 DVD (AMD64 + Intel) cannot find control file on floppy disk on opteron
by Frank Samuel 28 Jul '04

28 Jul '04

Recently I bought SuSE 9.1 (AMD64 + Intel). I met a problem when trying to use the DVD and a floppy disk(with control file in it) to autoinstall SuSE 9.1 on an opteron machine. I specified the following parameters at command line in the beginning of installation append language=english install=cdrom autoyast=floppy Press Ctrl + ALT + F2, I noticed a message of "There seems to be no floppy disk" when probing the hardware. But when I use the other side of the DVD (Intel), the floppy is detected and autoinstall starts succesfully. Using the CD Rom (Intel 32-bit) also works fine. Previous versions of SuSE like SLES 8 and SuSE 9.0 detects the floppy as well. Could someone tell me what's the problem? Thanks a lot __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

1 1

Is the yast2 autoyast broken ?
by Henrik Schmidt 28 Jul '04

28 Jul '04

I tried to remove all cups packages except cups-libs from the package list generated by 'yast2 autoyast'. If I deselect them and save with the GUI they are still in my config.xml afterwards. This is not the first bug so it seems the autoyast GUI is badly broken with 9.1. Here is my short buglist : - 'Create reference profile' is broken. It does not create entries for network, partitions, sound etc. pp - Removing single packages with 'Software->Package Selection' does not remove them from the list when saving. - Setting up a LPRNG printer is not supported at all - Setting up 24bit color depth is accepted but not saved - 'General->Confirm installation' shows 'no' though the box is checked 'yes' when you choose 'Configure'. - Soundcards which are autodetected do not show up in the list and can't be selected/configured Guess thats not all but I feel frustrated and will take a few days off trying to tweak my config.xml by hand next week. Here I ask again : Is there a complete reference of available xml tags for autoyast ? Is there a better documentation ? Is autoyast supported or unsupported by SuSE ? Henrik -- Henrik Schmidt Christian-Albrechts-Universitaet zu Kiel Institut fuer Informatik +49 (431) 880 75 - 50 Fax or 43 Phone Olshausenstr. 40 http://www.ks.informatik.uni-kiel.de 24098 Kiel, Germany email: hbs(a)ks.informatik.uni-kiel.de

5 7

AW: [suse-autoinstall] Is the yast2 autoyast broken ?
by Hollmann Frank 28 Jul '04

28 Jul '04

Hi, the remove-package construct does not work under SLES8 autoinstall. My Work-Around: create your own software-selection (*.sel) to circumvent this error Frank Hollmann OFD München - IT Bereich -----Ursprüngliche Nachricht----- Von: David Corlette [mailto:corlette@huarp.harvard.edu] Gesendet: Dienstag, 27. Juli 2004 17:16 An: Henrik Schmidt; suse-autoinstall(a)suse.com Betreff: Re: [suse-autoinstall] Is the yast2 autoyast broken ? > Simple question is : how do I tell autoyast not to install the cups > packages conflicting with lprng. Or more generally : How do I tell > autoyast to delete a package from a list at all. I can individually > add packages but I can't individually remove them with autoyast. Can't you just do: <remove-packages config:type="list"> <package>cups</package> </remove-packages> as it says at: http://www.suse.de/~nashif/autoinstall/9.1/html/CreateProfile.Software .html#id2523534 (where "cups" is a package you want to remove). Dave C --------------------------------------------------------- David Corlette mailto:corlette@huarp.harvard.edu (617)495-5922 http://www.arp.harvard.edu -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

AY in 9.1: List of bugs and feature requests
by Frank Steiner 28 Jul '04

28 Jul '04

Hi Anas, I give up with SuSE 9.1 because it seems to contain too many bugs (including bugs in the installation process with yast, which are not AY related (like system users not being created, systems crashing when loading modules for non-existent hardware etc.). It seems that neither the 2.6.5. kernel nor the coldplug system are stable yet... I will try again with SuSE 9.2 Anyway, here's a list of bugs I found in AY 9.1 which perhaps can be fixed before the release of 9.2. And a feature request list :-) This is just a concise summary of the things I wrote about on the list in some other mails. Bugs: ===== - AY automatically adds scsi controller modules for initrd in /etc/sysconfig/modules but fails to add the scsi_mod module first. Even if one adds the scsi_mod via the profile, the controller modules will be inserted first. Thus, the system will not be able to boot from a scsi disk - matching for "hostname" in rules.xml will not match the hostname but the IP. The variable "hostname" in the AY environment contains the IP. - chroot scripts can not be loaded with <location>nfs://</location> since AY will mount the location on /mnt, where the just installed system is already mountet, thus failing to copy the chroot scripts into the installed system. - profile.dtd does not include sysconfig.dtd - bootloader.dtd is missing the kernel_parameters element Feature wish-List: ================== - chroot scripts should be executed as last thing, *after* the bootloader config is written, so that it is e.g. possible to tweak the lilo.conf just before rebooting. - allow "<match>*</match>" to match against anything, or let AY take a missing match as "always succeed" so that one can e.g. just write <rule> <hostaddress> </hostaddress> <result> <profile>@hostaddress@.xml</profile> </result> </rule> to add a specific profile for every host with a single rule. - allow to use variables via @ in the result part of a rule when they were set in a custom script, i.e., allow <rule> <custom1> <script> <![CDATA[ #!/bin/sh export myhostname=`grep HOSTNAME /var/lib/dhcpcd/dhcpcd-eth0.info | sed 's/HOSTNAME=//g'` echo -n undefined ]]> </script> <match>undefined</match> <match_type>exact</match_type> </custom1> <result> <profile>@myhostname@.xml</profile> <continue config:type="boolean">true</continue> </result> </rule> - allow to give partition information to be used if no fstab is found. If an fstab is found, use the fstab and ignore the partition information from the profile. That would allow to use one single profile for hosts with empty or previously formatted hard disks. If the fstab was found, it would be used. If no fstab was found, the partition information would be used. In AY1 one could do it this way. - allow the user to change the default formatting behaviour when an fstab exists. I.e., the user should be able to tell AY: "if an existing fstab is found, do not format any partition except the ones I explicitely define". Best regards, 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 * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *

2 2