From: Josh Fryman <fryman@cc.gatech.edu>
To: Abraham vd Merwe <abraham@2d3d.co.za>
Cc: linux@aerythmic.be, linux-kernel@vger.kernel.org
Subject: Re: Stolen Memory <- i830M video chip
Date: Fri, 12 Apr 2002 07:31:36 -0400 [thread overview]
Message-ID: <20020412073136.53e533ed.fryman@cc.gatech.edu> (raw)
In-Reply-To: <20020412094323.B8997@crystal.2d3d.co.za>
> It is therefore a OEM BIOS problem. Dell was notified about this a long time
> ago - I thought they fixed it in the mean time. Try moaning about this to
> Asus as well...
this isn't fixed in the new dell C400 laptops (still). however, i argue that
BIOS problem or no, a solution _does_ exist. there is a 3rd party that
sells commercial X server drop-ins for new chipsets. one of the guys here
bought their X server for $40 or so, and now has full-color & -resolution
without getting a BIOS update.
so if it's a BIOS problem that can only be fixed by Dell, how were these guys
able to do the fix? and why can't the open source guys (XFree or Linux kernel)
seem to do the same?
-josh
ps > company is xig.com : Dell C400 w/generic I830-M support:
http://www.xig.com/Pages/Atop/LaptopIndividualSupportSpecs/Dell-IndividualLaptops/LatitudeC400.html
next prev parent reply other threads:[~2002-04-12 11:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-11 20:50 Stolen Memory <- i830M video chip Michael De Nil
2002-04-11 20:29 ` Blue Lang
2002-04-12 7:37 ` i830M video chip (X driver deficient) Eric W. Biederman
2002-04-12 17:06 ` Blue Lang
2002-04-12 18:09 ` Eric W. Biederman
2002-04-12 7:43 ` Stolen Memory <- i830M video chip Abraham vd Merwe
2002-04-12 11:31 ` Josh Fryman [this message]
2002-04-12 12:39 ` Abraham vd Merwe
[not found] ` <20020412085204.2202df0e.fryman@cc.gatech.edu>
2002-04-12 12:57 ` Abraham vd Merwe
2002-04-13 9:06 ` Michael De Nil
2002-04-13 16:51 ` Alan Cox
2002-04-15 16:20 ` Michael De Nil
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=20020412073136.53e533ed.fryman@cc.gatech.edu \
--to=fryman@cc.gatech.edu \
--cc=abraham@2d3d.co.za \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@aerythmic.be \
/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