On Tue, Feb 21, 2012 at 05:51:29AM +0100, Ralf Mardorf wrote: > Did you check by running "sudo hwinfo --framebuffer" too? It shouldn't > differ, but perhaps there's something fishy with vbeinfo. I just checked `sudo hwinfo --framebuffer`, the attachment below is the result. Cheers, Bill
02: None 00.0: 11001 VESA Framebuffer [Created at bios.459] Unique ID: rdCR.ku_DuSHewh1 Hardware Class: framebuffer Model: "Intel(R)Sandybridge Mobile Graphics Controller" Vendor: "Intel Corporation" Device: "Intel(R)Sandybridge Mobile Graphics Controller" SubVendor: "Intel(R)Sandybridge Mobile Graphics Chipset Accelerated VGA BIOS" SubDevice: Revision: "Hardware Version 0.0" Memory Size: 63 MB + 960 kB Memory Range: 0xe0000000-0xe3feffff (rw) Mode 0x0360: 768x480 (+768), 8 bits Mode 0x0361: 768x480 (+1536), 16 bits Mode 0x0362: 768x480 (+3072), 24 bits Mode 0x0363: 960x600 (+960), 8 bits Mode 0x0364: 960x600 (+1920), 16 bits Mode 0x0365: 960x600 (+3840), 24 bits Mode 0x0305: 1024x768 (+1024), 8 bits Mode 0x0317: 1024x768 (+2048), 16 bits Mode 0x0318: 1024x768 (+4096), 24 bits Mode 0x0312: 640x480 (+2560), 24 bits Mode 0x0314: 800x600 (+1600), 16 bits Mode 0x0315: 800x600 (+3200), 24 bits Mode 0x0301: 640x480 (+640), 8 bits Mode 0x0303: 800x600 (+832), 8 bits Mode 0x0311: 640x480 (+1280), 16 bits Config Status: cfg=new, avail=yes, need=no, active=unknown
