Re: [fedora-arm] beginning of Fedora support for the Raspberry Pi 2
by Adam Goode
The firmware should be acceptable for immediate packaging in Fedora:
https://fedoraproject.org/wiki/Packaging:LicensingGuidelines?rd=Packaging...
(I believe that page was amended explicitly to allow for the raspberry pi
bootloader. It even mentions raspberry pi by name in the example.)
The firmware is still required to boot, because it still provides runtime
services to userspace. Eventually it may go away, but probably not in 2015.
I think you would chain to u-boot if you wanted u-boot in the mix.
Firmware upstream: https://github.com/raspberrypi/firmware
This video contains some info about the overall open source roadmap:
https://www.youtube.com/watch?v=EXDeketJNdk
Ultimately it is on people's radar but far off. (But could be accelerated
by motivated individuals.)
Adam
On Wed, Feb 4, 2015 at 10:43 AM, Peter Robinson <pbrobinson(a)gmail.com>
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
>
> The first phase I believe should be a remix, with the modified
> packages required to support the install for that remix being is a
> published repository, while we're awaiting all the bits to land
> upstream.
>
> The short term repository should only contain the following:
> * kernel
> * bootloader
> * firmware
> * mainline userspace packages that need non upstream pacakges
>
> Everything else (eg xorg drivers) should be packaged up and go through
> the standard package review process and be in mainline Fedora.
>
> From there we can spin a remix image for testing.
>
> BUT before we get to that we need to review all the
> projects/sources/packages that are needed and document what packages
> are needed and where the upstream is located. In the case of firmware
> we also need to ensure it's re-distributable. Does the GPU firmware
> still boot or is it now possible to use the upstream u-boot support to
> boot the device and then load the firmware via the kernel like other
> standard drivers that need firmware, or do we even need binary
> firmware any more?
>
> I believe Seneca has volunteered to spear head this so it would be
> great if they can start by documenting the above and post the details
> of it in response to this mail so we can work out what needs to be
> done and where in preparation for the remix, this will then give us a
> good picture as well when we might be able to just support it by the
> standard mainline process.
>
> Regards,
> Peter
> _______________________________________________
> arm mailing list
> arm(a)lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/arm
9 years, 4 months
Raspberry PI 3 locking up
by Rafael Leiva-Ochoa
Hi Everyone,
I've been running a raspberry pi 3 with Fedora release 25 (Twenty
Five) using kernal 4.9.6-200.fc25.armv7hl, and I have been noticing for the
last 2 weeks that my Pi locks up. I tried hooking it up to an HDMI monitor,
and USB keyboard to see if the system generates any message, but I only get
a blank screen and no reaction from the keyboard. I have looked at the
/var/log/message, and dmesg, and I don't see anything that could be causing
the problem. I was thinking it could be overheating, but Fedara 25 does not
support any of the rasbian commands to run heat sensor checks.
Any ideas?
Thanks,
Rafael
7 years, 4 months
Re: Fedora Minimal 36 installation on raspberry pi 2B
by Gregory Carter
DNF no longer has sufficient resources on my PI 3, after a recent update,
to work anymore.
The slooooooow creap of fixes, patches and related support elements to make
ARM a well supported option on Fedora is taking its toll.
I know microdnf has been discussed a few times, but here is another
alternative which worked for me.
Another way of dealing with dnf memory issues is to add swap space using a
swap file on my Raspberry PI 3+
This corrects a memory deficit of about 200MB on my PI 3's working set of
physical RAM pages, which kicks me out of the remote shell.
Here is the steps I used to start using dnf again:
I decided I would put the swap file off the /mnt so I made a directory for
it:
mkdir /mnt/swapfiles
Then I made the swapfile I picked 5G, if you don't have that sort of space
you might need to experiment with an appropriate size, maybe 2G?
fallocate -l 5G /mnt/swapfiles/swpf1
An Alternative is to use dd to make the swp if you happen to be
running a slimmed down installation and do not have fallocate
installed.
dd if=/dev/zero of=/mnt/swapfiles/swpf1 bs=1024 count=5048576
Set the access rights on the swapfile like so:
chmod 600 /mnt/swapfiles/swpf1
Tell Linux about the swapfile:
mkswap /mnt/swapfiles/swpf1
Activate the swapfile:
swapon /mnt/swapfiles/swpf1
I only use the swap file when I am loading or patching with DNF, so I
did not put the swapfile configuration into my fstab file.
So I just execute a swapon before I do a "dnf update".
My reason for doing so is to eliminate any unwanted writes to the
sdcard that are not absolutely required.
Which helps extend the life of the sdcard.
If you want to add the swapfile so that it is always on, you have to
add a line to the /etc/fstab file like so:
/mnt/swapfiles/swpf1 swap swap defaults 0 0
i hope you found this helpful. I know I did. :-)
On Fri, Jan 20, 2023 at 3:39 PM Irene Diez <idiez(a)redhat.com> wrote:
> Hello there,
>
> I'm trying to install Fedora-Minimal-36-1.5.armhfp.raw on my raspberry pi
> 2B. Installation was a success but the device runs out of memory when
> trying to install anything via dnf and I get kicked out of the shell.
>
> I've followed the installation instructions in
> https://fedoraproject.org/wiki/Architectures/ARM/Raspberry_Pi#Manual,
> which specify that this model is supported since Fedora 29; so, is it there
> anything that I'm missing for Fedora to work?
>
> Thanks,
>
> Irene
> _______________________________________________
> arm mailing list -- arm(a)lists.fedoraproject.org
> To unsubscribe send an email to arm-leave(a)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
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>
1 year, 3 months
Re: Urgent testing request: Raspberry Pi 3 owners
by RENARD Pierre-Francois
On 04/25/2018 02:31 PM, RENARD Pierre-Francois wrote:
> 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
>
>
So far so good :)
fresh install + dnf upgrade + dnf install of few packages
do you have anything to test ?
Fox
6 years, 1 month
Re: Raspberry Pi and its 7" display
by Peter Robinson
On Sun, Dec 9, 2018 at 1:52 AM Ted Davis <12e3pi(a)gmail.com> wrote:
>
> Hi Kevin,
>
> Do you or anyone know if gpm works on these rpi touchscreens in console-tty?
Not currently.
> And/Or question 2:
>
> F29 aarch are .xz, need I have fedora installed say x86-64, to have dnf (?) to write the aarch image for rpi 3 B+?
>
> Or, is there a writable .iso available instead of the f29.aarch.xz?
Please read the docs and start a new thread if they don't answer your questions.
> Ty
>
> Ted
>
> On Saturday, December 8, 2018, Kevin Cummings <cummings(a)kjchome.homeip.net> wrote:
>>
>> Hi Folks,
>> Longtime Fedora user here. Last winter, I got a Raspberry Pi, and
>> installed F28 on it. Using the HDMI output, it works well. Recently, I
>> picked up the Raspberry Pi 7" display (and case). After hooking up the
>> display to the Pi via the ribbon cable, I booted it up.
>>
>> The 7" display works well as the initial console, and I see all the
>> usual messages go flying by. At some point (when it decides to switch
>> to graphics mode) the display goes blank. Nothing on it. I cannot
>> switch even to a virtual console. The new case blocks using the HDMI
>> port, so I had to remove the Pi from the case (while leaving the ribbon
>> cable attached to the display). After plugging a monitor into the HDMI
>> port, what I discovered was that the Pi boots using the display as
>> console, then switches to the HDMI port for the X11 driver. (not useful)
>>
>> How can I get the X11 display to come up on the 7" display in graphics
>> mode. What do I need? A new xorg-x11-drv driver? A newer kernel?
>>
>> 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.
>>
>> --
>> Kevin J. Cummings
>> cummings(a)kjchome.homeip.net
>> cummings(a)kjc386.framingham.ma.us
>> kjchome(a)icloud.com
>> Registered Linux User #1232 (http://www.linuxcounter.net/)
>> _______________________________________________
>> arm mailing list -- arm(a)lists.fedoraproject.org
>> To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
>> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
>> 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(a)lists.fedoraproject.org
> To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org
5 years, 5 months
Re: Students and engineers interested in contributing to Fedora Linux on Raspberry Pi
by Jeremy Linton
Hi,
Welcome!
On 1/13/21 3:42 PM, Joel Savitz wrote:
> Good afternoon,
>
> A group of computer science undergraduates and I are interested in
> contributing to the usability of Fedora Linux on the Raspberry Pi 4.
>
> I was a part of this group as an undergrad and we developed a compatibility
> layer for translating RPi.GPIO syntax into calls to libgpiod. It is
> currently available on PyPi and under review for inclusion in Fedora:
> https://github.com/underground-software/RPi.GPIO2
> https://pypi.org/project/RPi.GPIO2/
>
> The maintainer of the (broken) RPi.GPIO fedora package agreed to obsolete
> it in favor of our new package, which is a drop in replacement for RPi.GPIO
> (hence the 2), however I have not heard from him since September.
>
> Anyway, we are looking for a new project or area of Fedora on the Raspberry
> Pi to improve over the upcoming semester. Does anyone have any suggestions?
From my perspective, the main issues with the rpi4 and fedora surround
low level firmware/driver problems. That is what keeps it from "just
working" as expected with a standard fedora image.
As such you might want to take a look at:
https://github.com/lategoodbye/rpi-zero/issues/43
which is the running conversation about upstream kernel features that
need work.
On the firmware side you might look at
https://github.com/pftf/RPI4/issues which is a mix of bugs and future
features required to make the platform behave as expected.
There is probably a uboot related list too, but I don't know where it
is. Peter can probably comment.
Finally besides Trusted Firmware, there is a project that seeks to
replace the videocore firmware as well
https://github.com/librerpi/rpi-open-firmware. If that happens it would
remove another longstanding binary blob used to boot the platform.
There are of course others, but that should provide a few starting places.
Welcome again!
3 years, 4 months
Re: Raspberry Pi 2 - are post-install steps required?
by Richard Ryniker
I believe GPIO is broken because the Raspbery Pi hardware platform is not
correctly recognized, but I have not had available time to look
carefully.
[root@RPi3-1 ryniker]# uname -a
Linux RPi3-1 4.8.4-301.fc25.armv7hl #1 SMP Tue Oct 25 02:01:39 UTC 2016 armv7l armv7l armv7l GNU/Linux
Simple test to demonstrate failure:
[root@RPi3-1 ryniker]# echo 23 >/sys/class/gpio/export
bash: echo: write error: Invalid argument
[root@RPi3-1 ryniker]#
Suspicious symptom: look at /proc/cpuinfo and see:
Hardware : Generic DT based system
Revision : 0000
Serial : 00000000b9dd7fd3
Using Raspbian, where GPIO works, /proc/cpuinfo reports:
Hardware : BCM2709
Revision : a22082
Serial : 00000000e0b59fb5
I suspect the required files may be present in Fedora, possibly one of these:
/boot/dtb-4.8.4-301.fc25.armv7hl/bcm2836-rpi-2-b.dtb
/boot/dtb-4.8.4-301.fc25.armv7hl/bcm2837-rpi-3-b.dtb
but they may not be used because of some failure to correctly identify
the hardware platform. On the other hand:
[ryniker@RPi3-1 ~]$ echo $(cat /sys/firmware/devicetree/base/model)
Raspberry Pi 3 Model B
[ryniker@RPi3-1 ~]$
seems to get it right, therefore it is not complete failure to recognize
the platform, maybe just a partial failure because names have evolved so
some match fails. And it remains possible some configuration data is
simply absent, or incorrect.
7 years, 4 months
Raspberry Pi 3+
by Richard Ryniker
F27 will not boot on the new Model 3+. Green LED blinks 4 times
(medium), then 4 times (fast), then repeats. The colored splash screen
is displayed.
Might this be just a device tree problem? Raspbian journal contains a line:
raspberrypi kernel: OF: fdt:Machine model: Raspberry Pi 3 Model B Plus Rev 1.3
Do we just need a bcm2710-rpi-3-b-plus.dtb file in Fedora's /boot
filesystem? Has anyone succeeded to boot Fedora on the 3+ Pi?
6 years, 2 months
Re: Raspberry Pi 3+
by Peter Robinson
On Tue, Mar 20, 2018 at 1:47 AM, Richard Ryniker <ryniker(a)alum.mit.edu> wrote:
> F27 will not boot on the new Model 3+. Green LED blinks 4 times
> (medium), then 4 times (fast), then repeats. The colored splash screen
> is displayed.
That's expected.
> Might this be just a device tree problem? Raspbian journal contains a line:
No, it's a firmware, u-boot and device tree problem.
> raspberrypi kernel: OF: fdt:Machine model: Raspberry Pi 3 Model B Plus Rev 1.3
>
> Do we just need a bcm2710-rpi-3-b-plus.dtb file in Fedora's /boot
> filesystem? Has anyone succeeded to boot Fedora on the 3+ Pi?
Yes, I have support there and it works fine, we'll almost be there for
F-28 beta with likely just a small process to get it to boot
initially. I'm undecided whether I want to do the related work to get
this support into F-27.
Peter
6 years, 2 months
