From: Antonino Daplas <adaplas@pol.net>
To: Linux Fbdev development list <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Frame buffer Reading fails!!
Date: 04 Jan 2003 19:06:37 +0800 [thread overview]
Message-ID: <1041678353.957.8.camel@localhost.localdomain> (raw)
In-Reply-To: <00df01c2b33f$a1354690$bd00000a@abhilash>
On Fri, 2003-01-03 at 23:48, Abhilash wrote:
> Hello,
>
> As u suggested I tried following code in RedHat7.1.
> But it shows
>
> "The framebuffer device was opened successfully."
> "Error reading fixed information."
>
> What could be the problem?
> I am new to this.
>
Try doing it again as root. /dev/fbX is most probably owned by root (as
it should be).
If it still doesn't work, do a
cat /dev/urandom > /dev/fb0
to check if /dev/fb0 is valid. BTW, what fb driver are you using?
Tony
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
prev parent reply other threads:[~2003-01-04 11:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-03 15:48 Frame buffer Reading fails!! Abhilash
2003-01-04 11:06 ` Antonino Daplas [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=1041678353.957.8.camel@localhost.localdomain \
--to=adaplas@pol.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).