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 19:58:59 -0400 [thread overview]
Message-ID: <4A3EC943.3060006@uri.edu> (raw)
In-Reply-To: <200906212305.n5LN5SMc006356@mailserv.unb.ca>
Thank you, David.
David Fellows wrote:
> On Sun, 21 Jun 2009 17:55:15 -0400
> "John P. Burkett" wrote -
>> Drake Donahue wrote:
>>> Burkett asked:
>>>
>>> Should I back up any particular files before doing "emerge
>>> =sys-kernel/gentoo-sources-2.6.22-r2"? You will simply be restoring the
>>> bits that depclean removed.
>>>
>>> No files should need to backed up.
>> Thank you David. Doing
>> emerge =sys-kernel/gentoo-sources-2.6.22-r2
>> produced the following response
>> emerge: there are no ebuilds to satisfy
>> "=sys-kernel/gentoo-sources-2.6.22-r2"
>
> That is true. 2.6.22 has been removed from the portage tree. Your choices are:
> 1) to find some one who still has the 2.6.22-r2 ebuild and the corrresponding
> sources and patches and create an overlay from them, then use that to
> emerge from.
>
> 2) find someone who still has the top level Makefile from 2.6.22-r2 who will
> send it to you. And hope that that is all you are missing.
This appears to be the easiest short term solution. In looking for the
top level Makefile from 2.6.22-r2, do I need to specify that it is to be
used on an amd64 machine or should I expect that any such file might
work on amd64 architecture?
>
> 3) Upgrade to a newer kernel. Presumably the latest stable that is compatible
> with your desired driver version.
>
> Realistically 3 is your only reasonable option. The downside is you will have
> to do a kernel configuration that is consistent with your existing
> configuration.
>
> You will want to read the kernel upgrade guide first.
> http://www.gentoo.org/doc/en/kernel-upgrade.xml
>
> Remember that emerging a kernel source only installs the source files.
> Compiling the kernel is another step. You may already have a suitable kernel
> source emerged. eselect kernel list will show which are emerged as will
> ls -l /usr/src
>
>> I also tried
>> emerge -s gentoo-sources-2.6.22-r2-osmp
>> and a few other variations without finding any ebuilds.
>
> The osmp is a local identifying tag specified by the person that built
> your kernel. The smp probably means symetric multiprocessor. No idea
> what the o stands for.
>
>> Ideas about how to emerge the sources would be very welcome.
>>
>
>
> Dave F
>
>
--
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 23:59 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 [this message]
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=4A3EC943.3060006@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