From: "Jordan Crouse" <jordan.crouse@amd.com>
To: "Andrew Paprocki" <andrew@ishiboo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: lxfb is not changing modes, no errors/information printing out
Date: Sun, 27 Jan 2008 12:28:07 -0700 [thread overview]
Message-ID: <20080127192807.GF8635@cosmic.amd.com> (raw)
In-Reply-To: <76366b180801271045u7342540p58f5970a49c097be@mail.gmail.com>
On 27/01/08 13:45 -0500, Andrew Paprocki wrote:
> Using 2.6.24, I can't get my Geode LX (LX800 CPU) to boot in anything
> other than the default 80x25 console even though lxfb appears to be
> loading normally. This device doesn't work with the VESA fb either
> when I request "vga=0x31a". All the other boards I have display a
> 1280x1024 console on my monitor. Are my kernel parameters wrong in
> some way? I tried "video=lxfb:<mode>" with and without "vga=0x31a".
> The driver is compiled into the kernel -- I am not using modules.
Can you change the mode after you have booted with 'fbset'?
> Also, a side note.. blanking on this display doesn't seem to work
> properly. When the screen would normally blank after a timeout, a thin
> ~20px width vertical black strip appears on the left-hand side of the
> screen, but the rest of the display area remains showing whatever
> contents were on the screen when the blank was triggered. Hitting a
> key goes back to displaying the current fb contents like you would
> expect.
Thanks for reporting that - thats a known bug, I'll send a patch to fix it.
Jordan
--
Jordan Crouse
Systems Software Development Engineer
Advanced Micro Devices, Inc.
next prev parent reply other threads:[~2008-01-27 19:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-27 18:45 lxfb is not changing modes, no errors/information printing out Andrew Paprocki
2008-01-27 19:28 ` Jordan Crouse [this message]
2008-01-27 19:55 ` Andrew Paprocki
2008-01-27 20:38 ` Jordan Crouse
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=20080127192807.GF8635@cosmic.amd.com \
--to=jordan.crouse@amd.com \
--cc=andrew@ishiboo.com \
--cc=linux-kernel@vger.kernel.org \
/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