From: Philip Webb <purslow@sympatico.ca>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] new box DRI problem : more
Date: Wed, 31 Oct 2007 00:03:00 -0400 [thread overview]
Message-ID: <20071031040300.GA4634@sympatico.ca> (raw)
In-Reply-To: <b79f23070710300658k208bc147x9f162402bf9bb2d8@mail.gmail.com>
071030 James Ausmus wrote:
> On 10/30/07, Benno Schulenberg <benno.schulenberg@gmail.com> wrote:
>> build the Mesa modules from git, the 1.2.2 and 1.4 part:
>> http://dri.freedesktop.org/wiki/Building
>> These three lines were added to i915/intel_context.h since 7.0.1:
>> #define PCI_CHIP_G33_G 0x29C2
>> #define PCI_CHIP_Q35_G 0x29B2
>> #define PCI_CHIP_Q33_G 0x29D2
> You don't have to go to all that, the media-libs/mesa-7.0.1 works fine
> *IF* you apply the attached patch (either hack the ebuild
> or CTRL-Z immediately after emerge gets done unpacking the source).
> I had the same problem you did, did the Googling, found the patch
> and everything works fine for me now.
I did try unpacking the MesaLibs distfile, patching & repacking,
but of course Portage objected that the file size was incorrect !
I've looked at the Mesa ebuild, but have no idea how to hack it
nor am I confident of applying the patch during a suspended emerge.
I could try the 2nd, but could you fill out a few more details of the 1st,
which I will note for future occasions ?
This certainly looks like the solution to the DRI problem.
Meanwhile, what I believed to be a small irritant is proving a show-stopper.
Leaving aside DRI, the display from the new machine spills off the screen:
it's way off to the left (eg Gkrellm is invisible on the KDE desktop)
& loses about half the KDE panel when placed at top/bottom/right-side;
mouse-X starts left of centre & the fonts & icons are badly oversized.
KDE Control Centre tells me the display is 1680x1050 @ 60 Hz (as it sb).
Elsewhere, it does appear the screen's physical size ( 430 x 270 mm )
is being recognised, tho' perhaps it's not being applied correctly.
I believed the problem was due to faulty thro'put by my KVM switch,
but plugging the monitor directly into the new machine make no difference.
I don't see any obvious solution in the monitor manual (Samsung 206BW).
The current machine using an Nvidia card & direct monitor plug-in
produces none of these defects, suggesting the cause is the G33 chip.
I'm not keen to buy another Nvidia card, if I can avoid it ...
Any advice here too wb very welcome.
--
========================,,============================================
SUPPORT ___________//___, Philip Webb : purslow@chass.utoronto.ca
ELECTRIC /] [] [] [] [] []| Centre for Urban & Community Studies
TRANSIT `-O----------O---' University of Toronto
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2007-10-31 4:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-27 23:37 [gentoo-user] Glxgears crashes X Philip Webb
2007-10-28 22:15 ` [gentoo-user] new box DRI problem : more Philip Webb
2007-10-29 11:27 ` Benno Schulenberg
2007-10-29 19:57 ` Philip Webb
2007-10-29 20:31 ` Benno Schulenberg
2007-10-29 22:02 ` Philip Webb
2007-10-29 23:35 ` Benno Schulenberg
2007-10-30 3:55 ` Philip Webb
2007-10-30 9:45 ` Benno Schulenberg
2007-10-30 13:58 ` James Ausmus
2007-10-31 4:03 ` Philip Webb [this message]
2007-10-31 4:58 ` Dale
2007-10-31 7:10 ` Philip Webb
2007-11-01 8:29 ` Philip Webb
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=20071031040300.GA4634@sympatico.ca \
--to=purslow@sympatico.ca \
--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