openSUSE Autoinstall January 2005

autoinstall@lists.opensuse.org

48 participants
73 discussions

Re: [suse-autoinstall] Confirm Hardware Detection
by cozypaul＠web.de 18 Jan '05

18 Jan '05

Anas Nashif <nashif(a)suse.de> schrieb am 17.01.05 16:47:52: > > How did you start the autoinstallation? > You seem to have started in manual mode. Hi Anas, thank you for you answer.:=)) I've booted my installation from sles964amd first cd and put the following command: nousb nopcmcia insmod=tg3 hostip=10.1.113.23 netmask=255.255.255.0 gateway=10.1.113.254 install=http://10.1.128.23/sles9a autoyast=http://10.1.128/inscon/amd.xml.The same message comes at the beginning, although i've started with nousb options ! CozyPaul > > anas > > Pawel Slabiak wrote: > > Hi all, > > i really don't know why i get the following messages after first reboot: > > > > " Confirm Hardware Detection" > > Yast2 will detect the following hardware: > > Network Cards > > > > Continue Skip > > > > I put a corect line in my install.xml, here ist a small piece of this xml file: > > > > <modules config:type="list"> > > <module_entry> > > <device>eth0</device> > > <module>tg3</module> > > <device>eth1</device> > > <module>tg3</module> > > <options></options> > > </module_entry> > > </modules> > > > > Thanks for any advice > > > > Greets > > > > Cozy Paul > > > > > > __________________________________________________________ > > Mit WEB.DE FreePhone mit hoechster Qualitaet ab 0 Ct./Min. > > weltweit telefonieren! http://freephone.web.de/?mc=021201 > > > > ______________________________________________________________ Verschicken Sie romantische, coole und witzige Bilder per SMS! Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193

1 0

Problem setting the IP-Address with SuSE 9.1 within append
by Sven Osterwalder 18 Jan '05

18 Jan '05

Hello everyone, I've configured an autoinstall-script with yast and burned a modified suse boot-cd to start directly the autosetup. Im giving the following parameters to the kernel: install=nfs://192.168.1.1/tmp/SuSE/complete autoyast=nfs://192.168.1.1/tmp/SuSE/autoinstall/autoinstall2.xml ip=192.168.1.2 So it starts until yast would start and do all automatic. There it tries to catch an ip, allthough I have given an ip with ip=. I tried the setting dhcp=0 but then it tries to get an ip over bootp. Why this? He should have an ip and should could connect to the nfs-server. When I enter it manually in the installer, the autoinstall works perfect. Thanks and with kind regards Sven Osterwalder

2 1

Bonding of network cards
by "Andreas Müller" 17 Jan '05

17 Jan '05

I have two bcm5700 networkcards in my server and I want to bond them but I have no idea how I can do this with autoyast. Is it possible?

3 2

Re: [suse-autoinstall] SLES9: Howto bypass 256 chars boot-kernel parameter limit?
by Jochen Schaefer 17 Jan '05

17 Jan '05

some problems whith linefeeds last mail. I don't like this client. >>>"Jochen Schaefer" <jschaef(a)novell.com> 01/16 9:48 pm >>> Hi, I don't think you need the ramdisk_size parameter, netdevice parm, BOOT_IMAGE parm, initrd parm. What does SuSE=xxxx? Take a SLES9Type at the prompt: hostip=..., gateway=..., netmask ..., hostip ... autoyast=..., install=... .That should be enough. And with DHCP you don't need the hostip, gateway and netmask. parms. I don't understand your question. The infois AFAIK the autoyastfile and you configured your environment to get it from network: autoyast=nfs://192.168.1.202/nfssrc/profiles/ If you want to read a grub menu.lst over network get the grub bootfrom www.suse.de/~nashif and configure it somethink like this: color white/blue black/lightdefault 0 timeout 8 framebuffer 1 #gfxmenu (fd0)/boot/message title harddisk root (hd0) chainloader +1 title SUSE grub network disk i386 dhcp ifconfig -configfile (nd)/sles9/i386/grub/menu.lst you have to configure your tftpfor the second entry. And the grubdoesn't work with every networkcard. Jochen >>>Hans Kamm <hans753(a)hotmail.com> 01/16 8:56 pm >>> Hi, I want to install SLES9 using autoyast. Inserting a CD to get the bootloader and then I want to install via network (autoinst.xml and CDs on NFS). The kernelparameter has a limitation of 256 chars, I' ve tried to reduce the size and get still a length of 250 chars, see below: BOOT_IMAGE=linux SuSE=,1203200100,EC360BE5., initrd=initrd ramdisk_size=65536 textmode=1 splash=silent netdevice=eth0 hostip=192.168.1.201/24 gateway=192.168.1.1 autoyast=nfs://192.168.1.202/nfssrc/profiles/ install=nfs://192.168.1.202/nfssrc/sles9/ Any ideas how to bypass the liimitations? Is there a way to put a 'info' file somewhere on the network (not on floppy). Greets Hans _________________________________________________________________ Tun Sie Ihrem Rechner 'was Gutes. MSN Hotmail mit McAfee® Anti http://www.msn.de/email/antivirus/ Jetzt kostenlos anmelden! -- To unsubscribe, esuse For additional commands, esuse

2 1

Confirm Hardware Detection
by Pawel Slabiak 17 Jan '05

17 Jan '05

Hi all, i really don't know why i get the following messages after first reboot: " Confirm Hardware Detection" Yast2 will detect the following hardware: Network Cards Continue Skip I put a corect line in my install.xml, here ist a small piece of this xml file: <modules config:type="list"> <module_entry> <device>eth0</device> <module>tg3</module> <device>eth1</device> <module>tg3</module> <options></options> </module_entry> </modules> Thanks for any advice Greets Cozy Paul __________________________________________________________ Mit WEB.DE FreePhone mit hoechster Qualitaet ab 0 Ct./Min. weltweit telefonieren! http://freephone.web.de/?mc=021201

2 1

RE: [suse-autoinstall] AutoYaST-Problem after first reboot
by rab2003＠web.de 17 Jan '05

17 Jan '05

Hi, I'm installing a minimal system and a small X11 (only X an fvwm2). We added X manually to the package-list. Without the X11-Configuration by autoyast we have to setup the x-server by hand with sax/sax2. Now its done within the setup. Andreas "Suffin, Charles" <Charles.Suffin(a)stratus.com> schrieb am 11.01.05 14:04:12: > > That's great, Andreas, but you are specifying a "minimal" install, so > perhaps you shouldn't be doing anything with graphics in the first place. > If you actually want graphics, you should change this to the default or full > install (I think). > > <base>Minimal</base> > <kernel>kernel-default</kernel> > > What happens if you leave out the entire X11 section in the XML file when > you do a minimal install? > > -- Charlie > > -----Original Message----- > From: rab2003(a)web.de [mailto:rab2003@web.de] > Sent: Tuesday, January 11, 2005 7:53 AM > To: suse-autoinstall(a)suse.com > Subject: Re: [suse-autoinstall] AutoYaST-Problem after first reboot > > Hi, > > Problem is fixed! > Package "SaX2-gui" was missing in installation. > > > Andreas > > > <rab2003(a)web.de> schrieb am 11.01.05 10:43:13: ______________________________________________________________ Verschicken Sie romantische, coole und witzige Bilder per SMS! Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193

1 0

Installation Problems with SLES9 on AMD64 boxes
by Andy Kar 16 Jan '05

16 Jan '05

I'm trying to auto install SLES9 on a x86_64 box. The same procedure works on a x86 box but fails on the x86_64 box. The only difference between the two is the installation location on isolinux.cfg. Here are the problems: 1. At startup the installer says "You are trying to install 32 bit OS on a 64 bit machine". I've to press "Continue" to move to the next. I've copied the files (initrd, linux...) from the x86_64 loader CD, so I'm not sure why I'm getting the error. 2. After the config file is retrieved YAST proceeds and gets stuck on the Software installation part. The error message is "Could not set base installation: Minimal". Here's the config entry <software> <addons config:type="list"> <addon>Base-System</addon> <addon>YaST2</addon> </addons> <base>Minimal</base> </software> Thanks Andy

2 2

Re: [suse-autoinstall] SLES9: Howto bypass 256 chars boot-kernel parameter limit?
by Jochen Schaefer 16 Jan '05

16 Jan '05

Hi, I don't think you need the ramdisk_size parameter, netdevice parm, BOOT_IMAGE parm, initrd parm. What does SuSE=xxxx? Take a SLES9-CD1. Type at the prompt: hostip=..., gateway=..., netmask ..., hostip ... autoyast=..., install=... .That should be enough. And with DHCP you don't need the hostip, gateway and netmask. parms. I don't understand your question. The info-file is AFAIK the autoyast-xml file and you configured your environment to get it from network: autoyast=nfs://192.168.1.202/nfssrc/profiles/ If you want to read a grub menu.lst over network get the grub boot-floppy from www.suse.de/~nashif and configure it somethink like this: color white/blue black/light-gray default 0 timeout 8 framebuffer 1 #gfxmenu (fd0)/boot/message title harddisk root (hd0) chainloader +1 title SUSE grub network disk i386 dhcp ifconfig --server=192.168.1.1 configfile (nd)/sles9/i386/grub/menu.lst you have to configure your tftp-server for the second entry. And the grub-floppy doesn't work with every networkcard. Jochen >>>Hans Kamm <hans753(a)hotmail.com> 01/16 8:56 pm >>> Hi, I want to install SLES9 using autoyast. Inserting a CD to get the bootloader and then I want to install via network (autoinst.xml and CDs on NFS). The kernelparameter has a limitation of 256 chars, I' ve tried to reduce the size and get still a length of 250 chars, see below: BOOT_IMAGE=linux SuSE=,1203200100,EC360BE5., initrd=initrd ramdisk_size=65536 textmode=1 splash=silent netdevice=eth0 hostip=192.168.1.201/24 gateway=192.168.1.1 autoyast=nfs://192.168.1.202/nfssrc/profiles/ install=nfs://192.168.1.202/nfssrc/sles9/ Any ideas how to bypass the liimitations? Is there a way to put a 'info' file somewhere on the network (not on floppy). Greets Hans _________________________________________________________________ Tun Sie Ihrem Rechner 'was Gutes. MSN Hotmail mit McAfee® Anti http://www.msn.de/email/antivirus/ Jetzt kostenlos anmelden! -- To unsubscribe, esuse For additional commands, esuse

1 0

SLES9: Howto bypass 256 chars boot-kernel parameter limit?
by Hans Kamm 16 Jan '05

16 Jan '05

Hi, I want to install SLES9 using autoyast. Inserting a CD to get the bootloader and then I want to install via network (autoinst.xml and CDs on NFS). The kernelparameter has a limitation of 256 chars, I' ve tried to reduce the size and get still a length of 250 chars, see below: BOOT_IMAGE=linux SuSE=,1203200100,EC360BE5., initrd=initrd ramdisk_size=65536 textmode=1 splash=silent netdevice=eth0 hostip=192.168.1.201/24 gateway=192.168.1.1 autoyast=nfs://192.168.1.202/nfssrc/profiles/ install=nfs://192.168.1.202/nfssrc/sles9/ Any ideas how to bypass the liimitations? Is there a way to put a 'info' file somewhere on the network (not on floppy). Greets Hans _________________________________________________________________ Tun Sie Ihrem Rechner was Gutes. MSN Hotmail mit McAfee® Anti-Virus. http://www.msn.de/email/antivirus/ Jetzt kostenlos anmelden!

1 0

LV on MD
by "Andreas Müller" 16 Jan '05

16 Jan '05

I try to configure LV's on a softwareraid (md) of two ata-disks in autoyast. On installation apears an error, 'md device is not known'. I think my configuration is right. If I try it on a running system in yast it works. <partitioning config:type="list"> <drive> <device>/dev/hda</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <format config:type="boolean">false</format> <partition_type>primary</partition_type> <partition_id config:type="integer">253</partition_id> <raid_name>/dev/md0</raid_name> <raid_type>raid</raid_type> <size>512M</size> </partition> <partition> <format config:type="boolean">false</format> <partition_type>primary</partition_type> <partition_id config:type="integer">253</partition_id> <raid_name>/dev/md1</raid_name> <raid_type>raid</raid_type> <size>1G</size> </partition> <partition> <format config:type="boolean">false</format> <partition_type>primary</partition_type> <partition_id config:type="integer">253</partition_id> <raid_name>/dev/md2</raid_name> <raid_type>raid</raid_type> <size>max</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/hdb</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <format config:type="boolean">false</format> <partition_type>primary</partition_type> <partition_id config:type="integer">253</partition_id> <raid_name>/dev/md0</raid_name> <raid_type>raid</raid_type> <size>512M</size> </partition> <partition> <format config:type="boolean">false</format> <partition_type>primary</partition_type> <partition_id config:type="integer">253</partition_id> <raid_name>/dev/md1</raid_name> <raid_type>raid</raid_type> <size>1G</size> </partition> <partition> <format config:type="boolean">false</format> <partition_type>primary</partition_type> <partition_id config:type="integer">253</partition_id> <raid_name>/dev/md2</raid_name> <raid_type>raid</raid_type> <size>max</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/md</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/boot</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">0</partition_nr> <raid_options> <chunk_size>4</chunk_size> <parity_algorithm>left-asymmetric</parity_algorithm> <raid_type>raid1</raid_type> </raid_options> </partition> <partition> <format config:type="boolean">true</format> <mount>/</mount> <partition_id config:type="integer">130</partition_id> <partition_nr config:type="integer">1</partition_nr> <raid_options> <chunk_size>4</chunk_size> <parity_algorithm>left-asymmetric</parity_algorithm> <raid_type>raid1</raid_type> </raid_options> </partition> <partition> <format config:type="boolean">false</format> <partition_nr config:type="integer">2</partition_nr> <raid_options> <chunk_size>4</chunk_size> <parity_algorithm>left-asymmetric</parity_algorithm> <raid_type>raid1</raid_type> </raid_options> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/md2</device> <partitions config:type="list"> <partition> <lvm_group>system</lvm_group> <partition_type>primary</partition_type> <size>max</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/system</device> <is_lvm_vg config:type="boolean">true</is_lvm_vg> <partitions config:type="list"> <partition> <filesystem config:type="symbol">reiser</filesystem> <lv_name>user_lv</lv_name> <mount>/usr</mount> <size>500mb</size> </partition> </partitions> <pesize>4M</pesize> <use>all</use> </drive> </partitioning> ______________________________________________________________ Verschicken Sie romantische, coole und witzige Bilder per SMS! Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193

3 4

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

openSUSE Autoinstall January 2005