Second call for X testers.

[Fabio Massimo Di Nitto]

On Tue, 31 Aug 2004, Matt Zimmerman wrote:

> On Tue, Aug 31, 2004 at 01:56:05PM +0200, Fabio Massimo Di Nitto wrote:
>
> > apt-get update
> > apt-get upgrade
> > apt-get install discover1 xresprobe laptop-detect mdetect
> > apt-get --purge remove xserver-xfree86
> > (be sure there is no /etc/X11/XF86Config-4 file)
> > echo $LANG
> > (check if the language is set properly)
> > apt-get install xserver-xfree86
> >
> > take notes of how many questions you will see (if any).
>
> You forgot "make a backup of /etc/X11/XF86Config-4 for comparison" :-)

ehm.... quoting myself from my original message:

Make a copy of /etc/X11/XF86Config-4 for backup and exit X. login in
console mode and do in sequence the following 3 tests (please keep the
same order when executing and reporting):

> In both cases, the resulting config file looked reasonable and worked
> correctly.

goody.

> This was very strange.  I was asked all of
> xserver-xfree86/config/display/modes,
> xserver-xfree86/config/monitor/selection-method and
> xserver-xfree86/config/monitor/mode-list.  This seems quite redundant.

One things is the resolution you want, the other is what the monitor can
do. They look redundant but they are not.

> DEBCONF_DEBUG=developer output attached.

thanks.

> powerpc desktop: two questions (keyboard layout, mode selection)
>   This gave me an fbdev configuration with a correct BusID, and 1024x768,
>   800x600 and 640x480 modes.  However, when X started, the virtual desktop
>   seemed to be 1280x1024, while the screen was 1024x768, so the entire
>   bottom panel, and the clock and system tray in the top panel, were off the
>   edge of the screen, and the background graphics were misaligned.

This sounds strange.. what modes were written in the config file?
It looks more that the Mode was 1280x1024 and monitor was forced to go
down by the frequencies selections. Can you check the modelines in the
log?

Fabio

-- 
<user> fajita: step one
<fajita> Whatever the problem, step one is always to look in the error log.
<user> fajita: step two
<fajita> When in danger or in doubt, step two is to scream and shout.