Re: Change in kernel PPS GPIO handling?
by Stefan Wahren
Hi Peter,
Am 31.03.22 um 15:19 schrieb Peter Robinson:
> Hi Stefan,
>
>>>> At least the 32 bit issues on Raspberry Pi 4 are expected since the
>>>> kernel config doesn't have ARM_LPAE enabled.
>>>>
>>> Okay, here is the explanation for the different behavior on Raspberry Pi
>>> 400 and Raspberry Pi 4 B. The Raspberry Pi 400 has a newer BCM2711 SoC
>>> (Stepping C0), which have less DMA restrictions for the emmc2 interface
>>> (responsible for SD card access). For the Raspberry Pi 4 B there are
>>> older boards which have Stepping B0 and all the new boards should have
>>> Stepping C0 [1].
>>>
>>> Unfortunately there is no 100% reliable way to detect the stepping from
>>> the kernel side. So currently the Raspberry Pi firmware patches the
>>> dma-ranges in the firmware DT [2]. So in case U-Boot [3] or another
>>> bootloader ignores this firmware DT and read a fresh DTB the right
>>> dma-ranges get lost. Finally this results in unexpected behavior as soon
>>> the emmc2 switches to DMA mode [4].
>>>
>> Okay, at least i found a fix [1] for the 64 bit boot issues (Original
>> Fedora 35, Linux 5.14) with RPi 400/RPi 4 Stepping C0. This requires the
>> DTB files to be updated and U-Boot to choose between the B0 and the C0
>> variant of the Rpi 4 DTB file.
> Thanks for the update on this, great news. In the case of the RPi-400
> are they all the C0 stepping? I don't see the 400 in your patch.
Yes, please look at [1]
The patch changes makes bcm2711.dtsi default to C0. So all including RPi
4 boards (RPi 4, CM4, RPi 400) will be affected and all new boards don't
need to care about it.
> Is there a documented way of detecting the stepping that can be used
> in U-Boot I can use to create a patch there, or did you have a test
> patch for this?
I searched in the Raspberry Pi forum and there was the statement that
there is no direct (official) way to detect the SoC stepping. A
possibility might be to detect the DMA range provided by the firmware
FDT (U-Boot has dev_get_dma_range() for this) and based on the value
decide which DTB should be loaded (bcm2711-rpi-4-b.dtb for C0 and
bcm2711-rpi-4-b-b0.dtb for B0).
> Do you plan to send this patch upstream, if so feel free to add me to
> the cc and in the mean time I'll test it.
Yes. I didn't send it yet, because the merge window is currently open
and i want to rebase it on 5.18-rc1. The patch itself is a little bit
controversial (fix which introduce new file and change behavior).
Best regards
>
>> Unfortunately this doesn't fix the SD card issues on 32 bit.
> That's less of a problem, Fedora 36 will be the last version of Fedora
> to support 32 bit and I've always suggested people run 64 bit Fedora
> on their RPi4 and most people do tend to do that.
>
> Thanks,
> Peter
[1] - https://github.com/raspberrypi/firmware/issues/1704
2 years, 2 months
Re: [fedora-arm] [SOLVED] Fedora 21 on Raspberry PI 2
by Bob Goodwin
On 13/05/15 17:14, Dario Lesca wrote:
> Il giorno mar, 12/05/2015 alle 10.14 +0200, Dario Lesca ha scritto:
>> >Follow this how to:
>> >
>> >http://jonarcher.info/2015/02/getting-fedora-21-raspberry-pi-2/
>> >
>> >I have load and update a official F21 arm7 (minimal install) on a new
>> >raspberry PI 2, to make network backup of some server on a 1Gb USB hd
>> >via rsync.
>> >
>>> > >Linux s-backup-lampo 3.18.12-v7+ #783 SMP PREEMPT Tue May 5 22:48:52 BST 2015 armv7l armv7l armv7l GNU/Linux
>> >
>> >Apparent all work find, but after a while rsync run, the mount point go
>> >in read only mode and rsync stop to work with this error:
>> >
>>> > >rsync: write failed on "/mnt/metal-bk-1t/temp2/dir/file": Input/output error (5)
>>> > >rsync error: error in file IO (code 11) at receiver.c(393) [receiver=3.1.1]
>> >
>> >And in dmesg and journalctl I see a lot of this message:
>> >
>>> > >mag 11 09:01:17 s-backup-lampo.ansaldisrl.it kernel: XFS (sda1): xfs_log_force: error -5 returned.
>>> > >....
>> >
> It was a power problem.
> I have connect hard disk to a USB HUB powered an now all work fine!
>
> Thanks.
> -- Dario Lesca (inviato dal mio Linux Fedora 21 con Gnome 3.14)
After seeing your message here I tried Jon Archer's image on the
raspberry pi 2 b and It does provide a working F-21!
However it looks like I will have to put in some more effort:
[bobg@raspberrypi ~]$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/root 1.3G 1.2G 44M 97% /
devtmpfs 460M 0 460M 0% /dev
tmpfs 464M 0 464M 0% /dev/shm
tmpfs 464M 364K 464M 1% /run
tmpfs 464M 0 464M 0% /sys/fs/cgroup
/dev/mmcblk0p1 488M 15M 474M 3% /boot
tmpfs 93M 0 93M 0% /run/user/1000
tmpfs 93M 0 93M 0% /run/user/0
It is limited by having everything stuffed into 2 gigs of a 16GB SD
card. However I am happy to see this much working and be able to work in
familiar territory instead of the orignal Raspian.
Bob
--
Bob Goodwin - Zuni, Virginia, USA
http://www.qrz.com/db/W2BOD
box10 FEDORA-22b/64bit LINUX XFCE
9 years
Re: [fedora-arm] beginning of Fedora support for the Raspberry Pi 2
by Andrew Gillis
That's correct. There is no SATA interface on the Raspberry Pi 2.
-Andrew
On Wed, Feb 4, 2015 at 1:49 PM, Robert Moskowitz <rgm(a)htt-consult.com>
wrote:
>
> On 02/04/2015 10:43 AM, Peter Robinson wrote:
>
>> Hi All,
>>
>> As a follow up of the discussion that happened at the last ARM meeting
>> (and because 3 days post announcement of it I'm sick of repeating
>> myseld:-P ) I thought I'd outline the process for getting support for
>> the Raspberry Pi 2 into Fedora
>>
>
> Just a small question...
>
> I have not found a schematic, but the pics do not seem to show a SATA
> interface. Is this correct?
>
> No SATA, I have no time for it; I am already crunched for time.
>
> Though it would be nice.
>
>
> _______________________________________________
> arm mailing list
> arm(a)lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/arm
--
Andrew Gillis
Lead Developer VortexBox
vortexbox.org
9 years, 4 months
Re: Raspberry Pi and its 7" display
by Peter Robinson
On Wed, Dec 12, 2018 at 10:18 AM Torbjorn Jansson
<torbjorn.jansson(a)mbox200.swipnet.se> wrote:
>
> On 2018-12-11 03:20, Peter Robinson wrote:
> >> I'd like to turn this into a MythTV server (with a USB capture) and use
> >> the display as a system console with the ability to watch videos on it.
> >> (Yeah, I'm aware that its only a 800x400 screen.) Failing that, I'd
> >> like to use it in a "tablet" mode and get used to the touch screen
> >> interface.
> >
> > Well when it's supported upstream it will be enabled.
> >
> > [1] https://fedoraproject.org/wiki/Architectures/ARM/Raspberry_Pi#Is_the_Rasp...
>
>
> A bit off-topic but i just checked the url above and noticed something:
> Under section "Power Supplies" we have this text:
> "The Raspberry Pi 3 Series needs a 2.5W PSU"
>
> Surely this must be a typo, 2.5W would mean 5v at 500mA and that's unlikely to
> be enough for a rpi3, even older official power supplies was 2amp and that is 10W
>
> So it must be Amps and not Watts.
Correct, the PSU stuff is also covered in prerequisites and it was
correct there and links there to the official Raspberry Pi PSU docs,
I've also updated the other bit.
5 years, 5 months
Re: Unable to see 'Initial setup wizard' on Raspberry PI 3 using aarch64 images
by Peter Robinson
On Wed, Nov 22, 2017 at 9:37 AM, Ashwin Rao <ashwin.shirvanthe(a)gmail.com> wrote:
> Hi,
>
> When running the aarch64 Workstation, Server, and Minimal images I am not able to see the initial setup wizard. I can see the messages shown during boot but after some time the screen either starts to flicker or just blanks out. I tried this on 3 different raspberry Pis with different cards and the result is always the same.
> The steps I followed are
> 1. I downloaded the aarch64 images from [ https://fedoraproject.org/wiki/Architectures/ARM/Raspberry_Pi#Raspberry_P... ] and followed the instructions mentioned on the same web page to prepare the images using xzcat.
> 2. I connect the HDMI cable of my monitor, and connect the keyboard and mouse. I am not connecting an Ethernet cable.
> 3. I can see the boot screen, and the messages showing that the device is booting.
> 4. After some time the screen either blanks out or starts to flicker. I have tried it with different monitors and different power supplies as well but the result is the same. I noticed that the red LED of the Raspberry Pi also starts to blink abruptly.
>
> I am able to use Raspbian and OpenSuse using the same Raspberry Pis so I doubt there is an issue with the card, the power supply, or with the Pis.
>
> It would be nice if someone suggests the things I need to do, or if someone was able to troubleshoot similar issues.
The problem is with either the monitor or the HDMI cable, the VC4 open
driver (which neither of the other distros use yet) can be a bit
fragile with some EDID responses from some monitors or cables (yes
we've had people with issues that were fixed when they swapped the
HDMI cable). It's improved a lot since F-25 when we first started
supporting the RPi but it's not perfect yet.
On the case of Server and Minimal if you never want to use a graphical
interface and are happy with just the text console you can add a
blacklist so the GPU driver isn't laoded on boot. This can be done by
adding blacklist=vc4 to the kernel command line or creating a file
/etc/modprobe.conf/vc4.conf with the line "blacklist vc4"
Peter
6 years, 6 months
Re: Raspberry Pi 3+
by Peter Robinson
On Fri, Mar 23, 2018 at 11:28 AM, Tomáš Frolík <tomas.frolik2(a)gmail.com> wrote:
> I am a fan Fedora project and Raspberry, too, I have a whole new piece RPi 3+ in the drawer for only a few days. Nevertheless, there is no functional combination RPi 3+ and Fedora. I will be excited when it will be ready to use. Can you here indicate the functional image is released when it will happen?
Everything is in Fedora 28+ now.... well almost. The 4.16rc6 kernel
has a bootable DT, that's not yet in the F-28 nightly images though
due to the beta freeze.
There's all the bits in the firmware/u-boot though. So on a F-28
nightly image if you set a card up as per usual for a Raspberry Pi 3
and then do one other command it'll boot.
Once you've set up the card all you have to do is copy the RPi3 DT to
a 3plus DT and it'll do an initial boot. Once it's booted you can then
just upgrade the kernel and it'll be fine moving forward.
On ARMv7 basically do the following:
cp <BOOT mount point>/dtb-kernel-4.16.0-0.rc4.git0.1.fc28/bcm2837-rpi-3-b.dtb
<BOOT mount point>/dtb-kernel-4.16.0-0.rc4.git0.1.fc28/bcm2837-rpi-3-b-plus.dtb
On aarch64:
cp <BOOT mount point>/dtb-kernel-4.16.0-0.rc4.git0.1.fc28/broadcom/bcm2837-rpi-3-b.dtb
<BOOT mount point>/dtb-kernel-4.16.0-0.rc4.git0.1.fc28/broadcom/bcm2837-rpi-3-b-plus.dtb
Unmount boot and continue as usual.
Once it's running if you update the kernel to rc6 you should be
running just fine. One other thing to note is there's some different
bits needed for the wifi. I'm going to put all of those, inc the one
needed for the original Pi3, into an rpm but I've not had a chance to
do that as yet. Give me a day or so and I'll likely get that done.
Peter
6 years, 2 months
Re: Raspberry Pi 4 support
by Peter Robinson
On Sun, Mar 7, 2021 at 4:24 PM Ondřej Budai <obudai(a)fedoraproject.org> wrote:
>
> Hello guys,
>
> is Raspberry Pi 4 officially supported by Fedora? Both docs[1] and wiki[2] don't mention Pi 4 as supported. The wiki even says that "We do not (as of 30th October 2019) support the Raspberry Pi 4 in any Fedora release."[3]
>
> On the other hand, I tried writing a Fedora image onto an SD card and booting an RPI 4 from it and it worked flawlessly. So maybe the docs and wiki are just outdated?
No, they're not out of date. By working flawlessly you don't outline
the hardware options you tested. There's still issues with USB on some
devices, WiFi on some devices, accelerated video and related things on
any device. The enablement of various components on the device is
improving but we're not at a point where actually it does actually
"work flawlessly" which for a lot of newbies is a problem and causes a
lot of support requests of the maintainer (AKA me) and hence why it's
still not "officially supported"
3 years, 2 months
Re: Urgent testing request: Raspberry Pi 3 owners
by RENARD Pierre-Francois
On 04/24/2018 09:24 PM, Peter Robinson wrote:
> On Tue, Apr 24, 2018 at 8:23 PM, Adam Williamson
> <adamwill(a)fedoraproject.org> wrote:
>> Hi folks!
>>
>> It'd be great if anyone with a Raspberry Pi 3 could test out a couple
>> of prospective builds to go into Fedora 28 Final:
>>
>> https://koji.fedoraproject.org/koji/buildinfo?buildID=1074979 (kernel)
>> https://koji.fedoraproject.org/koji/buildinfo?buildID=1072875 (bcm283x-firmware)
>>
>> like, soon - within the next couple of hours would be great. Both
>> builds are intended to improve things on the Pi 3, but they're very new
> Primarily on the 3+
>
>> and I'd like at least a few folks to boot with them and confirm that
>> things at the very least aren't any *worse* than before, before we can
>> pull them into the release.
>>
>> If you could post feedback for the bcm283x-firmware build to the
>> update:
>> https://bodhi.fedoraproject.org/updates/FEDORA-2018-142a31fda3
>>
>> and feedback for the kernel build to this bug:
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1570983
>>
>> that'd be awesome. Thanks a lot, folks!
>> --
>> Adam Williamson
>> Fedora QA Community Monkey
>> IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
>> http://www.happyassassin.net
>> _______________________________________________
>> arm mailing list -- arm(a)lists.fedoraproject.org
>> To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
> _______________________________________________
> arm mailing list -- arm(a)lists.fedoraproject.org
> To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
upgrade done on a PI3B, ongoing on 2 PI3B+
all on fresh installed aarch64 systems from 20180424 image
6 years, 1 month
