August 2003 - openSUSE Autoinstall - openSUSE Mailing Lists

init process failed over pxe with own initrd
by Markus Klimke 08 Aug '03

08 Aug '03

Hi there, I've created my own ramdisc. The kernel loads the basic root-filesystem into the ram without any problems. The conf file on my tftp server looks like this: ---snip--- default linux label linux kernel linux append init=/linuxrc rw initrd=initrd root=/dev/ram ---snap--- I've also tried it with some other options like 'load_ramdisk=1' and other stuff, but nothing really solves it, that, during the boot sequence, he stucks with the following kernel panic: ---snip--- Freeing initrd memory: 278k freed VFS: Mounted root (ext2 filesystem) Freeing unused kernel memory : 160k kernel panic: No init found. Try passing init= option to kernel ---snap--- With the original SuSE initrd it works fine, and after I decompressed it I found a linuxrc binary. My linuxrc is a sh-script. But I think this don't mind here, because it doesn't find an init at all. My ramdisc holds this: ---snip--- /bin linuxrc ---snap--- Some workarounds failed also: 1.) Copying a bare skeleton consisting of 'init' and '/etc/init.d/{rc,rc1.d}' leads to that it won't process the init program (a little success, but I only tried it to figure out whether the problem relates to my initrd). 2.) Writing a C file which starts a shell script. The binary C file is called 'init' and was found in /sbin of my ramdisc. Am I blind of something nasty I forgot? Or depends the failure on some other facts not mentioned above? Please help, my brain feels like filled up with scrap since three days of troubleshooting... Best regards and many thanks for every advice Markus

1 0

Bug in switching from static to DHCP IP address (SuSE 8.2)
by Hayo Schmidt 07 Aug '03

07 Aug '03

I had set up my network with a static IP address for my home network. I wanted to change this to use the laptop at work. It was not possible to do this with YaST. YaST always created an entry in /etc/hosts containing the old static IP address. So it was not possible to access the system by name. /etc/sysconfig/network/ifcfg-eth0 looked like this: BOOTPROTO='dhcp' MTU='' REMOTE_IPADDR='' STARTMODE='onboot' UNIQUE='CLZK.uKObkw8DXlC' WIRELESS='no' BROADCAST='192.168.162.127' IPADDR='192.168.162.123' NETMASK='255.255.255.128' NETWORK='192.168.162.0' I changed it as follows and deleted the entry form /etc/hosts: BOOTPROTO='dhcp' MTU='' REMOTE_IPADDR='' STARTMODE='onboot' UNIQUE='CLZK.uKObkw8DXlC' WIRELESS='no' BROADCAST='' IPADDR='' NETMASK='' NETWORK='' It was not possible to delete these entries with YaST. After running YaST (-> SuSEconfig) it works now. But it ist not satisfying, as i am going to have thes problems everytime i change the network - almost daily. Hayo Schmidt

1 0

partition full?
by Mag. Furtschegger Franz 06 Aug '03

06 Aug '03

Hi all, I'm trying to install suse 8.2 with autoyast2; installfiles over nfs. Now I have a big problem and no solution: I want to have on the target system two primary partitions: /dev/hda1 mounted as / (size 5GB) /dev/hda2 mounted as swap (size 512MB) during auto-installation - after partition hda1 is ready formated I get an error, that it isn't possible to mount /dev/hda1 into /mnt/. If I analyse the generated partitions with partitionimage I see, that after formatting hda1 every space on hda1 is used (no space left on hda1!!!) But: Everything works best (no error), if I use ext2 instead of reiser What am I doing wrong? I have installed autoyast2-installation-2.7.19-0 and autoyast2-2.7.19-0 Hope anybody can help me. Franz --- my entries in my xml-file are: <partitioning config:type="list"> <drive> <device>/dev/hda</device> <partitions config:type="list"> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <crypt_key></crypt_key> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <size>5GB</size> </partition> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <crypt_key></crypt_key> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <size>512MB</size> </partition> </partitions> <use>all</use> </drive> </partitioning>

2 1

AW: [suse-autoinstall] Autoyast2 - Disable graphical installation
by matthias.redlich＠freudenberg.de 01 Aug '03

01 Aug '03

> The parameter is textmode=1 > See also the autoinst manual, 6.2. Advanced Linuxrc Options: > http://w3.suse.de/~nashif/autoinstall/8.1/html/x1306.html#AEN1333 Thanks a lot! That's exactly the parameter we searched for. Best regards - Matthias Redlich

1 0

Autoyast2 - Disable graphical installation
by matthias.redlich＠freudenberg.de 01 Aug '03

01 Aug '03

Hello, we are currently testing the automation of Linux installations. (SLES 8) So far, everything works pretty good, but there is still one detail we would like to improve: Before the installation begins a X server is started to provide a graphical installation. Since we do not think it is necessary to have a graphical installation (with xserver) for an automatic installation we are searching for a solution to avoid this. How can I tell the system not to start xserver whilst installation but install in textmode? (the same effect as pressing F2 (text mode) in the boot menue when booting from a SuSE CD) A parameter for the bootloader would be most convenient. We have already tried to use "vga=normal", but this parameter does not work. Thanks in advance, - Matthias Redlich

2 1