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 
<https://dl.fedoraproject.org/pub/fedora-secondary/development/rawhide/Spins/aarch64/images/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 <stevenfa...@gmail.com 
<mailto:stevenfa...@gmail.com>> wrote:

    On 4/17/20 12:23 PM, ng0...@gmail.com <mailto: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 <pbrobin...@gmail.com 
<mailto:pbrobin...@gmail.com> <mailto:pbrobin...@gmail.com 
<mailto:pbrobin...@gmail.com>>> wrote:
     >
     >     On Fri, Apr 17, 2020 at 12:13 PM <ng0...@gmail.com <mailto:ng0...@gmail.com> 
<mailto:ng0...@gmail.com <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 <pbrobin...@gmail.com 
<mailto:pbrobin...@gmail.com> <mailto:pbrobin...@gmail.com 
<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 
<mailto:arm@lists.fedoraproject.org>
     > To unsubscribe send an email to arm-le...@lists.fedoraproject.org 
<mailto: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 
<mailto:arm@lists.fedoraproject.org>
    To unsubscribe send an email to arm-le...@lists.fedoraproject.org 
<mailto: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

Reply via email to