From: Michal Januszewski <spock@gentoo.org>
To: Ryan Hope <rmh3093@gmail.com>
Cc: linux-fbdev-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, hpa@zytor.com
Subject: Re: [PATCH v2 0/5] uvesafb: a general description
Date: Fri, 6 Jul 2007 21:53:43 +0200 [thread overview]
Message-ID: <20070706195343.GA12096@spock.one.pl> (raw)
In-Reply-To: <48f7fe350707051038p422ea305w10d727bcc44e5d7b@mail.gmail.com>
On Thu, Jul 05, 2007 at 01:38:46PM -0400, Ryan Hope wrote:
> I applied
> http://dev.gentoo.org/~spock/projects/uvesafb/archive/uvesafb-0.1-rc2-2.6.22-rc6.patchto
> 2.6.22-rc6-mm1... everything seems to be working properly. However, in dmesg
> I did notice the following message:
>
> uvesafb: message too long (9872), can't execute task
> uvesafb: VBE get state call failed (eax=0x4f04, err=-7)
>
> The messages seem to get generated when I switch VTs. Just thought I would
> let you know. If there is anything else I can do to help let me know.
It looks like the VBE hardware state buffer for your video card is
larger than the 4k currently supported by connector. The problem should
be easily fixed by setting CONNECTOR_MAX_MSG_SIZE in include/linux/connector.h
to e.g. 16k. I've already updated the patch on my website, so next time
you download it, the error messages should be gone.
Best regards,
Michal
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
prev parent reply other threads:[~2007-07-06 19:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-30 16:31 [PATCH v2 0/5] uvesafb: a general description Michal Januszewski
2007-06-30 20:48 ` Gabriel C
2007-07-03 23:05 ` Gabriel C
2007-07-05 17:38 ` Ryan Hope
2007-07-06 19:53 ` Michal Januszewski [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=20070706195343.GA12096@spock.one.pl \
--to=spock@gentoo.org \
--cc=hpa@zytor.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rmh3093@gmail.com \
/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).