> > This is the (relevant) output from /proc/cpuinfo:
> > Hardware : BCM2835
> > Revision : c03111
> > Serial : 100094b1358a
> > Model : Raspberry Pi 4 Model B Rev 1.1
>
> this should work with Linux 5.6. So i don't have an idea what's the
> problem here.
>
> Rev 1.2 needs recent changes to
On Sun, 5 Apr 2020, Fred van Zwieten wrote:
OK, my issue was a "glitch in the matrix". I retried with another sd-card
(Kingston 8GB) and it now just works! My use case is server only, so I will
not test any desktop stuff.
I worked out how to get my pi4 working the 5.6.2-300.fc32.aarch64
Hi,
OK, my issue was a "glitch in the matrix". I retried with another sd-card
(Kingston 8GB) and it now just works! My use case is server only, so I will
not test any desktop stuff.
- Fred
On Sat, Apr 4, 2020 at 1:46 AM Thomas H.P. Andersen
wrote:
>
>
> On Fri, Apr 3, 2020 at 6:13 PM Stefan
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
>
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
> target, I used the rpi3 value. It does boot, but, like I said, it
>
Hi Peter,
Yeah, I currently run Buster on it. As soon as I can get to an RH based
aarch distro, I jump.
Fedora 32 aarch is the one, I hope...
- Fred
On Fri, Apr 3, 2020 at 1:17 PM Peter Robinson wrote:
> > I haven't retried it yet, but I do have some extra info on my previous
> (and failed)
On Fri, 3 Apr 2020, Fred van Zwieten wrote:
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
target, I used the rpi3 value. It does boot, but, like I said, it hangs in a
later
> 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
> target, I used the rpi3 value. It does boot, but, like I said, it hangs in a
> later stage. I will provide screenshots
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
target, I used the rpi3 value. It does boot, but, like I said, it hangs in
a later stage. I will provide screenshots when I am able
Hello Dirk,
I've tried it with balenaEtcher: It works !!
Thank you for that tip !!
Andreas
PS: I dind't know why it not works with xzcat and dd but now I have a
working method.
Am 03.04.20 um 10:23 schrieb Dirk Streubel:
Hello together,
Hello Dirk
how did you you install
> Hello together,
>
> Hello Dirk
>
> how did you you install Fedora-Minimal-32_Beta-1.2.aarch64.raw.xz on SD-Card?
>
> Just xzcat Fedora-Minimal-32_Beta-1.2.aarch64.raw.xz | dd of=/dev/sdc
> status=progress bs=4M
>
> didn't work for me. All I get is a dracut shell
>
>
> Thanks
>
> Andreas
Hello
Am 03.04.20 um 09:28 schrieb Dirk Streubel:
Hello Paul,
Am 02.04.20 um 18:31 schrieb Paul Whalen:
Hi Fred,
- Original Message -
I tried Fedora-Minimal-32_Beta-1.2.aarch64.raw.xz but it did not work for me
What didnt work?
The minimal image should work OK (running it on two
Hello Paul,
Am 02.04.20 um 18:31 schrieb Paul Whalen:
> Hi Fred,
>
> - Original Message -
>> I tried Fedora-Minimal-32_Beta-1.2.aarch64.raw.xz but it did not work for me
> What didnt work?
>
> The minimal image should work OK (running it on two RPi4's). Desktop and
> server
> images
Hi Paul,
>From memory, it first hung for a long time before continuing and later it
hung indefinitely (well, as long as my patience was). I will retry later
and update the thread. I only have 1 rpi4 and it is in use as my private
cloud, so i can not experiment at will.
- Fred
On Thu, Apr 2,
Hi Fred,
Am 02.04.20 um 18:17 schrieb Fred van Zwieten:
> I tried Fedora-Minimal-32_Beta-1.2.aarch64.raw.xz but it did not work
> for me
>
could you also please tell which hardware revision of the Raspberry Pi 4
you are using?
https://imgur.com/a/FH3gmYA
Regards
Stefan
Hi Fred,
- Original Message -
> I tried Fedora-Minimal-32_Beta-1.2.aarch64.raw.xz but it did not work for me
What didnt work?
The minimal image should work OK (running it on two RPi4's). Desktop and server
images are currently broken as others have mentioned.
>
> On Thu, Apr 2,
I tried Fedora-Minimal-32_Beta-1.2.aarch64.raw.xz but it did not work for me
On Thu, Apr 2, 2020 at 3:52 PM Andreas Reschke wrote:
> Hello Thomas
>
> I think that I have taken the Fedora-Workstation-31-1.9.aarch64.raw.xz to
> install my Raspi4.
>
> Do you mean the
Hello Thomas
I think that I have taken the Fedora-Workstation-31-1.9.aarch64.raw.xz
to install my Raspi4.
Do you mean the Fedora-Minimal-32_Beta-1.2.aarch64.raw.xz Image? I will
try it with another SD-Card.
thanks
Andreas
Am 02.04.20 um 15:43 schrieb Thomas H.P. Andersen:
Hi Andreas
I
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
19 matches
Mail list logo
