From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64] Re: emerge -eav system failed with ati-drivers
Date: Tue, 23 Jun 2009 03:25:35 +0000 (UTC) [thread overview]
Message-ID: <pan.2009.06.23.03.25.34@cox.net> (raw)
In-Reply-To: 200906221754.n5MHsr1q010698@mailserv.unb.ca
David Fellows <fellows@unb.ca> posted
200906221754.n5MHsr1q010698@mailserv.unb.ca, excerpted below, on Mon, 22
Jun 2009 14:54:52 -0300:
> If you do at least you could recreate the patched source tree manually.
> First rename your existing linux-2.6.22-gentoo-r2 to something else.
>
> After you unpack and apply patches, copy your .config file into the new.
> make oldconfig, make and so on. Install this kernel into /boot and
> update grub accordingly. Boot into it. emerge your ati driver.
The mainline/Linus/kernel.org 2.6.22 kernel is always available from
kernel.org. Gentoo's gentoo-sources kernel is described as "lightly
patched", so the unpatched kernel.org kernel would probably work. I've
always used mainline, here, and always handled the kernel myself as well,
since I knew how to do it already in Mandrake, when I switched.
If the Gentoo patches are needed or you want to use the ebuild, both it
and the Gentoo patches should be available from the Gentoo source
repository.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2009-06-23 3:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-21 17:47 [gentoo-amd64] emerge -eav system failed with ati-drivers John P. Burkett
2009-06-21 17:55 ` Drake Donahue
2009-06-21 18:17 ` David Relson
2009-06-21 18:54 ` John P. Burkett
2009-06-21 19:10 ` David Relson
2009-06-21 19:19 ` John P. Burkett
2009-06-21 20:10 ` David Relson
2009-06-21 20:48 ` Drake Donahue
2009-06-21 21:55 ` John P. Burkett
2009-06-21 23:05 ` David Fellows
2009-06-21 23:13 ` Mark Knecht
2009-06-21 23:58 ` John P. Burkett
2009-06-22 14:19 ` David Fellows
2009-06-22 15:49 ` John P. Burkett
2009-06-22 17:54 ` David Fellows
2009-06-22 22:59 ` John P. Burkett
2009-06-23 3:25 ` Duncan [this message]
2009-06-22 14:00 ` John P. Burkett
2009-06-21 23:19 ` [gentoo-amd64] " Duncan
2009-06-22 0:02 ` John P. Burkett
2009-06-22 0:46 ` David Relson
2009-06-21 18:40 ` [gentoo-amd64] " John P. Burkett
-- strict thread matches above, loose matches on Subject: below --
2009-06-20 23:01 John P. Burkett
2009-06-20 23:17 ` [gentoo-amd64] " Nikos Chantziaras
2009-06-21 1:26 ` Duncan
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=pan.2009.06.23.03.25.34@cox.net \
--to=1i5t5.duncan@cox.net \
--cc=gentoo-amd64@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