http://bugzilla.suse.com/show_bug.cgi?id=1120143 http://bugzilla.suse.com/show_bug.cgi?id=1120143#c3 James Carter <jimc@math.ucla.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(jimc@math.ucla.ed | |u) | --- Comment #3 from James Carter <jimc@math.ucla.edu> --- Created attachment 795761 --> http://bugzilla.suse.com/attachment.cgi?id=795761&action=edit Syslog at boot with dmesg output Starting with the Tumbleweed instance about a week before openSUSE-release-20190125-8.1.aarch64, the display is magically back to normal. (I was diverted by another issue and didn't get onto trying to identify just what went right, just was glad that I can see the screen again.) I'm still betting on a device tree issue. This isn't the Raspberry Pi laptop; it's a standard RPi 3B with a HDMI connection to the monitor. When it failed, the X-server would not start, sayind "no screens found" in Xorg.0.log, and no video went out to the monitor, causing the black screen. Now the X-server, display manager, and desktop are behaving as they did before 2018-12-14. I haven't had issues with I2C, but haven't tried anything fancy on that bus, so I wouldn't have noticed problems. At boot I dump dmesg into syslog, and I've attached all the boot messages that were logged, but this is for the *working* kernel; messages from failing versions have rotated into oblivion, sorry. Please ignore chaotic clock sync, which is "normal" on a RPi (no realtime clock). Search for "Booting Linux" to find the start of dmesg. We'll probably never be sure what went wrong in 2018-12-14. Let's close this report. -- You are receiving this mail because: You are on the CC list for the bug.