Ticket #82 (closed defect: wontfix)

Opened 6 years ago

Last modified 5 years ago

Buggy GUI X.Org configuration tool ported from Ubuntu

Reported by: beranger5ca@… Owned by: parsix-devel@…
Priority: lowest Component: Hardware Detection
Version: 1.0 (ramon) Severity: minor
Keywords: Cc: alan@…

Description

The only visible bug is in... (surprise?!) the "new GUI X.Org configuration tool ported from Ubuntu"!

X started (Radeon 9200SE with the open-source radeon driver) in 1024x768, so I wanted to change it to 1400 x 1050. The "new GUI X.Org configuration tool ported from Ubuntu" showed me the wrong Relisys CRT, so I changed it, and selected a different resolution for the video adapter too.

Unfortunately, nothing changed on the screen no matter what, so I had to restart X. This brought me a... 2048x1536 virtual workspace holding a physical screen of 1024x768!

I went then back to the "new GUI X.Org configuration tool ported from Ubuntu", set the screen to 1400x1050, and this time it worked.

Should have behaved much better. Any improved tool from Ubuntu?

Change History

comment:1 Changed 6 years ago by beranger5ca@…

UPDATED DETAILS:
-- I can't use something like "xscreen=1400x1050 xmodule=radeon" at
boot prompt (the xscreen part), because it will fail miserably; so I had to let it only with (for instance) options like "xmodule=radeon", but it will still default to 1024x768, because of THE REAL BUG.
-- The fact that the CRT was not correctly detected has no relevance, as the probed H and V frequencies are correct.

THE REAL BUG:
-- xorg.conf has ALL the possible (and correct) ModeLine? values in the Section "Monitor", BUT:
-- in Section "Screen", Subsection "Display", the Modes lines start with the highest value of "1024x768"!

SUGGESTION:
-- Add to the Modes lines (in Section "Screen", Subsection "Display") ALL the ModeLine? lines probed and listed in Section "Monitor"; other distros do that; however resolutions higher than 1600x1200 should not be used even if detected as possible.
-- If not possible, add at least "1280x1024" if no specific boot options were used, or the respective wide resolution (1680x1050, 1440x900, 1280x800) if used.

comment:2 Changed 6 years ago by alan@…

I wasn't aware that it would honor such options. But there is one more issue,
not mentioned at Bug 82: "ati" defaults to "fglrx", but in my case the 100%
free "radeon" driver performs better. Does it honor "xmodule=radeon"? (I hope
so.)

The auto detection system does not support binary nvidia/fglrx drivers. I wonder how it's possible? At work I've ATI graphic card and it always is being detected as "ati". Please double check.

Also it is possible to use several boot options at the same time. Like xscreen=1280x1024 xmodule=ati and so. What means that "fail miserably" black screen? What's the maximum supported resolution of your CRT monitor?

Another note that 1024x768 is the safest default value for CRT monitors. We can not change it to higher values, because it will fail on the older ones.

Cheers,
Alan

comment:3 Changed 6 years ago by beranger5ca@…

The auto detection system does not support binary nvidia/fglrx
drivers. I wonder how it's possible? At work I've ATI graphic
card and it always is being detected as "ati".

"ati" is a wrapper. If "fglrx" is available, it will use it, otherwise it will use "radeon". It's like that since ages!

xscreen=1280x1024 xmodule=ati and so. What means that
"fail miserably" black screen?

Weird clock times, virtual screen larger than real screen, etc.

What's the maximum supported resolution of your CRT monitor?

Supported: 2048x1536 (but my Radeon only has 64 MB), 1920x1440, 1856x1392, 1792x1344, 1600x1200, 1400x1050, 1280x1024 etc. etc.

Another note that 1024x768 is the safest default value for CRT monitors.
We can not change it to higher values, because it will fail on the older ones.

I suppose you haven't understood me. In "Section "Monitor"", xorg.conf has *PROBED* clock values for ALL THE *SUPPORTED* resolutions, based on the fact that the CRT supports 30-95 KHz and 50-160 Hz frequencies.

Why having them there, if downwards it limits itself to 1024x768?

Ubuntu boots into 1600x1200, this is why I said there is a limit. Somehow, even it detects I can use higher resolutions, it limits the "Modes" line to 1600x1200.

Of course, the same Ubuntu LiveCD limits itself to 1024x768 on my old laptop, automatically.

So there must be a way.

comment:4 Changed 6 years ago by alan@…

The backend package of displayconfig-gtk application called guidance-backends has been updated. Would you please test and see if the problem has been solved or not? Thanks.

comment:5 Changed 6 years ago by beranger5ca@…

On the contrary, it's now broken!

I didn't want to answer before I got the chance to test the new CD too -- but it's the same:

parsix@0[~]$ displayconfig-gtk
Traceback (most recent call last):

File "/usr/bin/displayconfig-gtk", line 74, in ?

from displayconfiggtk.DisplayConfig? import DisplayConfig?

File "/usr/lib/python2.4/site-packages/displayconfiggtk/DisplayConfig.py", line 36, in ?

from widgets import *

File "/usr/lib/python2.4/site-packages/displayconfiggtk/widgets.py", line 37, in ?

from displayconfigabstraction import *

ImportError?: No module named displayconfigabstraction

On the other hand, the LiveCD starts in 1024x768 as a maximum resolution on a CRT -- so it does *not* behave like Ubuntu!

comment:6 Changed 6 years ago by alan@…

Mmm, it works on my system, For a CRT monitor, pass desired resolution via xscreen= boot parameter on live CD mode.

comment:7 Changed 5 years ago by alan@…

  • Cc alan@… added
  • Status changed from new to closed
  • Resolution set to wontfix

I'm closing this bug, as we are not using that tool anymore.

Alan

Note: See TracTickets for help on using tickets.