Hi
OK, tried out the 2.6.15.4 kernel. 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 128x30
atyfb: fb0: ATY Mach64 frame buffer device on PCI
It's only *seems* to be a success... The console is correctly set to
128x30, however the timings are apparently not passed from the BIOS to
the console driver. From this point on the screen becomes unreadable
and unusable: white blooms from the edges and spreads inward.
I'll try it out with the 2.6.16 kernel tomorrow...
Thanks for your help!
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
From: "Antonino A. Daplas" <adaplas@gmail.com> Date: 2006-02-24 21:16:37
Fractallyte wrote:
Hi
OK, tried out the 2.6.15.4 kernel. 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 128x30
atyfb: fb0: ATY Mach64 frame buffer device on PCI
It's only *seems* to be a success... The console is correctly set to
128x30, however the timings are apparently not passed from the BIOS to
the console driver. From this point on the screen becomes unreadable
and unusable: white blooms from the edges and spreads inward.
I'll try it out with the 2.6.16 kernel tomorrow...
Thanks for your help!
Too many Mobility's that need xclk=62. Try booting with:
video=atyfb:xclk:62
Tony
-------------------------------------------------------
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
From: Ville Syrjälä <syrjala@sci.fi> Date: 2006-03-03 15:01:36
On Fri, Feb 24, 2006 at 08:16:52PM +0000, Fractallyte wrote:
Hi
OK, tried out the 2.6.15.4 kernel. 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 128x30
atyfb: fb0: ATY Mach64 frame buffer device on PCI
It's only *seems* to be a success... The console is correctly set to
128x30, however the timings are apparently not passed from the BIOS to
the console driver. From this point on the screen becomes unreadable
and unusable: white blooms from the edges and spreads inward.
IIRC my OmniBook 500 did the same thing in the past. I don't remember
what (if anything) I did to fix it. I tried to fiddle around with the
BIOS 'video expansion' option and tried passing various modes to atyfb
but I just can't reproduce it.
--
Ville Syrjälä
syrjala@sci.fi
http://www.sci.fi/~syrjala/
-------------------------------------------------------
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&kid0944&bid$1720&dat1642
It's only *seems* to be a success... The console is correctly set to
128x30, however the timings are apparently not passed from the BIOS to
the console driver. From this point on the screen becomes unreadable
and unusable: white blooms from the edges and spreads inward.
IIRC my OmniBook 500 did the same thing in the past. I don't remember
what (if anything) I did to fix it. I tried to fiddle around with the
BIOS 'video expansion' option and tried passing various modes to atyfb
but I just can't reproduce it.
--
Ville Syrjälä
syrjala@sci.fi
http://www.sci.fi/~syrjala/
Unfortunately, the BIOS options on a Vaio C1VE are rather limited! I'm
still trying various atyfb options...
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&kid0944&bid$1720&dat1642
From: Ville Syrjälä <syrjala@sci.fi> Date: 2006-03-12 22:44:02
On Fri, Mar 03, 2006 at 07:04:24PM +0000, Fractallyte wrote:
On 3 Mar 2006, at 15:01, Ville Syrjälä wrote:
quoted
quoted
It's only *seems* to be a success... The console is correctly set to
128x30, however the timings are apparently not passed from the BIOS to
the console driver. From this point on the screen becomes unreadable
and unusable: white blooms from the edges and spreads inward.
IIRC my OmniBook 500 did the same thing in the past. I don't remember
what (if anything) I did to fix it. I tried to fiddle around with the
BIOS 'video expansion' option and tried passing various modes to atyfb
but I just can't reproduce it.
--
Ville Syrjälä
syrjala@sci.fi
http://www.sci.fi/~syrjala/
Unfortunately, the BIOS options on a Vaio C1VE are rather limited! I'm
still trying various atyfb options...
I was looking for the OB500 service manual and I stumbled on a HP forum
thread discussing similar problems. It seems the "screen going white"
problem may be caused by oxidation of the screen cable connectors.
Here is the full thread:
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=121645
--
Ville Syrjälä
syrjala@sci.fi
http://www.sci.fi/~syrjala/
-------------------------------------------------------
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&kid0944&bid$1720&dat1642
Nice! ;-) Fortunately, my laptop has a completely stable and reliable
display. It's definitely a kernel driver problem. A patched 2.4
kernel allows me to get the full-width 1024x480 console, but the 2.6
kernel is very different.
I'm just looking at modedb.c - the standard video mode definitions
don't include 1024x480. The 2.4 kernel patch modified this file; I'm
wondering whether it would make a difference with the present kernel...
On 12 Mar 2006, at 22:43, Ville Syrjälä wrote:
I was looking for the OB500 service manual and I stumbled on a HP forum
thread discussing similar problems. It seems the "screen going white"
problem may be caused by oxidation of the screen cable connectors.
Here is the full thread:
http://forums1.itrc.hp.com/service/forums/questionanswer.do?
threadId=121645
--
Ville Syrjälä
syrjala@sci.fi
http://www.sci.fi/~syrjala/
-------------------------------------------------------
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&kid0944&bid$1720&dat1642