From: Fractallyte <fractallyte@csi.com>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Re: Re: atyfb, console, kernel 2.6.14 & Sony Vaio C1VE
Date: Tue, 14 Mar 2006 17:10:00 +0000 [thread overview]
Message-ID: <759672060d21cbb72d1f7e25a09a2f2e@csi.com> (raw)
In-Reply-To: <20060312224354.GA1338@sci.fi>
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&kid\x110944&bid$1720&dat\x121642
prev parent reply other threads:[~2006-03-14 17:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-24 20:16 Re: atyfb, console, kernel 2.6.14 & Sony Vaio C1VE Fractallyte
2006-02-24 21:16 ` Antonino A. Daplas
[not found] ` <2b6bda73c1ef8b8d6463bbe2de83a431@csi.com>
2006-02-26 21:07 ` Antonino A. Daplas
2006-03-03 19:01 ` Fractallyte
2006-03-03 15:01 ` Ville Syrjälä
2006-03-03 19:04 ` Fractallyte
2006-03-12 22:43 ` Ville Syrjälä
2006-03-14 17:10 ` Fractallyte [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=759672060d21cbb72d1f7e25a09a2f2e@csi.com \
--to=fractallyte@csi.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).