Re: F28 GNOME graphical login screen not displayed on Raspberry Pi 3.
by Peter Robinson
On Tue, Mar 27, 2018 at 5:41 PM, Richard Ryniker <ryniker(a)alum.mit.edu> wrote:
> After booting an image such as
>
> Fedora-Workstation-armhfp-28-20180324.n.0-sda.raw.xz
>
> on a Raspberry Pi model 3, the First Boot process completes, but no
> graphical login screen appears. The system becomes unresponsive after a
> graphical pointer arrow is displayed (on top of whatever text was left on
> the screen from the boot process.)
>
> This failure remains even when the installed image is updated to include
> the latest software from updates-testing as of March 25.
>
> This is specific to the GNOME image. Graphical login works for other
> images, specifically KDE and LXDE.
>
> Question 1: Can anyone report success with F28 Raspberry Pi 3 GNOME
> graphical login? (Perhaps different display hardware makes a
> difference.)
>
> Question 2: Does this problem aflict other armhfp systems, or is this
> unique to Raspberry Pi hardware?
>
> This problem is new in F28. In my experience, up-to-date F27 GNOME
> systems using Raspberry Pi 3 hardware have no trouble with graphical
> login.
It's a known problem in Fedora 28 Workstation in general, it's not
limited to ARM let alone the Raspberry Pi. There's a thread on the
desktop@ list where it's being discussed. There seems to have been a
number of things that have regressed in terms of both memory and cpu
usage.
Completely unrelated to the regressions in F-28 there's already a
planned hackfest in May to improve performance of gnome on constrained
devices so I would expect this to improve greatly in the F-29 cycle
with luck.
Peter
6 years, 2 months
F28 GNOME graphical login screen not displayed on Raspberry Pi 3.
by Richard Ryniker
After booting an image such as
Fedora-Workstation-armhfp-28-20180324.n.0-sda.raw.xz
on a Raspberry Pi model 3, the First Boot process completes, but no
graphical login screen appears. The system becomes unresponsive after a
graphical pointer arrow is displayed (on top of whatever text was left on
the screen from the boot process.)
This failure remains even when the installed image is updated to include
the latest software from updates-testing as of March 25.
This is specific to the GNOME image. Graphical login works for other
images, specifically KDE and LXDE.
Question 1: Can anyone report success with F28 Raspberry Pi 3 GNOME
graphical login? (Perhaps different display hardware makes a
difference.)
Question 2: Does this problem aflict other armhfp systems, or is this
unique to Raspberry Pi hardware?
This problem is new in F28. In my experience, up-to-date F27 GNOME
systems using Raspberry Pi 3 hardware have no trouble with graphical
login.
6 years, 2 months
Re: F28 GNOME graphical login screen not displayed on Raspberry Pi 3.
by Paul Whalen
Hi Richard,
----- Original Message -----
> After booting an image such as
>
> Fedora-Workstation-armhfp-28-20180324.n.0-sda.raw.xz
>
> on a Raspberry Pi model 3, the First Boot process completes, but no
> graphical login screen appears. The system becomes unresponsive after a
> graphical pointer arrow is displayed (on top of whatever text was left on
> the screen from the boot process.)
>
> This failure remains even when the installed image is updated to include
> the latest software from updates-testing as of March 25.
>
> This is specific to the GNOME image. Graphical login works for other
> images, specifically KDE and LXDE.
>
> Question 1: Can anyone report success with F28 Raspberry Pi 3 GNOME
> graphical login? (Perhaps different display hardware makes a
> difference.)
Could you try the F28 Beta RC1.1 image:
https://kojipkgs.fedoraproject.org/compose/28/Fedora-28-20180326.0/compos...
If that doesnt work, please open a bug and let us know so others can add more details.
>
> Question 2: Does this problem aflict other armhfp systems, or is this
> unique to Raspberry Pi hardware?
It works in qemu but I have yet to test on hardware.
Thanks,
Paul
>
> This problem is new in F28. In my experience, up-to-date F27 GNOME
> systems using Raspberry Pi 3 hardware have no trouble with graphical
> login.
> _______________________________________________
> 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: Raspberry PI 3 locking up
by Winfried de Heiden
Hi all,
I don't know by head but it should be enough; it worked for weeks and
it is sold as "the official PI power supply".
I'll check tonight to be shure.
Winfried
-----Oorspronkelijke bericht-----
Datum: Wed, 1 Feb 2017 11:27:45 +0000
Onderwerp: [fedora-arm] Re: Raspberry PI 3 locking up
Cc: arm(a)lists.fedoraproject.org, Rafael Leiva-Ochoa <spawn(a)rloteck.net>
Aan: Winfried de Heiden <wdh(a)dds.nl>
Van: Peter Robinson <pbrobinson(a)gmail.com>
On Wed, Feb 1, 2017 at 7:52 AM, Winfried de Heiden <wdh(a)dds.nl> wrote:
> Hi all,
>
> Same for me, since a couple of days the Rapsbery Pi 3 suddenly stops.
> One or
> two time I was quick enough to catch a kernel panic on the screen.
>
> Looks like a kernel thing to me. I moved the SD-card to my "
> old" Raspberry
> Pi 2 (two), the same installation is running fine for a couple of
> days.
What is the AMP rating of your power supplies?
> Screen shot of the kernel panic attached. I think I' ll create a
> bugzilla on
> this.
>
> Winfried
>
>
>
> Op wo, 1 feb 2017 om 1:26 , schreef Rafael Leiva-Ochoa <spawn@rloteck
> .net>:
>
> 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
>
>
> _______________________________________________
> 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
7 years, 4 months
Raspberry Pi 4 issues with Fedora Rawhide
by Lukas Brabec
Hi all,
I am writing this email to raise awareness well ahead of the F41 branching
on August 6 about the bugs I found while running Fedora Rawhide on the RPi
4.
I have proposed these bugs as blockers for the F41 release:
* gnome-initial-setup: Choosing avatar results in SetIconFile call failed
for
unknown reason [0]
I proposed this as F41 Final blocker, but this is fairly minor bug and I can
imagine that we would waive it if not fixed and create a common issue.
* gsk: vulkan renderer breaks gtk4 apps on Raspberry Pi 4 and 400 [1]
GSK now defaults to vulkan and it causes problems on RPi, I initially
encountered crashing gnome-initial-setup (and later that all GTK4 apps are
crashing upon startup). Thus I proposed it as a F41 Beta blocker. This
crashing on app startup will be resolved in the next GTK release, the fix is
already merged.
However, there are still issues with GTK4 apps [2], all related to vulkan
renderer [3] [4] [5]. It is not yet clear if the problems are bugs in GTK or
mesa. In the end, if proven difficult to fix, we could always switch back to
older renderer as suggested by Adam during F40 cycle [6].
* Raspberry Pi 4 won't wake up from suspend [7]
Although we don't have a criterion for suspend, I proposed this as a blocker
bug. I cannot login every time I keep Raspberry Pi idling for 15 minutes and
I have to restart it, this could also lead to loss of data. This is
something
different compared to the x86_64 situation. On x86_64 we probably wouldn't
block on suspend on some particular hardware configuration, but I think we
should block here since we support only a handful of ARM boards.
Also, suspend on Raspberry Pi OS is disabled, so I'm not sure if suspend on
Raspberry Pi is something we even want in Fedora.
[0] https://bugzilla.redhat.com/show_bug.cgi?id=2278845
[1] https://bugzilla.redhat.com/show_bug.cgi?id=2282171
[2] https://gitlab.gnome.org/GNOME/gtk/-/issues/6726#note_2121079
[3] https://gitlab.gnome.org/GNOME/gtk/-/issues/6743
[4] https://gitlab.gnome.org/GNOME/gtk/-/issues/6744
[5] https://gitlab.gnome.org/GNOME/gtk/-/issues/6745
[6] https://gitlab.gnome.org/GNOME/gtk/-/issues/6498#note_2063629
[7] https://bugzilla.redhat.com/show_bug.cgi?id=2283978
---
L.
1 day, 16 hours
Re: Raspberry Pi 3B+ fails to boot aarch64 image
by Peter Robinson
On Tue, Mar 12, 2019 at 9:00 PM Jan Kratochvil
<jan.kratochvil(a)redhat.com> wrote:
>
> On Tue, 12 Mar 2019 20:58:43 +0100, Stuart D. Gathman wrote:
> > I have rPi3B, and it required a few config tweaks. The
> > arm-image-installer package for Fedora has a script with the tweaks.
>
> Could you be more specific, please?
>
> I have tried both 'xz -dc' and both fedora-arm-image-installer with no change
> of the result:
> # fedora-arm-image-installer --image=arch/iso-copy/Fedora-Workstation-29-1.2.aarch64.raw.xz --media=/dev/XXXsda --norootpass --resizefs --target=rpi3
>
> I have found as a "tweak" only --blacklistvc4 from:
> Blank screen after boot on Raspberry Pi
> https://bugzilla.redhat.com/show_bug.cgi?id=1387733
> Where they talk about black screen but I do not get black screen.
> When I added --blacklistvc4 I got during installation:
> = Blacklisting the VC4 Driver for the Raspberry Pi 2/3
> sed: can't read /tmp/boot/extlinux/extlinux.conf: No such file or directory
> But it did not change anything, it still fails during boot with:
On aarch64 we boot with grub2, not extlinux so that explains the issue
there, I don't believe the vc4 driver is the issue you're actually
experiencing here.
> https://www.jankratochvil.net/t/rpi3fail.jpg
> [FAILED] Failed to start Avahi mDNS/DNS-SD Stack.
> ...
> [FAILED] Failed to start Modem Manager
> etc.
> It stays at the text failed systemd startup messages.
>
> Also
> /usr/share/arm-image-installer/boards.d/rpi3
> contains just:
> echo "= Raspberry Pi 3 Uboot is already in place, no changes needed."
> SYSCON="ttyS1,115200"
> So I do not see "a script with the tweaks".
The Raspberry Pi, because of the way it boots, is setup by default,
the vast majority of the boards need U-Boot dd:ed to somewhere special
in the first 2Mb of the disk.
5 years, 2 months
Re: FIXED: Raspberry Pi 3 stability issues
by Antonio M
I updated my Raspberry-Fedora after a long time, before upgrading
operations were very slow, after a long battle to uprade, now it works fine.
I have never experienced a full block of my system but I have never run my
Raspberry for more that five hours. Tonight I noticed that after login and
after a while HDMI was shut downd and my tv-set became blank, I had to
rechoose on my TV-set. Not clear about this issue, and I think not
connected to updated kernel
Tnx for help (and work)
Antonio Montagnani
Linux Fedora 25(Workstation)
inviato da Gmail
2017-02-10 16:10 GMT+01:00 Winfried de Heiden <wdh(a)dds.nl>:
> Hi all,
>
> running for 10 hours now with the 4.9.8-201.fc25.armv7hl, no crash so far.
> Looks good!
>
> Winfried
>
> -----Oorspronkelijke bericht-----
>
> *Datum*: Thu, 9 Feb 2017 12:37:32 +0000
> *Onderwerp*: [fedora-arm] FIXED: Raspberry Pi 3 stability issues
> *Aan*: arm(a)lists.fedoraproject.org
> *Van*: Peter Robinson <pbrobinson(a)gmail.com
> <Peter%20Robinson%20%3cpbrobinson(a)gmail.com%3e>>
>
> Hi,
>
> I'm not going to reply to all the threads so I'll just cover off here.
>
> It looks like (with a few days of testing) that I've managed to fix
> the stability issues seen on 4.9 on the Raspberry Pi 3. There is now a
> kernel-4.9.8-201.fc25 in updates-testing (maybe still on it's way to
> mirrors) that has been stable for me on a RPI3 running Workstation for
> a few days without issue.
>
> To test this you need to run:
> "dnf upgrade --enablerepo=updates-testing --refresh kernel*"
>
> If it works please provide karma on the update [1] if your still see
> the lock up issue please provide details on the bug [2]. If you have
> other issues with the Raspberry Pi please file a new bug or post a new
> message to the mailing list.
>
> Peter
>
> [1] https://bodhi.fedoraproject.org/updates/FEDORA-2017-76e3fe6cfa
> [2] https://bugzilla.redhat.com/show_bug.cgi?id=1418183
> _______________________________________________
> 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
>
>
7 years, 3 months
Serial communication with Raspberry PI
by William Jacobs
I am looking for help getting serial communication to work via the UART on either a Raspberry PI 3 B or a 3 B + that is running Fedora 29. The kernel recognizes the UART as /dev/ttyS1 on these systems. Data flows, but it is corrupted at random intervals. This happens at any baud rate. With these same two computers, everything works fine if I run Debian, which I really don't like. So it is not a hardware issue. I am thinking it is more of a device tree problem.
I also have UART to USB adapters that the kernel recognizes ad /dev/ttyUSB0. When using these under Fedora there is no corrupted data.
I would mention that I also have Fedora running nicely on a Quad Core i.MX6 based Hummingboard2. On that UART, there is no corrupted data issue.
For my project, I really would like to use Fedora and have good communication via the Raspberry PI UART. Is anyone here successfully using the UART on the Raspberry PI 3 B or 3 B +?
One final thing to mention, I do not have the console enabled on /dev/ttyS1. If I do enable it, I get the corrupted data when trying to log in or look at console output via a serial connection.
Any help would be greatly appreciated even if it just to tell me what to go read.
Thanks,
Will
5 years, 4 months
Re: Serial communication with Raspberry PI
by Stefan Wahren
Hi William,
Am 17.01.19 um 03:02 schrieb William Jacobs:
> I am looking for help getting serial communication to work via the UART on either a Raspberry PI 3 B or a 3 B + that is running Fedora 29. The kernel recognizes the UART as /dev/ttyS1 on these systems. Data flows, but it is corrupted at random intervals. This happens at any baud rate. With these same two computers, everything works fine if I run Debian, which I really don't like. So it is not a hardware issue. I am thinking it is more of a device tree problem.
i assume the root cause is the experimental cpu frequency driver. So
either you blacklist this driver or use /dev/ttyAMA0 which doesn't
depend on VPU clock.
Best regards
Stefan
>
> I also have UART to USB adapters that the kernel recognizes ad /dev/ttyUSB0. When using these under Fedora there is no corrupted data.
>
> I would mention that I also have Fedora running nicely on a Quad Core i.MX6 based Hummingboard2. On that UART, there is no corrupted data issue.
>
> For my project, I really would like to use Fedora and have good communication via the Raspberry PI UART. Is anyone here successfully using the UART on the Raspberry PI 3 B or 3 B +?
>
> One final thing to mention, I do not have the console enabled on /dev/ttyS1. If I do enable it, I get the corrupted data when trying to log in or look at console output via a serial connection.
>
> Any help would be greatly appreciated even if it just to tell me what to go read.
>
> Thanks,
> Will
5 years, 4 months
