Re: Possible Hangups on Raspberry Pi with FC25 Server
by Daniel Laczi
Am 31. Januar 2017 00:19:01 MEZ schrieb Peter Robinson <pbrobinson(a)gmail.com>:
>On Mon, Jan 30, 2017 at 9:03 PM, Alexander Petrenz
><petrenz.a(a)gmail.com> wrote:
>> Hi all,
>>
>> since I wasn´t able to find out what´s causing those crashes I moved
>to
>> raspian and since then the Pi (it was a Gen 3, Model B) is running
>without
>> any hickups. So in the end I´m sure, the issue was software related.
>
>Yes little surprise there, unless it's PSU and we're not as power
>optimised as Raspbian yet.
>
>In terms of software, other than the fact they're both Linux distros,
>that link Raspbian and Fedora 25. Kernel, toolchain, their binary
>display drivers etc are all different. We're all upstream and open,
>it's not yet perfect but it's all open but we're not yet the most
>power efficient.
>
Fedora might not be perfect if your doing client stuff and need display drivers. However it is really great if you need a small server, because it is the only maintained distro for the Raspian shipping SELinux by default! Thanks for anything your doing Peter ;)
>> Alex
>>
>> On Fri, Jan 27, 2017 at 8:39 AM, Winfried de Heiden <wdh(a)dds.nl>
>wrote:
>>>
>>> Hi all,
>>>
>>> Since a couple of days I'm hit by hangups as well :( Hard to trace
>since
>>> the Raspberry Pi 3 does nit react to keyboard, network etc. anymore
>and the
>>> HDMI monitor goes black.... However, yesterday I was able to take a
>photo
>>> before the screen goes black: Kernel Panic ... Fatal exception in
>interrupt;
>>> screen shot attached!
>>>
>>> This raspberry Pi has been running for weeks without problems on
>Fedora 25
>>> using the same power.
>>>
>>> Hmmm, any sugestions on this?
>>>
>>> Winfried
>>>
>>>
>>> -----Oorspronkelijke bericht-----
>>>
>>> Datum: Thu, 26 Jan 2017 15:13:26 +0100
>>> Onderwerp: [fedora-arm] Re: Possible Hangups on Raspberry Pi with
>FC25
>>> Server
>>> Aan: arm(a)lists.fedoraproject.org
>>> Van: Alexander Petrenz <petrenz.a(a)gmail.com>
>>>
>>> _______________________________________________
>>> 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
>>
>_______________________________________________
>arm mailing list -- arm(a)lists.fedoraproject.org
>To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
--
Mit freundlichen Grüßen
Daniel Laczi
7 years, 4 months
Re: Raspberry Pi 3+
by Richard Ryniker
Thank you, Peter Robinson, your instructions worked beautifully.
Perhaps this will not work with the aarch64 version used by Tomáš Frolík,
but you already explained in an earlier post why there is little reason
to use that on a Raspberry Pi.
I used the following to install on a SD card:
fedora-arm-image-installer --image=fedora/F28/Fedora-Workstation-armhfp-28-20180324.n.0-sda.raw.xz --target=rpi3 --media=/dev/sde --norootpass --resizefs --selinux=off
and copied the dtb file to bcm2837-rpi-3-b-plus.dtb as described, and
then successfully booted my Raspberry Pi 3B+.
After completion of the first-boot dialog, things pretty much fell
apart. I saw the expected pointer on my screen, but the machine stuck
before it displayed the graphical login screen. There was no response to
my attempt to switch to another terminal with Ctrl-Alt-F4 or Alt-F4.
I mounted my SD card on my regular Fedora workstation, then manually
changed the default target to multi-user.target. This worked much
better, I could log in and discover the RPi wired Ethernet is not
operational.
Bypass this problem with a USB Ethernet dongle (which is automatically
configured without any problems), and I can run "dnf upgrade" which
mostly succeeds (there is a problem with libvirt-daemon, but that occurs
with the RPi 3B also.)
Reboot, and I now have an (except for libvirt-daemon) up-to-date F28 on my
Raspberry Pi 3B+.
No graphical login and no wired Ethernet are problems to be solved, but
at least there is a path to get a current F28 environment on the 3B+ for
those who want to work on this machine.
6 years, 2 months
Re: Change in kernel PPS GPIO handling?
by Stefan Wahren
Am 05.03.22 um 12:34 schrieb Stefan Wahren:
> Am 04.03.22 um 21:50 schrieb Stefan Wahren:
>> Am 03.03.22 um 02:29 schrieb Chris Adams:
>>> Once upon a time, Stefan Wahren <stefan.wahren(a)i2se.com> said:
>>>> Hi Chris,
>>>>
>>>> Am 02.03.22 um 10:51 schrieb Peter Robinson:
>>>>>> I have an RPi4 running Fedora 35. It hadn't been updated in a while, so
>>>>>> I applied updates today. When I boot to the kernel 5.16.11-200, I lose
>>>>>> the PPS device from my GPS hat. Boot back to 5.14.16-301.fc35 and it
>>>>>> works.
>>>>>>
>>>>>> I'm booting with EFI firmware, and with a device tree config.txt that
>>>>> All our firmware are EFI, that's the only way we support booting, is
>>>>> it the default U-Boot based one or are you using the edk2 one?
>>>>>
>>>>>> has "dtoverlay=pps-gpio,gpiopin=4" in it. I removed the /boot/dtb
>>>>>> symlink and set /etc/u-boot.conf to not re-add it.
>>>>>>
>>>>>> When I boot 5.16, I see /proc/device-tree, and it has
>>>>>> /proc/device-tree/pps@4 in it (and the contents look correct), but
>>>>>> loading the pps-gpio kernel module just gives:
>>>>>>
>>>>>> pps-gpio: probe of pps@4 failed with error -22
>>>>> Any chance you can tell us which kernel it started with, 5.14.x to
>>>>> 5.16.x is a big window to debug and looking at kernel logs for
>>>>> drivers/pps there's been no changes in that space in the 5.15+ kernels
>>>>> at all.
>>>>>
>>>>> I wonder if it's a change/regression in the firmware overlay <->
>>>>> kernel interface.
>>>> do you use the DTB file from 5.14.x or 5.16x?
>>>>
>>>> I guess this is related to this commit:
>>>>
>>>> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?...
>>>>
>>>> Unfortunately this is a change which requires this DTS fix:
>>>>
>>>> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?...
>>>>
>>>> So DTB and kernel must "match".
>>> Okay, so what's the best way to do that?
>>>
>>> I have EFI firmware from https://github.com/pftf/RPi4 in /boot/efi, and
>>> the /boot/dtb symlink removed. The bcm2711-rpi-4-b.dtb file in
>>> /boot/efi is from the RPi4_UEFI_Firmware_v1.32.zip file. I have a
>>> config.txt in /boot/efi that references overlays in /boot/efi/overlays
>>> from RPM bcm283x-overlays (like pps-gpio)..
>>>
>>> I'm not quite sure how I need to fit all this together.
>> Let me recap the situation. mainline and rpi vendor tree are independent
>> in development. Synchronization (incl. device tree) happens in both
>> directions.
>>
>> U-Boot bootloader decided to keep an own copy of the mainline DT files
>> (which is currently based on an older 5.15 version which lacks the
>> gpio-ranges property). According to this statement [1] the EDK2 UEFI
>> decided to use the rpi vendor tree and don't care about the mainline DT
>> files.
>>
>> I'm sorry but as a spare-time kernel developer, i don't have to time to
>> fight against all this mess.
>>
>> I hope i will have some time for debugging in the near future ...
>>
>> [1] - https://github.com/pftf/RPi4/issues/193
>>
> Today i tried Fedora 35 Minimal for my first time, here are my test results:
>
> Raspberry Pi 400 32 bit => bus width issue
> Raspberry Pi 400 64 bit => hangs while show graphics
> Raspberry Pi 4 B 4 GB 32 bit => kernel crash
> Raspberry Pi 4 B 4 GB 64 bit => boot into setup
> Raspberry Pi 4 B 8 GB 32 bit => black screen, fails to start kernel?
> Raspberry Pi 4 B 8 GB 64 bit => boot into setup
>
> 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].
Best regards
[1] -
https://www.jeffgeerling.com/blog/2021/raspberry-pi-4-model-bs-arriving-n...
[2] -
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commi...
[3] - https://forums.raspberrypi.com/viewtopic.php?t=319125
[4] - https://bugzilla.redhat.com/show_bug.cgi?id=2011423
2 years, 2 months
Re: Raspberry Pi and its 7" display
by Ted Davis
Hi Kevin,
Do you or anyone know if gpm works on these rpi touchscreens in console-tty?
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?
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
>
5 years, 5 months
Re: Raspberry Pi 3
by Stephen John Smoogen
On 29 February 2016 at 05:28, Peter Robinson <pbrobinson(a)gmail.com> wrote:
> On Mon, Feb 29, 2016 at 12:22 PM, Jeffrey Ollie <jeff(a)ocjtech.us> wrote:
>> Built-in WiFi, Bluetooth, 64 bit processor. Is this finally the Raspberry Pi
>> that Fedora will run unmodified on? Sure hope so...
>
> No, not currently, and certainly won't be in Fedora 24 unless someone
> contributes a lot of stuff very quickly.
>
> Why? There's no source (yet) for the new SoC, it's not upstream and
> won't be until at least 4.7 (it has to be queued for inclusion by rc4
> of the previous release to land in the next release) it supports a
> boot process that is nothing like what we currently support for
> aarch64 so it would need significant work for aarch64 in Fedora, and
> the wifi firmware (looks similar issues that people have with Apple
> Mac wifi) isn't currently in linux-firmware so it's not (as far as I'm
> aware) currently able to be distributed as part of Fedora.
At some point, I have to wonder if Raspberry Pi is just trolling us
with each hardware release.
> _______________________________________________
> arm mailing list
> arm(a)lists.fedoraproject.org
> http://lists.fedoraproject.org/admin/lists/arm@lists.fedoraproject.org
--
Stephen J Smoogen.
8 years, 3 months
Re: Raspberry Pi 3
by Jeffrey Ollie
On Mon, Feb 29, 2016 at 12:24 PM, Zoltan Hoppar <hopparz(a)gmail.com> wrote:
>
> I just want to mention that Olimex do completely FOSS solutions, and
> trying to keep it so. Even more I don't get it why we fighting with
> RSPi, and try to find like this:
>
Not that there's anything wrong with Olimex's products, but they certainly
do not have the marketing and community that the Raspberry Pi has. If
you're relatively inexperienced with electronics or Linux, it's worth a lot
to have a community like the Raspberry Pi has for solutions and help. If
you live in even a moderately sized metropolitan area there's probably a
Linux user group or hackerspace nearby that you can turn to for in-person
help, encouragement, and maybe even training.
--
Jeff Ollie
8 years, 3 months
Re: Raspberry Pi 3
by Fernando Cassia
On 2/29/16, Stephen John Smoogen <smooge(a)gmail.com> wrote:
> On 29 February 2016 at 05:28, Peter Robinson <pbrobinson(a)gmail.com> wrote:
>> On Mon, Feb 29, 2016 at 12:22 PM, Jeffrey Ollie <jeff(a)ocjtech.us> wrote:
>>> Built-in WiFi, Bluetooth, 64 bit processor. Is this finally the Raspberry
>>> Pi
>>> that Fedora will run unmodified on? Sure hope so...
> At some point, I have to wonder if Raspberry Pi is just trolling us
> with each hardware release.
I just dont understand why they insist on having everything onboard
(specially wireless) when usb dongles for wifi and BT can be had for a
couple of dollars. Plus, having those EXTERNALLY means you can update
to newer specs without switching mainboard.
Much more interesting, IMHO would be the addition of a SATA port AND USB 3.0.
Then one can hook as many external devices as needed. Want to turn the
Raspi4 into a gigabit router? just hang a pair of USB 3.0->GigE
adapters and youre done.
FC
8 years, 3 months
Re: Raspberry Pi 3+
by Peter Robinson
On Mon, Mar 26, 2018 at 2:56 AM, Richard Ryniker <ryniker(a)alum.mit.edu> wrote:
> Thank you, Peter Robinson, your instructions worked beautifully.
>
> Perhaps this will not work with the aarch64 version used by Tomáš Frolík,
> but you already explained in an earlier post why there is little reason
> to use that on a Raspberry Pi.
It should work in exactly the same way, the only difference on aarch64
is that the DT is in a broadcom sub directory.
> I used the following to install on a SD card:
>
> fedora-arm-image-installer --image=fedora/F28/Fedora-Workstation-armhfp-28-20180324.n.0-sda.raw.xz --target=rpi3 --media=/dev/sde --norootpass --resizefs --selinux=off
>
> and copied the dtb file to bcm2837-rpi-3-b-plus.dtb as described, and
> then successfully booted my Raspberry Pi 3B+.
>
> After completion of the first-boot dialog, things pretty much fell
> apart. I saw the expected pointer on my screen, but the machine stuck
> before it displayed the graphical login screen. There was no response to
> my attempt to switch to another terminal with Ctrl-Alt-F4 or Alt-F4.
>
> I mounted my SD card on my regular Fedora workstation, then manually
> changed the default target to multi-user.target. This worked much
> better, I could log in and discover the RPi wired Ethernet is not
> operational.
>
> Bypass this problem with a USB Ethernet dongle (which is automatically
> configured without any problems), and I can run "dnf upgrade" which
> mostly succeeds (there is a problem with libvirt-daemon, but that occurs
> with the RPi 3B also.)
>
> Reboot, and I now have an (except for libvirt-daemon) up-to-date F28 on my
> Raspberry Pi 3B+.
>
> No graphical login and no wired Ethernet are problems to be solved, but
> at least there is a path to get a current F28 environment on the 3B+ for
> those who want to work on this machine.
> _______________________________________________
> arm mailing list -- arm(a)lists.fedoraproject.org
> To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
6 years, 2 months
Re: [fedora-arm] beginning of Fedora support for the Raspberry Pi 2
by Robert Moskowitz
On 02/05/2015 05:48 PM, Troy Dawson wrote:
> pcduino3 nano has SATA and Gbit ethernet and is only $4 more expensive
> than the Raspberry Pi. I like it. I'm not sure why it's not more
> popular. Maybe cuz it's hard to say.
Very nice. Does F21 minimal run on it? Does Rawhide support its video?
I do not see a barrel power plug, so power only through the OTG?
Also this price seems to be for the board alone? So you have to add in
a power cable and the special SATA cable (my Cubies come with both of
these).
>
> Troy
>
> On 02/04/2015 02:17 PM, Frans Meulenbroeks wrote:
>> No SATA, no USB3.0 and only 100 Mbit ethernet.
>> So for storage you are limited to a USB hard disk or a (fast) SDHC card.
>> Then again at this pricepoint it will be quite popular.
>>
>> Banana pi, orange pi etc, are all somewhat more expensive but have SATA
>> and Gbit ethernet.
>>
>> 2015-02-04 20:28 GMT+01:00 Andrew Gillis <andrew(a)vortexbox.org
>> <mailto:andrew@vortexbox.org>>:
>>
>> 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 <mailto:rgm@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 <mailto:arm@lists.fedoraproject.org>
>> https://admin.fedoraproject.__org/mailman/listinfo/arm
>> <https://admin.fedoraproject.org/mailman/listinfo/arm>
>>
>>
>>
>>
>> --
>> Andrew Gillis
>> Lead Developer VortexBox
>> vortexbox.org <http://vortexbox.org>
>>
>> _______________________________________________
>> arm mailing list
>> arm(a)lists.fedoraproject.org <mailto:arm@lists.fedoraproject.org>
>> https://admin.fedoraproject.org/mailman/listinfo/arm
>>
>>
>>
>>
>> _______________________________________________
>> arm mailing list
>> arm(a)lists.fedoraproject.org
>> https://admin.fedoraproject.org/mailman/listinfo/arm
>>
> _______________________________________________
> arm mailing list
> arm(a)lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/arm
9 years, 3 months
