From: David Fellows <fellows@unb.ca>
To: gentoo-amd64@lists.gentoo.org, "John P. Burkett" <burkett@uri.edu>
Subject: Re: [gentoo-amd64] emerge -eav system failed with ati-drivers
Date: Mon, 22 Jun 2009 14:54:52 -0300 [thread overview]
Message-ID: <200906221754.n5MHsr1q010698@mailserv.unb.ca> (raw)
In-Reply-To: <4A3FA7FB.3090900@uri.edu>
On Mon, 22 Jun 2009 11:49:15 -0400
"John P. Burkett" wrote -
>
> Thank you, David. The 2.6.22 Makefile I copied from another machine (as
> described in my previous note) starts as follows:
> VERSION = 2
> PATCHLEVEL = 6
> SUBLEVEL = 22
> EXTRAVERSION = -gentoo-r2
> NAME = Holy Dancing Manatees, Batman!
>
> As reported in my last note, putting that in my linux-2.6.22-gentoo-r2
> directory does not suffice to let "emerge ati-drivers" succeed.
>
> My latest experiment was editing the Makefile, changing the fourth line
> from EXTRAVERSION = -gentoo-r2
> to
> EXTRAVERSION = -gentoo-r2-osmp
>
> After making that change, I again tried
> emerge ati-drivers
>
> The response was the familiar
> * Found kernel source directory:
> * /usr/src/linux
> * Could not detect kernel version.
> * Please ensure that /usr/src/linux points to a complete set of Linux
> sources.
> *
> * ERROR: x11-drivers/ati-drivers-8.552-r2 failed.
>
> I wonder why "emerge ati-drivers" still does not detect the kernel version.
>
Don't really know.
You have verified that /usr/src/linux is a symlink to linux-2.6.22-gentoo-r2
haven't you?
If the top level MAkefile is missing, there could be any number of other files
missing.
You might look in /usr/portage/distfiles to see if you still have the
distributioon files
ls linux* and look for 2.6.22 and ls genpat* and likewise.
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.
I am afreaid I have runn out of advice.
Dave F
next prev parent reply other threads:[~2009-06-22 17:54 UTC|newest]
Thread overview: 25+ 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 [this message]
2009-06-22 22:59 ` John P. Burkett
2009-06-23 3:25 ` [gentoo-amd64] " Duncan
2009-06-22 14:00 ` [gentoo-amd64] " 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-22 0:44 John P. Burkett
2009-06-20 23:01 John P. Burkett
2009-06-21 4:49 ` Drake Donahue
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=200906221754.n5MHsr1q010698@mailserv.unb.ca \
--to=fellows@unb.ca \
--cc=burkett@uri.edu \
--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