RE: [suse-xfree86] Latest drivers from ATI on SuSE 9.3 / version 8.25.18
Matthias Hopf wrote on Friday, May 26, 2006 12:03 PM::
On May 26, 06 02:22:22 +0200, Dieter Jurzitza wrote:
402 MHz is a little bit too much for my poor monitor (carefully speaking). So, ATI-developers, there is still some work to be done!
Anlog monitors don't have an upper limit for dot clocks. They have a bandwidth that describes with which frequency the signal will start degrading. No hard limit.
I was about to make the same point myself, however, I think there is still a problem with the modeline generated by sax2. 401.86 MHz / 2240 = 179.4 kHz horizontal frequency 179.4 kHz / 1300 = 138 Hz vertical refresh rate These frequencies are high for most, if not all, monitors. It strikes me that the dot clock is out by a factor of 2. Halving it would bring the frequencies well within scope of the monitor mentioned (which is claimed to support 160 Hz vertical and 121 kHz horizontal and resolutions up to 1800x1440). Phil -- ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the H.E Information Systems Ltd. Tel: 0161 866 9066 Web: www.heis.co.uk This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. www.clearswift.com **********************************************************************
On May 26, 06 13:24:46 +0100, Phil Betts wrote:
Matthias Hopf wrote on Friday, May 26, 2006 12:03 PM::
On May 26, 06 02:22:22 +0200, Dieter Jurzitza wrote:
402 MHz is a little bit too much for my poor monitor (carefully speaking). So, ATI-developers, there is still some work to be done!
Anlog monitors don't have an upper limit for dot clocks. They have a bandwidth that describes with which frequency the signal will start degrading. No hard limit.
I was about to make the same point myself, however, I think there is still a problem with the modeline generated by sax2.
401.86 MHz / 2240 = 179.4 kHz horizontal frequency 179.4 kHz / 1300 = 138 Hz vertical refresh rate
These frequencies are high for most, if not all, monitors.
You were talking about 9.3. This is pretty old. Or did you update the sax2 packages to current ones? I doubt they will install and run cleanly on 9.3. CU Matthias -- Matthias Hopf <mhopf@suse.de> __ __ __ Maxfeldstr. 5 / 90409 Nuernberg (_ | | (_ |__ mat@mshopf.de Phone +49-911-74053-715 __) |_| __) |__ labs www.mshopf.de
Dear listmembers, hi Matthias, this part has been a sax-bug since ever? Ok, I can live with that - will have to, anyway. I only wonder why you didn't mention that when I first reported this about a half a year ago - at that time there had had been time for a bugfix. The question is, is this actually a sax-bug or is this a bug of the monitor specification that results in erratic modelines? Thanks and take care Dieter Am Freitag, 26. Mai 2006 15:31 schrieb Matthias Hopf:
On May 26, 06 13:24:46 +0100, Phil Betts wrote:
Matthias Hopf wrote on Friday, May 26, 2006 12:03 PM::
-- ----------------------------------------------------------- | \ /\_/\ | | ~x~ |/-----\ / \ /- \_/ ^^__ _ / _ ____ / <°°__ \- \_/ | |/ | | || || _| _| _| _| if you really want to see the pictures above - use some font with constant spacing like courier! :-) -----------------------------------------------------------
Dieter, On May 26, 06 18:42:36 +0200, Dieter Jurzitza wrote:
this part has been a sax-bug since ever? Ok, I can live with that - will have
No, it *is* a driver bug in ATI's driver that the driver crashes when too many modelines are present. Sax2 generated a lot of mode lines for large resolutions in 9.3. Begining with 10.0 sax2 doesn't do that any more for fglrx due to and *only* due to this bug. ATI seems to have fixed this issue. Read Bug #115281 for more information. If your problem is about modelines the monitor isn't able to handle, that is not a bug. Drivers *have* to ignore modelines that are not within the monitor's specification.
to, anyway. I only wonder why you didn't mention that when I first reported this about a half a year ago - at that time there had had been time for a bugfix. The question is, is this actually a sax-bug or is this a bug of the
And there has been. Not a fix (which we can't), but a workaround. Of course it won't make it into 9.3. CU Matthias -- Matthias Hopf <mhopf@suse.de> __ __ __ Maxfeldstr. 5 / 90409 Nuernberg (_ | | (_ |__ mat@mshopf.de Phone +49-911-74053-715 __) |_| __) |__ labs www.mshopf.de
participants (3)
-
Dieter Jurzitza
-
Matthias Hopf
-
Phil Betts