Re: [suse-autoinstall] Fw: autoyast and loadorder of modules
du hast recht, fuer sles8 funktionierts, indem man die treiberreihenfolge als append parameter fuer den bootkernel mitgibt (aber wahrscheinlich auch nur, weil sles8 erst alle pakete installiert, dann die postskripte ausfuehrt und danach der initial boot erfolgt, waehrend suse9 halt gleich nach der 1. cd rebooten will und die bis dahin zusammengebaute initrd die einstellungen einfach ignoriert!). wenn sles9 auf basis suse 9 aufgebaut ist, haben wir dann dort wahrscheinlich die mimik von suse9 nach der ersten cd?! waere einen versuch wert ;-) Harald.Milz@compu tacenter.com To 06/09/2004 12:54 Helge Koehn/Germany/IBM@IBMDE PM cc Subject Re: [suse-autoinstall] Fw: autoyast and loadorder of modules Nur halt mit SLES8, da geht's ja. SuSE9 ist insofern kaputt. Mal sehen, was SLES9 macht - wenn sich's mal installieren läßt :-( Mit freundlichen Gruessen - Best regards Harald Milz Senior Consultant CC CompuNet AG & Co. oHG A part of Computacenter plc Hoerselbergstrasse 7, 81677 Muenchen, Germany Phone: +49 (0)89 45712-161, Fax: -331, Mobile: +49 (0)173 3866604 E-Mail : Harald.Milz@computacenter.com Visit us on the Internet: http://www.computacenter.com Visit our Online-Shop: http://www.compunet.de/connect This email is confidential. If you are not the intended recipient, you must not disclose or use the information contained in it. If you have received this mail in error, please tell us immediately by return email and delete the document. Helge Koehn <koehn@de.ibm.com> on 09.06.2004 12:03:42 To: suse-autoinstall@suse.com cc: Subject: [suse-autoinstall] Fw: autoyast and loadorder of modules -------------------------------------------------------------------------- ... any ideas to that problem from march?! till now not one answer :-( helge. ----- Forwarded by Helge Koehn/Germany/IBM on 06/09/2004 11:57 AM ----- Helge Koehn/Germany/IBM To 03/08/2004 03:14 suse-autoinstall@suse.com PM cc Subject autoyast and loadorder of modules hi, we face a problem where we have to load kernelmodules in a specific order to get our scsi devices recognized correctly! we are doing an autoyastinstallation via pxe. we send with the append parameter in the pxe-config file the modules to load, that works. our scsi device are recognized in the correct order. in the autoyast.xml we are partitioning the scsi devices and write the bootloader to /dev/sda. the stuff from disk 1 is transfered to the installed system. after the first initial boot, the order we have with the append parameter in the pxe-config file no longer works, autoyast has build its own initrd for the initial boot and with that the devices are changing because of loading the adapterdrivers in the wrong order! how can we arrange that our wanted order of devices also works after the initial boot. so that /dev/sda remains /dev/sda and not switches to /dev/sdb thanks for an answer. helge. -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com COMPUTACENTER (UK) LTD The contents of this e-mail are intended for the named addressee only. It contains information which may be confidential and which may also be privileged. Unless you are the named addressee (or authorised to receive for the addressee) you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it. Computacenter information is available from http://www.computacenter.com This footnote also confirms that this email message has been swept for the presence of computer viruses. ***************************************************************************************************************************
sles9 is based on suse 9.1 On Wed, 9 Jun 2004, Helge Koehn wrote:
du hast recht, fuer sles8 funktionierts, indem man die treiberreihenfolge als append parameter fuer den bootkernel mitgibt (aber wahrscheinlich auch nur, weil sles8 erst alle pakete installiert, dann die postskripte ausfuehrt und danach der initial boot erfolgt, waehrend suse9 halt gleich nach der 1. cd rebooten will und die bis dahin zusammengebaute initrd die einstellungen einfach ignoriert!).
wenn sles9 auf basis suse 9 aufgebaut ist, haben wir dann dort wahrscheinlich die mimik von suse9 nach der ersten cd?! waere einen versuch wert ;-)
Harald.Milz@compu tacenter.com To 06/09/2004 12:54 Helge Koehn/Germany/IBM@IBMDE PM cc
Subject Re: [suse-autoinstall] Fw: autoyast and loadorder of modules
Nur halt mit SLES8, da geht's ja. SuSE9 ist insofern kaputt. Mal sehen, was SLES9 macht - wenn sich's mal installieren läßt :-(
Mit freundlichen Gruessen - Best regards
Harald Milz Senior Consultant
CC CompuNet AG & Co. oHG A part of Computacenter plc Hoerselbergstrasse 7, 81677 Muenchen, Germany Phone: +49 (0)89 45712-161, Fax: -331, Mobile: +49 (0)173 3866604 E-Mail : Harald.Milz@computacenter.com Visit us on the Internet: http://www.computacenter.com Visit our Online-Shop: http://www.compunet.de/connect
This email is confidential. If you are not the intended recipient, you must not disclose or use the information contained in it. If you have received this mail in error, please tell us immediately by return email and delete the document.
Helge Koehn <koehn@de.ibm.com> on 09.06.2004 12:03:42
To: suse-autoinstall@suse.com cc: Subject: [suse-autoinstall] Fw: autoyast and loadorder of modules
--------------------------------------------------------------------------
... any ideas to that problem from march?! till now not one answer :-( helge.
----- Forwarded by Helge Koehn/Germany/IBM on 06/09/2004 11:57 AM -----
Helge Koehn/Germany/IBM To 03/08/2004 03:14 suse-autoinstall@suse.com PM cc
Subject autoyast and loadorder of modules
hi,
we face a problem where we have to load kernelmodules in a specific order to get our scsi devices recognized correctly! we are doing an autoyastinstallation via pxe. we send with the append parameter in the pxe-config file the modules to load, that works. our scsi device are recognized in the correct order. in the autoyast.xml we are partitioning the scsi devices and write the bootloader to /dev/sda. the stuff from disk 1 is transfered to the installed system. after the first initial boot, the order we have with the append parameter in the pxe-config file no longer works, autoyast has build its own initrd for the initial boot and with that the devices are changing because of loading the adapterdrivers in the wrong order!
how can we arrange that our wanted order of devices also works after the initial boot. so that /dev/sda remains /dev/sda and not switches to /dev/sdb
thanks for an answer. helge.
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
COMPUTACENTER (UK) LTD
The contents of this e-mail are intended for the named addressee only. It contains information which may be confidential and which may also be privileged. Unless you are the named addressee (or authorised to receive for the addressee) you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.
Computacenter information is available from http://www.computacenter.com
This footnote also confirms that this email message has been swept for the presence of computer viruses.
***************************************************************************************************************************
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
-- Andreas Vetter Universitaet Wuerzburg, Theoretische Physik 1 Am Hubland, 97074 Wuerzburg, Deutschland / Germany
participants (2)
-
Andreas Vetter
-
Helge Koehn