On 01.09.14 09:34, Adrian Schröter wrote:
> On Montag, 1. September 2014, 09:28:02 wrote Alexander Graf:
>>
>>> Am 01.09.2014 um 09:19 schrieb Adrian Schröter <[email protected]>:
>>>
>>> On Montag, 1. September 2014, 09:10:05 wrote Alexander Graf:
>>>>
>>>>> Am 01.09.2014 um 09:01 schrieb Adrian Schröter <[email protected]>:
>>>>>
>>>>> 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.
>>>>
>>>> But wouldn't thag mean that we'd have to have an x86 obs kernel in the 
>>>> aarch64 repo?
>>>
>>> Yes, we need one. You are right, there is currently only an aarch64 one.
>>>
>>> I have added it now to
>>>
>>> openSUSE:Factory:ARM/aggregate_for_x86_64
>>>
>>> and adapted the prjconf.
>>>
>>> Should be fine now.
>>
>> So how exactly does this ensure that the kernel module in question is loaded 
>> on bootup?
> 
> The build script is loading kernel and initrd which got preinstalled as 
> /.build.kernel.kvm
> and /.build.initrd.kvm
> 
>> The only reason that the obs kernel replacement maybe could help things on 
>> native builds is that we can install the kernel in the target fs and have 
>> udev automatically load modules for it. But our kernel modules on the target 
>> fs are aarch64 and won't work.
> 
> Right, but the initrd should bring the right set of kernel modules already 
> with it.

So with this setup we now get build failures for kpartx:

https://build.opensuse.org/package/live_build_log/openSUSE:Factory:ARM/JeOS-efi.aarch64/images/aarch64


Alex
-- 
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]

Reply via email to