From: Eric Bambach <eric@cisu.net>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: VesaFB Problems
Date: Sun, 19 Jun 2005 22:36:57 -0500 [thread overview]
Message-ID: <200506192236.58009.eric@cisu.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1553 bytes --]
Hello,
Please CC me I'm not subscribed.
If I am not asking on the correct list can someone refer me to a better place
to ask?
I am having trouble with vesafb. Here is an excerpt from dmesg, full dmesg
attached.
vesafb: BUG, returned from vm86 with 0
vesafb: warning, copying modelist from somewhere in RAM!
vesafb: Getting mode info block failed (eax=0x4f00)
vesafb: vbe_init failed
vesafb: probe of vesafb0 failed with error -22
#uname -a Linux eric 2.6.11-gentoo-r9 #7 SMP Sun Jun 19 21:57:28 CDT 2005 i686
AMD Athlon(tm) MP 2600+ AuthenticAMD GNU/Linux
I am triying to get fbsplash working in Gentoo and I followed the
instructions to a T, but I get no output (as in fbsplash doesnt even try to
load) and I think its related to this message. I am using the nvidia module,
but its loaded WAY after this message and after fbsplash would try to
init...so I doubt theres a conflict. I have 1 AGP GeForce 4ish and a PCI
GeForce2 for dual monitors. Could it be related to 2 videocards?
Any ideas about this message? Can I be of help debugging?
--
----------------------------------------
--EB
> All is fine except that I can reliably "oops" it simply by trying to read
> from /proc/apm (e.g. cat /proc/apm).
> oops output and ksymoops-2.3.4 output is attached.
> Is there anything else I can contribute?
The latitude and longtitude of the bios writers current position, and
a ballistic missile.
--Alan Cox LKML-December 08,2000
----------------------------------------
[-- Attachment #2: lspci.dump.gz --]
[-- Type: application/x-gzip, Size: 1188 bytes --]
[-- Attachment #3: dmesg.dump.gz --]
[-- Type: application/x-gzip, Size: 7164 bytes --]
reply other threads:[~2005-06-20 3:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200506192236.58009.eric@cisu.net \
--to=eric@cisu.net \
--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).