May 2002 - openSUSE Autoinstall - openSUSE Mailing Lists

Monitor/Sound configuration, keyboard layout, kdm
by Andreas Weber 11 Jun '02

11 Jun '02

Hi, when I specify the monitor using the configuration system, this is ignored during installation. It seems that the monitor is detected via DDC and only VESA standard modes are used. Does anyone know how to fix this? The <monitor> section of my config file looks is as follows: <monitor> <display> <max_hsync config:type="integer" >94</max_hsync> <max_vsync config:type="integer" >160</max_vsync> <min_hsync config:type="integer" >30</min_hsync> <min_vsync config:type="integer" >48</min_vsync> </display> <monitor_device>ECOMO 19H98</monitor_device> <monitor_vendor>ELSA</monitor_vendor> </monitor> I also configured a sound card using the configuration system. The sound card is working after installation but when logging in using kde for the first time, the SuSE hardware detection comes up, detecting new sound hardware. I could turn off the hardware detection, but this isn't really a solution... The third thing I can't get to work is installing the system with language english but with a german keyboard layout. I always get the english keyboard layout when using english language. To get a german keyboard layout, I have to configure language 'Deutsch', resulting in <language>de_DE</language>. I use kdm as my login manager. After installation is done, kdm starts up, but configuration is wrong (wrong title: SuSE Linux 7.3.99, wrong list of session types). This can be fixed by an additional run of SuSEconfig after installation is done, running it in a post-script dos not work. Is there a workaround for this, except generating kdmrc manually? Another thing which doesn't work: With the following section in the config file, the system should ask for confirmation before doing anything, shouldn't it? <report> <confirm config:type="boolean" >true</confirm> <errors> <log config:type="boolean" >true</log> <show config:type="boolean" >true</show> <timeout config:type="integer" >15</timeout> </errors> <messages> <log config:type="boolean" >true</log> <show config:type="boolean" >true</show> <timeout config:type="integer" >5</timeout> </messages> <warnings> <log config:type="boolean" >true</log> <show config:type="boolean" >true</show> <timeout config:type="integer" >5</timeout> </warnings> </report> I have never had to confirm installation so far... Regards, Andreas

2 2

How to creat a single boot floppy
by Jibin Huang 31 May '02

31 May '02

Hi, all: I try to install SuSE 8.0 from NFS server. But I can´t find the way to build a single boot floppy for the autoinstall procedure. I need two modules for the hardware(3c59x and aic7xxx) , and put the profile in NFS server. Could somebody tell me, what should I do? Regards Jibin

1 0

Re: [suse-autoinstall] Autoinstall with PXE
by Jörgen Karlsson 31 May '02

31 May '02

>> > > I always get the "Insert modules Disk 3" when running with > > autoyast=nfs://172.16.100.1/opt/suse > > set on kernel cmdline. Is this because yast2 cannot find the modules it > > need? Or does it always ask > > this question? How do I get past it? (our systems only has a serial > > console, no floppy, no cdrom). > What do you have in autoyast=nfs://172.16.100.1/opt/suse ? If you have > copied the CDs to this directory and you wish to install over NFS, you > should use install=nfs://172.16.100.1/opt/suse This is my commandline. init=/linuxrc rw autoyast=nfs://172.16.100.1/opt/SuSE/main.xml install=nfs://172.16.100.1/opt/SuSE It looks like linuxrc cannot find any modules on the ramdisk. Adding root=/dev/ram0 does not help either. Last out messages from kernel : : RAMDISK: Compressed image found at block 0 Uncompressing.........................................done. Freeing initrd memory: 65536k freed VFS: Mounted root (minix filesystem). Freeing unused kernel memory: 120k freed Moving into tmpfs... done. ramdisk /dev/ram0 freed >>> SuSE installation program v1.3 (c) 1996-2002 SuSE Linux AG <<< Starting hardware detection... Activating usb devices... done Searching for infofile...... /Jörgen Karlsson

3 5

console speed
by Jörgen Karlsson 31 May '02

31 May '02

How do you set the serial speed yast2 uses? Bios, terminal, is set to 38400. Yast2 switches to 115200 during installation. Kernel cmd includes console=ttyS0,38400 but yast2 don't get it. Very annoying as we need our settings at 38400 /Jörgen Karlsson

1 0

Antwort: [suse-autoinstall] Single boot floppy - solved
by Andreas Rother 31 May '02

31 May '02

Phone : unbekannt / Fax : unbekannt / Mobile : unbekannt "Andreas Rother" <Andreas.Rother@e An: suse-autoinstall(a)suse.com plus.de> Kopie: Thema: [suse-autoinstall] Single boot floppy 29.05.2002 10:43 > If I try to mount manually on console <F9> with the command "mount > /var/adm/mount/suse/images/root /mnt -o loop" I get the error message: > "mount: invalid number of arguments" These error messages were cause by the cramfs module. The module was build for a 2.4.17-4GB kernel and refused to work with the install kernel. I copied the module from a running 8.0 and now it works. Kind regards, Andreas -- Andreas Rother - E-Plus Mobilfunk GmbH & Co. KG

1 0

Single boot floppy
by Andreas Rother 29 May '02

29 May '02

Hi all! I try to build a single boot floppy for the autoinstall procedure. As the hardware is quite similar (i.e all nodes have 3com NICs), I'm quite annoyed by the fact, that I have to use three floppies until the automatic installation starts. I use an install server (NFS) and profiles depending on the client ip (gethostip). After erasing needless things like memtest and suselogo and adding to modules (reiserfs.o and 3c59x.o) to the initrd, I still don't have enough space on the floppy for all data. So I reduced the kernel by creating a special installation kernel that lacks of ISDN, sound, v4l, IrDA etc. Now everything fits onto one floppy, but the autoinstall process hangs at the point where the root image is mounted from the NFS sever by the client. >From the log file on console <F3>: ---8<--- OK, going to mount 0.0.0.0:/home/install auto2_net_dev: 464 NFS mount ok. inst_check_instsys:780 ramdisk_ig = 0 setfont lat1-16.psfu (map none) Setting up localhost...done going fot automatic install mount: /var/adm/mount/suse/images/root: we need a loop device mount: using /dev/loop0 mount: /dev/loop0: No such device ---8<--- I've doublechecked that the network works, the installation sources are mounted and that the kernel has "loop device" enabled. If I try to mount manually on console <F9> with the command "mount /var/adm/mount/suse/images/root /mnt -o loop" I get the error message: "mount: invalid number of arguments" Any hints? Has anyone succeeded in building such a bootdisk? Kind regards, Andreas -- Andreas Rother - E-Plus Mobilfunk GmbH & Co. KG

1 0

Re: [suse-autoinstall] YAST2 - using netdevice=eth1
by Hella.Breitkopf＠varetis.de 24 May '02

24 May '02

Anas Nashif <nashif(a)suse.de> [22.05.2002 04:45]: >* Hella.Breitkopf(a)varetis.de <Hella.Breitkopf(a)varetis.de> [May 21. 2002 23:12]: >> Hi List, hi Anas, >> >> Anas Nashif's great documentation of his tool AutoYast2 mentions this: >> >> Putting this to the bootcd kernel commandline, I expected the use of >> network device "eth1" for network setup (with dhcp): >> >> linux netdevice=eth1 install=nfs://1.2.3.4/x/suse8.0 >> autoyast=nfs://1.2.3.5/y/auto.xml >> >> Unluckily the information of the "netdevice" keyword seems to be ignored: >> ----- >> Trying to activate eth0 >> Setting up localhost...done >> timed out waiting for a valid DHCP server response >> >> Sending DHCP request to eth0... no/incomplete answer >> Ok, that didn't work; see if we can activate another network device... >> No further network cards found; giving up. >> ----- > >Does linuxrc in this case actually loads both network devices periot to >sending the DHCP request... Previous to the run with eth0 there is an "empty" run. There is no try with eth1. Since on my machines both devices are using the same module, the loading of the correct module means both devices are available .. IIRC we've no "ifconfig -a" at that moment, but /proc/net/dev shows both interfaces. (But eth1 is not up). > >> If I do a "manual Installation", I *can* choose between two >> network devices. And fetching dhcp information and the following >> installation from "eth1" works. >> (An installation over "eth0" works, too - if there is a cable. >> But there are good reasons to use eth1 in this case. ) >> >> Other parameters (I tried e.g. ip,netmask,gateway) work as expected, so why >> netdevice doesn't? > >We are investigating.... >> >> Hella - my next boot cd should include that. >> (Somebody interested in a description, how to build a crude boot cd >> for network installation?) >> > >Building a boot CD will be part of the next release and would be >provided as a replacement for similar functionality available with >alice. Yes, that would quite nice and usefull. >Are you interested in a description or are you offering one...? If you >have one, that might help me while putting the docs for next release :-) I'm offering. I've to document the stuff I do, anyway. But it's a crude not very elegant solution. (So, yes, I'd be interested in a *better* description, too.) > >Regards, >Anas Regards, Hella

2 1

Autoinstall with PXE
by Jörgen Karlsson 23 May '02

23 May '02

Hi, We are currently using PXE to autoinstall (kickstart) our RedHat systems. Now we are switching to SUSE. I can't figure out what files to include in a boot image (initrd) to use for PXE boot/install. I have tried the kernel in suse/images/boot/linux and the image in suse/images/boot/initrd. Is this the correct ones? I always get the "Insert modules Disk 3" when running with autoyast=nfs://172.16.100.1/opt/suse set on kernel cmdline. Is this because yast2 cannot find the modules it need? Or does it always ask this question? How do I get past it? (our systems only has a serial console, no floppy, no cdrom). Maybe it should be enough to add all modules I need to /modules. Especially the ones from disk 3,4,5,6.... ? How does yast2 determine its ip address during installation? If it is not set in linuxrc.config or on kernel cmdline does it try dhcp by default? Can yast2 use the server ip in the dhcp response as ip for an nfs server installation? And use the boot filename in same response as path to autoinst.xml? It would be nice you didn't have to specify any ip specifics (or server paths) on either kernel cmdline and linuxrc.config. Yast should be able to pick up everything from the dhcp file. Or do I have to fix the PXE bootstrap loader to supply this information? /J Karlsson

2 1

HOWTO Create a Yast2 Autoinstall Custom CD for Network Installation (long)
by Hella.Breitkopf＠varetis.de 22 May '02

22 May '02

* CREATING AN AUTOINSTALLATION CD FOR AUTOYAST2 NETWORK INSTALLATION * V 0.001 - draft - hella.breitkopf(a)varetis.de For SuSE version: SuSE 8.0 (This description is not validated, yet. No guarantee, that it works for you.) Objective: Fully unattended installation - boot from cd, fetch installation source and installation description ("control file") from your local network You'll need: 1) NFS Server with a copy of the DVD installation source (not described here - more infos in the autoyast2 documentation) In my example: 192.168.0.10 with /install/suse8.0 2) NFS Server with a XML installation control file (not described here) In my example: 192.168.0.5 with /path/1.xml (You could try to refine this with hex-ip-named.xml's and the like, see chapter 5.2 of AutoYast2 documentation. And of course, if you keep your xml files on http or tftp, it should work too.) 3) A working DHCP server (not described here) 4) SuSE 8.0 boot cd (CD1) 5) Linux machine (I did it on SuSE 7.3) with package "mkisofs" and enough free hard disk space (2 to 3 times 640 kbytes) 6) root password on that system, or sudo rights to mount stuff on all locations .. 7) One unused system to test the auto-installation It'll only work on machines which can boot from CD, the network card should be supported .. (try a manual installation with nfs source) I) Test your bootprompt line Boot CD1 in your test system and type as kernel options following line linux autoyast=nfs://192.168.0.5/path/1.xml install=nfs://192.168.0.10/install/suse8.0 Remark1 : You don't have to type in "linux" Remark2: If you've got a German keyboard connected: "=" is on "´"(Akzent) , ":" is on "ö", "/" is on "-" This should install all things you've configured in your xml file. (Tip: Start with a minimal system - It's installed much faster.) If it works, proceed to step II .. II) Prepare CD Contend create a "working directory", I named mine "bootmedia": ~> mkdir bootmedia ~> cd bootmedia ~/bootmedia> * Get an original iso Image * We steal it from the SuSE Installation CD: ~/bootmedia> dd if=/dev/hdc of=susecd1.orig.iso ~/bootmedia> mkdir susecd1 ~/bootmedia> sudo mount -o loop ./susecd1.orig.iso ./susecd1 * Prepare the content for your own iso image * ~/bootmedia> mkdir autoinst-master ~/bootmedia> tar -C susecd1 -cf - . | tar -xvf - -C autoinst-master We need to change things, so make all files writable: ~/bootmedia> chmod +w -R autoinst-master We don't need the RPM sources, we fetch them from the network, anyway: ~/bootmedia> find autoinst-master/ -name "*.rpm" -exec rm {} \; ( 547 Mbyte less data result in a 538 Mbyte smaller iso image ) * Prepare syslinux config file Here we put the stuff which we previously had to type in at the boot prompt. Change "autoinst-master/suse/images/boot/isolinux.cfg" that it looks like this: ~/boodmedia> cat autoinst-master/suse/images/boot/isolinux.cfg #----- isolinux.cfg - syslinux config file default autoyast # default - autoinstallation with configuration settings # + installation sources from the network label autoyast kernel linux #one line from "append" - "suse8.0" !!! append initrd=initrd ramdisk_size=65536 autoyast=nfs://192.168.0.5/path/1.xml install=nfs://192.168.0.10/install/suse8.0 # nfs installation: manual installation with sources from the network label nfsinstall kernel linux append initrd=initrd ramdisk_size=65536 install=nfs://192.168.0.10/install/suse8.0 implicit 0 gfxboot suselogo display message prompt 1 timeout 100 readinfo 2 framebuffer 1 #---- end of isolinux.cfg III) Create Your Own ISO Image The tricky thing is to get a bootable cd image. This is done by using the "El Torito" technique: a floppy boot image is included ... luckily we can orientate on the way SuSE did it. The nice thing with iso images created with the tool "mkisofs": one can see the options with which they were created. Just do a ~/boodmedia> head susecd1.orig.iso # (or take a look with some editor, the konqueror, whatever) and look at that line: mkisofs 1.14 -p CD-Team, feedback(a)suse.de -P SuSE GmbH, suse(a)suse.de -r -T -J -pad -sort /var/tmp/m_cd-Wbjzkb -no-emul-boot -boot-load-size 4 -boot-info-table -b suse/images/boot/isolinux.bin -c suse/images/boot.catalog -A SuSE-Linux-Professional-DE-i386-8.0.0#0 -V SU8000.001 -o ../../iso/SuSE-8.0-Prof-i386-de-RC4-CD1.iso /var/tmp/m_cd-YiiVui CD1 We use (mostly) the same options - with other values. For full information on all this options look in the man-page of mkisofs ! one line: ! ~bootmedia> mkisofs -p your.email@domain -P "company+department info" -r -T -J -pad -no-emul-boot -boot-load-size 4 -boot-info-table -b suse/images/boot/isolinux.bin -c suse/images/boot.catalog -A SuSE-Linux-Professional-DE-i386-8.0.0#autoinstall0 -V SuSEautoinst.001 -o autoinst1.iso autoinst-master Remark: suse/images/boot/isolinux.bin is the "floppy-boot-image" for El Torito. IV) Write ISO Image on CD If you've got your boot CD iso-image (here named autoinst1.iso), you can burn it with any cd record tool you want - if it can do iso images (Most do). (I did it on windows with nero, since my cd-rw drive is not here, yet. On Linux "cdrecord" whith option "-data" should do.) POSSIBLE IMPROVEMENTS: - Probable one can solve this much more elegant. But it did work, on my side. - One might make the iso image smaller with deleting more (not needed) files. - No slide-show ( Or own slide show ) NEEDED IMPROVEMENT: ->> How to integrate the autoyast updates? SUGGESTIONS: are highly welcome! ---- Regards, Hella Breitkopf

1 0

YAST2 - using netdevice=eth1
by Hella.Breitkopf＠varetis.de 22 May '02

22 May '02

Hi List, hi Anas, Anas Nashif's great documentation of his tool AutoYast2 mentions this: Putting this to the bootcd kernel commandline, I expected the use of network device "eth1" for network setup (with dhcp): linux netdevice=eth1 install=nfs://1.2.3.4/x/suse8.0 autoyast=nfs://1.2.3.5/y/auto.xml Unluckily the information of the "netdevice" keyword seems to be ignored: ----- Trying to activate eth0 Setting up localhost...done timed out waiting for a valid DHCP server response Sending DHCP request to eth0... no/incomplete answer Ok, that didn't work; see if we can activate another network device... No further network cards found; giving up. ----- If I do a "manual Installation", I *can* choose between two network devices. And fetching dhcp information and the following installation from "eth1" works. (An installation over "eth0" works, too - if there is a cable. But there are good reasons to use eth1 in this case. ) Other parameters (I tried e.g. ip,netmask,gateway) work as expected, so why netdevice doesn't? Somebody else with this problem? Did I do something wrong? Or do I have to create an info file on my boot cd? Best Regards, Hella - my next boot cd should include that. (Somebody interested in a description, how to build a crude boot cd for network installation?)

2 1