From: "John P. Burkett" <burkett@uri.edu>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] emerge -eav system failed with ati-drivers
Date: Sun, 21 Jun 2009 14:54:36 -0400 [thread overview]
Message-ID: <4A3E81EC.8080404@uri.edu> (raw)
In-Reply-To: <20090621141712.4a279357@osage.osagesoftware.com>
David Relson wrote:
> On Sun, 21 Jun 2009 13:55:10 -0400
> Drake Donahue wrote:
>
>> <snip>
>>
>> I'm guessing you did an "emerge --depclean" sometime after compiling
>> the 2.6.22-r2 kernel and after emerging a new gentoo-sources that
>> erased your make files, This is something depclean loves to do while
>> leaving 99% of the older kernel source files intact.
>> I think depclean leaves your .config file in place. Been a few weeks
>> since I burned myself last with this one.
>> If you were following directions back in 2007 you should have a
>> stored 2.6.22-r2 config in the /boot directory.
>>
>> Try "emerge =sys-kernel/gentoo-sources-2.6.22-r2 to re-emerge the old
>> package and regain the make files. What the osmp is about beats me.
>>
>> or
>>
>> Emerge a new gentoo-sources, eselect it, configure, compile, install a
>> new (current) kernel.
>
> My understanding is that ati-drivers expects /usr/src/linux to contain
> the source of the currently running kernel.
>
> I'm running a 2.6.28 kernel. I have downloaded 2.6.30 and built that
> but have not yet rebooted. "emerge ati-drivers" failed with 2.6.30
> in /usr/src/linux. Changing directory names allowed ati-drivers to
> build happily.
>
David, thank you for sharing your experience. On my system, doing "uname
-r" gets the response "2.6.22-gentoo-r2-osmp". In my /usr/src/linux
directory I currently have a .config file starting with the lines
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.22-gentoo-r2
# Mon Sep 3 21:48:37 2007
Can you suggest how to change directory names to allow the ati-drivers
to build?
Best regards,
John
> HTH,
>
> David
>
>
--
John P. Burkett
Department of Economics
University of Rhode Island
Kingston, RI 02881-0808
USA
phone (401) 874-9195
next prev parent reply other threads:[~2009-06-21 18: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 [this message]
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 ` [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=4A3E81EC.8080404@uri.edu \
--to=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