Bug 720624 - X corrupted with Sandy Bridge graphics - Dell Optiplex 790 USFF
Summary: X corrupted with Sandy Bridge graphics - Dell Optiplex 790 USFF
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: distribution
Version: 5.7
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: RHEL Program Management
QA Contact: Ondrej Hudlicky
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-12 09:58 UTC by Gordon Stocks
Modified: 2014-12-15 14:32 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-02 13:05:06 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Xorg.0.log from Optiplex 790USFF (49.80 KB, text/plain)
2011-07-12 13:23 UTC, Gordon Stocks
no flags Details

Description Gordon Stocks 2011-07-12 09:58:27 UTC
Description of problem:
X fails during graphical install, and is corrupt (garbled, mostly blank screen) when started following text install on Dell Optiplex 790 USFF with onboard Sandy Bridge Graphics chip.

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


How reproducible:
Always

Steps to Reproduce:
1. Install RH5.7
2. start X
3.
  
Actual results:
X display is garbled, mostly blank.

Expected results:
regular X display

Additional info:
New (ish) Dell Optiplex 790 USFF has onboard Sandy Bridge Graphics chipset. Graphical install of RH5.7 (and below) is not possible. Going through a text install, then trying to start x once install is complete results in a mostly blank screen with garbled lines that alter as the mouse is moved.

RH6.0 also had this issue, although RH6.1 appears to work fine.

[root@790test ~]# lspci | grep -i graph
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)

[root@790test ~]# more /proc/cpuinfo | grep model
model           : 42
model name      :        Intel(R) Core(TM) i5-2500S CPU @ 2.70GHz

Not sure what other information would be useful..

Comment 2 Vladimir Benes 2011-07-12 12:42:24 UTC
we've tested Lenovo X220 but we cannot se such error.. Anaconda works well and also vesa driver can be used to start X.org server

00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
	Subsystem: Lenovo Device [17aa:21da]
	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 31
	Region 0: Memory at f0000000 (64-bit, non-prefetchable) [size=4M]
	Region 2: Memory at e0000000 (64-bit, prefetchable) [size=256M]
	Region 4: I/O ports at 4000 [size=64]
	Expansion ROM at <unassigned> [disabled]
	Capabilities: <access denied>
	Kernel driver in use: i915
	Kernel modules: i915

Intel(R) Core(TM) i7-2620M CPU @ 2.70GHz

do you need any other info from me?

Comment 3 Gordon Stocks 2011-07-12 13:23:20 UTC
Created attachment 512428 [details]
Xorg.0.log from Optiplex 790USFF

Comment 4 Gordon Stocks 2011-07-12 13:24:52 UTC
Thanks for the response. Strange then that I can't get anything out of this system at all, then. I don't get any errors in the Xorg log (attached). I just get a mostly blank screen with some horizontal lines that I presume is the mouse pointer as it reacts to mouse movement.

lscpi -vvv looks almost identical to yours:


00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller])
        Subsystem: Dell Device 04ad
        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 11
        Region 0: Memory at e0c00000 (64-bit, non-prefetchable) [size=4M]
        Region 2: Memory at d0000000 (64-bit, prefetchable) [size=256M]
        Region 4: I/O ports at 3000 [size=64]
        Expansion ROM at <unassigned> [disabled]
        Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit-
                Address: 00000000  Data: 0000
        Capabilities: [d0] Power Management version 2
                Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [a4] PCI Advanced Features
                AFCap: TP+ FLR+
                AFCtrl: FLR-
                AFStatus: TP-


Did you have to alter anything to get X to start on the Lenovo system? For me, anaconda just produces an entirely black screen. The monitor still has a signal, however, as it doesn't go to sleep mode - it's just black.

Thanks,
Gordon

Comment 5 Vladimir Benes 2011-07-12 13:30:26 UTC
nope it worked out of the box. There is a bug with synaptics touchpad  so I had to comment that section out of xorg.conf after installation but everything else was working well..

Comment 6 Gordon Stocks 2011-07-12 14:01:36 UTC
Ok. getting somewhere. I moved aside the xorg.conf and tried to start X again - success! I'm so used to the default xorg.conf working fine for these systems that I didn't think to change that. Still not clear on why it fails in anaconda, however - I take it you didn't have any issues there either?

I'm going back to try similar on 5.6, as that is what we would be using on this system until 5.7 is released.

Not sure what in the default xorg.conf would cause the issues I have been seeing, however. I'll see if 5.6 also works in this way, but still interested in why anaconda doesn't go with graphical mode, or why the default xorg.conf has issues.

Comment 7 Gordon Stocks 2011-07-12 16:17:06 UTC
This also appears to be the case with 5.6. Anaconda doesn't go graphical (Blank screen) and the default xorg.conf produces the same garbled effect. Moving aside the xorg.conf and restarting X works just fine. Can log in and go about my business..

However, switching to a virtual console, say, F1 ,and back again hangs the machine completely...

Comment 9 Tru Huynh 2011-09-08 13:44:08 UTC
same thing here with the full startx (without xorg.conf) output

[root@lutin ~]# startx
xauth:  creating new authority file /root/.serverauth.3273

_XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
_XSERVTransOpen: transport open failed for inet6/lutin.sis.pasteur.fr:0
_XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6

X Window System Version 7.1.1
Release Date: 12 May 2006
X Protocol Version 11, Revision 0, Release 7.1.1
Build Operating System: Linux 2.6.18-53.el5 x86_64 Red Hat, Inc.
Current Operating System: Linux lutin.sis.pasteur.fr 2.6.18-274.el5 #1 SMP Fri Jul 22 04:43:29 EDT 2011 x86_64
Build Date: 20 April 2011
Build ID: xorg-x11-server 1.1.1-48.76.el5_6.4 
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Thu Sep  8 16:41:10 2011
(EE) Unable to locate/open config file
New driver is "i810"
(==) Using default built-in configuration (55 lines)
(EE) open /dev/fb0: No such file or directory
(WW) VESA(0): Failed to set up write-combining range (0x83f00000,0xf0000)
(WW) VESA(0): Failed to set up write-combining range (0x83e00000,0x1f0000)
(WW) VESA(0): Failed to set up write-combining range (0x83c00000,0x3f0000)
(WW) VESA(0): Failed to set up write-combining range (0x83800000,0x7f0000)
(WW) VESA(0): Failed to set up write-combining range (0x83000000,0xff0000)
(WW) VESA(0): Failed to set up write-combining range (0x82000000,0x1ff0000)
(WW) VESA(0): Failed to set up write-combining range (0x80000000,0x3ff0000)
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Multiple symbols for level 1/group 1 on key <I5F>
>                   Using XF86Sleep, ignoring XF86Standby
> Warning:          Symbol map for key <I5F> redefined
>                   Using last definition for conflicting fields
Errors from xkbcomp are not fatal to the X server
localuser:root being added to access control list
No profile for user 'root' found
SESSION_MANAGER=local/lutin.sis.pasteur.fr:/tmp/.ICE-unix/3296

** (eggcups:3375): WARNING **: IPP request failed with status 1030

** (nm-applet:3397): WARNING **: No connections defined

** (nm-applet:3397): WARNING **: Invalid return value type: GPtrArray_DBusGObjectPath_
Initializing nautilus-open-terminal extension


on the console, ctrl+alt+F1 then alt+F7 crashes the desktop
(upper area of the X display is garbled).

Comment 10 Gordon Stocks 2011-09-08 15:05:13 UTC
Interesting. Not quite the same as I see here.

With the default xorg.conf, X is garbled, but you can still tell the mouse pointers is moving - the garbled lines change shade. However without an xorg.conf file, X does start automatically, and function correctly, until you ctrl-alt-f1 -> alt-f7 which doesn't just crash the desktop, it hard hangs the machine (completely unresponsive both locally and remotely) requiring a poweroff/on. In this case I do not get any kind of log output suggesting what the issue actually is.

Glad to know it's not just me that is having issues with this though.

Comment 11 Ron 2011-09-20 17:01:37 UTC
@Gordon:  I have the exact same issue on CentOS 5.6, 5.7 & 6 on the same hardware.
Fedora Core 15 however doesn't have this issue.  It just has others!
We need to somehow escalate this.

Comment 12 RHEL Program Management 2011-09-23 00:39:48 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.

Comment 13 Ron 2011-09-26 18:22:57 UTC
This is a real show stopper for those of us with Optiplex 790s and the intel chipset.  It NEEDS to be fixed in the next release please.

Comment 14 RHEL Program Management 2014-03-07 13:36:41 UTC
This bug/component is not included in scope for RHEL-5.11.0 which is the last RHEL5 minor release. This Bugzilla will soon be CLOSED as WONTFIX (at the end of RHEL5.11 development phase (Apr 22, 2014)). Please contact your account manager or support representative in case you need to escalate this bug.

Comment 15 RHEL Program Management 2014-06-02 13:05:06 UTC
Thank you for submitting this request for inclusion in Red Hat Enterprise Linux 5. We've carefully evaluated the request, but are unable to include it in RHEL5 stream. If the issue is critical for your business, please provide additional business justification through the appropriate support channels (https://access.redhat.com/site/support).


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