April 2004 - openSUSE Autoinstall - openSUSE Mailing Lists

Antwort: RE: [suse-autoinstall] Antwort: AW: [suse-autoinstall] Antwort: [ suse-autoinstall] autoinst
by Manuel.Laesser＠telekurs.com 01 Apr '04

01 Apr '04

Hello Todd Yes, I think your right. If you create an iso image using autoyast the /boot/loader/isolinux.cfg on the cd looks like this: ***************************** default autoyast # autoyast label autoyast kernel linux append initrd=initrd ramdisk_size=65536 autoyast=default instmode=cd usedhcp=0 textmode=1 ... **************************** The "texmode=1" was added by myself. But in this case "instmode=cd" would be wrong.... :-o??. If you go to the PDF of Anas Nashif on page 38/39 it says you should use "autoyast=file:/autoinst.xml" for CD-ROM as well. I'll test if it works whith this option. Regards Manuel Mit freundlichen Grüssen, Manuel Laesser ----------------------------------------------------------- Telekurs Services Hardturmstrasse 201, 8005 Zürich Phone : +41 1 279 44 24 Fax : +41 1 279 34 44 mailto : manuel.laesser(a)telekurs.com -----------------------------------------------------------

1 0

RE: [suse-autoinstall] Antwort: AW: [suse-autoinstall] Antwort: [ suse-autoinstall] autoinst
by Ness, Todd 01 Apr '04

01 Apr '04

I believe you have to add it to your initrd file, there are instructions in the list archives for how to add stuff to initrd. -----Original Message----- From: Manuel.Laesser(a)telekurs.com [mailto:Manuel.Laesser@telekurs.com] Sent: Thursday, April 01, 2004 7:35 AM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] Antwort: AW: [suse-autoinstall] Antwort: [suse-autoinstall] autoinst Hello Fabian That's exactly what I did! autoinst.xml is in the root of my cd. sles8:/home/tklsa # ls -l /mnt total 4471 dr-xr-xr-x 6 root root 4096 Mar 26 14:00 . drwxr-xr-x 21 root root 4096 Apr 1 2004 .. -r--r--r-- 1 root root 2185477 Mar 26 13:48 ARCHIVES.gz -r--r--r-- 1 root root 1265 Mar 26 13:48 COPYRIGHT -r--r--r-- 1 root root 27878 Mar 26 13:48 COPYRIGHT.yast -r--r--r-- 1 root root 2254127 Mar 26 13:48 ChangeLog -r--r--r-- 1 root root 17205 Mar 26 13:48 INDEX.gz -r--r--r-- 1 root root 17862 Mar 26 13:48 LICENSE.TXT -r--r--r-- 1 root root 742 Mar 26 13:48 README -r--r--r-- 1 root root 810 Mar 29 11:54 TRANS.TBL dr-xr-xr-x 7 root root 2048 Mar 26 13:48 UnitedLinux -r--r--r-- 1 root root 15077 Mar 26 13:48 autoinst.xml dr-xr-xr-x 3 root root 4096 Mar 26 13:49 boot -r--r--r-- 1 root root 2048 Mar 29 11:54 boot.cat -r--r--r-- 1 root root 587 Mar 26 13:48 content -r--r--r-- 1 root root 31479 Mar 26 13:48 ls-lR.gz dr-xr-xr-x 2 root root 2048 Mar 26 13:58 media.1 -r--r--r-- 1 root root 2474 Mar 26 13:48 pubring.gpg dr-xr-xr-x 3 root root 2048 Mar 26 14:00 tk Greetings Manuel Mit freundlichen Grüssen, Manuel Laesser ----------------------------------------------------------- Telekurs Services Hardturmstrasse 201, 8005 Zürich Phone : +41 1 279 44 24 Fax : +41 1 279 34 44 mailto : manuel.laesser(a)telekurs.com -----------------------------------------------------------

1 0

AW: [suse-autoinstall] Antwort: [suse-autoinstall] autoinst
by Lenz, Fabian 01 Apr '04

01 Apr '04

Hello! The autoinst.xml must be in the root directory of the cd. Autoyast search the file in the root directory. the name of the file must be autoinst.xml! -----Ursprungliche Nachricht----- Von: Manuel.Laesser(a)telekurs.com [mailto:Manuel.Laesser@telekurs.com] Gesendet: Montag, 29. Marz 2004 10:52 An: suse-autoinstall(a)suse.com Betreff: [suse-autoinstall] Antwort: [suse-autoinstall] autoinst Hello, today I burn the original iso image created by autoyast to a cd and tried to boot my test server. Unlike the iso image on which I made some changes (see mail before), the system is able to boot from the cd. Unfortunately the automatic installation stops when it comes to the stage of retrieving the xml file. Then I got the follwing error message: Profile for this machine could not be found or retrieved.... I could also enter a path where the file is located. I specified /dev/hdc (cdrom) and also tried with /dev/cdrom without success. Why does autoyast not find my autoinst.xml on the cd? Has anyone a good idea? Thank you very much! Manuel

2 1

Re: Re: [suse-autoinstall] Two type network adapters problem
by damien.selles＠eu.effem.com 01 Apr '04

01 Apr '04

hi again. I found the info somewhere on the web.. I don't remember where: kernel_version=`hostname` pcimap=/lib/modules/$kernel_version/modules.pcimap alldev=$(lspci -n| sed -e 's/^.*:[[:blank:]]\+$[^[:blank:]]\+$.*$/\1/') if [ -n "$alldev" -a -r $pcimap ] then for i in $alldev do vendor="$(echo $i| cut -d':' -f1)" device="$(echo $i| cut -d':' -f2)" all_modules=`grep "0x0000$vendor[[:blank:]]\+0x0000$device" $pcimap \ |awk '{ print $1 }'|sort -u` for module in $all_modules do find /lib/modules/$kernel_version/kernel/drivers/net/ -name \ "$module.o"|grep $module > /dev/null if [ $? = 0 ] then echo $module fi done done fi This should give you what you are looking for. Regards, Damien. "george_king" <george_king(a)ustc.edu> ustc.edu To: 01/04/2004 15:31 "damien.selles" <damien.selles(a)eu.effem.com>, "george_king" <george_king(a)ustc.edu> Please respond to cc: george_king "suse-autoinstall " <suse-autoinstall(a)suse.com> Subject: Re: Re: [suse-autoinstall] Two type network adapters problem --------------------------------------------------------------------------------------------------------------------------------------------------- BTW, do you know how to identify the module name used by a network interface? Replyed From: george_king <george_king(a)ustc.edu> > > Hi Georges, > > I have had some similar issues with several network cards in the server. > And I did not find any autoyast option/function to solve it. > The solution I found was a postscript, as you mentionned. > > Now, if you have only one network card to configure, to can proceed that > way: > > 1- identify the Mac address of the used card > 2- identify the module used by this card > 3- configure "nameif" to create "your_eth" ... (man nameif :p ) > 4- create the ifcfg-your_eth file > 5- update /etc/modules.conf with "alias your_eth module" > > it should bypass your iss r>> other modules loaded. > > In case you are relunctant to use nameif... well.. your post script must be > a bit more complex.. > but it is still possible. :)) > > hope it will help. > > > Regards, > Damien. > > > > > > > "george_king" > <george_king(a)ustc.edu> > ustc.edu > To: > 01/04/2004 13:56 "suse-autoinstall" <suse-autoinstall(a)suse.com> > Please respond to cc: > george_king > > > > Subject: > [suse-autoinstall] Two type network adapters problem > > ------------------------------------------------------------------------------------------------------------------------------------------------- > > > > Hi, > > I encounter a problem when I use autoyast to > install a machine with two type network adapters. > > The target machine have two types of network > adapter. Since the number of network adapters is > not fixed, I can not tell autoyast xml file how > many network interface should be configured. I > write a post-install script to config the network > adapter used for network install. What I do is 1) > add alias to modules.conf 2) add ifcfg-eth? files. > > The way can work in most of cases. But in follow > case, it fail -- > during installation, autoyast find three interface > eth0 3c59x > eth1 3c59x > eth2 e100 -- It is for network install. > > My script will add "alias eth2 e100" to > modules.conf. > > When the system reboot, it can not bring up e100 > network adapter. I can make it work by change > "eth2" to eth0 . It seems that kernel think e100 > is "eth0" because 3c59x was not loaded. > > Since network type and network adapter number is > not fixed, i can not make my script to config all > found network adapters. Does autoyast xml can > probe all found network adapter and make > configuration for all of them? If so, what shall > we do? > > > -- > USTC Alumni Email System > > > > > > > > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com > > -- USTC Alumni Email System

1 0

Re: [suse-autoinstall] Two type network adapters problem
by damien.selles＠eu.effem.com 01 Apr '04

01 Apr '04

Hi Georges, I have had some similar issues with several network cards in the server. And I did not find any autoyast option/function to solve it. The solution I found was a postscript, as you mentionned. Now, if you have only one network card to configure, to can proceed that way: 1- identify the Mac address of the used card 2- identify the module used by this card 3- configure "nameif" to create "your_eth" ... (man nameif :p ) 4- create the ifcfg-your_eth file 5- update /etc/modules.conf with "alias your_eth module" it should bypass your issue with the eth number that can depend on the other modules loaded. In case you are relunctant to use nameif... well.. your post script must be a bit more complex.. but it is still possible. :)) hope it will help. Regards, Damien. "george_king" <george_king(a)ustc.edu> ustc.edu To: 01/04/2004 13:56 "suse-autoinstall" <suse-autoinstall(a)suse.com> Please respond to cc: george_king Subject: [suse-autoinstall] Two type network adapters problem ------------------------------------------------------------------------------------------------------------------------------------------------- Hi, I encounter a problem when I use autoyast to install a machine with two type network adapters. The target machine have two types of network adapter. Since the number of network adapters is not fixed, I can not tell autoyast xml file how many network interface should be configured. I write a post-install script to config the network adapter used for network install. What I do is 1) add alias to modules.conf 2) add ifcfg-eth? files. The way can work in most of cases. But in follow case, it fail -- during installation, autoyast find three interface eth0 3c59x eth1 3c59x eth2 e100 -- It is for network install. My script will add "alias eth2 e100" to modules.conf. When the system reboot, it can not bring up e100 network adapter. I can make it work by change "eth2" to eth0 . It seems that kernel think e100 is "eth0" because 3c59x was not loaded. Since network type and network adapter number is not fixed, i can not make my script to config all found network adapters. Does autoyast xml can probe all found network adapter and make configuration for all of them? If so, what shall we do? -- USTC Alumni Email System

1 0

Two type network adapters problem
by george_king 01 Apr '04

01 Apr '04

Hi, I encounter a problem when I use autoyast to install a machine with two type network adapters. The target machine have two types of network adapter. Since the number of network adapters is not fixed, I can not tell autoyast xml file how many network interface should be configured. I write a post-install script to config the network adapter used for network install. What I do is 1) add alias to modules.conf 2) add ifcfg-eth? files. The way can work in most of cases. But in follow case, it fail -- during installation, autoyast find three interface eth0 3c59x eth1 3c59x eth2 e100 -- It is for network install. My script will add "alias eth2 e100" to modules.conf. When the system reboot, it can not bring up e100 network adapter. I can make it work by change "eth2" to eth0 . It seems that kernel think e100 is "eth0" because 3c59x was not loaded. Since network type and network adapter number is not fixed, i can not make my script to config all found network adapters. Does autoyast xml can probe all found network adapter and make configuration for all of them? If so, what shall we do? -- USTC Alumni Email System

1 0