how to set lower resolution in fc6t3 xorg?

[Marius Andreiana]

Hi,

FC6t3's xorg.conf does't have anymore the Modes "1024x768"
"800x600"...
line anymore. I've tried adding it but it doesn't recognize the option
(in Screen section).

How to set a lower resolution than the default? (don't want to use
Desktop preferences, which takes effect only after user logs in).
system-config-display offers a choice of "1024x768" or "800x600", I
guess from the commented line in xorg.conf. I removed the line but it
still doesn't change anything.

Thanks,
-- 
Marius Andreiana

[Adam Jackson]

Marius Andreiana wrote:
>  Hi,
>  
>  FC6t3's xorg.conf does't have anymore the Modes "1024x768"
> "800x600"...
>  line anymore. I've tried adding it but it doesn't recognize the option
>  (in Screen section). 
You have to create a Display subsection for it:

Section "Screen"
     # blah blah...
     Subsection "Display"
         Depth 24
         Modes "1024x768"
     EndSubsection
EndSection

- ajax

[Marius Andreiana]

On Tue, 2006-09-19 at 12:57 -0400, Adam Jackson wrote:
>  Marius Andreiana wrote:
>  > Hi,
>  > 
>  > FC6t3's xorg.conf does't have anymore the Modes "1024x768"
> "800x600"...
>  > line anymore. I've tried adding it but it doesn't recognize the option
>  > (in Screen section).
>  
>  You have to create a Display subsection for it: 
Thanks!

Should I file a bug for system-config-display not doing this?

-- 
Marius Andreiana
http://marius.andreiana.googlepages.com

[Adam Jackson]

Marius Andreiana wrote:
>  On Tue, 2006-09-19 at 12:57 -0400, Adam Jackson wrote:
> > Marius Andreiana wrote:
> >> Hi,
> >>
> >> FC6t3's xorg.conf does't have anymore the Modes "1024x768"
> "800x600"...
> >> line anymore. I've tried adding it but it doesn't recognize the option
> >> (in Screen section).
> > You have to create a Display subsection for it:
>  Thanks!
>  
>  Should I file a bug for system-config-display not doing this? 
Nah, there's plenty of bugs about it in one form or another, and I'm 
working on it already.  It's mostly a bug in pyxf86config, which insists 
on creating its own types for every section of the config, rather than 
just decomposing it into a sexp.  The irony is that the list approach 
would have been more flexible in less code, and wouldn't have been quite 
as fragile when the underlying libxf86config grows new features.  It's 
not my favorite library ever.

- ajax

[Adam Jackson]

Adam Jackson wrote:
>  Marius Andreiana wrote:
> > Should I file a bug for system-config-display not doing this?
>  
>  Nah, there's plenty of bugs about it in one form or another, and I'm 
>  working on it already.  It's mostly a bug in pyxf86config, which insists 
>  on creating its own types for every section of the config, rather than 
>  just decomposing it into a sexp.  The irony is that the list approach 
>  would have been more flexible in less code, and wouldn't have been quite 
>  as fragile when the underlying libxf86config grows new features.  It's 
>  not my favorite library ever. 
Should be fixed in the next pyxf86config/rhpxl update.

- ajax

[n0dalus]

On 9/22/06, Adam Jackson <ajackson(a)redhat.com&gt; wrote:
>  Should be fixed in the next pyxf86config/rhpxl update.
>  
Will this update stop the system from choosing a bad resolution in the
first place? My 4:3 monitor is currently running at some horrid
1920x1080 resolution instead of a good 1600x1200 or a sane (and what
the default for my monitor should be) 1152x864. Is this a separate
bug?

n0dalus.

[Adam Jackson]

n0dalus wrote:
>  On 9/22/06, Adam Jackson <ajackson(a)redhat.com&gt; wrote:
> >
> > Should be fixed in the next pyxf86config/rhpxl update.
> >
>  
>  Will this update stop the system from choosing a bad resolution in the
>  first place? My 4:3 monitor is currently running at some horrid
>  1920x1080 resolution instead of a good 1600x1200 or a sane (and what
>  the default for my monitor should be) 1152x864. Is this a separate
>  bug? 
That depends.  The core X server logic should pick a sane virtual size 
by now, but I have sneaking suspicions that some of the drivers are 
defeating it.  You should bz this issue, and attach a log file from a 
session where it picks a bad mode.

- ajax