From: "Norman Rieß" <norman@smash-net.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] ati-drivers: no kernel found?
Date: Thu, 11 Mar 2010 12:09:43 +0100 [thread overview]
Message-ID: <4B98CF77.2030500@smash-net.org> (raw)
In-Reply-To: <20100311115540.3070b471@lx-arnau.pic.es>
Am 03/11/10 11:55, schrieb Arnau Bria:
> On Thu, 11 Mar 2010 11:31:03 +0100
> Norman Rieß wrote:
>
> [...]
>
>> This listing is not a complete kernel set.
>>
> For curiosity, what is missing? make oldconfing?¿
>
>
>> Did you do a emerge --depclean lately?
>>
> yep.
>
>
>> Reemerge you kernel ebuild and do a make oldconfig to be sure.
>>
> I'm with r6 and gentoo-sources is at r10, is it important? do Ihave to
> remerge r6 too?
>
>
>> Then try it again.
>>
>> Norman
>>
> Thanks,
> Arnau
>
>
>
A complete listing looks like this:
bragi linux # ls
arch drivers Kbuild modules.builtin samples usr
block firmware kernel modules.order scripts virt
COPYING fs lib Module.symvers security vmlinux
CREDITS include MAINTAINERS net sound vmlinux.o
crypto init Makefile README System.map
Documentation ipc mm REPORTING-BUGS tools
bragi linux #
Depclean seems to delete some parts of the kernel directory if you have
a newer kernel ebuild available. Had that too, once.
Which release you use r6 or r10 is your choise. r10 is newer with more
security patches and such, so i would say you should use that one.
Do you know how to deal with a kernel update?
Norman
next prev parent reply other threads:[~2010-03-11 11:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-11 10:23 [gentoo-user] ati-drivers: no kernel found? Arnau Bria
2010-03-11 10:31 ` Norman Rieß
2010-03-11 10:55 ` Arnau Bria
2010-03-11 11:09 ` Norman Rieß [this message]
2010-03-11 11:34 ` Arnau Bria
2010-03-11 10:48 ` Neil Bothwick
2010-03-11 11:13 ` Arnau Bria
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=4B98CF77.2030500@smash-net.org \
--to=norman@smash-net.org \
--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