Sorry for the confusion, but I open a separate thread for this bug now, because it does not depend on the <global> parameters in the profile as I wrote before (the subject was meant to be "bug with timeout", not "but with timeout" :-)) It seems like the timeout value for lilo.conf get's a "0" added whenever it is read in YaST. On some systems it grows above the allowed value, on others not (that's why I thought it was depending on the global values). My bootloader profile is only this: <bootloader> <loader_type>lilo</loader_type> <loader_device>/dev/sda</loader_device> <location>custom</location> </bootloader> Nothing about the timeout option. But the generated lilo.conf I find: timeout = 80000 causing AY to throw an error. In y2log I find those lines very interesting: 2009-04-17 17:28:03 <1> sunserver2(4672) [YCP] BootLILO.ycp:163 Proposed globals: $["default":"SUSE_Linux", "gfxmenu":"/boot/message", "prompt":"1", "timeout":"8"] ... 2009-04-17 17:59:14 <1> sunserver2(4672) [YCP] bootloader/routines/lib_iface.ycp:228 Read global settings: $["default":"Linux", "gfxmenu":"/boot/message", "lines_cache_id":"4", "prompt":"1", "stage1_dev":"/dev/disk/by-id/scsi-3600508e0000000001d57ab1ae1a97a05", "timeout":"800"] ... 2009-04-17 17:59:26 <1> sunserver2(4672) [YCP] bootloader/routines/lib_iface.ycp:208 Storing global settings $["default":"Linux", "lines_cache_id":"4", "prompt":"1", "stage1_dev":"/dev/disk/by-id/scsi-3600508e0000000001d57ab1ae1a97a05", "timeout":"800"] ... 2009-04-17 17:59:35 <1> sunserver2(4672) [YCP] bootloader/routines/lib_iface.ycp:228 Read global settings: $["default":"Linux", "lines_cache_id":"2", "prompt":"1", "stage1_dev":"/dev/disk/by-id/scsi-3600508e0000000001d57ab1ae1a97a05", "timeout":"8000"] I didn't find the "80", but it seems like a 0 is added for a "write-read" cycle. This is a real stopper, because as far as I understand I cannot alter the lilo.conf file before lilo is called once, only after it (with a chroot script), but I don't get there as AY hangs before. Any idea what I could do? If you think it's not an AY but a YaST bug, I can file a support request via the Novell SLES Support if that helps getting resources to work on it. I've done that for the problem with the unsigned repositories where you assumed that it was a problem in YaST/the installer. Maybe we get enough stuff for a driverupdate? :-) This bug, the ignored <global> options, the wrong windows section (see last mail in "AY changes types of existing partitions"), the unsigned repositories, and then, maybe, also the partition_id thing ;-) cu, Frank -- Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/ Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/ LMU, Amalienstr. 17 Phone: +49 89 2180-4049 80333 Muenchen, Germany Fax: +49 89 2180-99-4049 * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. * -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org