Hi Marcus,

Le 29/10/2013 10:59, Marcus Schäfer a écrit :
> Hi,
>
>> As you can see here:
>> https://build.opensuse.org/project/monitor/openSUSE:13.1:Ports
>>
>> armv7 images are still broken with the same error message as in Factory some 
>> time ago (which should have been fixed): "Couldn't find kernel file":
> Because SUSE has so many different kernel layouts, kernel image types
> and names over all the supported architectures kiwi tries to map
> them and create a .kernel link. This works in the following way:
>
> in /usr/share/kiwi/modules/KIWIConfig.sh::suseStripKernel() there
> is among other parts the code which moves the kernel file to
> a uniq name (vmlinuz)
>  
>   #==========================================
>   # create common kernel files, last wins !
>   #------------------------------------------
>   ...for arm we added some time ago:
>
>   if [ -f uImage-$VERSION ];then
>      mv uImage-$VERSION vmlinuz
>   elif [[ $arch =~ ^arm ]] && [ -f zImage-$VERSION ];then
>      mv zImage-$VERSION vmlinuz
>   elif [[ $arch =~ ^arm ]] && [ -f Image-$VERSION ];then
>      mv Image-$VERSION vmlinuz
>   ...
>   
> whenever the layout or the name of the kernel changes I need
> to adapt this. My first guess is, this is what happened
>
> if the mapping failed the function:
>
>   /usr/share/kiwi/modules/KIWIImage.pm::extractLinux()
>
> will not be able to extract the maped kernel file and thus the
> link will not exist which in the end leads to the error you
> are facing 
>
> if you can tell me which kernels we support for 13.1 on arm and
> what names and image types we will use I can fix this

Your kiwi patch in 13.1:Ports did not fix it (see [0]) and now armv6 also fails 
on kernel extraction, see [1].

[0]: 
https://build.opensuse.org/package/live_build_log/openSUSE:13.1:Ports/JeOS-panda/images_arm/armv7l
[1]: 
https://build.opensuse.org/package/live_build_log/devel:ARM:13.1:Contrib:RaspberryPi/JeOS-raspberrypi/images/armv6l


Guillaume

>
> Regards,
> Marcus

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

Reply via email to