[Bug 411723] New: vesa driver cannot be reconfigured to another refresh rate that the standard
https://bugzilla.novell.com/show_bug.cgi?id=411723 Summary: vesa driver cannot be reconfigured to another refresh rate that the standard Product: openSUSE 10.3 Version: Final Platform: i586 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: X.Org AssignedTo: sndirsch@novell.com ReportedBy: uga@domestic.de QAContact: xorg-maintainer-bugs@forge.provo.novell.com Found By: --- Sorry, because issue 411446 was so quickly closed I must open a new one because 411446 was originally not only related to the s3 driver. Because of the problem with the s3 driver I wanted to configure the vesa driver with another refresh rate than the default. With sax2 -m 0=vesa I got a default configuration with 60 Hz, was able to start Gnome and SaX2. SaX2 provided a list of several modi and let me select the modus 800x600@85. But after a reboot the monitor flickers as much as before. xorg.conf shows no Modeline and the ModelName "800X600@60HZ": Section "Monitor" HorizSync 20-61 Identifier "Monitor[0]" ModelName "800X600@60HZ" Option "DPMS" VendorName "--> VESA" VertRefresh 50-85 EndSection Section "Device" BoardName "Trio 64V2/DX or /GX" BusID "0:15:0" Driver "vesa" Identifier "Device[0]" VendorName "S3" EndSection Section "Screen" DefaultDepth 16 SubSection "Display" Depth 15 Modes "800x600" EndSubSection SubSection "Display" Depth 16 Modes "800x600" EndSubSection SubSection "Display" Depth 24 Modes "800x600" EndSubSection SubSection "Display" Depth 8 Modes "800x600" EndSubSection Device "Device[0]" Identifier "Screen[0]" Monitor "Monitor[0]" EndSection hwinfo --monitor shows: Resolution: 800x600@75Hz xrandr shows: 800x600 84.0* 640x480 85.0 640x400 86.0 I also tried sax2 -m 0=vesa --vesa 0:800x600@75 and sax2 -m 0=vesa --vesa 0:800x600@85 but always got the same Modeline (with this command sax2 generates one in xorg.conf, but always the same). With sax2 -x -m 0=vesa --vesa 0:800x600@75 no Modeline was generated. In all cases I see the same 60 Hz flickering. Although my monitor is a legacy model I want to be able to configure monitors operated by openSUSE with all possible settings. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=411723 User sndirsch@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=411723#c1 Stefan Dirsch <sndirsch@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |uga@domestic.de --- Comment #1 from Stefan Dirsch <sndirsch@novell.com> 2008-07-23 23:15:14 MDT --- Please attach your /var/log/Xorg.0.log with vesa driver configured, so I can see and explain to you which modes are available. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=411723 User uga@domestic.de added comment https://bugzilla.novell.com/show_bug.cgi?id=411723#c2 Uwe Galle <uga@domestic.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|uga@domestic.de | --- Comment #2 from Uwe Galle <uga@domestic.de> 2008-07-24 15:14:38 MDT --- Created an attachment (id=229881) --> (https://bugzilla.novell.com/attachment.cgi?id=229881) Xorg.0.log with vesa driver -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=411723 User uga@domestic.de added comment https://bugzilla.novell.com/show_bug.cgi?id=411723#c3 --- Comment #3 from Uwe Galle <uga@domestic.de> 2008-07-24 15:15:32 MDT --- Sorry for the delay, there was a problem with bugzilla today. I attach the requested log. Hopefully the modes in the log will help me. But I want also to remark that even in that case it should always be a bug if a configuration utility like SaX2 offers setting values what cannot be used. It is not understandable and very frustrating if you select a setting and this setting has no effect. And this is definitely the case with SaX2. This should be changed. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=411723 User sndirsch@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=411723#c4 Stefan Dirsch <sndirsch@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|sndirsch@novell.com |lverhaegen@novell.com --- Comment #4 from Stefan Dirsch <sndirsch@novell.com> 2008-07-24 21:20:10 MDT --- Uwe, what you were selecting in SaX2 was the monitor model, which means that you think your monitor is capable of displaying a mode 800x600@75Hz. If the card + driver can do this is a different question. I'm no longer sure what the vesa driver can do and does here. For me it seems it choses a 84Hz mode. But why does it flicker then? (II) VESA(0): Printing DDC gathered Modelines: [...] (II) VESA(0): Modeline "800x600" 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync [...] (II) VESA(0): Searching for matching VESA mode(s): (--) VESA(0): Virtual size is 800x600 (pitch 800) (**) VESA(0): *Built-in mode "800x600" [...] (II) VESA(0): Attempting to use 84Hz refresh for mode "800x600" (114) Maybe this fails ... Reassigning to a person, who is more familar with modesetting, VESA BIOS and vesa driver. I'm wondering why you still don't consider to replace your graphics card ... -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=411723 Stefan Dirsch <sndirsch@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sndirsch@novell.com Summary|vesa driver cannot be reconfigured to another |vesa: driver cannot be configured to use a |refresh rate that the standard |specific refresh rate -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=411723 User uga@domestic.de added comment https://bugzilla.novell.com/show_bug.cgi?id=411723#c5 --- Comment #5 from Uwe Galle <uga@domestic.de> 2008-07-25 05:39:26 MDT --- Generally I can live with this problem and I want to have a working vesa driver for similar situations in the future ... Generally it must simply be possible to invoke a configuration tool, change the refresh rate and that's it. Such complications must be removed. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=411723 User sndirsch@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=411723#c6 --- Comment #6 from Stefan Dirsch <sndirsch@novell.com> 2008-07-25 06:28:07 MDT --- Unfortunately you can't circumvent a limitation of a driver and the card's VBIOS with some config tool. What you want would be a working s3 driver. We don't have this any longer for your S3 card. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=411723 User uga@domestic.de added comment https://bugzilla.novell.com/show_bug.cgi?id=411723#c7 --- Comment #7 from Uwe Galle <uga@domestic.de> 2008-07-25 07:27:49 MDT --- If there is a limitation of a driver or of a VBIOS on a card or on board controller the configuaration tool must recognize that and cannot offer settings what cannot be used. The main problem is the inconsistency between the offered settings and the missings effects of these settings. And do you know that for sure that there is a limitation of the VBIOS? On that system was running Windows previously - of course with a working Windows driver - without any problems. If a driver was able to operate the on board controller with the desired mode the VBIOS should be able to do the same. I don't think that there is a VBIOS limitation. I believe that there is a OS problem. Unfortunately hwinfo --gfxcard displays not enough information for me to decide if there is a VBIOS limitation: 15: PCI 0f.0: 0300 VGA compatible controller (VGA) [Created at pci.301] UDI: /org/freedesktop/Hal/devices/pci_5333_8901 Unique ID: _+Pw.zRTkGjKA2qF SysFS ID: /devices/pci0000:00/0000:00:0f.0 SysFS BusID: 0000:00:0f.0 Hardware Class: graphics card Model: "S3 86C775 Trio64V2/DX, 86C785 Trio64V2/GX" Vendor: pci 0x5333 "S3 Inc." Device: pci 0x8901 "Trio 64V2/DX or /GX" SubVendor: pci 0x5333 "S3 Inc." SubDevice: pci 0x8901 "86C775 Trio64V2/DX, 86C785 Trio64V2/GX" Revision: 0x16 Memory Range: 0xf8000000-0xfbffffff (rw,non-prefetchable) Memory Range: 0x70100000-0x7010ffff (ro,prefetchable,disabled) IRQ: 18 (15 events) I/O Ports: 0x3c0-0x3df (rw) Module Alias: "pci:v00005333d00008901sv00005333sd00008901bc03sc00i00" Driver Info #0: XFree86 v4 Server Module: s3 Config Status: cfg=no, avail=yes, need=no, active=unknown Primary display adapter: #15 If you know a tool or method to detect a possible limitation of the VBIOS let me know that, please. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=411723 User sndirsch@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=411723#c8 --- Comment #8 from Stefan Dirsch <sndirsch@novell.com> 2008-07-25 07:35:38 MDT --- Again, with SaX2 you configured the refresh ranges of your monitor, not the refresh rate which is later used by the driver. You would not run into these issues with the s3 driver, since it's no limited to the modes, which are provided by the card's BIOS, whereas the vesa driver is. I need to give up at this point trying to explain this. Maybe Luc can explain it better than me. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=411723 User lverhaegen@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=411723#c10 Luc Verhaegen <lverhaegen@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #10 from Luc Verhaegen <lverhaegen@novell.com> 2008-09-03 04:34:47 MDT --- Urgh. What stops you from editing xorg.conf directly? Why are you not specifying the monitor range as such: VertRefresh 50-80 At which point every driver will ditch modes with a vertical refresh higher than 80, including the 85Hz you wanted to get rid of. There will be at least 56Hz, whether you get 60 or 75 all depends on the bios. This is the only real way to force the VESA driver to limit its choice of modes. Yes, the vesa driver is not perfect, it could be more intelligent, it definitely could be a lot more verbose, but then, vesa is a fallback only. And the S3 driver is not something any overloaded developer will spend a lot of time on 13 years later. And _YES_, if you are using vesa, the limits are entirely in the VBIOS. And _YES_, anyone who knows anything about vesa knows this as well. -- 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.
participants (1)
-
bugzilla_noreply＠novell.com