Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#52770 - [linux]Boot freeze with hdmi monitor plugged in
Attached to Project:
Arch Linux
Opened by Jonas Dyba (wesalius) - Monday, 30 January 2017, 08:20 GMT
Last edited by Andreas Radke (AndyRTR) - Sunday, 27 February 2022, 10:45 GMT
Opened by Jonas Dyba (wesalius) - Monday, 30 January 2017, 08:20 GMT
Last edited by Andreas Radke (AndyRTR) - Sunday, 27 February 2022, 10:45 GMT
|
DetailsDescription:
Recently when running at Kernel: 4.9.6-1-ARCH x86_64 (64 bit) Desktop: LXQt, Drivers: modesetting,intel) I got stuck at [OK] Graphical interfaced reached without any option but hard reboot (no keypresses). After unplugging my hdmi it booted ok (tried multiple times). I tried to log what happened with loglevel=6 param at boot, but it got "solved" with this setting: now I boot normally just as before, thanks to logging? (someone at archs IRC said it might be that this is a race condition that was mitigated by the logging). Steps to reproduce: 1. Plug in hdmi cable 2. get stuck at [OK] Graphical interfaced reached 3. unplug 4. boot ok 5. enable logging 6. boot normally with or without hdmi |
This task depends upon
Closed by Andreas Radke (AndyRTR)
Sunday, 27 February 2022, 10:45 GMT
Reason for closing: None
Additional comments about closing: No response in years. Let's assume fixed upstream.
Sunday, 27 February 2022, 10:45 GMT
Reason for closing: None
Additional comments about closing: No response in years. Let's assume fixed upstream.
Comment by Andreas Radke (AndyRTR) -
Tuesday, 10 December 2019, 09:49 GMT
Is this still an issue?