Some initial steps solving the Raspberry Pi (3 and 4) issue where OpenSuSE LEAP does reach Graphical Target but Tumbleweed does not
Posted by jpluimers on 2024/12/13
This is from years ago, but I forgot to schedule it, so here it is:
Problem on an E20 (enlightenment using lightdm) image:
- LEAP 15.2 did reach Graphical Target
- Image [Wayback]
openSUSE-Leap-15.2-ARM-E20-raspberrypi3.aarch64-2020.07.08-Build1.34.raw.xz[Wayback] .packages [Wayback] .raw.xz.sha256 [Wayback] [Wayback] .raw.xz.sha256.asc
- Image [Wayback]
- Tumbleweed did not.
- Image [Wayback]
openSUSE-Tumbleweed-ARM-E20-raspberrypi3.aarch64-2020.08.15-Snapshot20200904.raw.xz[Wayback] .packages [Wayback] .raw.xz.sha256 [Wayback] [Wayback] .raw.xz.sha256.asc-
- Image [Wayback] openSUSE-Tumbleweed-ARM-E20-raspberrypi3.aarch64-2020.08.15-Snapshot20200905.raw.xz [Wayback] .packages [Wayback] .raw.xz.sha256 [Wayback] [Wayback] .raw.xz.sha256.asc
-
- Image [Wayback]
Parts of the chat transcript:
[10:39am] <wiert>
I can use some help with openSUSE-Tumbleweed-ARM-E20-raspberrypi3.aarch64-2020.08.15-Snapshot20200904.raw.xz
[10:40am] <wiert>
It looks like it does not start in graphical mode, despite it saying it is starting it.
[10:41am] <wiert>
This is the screenshot after booting: https://photos.app.goo.gl/Y8bAh93XiHBDxZwF8
[10:41am] <wiert>
How can I get enough context so I can provide that information for a bug report?
[10:42am] <wiert>
It is running on Raspberry Pi 3B
[10:42am] <wiert>
I have enough fresh Micro SD cards to re-install from plain image openSUSE-Tumbleweed-ARM-E20-raspberrypi3.aarch64-2020.08.15-Snapshot20200904.raw.xz
[10:52am] <guillaume_g>
wiert: Hi! You can log in and get the journal to check error messages
[10:57am] <wiert>
I resolved “Aug 27 00:01:03 localhost.localdomain lightdm[1842]: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files” by running `journalctl -u display-manager`
[10:59am] <wiert>
It still does not start
[10:59am]
kasimir left the chat room. (Quit: kasimir)
[11:07am] <guillaume_g>
journalctl does not boot anything, it just shows log messages
[11:09am] <wiert>
Sorry, had the cancer hospital on the phone when copy/pasting the command line.
[11:09am] <wiert>
The fix was `zypper install –no-confirm accountsservice` to get rid of the errors.
[11:10am] <wiert>
There are no errors left, but the Graphical Target does not start either.
[11:10am] <wiert>
See the journalctl output here: https://gist.github.com/jpluimers/d013ef1c6230e03bfeea30dafb81f6f5
[11:12am] <wiert>
I will try another Micro SD card with “openSUSE-Leap-15.2-ARM-E20-raspberrypi3.aarch64-2020.07.08-Build1.34.raw.xz” shortly.
[11:12am] <guillaume_g>
Could you check if lightdm is installed?
[11:18am] <wiert>
# rpm -aq | grep light
[11:18am] <wiert>
xbacklight-1.2.3-1.4.aarch64
[11:18am] <wiert>
beforelight-1.0.5-7.17.aarch64
[11:18am] <wiert>
liblightdm-gobject-1-0-1.30.0-2.2.aarch64
[11:18am] <wiert>
enlightenment-theme-openSUSE-20200528-1.2.noarch
[11:18am] <wiert>
enlightenment-profiles-openSUSE-20160622-1.8.noarch
[11:18am] <wiert>
enlightenment-branding-openSUSE-0.1-5.10.aarch64
[11:18am] <wiert>
enlightenment-0.24.2-2.2.aarch64
[11:18am] <wiert>
lightdm-gtk-greeter-branding-openSUSE-2.0-3.2.noarch
[11:18am] <wiert>
lightdm-gtk-greeter-2.0.6-1.10.aarch64
[11:18am] <wiert>
lightdm-1.30.0-2.2.aarch64
[11:18am] <wiert>
lightdm-lang-1.30.0-2.2.noarch
[11:18am] <wiert>
patterns-enlightenment-enlightenment-20170319-2.8.aarch64
[11:19am] <fvogt>
Maybe the usual issue with systemd not setting CanGraphical=true. Does it work if you boot with “nomodeset”?
[11:20am] <wiert>
https://openqa.opensuse.org/tests/1384610 shows that during automated tests, it does work.
[11:21am] <wiert>
@fvogt I need some help with that as I have never booted with different kernel parameters. How do I do that?
[11:22am] <fvogt>
wiert: press e during grub, then append it to the “linux” line
[11:23am] <wiert>
Need to check first if my USB keyboard is recognised that early.
[11:24am] <wiert>
Give me a few minutes as I first need to empty the ileostomy bag before I can sit down behind a keyboard again (current state is lying down due to the ileostomy problems I have)
[11:26am] <guillaume_g>
fvogt: where CanGraphical=true should be set? I do not think JeOS set it.
[11:27am] <fvogt>
guillaume_g: systemd does it with udev rules
[11:32am] <guillaume_g>
fvogt: ok, so it should detect properly the hdmi output… How could we check that it is detected properly?
[11:37am] <fvogt>
guillaume_g: https://github.com/systemd/systemd/issues/16341 -> loginctl show-seat seat0
[11:37am] <|Anna|>
Github project systemd/systemd issue#16341: “No device with CanGraphical=yes on Raspberry Pi 4B with openSUSE Tumbleweed and KDE”, created on 2020-07-02, status: open, unassigned, https://github.com/systemd/systemd/issues/16341
[11:38am] <wiert>
(the ileostomy is a result of metastased rectum cancer, which is the reason I have not been here for about a year, but I need to setup a spare Raspberry Pi so my mentally retarded brother can visit https://martijn.pluimers.com/agenda-month-weather.html if his current Raspberry Pi breaks down in the weeks after my upcoming surgery next friday)
[11:39am] <wiert>
Indeed what I was afraid of: during grub, no USB keyboard is recognised.
[11:40am] <wiert>
any alternatives to shoehorn nomodeset into the kernel boot options?
[11:44am] <fvogt>
wiert: As you can log in, run “loginctl show-seat seat0” to show whether it’s indeed the cause
[11:44am] <fvogt>
If it has CanGraphical=true, it needs a bit more digging…
[11:46am] <wiert>
Bummer:
[11:46am] <wiert>
# loginctl show-seat seat0
[11:46am] <wiert>
Id=seat0
[11:46am] <wiert>
CanMultiSession=yes
[11:46am] <wiert>
CanTTY=yes
[11:46am] <wiert>
CanGraphical=yes
[11:46am] <wiert>
Sessions=
[11:46am] <wiert>
IdleHint=yes
[11:46am] <wiert>
IdleSinceHint=0
[11:46am] <wiert>
IdleSinceHintMonotonic=0
[11:48am] <fvogt>
In your journal it doesn’t say anything about graphical target, so what happens if you systemctl start graphical.target?
[11:52am] <wiert>
This happens:
[11:52am] <wiert>
Sep 07 09:49:20 donald display-manager[2920]: /etc/vconsole.conf available
[11:52am] <wiert>
Sep 07 09:49:20 donald display-manager[2920]: KEYMAP: us.map.gz
[11:52am] <wiert>
Sep 07 09:49:20 donald display-manager[2920]: Command: localectl set-keymap us.map.gz
[11:52am] <wiert>
Sep 07 09:49:20 donald display-manager[2920]: W: Cannot find mapping for us.map.gz in /usr/share/systemd/kbd-model-map
[11:52am] <wiert>
Sep 07 09:49:20 donald display-manager[2920]: W: This will result in an ‘us’ X keyboard layout as default
[11:52am] <wiert>
Sep 07 09:49:20 donald dbus-daemon[1026]: [system] Activating via systemd: service name=’org.freedesktop.locale1′ unit=’dbus-org.freedesktop.locale1.service’ requested by ‘:1.40’ (uid=0 pid=2933 comm=”localectl set-keymap us.map.gz “)
[11:52am] <wiert>
Sep 07 09:49:20 donald systemd[1]: issue-generator.service: Succeeded.
[11:52am] <wiert>
Sep 07 09:49:20 donald systemd[1]: Finished Generate issue file for login session.
[11:52am] <wiert>
Sep 07 09:49:20 donald systemd[1]: Starting Locale Service…
[11:52am] <wiert>
Sep 07 09:49:21 donald dbus-daemon[1026]: [system] Successfully activated service ‘org.freedesktop.locale1’
[11:52am] <wiert>
Sep 07 09:49:21 donald systemd[1]: Started Locale Service.
[11:52am] <wiert>
Sep 07 09:49:21 donald root[2945]: /etc/init.d/xdm: No changes for /etc/X11/xdm/Xservers
[11:52am] <wiert>
Sep 07 09:49:21 donald root[2945]: /etc/init.d/xdm: No changes for /etc/X11/xdm/xdm-config
[11:52am] <wiert>
Sep 07 09:49:21 donald startproc[2980]: startproc: exit status of parent of /usr/sbin/lightdm: 1
[11:52am] <wiert>
Sep 07 09:49:21 donald display-manager[2913]: Starting service lightdm
[11:52am] <wiert>
Sep 07 09:49:21 donald systemd[1]: display-manager.service: Control process exited, code=exited, status=1/FAILURE
[11:52am] <wiert>
Sep 07 09:49:21 donald systemd[1]: display-manager.service: Failed with result ‘exit-code’.
[11:52am] <wiert>
Sep 07 09:49:21 donald systemd[1]: Failed to start X Display Manager.
[11:52am] <wiert>
Sep 07 09:49:21 donald systemd[1]: display-manager.service: Triggering OnFailure= dependencies.
[11:52am] <wiert>
Sep 07 09:49:21 donald systemd[1]: display-manager.service: Failed to enqueue OnFailure= job, ignoring: Unit plymouth-quit.service not found.
[11:52am] <wiert>
Sep 07 09:49:21 donald systemd[1]: Starting Update UTMP about System Runlevel Changes…
[11:52am] <wiert>
Sep 07 09:49:21 donald systemd[1]: systemd-update-utmp-runlevel.service: Succeeded.
[11:52am] <wiert>
Sep 07 09:49:21 donald systemd[1]: Finished Update UTMP about System Runlevel Changes.
[11:52am] <wiert>
Sep 07 09:49:51 donald systemd[1]: systemd-localed.service: Succeeded.
[11:53am] <fvogt>
wiert: Please use susepaste or something like that for longer output
[11:53am] <wiert>
Is a gist OK too?
[11:53am] <fvogt>
Of course
[11:53am] <wiert>
Will do that for future quoting of output.
[11:53am] <fvogt>
Thanks
[11:55am] <wiert>
In the mean time, I’m going to put openSUSE-Leap-15.2-ARM-E20-raspberrypi3.aarch64-2020.07.08-Build1.34.raw.xz on another SD card and see what happens there.
[11:56am] <fvogt>
Ok, lightdm fails to start, but there’s no helpful error message
[11:57am] <wiert>
Did I ever tell I am a bug magnet in both professional as real life (that’s why I am scared to death about the upcoming surgery)
[12:04pm]
kasimir joined the chat room.
[12:13pm] <wiert>
That one boots in Graphical Target fine.
[12:14pm] <wiert>
What I will do is finish the configuration of this image, and will try to get back later with the lightdm on Tumbleweed.
[12:14pm] <wiert>
Is that OK?
--jeroen
The Wiert Corner - irregular stream of stuff 
Leave a comment