Hello, is there really no way to have the ethernet adapter detected automatically so that there will be the entry for my ethernet interface in /etc/modules.conf again? Since I create my CD according to Anas instruction it won't be inserted automatically.
Thank you for you help.
Regards Manuel
----- Weitergeleitet von Manuel Lässer/TK Services/Telekurs am 17.04.2004 13:32 -----
Manuel.Laesser@telekurs.com 07.04.2004 21:52
An Anas Nashif nashif@suse.de Kopie suse-autoinstall@suse.com Thema [suse-autoinstall] Antwort: Re: [suse-autoinstall] autoinst.xml on self-made cd
Hello Anas Thank you so much for this hint! It really works if you follow all your instruction below step by step. There are a couple of things that changed if I compare it with the installation from my repository-server.
1. at the stage when the license agreement is displayed, there is a 10 second countdown and after this the installation starts. How can I disable
this timer so you really have to press enter to continue?
2. no module will be loaded for the network interface(s) because there is no entry in /etc/modules.conf for eth0. If I install the server from my repository-server the ethernet interface eth0 will be discovered automatically and I've got an alias set for my eth0 in /etc/modules.conf. Is there a way, I can detect all ethernet interfaces and insert them all in /etc/modules.conf even I install my server from the cd as described by Anas below?
Thank you for your answer.
Regards Manuel
----------------------------------------------------------- Telekurs Services Hardturmstrasse 201, 8005 Zürich Phone : +41 1 279 44 24 Fax : +41 1 279 34 44 mailto : manuel.laesser@telekurs.com -----------------------------------------------------------
Anas Nashif nashif@suse.de 03.04.2004 02:59
An Manuel.Laesser@telekurs.com Kopie suse-autoinstall@suse.com Thema Re: [suse-autoinstall] autoinst.xml on self-made cd
Hi, I have just tried reproducing this, and it works for me as expected.
- unpack ISO/CD of SLES8 into a directory /tmp/SLES - unpack ISO/CD of SP3 into a directory /tmp/SP3 - cp /tmp/SP3/driverupdate /tmp/SLES - cp /tmp/SP3/boot/loader/linux /tmp/SLES/boot/loader - cp /tmp/SP3/boot/loader/initrd /tmp/SLES/boot/loader - Edit /tmp/SLES/boot/loader/isolinux.cfg and add autoyast=default instmode=cd - Copy autoinst.xml into /tmp/SLES
Create ISO image Boot and it works.
Anas
Manuel.Laesser@telekurs.com wrote:
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) :
- the root directory of the floppy disk
- the root directory of the installation medium (CD-ROM in my case)
- 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@telekurs.com
Manuel.Laesser@telekurs.com wrote:
Hello, is there really no way to have the ethernet adapter detected automatically so that there will be the entry for my ethernet interface in /etc/modules.conf again? Since I create my CD according to Anas instruction it won't be inserted automatically.
I didn't follow the discussion about creating the CD, but there is a way: Insert all possible network modules via the info file. We use a self-created initrd (for installing via pxe) which contains an info file with entries like this:
insmod 3c90x insmod e1000 insmod bcm5700 ...
This makes autoyast try all the modules, and the one that matches will be entered in modules.conf automatically. This works on SuSE 9.0, no idea about earlier versions.
cu, Frank
Hello Frank Thank you for your answer. Just some more questions. What is the exact name of this file? Where do I have to put it? I only found a module.config file in /modules of the unpacked initrd, but this doesn't seem to be the file you are talking about.
Thank you very much for your help.
Manuel
Manuel.Laesser@telekurs.com wrote:
Hello Frank Thank you for your answer. Just some more questions. What is the exact name of this file? Where do I have to put it? I only found a module.config file in /modules of the unpacked initrd, but this doesn't seem to be the file you are talking about.
No, I'm talking about the "configuration file" that feeds information to linuxrc. Look at chapter 7.3.1 from the Autoyast Doku for SuSE 9.0. This file is named "info" and you can put it on a floppy if you boot from a normal cdrom e.g., or if you plan to install everything via network, e.g. using pxe like we do it, you can put it into the intird that will be transfered with pxe.
We use a pxelinux.cfg (see chapter 5 of the docu) with
label linux kernel vmlinuz.install append initrd=initrd rw ramdisk_size=65536 apm=power-off
and for the "initrd" in the tftpboot directory, we unpacked the initrd from the SuSE CD and put out own "info" file into the root of the initrd before packing it again.
The info file looks like this:
# Initial Info file to boot over network.
###################################################### # general stuff Language: de_DE Display: color Keytable: us
############################################### # which network device do we use? Netdevice: eth0
############################################### # where do we install from install: nfs://<our ip hidde>/rpm-export/i586/9.0/SuSE/ autoyast: nfs://<our ip hidden>/rpm-export/autoyast/9.0/
############################################### # remote control VNC: 1 VNCPassword: <whatever we use there ;-)>
############################################### # which modules do we need
# SCSI Controllers insmod scsi_mod insmod sd_mod insmod aic7xxx insmod aic79xx insmod gdth insmod qla1280 # IBM serveRaid-Controller for xSeries insmod ips
# network controller at last so that link stays up until # the bootp request is made. insmod 3c90x insmod e1000 insmod bcm5700
# insmod bcm5700 line_speed=100 auto_speed=0 full_duplex=1
# END FILE
Have fun :-) cu, Frank
autoinstall@lists.opensuse.org
-
Frank Steiner -
Manuel.Laesser＠telekurs.com