Hi, yes, the thread you mentioned describes exactly the same problem! Well, of course I could modify the <bootloader> section and add the kernel used by live system as the first option. The problem here is that I would have to guess the kernel of the live system (ok, now I know it uses "desktop" but maybe the naming scheme will change in the future?). So I think it should be the other way round: the live system should interpret the <kernel> setting and adapt its bootloader for stage2! BTW: What happens if I don't use <forceboot> ? I didn't test this so far... Usually, the live system tries to kexec into the installed kernel (which would be the default kernel in my case), right? - Joschi On 05/13/2011 08:49 AM, 686f6c6d wrote:
Hi, if you change the kernel during install, IIRC, grub/grub-install does not "get it" and creates boot entries for the live system, which can result in all kinds of errors; you have to correct the grub entries yourself. You can also try adding the ext4 module for that specific kernel (which is basically just the same, adding/editing the<bootloader> section), but I would assume that grub error message is just misleading.
Please see the discussion in this thread: http://lists.opensuse.org/opensuse-autoinstall/2010-05/msg00003.html
tty, 686f6c6d
-- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org