This is Dell Latitude D610 laptop. 01:00.0 VGA compatible controller: ATI Technologies Inc M22 [Radeon Mobility M300] (prog-if 00 [VGA]) Subsystem: Dell Unknown device 2006 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 0, Cache Line Size 10 Interrupt: pin A routed to IRQ 16 Region 0: Memory at d0000000 (32-bit, prefetchable) [size=128M] Region 1: I/O ports at de00 [size=256] Region 2: Memory at dfdf0000 (32-bit, non-prefetchable) [size=64K] [virtual] Expansion ROM at dfd00000 [disabled] [size=128K] Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Capabilities: [58] Express Endpoint IRQ 0 Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag+ Device: Latency L0s <256ns, L1 <4us Device: AtnBtn- AtnInd- PwrInd- Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported- Device: RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+ Device: MaxPayload 128 bytes, MaxReadReq 128 bytes Link: Supported Speed 2.5Gb/s, Width x16, ASPM L0s L1, Port 0 Link: Latency L0s <256ns, L1 <2us Link: ASPM L1 Enabled RCB 64 bytes CommClk+ ExtSynch- Link: Speed 2.5Gb/s, Width x16 Capabilities: [80] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable- Address: 0000000000000000 Data: 0000 Capabilities: [100] Advanced Error Reporting
Created attachment 4496 [details] Screenshot of the screen garbage. This is the image of the garbled screen of the 1400x1050 mode.
Please attach X server config and log files.
Created attachment 4513 [details] Xorg.0.log
Created attachment 4514 [details] xorg.conf My xorg.conf which was originally generated by fglrxconfig for ATI proprietary drivers, later I added the driver section for open source driver and made it active.
Thanks, but the files would be more useful if they were from a 1400x1050 run. FWIW, does the problem persist if you don't enable the DRI? What if you use Option "AccelMethod" "EXA"?
Hm.. when I start Xorg by default with 1400x1050 mode, everything works fine. When starting with 1280x1024 resolution and then using gnome-display-properties for switching, it doesn't work as expected.
Created attachment 4919 [details] Xorg.0.log with XAA, DRI DRI enabled, accelmode is default (xaa) xdm starts 1280x768, when logging in, screen is switched to 1400x1050 mode This results: * ~100 pixels of garbage in both sides of display * cursor is not displayed correctly. It is shown as a white rectangle
Created attachment 4920 [details] Xorg.0.log with EXA, DRI DRI enabled, accelmode is default (xaa) gdm starts 1280x1024 (typo in previous comment), after I have logged in, screen is switched to 1400x1050 mode. This results: * ~100 pixels of garbage in both sides of display
Created attachment 4921 [details] Xorg.0.log with XAA, no DRI DRI disabled, accelmode is default (xaa) xdm starts 1280x1024 after when logging in screen is switched to 1400x1050 mode This results: * ~100 pixels of garbage in both sides of display * cursor is not displayed correctly. It is shown as a white rectangle * also there seems to be ~26 pixel corruption in the bottom of the screen also
Created attachment 4922 [details] Xorg.0.log with EXA, no DRI xdm starts 1280x1024 after when logging in screen is switched to 1400x1050 mode This results: * ~100 pixels of garbage in both sides of display * cursor is not displayed correctly. It is shown as a white rectangle * there is ~26 pixel corruption in the bottom of the screen
Also, the display hung (not sure about the machine) on logout when DRI was enabled. All these tests were performed after reboot.
Created attachment 4923 [details] Xorg.0.log with EXA and DRI on 1400x1050 mode only 1400x1050 mode only, switching doesn't change anything.
Marking broken (status null/blank) bugs in xorg with no activity in a long time as fixed. Please reopen if you think it's necessary, but first do a search if a similar bug report is already filed and in a NEW/ASSIGNED state. These bugs do not currently show in most search results as they do not have any status. Sorry for this janitorial spam, you know where to send hate mails to when your inbox gets full of bugs you're subscribed to.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.