atyfb, console, kernel 2.6.14 & Sony Vaio C1VE

[Fractallyte <fractallyte@csi.com>]

Dear List

I'm running Linux with 2.6.14 kernel on a Vaio C1VE laptop.  The LCD 
panel size is 1024x480.  ATI Mach64 framebuffer support is compiled 
into the kernel; however, when booting into the console, the display is 
stretched horizontally to 80 columns, and fbset reports a 640x480 
display.  dmesg reports that the atyfb driver is detecting the correct 
geometry and timings for the panel (tested and working in Xorg), but 
the console insists on 80x30 rather than 128x30.

(For reference) dmesg:

	atyfb: using auxiliary register aperture
	atyfb: 3D RAGE Mobility P/M (Mach64 LR, PCI) [0x4c52 rev 0x64]
	atyfb: Mach64 BIOS is located at c0000, mapped at c00c0000.
	atyfb: BIOS frequency table:
	atyfb: PCLK_min_freq 984, PCLK_max_freq 23600, ref_freq 2950, 
ref_divider 64
	atyfb: MCLK_pwd 4200, MCLK_max_freq 8300, XCLK_max_freq 12500, 
SCLK_freq 5000
	atyfb: BIOS contains driver information table.
	atyfb: colour active matrix monitor detected: Sharp
	atyfb:        id=1, 1024x480 pixels, 262144 colours (LT mode)
	atyfb:        supports refresh rates [60], default 60 Hz
	atyfb:        LCD CRTC parameters: 42.8044  1024 1048 1184 1344  480 
489 495 525
	atyfb:                           : 23618 160 1024 24 136 30 480 9 6
	atyfb: 8M SDRAM (1:1), 29.498928 MHz XTAL, 236 MHz PLL, 83 Mhz MCLK, 
125 MHz XCLK
	Console: switching to colour frame buffer device 80x30
	atyfb: fb0: ATY Mach64 frame buffer device on PCI

Some background information on the C1VE:

Marcel Wijlaars made a patch for the 2.4 kernel 
(http://sourceforge.net/mailarchive/message.php?msg_id=177653 and 
http://www.stack.nl/~marcelw/vaio.html) which allowed for a 1024x480 
console.  This was incorporated into kernel versions up to 2.4.20, but 
later removed by Alan Cox since it crashed some machines.  There's been 
nothing for the 2.6.x kernels specifically for the C1VE, but it seems 
that the Mach64 driver is capable of working correctly with this 
computer.  Alex Kern suggests it could be due to a bug in 
drivers/video/modedb.c

Is anyone able to take a look at this?  I'd be happy to help with 
testing and report back!

Amir



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642