April 2004 - openSUSE Autoinstall - openSUSE Mailing Lists

root passwort, sound
by Dominic Lukwata 13 Apr '04

13 Apr '04

Hi all, we autoinstall Suse 9.0. It work better and better but there still some problems: 1. we have not succeeded to set a root passowrd per autoinstall. 2. The sound module makes post installation after the first log in and the Master volume ist at zero. We use the onboard sound on the motherboard ASUS P4P800 Delux Hier ist the sound section in the controll file <sound> <autoinstall config:type="boolean">true</autoinstall> <modules_conf config:type="list"> <module_conf> <alias>snd-card-0</alias> <model>82801DB-ICH4, Intel</model> <module>snd-intel8x0</module> <options> <snd_ac97_clock>0</snd_ac97_clock> <snd_enable>1</snd_enable> <snd_index>0</snd_index> </options> <unique_key>uniq.virtual</unique_key> </module_conf> </modules_conf> <volume_settings config:type="list"> <listentry> <Master config:type="integer">75</Master> </listentry> </volume_settings> </sound> Does any one has any hint how to fix these? Thanks Dominic

3 3

Helge Koehn/Germany/IBM is out of the office.
by Helge Koehn 09 Apr '04

09 Apr '04

I will be out of the office starting 04/08/2004 and will not return until 04/14/2004. I will respond to your message when I return.

1 0

Re: SuSE - Yast2 Autoinstall CD for SLES8
by Robert Pollak 09 Apr '04

09 Apr '04

On Thu, 2004-04-08 at 09:30, s-steins(a)web.de wrote in private mail: > (refering to: http://lists2.suse.com/archive/suse-autoinstall/2004-Feb/0020.html) > > have you now been successful creating a single SLES8-YaST2-Autoinstall-CD from the > CD-Rom-Sources of the 4 CDs which came with the SLES-box? Hello, I'm afraid no. I only managed to create a version of the SLES8-CD (dependent on hd type: ide or scsi) containing the control file. This makes it possible to install SLES8 without floppy with two cd changes and one click of "OK". (SP3 is not necessary for this.) I did not manage to collect the needed rpms on one cd. According to Anas Nashif, "Create iso image" from autoyast2 cannot be used for this, because it only processes packets of one software source. (Since "Create iso image" started working in SP3, we have got three sources: UnitedLinux, SLES8, SP3.) The following approaches were unsuccesful so far: - Collecting the needed packets in one directory and using this as software source for "Create iso image". - Copying rpms from UnitedLinux-cd1 into the custom version of the sles8 cd; changing the package files entries s.t. the rpms are found at the new location. The next thing I had planned was to try it the other way round: to include rpms from sles8 into the UL cd. This could be easier, since the UL cd only contains one "product". But then the task was assigned to a coworker, and I think nothing has happened since then. Let me (and the list) know about your progress - I wish you good luck. -- Robert Pollak GPG Key ID: 748646AD

1 1

autoinst.xml on self-made cd
by Manuel.Laesser＠telekurs.com 07 Apr '04

07 Apr '04

Hello, sorry to bother you again and again. I'm using SLES8 with autoyast2-2.6.44-7 and autoyast2-installation-2.6.44-7. I think this is the latest version for SLES8 (comming with SP3). I copied autoinst.xml to the root of my self-made CD-ROM and I'm using the following parameter in isolinux.cfg # autoyast label autoyast kernel linux append initrd=initrd ramdisk_size=65536 autoyast=default instmode=cd usedhcp=0 textmode=1 If you use parameter "autoyast=default" YaST2 will look for autoinst.xml in the following three places (according to Anas Nashif PDF SLES8 - Automatic Linux Installation and Configuration with YaST2) : 1. the root directory of the floppy disk 2. the root directory of the installation medium (CD-ROM in my case) 3. the root directory of the initial ram disk used to boot the system Cool......unfortunately it doesn't work at all in my environment. I tried with "autoyast=file:/autoinst.xml", "autoyast=file://autoinst.xml", "autoyast=default" I always got this bloody control menu where it asks for the location of the autoinst.xml! From there I could choose http, device, floppy, nfs....but I didn't manage to access the cdrom. If I insert a floppy with my autoinst.xml in the root, the installation is proceeding. I also can edit isolinux.cfg with "autoyast=floppy://autoinst.xml" and it'll find autoinst.xml. Why do I get always very nice and well meant hints from the autoinstall mailing list telling me that the are using "...autoyast= default instmode=cd..." and everything is working fine. Does this have a coherence that I'm using SLES8 with autoyast2-2.6.44-7 and most of people Suse x.x with the newest autoyast2 autoyast2-2.8.14-20 or so..... I'm really stumped.... Any comment is welcome. Regards Manuel p.s. I'll send a box of the finest original swiss chocolate to the one who can give me the right tip to solve this problem...... ;-)) ----------------------------------------------------------- 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 -----------------------------------------------------------

2 4

lvm: autoyast complains about wrong lvcreate parameters
by Mathias Pietsch 07 Apr '04

07 Apr '04

hello. when i run an autoyast profile (for suse 8.2) with this lvm-configuration: <lvm config:type="list"> <lvm_group> <lvm_name>HomeVol</lvm_name> <pesize>4M</pesize> <logical_volumes config:type="list"> <lv> <lv_name>Linux_home_lv</lv_name> <lv_size>21296</lv_size> <lv_fs>ext3</lv_fs> <lv_mount>/export</lv_mount> </lv> </logical_volumes> </lvm_group> </lvm> i get the following errors: 1) yast says that on /export are some megabytes of disk space missing and i should deselect some packages (allthough nothing at all will be installed there during installation). and when i continue ... 2) yast complains about wrong lvcreate parameters. but when i run "lvcreate --name Linux_home_lv --size 21296 HomeVol" (these are exactly the parameters that should be used by autoyast, too) manually, the command succeeds and i can continue and finish the installation successfully. from the last line of /var/log/YaST2/y2log i can read that yast thinks the lv_size parameter is 0. (but i have to admit that i hardly can understand the content of these y2log* files). has anyone a clue about what goes wrong here? thanks in advance mp -- ---------------------------------------------------------------- Mathias Pietsch Network and System Administration - Neuroimage Nord, Bldg S10, 3rd Floor, Room 301 Department of Neurology Universitätsklinikum Hamburg-Eppendorf Martinistr. 52 D-20246 Hamburg Germany - Phone: +49-40-42803-8673 Fax: +49-40-42803-9955 Mail: m.pietsch(a)uke.uni-hamburg.de ---------------------------------------------------------------- GnuPG/PGP (http://www.gnupg.org) key id: 644112F2, fingerprint: E37B 77F4 87C7 6309 758D F507 A93C 207C 6441 12F2 ---------------------------------------------------------------- Please avoid sending me Word, Excel or PowerPoint attachments. (see http://www.fsf.org/philosophy/no-word-attachments.html) ----------------------------------------------------------------

1 0

Wireless and Suse 9.0
by Mike Wilson 05 Apr '04

05 Apr '04

New to Linux. Trying to get my Linksys WUSB V2.5 to work with Suse.I tried linux-wlan.org and others. I have missed something somewhere. It is USB and appears to use the prism drivers. I get all that in the configuration, however it never really connects

1 0

Automated install from hard disk
by Peter Jenkins 05 Apr '04

05 Apr '04

All, I'm trying to automate an install where the install media is on a partition of hard disk. Google has been good to me and I have worked out pretty much how to do this, but for one small part. I'm unsure of the correct syntax for "info" file that I've created and placed in the initrd. I've found this: <http://www.suse.de/~nashif/autoinstall/9.0/html/x1808.html> Which should be all I need, but as yet no combination gives me a full automated install. The best info file I've managed is: instmode: hd partition: sda2 rootimage: device://sda2/boot/root installdir: device://sda2 textmode: 1 autoyast: file:///info This fails initially but I'm able to traverse the menus and point the installer to the correct disk partition etc and then off it goes and finds the autoyast file. You'll notice the "device://" in some of the parameters, I've also tried others including "hd://", "file:///" etc. I'd really like to hear from anyone that knows what I'm talking about who can point me in the right direction. Thanks in advance, Peter. -- Peter Jenkins Design & Engineering Team Professional Services EMEA Sun Microsystems Ltd

1 0

AW: [suse-autoinstall] Antwort: RE: [suse-autoinstall] Antwort: A W: [suse-autoinstall] Antwort: [ suse-autoinstall] autoinst
by Lenz, Fabian 03 Apr '04

03 Apr '04

Hello, That was my second question, but now i see that you have edit the isolinux.cfg! instmode=cd is right, my isolinux.cfg looks so # install label linux kernel linux append initrd=initrd ramdisk_size=65536 splash=silent showopts autoyast=default Language=de_DE UseDHCP=0 InstMode=cd and it works fine! Regards Fabian Lenz Azb Fachinformatiker für Systemintegration Deutsche Telekom AG Telekom Training BBi Koblenz Hausadresse: Blücherstr. 6-8, 56073 Koblenz Postanschrift: Postfach 9100, 56065 Koblenz Telefon (mobil): +49 (160) 3565851 E-Mail: mailto:Fabian.Lenz@telekom.de Intranet: http://ttc.telekom.de/ -----Ursprüngliche Nachricht----- Von: Manuel.Laesser(a)telekurs.com [mailto:Manuel.Laesser@telekurs.com] Gesendet: Donnerstag, 1. April 2004 17:02 An: suse-autoinstall(a)suse.com Betreff: [suse-autoinstall] Antwort: RE: [suse-autoinstall] Antwort: AW: [suse-autoinstall] Antwort: [ suse-autoinstall] autoinst 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 -----------------------------------------------------------

3 2

RE: [suse-autoinstall] autoinst.xml on self-made cd
by Ness, Todd 02 Apr '04

02 Apr '04

We spent yesterday trying to get autoinst.xml file to be recognized in / of the cdrom as well, no luck. With package version autoyast2-installation-2.6.41-62 I have made reading xml files from a /profiles directory of the initrd work, with a autoyast=file:/profiles/filename.xml in the isolinux.cfg file. Todd -----Original Message----- From: Manuel.Laesser(a)telekurs.com [mailto:Manuel.Laesser@telekurs.com] Sent: Friday, April 02, 2004 11:11 AM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] autoinst.xml on self-made cd Hello, sorry to bother you again and again. I'm using SLES8 with autoyast2-2.6.44-7 and autoyast2-installation-2.6.44-7. I think this is the latest version for SLES8 (comming with SP3). I copied autoinst.xml to the root of my self-made CD-ROM and I'm using the following parameter in isolinux.cfg # autoyast label autoyast kernel linux append initrd=initrd ramdisk_size=65536 autoyast=default instmode=cd usedhcp=0 textmode=1 If you use parameter "autoyast=default" YaST2 will look for autoinst.xml in the following three places (according to Anas Nashif PDF SLES8 - Automatic Linux Installation and Configuration with YaST2) : 1. the root directory of the floppy disk 2. the root directory of the installation medium (CD-ROM in my case) 3. the root directory of the initial ram disk used to boot the system Cool......unfortunately it doesn't work at all in my environment. I tried with "autoyast=file:/autoinst.xml", "autoyast=file://autoinst.xml", "autoyast=default" I always got this bloody control menu where it asks for the location of the autoinst.xml! From there I could choose http, device, floppy, nfs....but I didn't manage to access the cdrom. If I insert a floppy with my autoinst.xml in the root, the installation is proceeding. I also can edit isolinux.cfg with "autoyast=floppy://autoinst.xml" and it'll find autoinst.xml. Why do I get always very nice and well meant hints from the autoinstall mailing list telling me that the are using "...autoyast= default instmode=cd..." and everything is working fine. Does this have a coherence that I'm using SLES8 with autoyast2-2.6.44-7 and most of people Suse x.x with the newest autoyast2 autoyast2-2.8.14-20 or so..... I'm really stumped.... Any comment is welcome. Regards Manuel p.s. I'll send a box of the finest original swiss chocolate to the one who can give me the right tip to solve this problem...... ;-)) ----------------------------------------------------------- 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: Antwort: [suse-autoinstall] AW: Antwort: AW: [suse-autoinstal l] Antwort: RE: [suse-autoinstal l] Antwort: A W: [suse-autoinstall] Antw ort: [ suse-autoinstall] autoinst
by Lenz, Fabian 02 Apr '04

02 Apr '04

Hello! The packages are on Suse Linux CD1 in /suse/noarch/! Change the old packages with the new from the CD, there is the package autoyast..., autoyast-utilities and autoyast-installation, change all! Fabian Lenz Azb Fachinformatiker für Systemintegration Deutsche Telekom AG Telekom Training BBi Koblenz Hausadresse: Blücherstr. 6-8, 56073 Koblenz Postanschrift: Postfach 9100, 56065 Koblenz Telefon (mobil): +49 (160) 3565851 E-Mail: mailto:Fabian.Lenz@telekom.de <mailto:Fabian.Lenz@telekom.de> Intranet: http://ttc.telekom.de/ <http://ttc.telekom.de/> -----Ursprüngliche Nachricht----- Von: Manuel.Laesser(a)telekurs.com [mailto:Manuel.Laesser@telekurs.com] Gesendet: Freitag, 2. April 2004 11:53 An: autoinstall_suse(a)telekurs.com Cc: Lenz, Fabian Betreff: Antwort: [suse-autoinstall] AW: Antwort: AW: [suse-autoinstall] Antwort: RE: [suse-autoinstal l] Antwort: A W: [suse-autoinstall] Antwort: [ suse-autoinstall] autoinst Hello Is it possible to upgrade autoyast2-2.6.44-7 from SLES8 to Version autoyast2-2.8.14-20 from Suse 9.0? I just found some information about autoyast2 2.7.19 (Suse 8.2) which would fix probably my problem with /boot and ext2 instead of ext3. 23 May 2003 RPM autoyast2 2.7.19 (noarch) 673 kB This update fixes the following: -cloning systems with LVM configuration and -execution of perl post-install scripts. -Now it is possible to create a /boot partition as ext3 Additionaly this package has some corrections for the documentation Would I only have to upgrade this package on my Repository Server or are there any dependencies whith package autoyast2? Unfortunately I can't find package 2.8.14 under Suse Linux 9.0. Where would I get this package and all dependencies if necessary? Thank you for your Answer. 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: Antwort: AW: [suse-autoinstall] Antwort: RE: [suse-autoinstal l] Antwort: A W: [suse-autoinstall] Antwort: [ suse-autoinstall] autoinst
by Lenz, Fabian 02 Apr '04

02 Apr '04

I use the newest version of Autoyast, autoyast2-2.8.14-20, try it with this version, with older version i had have many problems. ;-) Fabian Lenz Azb Fachinformatiker für Systemintegration Deutsche Telekom AG Telekom Training BBi Koblenz Hausadresse: Blücherstr. 6-8, 56073 Koblenz Postanschrift: Postfach 9100, 56065 Koblenz Telefon (mobil): +49 (160) 3565851 E-Mail: mailto:Fabian.Lenz@telekom.de <mailto:Fabian.Lenz@telekom.de> Intranet: http://ttc.telekom.de/ <http://ttc.telekom.de/> -----Ursprüngliche Nachricht----- Von: Manuel.Laesser(a)telekurs.com [mailto:Manuel.Laesser@telekurs.com] Gesendet: Freitag, 2. April 2004 08:25 An: Lenz, Fabian Cc: autoinstall_suse(a)telekurs.com Betreff: Antwort: AW: [suse-autoinstall] Antwort: RE: [suse-autoinstall] Antwort: A W: [suse-autoinstall] Antwort: [ suse-autoinstall] autoinst Hello Fabian Thanx for you help. That's really strange! Why does your isolinux.cfg with "instmode=cd" work? Which version of autoyast do you use? I'm using autoyast2-2.6.44-7 and after the licence agreement I always got the menu to specify the location of the autoinst.xml......anyway, I'll try with "autoyast=file:/autoinst.xml" in my case, hope this will solve MY problems.... :-( 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 -----------------------------------------------------------

2 1

AW: [suse-autoinstall] AW: Antwort: AW: [suse-autoinstall] Antwor t: RE: [suse-autoinstal l] Antwort: A W: [suse-autoinstall] Antwort: [ su se-autoinstall] autoinst
by Lenz, Fabian 02 Apr '04

02 Apr '04

OK, this was the newest version 5 weeks ago, i don´t know if there is a newer version! Fabian Lenz Azb Fachinformatiker für Systemintegration Deutsche Telekom AG Telekom Training BBi Koblenz Hausadresse: Blücherstr. 6-8, 56073 Koblenz Postanschrift: Postfach 9100, 56065 Koblenz Telefon (mobil): +49 (160) 3565851 E-Mail: mailto:Fabian.Lenz@telekom.de Intranet: http://ttc.telekom.de/ -----Ursprüngliche Nachricht----- Von: Lenz, Fabian Gesendet: Freitag, 2. April 2004 08:35 An: Manuel.Laesser(a)telekurs.com; suse-autoinstall(a)suse.com Betreff: [suse-autoinstall] AW: Antwort: AW: [suse-autoinstall] Antwort: RE: [suse-autoinstal l] Antwort: A W: [suse-autoinstall] Antwort: [ suse-autoinstall] autoinst I use the newest version of Autoyast, autoyast2-2.8.14-20, try it with this version, with older version i had have many problems. ;-) Fabian Lenz Azb Fachinformatiker für Systemintegration Deutsche Telekom AG Telekom Training BBi Koblenz Hausadresse: Blücherstr. 6-8, 56073 Koblenz Postanschrift: Postfach 9100, 56065 Koblenz Telefon (mobil): +49 (160) 3565851 E-Mail: mailto:Fabian.Lenz@telekom.de <mailto:Fabian.Lenz@telekom.de> Intranet: http://ttc.telekom.de/ <http://ttc.telekom.de/> -----Ursprüngliche Nachricht----- Von: Manuel.Laesser(a)telekurs.com [mailto:Manuel.Laesser@telekurs.com] Gesendet: Freitag, 2. April 2004 08:25 An: Lenz, Fabian Cc: autoinstall_suse(a)telekurs.com Betreff: Antwort: AW: [suse-autoinstall] Antwort: RE: [suse-autoinstall] Antwort: A W: [suse-autoinstall] Antwort: [ suse-autoinstall] autoinst Hello Fabian Thanx for you help. That's really strange! Why does your isolinux.cfg with "instmode=cd" work? Which version of autoyast do you use? I'm using autoyast2-2.6.44-7 and after the licence agreement I always got the menu to specify the location of the autoinst.xml......anyway, I'll try with "autoyast=file:/autoinst.xml" in my case, hope this will solve MY problems.... :-( 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

RE: [suse-autoinstall] Single Disk Network Install - Not Network Boot
by discip＠pjm.com 01 Apr '04

01 Apr '04

Ok, how might I do this with a CD? Where do I put the info file? Which .iso image should I start with to modify? Thanks, Paul -----Original Message----- From: Anas Nashif [mailto:nashif@suse.de] Sent: Monday, January 26, 2004 8:09 PM To: discip(a)pjm.com Cc: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] Single Disk Network Install - Not Network Boot Hi, single floppy disk network install is not possible. You need at least 2 floppies. You need a CD for this. And by the way, even with rh kickstart you cant do that in recent releases. Anas discip(a)pjm.com wrote: > Hey, > I am trying to do an NFS install and would really like to get > everything I need to get this to work onto a single diskette (or CD if > it's absolutely necessary). I'd like to just pop in a floppy, turn on > the machine and have it boot, restart, and be ready to go. As it > stands now, I have all the config setup (info file and autoinst.xml), > but I need to swap 3 floppies first for modules and stuff. Can I get > these all on a single disk? I can do this with Redhat's kickstart. > Any help would be greatly appreciated as I will eventually need to > hand this process off to some less informed individuals who I don't > want to have to mess with lots of disks,etc. > > Thanks a lot, > Paul > -- 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] Antwort: RE: [suse-autoinstall] Antwort: A W: [suse-autoinstall] Antwort: [ suse-autoinstall] autoinst
by Ness, Todd 01 Apr '04

01 Apr '04

Let me know what you come up with, it would be easier to just add autoinst.xml to the root of the CD instead of imbedding in the initrd. -----Original Message----- From: Manuel.Laesser(a)telekurs.com [mailto:Manuel.Laesser@telekurs.com] Sent: Thursday, April 01, 2004 8:02 AM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] Antwort: RE: [suse-autoinstall] Antwort: AW: [suse-autoinstall] Antwort: [ suse-autoinstall] autoinst 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: Re: [suse-autoinstall] Two type network adapters problem
by george_king 01 Apr '04

01 Apr '04

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

2 1

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