This site requires JavaScript to be enabled to function correctly, please enable it.
Bug 2270301 - Basic Graphics Mode seems to be broken on Fedora Workstation RC 1.9
Summary: Basic Graphics Mode seems to be broken on Fedora Workstation RC 1.9
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-server
Version: 40
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F40BetaBlocker
TreeView+ depends on / blocked
 
Reported: 2024-03-19 14:18 UTC by Lukas Ruzicka
Modified: 2024-03-20 09:25 UTC (History)
11 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-03-20 09:25:20 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Video from the EFI attempt (15.82 MB, video/x-msvideo)
2024-03-19 14:42 UTC, Lukas Ruzicka
no flags Details
screenshot from a EFI notebook booting basic graphics mode (703.06 KB, image/jpeg)
2024-03-19 15:42 UTC, Geraldo Simião
no flags Details

Description Lukas Ruzicka 2024-03-19 14:18:03 UTC
I cannot boot into the Live session using basic graphics mode on neither EFI or BIOS. I have been trying this on a bare machine using the PiKVM device for distant connection. Unfortunately, I could not test directly.



Reproducible: Always

Steps to Reproduce:
Try booting the Fedora Workstation RC 1.9 iso.
Actual Results:  
When trying over EFI:
 - Grub appears
 - I select the Troubleshooting and boot in basic mode
 - After a while the machine restarts into BIOS mode. (see attached video)

When trying BIOS mode
 - Same as with EFI but nothing restarts and the machine remains on a black screen until reset.
 - When 'rhgb' and 'quiet' are removed, it remains on a screen with "Booting a command list".

Expected Results:  
Both ways should offer basic graphics mode.

Comment 1 Lukas Ruzicka 2024-03-19 14:42:44 UTC
Created attachment 2022609 [details]
Video from the EFI attempt

Comment 2 Fedora Blocker Bugs Application 2024-03-19 15:02:56 UTC
Proposed as a Blocker for 40-beta by Fedora user lruzicka using the blocker tracking app because:

 Proposing for a blocker discussion.

Comment 3 Geraldo Simião 2024-03-19 15:26:20 UTC
I tested on this notebook:
Processors: 2 × Pentium® Dual-Core CPU T4500 @ 2.30GHz
Memory: 5.7 GiB of RAM
Graphics Processor: Mesa Mobile Intel® GM45 Express Chipset
Manufacturer: Hewlett-Packard
Product Name: HP G42 Notebook PC
sudo efibootmgr
EFI variables are not supported on this system.

And here basic graphics video mode booted successfully.

Comment 4 Geraldo Simião 2024-03-19 15:27:42 UTC
heres a video of F40 Workstation beta 1.9 booting on this HP laptop in basic mode: https://geraldosimiao.fedorapeople.org/Screencasts/F40Work-beta19-basic-video.mp4

Comment 5 Geraldo Simião 2024-03-19 15:42:36 UTC
Created attachment 2022612 [details]
screenshot from a EFI notebook booting basic graphics mode

F40 Workstation Beta 1.9 iso

Comment 6 Kamil Páral 2024-03-19 15:53:11 UTC
Tested F40 Workstation Beta 1.9 iso with basic graphics mode:

Asus B550 motherboard:
UEFI  boots OK
BIOS  boots OK

Thinkpad T480s:
UEFI  boots OK
BIOS  not tested (known to be broken for years)

Thinkpad P16v:
UEFI  boots OK
BIOS  not supported

Comment 7 Adam Williamson 2024-03-19 16:39:45 UTC
On my bare metal test box (Asus H97M-E motherboard, Radeon 6500 XT graphics):

Workstation UEFI - OK
Workstation BIOS - OK

KDE UEFI - OK
KDE BIOS - OK

SS SHIPIT

Comment 8 Lukas Ruzicka 2024-03-19 17:41:13 UTC
On the machine where it fails, the KDE iso works normally in basic graphics.

Comment 9 Kamil Páral 2024-03-20 09:25:20 UTC
I tested today the very same machine that Lukas reported problems on, with the same image, and both BIOS and UEFI basic graphics mode boots just fine. So I assume this must have been some random accident with our particular machine. Since everybody else reported that it boots fine for them, I'll close this bug, and if we can consistently reproduce the problem on our particular hardware, we'll reopen it.


Note You need to log in before you can comment on or make changes to this bug.