December 2004 - openSUSE Autoinstall - openSUSE Mailing Lists

trouble on generating a grub network boot floppy
by Ralf Gnädinger 03 Dec '04

03 Dec '04

Hi. This is the qmail-send program at lists.suse.com. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. <suse-autoinstall(a)lists.suse.com>: Sorry, only subscribers may post. If you are a subscriber, please forward this message to suse-autoinstall-owner(a)suse.com to get your new address included (#5.7.2) --- Below this line is a copy of the message. Return-Path: <ralf(a)verspoolt.org> Received: (qmail 19399 invoked from network); 3 Dec 2004 11:51:12 -0000 Received: from unknown (HELO hermes.suse.de) (195.135.221.8) by 0 with SMTP; 3 Dec 2004 11:51:12 -0000 Received: from scanhost.suse.de (scanhost.suse.de [149.44.160.36]) by hermes.suse.de (Postfix) with ESMTP id C860CDD2CE for <suse-autoinstall(a)lists.suse.com>; Fri, 3 Dec 2004 12:51:12 +0100 (CET) Received: from hermes.suse.de ([149.44.160.1]) by scanhost.suse.de (scanhost [149.44.160.36]) (amavisd-new, port 10025) with ESMTP id 09562-07 for <suse-autoinstall(a)lists.suse.com>; Fri, 3 Dec 2004 12:50:57 +0100 (CET) Received: from Cantor.suse.de (mail-ex.suse.de [195.135.220.2]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by hermes.suse.de (Postfix) with ESMTP id BC45B68D45 for <suse-autoinstall(a)lists.suse.com>; Fri, 3 Dec 2004 12:50:57 +0100 (CET) Received: from dd1032.kasserver.com (dd1032.kasserver.com [81.209.148.116]) by Cantor.suse.de (Postfix) with ESMTP id A243811B5B79 for <suse-autoinstall(a)lists.suse.com>; Fri, 3 Dec 2004 12:50:57 +0100 (CET) Received: from 193.100.166.26 (auth. user v029029(a)mail.verspoolt.org) by webmail.verspoolt.org with HTTP; Fri, 03 Dec 2004 12:50:42 +0100 To: suse-autoinstall(a)lists.suse.com Subject: trouble on generating a grub network boot floppy Date: Fri, 03 Dec 2004 12:50:42 +0100 X-Mailer: IlohaMail/0.8.13 (On: webmail.verspoolt.org) Message-ID: <z5myWovI.1102074642.6354540.v029029(a)mail.verspoolt.org> From: "Ralf =?ISO-8859-1?Q?Gn=E4dinger?=" <ralf(a)verspoolt.org> Bounce-To: "Ralf =?ISO-8859-1?Q?Gn=E4dinger?=" <ralf(a)verspoolt.org> Errors-To: "Ralf =?ISO-8859-1?Q?Gn=E4dinger?=" <ralf(a)verspoolt.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: by amavisd-new at scanhost.suse.de X-Spam-Status: No, hits=-5.9 tagged_above=-20.0 required=5.0 tests=BAYES_00, MY_LINUX X-Spam-Level: Hi, i`m getting some trouble when i try to generate my own floppy boot disk with grub. the configuration of my self comiled grub looks like this: /configure --enable-diskless --enable-smc9000 --enable--smc9000-scan=3D3D3D0x320,0x340 --enable-3c90x all seems find till i try to load the kernel and initrd over the lan. all i get is the output of the network card check and the network configuration including the my configuration for the kernel: kernel /linux.80 netdevice=3D3D3Deth0 server=3D3D3D89.0.14.4 ramdisk_size=3D3D3D655=3D 36 autoyast=3D3D3Dnfs://89.0.14.4/srv/ftp/ayconf/myconf.xml install://89.0.14.4/srv/ftp after this line the loading process stops nothing like [bzimage ...] the menu.lst file couldn`t be the reason it works with the offical floppy provided by this site. do anyone have some idea how to got this work? unfortunally i`m forced to generate a new boot disk becaus the offical one won`t work for my smc card ( the card is not detected correctly). thx in advance ralf

1 0

RE: [suse-autoinstall] Grub and autoyast (getting null for device?)
by Benjamin Shi 03 Dec '04

03 Dec '04

In /usr/share/YaST2/include/bootloader/grub/misc.ycp, string dev = select ( select ( filter (`l, device_map, ``(l[1]:"" == o_dev)), 0, [] ), 0, "" ); if (dev == "") dev = "(null)"; else if (num != 0 && num != "") { num = num - 1; string number = sformat ("%1", num); dev = substring (dev, 0, size (dev) - 1) + "," + number + ")"; } return dev; It is setting dev to (null) which almost certainly break grub. Don't know why dev is "" to beging with, but setting it to a more sensible default value, ((hd0,0) maybe?) fix the problem. -----Original Message----- From: Benjamin Shi Sent: Wednesday, December 01, 2004 6:20 PM To: suse-autoinstall(a)suse.com Subject: RE: [suse-autoinstall] Grub and autoyast (getting null for device?) Also, this is installing suse 9.0 on amd64 opterons. We tried to update /etc/grub.conf with (hd0,0) on tty2, then went back to tty1 to rerun the bootloader config; /etc/grub.conf gets overwritten with (null) again. -----Original Message----- From: Benjamin Shi Sent: Wednesday, December 01, 2004 6:17 PM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] Grub and autoyast (getting null for device?) Hi, all: We are running into problem installing grub via autoyast installation. Here is the error: cat /etc/grub.conf | /usr/sbin/grub --batch --device-map=/boot/grub/device.map GRUB version 0.93 (640K lower / 3072K upper memory) [ Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists the possible completions of a device/filename. ] grub> root (null) Error 23: Error while parsing number grub> install --stage2=/boot/grub/stage2 /grub/stage1 d (hd0,0) /grub/stage2 0x8000 (null)/grub/menu.lst Error 12: Invalid device requested grub> quit Yast install is using (null) instead of (hd0,0). The device.map seems to be fine, and we have tried to reduced the bootloader sectin on autoinst.xml to minimum: <bootloader> <activate config:type="boolean">true</activate> <loader_device></loader_device> <loader_type>grub</loader_type> <location></location> </bootloader> It didn't help either, using /dev/sda in the loader_device section. Yast always gets (null). Where is yast reading this value from and what can we do to fix it? Thanks in advance for any help. Regards, Ben -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1

Suse 9.1 Network driver problem
by Milind Nanal 03 Dec '04

03 Dec '04

List, I have installed Suse 9.1 on HP system. The system is having Brodcom Gigabyte Ethernet card. The installation went fine with out any error. The problem I am facing is that the LAN driver are not getting loaded while system booting process. I have to run YAST to activate LAN driver & then only it works. Dose any one tell me why it could be? Quick response is highly appreciated. Regards, Milind

1 0

Instalation Repository
by Robert Morrow 02 Dec '04

02 Dec '04

I have created an installation repository on my FTP server and want to add customer rpm's. I have added one and ran the create_package_descr and it shows up as an option to install but when I go to install it, it tells me it can not find the package. Robert Morrow Network Specialist (913)588-7306

1 0

autoyast using a http port other than 80
by Romani, Roberto 02 Dec '04

02 Dec '04

Is there a patch to autoyast that allows it to use a different http port than 80

2 1

Preventing AutoYast from partitioning the disks
by Naveen 02 Dec '04

02 Dec '04

Hi, We are trying to use AutoYast to perform 'a kind of unattended install'. We would like to do the disk partitioning manually and this we wish to do during the install only. That is, during installation Yast should prompt for a manual disk partitioning but nothing else. How to do this with AutoYast ? We have tried omitting the entries related to disk partitioning from the AutoYast file but it didn't help. - Naveen

1 0

RE: [suse-autoinstall] Grub and autoyast (getting null for device?)
by Benjamin Shi 01 Dec '04

01 Dec '04

Also, this is installing suse 9.0 on amd64 opterons. We tried to update /etc/grub.conf with (hd0,0) on tty2, then went back to tty1 to rerun the bootloader config; /etc/grub.conf gets overwritten with (null) again. -----Original Message----- From: Benjamin Shi Sent: Wednesday, December 01, 2004 6:17 PM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] Grub and autoyast (getting null for device?) Hi, all: We are running into problem installing grub via autoyast installation. Here is the error: cat /etc/grub.conf | /usr/sbin/grub --batch --device-map=/boot/grub/device.map GRUB version 0.93 (640K lower / 3072K upper memory) [ Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists the possible completions of a device/filename. ] grub> root (null) Error 23: Error while parsing number grub> install --stage2=/boot/grub/stage2 /grub/stage1 d (hd0,0) /grub/stage2 0x8000 (null)/grub/menu.lst Error 12: Invalid device requested grub> quit Yast install is using (null) instead of (hd0,0). The device.map seems to be fine, and we have tried to reduced the bootloader sectin on autoinst.xml to minimum: <bootloader> <activate config:type="boolean">true</activate> <loader_device></loader_device> <loader_type>grub</loader_type> <location></location> </bootloader> It didn't help either, using /dev/sda in the loader_device section. Yast always gets (null). Where is yast reading this value from and what can we do to fix it? Thanks in advance for any help. Regards, Ben -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Grub and autoyast (getting null for device?)
by Benjamin Shi 01 Dec '04

01 Dec '04

Hi, all: We are running into problem installing grub via autoyast installation. Here is the error: cat /etc/grub.conf | /usr/sbin/grub --batch --device-map=/boot/grub/device.map GRUB version 0.93 (640K lower / 3072K upper memory) [ Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists the possible completions of a device/filename. ] grub> root (null) Error 23: Error while parsing number grub> install --stage2=/boot/grub/stage2 /grub/stage1 d (hd0,0) /grub/stage2 0x8000 (null)/grub/menu.lst Error 12: Invalid device requested grub> quit Yast install is using (null) instead of (hd0,0). The device.map seems to be fine, and we have tried to reduced the bootloader sectin on autoinst.xml to minimum: <bootloader> <activate config:type="boolean">true</activate> <loader_device></loader_device> <loader_type>grub</loader_type> <location></location> </bootloader> It didn't help either, using /dev/sda in the loader_device section. Yast always gets (null). Where is yast reading this value from and what can we do to fix it? Thanks in advance for any help. Regards, Ben

1 0

Multiple source through http
by Aaron McSorley 01 Dec '04

01 Dec '04

Does multiple source install for SLES8 and SLES9 work through http? Thanks Aaron

2 1

dhcp-server configuration XML configuration not supported although generated?
by fraser_bailey＠agilent.com 01 Dec '04

01 Dec '04

I've just installed a system and used autoyast to create a reference profile. The installed ystem has the dhcp server enabled. The reference profile contains a: <dhcp-server> . . . </dhcp-server> block. xmllint -dtdvalid /usr/share/autoinstall/dtd/profile.dtd x.xml blows up on this block. Inspection of the DTD suggests this element is undefined. This means autoyast will probably blow up when it tries to use this xml file to autoload a system. Is this a problem? How can I validate the generated xml? Will autoyast be able to handle dhcp-server blocks? advice appreciated.

1 0