[fedora-arm] Re: Fedora 32 on RPI4

2020-04-02 Thread Thomas H.P. Andersen
Hi Andreas I use fedora32 on my raspberry 4 and it works fine with the latest kernel. Note that I only managed to get the Minimal build to boot. See the former threads on the boot getting stuck in dracut for workstation images. I just used Minimal and then installed all the things from

[fedora-arm] Re: Fedora 32 on RPI4

2020-04-03 Thread Thomas H.P. Andersen
On Fri, Apr 3, 2020 at 6:13 PM Stefan Wahren wrote: > Hi Fred, > > Am 03.04.20 um 13:10 schrieb Fred van Zwieten: > > I haven't retried it yet, but I do have some extra info on my previous > > (and failed) attempt: > > > > I used arm-image-installer as the tool. As it does not yet have a rpi4 >

[fedora-arm] Re: CMA on raspberry pi 4

2020-04-28 Thread Thomas H.P. Andersen
On Tue, Apr 28, 2020 at 3:20 PM Peter Robinson wrote: > Hi Thomas, > > > I have looked into the CMA setting issue a bit. This is what I have > found so far. > > > > The rpi4 needs CMA to be in ZONE_DMA (lower 1GB of memory) as this is > the only area that the peripherals on the rpi4 can address.

[fedora-arm] Re: CMA on raspberry pi 4

2020-04-28 Thread Thomas H.P. Andersen
> cma=256M@704M > > I end up with an apparenlty fully functional Fedora and after deactivation > of animation effects using Tweaks, Gnome is not (very) sluggish and works > fine for me. > > Cheers, Thomas B > > > On Thu, Apr 23, 2020 at 5:46 PM Thomas H.P. Andersen > wro

[fedora-arm] Re: Raspberry Pi 4 / Fedora 32 / Kernel 5.6

2020-04-22 Thread Thomas H.P. Andersen
On Sat, Apr 18, 2020 at 10:56 AM Thomas wrote: > > > Just remove the cma= entry in the grub.cfg on the vfat partition it > > will be easier, and an order of magnitude quicker. > > > > I had a similar issue with recent kernels that I solved by removing > > a cma= setting from the kernel boot

[fedora-arm] CMA on raspberry pi 4

2020-04-23 Thread Thomas H.P. Andersen
Hi, I have looked into the CMA setting issue a bit. This is what I have found so far. The rpi4 needs CMA to be in ZONE_DMA (lower 1GB of memory) as this is the only area that the peripherals on the rpi4 can address. The DT sets the allowed range to allocate the CMA from (

[fedora-arm] Re: Question to booting Fedora 32 on Raspi 4

2020-05-12 Thread Thomas H.P. Andersen
On Tue, May 12, 2020 at 9:27 AM Andreas Reschke wrote: > > Am 12.05.20 um 08:56 schrieb Peter Robinson: > >> everytime I boot my Raspi I have to wait a few minutes till the kernel > >> start to boot. > >> > >> Last line is: > >> > >> genet@7d58 Waiting for PHY auto negtiation to complete >

[fedora-arm] Re: CMA on raspberry pi 4

2020-05-07 Thread Thomas H.P. Andersen
On Thu, May 7, 2020 at 11:23 AM Peter Robinson wrote: > Hi Thomas, > > >> > I have looked into the CMA setting issue a bit. This is what I have > found so far. > >> > > >> > The rpi4 needs CMA to be in ZONE_DMA (lower 1GB of memory) as this is > the only area that the peripherals on the rpi4 can

[fedora-arm] Re: CMA on raspberry pi 4

2020-05-07 Thread Thomas H.P. Andersen
On Thu, May 7, 2020 at 4:10 PM Peter Robinson wrote: > >> >> > I have looked into the CMA setting issue a bit. This is what I > have found so far. > >> >> > > >> >> > The rpi4 needs CMA to be in ZONE_DMA (lower 1GB of memory) as this > is the only area that the peripherals on the rpi4 can