25.11.2016 00:24, Alexander Graf пишет:
> 
> 
>> Am 24.11.2016 um 21:46 schrieb Matwey V. Kornilov 
>> <[email protected]>:
>>
>> 24.11.2016 22:18, Alexander Graf пишет:
>>>
>>>
>>>> On 24/11/2016 20:15, Alexander Graf wrote:
>>>>
>>>>
>>>>> On 23/11/2016 14:00, Dirk Müller wrote:
>>>>> Hi All,
>>>>>
>>>>> over the last few days I've been pretty busy with enabling
>>>>> pre-configured appliances for ARMv7 and AArch64 on openSUSE Leap 42.2,
>>>>> and I'm happy to report that we now have some images available:
>>>>>
>>>>> http://download.opensuse.org/ports/armv7hl/distribution/leap/42.2/appliances/
>>>>>
>>>>>
>>>>> http://download.opensuse.org/ports/aarch64/distribution/leap/42.2/appliances/
>>>>>
>>>>>
>>>>>
>>>>> As you can see its a pretty elaborative list of images, and I don't
>>>>> have time to test all of them myself. so whoever is interested in
>>>>> having some of those variants working for him, please try them out and
>>>>> report both successes and failures. The overall goal is to announce
>>>>> the ARM port end of next week (Dec 1st) so it would be great to have
>>>>> some testing feedback before that (and << before that so that we can
>>>>> maybe even fix it before announcement).
>>>>
>>>> That panda image is broken. Grub2 in Leap 42.2 is older than Tumbleweed,
>>>> so it's missing critical armv7 fixes for EFI boot. If I copy the
>>>> Tumbleweed grub2 binary onto the image, it seems to work.
>>>
>>> Ah, there's more breakage. The grub.cfg generator doesn't know which
>>> image format to take, so it picks vmlinux-foo.gz which grub2 can't boot
>>> from, as it needs the zImage.
>>>
>>> I think we should just disable EFI boot for all armv7 systems.
>>
>> Actually, I've already sent a fix:
>> https://bugzilla.opensuse.org/show_bug.cgi?id=1008545
>> https://bugzilla.opensuse.org/show_bug.cgi?id=1008568
> 
> Ah, cool. So how do we get those into Leap before the announcement?
> 

It would be better to ask SLES guys.

> Alex
> 
> 


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

Reply via email to