From: Jurriaan <thunder7@xs4all.nl>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Anyone got vm86d working? I've got some questions
Date: Wed, 9 Apr 2003 13:03:38 +0200 [thread overview]
Message-ID: <20030409110338.GA1760@middle.of.nowhere> (raw)
The vm86d package from Antonino Daplas should allow me to change the
parameters of my VESA framebuffer after booting.
Unfortunately, I can't get it working. vm86d won't run unless I have a
/dev/vm86 entry. The auther mentioned the correct major/minor numbers
for this entry would be in linux/Documentation/devices.txt and
linux/include/linux/misc.h. Since vm86 is a patch against 2.5.66, I
tried looking for this information, but 'vm86' doesn't appear in
devices.txt and 2.5.66 has no include/linux/misc.h file.
Then I searched 2.5.66 and 2.4.21pre7 for any mention of vm86. No luck.
touch /dev/vm86 works in so far as vm86d starts without error messages,
but neither fbset nor stty change anything about the resolution. strace
on vm86d shows endless select() calls without anything else.
Googling didn't help, alas.
Antonino also mentioned going away for a while, and not having a linux
box at his disposal; so now I'm asking here.
If you have a /dev/vm86, could you tell me the output of
ls -l /dev/vm86
please?
Thanks,
Jurriaan
--
"Windows?", said Pooh. "I want a computer, not a house."
Pooh buys himself a 'Puter.
Debian (Unstable) GNU/Linux 2.5.66 3940 bogomips load av: 1.15 0.88 0.36
-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger
for complex code. Debugging C/C++ programs can leave you feeling lost and
disoriented. TotalView can help you find your way. Available on major UNIX
and Linux platforms. Try it free. www.etnus.com
reply other threads:[~2003-04-09 16:41 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=20030409110338.GA1760@middle.of.nowhere \
--to=thunder7@xs4all.nl \
--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).