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:01:39 +0000 [thread overview]
Message-ID: <f843337601bf9e23232d10976cde8648@csi.com> (raw)
In-Reply-To: <44021879.7040806@gmail.com>
On 26 Feb 2006, at 21:07, Antonino A. Daplas wrote:
>
> Fractallyte wrote:
>
> Putting back Ville and fbdev-devel back on the CC list.
>
>> Thanks for the quick reply!
>>
>> I tried what you suggested, but it has no effect. The interesting
>> thing
>> is that the BIOS timings and geometry work perfectly in Xorg. I've
>> tried using SVGATextMode and FBSet using these values, but neither
>> works.
>>
>> Could it be that the display is correct (it fills up the screen, after
>> all - just stretched out), but the console just doesn't recognise it?
>
> I doubt it. If you can run X over fbdev and you get a perfect display,
> then I would agree with you that this is a bug in the console code.
I suddenly remembered: I CAN'T run X over atyfb. I just get a blank
(sometimes corrupted) screen. To run X I have to turn off atyfb in
grub.
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
next prev parent reply other threads:[~2006-03-03 19:01 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 [this message]
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
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=f843337601bf9e23232d10976cde8648@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).