[Bug 553822] New: Video mode not initialized correctly on intel 945 GM with external display.
http://bugzilla.novell.com/show_bug.cgi?id=553822 Summary: Video mode not initialized correctly on intel 945 GM with external display. Classification: openSUSE Product: openSUSE 11.2 Version: RC 2 Platform: i686 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: X.Org AssignedTo: bnc-team-xorg-bugs@forge.provo.novell.com ReportedBy: sbron@wanadoo.nl QAContact: xorg-maintainer-bugs@forge.provo.novell.com Found By: --- Created an attachment (id=326284) --> (http://bugzilla.novell.com/attachment.cgi?id=326284) Xorg log file User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.4) Gecko/20091016 SUSE/3.5.4-1.1.2 Firefox/3.5.4 When I boot my laptop while it is sitting in its docking station with an external monitor connected, the display on the external monitor is correct until the login screen appears. At that time the monitor complains that the input is out of range and after a few seconds it goes to sleep. The problem remains when I login. With some earlier SuSE version the situation could be remedied by using the i810 driver (I think) instead of the intel driver. On OpenSuSE 11.1 the i810 driver was no longer available, so I added the command "xrandr --output VGA --auto" to .xinitrc, which would restore the correct video mode during login. The xrandr work-around is no longer satisfactory on 11.2, because now the mouse pointer is invisible after I login. It can sometimes be revealed by running some xrandr --output LVDS --off or --auto commands. If that fails I switch to a text screen (Ctrl-Alt-F1) and back to graphics (Ctrl-Alt-F7) to get the cursor back. Reproducible: Always Steps to Reproduce: 1. Boot the PC, or restart X 2. Wait for the KDM login screen Actual Results: Monitor briefly shows a distorted image (part of the login screen is visible in the top right-hand part of the screen) and indicates the input is out of range. After a few seconds the monitor goes to sleep. Expected Results: Login screen should be displayed in 1280x1024 60Hz mode. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=553822
User sbron@wanadoo.nl added comment
http://bugzilla.novell.com/show_bug.cgi?id=553822#c1
--- Comment #1 from Schelte Bron
http://bugzilla.novell.com/show_bug.cgi?id=553822
User sbron@wanadoo.nl added comment
http://bugzilla.novell.com/show_bug.cgi?id=553822#c2
--- Comment #2 from Schelte Bron
http://bugzilla.novell.com/show_bug.cgi?id=553822
User sbron@wanadoo.nl added comment
http://bugzilla.novell.com/show_bug.cgi?id=553822#c3
--- Comment #3 from Schelte Bron
http://bugzilla.novell.com/show_bug.cgi?id=553822
User sbron@wanadoo.nl added comment
http://bugzilla.novell.com/show_bug.cgi?id=553822#c4
--- Comment #4 from Schelte Bron
http://bugzilla.novell.com/show_bug.cgi?id=553822
User sndirsch@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=553822#c5
Stefan Dirsch
http://bugzilla.novell.com/show_bug.cgi?id=553822
Stefan Dirsch
http://bugzilla.novell.com/show_bug.cgi?id=553822
User sbron@wanadoo.nl added comment
http://bugzilla.novell.com/show_bug.cgi?id=553822#c6
Schelte Bron
http://bugzilla.novell.com/show_bug.cgi?id=553822
User sndirsch@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=553822#c7
Stefan Dirsch
Created an attachment (id=326286) --> (http://bugzilla.novell.com/attachment.cgi?id=326286) [details] Output of: hwinfo --gfxcard --monitor
Looks like no monitor is detected via DDC. So you would need a rather tricky xorg.conf for a dualhead setup. But I think SaX2 can still create a xorg.conf file for such a configuration. The idea is to create a clone mode configuration in SaX2. Let me know if that works. And attach new /etc/X11/xorg.conf. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=553822
User sbron@wanadoo.nl added comment
http://bugzilla.novell.com/show_bug.cgi?id=553822#c8
--- Comment #8 from Schelte Bron
http://bugzilla.novell.com/show_bug.cgi?id=553822
User sndirsch@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=553822#c9
--- Comment #9 from Stefan Dirsch
http://bugzilla.novell.com/show_bug.cgi?id=553822
User sbron@wanadoo.nl added comment
http://bugzilla.novell.com/show_bug.cgi?id=553822#c10
--- Comment #10 from Schelte Bron
http://bugzilla.novell.com/show_bug.cgi?id=553822
User sbron@wanadoo.nl added comment
http://bugzilla.novell.com/show_bug.cgi?id=553822#c11
Schelte Bron
http://bugzilla.novell.com/show_bug.cgi?id=553822
User sndirsch@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=553822#c12
Stefan Dirsch
Removed the ModeLine lines from xorg.conf with the same result.
Note: Originally the problem happened without any xorg.conf file at all.
Could you attach /var/log/Xorg.0.log for this setup? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=553822
User sbron@wanadoo.nl added comment
http://bugzilla.novell.com/show_bug.cgi?id=553822#c13
Schelte Bron
http://bugzilla.novell.com/show_bug.cgi?id=553822
User sndirsch@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=553822#c14
Stefan Dirsch
http://bugzilla.novell.com/show_bug.cgi?id=553822
User sbron@wanadoo.nl added comment
http://bugzilla.novell.com/show_bug.cgi?id=553822#c15
--- Comment #15 from Schelte Bron
http://bugzilla.novell.com/show_bug.cgi?id=553822
User sndirsch@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=553822#c16
--- Comment #16 from Stefan Dirsch
http://bugzilla.novell.com/show_bug.cgi?id=553822
User sbron@wanadoo.nl added comment
http://bugzilla.novell.com/show_bug.cgi?id=553822#c17
--- Comment #17 from Schelte Bron
http://bugzilla.novell.com/show_bug.cgi?id=553822
User sbron@wanadoo.nl added comment
http://bugzilla.novell.com/show_bug.cgi?id=553822#c18
--- Comment #18 from Schelte Bron
http://bugzilla.novell.com/show_bug.cgi?id=553822
User sbron@wanadoo.nl added comment
http://bugzilla.novell.com/show_bug.cgi?id=553822#c19
--- Comment #19 from Schelte Bron
http://bugzilla.novell.com/show_bug.cgi?id=553822
User sbron@wanadoo.nl added comment
http://bugzilla.novell.com/show_bug.cgi?id=553822#c20
--- Comment #20 from Schelte Bron
http://bugzilla.novell.com/show_bug.cgi?id=553822
User sbron@wanadoo.nl added comment
http://bugzilla.novell.com/show_bug.cgi?id=553822#c21
--- Comment #21 from Schelte Bron
http://bugzilla.novell.com/show_bug.cgi?id=553822
User sbron@wanadoo.nl added comment
http://bugzilla.novell.com/show_bug.cgi?id=553822#c22
--- Comment #22 from Schelte Bron
http://bugzilla.novell.com/show_bug.cgi?id=553822
User sbron@wanadoo.nl added comment
http://bugzilla.novell.com/show_bug.cgi?id=553822#c23
--- Comment #23 from Schelte Bron
http://bugzilla.novell.com/show_bug.cgi?id=553822
User sndirsch@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=553822#c24
--- Comment #24 from Stefan Dirsch
I can switch to 1280x1024 and that gives the correct display (same as when I run xrandr --output VGA --auto). With the distorted display, the monitor claim the input is H=47.6kHz V=60Hz, so again not what the logfile indicates.
I can find various modes for 1024x768 in the logfile using 50, 60, 70 and 75 Hz. According to xrandr the one for 75Hz is used. I wouldn't trust what the monitor itself displays via the OSD. But why don't you limit it to 60 Hz as I suggested before?
As the suspicion was a broken monitor, I borrowed another monitor (Dell 1905FP). Although this monitor is capable of showing the login screen, it is not at the preferred resolution of 1280x1024 either.
I already explained above (comment #16) why this isn't done in mirror mode.
The monitor reports it is 1280x768 60Hz, contrary to what xrandr reports (1024x768_60).
I wouldn't trust the OSD of this monitor either.
The same figures were reported by the monitor with or without the attached xorg.conf file.
As already mentioned above. Limit the range for vertical frequency to 60 Hz.
With the dell monitor I could briefly see a graphics screen with a watch cursor before the login screen appears. I have the strong impression that this intermediate screen is displayed at the correct resolution.
Sounds like wild guessing.
Does kdm have some configuration settings that perhaps override the auto detected modes?
I don't know. I'm not an KDE expert. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=553822
User sndirsch@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=553822#c25
--- Comment #25 from Stefan Dirsch
http://bugzilla.novell.com/show_bug.cgi?id=553822
User sbron@wanadoo.nl added comment
http://bugzilla.novell.com/show_bug.cgi?id=553822#c26
--- Comment #26 from Schelte Bron
http://bugzilla.novell.com/show_bug.cgi?id=553822
User sndirsch@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=553822#c27
--- Comment #27 from Stefan Dirsch
http://bugzilla.novell.com/show_bug.cgi?id=553822
User sbron@wanadoo.nl added comment
http://bugzilla.novell.com/show_bug.cgi?id=553822#c28
--- Comment #28 from Schelte Bron
http://bugzilla.novell.com/show_bug.cgi?id=553822
User sndirsch@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=553822#c29
--- Comment #29 from Stefan Dirsch
I will collect the logs for the 59-61 case tomorrow.
Thanks.
One more thing I'm not sure you are aware of: The graphical screens that are being displayed during the boot process show up perfectly.
This is the kernel framebuffer + splash screen. Unrelated to X.Org (driver).
Also, when I had this problem before with SuSE 11.1 I think I tried the vesa driver. As I remember that also fixed this problem. Would it be helpful to try that setup again?
The vesa driver is rather slow - compared to the intel driver with 2D/3D support. I don't think you want to use vesa if you can avoid it. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=553822
User sbron@wanadoo.nl added comment
http://bugzilla.novell.com/show_bug.cgi?id=553822#c30
--- Comment #30 from Schelte Bron
http://bugzilla.novell.com/show_bug.cgi?id=553822
User sbron@wanadoo.nl added comment
http://bugzilla.novell.com/show_bug.cgi?id=553822#c31
--- Comment #31 from Schelte Bron
http://bugzilla.novell.com/show_bug.cgi?id=553822
User sbron@wanadoo.nl added comment
http://bugzilla.novell.com/show_bug.cgi?id=553822#c32
--- Comment #32 from Schelte Bron
http://bugzilla.novell.com/show_bug.cgi?id=553822
User sbron@wanadoo.nl added comment
http://bugzilla.novell.com/show_bug.cgi?id=553822#c33
--- Comment #33 from Schelte Bron
http://bugzilla.novell.com/show_bug.cgi?id=553822
User sbron@wanadoo.nl added comment
http://bugzilla.novell.com/show_bug.cgi?id=553822#c34
--- Comment #34 from Schelte Bron
http://bugzilla.novell.com/show_bug.cgi?id=553822
User sndirsch@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=553822#c35
--- Comment #35 from Stefan Dirsch
Created an attachment (id=326743) --> (http://bugzilla.novell.com/attachment.cgi?id=326743) [details] Output of xrandr with VertRefresh 59-61
Looks much better! All resolutions use 60Hz now. 1280 marked as native resolution (+) and 1024x768 marked as the current resolution (for the reasons given above). (In reply to comment #33)
Created an attachment (id=326745) --> (http://bugzilla.novell.com/attachment.cgi?id=326745) [details] Output of xrandr using vesa driver
This might give you the native resolution by default on the external screen. But since vesa driver cannot support RANDR 1.2 I seriously doubt that you get also the native resolution on the LCD panel, if anything at all. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=553822
User sndirsch@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=553822#c36
--- Comment #36 from Stefan Dirsch
http://bugzilla.novell.com/show_bug.cgi?id=553822
User sbron@wanadoo.nl added comment
http://bugzilla.novell.com/show_bug.cgi?id=553822#c37
--- Comment #37 from Schelte Bron
But since vesa driver cannot support RANDR 1.2 I seriously doubt that you get also the native resolution on the LCD panel, if anything at all.
I am not really interested in using both screens at the same time. But when the laptop is in its docking station I want to use the 1280x1024 on the external screen. Also, I just wanted to use the vesa driver as a data point to prove the problem is in the intel driver. (In reply to comment #36)
Why don't you configure your external monitor in KDE with a resolution of 1280x1024, so everything is fine after login?
As I indicated in the initial description, that is the work-around I have been using. But it is a work around. The misbehaving login screen keeps me from doing things like selecting the session type (not to mention the criticism I get from win users when they see the login screen). So, when I found that the problem still had not been fixed in 11.2 I decided to report the bug. But I respect your opinion that the bug isn't worth fixing and I'll continue to use the work-around. Thank you for your assistance. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=553822
User sndirsch@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=553822#c38
Stefan Dirsch
http://bugzilla.novell.com/show_bug.cgi?id=553822
http://bugzilla.novell.com/show_bug.cgi?id=553822#c39
--- Comment #39 from Schelte Bron
participants (1)
-
bugzilla_noreply@novell.com