Bug 1961092
| Summary: | X fails to start when booting the installer in "basic graphics mode". | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Jan Stodola <jstodola> | ||||||||||
| Component: | lorax-templates-rhel | Assignee: | Brian Lane <bcl> | ||||||||||
| Status: | CLOSED ERRATA | QA Contact: | Release Test Team <release-test-team-automation> | ||||||||||
| Severity: | medium | Docs Contact: | Sagar Dubewar <sdubewar> | ||||||||||
| Priority: | unspecified | ||||||||||||
| Version: | 9.0 | CC: | ajax, bcl, csoriano, davide, javierm, jwboyer, lkuprova, lmanasko, mdolezel, michel, ngompa13, pzatko, rdieter, sbarcomb, sbueno, sdubewar, tdawson, tpelka | ||||||||||
| Target Milestone: | rc | Keywords: | Regression, Triaged | ||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | Unspecified | ||||||||||||
| OS: | Unspecified | ||||||||||||
| Whiteboard: | |||||||||||||
| Fixed In Version: | lorax-templates-rhel-9.0-26.el9 | Doc Type: | Bug Fix | ||||||||||
| Doc Text: |
.The `basic graphics` mode has been removed from the boot menu
Previously, the `basic graphics` mode was used to install RHEL on hardware with an unsupported graphics card or to work around issues in graphic drivers that prevented starting the graphical interface. With this update, the option to install in a `basic graphics` mode has been removed from the installer boot menu. Use the VNC installation options for graphical installations on unsupported hardware or to work around driver bugs.
For more information on installations using VNC, see the link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/performing_a_standard_rhel_9_installation/assembly_performing-a-remote-installation-using-vnc_installing-rhel[Performing a remote RHEL installation using VNC] section.
|
Story Points: | --- | ||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2022-05-17 12:38:14 UTC | Type: | Bug | ||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||
| Documentation: | --- | CRM: | |||||||||||
| Verified Versions: | Category: | --- | |||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
| Embargoed: | |||||||||||||
| Bug Depends On: | |||||||||||||
| Bug Blocks: | 1942219 | ||||||||||||
| Attachments: |
|
||||||||||||
|
Description
Jan Stodola
2021-05-17 08:49:10 UTC
Created attachment 1783971 [details]
anaconda.log
Created attachment 1783972 [details]
syslog
Created attachment 1783973 [details]
X.log
Created attachment 1784159 [details]
journalctl from installed system
The same problem exists on an installed system. When booting with "nomodeset" on the kernel command line, X won't start. Re-assigning to Xorg for review.
"Basic graphics" is a terrible name and we need to call it "emergency graphics" or something. If we keep it. But I wish we wouldn't keep it. One recurring issue we see is people choosing basic graphics because they think it's the safest choice and then wondering why gfx is so slow after installation, because the 'nomodeset' you added to kcmdline to get basic graphics will get propagated into the installed system's grub.conf. At root, the issue here is there is no longer a vesa driver in RHEL9. When you say 'nomodeset' on the kernel command line it disables all KMS drivers. The only other kind of X driver is fbdev, which would work just fine on UEFI systems, but here you've chosen to boot your virtual machine with BIOS instead. Which means you have asked the kernel to disable graphics entirely. I'm not sure what else to do here besides remove the basic graphics option from the boot menu, which would be a lorax template issue. If there's really a need to keep a "basic" mode the best we can give you is disabling graphics acceleration, but I'd kind of like to see an existence proof of its necessity first, and a Really Good Reason why they can't use vnc instead. Would it make sense to remove this and replace it with a menu entry to boot in text mode by only adding inst.text? This would make anaconda prompt for vnc use and not start X but also not mess with propagating settings to the installed system. Changing this would also require documentations changes where we could explain in more detail why nomodeset really isn't the right thing to use anymore. > Would it make sense to remove this and replace it with a menu entry to boot in text mode by only adding inst.text? This would make anaconda prompt for vnc use and not start X but also not mess with propagating settings to the installed system. That sounds good to me, sure. > Changing this would also require documentations changes where we could explain in more detail why nomodeset really isn't the right thing to use anymore. I'm happy to help with the doc content here. (In reply to Adam Jackson from comment #7) > > Would it make sense to remove this and replace it with a menu entry to boot in text mode by only adding inst.text? This would make anaconda prompt for vnc use and not start X but also not mess with propagating settings to the installed system. > > That sounds good to me, sure. > > > Changing this would also require documentations changes where we could explain in more detail why nomodeset really isn't the right thing to use anymore. > > I'm happy to help with the doc content here. Sorry, this slipped my attention for a bit. So I tried to change things upstream in Fedora and has some people claiming that nomodeset still helps them in some situations. Is this something that's different between the Fedora and RHEL kernels maybe? https://github.com/weldr/lorax/pull/1152 I don't think there's really a technical difference, but there may be a philosophy/user base difference. With Fedora we still kinda want to do what we can to make it work graphically on $RANDOM_USER_HARDWARE. "Basic graphics" does still sometimes help there, if e.g. someone is using a new NVIDIA adapter that doesn't work with 'native' drivers or something. That may be less important on RHEL, where we have some notion of "supported hardware", and we're less bothered about desktop use in general... I can see "remove it on RHEL, keep it on Fedora" as a possible outcome here, honestly. And renaming it to something scarier isn't a bad idea either. Here's a pull request for c9s, we just need an ITM set. https://gitlab.com/redhat/centos-stream/rpms/lorax-templates-rhel/-/merge_requests/21 (This won't be going into Fedora, just RHEL 9) JFYI, I think it would be worth revisiting with Javier's work on SimpleDRM enablement. That eliminates all the issues around fbdev and rationalizes the graphics pipeline (we can use Wayland from the very beginning, etc.). I do also think it's worth considering renaming it from "basic graphics" to "failsafe graphics" or something similar. References: * https://fedoraproject.org/wiki/Changes/ReplaceFbdevDrivers * https://lists.freedesktop.org/archives/dri-devel/2021-October/328704.html * Bug 1986223 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (new packages: lorax-templates-rhel), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2022:2364 The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days |