Francisco Ares wrote: > > 2012/10/12 Dale <rdalek1...@gmail.com <mailto:rdalek1...@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!
