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

[hi]

Adobe Flash for arm64 does not exist. ADOBE stopped supporting Flash some time ago. It is dead technology.https://clinicalmbchb.com/flash-player-support-on-arm64-os-samsung-dex-android/U need to try out something around rasbian better, fedora I doubt will fully support old arm on 32 bitEl 30 abr. 2020 11:04, ng0...@gmail.com escribió:Hi, since I am quite happy now with the RPi 4B and Workstation 32 on, it is still not fit for the purpose of streaming video of some old cctv cameras that only work via a browser flash plugin.Two options exist:1) Firefox w/ install instructions from https://docs.fedoraproject.org/en-US/quick-docs/using-adobe-flash/ which fail:  - package flash-plugin-32.0.0.363-release.i386 does not have a compatible architecture  - package flash-plugin-32.0.0.363-release.x86_64 does not have a compatible architectureand2) Chromium following these instructions which work fine on my desktop computer:sudo gtar xzf flash_player_ppapi_linux.x86_64.tar.gz -C /usr/lib64/chromium-browser/PepperFlash/cd /usr/lib64/chromium-browser/PepperFlash/sudo chown -R root:root *However both fail on the RPi 4B when testing them https://get.adobe.com/flashplayer/about/ Other than flash video content plays fine on it.Any ideas for a quick fix and/or what is planned upstream?BTW, if anyone tries to set up a hotspot that should remember to run "sudo nm-connection-editor" and change the firewall setting from "default" to e.g. Workstation. Otherwise, it will not allow to connect when firewalld is not installed. It took me quite some time to figure out that one.Regards, Thomas BOn Wed, Apr 22, 2020 at 5:23 PM Thomas H.P. Andersen  wrote: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 line.

I removed cma= but it had no effect, see below.

Thanks, Thomas


Fedora-Workstation-32-20200416.n.0.aarch64.raw.xz

/EFI/fedora/grub.cfg

  set kernelopts="root=UUID=72ca87a8-123e-4645-a352-05639bb65638 ro
cma=256MB "
You should update both EFI/fedora/grub.cfg and EFI/fedora/grubenv 
> But do be warned, there is no accelerated graphics on the RPi4 and
> hence it is well and truly unsupported for any graphical systems.
> 
> > On Fri, Apr 17, 2020 at 1:17 PM Peter Robinson <
> > pbrobinson@gmail.com> wrote:
> > > 
> > > On Fri, Apr 17, 2020 at 12:13 PM  wrote:
> > > > 
> > > > Thanks for that! In one of latest images it gets stuck at the
> > > > point shown in the attached screenshot.
> > > 
> > > What image are you using, full file name please.
> > > 
> > > What revision of the hardware do you have? You should have a line
> > > at
> > > the early U-Boot phase that looks something like:
> > > RPI 4 Model B (0xc03111)
> > > 
> > > I'm interested in the hex values at the end.
> > > 
> > > > Good to have your clarification on RPi4 support in the Kernel.
> > > > 
> > > > Thomas
> > > > 
> > > > On Fri, Apr 17, 2020 at 12:01 PM Peter Robinson <
> > > > pbrobinson@gmail.com> wrote:
> > > > > 
> > > > > Hi Thomas,
> > > > > 
> > > > > > Hi, testing of daily images from 
> > > > > > https://dl.fedoraproject.org/pub/fedora-secondary/development/32/Workstation/aarch64/images/
> > > > > > Raspberry Pi 4 defies the keyboard.
> > > > > 
> > > > > I'm not sure what you mean by defies in this context? They
> > > > > keyboard
> > > > > doesn't work? At what point are you having issues. There is
> > > > > no support
> > > > > for USB (actually the PCIe), hence keyboards, in the U-Boot
> > > > > firmware
> > > > > which means it won't work in grub or the early boot process.
> > > > > Once it
> > > > > gets to Linux such as the login prompt they keyboard should
> > > > > work find
> > > > > as there is USB support.
> > > > > 
> > > > > > I have been under the assumption that 5.6 has support
> > > > > > built-in? Any ideas?
> > > > > 
> > > > > Support for what exactly? Support for a device such as the
> > > > > RPi4 is not
> > > > > a binary thing. There is initial support and enablement so
> > > > > it's useful
> > > > > for a number of situations but the support is far from
> > > > > complete and
> > > > > hence while for a it works for a lot of use cases we don't
> > > > > officially
> > > > > support the RPi4 yet because the HW enablement is incomplete.
> > > > > 
> > > > > Peter
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org

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

[ng0177]

Hi, since I am quite happy now with the RPi 4B and Workstation 32 on, it is
still not fit for the purpose of streaming video of some old cctv cameras
that only work via a browser flash plugin.

Two options exist:

1) Firefox w/ install instructions from
https://docs.fedoraproject.org/en-US/quick-docs/using-adobe-flash/ which
fail:
  - package flash-plugin-32.0.0.363-release.i386 does not have a compatible
architecture
  - package flash-plugin-32.0.0.363-release.x86_64 does not have a
compatible architecture

and

2) Chromium following these instructions which work fine on my desktop
computer:

sudo gtar xzf flash_player_ppapi_linux.x86_64.tar.gz -C
/usr/lib64/chromium-browser/PepperFlash/
cd /usr/lib64/chromium-browser/PepperFlash/
sudo chown -R root:root *

However both fail on the RPi 4B when testing them
https://get.adobe.com/flashplayer/about/ Other than flash video content
plays fine on it.

Any ideas for a quick fix and/or what is planned upstream?

BTW, if anyone tries to set up a hotspot that should remember to run "sudo
nm-connection-editor" and change the firewall setting from "default" to
e.g. Workstation. Otherwise, it will not allow to connect when firewalld is
not installed. It took me quite some time to figure out that one.

Regards, Thomas B

On Wed, Apr 22, 2020 at 5:23 PM Thomas H.P. Andersen 
wrote:

>
>
> 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 line.
>>
>> I removed cma= but it had no effect, see below.
>>
>> Thanks, Thomas
>>
>>
>> Fedora-Workstation-32-20200416.n.0.aarch64.raw.xz
>>
>> /EFI/fedora/grub.cfg
>>
>>   set kernelopts="root=UUID=72ca87a8-123e-4645-a352-05639bb65638 ro
>> cma=256MB "
>>
>>
> You should update both EFI/fedora/grub.cfg and EFI/fedora/grubenv
>
>
>> > But do be warned, there is no accelerated graphics on the RPi4 and
>> > hence it is well and truly unsupported for any graphical systems.
>> >
>> > > On Fri, Apr 17, 2020 at 1:17 PM Peter Robinson <
>> > > pbrobin...@gmail.com> wrote:
>> > > >
>> > > > On Fri, Apr 17, 2020 at 12:13 PM  wrote:
>> > > > >
>> > > > > Thanks for that! In one of latest images it gets stuck at the
>> > > > > point shown in the attached screenshot.
>> > > >
>> > > > What image are you using, full file name please.
>> > > >
>> > > > What revision of the hardware do you have? You should have a line
>> > > > at
>> > > > the early U-Boot phase that looks something like:
>> > > > RPI 4 Model B (0xc03111)
>> > > >
>> > > > I'm interested in the hex values at the end.
>> > > >
>> > > > > Good to have your clarification on RPi4 support in the Kernel.
>> > > > >
>> > > > > Thomas
>> > > > >
>> > > > > On Fri, Apr 17, 2020 at 12:01 PM Peter Robinson <
>> > > > > pbrobin...@gmail.com> wrote:
>> > > > > >
>> > > > > > Hi Thomas,
>> > > > > >
>> > > > > > > Hi, testing of daily images from
>> > > > > > >
>> https://dl.fedoraproject.org/pub/fedora-secondary/development/32/Workstation/aarch64/images/
>> > > > > > > Raspberry Pi 4 defies the keyboard.
>> > > > > >
>> > > > > > I'm not sure what you mean by defies in this context? They
>> > > > > > keyboard
>> > > > > > doesn't work? At what point are you having issues. There is
>> > > > > > no support
>> > > > > > for USB (actually the PCIe), hence keyboards, in the U-Boot
>> > > > > > firmware
>> > > > > > which means it won't work in grub or the early boot process.
>> > > > > > Once it
>> > > > > > gets to Linux such as the login prompt they keyboard should
>> > > > > > work find
>> > > > > > as there is USB support.
>> > > > > >
>> > > > > > > I have been under the assumption that 5.6 has support
>> > > > > > > built-in? Any ideas?
>> > > > > >
>> > > > > > Support for what exactly? Support for a device such as the
>> > > > > > RPi4 is not
>> > > > > > a binary thing. There is initial support and enablement so
>> > > > > > it's useful
>> > > > > > for a number of situations but the support is far from
>> > > > > > complete and
>> > > > > > hence while for a it works for a lot of use cases we don't
>> > > > > > officially
>> > > > > > support the RPi4 yet because the HW enablement is incomplete.
>> > > > > >
>> > > > > > Peter
>> ___
>> arm mailing list -- arm@lists.fedoraproject.org
>> To unsubscribe send an email to arm-le...@lists.fedoraproject.org
>> Fedora Code of Conduct:
>> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives:
>> https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org
>>
>
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org
Fedora Code of Conduct: 

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

[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 line.
>
> I removed cma= but it had no effect, see below.
>
> Thanks, Thomas
>
>
> Fedora-Workstation-32-20200416.n.0.aarch64.raw.xz
>
> /EFI/fedora/grub.cfg
>
>   set kernelopts="root=UUID=72ca87a8-123e-4645-a352-05639bb65638 ro
> cma=256MB "
>
>
You should update both EFI/fedora/grub.cfg and EFI/fedora/grubenv


> > But do be warned, there is no accelerated graphics on the RPi4 and
> > hence it is well and truly unsupported for any graphical systems.
> >
> > > On Fri, Apr 17, 2020 at 1:17 PM Peter Robinson <
> > > pbrobin...@gmail.com> wrote:
> > > >
> > > > On Fri, Apr 17, 2020 at 12:13 PM  wrote:
> > > > >
> > > > > Thanks for that! In one of latest images it gets stuck at the
> > > > > point shown in the attached screenshot.
> > > >
> > > > What image are you using, full file name please.
> > > >
> > > > What revision of the hardware do you have? You should have a line
> > > > at
> > > > the early U-Boot phase that looks something like:
> > > > RPI 4 Model B (0xc03111)
> > > >
> > > > I'm interested in the hex values at the end.
> > > >
> > > > > Good to have your clarification on RPi4 support in the Kernel.
> > > > >
> > > > > Thomas
> > > > >
> > > > > On Fri, Apr 17, 2020 at 12:01 PM Peter Robinson <
> > > > > pbrobin...@gmail.com> wrote:
> > > > > >
> > > > > > Hi Thomas,
> > > > > >
> > > > > > > Hi, testing of daily images from
> > > > > > >
> https://dl.fedoraproject.org/pub/fedora-secondary/development/32/Workstation/aarch64/images/
> > > > > > > Raspberry Pi 4 defies the keyboard.
> > > > > >
> > > > > > I'm not sure what you mean by defies in this context? They
> > > > > > keyboard
> > > > > > doesn't work? At what point are you having issues. There is
> > > > > > no support
> > > > > > for USB (actually the PCIe), hence keyboards, in the U-Boot
> > > > > > firmware
> > > > > > which means it won't work in grub or the early boot process.
> > > > > > Once it
> > > > > > gets to Linux such as the login prompt they keyboard should
> > > > > > work find
> > > > > > as there is USB support.
> > > > > >
> > > > > > > I have been under the assumption that 5.6 has support
> > > > > > > built-in? Any ideas?
> > > > > >
> > > > > > Support for what exactly? Support for a device such as the
> > > > > > RPi4 is not
> > > > > > a binary thing. There is initial support and enablement so
> > > > > > it's useful
> > > > > > for a number of situations but the support is far from
> > > > > > complete and
> > > > > > hence while for a it works for a lot of use cases we don't
> > > > > > officially
> > > > > > support the RPi4 yet because the HW enablement is incomplete.
> > > > > >
> > > > > > Peter
> ___
> arm mailing list -- arm@lists.fedoraproject.org
> To unsubscribe send an email to arm-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org
>
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org

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

[Steven A. Falco]

They change often.  Right now the latest is 
https://dl.fedoraproject.org/pub/fedora-secondary/development/rawhide/Spins/aarch64/images/Fedora-Minimal-Rawhide-20200422.n.0.aarch64.raw.xz

Just take the latest Minimal and you should be ok.

Steve

On 4/22/20 6:06 AM, ng0...@gmail.com wrote:

@gnome-desktop-environment

seems not to be available on Fedora-Minimal-Rawhide-20200421.n.0.aarch64.raw.xz 

from 
https://dl.fedoraproject.org/pub/fedora-secondary/development/rawhide/Spins/aarch64/images/

Any ideas? Much appreciate, Thomas

On Fri, Apr 17, 2020 at 8:47 PM Steven A. Falco mailto:stevenfa...@gmail.com>> wrote:

On 4/17/20 12:23 PM, ng0...@gmail.com  wrote:
 > Fedora-Workstation-32-20200416.n.0.aarch64.raw.xz
 >
 > I was not able to see the RPI 4 Model B (0x??) hex code, it scrolls 
too fast. How to find it on a running system?
 >
 > As recommended by other, I will go the minimal-first-way. But I do not 
know how to add a graphics package group e.g. Gnome?

This should install gnome:

dnf install @gnome-desktop-environment

A few other things that I found helpful:

1) I got lots of disconnects with 1 Gbps Ethernet, so I added the following 
to root's crontab (via crontab -e) to force the ethernet down to 100 Mbps:

@reboot sleep 10 ; /sbin/ethtool -s eth0 speed 100 duplex full

2) I was not able to login on the console serial port, because plymouth was 
interfering with agetty.  I removed plymouth via:

dnf remove plymouth

3) I had a problem with overscan - basically I had a black border all 
around the screen.  I fixed that by editing /boot/efi/config.txt and adding 
this line at the end of the file:

disable_overscan=1

         Steve

 >
 > Appreciate your help.
 >
 >
 > On Fri, Apr 17, 2020 at 1:17 PM Peter Robinson mailto:pbrobin...@gmail.com> >> wrote:
 >
 >     On Fri, Apr 17, 2020 at 12:13 PM mailto:ng0...@gmail.com> 
>> wrote:
 >      >
 >      > Thanks for that! In one of latest images it gets stuck at the 
point shown in the attached screenshot.
 >
 >     What image are you using, full file name please.
 >
 >     What revision of the hardware do you have? You should have a line at
 >     the early U-Boot phase that looks something like:
 >     RPI 4 Model B (0xc03111)
 >
 >     I'm interested in the hex values at the end.
 >
 >      > Good to have your clarification on RPi4 support in the Kernel.
 >      >
 >      > Thomas
 >      >
 >      > On Fri, Apr 17, 2020 at 12:01 PM Peter Robinson mailto:pbrobin...@gmail.com> >> wrote:
 >      >>
 >      >> Hi Thomas,
 >      >>
 >      >> > Hi, testing of daily images from 
https://dl.fedoraproject.org/pub/fedora-secondary/development/32/Workstation/aarch64/images/
 >      >>
 >      >> > Raspberry Pi 4 defies the keyboard.
 >      >>
 >      >> I'm not sure what you mean by defies in this context? They 
keyboard
 >      >> doesn't work? At what point are you having issues. There is no 
support
 >      >> for USB (actually the PCIe), hence keyboards, in the U-Boot 
firmware
 >      >> which means it won't work in grub or the early boot process. 
Once it
 >      >> gets to Linux such as the login prompt they keyboard should work 
find
 >      >> as there is USB support.
 >      >>
 >      >> > I have been under the assumption that 5.6 has support 
built-in? Any ideas?
 >      >>
 >      >> Support for what exactly? Support for a device such as the RPi4 
is not
 >      >> a binary thing. There is initial support and enablement so it's 
useful
 >      >> for a number of situations but the support is far from complete 
and
 >      >> hence while for a it works for a lot of use cases we don't 
officially
 >      >> support the RPi4 yet because the HW enablement is incomplete.
 >      >>
 >      >> Peter
 >
 >
 > ___
 > arm mailing list -- arm@lists.fedoraproject.org 

 > To unsubscribe send an email to arm-le...@lists.fedoraproject.org 

 > Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
 > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
 > List Archives: 
https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org
 >
___
arm mailing list -- arm@lists.fedoraproject.org 

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

[ng0177]

@gnome-desktop-environment

seems not to be available on
Fedora-Minimal-Rawhide-20200421.n.0.aarch64.raw.xz

from
https://dl.fedoraproject.org/pub/fedora-secondary/development/rawhide/Spins/aarch64/images/

Any ideas? Much appreciate, Thomas

On Fri, Apr 17, 2020 at 8:47 PM Steven A. Falco 
wrote:

> On 4/17/20 12:23 PM, ng0...@gmail.com wrote:
> > Fedora-Workstation-32-20200416.n.0.aarch64.raw.xz
> >
> > I was not able to see the RPI 4 Model B (0x??) hex code, it scrolls
> too fast. How to find it on a running system?
> >
> > As recommended by other, I will go the minimal-first-way. But I do not
> know how to add a graphics package group e.g. Gnome?
>
> This should install gnome:
>
> dnf install @gnome-desktop-environment
>
> A few other things that I found helpful:
>
> 1) I got lots of disconnects with 1 Gbps Ethernet, so I added the
> following to root's crontab (via crontab -e) to force the ethernet down to
> 100 Mbps:
>
> @reboot sleep 10 ; /sbin/ethtool -s eth0 speed 100 duplex full
>
> 2) I was not able to login on the console serial port, because plymouth
> was interfering with agetty.  I removed plymouth via:
>
> dnf remove plymouth
>
> 3) I had a problem with overscan - basically I had a black border all
> around the screen.  I fixed that by editing /boot/efi/config.txt and adding
> this line at the end of the file:
>
> disable_overscan=1
>
> Steve
>
> >
> > Appreciate your help.
> >
> >
> > On Fri, Apr 17, 2020 at 1:17 PM Peter Robinson  > wrote:
> >
> > On Fri, Apr 17, 2020 at 12:13 PM  ng0...@gmail.com>> wrote:
> >  >
> >  > Thanks for that! In one of latest images it gets stuck at the
> point shown in the attached screenshot.
> >
> > What image are you using, full file name please.
> >
> > What revision of the hardware do you have? You should have a line at
> > the early U-Boot phase that looks something like:
> > RPI 4 Model B (0xc03111)
> >
> > I'm interested in the hex values at the end.
> >
> >  > Good to have your clarification on RPi4 support in the Kernel.
> >  >
> >  > Thomas
> >  >
> >  > On Fri, Apr 17, 2020 at 12:01 PM Peter Robinson <
> pbrobin...@gmail.com > wrote:
> >  >>
> >  >> Hi Thomas,
> >  >>
> >  >> > Hi, testing of daily images from
> https://dl.fedoraproject.org/pub/fedora-secondary/development/32/Workstation/aarch64/images/
> >  >>
> >  >> > Raspberry Pi 4 defies the keyboard.
> >  >>
> >  >> I'm not sure what you mean by defies in this context? They
> keyboard
> >  >> doesn't work? At what point are you having issues. There is no
> support
> >  >> for USB (actually the PCIe), hence keyboards, in the U-Boot
> firmware
> >  >> which means it won't work in grub or the early boot process.
> Once it
> >  >> gets to Linux such as the login prompt they keyboard should work
> find
> >  >> as there is USB support.
> >  >>
> >  >> > I have been under the assumption that 5.6 has support
> built-in? Any ideas?
> >  >>
> >  >> Support for what exactly? Support for a device such as the RPi4
> is not
> >  >> a binary thing. There is initial support and enablement so it's
> useful
> >  >> for a number of situations but the support is far from complete
> and
> >  >> hence while for a it works for a lot of use cases we don't
> officially
> >  >> support the RPi4 yet because the HW enablement is incomplete.
> >  >>
> >  >> Peter
> >
> >
> > ___
> > arm mailing list -- arm@lists.fedoraproject.org
> > To unsubscribe send an email to arm-le...@lists.fedoraproject.org
> > Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives:
> https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org
> >
> ___
> arm mailing list -- arm@lists.fedoraproject.org
> To unsubscribe send an email to arm-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org
>
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org

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

[Thomas]

> 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 line.

I removed cma= but it had no effect, see below.

Thanks, Thomas


Fedora-Workstation-32-20200416.n.0.aarch64.raw.xz

/EFI/fedora/grub.cfg

  set kernelopts="root=UUID=72ca87a8-123e-4645-a352-05639bb65638 ro
cma=256MB "

> But do be warned, there is no accelerated graphics on the RPi4 and
> hence it is well and truly unsupported for any graphical systems.
> 
> > On Fri, Apr 17, 2020 at 1:17 PM Peter Robinson <
> > pbrobin...@gmail.com> wrote:
> > > 
> > > On Fri, Apr 17, 2020 at 12:13 PM  wrote:
> > > > 
> > > > Thanks for that! In one of latest images it gets stuck at the
> > > > point shown in the attached screenshot.
> > > 
> > > What image are you using, full file name please.
> > > 
> > > What revision of the hardware do you have? You should have a line
> > > at
> > > the early U-Boot phase that looks something like:
> > > RPI 4 Model B (0xc03111)
> > > 
> > > I'm interested in the hex values at the end.
> > > 
> > > > Good to have your clarification on RPi4 support in the Kernel.
> > > > 
> > > > Thomas
> > > > 
> > > > On Fri, Apr 17, 2020 at 12:01 PM Peter Robinson <
> > > > pbrobin...@gmail.com> wrote:
> > > > > 
> > > > > Hi Thomas,
> > > > > 
> > > > > > Hi, testing of daily images from 
> > > > > > https://dl.fedoraproject.org/pub/fedora-secondary/development/32/Workstation/aarch64/images/
> > > > > > Raspberry Pi 4 defies the keyboard.
> > > > > 
> > > > > I'm not sure what you mean by defies in this context? They
> > > > > keyboard
> > > > > doesn't work? At what point are you having issues. There is
> > > > > no support
> > > > > for USB (actually the PCIe), hence keyboards, in the U-Boot
> > > > > firmware
> > > > > which means it won't work in grub or the early boot process.
> > > > > Once it
> > > > > gets to Linux such as the login prompt they keyboard should
> > > > > work find
> > > > > as there is USB support.
> > > > > 
> > > > > > I have been under the assumption that 5.6 has support
> > > > > > built-in? Any ideas?
> > > > > 
> > > > > Support for what exactly? Support for a device such as the
> > > > > RPi4 is not
> > > > > a binary thing. There is initial support and enablement so
> > > > > it's useful
> > > > > for a number of situations but the support is far from
> > > > > complete and
> > > > > hence while for a it works for a lot of use cases we don't
> > > > > officially
> > > > > support the RPi4 yet because the HW enablement is incomplete.
> > > > > 
> > > > > Peter
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org

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

[Steven A. Falco]

On 4/17/20 12:23 PM, ng0...@gmail.com wrote:

Fedora-Workstation-32-20200416.n.0.aarch64.raw.xz

I was not able to see the RPI 4 Model B (0x??) hex code, it scrolls too 
fast. How to find it on a running system?

As recommended by other, I will go the minimal-first-way. But I do not know how 
to add a graphics package group e.g. Gnome?


This should install gnome:

dnf install @gnome-desktop-environment

A few other things that I found helpful:

1) I got lots of disconnects with 1 Gbps Ethernet, so I added the following to 
root's crontab (via crontab -e) to force the ethernet down to 100 Mbps:

@reboot sleep 10 ; /sbin/ethtool -s eth0 speed 100 duplex full

2) I was not able to login on the console serial port, because plymouth was 
interfering with agetty.  I removed plymouth via:

dnf remove plymouth

3) I had a problem with overscan - basically I had a black border all around 
the screen.  I fixed that by editing /boot/efi/config.txt and adding this line 
at the end of the file:

disable_overscan=1

Steve



Appreciate your help.


On Fri, Apr 17, 2020 at 1:17 PM Peter Robinson mailto:pbrobin...@gmail.com>> wrote:

On Fri, Apr 17, 2020 at 12:13 PM mailto:ng0...@gmail.com>> wrote:
 >
 > Thanks for that! In one of latest images it gets stuck at the point 
shown in the attached screenshot.

What image are you using, full file name please.

What revision of the hardware do you have? You should have a line at
the early U-Boot phase that looks something like:
RPI 4 Model B (0xc03111)

I'm interested in the hex values at the end.

 > Good to have your clarification on RPi4 support in the Kernel.
 >
 > Thomas
 >
 > On Fri, Apr 17, 2020 at 12:01 PM Peter Robinson mailto:pbrobin...@gmail.com>> wrote:
 >>
 >> Hi Thomas,
 >>
 >> > Hi, testing of daily images from 
https://dl.fedoraproject.org/pub/fedora-secondary/development/32/Workstation/aarch64/images/
 >>
 >> > Raspberry Pi 4 defies the keyboard.
 >>
 >> I'm not sure what you mean by defies in this context? They keyboard
 >> doesn't work? At what point are you having issues. There is no support
 >> for USB (actually the PCIe), hence keyboards, in the U-Boot firmware
 >> which means it won't work in grub or the early boot process. Once it
 >> gets to Linux such as the login prompt they keyboard should work find
 >> as there is USB support.
 >>
 >> > I have been under the assumption that 5.6 has support built-in? Any 
ideas?
 >>
 >> Support for what exactly? Support for a device such as the RPi4 is not
 >> a binary thing. There is initial support and enablement so it's useful
 >> for a number of situations but the support is far from complete and
 >> hence while for a it works for a lot of use cases we don't officially
 >> support the RPi4 yet because the HW enablement is incomplete.
 >>
 >> Peter


___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org


___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org

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

[ng0177]

>> As recommended by others, I will go the minimal-first-way. But I do not
know how to add a graphics package group e.g. Gnome?

>Just remove the cma= entry in the grub.cfg on the vfat partition it will
be easier, and an order of magnitude quicker.

OK, do you mean on the minimal or on the workstation edition?

On Fri, Apr 17, 2020 at 6:30 PM Peter Robinson  wrote:

> > Fedora-Workstation-32-20200416.n.0.aarch64.raw.xz
> >
> > I was not able to see the RPI 4 Model B (0x??) hex code, it scrolls
> too fast. How to find it on a running system?
>
> Not sure you currently can.
>
> > As recommended by other, I will go the minimal-first-way. But I do not
> know how to add a graphics package group e.g. Gnome?
>
> Just remove the cma= entry in the grub.cfg on the vfat partition it
> will be easier, and an order of magnitude quicker.
>
> But do be warned, there is no accelerated graphics on the RPi4 and
> hence it is well and truly unsupported for any graphical systems.
>
> > On Fri, Apr 17, 2020 at 1:17 PM Peter Robinson 
> wrote:
> >>
> >> On Fri, Apr 17, 2020 at 12:13 PM  wrote:
> >> >
> >> > Thanks for that! In one of latest images it gets stuck at the point
> shown in the attached screenshot.
> >>
> >> What image are you using, full file name please.
> >>
> >> What revision of the hardware do you have? You should have a line at
> >> the early U-Boot phase that looks something like:
> >> RPI 4 Model B (0xc03111)
> >>
> >> I'm interested in the hex values at the end.
> >>
> >> > Good to have your clarification on RPi4 support in the Kernel.
> >> >
> >> > Thomas
> >> >
> >> > On Fri, Apr 17, 2020 at 12:01 PM Peter Robinson 
> wrote:
> >> >>
> >> >> Hi Thomas,
> >> >>
> >> >> > Hi, testing of daily images from
> https://dl.fedoraproject.org/pub/fedora-secondary/development/32/Workstation/aarch64/images/
> >> >>
> >> >> > Raspberry Pi 4 defies the keyboard.
> >> >>
> >> >> I'm not sure what you mean by defies in this context? They keyboard
> >> >> doesn't work? At what point are you having issues. There is no
> support
> >> >> for USB (actually the PCIe), hence keyboards, in the U-Boot firmware
> >> >> which means it won't work in grub or the early boot process. Once it
> >> >> gets to Linux such as the login prompt they keyboard should work find
> >> >> as there is USB support.
> >> >>
> >> >> > I have been under the assumption that 5.6 has support built-in?
> Any ideas?
> >> >>
> >> >> Support for what exactly? Support for a device such as the RPi4 is
> not
> >> >> a binary thing. There is initial support and enablement so it's
> useful
> >> >> for a number of situations but the support is far from complete and
> >> >> hence while for a it works for a lot of use cases we don't officially
> >> >> support the RPi4 yet because the HW enablement is incomplete.
> >> >>
> >> >> Peter
>
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org

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

[Peter Robinson]

> Fedora-Workstation-32-20200416.n.0.aarch64.raw.xz
>
> I was not able to see the RPI 4 Model B (0x??) hex code, it scrolls too 
> fast. How to find it on a running system?

Not sure you currently can.

> As recommended by other, I will go the minimal-first-way. But I do not know 
> how to add a graphics package group e.g. Gnome?

Just remove the cma= entry in the grub.cfg on the vfat partition it
will be easier, and an order of magnitude quicker.

But do be warned, there is no accelerated graphics on the RPi4 and
hence it is well and truly unsupported for any graphical systems.

> On Fri, Apr 17, 2020 at 1:17 PM Peter Robinson  wrote:
>>
>> On Fri, Apr 17, 2020 at 12:13 PM  wrote:
>> >
>> > Thanks for that! In one of latest images it gets stuck at the point shown 
>> > in the attached screenshot.
>>
>> What image are you using, full file name please.
>>
>> What revision of the hardware do you have? You should have a line at
>> the early U-Boot phase that looks something like:
>> RPI 4 Model B (0xc03111)
>>
>> I'm interested in the hex values at the end.
>>
>> > Good to have your clarification on RPi4 support in the Kernel.
>> >
>> > Thomas
>> >
>> > On Fri, Apr 17, 2020 at 12:01 PM Peter Robinson  
>> > wrote:
>> >>
>> >> Hi Thomas,
>> >>
>> >> > Hi, testing of daily images from 
>> >> > https://dl.fedoraproject.org/pub/fedora-secondary/development/32/Workstation/aarch64/images/
>> >>
>> >> > Raspberry Pi 4 defies the keyboard.
>> >>
>> >> I'm not sure what you mean by defies in this context? They keyboard
>> >> doesn't work? At what point are you having issues. There is no support
>> >> for USB (actually the PCIe), hence keyboards, in the U-Boot firmware
>> >> which means it won't work in grub or the early boot process. Once it
>> >> gets to Linux such as the login prompt they keyboard should work find
>> >> as there is USB support.
>> >>
>> >> > I have been under the assumption that 5.6 has support built-in? Any 
>> >> > ideas?
>> >>
>> >> Support for what exactly? Support for a device such as the RPi4 is not
>> >> a binary thing. There is initial support and enablement so it's useful
>> >> for a number of situations but the support is far from complete and
>> >> hence while for a it works for a lot of use cases we don't officially
>> >> support the RPi4 yet because the HW enablement is incomplete.
>> >>
>> >> Peter
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org

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

[ng0177]

Fedora-Workstation-32-20200416.n.0.aarch64.raw.xz

I was not able to see the RPI 4 Model B (0x??) hex code, it scrolls too
fast. How to find it on a running system?

As recommended by other, I will go the minimal-first-way. But I do not know
how to add a graphics package group e.g. Gnome?

Appreciate your help.


On Fri, Apr 17, 2020 at 1:17 PM Peter Robinson  wrote:

> On Fri, Apr 17, 2020 at 12:13 PM  wrote:
> >
> > Thanks for that! In one of latest images it gets stuck at the point
> shown in the attached screenshot.
>
> What image are you using, full file name please.
>
> What revision of the hardware do you have? You should have a line at
> the early U-Boot phase that looks something like:
> RPI 4 Model B (0xc03111)
>
> I'm interested in the hex values at the end.
>
> > Good to have your clarification on RPi4 support in the Kernel.
> >
> > Thomas
> >
> > On Fri, Apr 17, 2020 at 12:01 PM Peter Robinson 
> wrote:
> >>
> >> Hi Thomas,
> >>
> >> > Hi, testing of daily images from
> https://dl.fedoraproject.org/pub/fedora-secondary/development/32/Workstation/aarch64/images/
> >>
> >> > Raspberry Pi 4 defies the keyboard.
> >>
> >> I'm not sure what you mean by defies in this context? They keyboard
> >> doesn't work? At what point are you having issues. There is no support
> >> for USB (actually the PCIe), hence keyboards, in the U-Boot firmware
> >> which means it won't work in grub or the early boot process. Once it
> >> gets to Linux such as the login prompt they keyboard should work find
> >> as there is USB support.
> >>
> >> > I have been under the assumption that 5.6 has support built-in? Any
> ideas?
> >>
> >> Support for what exactly? Support for a device such as the RPi4 is not
> >> a binary thing. There is initial support and enablement so it's useful
> >> for a number of situations but the support is far from complete and
> >> hence while for a it works for a lot of use cases we don't officially
> >> support the RPi4 yet because the HW enablement is incomplete.
> >>
> >> Peter
>
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org

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

[Steven A. Falco]

On 4/17/20 7:34 AM, Frantisek Zatloukal wrote:

On Fri, Apr 17, 2020, 13:21 Michael Young mailto:m.a.yo...@durham.ac.uk>> wrote:

On Fri, 17 Apr 2020, ng0...@gmail.com  wrote:

 > Thanks for that! In one of latest images it gets stuck at the point 
shown in
 > the attached screenshot.
 > Good to have your clarification on RPi4 support in the Kernel.


I hit the same issue while trying to run F32 Workstation aarch64 (RC1.3) on my 
rpi4.

I'll add some more information once I get to the rpi4. One way to workaround 
this is to use Minimal aarch64 raw.xz and then install workstation package 
group...


I had that experience too.  Start with the Minimal image, which should install 
and boot just fine.  Then add a graphics package group of your choice.  I'm 
using KDE on my Pi 4.

Steve
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org

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

[Frantisek Zatloukal]

On Fri, Apr 17, 2020, 13:21 Michael Young  wrote:

> On Fri, 17 Apr 2020, ng0...@gmail.com wrote:
>
> > Thanks for that! In one of latest images it gets stuck at the point
> shown in
> > the attached screenshot.
> > Good to have your clarification on RPi4 support in the Kernel.


I hit the same issue while trying to run F32 Workstation aarch64 (RC1.3) on
my rpi4.

I'll add some more information once I get to the rpi4. One way to
workaround this is to use Minimal aarch64 raw.xz and then install
workstation package group...
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org

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

[Michael Young]

On Fri, 17 Apr 2020, ng0...@gmail.com wrote:


Thanks for that! In one of latest images it gets stuck at the point shown in
the attached screenshot.
Good to have your clarification on RPi4 support in the Kernel.


I had a similar issue with recent kernels that I solved by removing a 
cma= setting from the kernel boot line.


Michael Young
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org

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

[Peter Robinson]

On Fri, Apr 17, 2020 at 12:13 PM  wrote:
>
> Thanks for that! In one of latest images it gets stuck at the point shown in 
> the attached screenshot.

What image are you using, full file name please.

What revision of the hardware do you have? You should have a line at
the early U-Boot phase that looks something like:
RPI 4 Model B (0xc03111)

I'm interested in the hex values at the end.

> Good to have your clarification on RPi4 support in the Kernel.
>
> Thomas
>
> On Fri, Apr 17, 2020 at 12:01 PM Peter Robinson  wrote:
>>
>> Hi Thomas,
>>
>> > Hi, testing of daily images from 
>> > https://dl.fedoraproject.org/pub/fedora-secondary/development/32/Workstation/aarch64/images/
>>
>> > Raspberry Pi 4 defies the keyboard.
>>
>> I'm not sure what you mean by defies in this context? They keyboard
>> doesn't work? At what point are you having issues. There is no support
>> for USB (actually the PCIe), hence keyboards, in the U-Boot firmware
>> which means it won't work in grub or the early boot process. Once it
>> gets to Linux such as the login prompt they keyboard should work find
>> as there is USB support.
>>
>> > I have been under the assumption that 5.6 has support built-in? Any ideas?
>>
>> Support for what exactly? Support for a device such as the RPi4 is not
>> a binary thing. There is initial support and enablement so it's useful
>> for a number of situations but the support is far from complete and
>> hence while for a it works for a lot of use cases we don't officially
>> support the RPi4 yet because the HW enablement is incomplete.
>>
>> Peter
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org

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

[Peter Robinson]

Hi Thomas,

> Hi, testing of daily images from 
> https://dl.fedoraproject.org/pub/fedora-secondary/development/32/Workstation/aarch64/images/

> Raspberry Pi 4 defies the keyboard.

I'm not sure what you mean by defies in this context? They keyboard
doesn't work? At what point are you having issues. There is no support
for USB (actually the PCIe), hence keyboards, in the U-Boot firmware
which means it won't work in grub or the early boot process. Once it
gets to Linux such as the login prompt they keyboard should work find
as there is USB support.

> I have been under the assumption that 5.6 has support built-in? Any ideas?

Support for what exactly? Support for a device such as the RPi4 is not
a binary thing. There is initial support and enablement so it's useful
for a number of situations but the support is far from complete and
hence while for a it works for a lot of use cases we don't officially
support the RPi4 yet because the HW enablement is incomplete.

Peter
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org