Fedora on allwinner h616
by fs 3000
Hello guys,
I have a orange pi zero 2 board. With a h616 soc. I have tried dd'ing the .raw file in to microsd card with the Fedora 35 image, even some centos ones. Nothing happens, it doesn't boot. After dd'iong the main image file, i I even tried copying the u-boot file like the centos wiki shows, same result, nothing.
dd if=/root/orangepi_zero2/u-boot-sunxi-with-spl.bin of=/dev/sdc bs=1024 seek=8 conv=fsync,notrunc
Is there a way to make fedora or even centos working on this board? That would be great.
Many thanks in advance for any pointers on this.
10 months
Re: wondering about a few kernel config options
by Justin Forbes
On Tue, Apr 26, 2022 at 9:15 PM Dusty Mabe <dustymabe(a)redhat.com> wrote:
>
> Hey jforbes,
>
> I'm looking at buying a quartz64 ARM board (relatively new board
> from pine64 kind of like a Raspberry Pi) [1]. I think there are
> some config options in the kernel that need to be set. I found where
> someone opened a PR for Arch [2]. I compared that with what we have
> in the Fedora aarch64 kernel config and here's what would need to change:
>
> CONFIG_MMC_SDHCI_OF_DWCMSHC is not set -> y
> CONFIG_MOTORCOMM_PHY=m -> y
>
> Is changing kernel config options a big ask or a reasonable request?
This should not be a problem. I am CCing arm(a)lists.fedoraproject.org
so that others are aware. I will try to remember for 5.17.5 tomorrow,
but on vacation travelling by motorcycle this week, so if I forget,
remind me early next week.
Justin
> Thanks for your advice on this,
> Dusty
>
> [1] https://www.pine64.org/quartz64a/
> [2] https://github.com/archlinuxarm/PKGBUILDs/pull/1918
>
10 months, 4 weeks
Raspberry Pi PoE HAT
by Ben Herrick
Fedora ARM mailing list,
I've been trying to get the fan on my Raspberry Pi PoE HAT working with
Fedora 35 and 36 Beta. I'm using the aarch64 raw image.
I came across the instructions on the wiki page
here: https://fedoraproject.org/wiki/Architectures/ARM/Raspberry_Pi/HATs#...
Unfortunately, the line in config.txt from the wiki didn't work for me.
The lines that did work on Fedora 36 Beta for aarch64 are below:
dtoverlay=i2c
dtoverlay=pwm-raspberrypi-poe
I'm also able to set the fan parameters with the below:
dtparam=poe_fan_temp0=70000,poe_fan_temp0_hyst=10000
dtparam=poe_fan_temp1=60000,poe_fan_temp1_hyst=10000
dtparam=poe_fan_temp2=50000,poe_fan_temp2_hyst=10000
dtparam=poe_fan_temp3=40000,poe_fan_temp3_hyst=10000
Note that these same lines didn't work for me on Fedora 35 aarch64.
I'm hoping others can replicate my experience and the wiki can be
updated to help others.
Please let me know if you have any questions or concerns.
-Ben Herrick
11 months
Migrate wiki to docs.fedoraproject.org?
by Peter Boy
We just had a short discussion about Quick Docs and RPi. The idea / suggestion came up to migrate all or part of the Arm wiki pages to docs.fp.o. This would involve establishing ARM Sig as an "engineering team“ (cf. https://docs.fedoraproject.org/en-US/engineering/) and would significantly increase visibility.
I reckon I read „somewhere some time ago" that someone was working on such a migration. I would be happy to contribute if support would be helpful.
If my recollection is incorrect and nevertheless, the Arm Group considers a migration desirable, I would be happy to work on such a migration. I would see this as an opportunity to actively contribute and not just be a "consumer" of the work of others here.
(I’m writing most of the Server Edition documentation and contribute to docs Team, so I hopefully know what I’m doing)
11 months, 3 weeks
Re: Clarification of RPi 4 support
by Peter Robinson
Please keep cc:s in tact
> > Can we also delete the FAQ section as well and just direct them to the
> > wiki, I have no idea who added this but I don't ever remember being
> > consulted.
>
> What is that bad with the FAQ section? There are some helpful informations. Probably just add a „note“ box and a link to the corresponding arm wiki? (Saying the arm wiki is the one maintained by arm maintainer and therefore the authoritative one)
Well it's basically the one in the FAQ except it's not updated. Why
duplicate the information unnecessarily.
11 months, 3 weeks