[Bug 327171] New: Sax2 doesn't let me chose the correct resolution - openSUSE Bugs - openSUSE Mailing Lists

newer
[Bug 327547] New: Translation...

[Bug 327171] New: Sax2 doesn't let me chose the correct resolution

older
[Bug 326653] New: Need to create a...

bugzilla_noreply＠novell.com

21 Sep 2007 21 Sep '07

15:30

https://bugzilla.novell.com/show_bug.cgi?id=327171 Summary: Sax2 doesn't let me chose the correct resolution Product: openSUSE 10.3 Version: RC 1 Platform: i686 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: SaX2 AssignedTo: ms@novell.com ReportedBy: matz@novell.com QAContact: qa@suse.de Found By: --- I just updated from 10.2 to 10.3 RC1. I have a nvidia card, and am (currently) using the 'nv' driver. When I call sax2 (either from text console or from inside X11) it correctly mentions my card ("NVidia GeForce 7600 GT") and monitor ("SGX GDM-5411"), but it gives me only these resolutions to chose from: 800x600 1024x768 1280x1024 1920x1440 2048x1536 For my monitor the good resolution is 1600x1200, which was possible to chose from in the past. I've checked that the monitor sync data is correct (30-121 kHz horz; 50-160 Hz vert). That 2048x1536 is offered also hints to the fact that the monitor should also be capable of showing the smaller 1600x1200 resolution. I wasn't able to fix this problem with board means, so had to hack xorg.conf myself :-/ -- 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.

Reply

Sign in to reply online Use email software

Show replies by date

bugzilla_noreply＠novell.com

24 Sep 24 Sep

08:32

New subject: [Bug 327171] sax2: doesn't let me chose the correct resolution

https://bugzilla.novell.com/show_bug.cgi?id=327171#c1 Marcus Schaefer changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |matz@novell.com Summary|Sax2 doesn't let me chose the correct resolution|sax2: doesn't let me chose the correct | |resolution --- Comment #1 from Marcus Schaefer 2007-09-24 02:32:29 MST --- Hmm, what does sysp -q xstuff tells you ? and what are the contents of /var/log/SaX.log ? 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.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

13:29

New subject: [Bug 327171] sax2: doesn't let me chose the correct resolution

https://bugzilla.novell.com/show_bug.cgi?id=327171#c2 Michael Matz changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|matz@novell.com | --- Comment #2 from Michael Matz 2007-09-24 07:29:39 MST --- Aha, interesting: % sysp -q xstuff Card0 => DDC : SGX0200 Card0 => Name : GDM-5411 Card0 => Vendor : SGX Card0 => Primary : 01-00-0 Card0 => Chipset : <undefined> Card0 => Vsync : 160 Card0 => Hsync : 121 Card0 => Vesa : 800 600 33 56 Card0 => Vesa : 800 600 36 60 Card0 => Vesa : 800 600 43 72 Card0 => Vesa : 800 600 45 75 Card0 => Vesa : 1024 768 66 87 Card0 => Vesa : 1024 768 46 60 Card0 => Vesa : 1024 768 53 70 Card0 => Vesa : 1024 768 57 75 Card0 => Vesa : 1280 1024 76 75 Card0 => Vesa : 1920 1440 108 75 Card0 => Vesa : 2048 1536 115 75 Card0 => Dacspeed : 135 Card0 => Modeline : 1280 1296 1440 1688 1024 1025 1028 1066 +/+ Card0 => Memory : 262144 Card0 => RandR : <undefined> Card0 => Current : 01-00-0 Card0 => RawDef : None Card0 => Option : None Card0 => Extension : None Card0 => Module : nv Card0 => Display : CRT Card0 => Size : 364x291 Card0 => VesaBios : 3.0 Card0 => FBBoot : 800 600 8 771 Card0 => FBBoot : 800 600 16 788 Card0 => FBBoot : 800 600 24 789 Card0 => FBBoot : 1024 768 8 773 Card0 => FBBoot : 1024 768 16 791 Card0 => FBBoot : 1024 768 24 792 Card0 => FBBoot : 1280 1024 8 775 Card0 => FBBoot : 1280 1024 16 794 Card0 => FBBoot : 1280 1024 24 795 Card0 => FBBoot : 1400 1050 8 839 Card0 => FBBoot : 1400 1050 16 840 Card0 => FBBoot : 1600 1200 8 837 Card0 => FBBoot : 1600 1200 16 838 Card0 => FBBoot : 2048 1536 24 850 So sysp thinks that 1600x1200 is no vesa mode. OTOH it also thinks that FBBoot (what is that btw?) includes such a mode. It seems sysp is somehow incomplete. The SaX2.log contains this (only the interesting parts): ------------------ SaX2.log ---------------------- 21-Sep 17:05:14 <X> Startup... 21-Sep 17:05:14 <X> [ Startup on already running Server: :0.0 -> grant ] 21-Sep 17:05:14 <I> Checksum of installed configuration is invalid ! 21-Sep 17:05:14 <I> Imported: Card 21-Sep 17:05:15 <I> Imported: Desktop 21-Sep 17:05:15 <I> Imported: Pointers 21-Sep 17:05:15 <I> Imported: Keyboard 21-Sep 17:05:15 <I> Imported: Layout 21-Sep 17:05:15 <I> Imported: Path 21-Sep 17:05:15 <I> Imported: Extensions 21-Sep 17:05:16 <I> SCCMonitorDisplay::using DDC reference resolutions 21-Sep 17:05:17 <I> SCCMonitorDisplay::resolution 1024x600: NO 21-Sep 17:05:17 <I> SCCMonitorDisplay::resolution 1280x1024: YES 21-Sep 17:05:17 <I> SCCMonitorDisplay::resolution 1024x768: YES 21-Sep 17:05:17 <I> SCCMonitorDisplay::resolution 1900x1200: NO 21-Sep 17:05:17 <I> SCCMonitorDisplay::resolution 1366x768: NO 21-Sep 17:05:17 <I> SCCMonitorDisplay::resolution 1440x900: NO 21-Sep 17:05:17 <I> SCCMonitorDisplay::resolution 1920x1200: NO 21-Sep 17:05:17 <I> SCCMonitorDisplay::resolution 2560x2048: NO 21-Sep 17:05:17 <I> SCCMonitorDisplay::resolution 2560x1600: NO 21-Sep 17:05:17 <I> SCCMonitorDisplay::resolution 1600x1200: NO 21-Sep 17:05:17 <I> SCCMonitorDisplay::resolution 1280x800: NO 21-Sep 17:05:17 <I> SCCMonitorDisplay::resolution 1400x1050: NO 21-Sep 17:05:17 <I> SCCMonitorDisplay::resolution 1280x960: NO 21-Sep 17:05:17 <I> SCCMonitorDisplay::resolution 2048x1536: YES 21-Sep 17:05:17 <I> SCCMonitorDisplay::resolution 1280x600: NO 21-Sep 17:05:17 <I> SCCMonitorDisplay::resolution 1152x864: NO 21-Sep 17:05:17 <I> SCCMonitorDisplay::resolution 768x576: NO 21-Sep 17:05:17 <I> SCCMonitorDisplay::resolution 2800x2100: NO 21-Sep 17:05:17 <I> SCCMonitorDisplay::resolution 1920x1440: YES 21-Sep 17:05:17 <I> SCCMonitorDisplay::resolution 1280x768: NO 21-Sep 17:05:17 <I> SCCMonitorDisplay::resolution 3200x2400: NO 21-Sep 17:05:17 <I> SCCMonitorDisplay::resolution 800x600: YES 21-Sep 17:05:17 <I> SCCMonitorDisplay::resolution 1680x1050: NO 21-Sep 17:05:17 <I> SCCMonitorDisplay::resolution 1600x1000: NO 21-Sep 17:05:17 <I> SCCMonitorDisplay::resolution 640x480: NO 21-Sep 17:05:17 <I> SCCMonitorDisplay::resolution 1600x1024: NO 21-Sep 17:05:17 <W> SCCMonitorDisplay::Warning: res key 1600x1200 is missing 21-Sep 17:05:17 <W> SCCMonitorDisplay::Warning: reset to default 640x480 key 21-Sep 17:05:17 <I> *** not yet handled: Pad Properties on display 0 I assume it doesn't find 1600x1200 because of the sysp problem? Anyway, for cross checking I also did a hwinfo --fr, which does show the video mode I want: % hwinfo --fr 02: None 00.0: 11001 VESA Framebuffer [Created at bios.447] Unique ID: rdCR.pHD5P5+bk68 Hardware Class: framebuffer Model: "NVIDIA G73 Board - p456h7b " Vendor: "NVIDIA Corporation" Device: "G73 Board - p456h7b " SubVendor: "NVIDIA" SubDevice: Revision: "Chip Rev" Memory Size: 256 MB Memory Range: 0xc0000000-0xcfffffff (rw) Mode 0x0300: 640x400 (+640), 8 bits Mode 0x0301: 640x480 (+640), 8 bits Mode 0x0303: 800x600 (+800), 8 bits Mode 0x0305: 1024x768 (+1024), 8 bits Mode 0x0307: 1280x1024 (+1280), 8 bits Mode 0x030e: 320x200 (+640), 16 bits Mode 0x030f: 320x200 (+1280), 24 bits Mode 0x0311: 640x480 (+1280), 16 bits Mode 0x0312: 640x480 (+2560), 24 bits Mode 0x0314: 800x600 (+1600), 16 bits Mode 0x0315: 800x600 (+3200), 24 bits Mode 0x0317: 1024x768 (+2048), 16 bits Mode 0x0318: 1024x768 (+4096), 24 bits Mode 0x031a: 1280x1024 (+2560), 16 bits Mode 0x031b: 1280x1024 (+5120), 24 bits Mode 0x0330: 320x200 (+320), 8 bits Mode 0x0331: 320x400 (+320), 8 bits Mode 0x0332: 320x400 (+640), 16 bits Mode 0x0333: 320x400 (+1280), 24 bits Mode 0x0334: 320x240 (+320), 8 bits Mode 0x0335: 320x240 (+640), 16 bits Mode 0x0336: 320x240 (+1280), 24 bits Mode 0x033d: 640x400 (+1280), 16 bits Mode 0x033e: 640x400 (+2560), 24 bits Mode 0x0345: 1600x1200 (+1600), 8 bits Mode 0x0346: 1600x1200 (+3200), 16 bits Mode 0x0347: 1400x1050 (+1400), 8 bits Mode 0x0348: 1400x1050 (+2800), 16 bits Mode 0x0352: 2048x1536 (+8192), 24 bits Config Status: cfg=new, avail=yes, need=no, active=unknown So, also hwinfo has the 1600x1200 mode only in 8 and 16 bit, although the card is capable of more (and the nv and nvidia driver happily accept also 24 bit), obviously because of incomplete VESA tables. But at least it does contain the mode itself, unlike sysp. -- 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.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

13:32

New subject: [Bug 327171] sax2: doesn't let me chose the correct resolution

https://bugzilla.novell.com/show_bug.cgi?id=327171#c3 --- Comment #3 from Marcus Schaefer 2007-09-24 07:32:17 MST --- The DDC information of your monitor is broken, it doesn't list the 1600x1200 resolution as supported by your monitor *f* monitor I will add the model to our CDB and overwrite the broken data stay tuned -- 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.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

13:40

New subject: [Bug 327171] sax2: doesn't let me chose the correct resolution

https://bugzilla.novell.com/show_bug.cgi?id=327171#c4 Marcus Schaefer changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #4 from Marcus Schaefer 2007-09-24 07:40:53 MST --- fixed -- 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.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

15:50

New subject: [Bug 327171] sax2: doesn't let me chose the correct resolution

https://bugzilla.novell.com/show_bug.cgi?id=327171#c5 --- Comment #5 from Michael Matz 2007-09-24 09:50:52 MST --- I'm not sure if my DDC info really is broken. This is from Xorg.0.log: (--) NV(0): DDC detected a CRT: (II) NV(0): Manufacturer: SGX Model: 200 Serial#: 2419214 (II) NV(0): Year: 2000 Week: 25 (II) NV(0): EDID Version: 1.2 (II) NV(0): Analog Display Input, Input Voltage Level: 0.700/0.300 V (II) NV(0): Sync: Separate Composite SyncOnGreen (II) NV(0): Max H-Image Size [cm]: horiz.: 40 vert.: 30 (II) NV(0): Gamma: 2.50 (II) NV(0): DPMS capabilities: Suspend Off; RGB/Color Display (II) NV(0): redX: 0.625 redY: 0.340 greenX: 0.280 greenY: 0.605 (II) NV(0): blueX: 0.155 blueY: 0.070 whiteX: 0.283 whiteY: 0.298 (II) NV(0): Supported VESA Video Modes: (II) NV(0): 720x400@70Hz (II) NV(0): 720x400@88Hz (II) NV(0): 640x480@60Hz (II) NV(0): 640x480@67Hz (II) NV(0): 640x480@72Hz (II) NV(0): 640x480@75Hz (II) NV(0): 800x600@56Hz (II) NV(0): 800x600@60Hz (II) NV(0): 800x600@72Hz (II) NV(0): 800x600@75Hz (II) NV(0): 832x624@75Hz (II) NV(0): 1024x768@87Hz (interlaced) (II) NV(0): 1024x768@60Hz (II) NV(0): 1024x768@70Hz (II) NV(0): 1024x768@75Hz (II) NV(0): 1280x1024@75Hz (II) NV(0): 1152x870@75Hz (II) NV(0): Manufacturer's mask: 0 (II) NV(0): Supported Future Video Modes: (II) NV(0): #0: hsize: 2048 vsize 1536 refresh: 75 vid: 20449 (II) NV(0): #1: hsize: 1920 vsize 1440 refresh: 75 vid: 20433 (II) NV(0): #2: hsize: 1856 vsize 1392 refresh: 75 vid: 20425 (II) NV(0): #3: hsize: 1800 vsize 1440 refresh: 85 vid: 39362 (II) NV(0): #4: hsize: 1792 vsize 1344 refresh: 75 vid: 20417 (II) NV(0): #5: hsize: 1600 vsize 1200 refresh: 85 vid: 22953 (II) NV(0): #6: hsize: 1280 vsize 1024 refresh: 85 vid: 39297 (II) NV(0): #7: hsize: 1280 vsize 960 refresh: 85 vid: 22913 (II) NV(0): Supported additional Video Mode: (II) NV(0): clock: 135.0 MHz Image Size: 364 x 291 mm (II) NV(0): h_active: 1280 h_sync: 1296 h_sync_end 1440 h_blank_end 1688 h_border: 0 (II) NV(0): v_active: 1024 v_sync: 1025 v_sync_end 1028 v_blanking: 1066 v_border: 0 (II) NV(0): Serial No: 2419214 (II) NV(0): Monitor name: GDM-5411 (II) NV(0): Ranges: V min: 48 V max: 160 Hz, H min: 30 H max: 121 kHz, PixClock max 300 MHz (II) NV(0): EDID (in hex): (II) NV(0): 00ffffffffffff004cf800020eea2400 (II) NV(0): 190a01020e281e96680cc9a057479b27 (II) NV(0): 12484cffff80e14fd14fc94fc299c14f (II) NV(0): a95981998159bc34009851002a401090 (II) NV(0): 13006c231100001e000000ff00323431 (II) NV(0): 393231340a2020202020000000fc0047 (II) NV(0): 444d2d353431310a20202020000000fd (II) NV(0): 0030a01e791e000a2020202020200004 So, there's a 1600x1200 in there just fine. The Xorg.0.log also continues with: (II) NV(0): Printing DDC gathered Modelines: ... (II) NV(0): Modeline "1600x1200" 235.00 1600 1728 1896 2192 1200 1203 1207 1262 -hsync +vsync So it seem DDC does provide it somehow, but isn't parsed by sysp? -- 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.

Reply

Sign in to reply online Use email software

6070

Age (days ago)

6073

Last active (days ago)

Download

5 comments

1 participants

tags

participants (1)

bugzilla_noreply＠novell.com