Thank you to all yous guys who are working so hard to get Fedora
running smoothly on the Raspberry Pi 4.
Here
is a photo of my Streaming DAC (with the lid off) that runs Fedora
34 + mpd + Chinese DAC board. It plays PCM and up to DSD512 from a
NAS. The Pi 4
I tried updating my Fedora 34 kernel from-
5.11.17-300
to
5.12.14-300
and it no longer recognises my XMOS USB device:
$ cat /proc/asound/cards
0 [ALSA ]: bcm2835_alsa - bcm2835 ALSA
bcm2835 ALSA
1 [vc4hdmi0 ]: vc4-hdmi - vc4-hdmi-0
On 11/07/2021 14:19, Peter Robinson wrote:
On Fri, Jul 9, 2021 at 2:44 PM David W. Legg wrote:
On 09/07/2021 14:19, Peter Robinson wrote:
Please leave the list on replies.
On Fri, Jul 9, 2021 at 1:30 PM David W. Legg wrote:
On 09/07/2021 12:38, Peter Robinson wrote:
Adding arm@ list
On 09/07/2021 14:19, Peter Robinson wrote:
Please leave the list on replies.
On Fri, Jul 9, 2021 at 1:30 PM David W. Legg wrote:
On 09/07/2021 12:38, Peter Robinson wrote:
Adding arm@ list back in.
On Fri, Jul 9, 2021 at 12:37 PM Peter Robinson wrote:
On Fri, Jul 9, 2021 at 12:30 PM
So, I installed Fedora-Minimal-33-1.3.aarch64.raw.xz on my RPI4, fully
updated it (05/03/2021) turned on root logins using ssh and turned off
selinux.
It boots nicely and lets me login etc., until I try and boot without a
monitor on one of the HDMI connectors.
The LEDs cycle around the same
You might need to review the previous emails from me with replied from
Peter Robinson about using
rpi-uboot-update after updates.
:D
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org
uld you provide more details
This will make it easier to help you.
Il giorno 8 gen 2022, alle ore 21:14, Peter Robinson ha
scritto:
On Sat, Jan 8, 2022 at 8:09 PM David W. Legg wrote:
Just wondering why my attempt to move a working headless Fedora 34 build
from a 2 GB rpi4 to a 4 GB rpi
both ways so
that it can't go wrong, i.e. get chopped
Good thought, though. Thanks.
On Sun, 9 Jan 2022, 13:35 Dennis Gilmore, wrote:
Adding count probably cut the image short, it is not necessary, I generally
always us bs=4MiB
Dennis
On Sun, Jan 9, 2022, 03:54 David W. Legg wrote:
Well, I
So, here is my (temporary) solution, as reported in Bugzilla bug
https://bugzilla.redhat.com/show_bug.cgi?id=2011423
So my 4GB rpi4 refused to boot with the symptoms described about, i.e. mmc0
errors.
I also found that Fedora-Minimal-34-1.2.aarch64.raw.xz and
Yes, Paul, I tried 2 different makes of card and four different cards, 3
different power supplies, and 2 different ways of writing the cards.
On 13/01/2022 20:59, Paul Whalen wrote:
Have you tried a different mSD card?
___
arm mailing list --
So, this is the continuation of the above saga.
With a brand *new* rpi4, I made two different 32GB SD cards of different
makes from both:
Fedora-Minimal-34-1.2.aarch64.raw.xz
and
Fedora-Minimal-35-1.2.aarch64.raw.xz
I did not fiddle with partition sizes or anything like that, but I did
Nice. I now have a:
Linux nas3
5.15.14-200.fc35.aarch64 (NB. 14 instead of 13)
running
headless and fully up to date wrt. dnf on the (presumably) newer
build standard of rpi4 4GB.
The
only oddity is that now the red LED
Just in case anyone thought the GPIO-related F35 problems were
limited to newer Pi 4s and Pi 400s, I can confirm that even my old
Pi 3B is similarly afflicted.
1. Install Fedora 35 aarch64 onto micro SD card:
arm-image-installer
So, with respect to my previous email, do I need to do the previously
recommended command:
echo "FirmwareDT=True" >> /etc/u-boot.conf
Or, is that only the case for a Pi 4? Is it still needed when using a Pi 3B?
I have lost track of what medicine is needed when! :(
:D
Just to supplement Stephan Wahren's observations about Pi 4s:-
I have tried the latest beta F36 with my Pi 3B+, and the GPIOs do not
seem to work (yet):
i.e. Fedora-Minimal-36_Beta-1.4.aarch64.raw.xz
The command, gpioset `gpiofind GPIO27`=0, seems to do nothing, as does
'=1' instead of the
"awkward this is"
On 18/01/2022 11:42, Stefan Wahren wrote:
the DTB
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org
Fedora Code of Conduct:
Just wondered if gpioset etc is
working yet on rpi4/Fedora 35?
gpioinfo and gpiodetect both seem happy, for example:
# gpiodetect
gpiochip0 [pinctrl-bcm2711] (58 lines)
gpiochip1 [raspberrypi-exp-gpio] (8 lines)
but gpioset does this:
Just wondering why my attempt to move a working headless Fedora 34 build
from a 2 GB rpi4 to a 4 GB rpi4 fails even to boot. In fact, it never
even puts out the steady red LED. I copied the micro SD card (from the 2
GB pi) directly over USB and wrote the build to another SD card using dd
using
Am 22.01.22 um 12:42 schrieb David W. Legg:
Ah, do you mean the red power LED that stays on after boot?
Yes
If so, will an updated F35 kernel fix it, or should I go back to F34
Yes, just to confirm that I still have the gpio/LED problem with the
latest kernel:
# gpioset `gpiofind GPIO27`=1
gpioset: error setting the GPIO line values: Unknown error 517
# uname -a
Linux arcturus.home 5.15.16-100.fc34.x86_64 #1 SMP Thu Jan 20 16:34:27
UTC 2022 x86_64 x86_64 x86_64
Enthused by my success with getting Fedora 35 going on mu rpi4, I
thought I would try an update :)
Starting from Fedora-Minimal-35-1.2.aarch64.raw.xz, I tried to upgrade
the kernel from
5.14.10-300.fc35.aarch64
to
5.15.13-200.fc35.aarch64.
So, I did a(n)
rpi-uboot-update
then dnf update
So, then I reverted to my working 5.14.10 kernel and did a:
dnf update --exclude=kernel*
which included an update up to:
uboot-images-armv8-2021.10-2.fc35.noarch
and re-booted.
Everything is fine.
So, the only
known problem I have is the
I suspect that, with the shortage of chips from China, we are dredging
the bottom of the barrel and are buying some Raspberry Pis with
anomalous, early or unusual hardware or firmware behaviour. :(
On 13/01/2022 21:07, Chris Adams wrote:
Hmm, I picked up a Pi4 4G recently, and was also unable
I have some RPIs with pairs of SATA disks attached.
One is an RPI4 which has 2 5TB SATA disks attached. It seems to supply
data at about 108MB/s over a 1Gb Ethernet connection, which pretty well
maxes the network out. The disks themselves are simply* attached using
the USB 3.0 connectors on
24 matches
Mail list logo
