| Summary: | [845] -intel produces corrupt display on older chipsets (i845G) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | xorg | Reporter: | Bryce Harrington <bryce> | ||||
| Component: | Driver/intel | Assignee: | Hong Liu <hong.liu> | ||||
| Status: | RESOLVED FIXED | QA Contact: | Xorg Project Team <xorg-team> | ||||
| Severity: | major | ||||||
| Priority: | medium | CC: | jmdorfman, michael.fu | ||||
| Version: | 7.3 (2007.09) | Keywords: | NEEDINFO | ||||
| Hardware: | x86 (IA32) | ||||||
| OS: | Linux (All) | ||||||
| URL: | https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/114331 | ||||||
| Whiteboard: | |||||||
| i915 platform: | i915 features: | ||||||
| Attachments: |
|
||||||
|
Description
Bryce Harrington
2008-01-13 21:35:07 UTC
Can you try with current git tip version? That we originally ignore i830M and 845G pci ids, so some code paths might slip. Created attachment 13980 [details] [review] validate max clock for probed mode From the log, the EDID doesn't set the prefer bit for its detailed mode. So we doesn't choose: (II) intel(0): Modeline "1024x768"x75.1 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz) But the EDID claims support VESA standard 1024x768@75Hz mode: (II) intel(0): Modeline "1024x768"x74.9 82.00 1024 1088 1192 1360 768 771 775 805 -hsync +vsync (60.3 kHz) Which exceeds the maxclock (80Mhz) of this monitor. Please try the attached patch. Thanks, Hong The patch is against X server. Bryce, would you please add the bug repoter to the cc field and introduce him to comment on this bug? thanks. I attempted to add the original reporter's email address to the CC but Bugzilla returned the following error: "Bugzilla was unable to make any match at all for one or more of the names and/or email addresses you entered on the previous page. Please go back and try other names or email addresses. CC: stephen.pountney@tiscali.co.uk did not match anything " I've responded to the Launchpad bug encouraging the reporter to join discussion here. Hello, I have the i830 chipset on my laptop. With Xorg-server version 1.4.0.90, I was getting visual corruption in Xorg. If I would restart Xorg, I would get a black screen with only the mouse pointer visible. Lastly, if I resumed with Tuxonice, the insides of windows would not render. Anyway, when I manually patched xorg-server 1.4.0.90 with the patch that was attached by Hong Liu, my problems appear to be solved! All the above conditions appear to be fixed... If you need any additional info from me to confirm this, please let me know. Cheers, John okay, I do still sometimes get a little corruption at the top of the screen (for top 3 or 4 rows of pixels evenly spaced whitish rectangles appear). it only seems limited to that area which is better than it was before as corruption could appear anywhere on the screen. if i switch desktops and go back, the corruption is gone. my other problems mentioned in the previous post though are fixed. guess i will reopen this as it is not totally fixed. so in summary, much better, but not quite fixed. sigh, okay, I am also still seeing some corruption on other parts of the screen. it appears to be a dark 3 or 4 pixel band that goes across the screen. it is about an 1/8th up from the bottom of the screen and usually goes away when I switch to another desktop and back. John, please pay attention to the bug title. this bug is for 845. bug# 14065 is the one for 830 chipset. We specifically asked Bryce opened two bugs for 845 and 830 platform each. would you please add your finding to bug# 14065? Still need bug reporters' comment on 845, or we have to reject this bug. oops, sorry about that. okay, reposted the previous comments i made on bug 14045. patch is commited to X server (with commit id d3c36fe721edc55636438bc3e0e7a6c03f62784e 4b5b6e7baab58072a983d2ec136965f404c3a74a). I am closing this bug since there is no response from original reporter. Please repoen it if problem still exists. Thanks, Hong |
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.