Same for me, but I haven’t noticed any light from the screen. (Maybe the ambient lighting was too bright to see it, though.)
As I recall, no effect. I’ll test again next time the issue happens. Working fine this morning.
@amarok likely backlight probe failure triggers blank display after power on (#494) · Issues · Librem5 / linux · GitLab
Thanks, @guido.gunther. I take it there’s nothing we can do for now, except to keep restarting until it works?
@irvinewade
The problem occurred again, so I tested a reboot from ssh (sudo required here). This did correct the problem (this time), and display appeared normally. I don’t think this works every time, so I’ll test again when the problem happens.
EDIT: OK, the ssh reboot seems to be working consistently so far.
In that topic, the OP’s issue is totally different from mine. The posts you made in that topic sound somewhat similar to my problem, except that the LED briefly illuminates (as normal), and then turns off (as normal). But for me, the display remains black instead of turning on and showing the login screen.
OK, thanx.
I’m not sure if I suffer somehow from the same issue though.
Sometimes I need to force a reboot more then 3 times before it shows the login screen.
And some-days, booting goes as it should.
Same here.
@amarok I’m not aware of any other workarounds than reboot. I’ll link the forum thread to the issue so the kernel team is aware that it’s not only affecting me
@amarok could you verify you’re seeing the
[ 0.921367] lm3692x 2-0036: Cannot read/clear faults: -110
[ 0.926880] lm3692x 2-0036: Fail writing initialization values
[ 0.933098] lm3692x: probe of 2-0036 failed with error -110
in dmesg when the screen fails to turn on (so we’re sure there’s not another issue as well)
I’ve got:
0.299923] lm3692x 2-0036: Cannot read/clear faults: -11
0.305349] lm3692x 2-0036: Fail writing initialization values
0.311542] lm3692x: probe of 2-0036 failed with error -11
same problem, green led 1 second then black screen, I thought it was due to the battery starting to weaken because if I plug in the charger at the time of the green led, the start-up goes without a hitch.
I’ve got the suspension activated
If I do a sudo reboot
, the phone doesn’t reboot systematically.
I have been checking logfiles after having boot problems and I noticed these log entries showing up:
- power key pressed
- edt_ft5x06 2-0038: Unable to fetch data, error: -6
- Failed to get current UI legacy scaling factor (2x)
- unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Next entry is again “Power key pressed.”
I asume that I used the power key once more due to seeing nothing on the screen.
I experienced 3 power on’s without problems. This morning the problem is back again.
Log events:
systemd-logind Power key pressed.
17/12/2023 09:54 session-1.scope Failed to claim ambient sensor: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name net.hadess.SensorProxy was not provided by any .service files
17/12/2023 09:54 session-1.scope Failed to get current UI legacy scaling factor
17/12/2023 09:54 session-1.scope Failed to get current UI legacy scaling factor
17/12/2023 09:54 session-1.scope unable to get EDID for xrandr-DSI-1: unable to get EDID for output
17/12/2023 09:54 session-1.scope Failed to claim ambient sensor: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name net.hadess.SensorProxy was not provided by any .service files
The issue has returned for me, too.
Indeed, it’s rarer, but it still happens.
Yes, definitely improved.