572243 – F13 - black screen in anaconda

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 572243 - F13 - black screen in anaconda

Summary: F13 - black screen in anaconda

Keywords:
Status:	CLOSED NEXTRELEASE
Alias:	None
Product:	Red Hat Enterprise Linux 6
Classification:	Red Hat
Component:	xorg-x11-drv-intel
Sub Component:
Version:	6.0
Hardware:	All
OS:	Linux
Priority:	low
Severity:	medium
Target Milestone:	rc
Target Release:	---
Assignee:	Adam Jackson
QA Contact:	Fedora Extras Quality Assurance
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2010-03-10 16:08 UTC by Michał Piotrowski
Modified:	2010-06-08 18:39 UTC (History)
CC List:	2 users (show)
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:	2010-06-08 18:30:34 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)
xorg.conf for vesa mode (68 bytes, text/plain) 2010-05-18 12:09 UTC, Michał Piotrowski	no flags	Details
xorg.log - from working vesa session (45.44 KB, text/plain) 2010-05-18 12:10 UTC, Michał Piotrowski	no flags	Details
xorg.log - from not working intel driver (5.10 KB, text/plain) 2010-05-18 12:11 UTC, Michał Piotrowski	no flags	Details
dmesg (35.64 KB, text/plain) 2010-05-18 12:11 UTC, Michał Piotrowski	no flags	Details
messages file (218.38 KB, text/plain) 2010-05-18 12:13 UTC, Michał Piotrowski	no flags	Details
result after boot without nomodeset (198.09 KB, image/jpeg) 2010-05-18 16:28 UTC, Michał Piotrowski	no flags	Details
new version of messages file (390.22 KB, text/plain) 2010-05-18 16:33 UTC, Michał Piotrowski	no flags	Details
messages with drm.debug=0x04 (57.70 KB, text/plain) 2010-05-19 13:02 UTC, Michał Piotrowski	no flags	Details
new version of dmesg with drm.debug=0x04 (47.40 KB, application/octet-stream) 2010-06-08 13:35 UTC, Michał Piotrowski	no flags	Details
View All

Description Michał Piotrowski 2010-03-10 16:08:58 UTC

Description of problem:
GPU no workie - black screen.

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


How reproducible:
I booted normal installation procedure and I saw a black screen. I booted simple driver and instalator falbacked to text mode.

Steps to Reproduce:
1.
2.
3.
  
Actual results:
[    39.164] (WW) Failed to open protocol names file /usr/lib64/xorg/protocol.txt
This is a pre-release version of the X server from Fedora Project.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the "xorg" product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the X.Org Foundation git repository.
See http://wiki.x.org/wiki/GitPage for git access instructions.
[    39.165]
X.Org X Server 1.7.99.901 (1.8.0 RC 1)
Release Date: 2010-02-12
[    39.165] X Protocol Version 11, Revision 0
[    39.165] Build Operating System: x86-01 2.6.18-164.6.1.el5
[    39.165] Current Operating System: Linux localhost.localdomain 2.6.33-0.52.rc8.git6.fc13.x86_64 #1 SMP Tue Feb 23 04:52:05 UTC 2010 x86_64
[    39.166] Kernel command line: initrd=initrd.img stage2=hd:LABEL="Fedora" xdriver=vesa nomodeset BOOT_IMAGE=vmlinuz
[    39.166] Build Date: 23 February 2010  05:04:42AM
[    39.166] Build ID: xorg-x11-server 1.7.99.901-8.20100223.fc13
[    39.166] Current version of pixman: 0.17.6
[    39.166]    Before reporting problems, check http://bodhi.fedoraproject.org/
        to make sure that you have the latest version.
[    39.166] Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    39.167] (++) Log file: "/tmp/X.log", Time: Wed Mar 10 16:50:55 2010
[    39.169] (==) Using config directory: "/etc/xorg.conf.d"
[    39.170] (==) No Layout section.  Using the first Screen section.
[    39.170] (==) No screen section available. Using defaults.
[    39.170] (**) |-->Screen "Default Screen Section" (0)
[    39.170] (**) |   |-->Monitor "<default monitor>"
[    39.174] (==) No monitor specified for screen "Default Screen Section".
        Using a default monitor configuration.
[    39.174] (==) Automatically adding devices
[    39.174] (==) Automatically enabling devices
[    39.174] (==) FontPath set to:
        catalogue:/etc/X11/fontpath.d,
        built-ins
[    39.174] (==) ModulePath set to "/usr/lib64/xorg/modules"
[    39.174] (II) Cannot locate a core pointer device.
[    39.174] (II) Cannot locate a core keyboard device.
[    39.174] (II) The server relies on udev to provide the list of input devices.
        If no devices become available, reconfigure udev or disable AutoAddDevices.
[    39.174] (II)
***************************************************************
***************************************************************
** Fedora switched to udev-based device detection with       **
** xorg-x11-server-1.7.99.901-1. Custom HAL configuration    **
** stored in /etc/hal/fdi/policy will not be seen by this    **
** server version. If you have such configuration you will   **
** need to update it to the new format.                      **
** For more information, see the Fedora wiki page            **
** https://fedoraproject.org/wiki/Input_device_configuration **
***************************************************************
***************************************************************
[    39.174] (II) Loader magic: 0x7cd980
[    39.174] (II) Module ABI versions:
[    39.174]    X.Org ANSI C Emulation: 0.4
[    39.174]    X.Org Video Driver: 7.0
[    39.174]    X.Org XInput driver : 9.0
[    39.174]    X.Org Server Extension : 3.0
[    39.193] (--) PCI:*(0:0:2:0) 8086:2a12:103c:3618 Intel Corporation Mobile GME965/GLE960 Integrated Graphics Controller rev 12, Mem @ 0xe4400000/1048576, 0xd0000000/268435456, I/O @ 0x00004000/8, BIOS @ 0x????????/131072
[    39.193] (--) PCI: (0:0:2:1) 8086:2a13:103c:3618 Intel Corporation Mobile GME965/GLE960 Integrated Graphics Controller rev 12, Mem @ 0xe4500000/1048576, BIOS @ 0x????????/65536
[    39.193] (II) LoadModule: "extmod"
[    39.200] (II) Loading /usr/lib64/xorg/modules/extensions/libextmod.so
[    39.299] (II) Module extmod: vendor="X.Org Foundation"
[    39.299]    compiled for 1.7.99.901, module version = 1.0.0
[    39.299]    Module class: X.Org Server Extension
[    39.299]    ABI class: X.Org Server Extension, version 3.0
[    39.299] (II) Loading extension SELinux
[    39.299] (II) Loading extension MIT-SCREEN-SAVER
[    39.299] (II) Loading extension XFree86-VidModeExtension
[    39.299] (II) Loading extension XFree86-DGA
[    39.299] (II) Loading extension DPMS
[    39.299] (II) Loading extension XVideo
[    39.299] (II) Loading extension XVideo-MotionCompensation
[    39.299] (II) Loading extension X-Resource
[    39.299] (II) LoadModule: "dbe"
[    39.302] (II) Loading /usr/lib64/xorg/modules/extensions/libdbe.so
[    39.360] (II) Module dbe: vendor="X.Org Foundation"
[    39.360]    compiled for 1.7.99.901, module version = 1.0.0
[    39.360]    Module class: X.Org Server Extension
[    39.360]    ABI class: X.Org Server Extension, version 3.0
[    39.360] (II) Loading extension DOUBLE-BUFFER
[    39.360] (II) LoadModule: "glx"
[    39.363] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
[    39.368] (II) Module glx: vendor="X.Org Foundation"
[    39.368]    compiled for 1.7.99.901, module version = 1.0.0
[    39.368]    ABI class: X.Org Server Extension, version 3.0
[    39.371] (==) AIGLX enabled
[    39.371] (II) Loading extension GLX
[    39.371] (II) LoadModule: "record"
[    39.374] (II) Loading /usr/lib64/xorg/modules/extensions/librecord.so
[    39.375] (II) Module record: vendor="X.Org Foundation"
[    39.375]    compiled for 1.7.99.901, module version = 1.13.0
[    39.375]    Module class: X.Org Server Extension
[    39.375]    ABI class: X.Org Server Extension, version 3.0
[    39.375] (II) Loading extension RECORD
[    39.375] (II) LoadModule: "dri"
[    39.378] (II) Loading /usr/lib64/xorg/modules/extensions/libdri.so
[    39.382] (II) Module dri: vendor="X.Org Foundation"
[    39.382]    compiled for 1.7.99.901, module version = 1.0.0
[    39.382]    ABI class: X.Org Server Extension, version 3.0
[    39.382] (II) Loading extension XFree86-DRI
[    39.382] (II) LoadModule: "dri2"
[    39.385] (II) Loading /usr/lib64/xorg/modules/extensions/libdri2.so
[    39.386] (II) Module dri2: vendor="X.Org Foundation"
[    39.386]    compiled for 1.7.99.901, module version = 1.2.0
[    39.386]    ABI class: X.Org Server Extension, version 3.0
[    39.386] (II) Loading extension DRI2
[    39.386] (==) Matched intel for the autoconfigured driver
[    39.386] (==) Assigned the driver to the xf86ConfigLayout
[    39.386] (II) LoadModule: "intel"
[    39.387] (II) Loading /usr/lib64/xorg/modules/drivers/intel_drv.so
[    39.515] (II) Module intel: vendor="X.Org Foundation"
[    39.515]    compiled for 1.7.99.3, module version = 2.10.0
[    39.515]    Module class: X.Org Video Driver
[    39.515]    ABI class: X.Org Video Driver, version 7.0
[    39.515] (II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
        i810-dc100, i810e, i815, i830M, 845G, 852GM/855GM, 865G, 915G,
        E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G,
        965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45,
        4 Series, G45/G43, Q45/Q43, G41, B43, Clarkdale, Arrandale
[    39.515] (++) using VT number 6

[    39.520] (II) Primary Device is: PCI 00@00:02:0
[    39.530] (EE) intel(0): No kernel modesetting driver detected.
[    39.531] (II) UnloadModule: "intel"
[    39.531] (EE) Screen(s) found, but none have a usable configuration.
[    39.531]
Fatal server error:
[    39.531] no screens found
[    39.531]
Please consult the Fedora Project support
         at http://bodhi.fedoraproject.org/
 for help.
[    39.531] Please also check the log file at "/tmp/X.log" for additional information.
[    39.531]


Expected results:

Additional info:

Comment 1 Adam Jackson 2010-03-10 19:12:27 UTC

Any particular reason why you didn't use the intel driver?

Comment 2 Michał Piotrowski 2010-03-10 19:28:19 UTC

I think that I used intel driver when I choosed installation with default graphics mode - black screen scenario. But I don't have a log from this installation.

Comment 3 Matěj Cepl 2010-03-17 23:18:45 UTC

(In reply to comment #2)
> I think that I used intel driver when I choosed installation with default
> graphics mode - black screen scenario. But I don't have a log from this
> installation.

And could we get one, please? Just start the installation and X should crash (if it happens) long before any changes would be written to the disk. If you can after crash switch to Alt+F2 (or Ctrl-Alt-F2) you could be able to save /tmp/X* files to some USB drive, and then attach them here.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.

Comment 4 Michał Piotrowski 2010-03-18 12:46:06 UTC

System doesn't respond to Alt+F2 or Ctrl-Alt-F2 - or maybe respond, but I see only a black screen.

I tried to install system in text mode, but I hit this bug https://bugzilla.redhat.com/show_bug.cgi?id=572658

Comment 5 Matěj Cepl 2010-03-26 17:12:17 UTC

There is really nothing to work on ... putting this bug in needinfo and if you will find anything new which could help us to move forward, please, let us know.

Comment 6 Michał Piotrowski 2010-03-27 16:03:44 UTC

I successfully installed a security spin without any screen issues. Maybe someone has fixed this bug?

Comment 7 Matěj Cepl 2010-04-07 22:06:08 UTC

Does Xorg work for you now on the installed system? If yes, then we can probably close this bug, there is nothing much more we should do about it.

Comment 8 Michał Piotrowski 2010-04-07 22:27:17 UTC

Yes it works now. Thanks.

Comment 9 Matěj Cepl 2010-04-12 12:30:09 UTC

Thank you for letting us know.

Comment 10 Michał Piotrowski 2010-04-22 15:39:14 UTC

I downloaded RHEL6 beta.

I tried to install system with a normal graphics driver and I had a black screen.

I used simple graphics driver - fortunately graphics installer works fine with this driver.

During the installation I had a really scary event. My laptop was on battery (was charged) - after selecting software it powered off. I wasn't able to power on it for a while (I find a solution to the problem on laptop support forum). It might be a hardware fault, but it didn't happened before - strange coincidence?

For the third time I managed to successfully install RHEL6Beta :)
Now I got a X running, but it seems to be a vesa driver. I can't use my native screen resolution 1280x800 and 3d effects. I'm not interested in second, but the working native resolution is good to have.

When I have this system running I can provide any info you need to fix this driver.

Comment 12 RHEL Program Management 2010-04-22 18:23:38 UTC

This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Comment 13 Matěj Cepl 2010-05-18 10:05:17 UTC

Please attach the standard info bundle

* your X server config file (/etc/X11/xorg.conf, if available),
* output of the dmesg command,
* system log (/var/log/messages), and
* X server log file (/var/log/Xorg.*.log)

to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.

Comment 14 Michał Piotrowski 2010-05-18 12:09:13 UTC

Created attachment 414821 [details]
xorg.conf for vesa mode

Comment 15 Michał Piotrowski 2010-05-18 12:10:30 UTC

Created attachment 414822 [details]
xorg.log - from working vesa session

Comment 16 Michał Piotrowski 2010-05-18 12:11:18 UTC

Created attachment 414823 [details]
xorg.log - from not working intel driver

Comment 17 Michał Piotrowski 2010-05-18 12:11:59 UTC

Created attachment 414825 [details]
dmesg

Comment 18 Michał Piotrowski 2010-05-18 12:13:59 UTC

Created attachment 414826 [details]
messages file

Comment 19 Michał Piotrowski 2010-05-18 12:15:39 UTC

I attached requested files.

I also removed default xorg.conf content and started x server - log is attached as "xorg.log - from not working intel driver"

Regards,
Michal

Comment 21 Adam Jackson 2010-05-18 15:45:40 UTC

The intel driver isn't going to work at all if you leave 'nomodeset' on the kernel command line.

Comment 22 Matěj Cepl 2010-05-18 15:48:56 UTC

> Kernel command line: ro root=UUID=48260d0f-c171-4a04-aeeb-d7dc0282d9e5 \
> rd_NO_LUKS rd_NO_LVM rd_NO_MD rd_NO_DM LANG=pl_PL.UTF-8 '
> SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=pl2 nomodeset rhgb quiet

I see in the xorg.log from comment 15 you have nomodeset set. Could you please try again WITHOUT nomodeset on the kernel command line (or in /etc/grub.conf)?

Thank you

Comment 23 Michał Piotrowski 2010-05-18 16:28:53 UTC

Created attachment 414903 [details]
result after boot without nomodeset

Comment 24 Michał Piotrowski 2010-05-18 16:33:29 UTC

Created attachment 414904 [details]
new version of messages file

Comment 25 Michał Piotrowski 2010-05-18 16:37:46 UTC

System without nomodeset doesn't work here - screenshot and log attached.

lspci -vvv
00:02.0 VGA compatible controller: Intel Corporation Mobile GME965/GLE960 Integrated Graphics Controller (rev 0c) (prog-if 00 [VGA controller])
        Subsystem: Hewlett-Packard Company Device 3618
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Interrupt: pin A routed to IRQ 27
        Region 0: Memory at e4400000 (64-bit, non-prefetchable) [size=1M]
        Region 2: Memory at d0000000 (64-bit, prefetchable) [size=256M]
        Region 4: I/O ports at 4000 [size=8]
        Expansion ROM at <unassigned> [disabled]
        Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
                Address: fee0300c  Data: 4189
        Capabilities: [d0] Power Management version 3
                Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
                Bridge: PM- B3+
        Kernel modules: i915

lspci -n
00:02.0 0300: 8086:2a12 (rev 0c)

Comment 26 Adam Jackson 2010-05-18 20:27:17 UTC

Please append 

    drm.debug=0x04

to the kernel command line and append the messages file after booting with that.

Comment 27 Michał Piotrowski 2010-05-19 13:02:01 UTC

Created attachment 415101 [details]
messages with drm.debug=0x04

Comment 28 Adam Jackson 2010-06-07 17:24:51 UTC

Well that sure didn't help, none of the debug messages actually made it into the log.  Can you ssh into the machine while booted with drm.debug=0x04 and collect the output of the 'dmesg' command?

Comment 29 Michał Piotrowski 2010-06-08 13:35:19 UTC

Created attachment 422195 [details]
new version of dmesg with drm.debug=0x04

I hope it helps now.

Comment 30 Adam Jackson 2010-06-08 18:30:34 UTC

This should be resolved by output setup stability fixes since -19.  Please re-test with beta 2 once it becomes available, and reopen if this is still an issue.  Thank you for testing!

Comment 31 Michał Piotrowski 2010-06-08 18:39:57 UTC

Ok, I'll test next beta. Thanks!

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