[fedora-arm] PinePhone Support

2020-02-19 Thread Nikhil Jha
Hi! I got Fedora working on PinePhone the other day, and it works surprisingly well, even though it's just desktop GNOME. It's a 5.6 kernel with... ... this device tree: https://megous.com/git/linux/tree/arch/arm64/boot/dts/allwinner/sun50i-a64-pinephone.dts?h=pp-5.6 (branch: pp-5.6) ... and

[fedora-arm] Re: Latest Fedora update leaves aarch64 unbootable RPi V3.

2020-02-19 Thread Paul Whalen
- Original Message - > On Wed, 2020-02-19 at 14:12 -0500, Paul Whalen wrote: > > > > - Original Message - > > > On Wed, 2020-02-19 at 12:04 -0500, Michael H. Warfield wrote: > > > > On Wed, 2020-02-19 at 11:25 -0500, Paul Whalen wrote: > > > > > Hi Michael, > > > > > > > > > >

[fedora-arm] Re: Latest Fedora update leaves aarch64 unbootable RPi V3.

2020-02-19 Thread Michael H. Warfield
On Wed, 2020-02-19 at 15:09 -0500, Michael H. Warfield wrote: : - > > The armhfp images use extlinux and require grubby-deprecated. The > > aarch64 > > images shouldn't have it installed. > > Looking at your bz, I see you mention the aarch64 image has > > extlinux- > > bootloader > > and

[fedora-arm] Re: Latest Fedora update leaves aarch64 unbootable RPi V3.

2020-02-19 Thread Michael H. Warfield
On Wed, 2020-02-19 at 14:12 -0500, Paul Whalen wrote: > > - Original Message - > > On Wed, 2020-02-19 at 12:04 -0500, Michael H. Warfield wrote: > > > On Wed, 2020-02-19 at 11:25 -0500, Paul Whalen wrote: > > > > Hi Michael, > > > > > > > > Trying to reproduce this issue without success.

[fedora-arm] Re: Latest Fedora update leaves aarch64 unbootable RPi V3.

2020-02-19 Thread Paul Whalen
- Original Message - > On Wed, 2020-02-19 at 12:04 -0500, Michael H. Warfield wrote: > > On Wed, 2020-02-19 at 11:25 -0500, Paul Whalen wrote: > > > Hi Michael, > > > > > > Trying to reproduce this issue without success. How did you write > > > the > > > images and > > > what command

[fedora-arm] Re: Latest Fedora update leaves aarch64 unbootable RPi V3.

2020-02-19 Thread Michael H. Warfield
On Wed, 2020-02-19 at 12:04 -0500, Michael H. Warfield wrote: > On Wed, 2020-02-19 at 11:25 -0500, Paul Whalen wrote: > > Hi Michael, > > > > Trying to reproduce this issue without success. How did you write > > the > > images and > > what command was used? After booting, did you confirm the

[fedora-arm] Re: Latest Fedora update leaves aarch64 unbootable RPi V3.

2020-02-19 Thread Michael H. Warfield
On Wed, 2020-02-19 at 11:25 -0500, Paul Whalen wrote: > Hi Michael, > > Trying to reproduce this issue without success. How did you write the > images and > what command was used? After booting, did you confirm the kargs were > as expected? The original image booted and worked. Some of the

[fedora-arm] Re: Latest Fedora update leaves aarch64 unbootable RPi V3.

2020-02-19 Thread Michael H. Warfield
On Wed, 2020-02-19 at 11:56 -0500, Michael H. Warfield wrote: > On Wed, 2020-02-19 at 11:25 -0500, Paul Whalen wrote: > > Hi Michael, > > Trying to reproduce this issue without success. How did you write > > the > > images and > > what command was used? After booting, did you confirm the kargs >

[fedora-arm] Re: Latest Fedora update leaves aarch64 unbootable RPi V3.

2020-02-19 Thread Paul Whalen
- Original Message - > On Wed, 2020-02-19 at 11:25 -0500, Paul Whalen wrote: > > Hi Michael, > > > Trying to reproduce this issue without success. How did you write the > > images and > > what command was used? After booting, did you confirm the kargs were > > as expected? > > I used

[fedora-arm] Re: Latest Fedora update leaves aarch64 unbootable RPi V3.

2020-02-19 Thread Michael H. Warfield
On Wed, 2020-02-19 at 11:25 -0500, Paul Whalen wrote: > Hi Michael, > Trying to reproduce this issue without success. How did you write the > images and > what command was used? After booting, did you confirm the kargs were > as expected? I used arm-install as recommended. > Once booted, you

[fedora-arm] Re: Latest Fedora update leaves aarch64 unbootable RPi V3.

2020-02-19 Thread Paul Whalen
Hi Michael, Trying to reproduce this issue without success. How did you write the images and what command was used? After booting, did you confirm the kargs were as expected? Once booted, you just 'dnf update' and get the corrupted grub.cfg? Thanks! Paul - Original Message - > On