Bug 572243
Summary: | F13 - black screen in anaconda | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Michał Piotrowski <mkkp4x4> | ||||||||||||||||||||
Component: | xorg-x11-drv-intel | Assignee: | Adam Jackson <ajax> | ||||||||||||||||||||
Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||||||
Severity: | medium | Docs Contact: | |||||||||||||||||||||
Priority: | low | ||||||||||||||||||||||
Version: | 6.0 | CC: | ajax, xgl-maint | ||||||||||||||||||||
Target Milestone: | rc | Keywords: | Reopened, Triaged | ||||||||||||||||||||
Target Release: | --- | ||||||||||||||||||||||
Hardware: | All | ||||||||||||||||||||||
OS: | Linux | ||||||||||||||||||||||
Whiteboard: | |||||||||||||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||||||||
Doc Text: | Story Points: | --- | |||||||||||||||||||||
Clone Of: | Environment: | ||||||||||||||||||||||
Last Closed: | 2010-06-08 18:30:34 UTC | Type: | --- | ||||||||||||||||||||
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
Michał Piotrowski
2010-03-10 16:08:58 UTC
Any particular reason why you didn't use the intel driver? 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. (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. 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 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. I successfully installed a security spin without any screen issues. Maybe someone has fixed this bug? 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. Yes it works now. Thanks. Thank you for letting us know. 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. 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. 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. Created attachment 414821 [details]
xorg.conf for vesa mode
Created attachment 414822 [details]
xorg.log - from working vesa session
Created attachment 414823 [details]
xorg.log - from not working intel driver
Created attachment 414825 [details]
dmesg
Created attachment 414826 [details]
messages file
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 The intel driver isn't going to work at all if you leave 'nomodeset' on the kernel command line. > 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 Created attachment 414903 [details]
result after boot without nomodeset
Created attachment 414904 [details]
new version of messages file
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) Please append drm.debug=0x04 to the kernel command line and append the messages file after booting with that. Created attachment 415101 [details]
messages with drm.debug=0x04
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? Created attachment 422195 [details]
new version of dmesg with drm.debug=0x04
I hope it helps now.
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! Ok, I'll test next beta. Thanks! |