From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] [OT] (sort of) strange things after upgrading the kernel
Date: Fri, 12 Oct 2012 22:13:19 -0500 [thread overview]
Message-ID: <5078DC4F.4080403@gmail.com> (raw)
In-Reply-To: <CAHH9eM6OoYFyBQa14gm5ToBciSCA=yMmUNtbzo0j3eiTjpt4TQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3070 bytes --]
Francisco Ares wrote:
>
> 2012/10/12 Dale <rdalek1967@gmail.com <mailto:rdalek1967@gmail.com>>
>
> Francisco Ares wrote:
> >
> >
> > Thanks for your reply, Dale.
> >
> > Yes, everything works as expected when using the old kernel.
> >
> > I decided to re-emerge some base libraries, and nothing worked,
> until
> > I remembered to re-emerge udev. After the build, it announced two
> > wrong lines in the new kernel "config" file:
> >
> > CONFIG_SYSFS_DEPRECATED=y
> > CONFIG_SYSFS_DEPRECATED_V2=y
> >
> > After correcting them and building the kernel again, now
> everything is
> > back to normal.
> >
> > Thanks again
> > Francisco
> >
> >
> > --
> > "If you have an apple and I have an apple and we exchange apples
> then
> > you and I will still each have one apple. But if you have an
> idea and
> > I have one idea and we exchange these ideas, then each of us
> will have
> > two ideas." - George Bernard Shaw
>
>
> Do you use oldconfig or build each one from scratch? I use
> oldconfig so
> that I at least have what I know works. It's just a matter of if
> I need
> anything new enabled. Some claim oldconfig shouldn't be used but
> I have
> only had it to fail once in the last 10 years or so. Most everyone I
> know of uses oldconfig.
>
> Glad you got it going tho.
>
> Dale
>
> :-) :-)
>
> --
> I am only responsible for what I said ... Not for what you
> understood or how you interpreted my words!
>
>
>
>
> I normally also use oldconfig. I think there might be a reason for it
> to be around. But this time I didn't, because the old kernel was
> version 2.6.39 and I thought oldconfig would mess things up more than
> help on the new 3.4.9. Don't know how right or wrong is this
> assumption, though.
>
> I just was lazy to upgrade the kernel, as it takes an hour or so to
> check most of menucofig.
>
> Francisco
>
I would have tried it but that is a LOT of updates. It may be faster to
start from scratch in that case. I know a few years ago there was some
changes that kept oldconfig from working as it should. That was the
only time it failed me but I do upgrade more often to avoid this sort of
thing. I try to upgrade every couple months. Now if I have long
uptimes, I may not actually ever use that kernel but I have a config
file to copy over that is a bit more up to date.
I would suggest printing or something the output of the following:
lspci -k That tells you what you need for your hardware, that is of
course from a kernel where all your hardware works. There may be some
specific things for certain software that is needed but at least you can
boot up and have a system to work with. I usually leave the rest to
defaults unless I am sure there is something I don't need.
Glad you got it sorted out and working tho.
Dale
:-) :-)
--
I am only responsible for what I said ... Not for what you understood or how you interpreted my words!
[-- Attachment #2: Type: text/html, Size: 4745 bytes --]
next prev parent reply other threads:[~2012-10-13 3:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHH9eM5+7aCQHe59tvhfSCzX6uAhCHP-7wjQ55YH_irxwoKvMg@mail.gmail.com>
2012-10-12 21:20 ` [gentoo-user] [OT] (sort of) strange things after upgrading the kernel Francisco Ares
2012-10-12 21:56 ` Dale
2012-10-13 1:50 ` Francisco Ares
2012-10-13 2:22 ` Dale
2012-10-13 2:42 ` Francisco Ares
2012-10-13 3:13 ` Dale [this message]
2012-10-14 13:36 ` Francisco Ares
2012-10-14 14:46 ` Dale
2012-10-14 21:54 ` Peter Humphrey
2012-10-14 22:33 ` Dale
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=5078DC4F.4080403@gmail.com \
--to=rdalek1967@gmail.com \
--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