Resolution in installer and usplash messed up in Dapper

Ditto with kernel 2.6.15-20.

Could you please attach the output of the command

sudo dmidecode

? Thanks!

The problem persists even with kernel 2.6.22
Here's the output:

# dmidecode 2.7
SMBIOS 2.3 present.
22 structures occupying 843 bytes.
Table at 0x000F0630.

Handle 0x0000, DMI type 0, 20 bytes.
BIOS Information
        Vendor: American Megatrends Inc.
        Version: Version 07.00T
        Release Date: 04/02/01
        Address: 0xF0000
        Runtime Size: 64 kB
        ROM Size: 256 kB
        Characteristics:
                ISA is supported
                PCI is supported
                PNP is supported
                APM is supported
                BIOS is upgradeable
                BIOS shadowing is allowed
                ESCD support is available
                Boot from CD is supported
                Selectable boot is supported
                BIOS ROM is socketed
                EDD is supported
                5.25"/360 KB floppy services are supported (int 13h)
                5.25"/1.2 MB floppy services are supported (int 13h)
                3.5"/720 KB floppy services are supported (int 13h)
                3.5"/2.88 MB floppy services are supported (int 13h)
                Print screen service is supported (int 5h)
                8042 keyboard services are supported (int 9h)
                Printer services are supported (int 17h)
                CGA/mono video services are supported (int 10h)
                ACPI is supported
                USB legacy is supported
                AGP is supported
                LS-120 boot is supported
                ATAPI Zip drive boot is supported
                BIOS boot specification is supported

Handle 0x0001, DMI type 1, 25 bytes.
System Information
        Manufacturer: MSI
        Product Name: MS-6712
        Version: 1.0
        Serial Number: 00000000
        UUID: Not Settable
        Wake-up Type: Modem Ring

Handle 0x0002, DMI type 2, 8 bytes.
Base Board Information
        Manufacturer: MSI
        Product Name: MS-6712
        Version: 1.0
        Serial Number: 00000000

Handle 0x0003, DMI type 3, 17 bytes.
Chassis Information
        Manufacturer: Uknown Chassis Manufacture
        Type: Desktop
        Lock: Not Present
        Version: Version 1.00
        Serial Number: 123456890
        Asset Tag: 0123ABC
        Boot-up State: Unknown
        Power Supply State: Unknown
        Thermal State: Unknown
        Security Status: Unknown
        OEM Information: 0x00000000

Handle 0x0004, DMI type 4, 32 bytes.
Processor Information
        Socket Designation: Socket-A
        Type: Central Processor
        Family: Athlon
        Manufacturer: AMD
        ID: 81 06 2C E3 55 00 00 00
        Signature: Family 6, Model 8, Stepping 1
        Flags:
                FPU (Floating-point unit on-chip)
                DE (Debugging extension)
                TSC (Time stamp counter)
                PAE (Physical address extension)
        Version: AMD Athlon(tm) XP 2100+
        Voltage: 3.3 V 2.9 V
        External Clock: 133 MHz
        Max Speed: 3000 MHz
        Current Speed: 1733 MHz
        Status: Populated, Enabled
        Upgrade: Socket A (Socket 462)
        L...

Is this with an LCD monitor?

No. A regular Philips 107e.

Just for completeness' sake: the problem also appears, when I switch to a console. So obviously, whenever X is not running, the resolution is wrong.

I'm a bit confused. Is this not something that can be adjusted using the width and height controls on your monitor?

I could adjust it. But then the screen would reach over the monitor's edge, as soon as X starts.

The resolution is perfect, as soon as X starts. Anything else is too small. At least the screen used only partially.

Really? Most monitors store different values for different resolutions.
Have you tried?

--
Matthew Garrett | <email address hidden>

I changed the resolution and now both usplash and X display properly. Thanks for the suggestion. Guess it would never have crossed my mind.

So this bug could be marked as fixed for me. Still the reason why Dapper displayed differently from Breezy, using the wrong resolution in the first place, is unknown.

I'll mark this bug fixed since it now works for the original reporter