Live CD asks screen resolution question

[Martin Pitt]

Current (2005-08-25) Breezy Live CD on amd64/Nvidia GeForce 5200 asks for
monitor resolution although xresprobe is installed.

However:
$ sudo xresprobe nv
id:
res:
freq:
disptype:

This doesn't look overly correct...

[Martin Pitt (pitti)]

Created an attachment (id=3389)
/var/log/casper/post.log

My casper post.log for completeness.

[Matt Zimmerman (mdz)]

Re-run xresprobe with XRESPROBE_DEBUG=yes and check the files it leaves in /tmp

[Martin Pitt (pitti)]

$ sudo env XRESPROBE_DEBUG=yes xresprobe nv
laptop: ; ddc: yes
attempting DDC detection
id:
res:
freq:
disptype:
id:
res:
freq:
disptype:
not cleaning up after Xorg; not forked

$ sudo env DEBUG_XRESPROBE=yes sudo xresprobe nv
id:
res:
freq:
disptype:

There is no file in /tmp that looks particularly interesting:

$ ls -la /tmp/
total 5
drwxrwxrwt 9 root root 240 2005-08-25 17:33 .
drwxr-xr-x 22 root root 1024 2005-08-25 17:26 ..
drwxrwxrwt 2 ubuntu ubuntu 60 2005-08-25 17:29 .esd-1000
drwx------ 3 ubuntu ubuntu 60 2005-08-25 17:29 gconfd-ubuntu
srw-rw-rw- 1 root root 0 2005-08-25 17:28 .gdm_socket
drwxrwxrwt 2 root root 60 2005-08-25 17:29 .ICE-unix
drwx------ 2 ubuntu ubuntu 60 2005-08-25 17:29 keyring-MCmam5
srwxr-xr-x 1 ubuntu ubuntu 0 2005-08-25 17:30 mapping-ubuntu
drwx------ 2 ubuntu ubuntu 440 2005-08-25 17:32 orbit-ubuntu
drwx------ 2 ubuntu ubuntu 60 2005-08-25 17:28 ssh-lJosX20647
-r--r--r-- 1 root root 11 2005-08-25 17:28 .X0-lock
drwxrwxrwt 2 root root 60 2005-08-25 17:28 .X11-unix

Maybe this gives a hint:

$ sudo ddcprobe
VESA BIOS Extensions not detected.

This happens on my installed system, too, so it's not a particular live-cd bug;
I adapt the bug metadata accordingly.

[Martin Pitt (pitti)]

I use DVI now, that might be a reason. I'll try the Hoary CD now, for
comparison. If it happens there, too, it's at least not a regression.

[Daniel Stone (daniels)]

Uhm, we've never had support for DDC on amd64 machines. mjg59 and Mithrandir
have been looking at an lrmi/x86emu shim in this case, but ran into weird and
esoteric problems with memory management.

This bug has been marked as a duplicate of bug 8177.