On Sonntag, 31. August 2014, 21:33:02 wrote Alexander Graf: > > On 31.08.14 19:35, Andreas Schwab wrote: > > Alexander Graf <[email protected]> writes: > > > >> For some reason the firmware does not detect the default boot entry of > >> the disk (to be debugged), so you have to manually point it to > >> > >> efi\boot\boota64.efi > > > > That should be bootaa64.efi according to the UEFI specs. > > Nicely spotted, thanks for fixing. It still doesn't boot though. > > Also the image can't get built right now in OBS because we're lacking > iso8859-1 kernel module support in the x86 vm kernel (which would have > to get modprobe'd by the initrd). > > Adrian, I think we had this problem before, didn't we? How did we fix it?
In old times this dependended on the worker configuration. But meanwhile we can provider own kernel & initrd in our projects to have this configured in a way that lasts :) I suppose you talk about openSUSE:Factory:ARM/images repo for aarch64? There is currently a VMinstall: !kernel-obs-build in prjconf, which enforces to skip to use the own kernel&initrd for inside of openSUSE:Factory:ARM. I have moved this line now, that we use it at least for qemu builds. You may need to trigger a rebuild manually to check if that works. Also check that kernel-obs-build package gets installed before starting the VM. -- Adrian Schroeter email: [email protected] SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
