public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Statux <statux@optonline.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Via UniChrome Pro and Xorg
Date: Tue, 19 Sep 2006 12:33:10 -0400	[thread overview]
Message-ID: <1158683590.6682.4.camel@statux.kicks-ass.net> (raw)
In-Reply-To: <200609191125.40778.benno.schulenberg@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1114 bytes --]

[snip]

> You mean x11-drivers/xf86-video-via-0.1.33.2 ?  It's far too old for 
> the 800 chips.  And openchrome doesn't do regular releases (see 
> https://bugs.gentoo.org/show_bug.cgi?id=147425) so if you want it 
> working, you'll need to build from SVN.
> 

Well that explains that.

> http://wiki.openchrome.org/tikiwiki/tiki-index.php?page=Compiling+the+source+code

[snip]

> Then simply use the vesa driver.  At depth 16 it should work 
> perfectly.  3D acceleration will not really work on the 800 chips 
> anyway: the Mesa stuff for the unichrome is unmaintained and there 
> is a bug in the textures code that trips up the 800s.
> 

I was avoiding use of the vesa driver for some reason but I'll give it a
try and see if I can get anywhere. Yeah, all my mother needs is a
straight 2D environment. I'm not big on on-board video/audio/networking
but for light use, it's ok. If she were to ever need something with more
juice, I'd get a seperate 3D card anyway.

Thanks.

> Benno
> 
> -- 
> Cetere mi opinias ke ne ĉio tradukenda estas.
-- 
Statux <statux@optonline.net>

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 191 bytes --]

      reply	other threads:[~2006-09-19 16:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-19  0:58 [gentoo-user] Via UniChrome Pro and Xorg Statux
2006-09-19  9:25 ` Benno Schulenberg
2006-09-19 16:33   ` Statux [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=1158683590.6682.4.camel@statux.kicks-ass.net \
    --to=statux@optonline.net \
    --cc=gentoo-user@lists.gentoo.org \
    /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