Bug 1470710

Summary: Fedora-Workstation-netinst-x86_64-26-1.5.iso, no video output for main interface
Product: [Fedora] Fedora Reporter: Keith Dixon <kldixon>
Component: xorg-x11Assignee: X/OpenGL Maintenance List <xgl-maint>
Status: CLOSED EOL QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 31CC: anaconda-maint-list, g.kaviyarasu, jkonecny, jonathan, mkolman, vanmeeuwen+fedora, vponcova
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-11-24 19:05:06 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:
Attachments:
Description Flags
syslog
none
anaconda.log
none
dnf.librepo.log
none
hawkey.log
none
ifcfg.log
none
packaging.log
none
program.log
none
sensitive-info.log
none
storage.log
none
X.log none

Description Keith Dixon 2017-07-13 13:49:49 UTC
Created attachment 1297621 [details]
syslog

Description of problem:
During booting of the installer, console 1, Ctrl+Alt+F1, the tmux terminal multiplexor, works fine but, when the switch to the main installation interface on console 6 is made, a cursor appears in the top left corner of the screen for a few seconds then the monitor OSD registers no input. 
Other activities continue, data is being downloaded, and I can switch back and forth between consoles 6 and 1, (terminals Ctrl+b 1 to 5 work), but console 6 remains dead.
Consoles 2, 3 and 5 show root prompts and console 4 seems to be syslog. All seem to work.
If I give the kernel parameter inst.text then console 6 gives a root prompt as intended.
Neither nouveau.noaccel=1 nor nouveau.nofbaccel=1 have any effect.
I have no problem in booting Fedora-Workstation-Live-x86_64-26-1.5.iso.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Boot netinst iso from a USB stick
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Keith Dixon 2017-07-13 13:53:02 UTC
Created attachment 1297623 [details]
anaconda.log

anaconda.log

Comment 2 Keith Dixon 2017-07-13 13:53:52 UTC
Created attachment 1297624 [details]
dnf.librepo.log

dnf.librepo.log

Comment 3 Keith Dixon 2017-07-13 13:55:18 UTC
Created attachment 1297625 [details]
hawkey.log

Comment 4 Keith Dixon 2017-07-13 13:56:19 UTC
Created attachment 1297626 [details]
ifcfg.log

Comment 5 Keith Dixon 2017-07-13 13:56:59 UTC
Created attachment 1297627 [details]
packaging.log

Comment 6 Keith Dixon 2017-07-13 13:57:38 UTC
Created attachment 1297633 [details]
program.log

Comment 7 Keith Dixon 2017-07-13 13:59:25 UTC
Created attachment 1297635 [details]
sensitive-info.log

Comment 8 Keith Dixon 2017-07-13 14:00:17 UTC
Created attachment 1297636 [details]
storage.log

Comment 9 Keith Dixon 2017-07-13 14:00:46 UTC
Created attachment 1297637 [details]
X.log

Comment 10 Jiri Konecny 2017-07-14 08:08:52 UTC
From our logs it looks to me like the X server was started successfully.

Maybe some problem with Xorg server?

Comment 11 Keith Dixon 2017-07-17 08:23:53 UTC
It occurred to me that I suffered what might be a related problem when installing Fedora 21 on the same hardware and submitted the following bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=1181563
That bug  was never resolved. The current problem is worse, as it completely prevents me installing, but is similar in that everything seems to be working except the GUI.

Comment 12 Keith Dixon 2017-07-21 08:53:03 UTC
I now know far more about anaconda than I ever wanted to. :)

The following imply that the nouveau driver may be preferred over the modesetting driver for older Nvidia gpus, (specifically for my hardware, GT218 [GeForce 210] NVA8):
http://phoronix.com/scan.php?page=news_item&px=Nouveau-Vs-Modesetting
https://bugs.freedesktop.org/show_bug.cgi?id=94844

The following is for anyone with the same problem who finds this bug.

1) Boot the netinst iso and, when they become available, switch to a console, with a root prompt, other than tmux or the xserver, e.g. console 2:
Ctrl+Alt+F2

2) Create the following file:
# cat > /usr/share/X11/xorg.conf.d/10-nouveau.conf << "EOF"
Section "OutputClass"
        Identifier "Nouveau"
        MatchDriver "nouveau"
        Driver "nouveau"
EndSection

EOF
and check it:
# cat /usr/share/X11/xorg.conf.d/10-nouveau.conf
This will force the xserver to use the nouveau driver, when it is restarted, if the nouveau kernel module is in use, instead of the modesetting driver. 
The nouveau driver is present, even though anaconda will never use it without this xorg.conf.d file:
# ls /usr/lib64/xorg/modules/drivers
ati_drv.so    intel_drv.so        openchrome_drv.so  v4l_drv.so
dummy_drv.so  modesetting_drv.so  qxl_drv.so         vesa_drv.so
fbdev_drv.so  nouveau_drv.so      radeon_drv.so      vmware_drv.so

3) Restart the anaconda service
# systemctl restart anaconda.service

This bug remains a bug of course. On the xorg side, the OutputClass section needs an  additional Match entry to specify the hardware more accurately. A MatchGPU entry, say, that would take a '|' separated list of GPU code names
https://nouveau.freedesktop.org/wiki/CodeNames/
Then anaconda would need to include a suitable 10-nouveau.conf file.

Comment 13 Keith Dixon 2017-11-15 14:01:46 UTC
Fedora-Workstation-netinst-x86_64-27-1.6.iso has the same problem but the workaround in comment 12 still works.

Comment 14 Keith Dixon 2018-05-04 16:34:34 UTC
Fedora-Workstation-netinst-x86_64-28-1.1.iso has the same problem but the workaround in comment 12 still works.

Comment 15 Keith Dixon 2018-11-01 11:42:34 UTC
Fedora-Workstation-netinst-x86_64-29-1.2.iso has the same problem but the workaround in comment 12 still works.

Comment 16 Keith Dixon 2019-05-01 14:19:35 UTC
Fedora-Workstation-netinst-x86_64-30-1.2.iso has the same problem but the workaround in comment 12 still works.

Comment 17 Keith Dixon 2019-11-01 14:56:05 UTC
Fedora-Everything-netinst-x86_64-31-1.9.iso has the same problem but the workaround in comment 12 still works.

Comment 18 Ben Cotton 2020-11-03 14:58:52 UTC
This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '31'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 31 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 19 Ben Cotton 2020-11-24 19:05:06 UTC
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.