From: Grant <emailgrant@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Problem with xf86-video-ati & nvidia-drivers
Date: Wed, 13 Jul 2011 10:23:47 -0700 [thread overview]
Message-ID: <CAN0CFw2msWocOi6_4aMsnXtJpxddE+sw3CjbbtgjxmZqDX7QMA@mail.gmail.com> (raw)
In-Reply-To: <ivjgho$jf0$1@dough.gmane.org>
>> When I was using an Nvidia video card, I noticed a strange sort of
>> fuzzy edge effect if I used nvidia-drivers. xf86-video-nouveau didn't
>> have the same problem. Now I've switched to an ATI video card and
>> unfortunately I have the same problem with xf86-video-ati. I tried to
>> enable the new modesetting radeon driver in the kernel to see if that
>> would help but it doesn't work with my HD4250 card yet.
>
> It should work. But you need firmware that is not included in the kernel.
> You need to install the x11-drivers/radeon-ucode package, and then build a
> kernel that includes the appropriate firmware. Which firmware file (one of
> the *.bin files in /lib/firmware/radeon) is needed should be printed during
> boot; at the moment the kernel hangs, it should print which firmware file it
> was trying to load.
>
> On my HD4870, I configured it like so:
>
> In "Device Drivers -> Generic Driver Options", I've set:
>
> (radeon/R700_rlc.bin) External firmware blobs to build into the kernel
> binary
> (/lib/firmware) Firmware blobs root directory
You're right. That fixed the stall during kernel load and now KMS works fine.
> Then rebuild and install the kernel. Before you reboot, make sure you have
> built media-libs/mesa with the "gallium" USE flag set, and do an "eselect
> mesa set r600 gallium". Make sure you don't have disabled KMS in the kernel
> command line or module options ("radeon.modeset=0" disables KMS). After you
> reboot, you should have KMS + Gallium3D working.
I've eselected to gallium but is there any benefit if I don't use 3D at all?
- Grant
next prev parent reply other threads:[~2011-07-13 18:10 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-09 23:21 [gentoo-user] Problem with xf86-video-ati & nvidia-drivers Grant
2011-07-10 0:20 ` meino.cramer
2011-07-11 23:48 ` Grant
2011-07-12 22:33 ` Grant
2011-07-13 2:27 ` meino.cramer
2011-07-13 15:55 ` Roger Mason
2011-07-13 16:17 ` meino.cramer
2011-07-13 17:13 ` Grant
2011-07-13 17:38 ` meino.cramer
2011-07-14 19:44 ` Grant
2011-07-14 20:07 ` Michael Mol
2011-07-14 23:29 ` Grant
2011-07-14 20:23 ` [gentoo-user] " Nikos Chantziaras
2011-07-14 23:30 ` Grant
2011-07-17 16:22 ` Grant
2011-07-17 16:47 ` Nikos Chantziaras
2011-07-17 16:54 ` Grant
2011-07-17 21:53 ` Michael Mol
2011-07-17 23:28 ` Grant
2011-07-18 13:18 ` [gentoo-user] " Stroller
2011-07-18 22:52 ` Grant
2011-07-19 0:56 ` Grant
2011-07-19 16:03 ` Daniel Frey
2011-07-19 19:41 ` Grant
2011-07-19 21:00 ` Mick
2011-07-20 18:38 ` Grant
2011-07-20 14:29 ` Stroller
2011-07-20 15:29 ` Michael Mol
2011-07-19 2:01 ` [gentoo-user] " Volker Armin Hemmann
2011-07-19 20:35 ` Grant
2011-07-19 20:54 ` Michael Mol
2011-07-20 21:22 ` Grant
2011-07-13 7:19 ` Nikos Chantziaras
2011-07-13 17:27 ` Grant
2011-07-13 7:13 ` Nikos Chantziaras
2011-07-13 12:25 ` Mick
2011-07-13 14:42 ` Nikos Chantziaras
2011-07-13 16:36 ` Mick
2011-07-16 16:22 ` Mick
2011-07-13 17:23 ` Grant [this message]
2011-07-14 6:13 ` Nikos Chantziaras
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=CAN0CFw2msWocOi6_4aMsnXtJpxddE+sw3CjbbtgjxmZqDX7QMA@mail.gmail.com \
--to=emailgrant@gmail.com \
--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