From: Alan Grimes <alangrimes@starpower.net>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Why am I shocked?
Date: Mon, 07 Apr 2003 14:56:52 -0400 [thread overview]
Message-ID: <3E91C9F4.9060504@starpower.net> (raw)
I must be insane.
I thought that /dev/fb0 was something that just worked... That simply
gave an interface to the VESA 2 buffer or, if that fails, the standard
VGA area. I was so smug in this assumption that I never bothered to
question this and left the machine alone for months and months while I
worked to port squeak ( www.squeak.org ) to it.
I felt uncomfortable letting such an amazingly powerful dual athlon go
to waste so I went looking for a GUI for it....
After considerable effort I managed to get picogui compiled...
I try to do a test-run of the thing and quickly discover that my lowly
old ATI Rage PRO Turbo based card was not supported at all! --
*incredible*. I had always known that leenooks was a piece of crap but
this is astonishing!!!!
DOS games recognise the damn thing automaticly - No configuration of any
kind required.
DOS programs have had the equivalent of framebuffer compatibility for
twenty years now!! and _LEENOOKS_, An OS that is supposed to be superior
in every way, simply does not support it!
I'll cut the kernel devels some slack because ATI is tight-lipped about
the specs of its products but not supporting VESA 2 modes is flat-out
_UNFORGIVABLE_.
What am I going to have to do, install windows XP pro on the thing??? =(
-------------------------------------------------------
This SF.net email is sponsored by: ValueWeb:
Dedicated Hosting for just $79/mo with 500 GB of bandwidth!
No other company gives more support or power for your dedicated server
http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/
next reply other threads:[~2003-04-07 19:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-07 18:56 Alan Grimes [this message]
2003-04-07 20:49 ` Why am I shocked? Ian Romanick
2003-04-08 3:06 ` Richard Drummond
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=3E91C9F4.9060504@starpower.net \
--to=alangrimes@starpower.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.