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: Fri, 3 Mar 2006 19:04:24 +0000 [thread overview]
Message-ID: <60b1aebf4e1937a06ebff8cd92a8f4b3@csi.com> (raw)
In-Reply-To: <20060303150123.GA27401@sci.fi>
On 3 Mar 2006, at 15:01, Ville Syrjälä wrote:
>> 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&kid\x110944&bid$1720&dat\x121642
next prev parent reply other threads:[~2006-03-03 19:04 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 [this message]
2006-03-12 22:43 ` Ville Syrjälä
2006-03-14 17:10 ` Fractallyte
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=60b1aebf4e1937a06ebff8cd92a8f4b3@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).