On Mon, 21 Jul 2008, Michael Lorenz wrote:
... which leaves the question why on earth it picks this resolution. I trust you don't have an ancient monitor from the previous ice age connected.max_dotclock according to supported modes: 108000 radeonfb0: using static EDID max_dotclock according to supported modes: 108000 radeonfb0: 64 MB aperture at 0x98000000, 64 KB registers at 0x90000000 radeonfb0: display 0: initial virtual resolution 640x350 at 32 bpp radeonfb0: port 0: physical 640x350 70Hz radeonfb0: port 1: physical 640x350 70Hz
This particular monitor is a couple of years old, but I would not say it is from the previous ice age... I tried a monitor I bought last year, but no success there either, although the dmesg changed to say:
max_dotclock according to supported modes: 162000 radeonfb0: using static EDID max_dotclock according to supported modes: 162000 radeonfb0: 64 MB aperture at 0x98000000, 64 KB registers at 0x90000000 radeonfb0: display 0: initial virtual resolution 1280x1024 at 32 bpp radeonfb0: port 0: physical 1280x1024 60Hz radeonfb0: port 1: physical 1280x1024 60Hz /Krister