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@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@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@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com