[Bug 213630] New: Wrong DisplaySize in xorg.conf
https://bugzilla.novell.com/show_bug.cgi?id=213630 Summary: Wrong DisplaySize in xorg.conf Product: openSUSE 10.2 Version: Alpha 5 plus Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: SaX2 AssignedTo: ms@novell.com ReportedBy: sndirsch@novell.com QAContact: qa@suse.de SaX2 detects a wrong DisplaySize DisplaySize 16 16 for a 17" 1280x1024 Display and therefore the font size in gdm and afterwards in the GNOME session is comletely bogus. This can be reproduced on d170, which has been installed with Alpha5+. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=213630 ms@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |sndirsch@novell.com ------- Comment #1 from ms@novell.com 2006-10-20 02:30 MST ------- what does hwinfo --monitor print ? Thanks -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=213630 sndirsch@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|sndirsch@novell.com | ------- Comment #2 from sndirsch@novell.com 2006-10-20 02:36 MST ------- d170:~ # hwinfo --monitor 33: None 00.0: 10000 Monitor [Created at fb.71] Unique ID: rdCR.EY_qmtb9YY0 Hardware Class: monitor Model: "Generic Monitor" Vendor: "Generic" Device: "Monitor" Resolution: 1280x1024@77Hz Driver Info #0: Max. Resolution: 1280x1024 Vert. Sync Range: 50-90 Hz Hor. Sync Range: 31-82 kHz Config Status: cfg=new, avail=yes, need=no, active=unknown BTW, I made sure that no Xserver is running and monitor is turned on. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=213630 ms@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |sndirsch@novell.com ------- Comment #3 from ms@novell.com 2006-10-20 02:38 MST ------- no this is a generic entry you got if you call it from within runlevel 5 please call it without any X running. Thanks -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=213630 sndirsch@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|sndirsch@novell.com | ------- Comment #4 from sndirsch@novell.com 2006-10-20 02:43 MST ------- Unfortunately you're wrong here. Check yourself on d170. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=213630 ms@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |sndirsch@novell.com ------- Comment #5 from ms@novell.com 2006-10-20 02:58 MST ------- I'm pretty sure I'm not wrong :) I cannot reproduce this issue on d170. I saw the old sysp output which is: /usr/sbin/sysp -q xstuff Card0 => DDC : <undefined> Card0 => Name : Monitor Card0 => Vendor : Generic Card0 => Primary : 00-02-0 Card0 => Chipset : <undefined> Card0 => Vsync : 61 Card0 => Hsync : 63 Card0 => Vesa : 1280 1024 62 60 Card0 => FbTiming : "1280x1024" 102.62 1280 1312 1472 1632 1024 1028 1032 1048 -HSync -VSync Card0 => Dacspeed : 220 Card0 => Modeline : <undefined> Card0 => Memory : 7872 Card0 => Current : 00-02-0 Card0 => RawDef : None Card0 => Option : None Card0 => Extension : None Card0 => Module : i810 Card0 => Display : CRT Card0 => Size : 16x16 Card0 => VesaBios : 3.0 and the new one you got if you call it now: /usr/sbin/sysp -s xstuff Card0 => DDC : <undefined> Card0 => Name : Monitor Card0 => Vendor : Generic Card0 => Primary : 00-02-0 Card0 => Chipset : <undefined> Card0 => Vsync : 61 Card0 => Hsync : 63 Card0 => Vesa : 1280 1024 62 60 Card0 => FbTiming : "1280x1024" 102.62 1280 1312 1472 1632 1024 1028 1032 1048 -HSync -VSync Card0 => Dacspeed : 220 Card0 => Modeline : <undefined> Card0 => Memory : 4096 Card0 => Current : 00-02-0 Card0 => RawDef : None Card0 => Option : None Card0 => Extension : None Card0 => Module : i810 Card0 => Display : CRT Card0 => VesaBios : <undefined> as you can see the VesaBios couldn't be accessed therefore no size information exists. The time before the vesa BIOS was v3.0 and reports wrong size values. And what great graphics chip is this... Intel just call sax2 -r now on d170 and I ensure it will work ;) By the way. The call to XOpenDisplay() on our current systems never returns if there is no X-Server running. This happens on Intel chips only. Have you already heard about it ? I think yes because Andreas Grünbacher told me that you already know it -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=213630 sndirsch@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mhopf@novell.com, eich@novell.com Status|NEEDINFO |ASSIGNED Info Provider|sndirsch@novell.com | ------- Comment #6 from sndirsch@novell.com 2006-10-20 03:20 MST ------- Oh well. Sometimes with new X.Org 7/i810 driver (not sure who is responsible for this) you need to reboot the machine, because VBIOS is no longer accessible. Look for (II) I810(0): initializing int10 (EE) I810(0): V_BIOS address 0x7d8e0 out of range (EE) I810(0): VBE initialization failed. in the logfile. This seems to be a new "feature". :-( After booting you can sometimes reproduce the "DisplaySize 16 16" issue, sometimes you can't, but only with "sax2 -a -r", not with "/usr/sbin/sysp -s xstuff" - for whatever reasons. I also saw the "DisplaySize 80 40" instead in the xorg.conf file.
By the way. The call to XOpenDisplay() on our current systems never returns if there is no X-Server running. This happens on Intel chips only. Have you already heard about it ? I think yes because Andreas Grünbacher told me that you already know it
No, I didn't. Sounds weird. Probably this are all Xserver/driver bugs, although I have no idea how to fix them. :-( -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=213630 sndirsch@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sndirsch@novell.com AssignedTo|ms@novell.com |snwint@novell.com Status|ASSIGNED |NEW ------- Comment #7 from sndirsch@novell.com 2006-10-20 05:03 MST ------- I suggest to a validation check for x/y values < 100. At least this would help for "16x16" and "80x40". Reassigning to Steffen. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=213630 snwint@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Comment #8 from snwint@novell.com 2006-10-20 05:45 MST ------- Ok, added check for >= 100. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=213630 ------- Comment #9 from sndirsch@novell.com 2006-10-20 06:19 MST ------- Thanks. It might make more sense to check for reasonable values of dpi (50 < x < 200) instead. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=213630 ------- Comment #10 from snwint@novell.com 2006-10-20 07:37 MST ------- As an additional check, maybe. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
participants (1)
-
bugzilla_noreply@novell.com