dapper livecd: xorg not started in 1400x1050

This is the /etc/X11/xorg.conf file as found after boot with the Dapper flight 6 live CD.

This is the /etc/X11/xorg.conf file I modified to add the 1400x1050 mode to the screen section.

This is the /var/log/Xorg.0.log.old of the initial X.org boot in 1024x768 mode.
The log ends with lines of the shutdown of the server (end with Ctrl+Alt+Bkspace).

This is /var/log/Xorg.0.log after addition of mode 1400x1050 in /etc/X11/xorg.conf

After further investigation (read /usr/bin/dexconf), the list of video modes seems to come from the debconf database : xserver-xorg/config/display/modes

Where is does this value come from?

When booting in framebuffer 1400x1050, using "sudo dpkg-reconfigure -phigh xserver-xorg" (as indicated in xorg.conf) rebuilds an xorg.conf file which contains only 1400x1050 mode: it fixes the xorg.conf.

Hi,

I seem to have the same problem (no higher resolution than 1024x768) with the Dapper Beta LiveCD for my Medion 95500 laptop (with a 17" wide screen).

from http://ole.tange.dk/linux/problemer/medion-95500/ you can read that this laptop has a:
* nVidia Geforce Go 6600 (PCI:0148 rev a2)

So it seems this bug is not specific for the ATI chipset (so it's probably a 'generic' bug)

can you both please exit from X and provide the output of xresprobe $driver ?
(where $driver is ati/nv or whatever is required on your hw)

Thanks
Fabio

The console output the xresprobe nv command

The contents of the /tmp/xprobe.7595 directory that goes with the previous xresprobe nv console output attachment.

Attachment contains generated
xorg.conf
xorg.log
xorg-stdout.log

ok there are 2 different bugs here. one for ati and for nv. Japi please open another bug for your problem and add also generated xorg.conf and Xorg.0.log

Fabio

Oliver please provide me with the info i requested.

Hello Fabio,

I submitted a new bug (#42932) for "my" problem.

I have no directory /tmp/xprobe.*
Locale is fr_BE.

The xresprobe output is the same on Ubuntu Breezy.

Similar to Bug #5801

Modifying package to xresprobe, where this bug really belongs.

Olivier: please run 'sudo xresprobe ati', that error message means that it cannot launch X server to probe the values.

'sudo xresprobe ati' on the edgy live cd reports 1400x1050 but the X server is in 1024x768.

The status of this bug is still 'Needs info' even if all requested info has been provided one month ago.

I won't be able to test with Feisty Beta and provide more info as my computer is now dead (hardware failure).

Setting back to confirmed.