|
|
|
|
| Kernel Upgrade for AMD64 fails |
|
|
|
[Original]
[Print]
[Top]
|
I bet I'm not the 1st one running into this problem.
Trying to upgrade my kernel on my well running amd64 box from 2.6.10 to
2.6.15* just fails. Booting looks fine but running sysinit shows obscure
errors like "special device /dev/hda2 does not exist" (but /dev/hda1 is
already mounted as boot partition), claims about not being able to access
the hardware clock and so on. I've checked any option in the kernel but
obviously missed something. The kernel is mostly autmatigalley generated by
make oldconfig from 2.6.10.
The old kernel runs well on exactly the same system, the system updated to
the newest ebuilds. All my other x86 boxes runs also well.
Any help?
TiA,
Jan
|
|
|
[Original]
[Print]
[Top]
|
|
[Original]
[Print]
[Top]
|
Jan Schubert wrote:
I bet I'm not the 1st one running into this problem.
Trying to upgrade my kernel on my well running amd64 box from 2.6.10 to
2.6.15* just fails. Booting looks fine but running sysinit shows obscure
errors like "special device /dev/hda2 does not exist" (but /dev/hda1 is
already mounted as boot partition), claims about not being able to access
the hardware clock and so on. I've checked any option in the kernel but
obviously missed something. The kernel is mostly autmatigalley generated by
make oldconfig from 2.6.10.
Oe thing that comes inmind is that you are using devfs in your 2.6.10, since
2.6.13 kernel don't any more support it and require that you use udev.
Some experimental udev versions have been broken too, if you happen to use
unstable, I do recommend you go back on stable for udev.
//Aho
|
|
|
[Original]
[Print]
[Top]
|
|
[Original]
[Print]
[Top]
|
On Saturday 28 January 2006 11:59, Jan Schubert stood up and spoke the
following words to the masses in /alt.os.linux.gentoo...:/
I bet I'm not the 1st one running into this problem.
Trying to upgrade my kernel on my well running amd64 box from 2.6.10
to 2.6.15* just fails. Booting looks fine but running sysinit shows
obscure errors like "special device /dev/hda2 does not exist" (but
/dev/hda1 is already mounted as boot partition), claims about not
being able to access the hardware clock and so on. I've checked any
option in the kernel but obviously missed something. The kernel is
mostly autmatigalley generated by make oldconfig from 2.6.10.
The old kernel runs well on exactly the same system, the system
updated to the newest ebuilds. All my other x86 boxes runs also well.
Any help?
If I were you, I would configure the kernel manually this time, not by
means of /oldconfig./
A lot has changed since 2.6.10 and things have been moved around in the
kernel configuration options. It's therefore quite possible that your
method of configuration has skipped something here and there.
Try a...:
make menuconfig
.... or...
make xconfig
.... or ...
make gconfig
.... and make sure that the correct options are set for your hardware
clock and so on.
I would also suggest using 2.6.15.1, which includes a number of bugfixes
versus 2.6.15.
Hope this helps... ;-)
--
With kind regards,
*Aragorn*
(Registered GNU/Linux user # 223157)
|
|
|
[Original]
[Print]
[Top]
|
|
[Original]
[Print]
[Top]
|
J.O. Aho wrote:
Some experimental udev versions have been broken too, if you happen to use
unstable, I do recommend you go back on stable for udev.
Just emerged 0.79-r1 instead of the previous 0.81-r1. Will give it a try
right now.
Thx,
Jan
--
"Lasst uns mehr Freiheit wagen!" - Angela Merkel, 30.11.2005
|
|
|
[Original]
[Print]
[Top]
|
|
[Original]
[Print]
[Top]
|
Aragorn wrote:
If I were you, I would configure the kernel manually this time, not by
means of /oldconfig./
I usually go over it afterwards. So I think I'm fine in here. But indeed,
there has been a lot of changes :-).
Thx a lot,
Jan
--
"Lasst uns mehr Freiheit wagen!" - Angela Merkel, 30.11.2005
|
|
[Original]
[Print]
[Top]
|
|
[Original]
[Print]
[Top]
|
Jan Schubert wrote:
Just emerged 0.79-r1 instead of the previous 0.81-r1. Will give it a try
right now.
Ah, gotya :-). Nit sure what has done the trick, but I enabled
CONFIG_HOTPLUG and set RC_DEVICE_TARBALL to yes in rc.
I'm fine now. Thx a lot,
Jan
|
|
[Original]
[Print]
[Top]
|
|
[Original]
[Print]
[Top]
|
Jan Schubert wrote:
Jan Schubert wrote:
Just emerged 0.79-r1 instead of the previous 0.81-r1. Will give it a try
right now.
Ah, gotya :-). Nit sure what has done the trick, but I enabled
CONFIG_HOTPLUG and set RC_DEVICE_TARBALL to yes in rc.
If you don't have CONFIG_HOTPLUG enabled, udev won't work, and you won't
have any device nodes. If you have it enabled, you shouldn't need
RC_DEVICE_TARBALL.
|
|
|
[Original]
[Print]
[Top]
|
|
|
The content of this page is collected from Linux Forum, All copyrights and other associated rights are reserved by the original authors of the articles.