|
Home > Archive > Red Hat Kernel > January 2004 > Re: 2.4.20-20.9 upgrade problem
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Re: 2.4.20-20.9 upgrade problem
|
|
| J.O. Aho 2004-01-23, 7:26 pm |
| Henrik Schack Jensen wrote:quote:
> Hi
> Have just tried to upgrade a Netfinity 5000 with Serveraid controller to
> the 2.4.20-20.9 kernel, hmm no big success the ramdisk image seems to be
> missing a lot of drivers including the Serveraid driver :-(
> Any clues on why all these drivers where ripped of the ramdisk, and what
> to do ?
man mkinitrd
| |
| J.O. Aho 2004-01-23, 7:26 pm |
| Henrik Schack Jensen wrote:quote:
> Hi
> Have just tried to upgrade a Netfinity 5000 with Serveraid controller to
> the 2.4.20-20.9 kernel, hmm no big success the ramdisk image seems to be
> missing a lot of drivers including the Serveraid driver :-(
> Any clues on why all these drivers where ripped of the ramdisk, and what
> to do ?
man mkinitrd
| |
| Henrik Schack Jensen 2004-01-23, 7:26 pm |
| Well yes, I know I kan make my own ramdisk image, but usually the one
provided by RedHat is working fine, why did the change it ?
J.O. Aho wrote:quote:
> Henrik Schack Jensen wrote:
>
>
>
> man mkinitrd
>
>
| |
| Henrik Schack Jensen 2004-01-23, 7:26 pm |
| Well yes, I know I kan make my own ramdisk image, but usually the one
provided by RedHat is working fine, why did the change it ?
J.O. Aho wrote:quote:
> Henrik Schack Jensen wrote:
>
>
>
> man mkinitrd
>
>
| |
| J.O. Aho 2004-01-23, 7:26 pm |
| Henrik Schack Jensen wrote:quote:
> Hi
> Have just tried to upgrade a Netfinity 5000 with Serveraid controller to
> the 2.4.20-20.9 kernel, hmm no big success the ramdisk image seems to be
> missing a lot of drivers including the Serveraid driver :-(
> Any clues on why all these drivers where ripped of the ramdisk, and what
> to do ?
man mkinitrd
| |
| Henrik Schack Jensen 2004-01-23, 7:26 pm |
| Well yes, I know I kan make my own ramdisk image, but usually the one
provided by RedHat is working fine, why did the change it ?
J.O. Aho wrote:quote:
> Henrik Schack Jensen wrote:
>
>
>
> man mkinitrd
>
>
| |
| Boris Glawe 2004-01-23, 7:26 pm |
| J.O. Aho wrote:quote:
> Henrik Schack Jensen wrote:
>
>
>
> I'm not sure if the image is premade or if it's created during the
> installation of the kernel rpm. Have you checked if the driver is
> included in the new kernel? I know that RedHat has decided to lessen the
> number of drivers in the default kernels and then include an additional
> rpm with "unsupported" drivers (unsupported by redhat).
>
>
> //Aho
>
rpm -qlp kernel-2.4.20-20.9.i686.rpm | grep initrd
does not return any results... so it seems to be created during installation.
maybe something went wrong then.
| |
| Boris Glawe 2004-01-23, 7:26 pm |
| J.O. Aho wrote:quote:
> Henrik Schack Jensen wrote:
>
>
>
> I'm not sure if the image is premade or if it's created during the
> installation of the kernel rpm. Have you checked if the driver is
> included in the new kernel? I know that RedHat has decided to lessen the
> number of drivers in the default kernels and then include an additional
> rpm with "unsupported" drivers (unsupported by redhat).
>
>
> //Aho
>
rpm -qlp kernel-2.4.20-20.9.i686.rpm | grep initrd
does not return any results... so it seems to be created during installation.
maybe something went wrong then.
| |
| Henrik Schack Jensen 2004-01-23, 7:26 pm |
| Hmm I'll check that, thanx
/Henrik
Boris Glawe wrote:quote:
> J.O. Aho wrote:
>
>
> rpm -qlp kernel-2.4.20-20.9.i686.rpm | grep initrd
>
> does not return any results... so it seems to be created during
> installation. maybe something went wrong then.
>
| |
| Henrik Schack Jensen 2004-01-23, 7:26 pm |
| Hmm I'll check that, thanx
/Henrik
Boris Glawe wrote:quote:
> J.O. Aho wrote:
>
>
> rpm -qlp kernel-2.4.20-20.9.i686.rpm | grep initrd
>
> does not return any results... so it seems to be created during
> installation. maybe something went wrong then.
>
| |
| Boris Glawe 2004-01-23, 7:26 pm |
| J.O. Aho wrote:quote:
> Henrik Schack Jensen wrote:
>
>
>
> I'm not sure if the image is premade or if it's created during the
> installation of the kernel rpm. Have you checked if the driver is
> included in the new kernel? I know that RedHat has decided to lessen the
> number of drivers in the default kernels and then include an additional
> rpm with "unsupported" drivers (unsupported by redhat).
>
>
> //Aho
>
rpm -qlp kernel-2.4.20-20.9.i686.rpm | grep initrd
does not return any results... so it seems to be created during installation.
maybe something went wrong then.
| |
| Henrik Schack Jensen 2004-01-23, 7:26 pm |
| Hmm I'll check that, thanx
/Henrik
Boris Glawe wrote:quote:
> J.O. Aho wrote:
>
>
> rpm -qlp kernel-2.4.20-20.9.i686.rpm | grep initrd
>
> does not return any results... so it seems to be created during
> installation. maybe something went wrong then.
>
| |
|
| On Wed, 27 Aug 2003 19:38:15 +0200, the right honourable Henrik Schack
Jensen <schack@tdconline.dk> wrote:
[QUOTE][color=darkred]
>Well yes, I know I kan make my own ramdisk image, but usually the one
>provided by RedHat is working fine, why did the change it ?
>
>
>J.O. Aho wrote:
I had the same problem, building my 2.4.22 kernel yesterday.
Seems you have to explicitly tell "make" to do it.
in "make menuconfig" you'll find the setting under "block devices"
Right now, as I type this, my RH9 box is building a kernel. I expect
an initrd image to appear in /boot.
On the RH site they mention this:
http://www.redhat.com/docs/manuals/...nel-initrd.html
If you do not work from the RPM package, it's not made automagically I
think.
Another thing I bumped into, is the disappearance of the include/asm
symlink.
It's erased by "make mrproper" and is should be build up again by the
Makefile.
Always follow the right order:
make clean
make mrproper
make menuconfig
make dep &> /home/you/make_dep.log
make bzImage &> /home/you/make_image.log
etc.
save your own configuration (result after make menuconfig) in you own
file. menuconfig has an option for that, eg. in your_kernel.config.
save it on a floppy for later.
just before doing "make menuconfig" (which uses .config for it's
suggestions) , you do
cp your_kernel_config .config
I'm new to this all, so check everything I said.
frgr
Erik
| |
|
| On Wed, 27 Aug 2003 19:38:15 +0200, the right honourable Henrik Schack
Jensen <schack@tdconline.dk> wrote:
[QUOTE][color=darkred]
>Well yes, I know I kan make my own ramdisk image, but usually the one
>provided by RedHat is working fine, why did the change it ?
>
>
>J.O. Aho wrote:
I had the same problem, building my 2.4.22 kernel yesterday.
Seems you have to explicitly tell "make" to do it.
in "make menuconfig" you'll find the setting under "block devices"
Right now, as I type this, my RH9 box is building a kernel. I expect
an initrd image to appear in /boot.
On the RH site they mention this:
http://www.redhat.com/docs/manuals/...nel-initrd.html
If you do not work from the RPM package, it's not made automagically I
think.
Another thing I bumped into, is the disappearance of the include/asm
symlink.
It's erased by "make mrproper" and is should be build up again by the
Makefile.
Always follow the right order:
make clean
make mrproper
make menuconfig
make dep &> /home/you/make_dep.log
make bzImage &> /home/you/make_image.log
etc.
save your own configuration (result after make menuconfig) in you own
file. menuconfig has an option for that, eg. in your_kernel.config.
save it on a floppy for later.
just before doing "make menuconfig" (which uses .config for it's
suggestions) , you do
cp your_kernel_config .config
I'm new to this all, so check everything I said.
frgr
Erik
| |
|
| On Wed, 27 Aug 2003 19:38:15 +0200, the right honourable Henrik Schack
Jensen <schack@tdconline.dk> wrote:
[QUOTE][color=darkred]
>Well yes, I know I kan make my own ramdisk image, but usually the one
>provided by RedHat is working fine, why did the change it ?
>
>
>J.O. Aho wrote:
I had the same problem, building my 2.4.22 kernel yesterday.
Seems you have to explicitly tell "make" to do it.
in "make menuconfig" you'll find the setting under "block devices"
Right now, as I type this, my RH9 box is building a kernel. I expect
an initrd image to appear in /boot.
On the RH site they mention this:
http://www.redhat.com/docs/manuals/...nel-initrd.html
If you do not work from the RPM package, it's not made automagically I
think.
Another thing I bumped into, is the disappearance of the include/asm
symlink.
It's erased by "make mrproper" and is should be build up again by the
Makefile.
Always follow the right order:
make clean
make mrproper
make menuconfig
make dep &> /home/you/make_dep.log
make bzImage &> /home/you/make_image.log
etc.
save your own configuration (result after make menuconfig) in you own
file. menuconfig has an option for that, eg. in your_kernel.config.
save it on a floppy for later.
just before doing "make menuconfig" (which uses .config for it's
suggestions) , you do
cp your_kernel_config .config
I'm new to this all, so check everything I said.
frgr
Erik
| |
| J.O. Aho 2004-01-23, 7:26 pm |
| Henrik Schack Jensen wrote:quote:
> Hi
> Have just tried to upgrade a Netfinity 5000 with Serveraid controller to
> the 2.4.20-20.9 kernel, hmm no big success the ramdisk image seems to be
> missing a lot of drivers including the Serveraid driver :-(
> Any clues on why all these drivers where ripped of the ramdisk, and what
> to do ?
man mkinitrd
| |
| Henrik Schack Jensen 2004-01-23, 7:26 pm |
| Well yes, I know I kan make my own ramdisk image, but usually the one
provided by RedHat is working fine, why did the change it ?
J.O. Aho wrote:quote:
> Henrik Schack Jensen wrote:
>
>
>
> man mkinitrd
>
>
| |
| Boris Glawe 2004-01-23, 7:26 pm |
| J.O. Aho wrote:quote:
> Henrik Schack Jensen wrote:
>
>
>
> I'm not sure if the image is premade or if it's created during the
> installation of the kernel rpm. Have you checked if the driver is
> included in the new kernel? I know that RedHat has decided to lessen the
> number of drivers in the default kernels and then include an additional
> rpm with "unsupported" drivers (unsupported by redhat).
>
>
> //Aho
>
rpm -qlp kernel-2.4.20-20.9.i686.rpm | grep initrd
does not return any results... so it seems to be created during installation.
maybe something went wrong then.
| |
| Henrik Schack Jensen 2004-01-23, 7:26 pm |
| Hmm I'll check that, thanx
/Henrik
Boris Glawe wrote:quote:
> J.O. Aho wrote:
>
>
> rpm -qlp kernel-2.4.20-20.9.i686.rpm | grep initrd
>
> does not return any results... so it seems to be created during
> installation. maybe something went wrong then.
>
| |
|
| On Wed, 27 Aug 2003 19:38:15 +0200, the right honourable Henrik Schack
Jensen <schack@tdconline.dk> wrote:
[QUOTE][color=darkred]
>Well yes, I know I kan make my own ramdisk image, but usually the one
>provided by RedHat is working fine, why did the change it ?
>
>
>J.O. Aho wrote:
I had the same problem, building my 2.4.22 kernel yesterday.
Seems you have to explicitly tell "make" to do it.
in "make menuconfig" you'll find the setting under "block devices"
Right now, as I type this, my RH9 box is building a kernel. I expect
an initrd image to appear in /boot.
On the RH site they mention this:
http://www.redhat.com/docs/manuals/...nel-initrd.html
If you do not work from the RPM package, it's not made automagically I
think.
Another thing I bumped into, is the disappearance of the include/asm
symlink.
It's erased by "make mrproper" and is should be build up again by the
Makefile.
Always follow the right order:
make clean
make mrproper
make menuconfig
make dep &> /home/you/make_dep.log
make bzImage &> /home/you/make_image.log
etc.
save your own configuration (result after make menuconfig) in you own
file. menuconfig has an option for that, eg. in your_kernel.config.
save it on a floppy for later.
just before doing "make menuconfig" (which uses .config for it's
suggestions) , you do
cp your_kernel_config .config
I'm new to this all, so check everything I said.
frgr
Erik
| |
| J.O. Aho 2004-01-23, 7:26 pm |
| Henrik Schack Jensen wrote:quote:
> Hi
> Have just tried to upgrade a Netfinity 5000 with Serveraid controller to
> the 2.4.20-20.9 kernel, hmm no big success the ramdisk image seems to be
> missing a lot of drivers including the Serveraid driver :-(
> Any clues on why all these drivers where ripped of the ramdisk, and what
> to do ?
man mkinitrd
| |
| Henrik Schack Jensen 2004-01-23, 7:26 pm |
| Well yes, I know I kan make my own ramdisk image, but usually the one
provided by RedHat is working fine, why did the change it ?
J.O. Aho wrote:quote:
> Henrik Schack Jensen wrote:
>
>
>
> man mkinitrd
>
>
| |
| Boris Glawe 2004-01-23, 7:26 pm |
| J.O. Aho wrote:quote:
> Henrik Schack Jensen wrote:
>
>
>
> I'm not sure if the image is premade or if it's created during the
> installation of the kernel rpm. Have you checked if the driver is
> included in the new kernel? I know that RedHat has decided to lessen the
> number of drivers in the default kernels and then include an additional
> rpm with "unsupported" drivers (unsupported by redhat).
>
>
> //Aho
>
rpm -qlp kernel-2.4.20-20.9.i686.rpm | grep initrd
does not return any results... so it seems to be created during installation.
maybe something went wrong then.
| |
| Henrik Schack Jensen 2004-01-23, 7:26 pm |
| Hmm I'll check that, thanx
/Henrik
Boris Glawe wrote:quote:
> J.O. Aho wrote:
>
>
> rpm -qlp kernel-2.4.20-20.9.i686.rpm | grep initrd
>
> does not return any results... so it seems to be created during
> installation. maybe something went wrong then.
>
| |
|
| On Wed, 27 Aug 2003 19:38:15 +0200, the right honourable Henrik Schack
Jensen <schack@tdconline.dk> wrote:
[QUOTE][color=darkred]
>Well yes, I know I kan make my own ramdisk image, but usually the one
>provided by RedHat is working fine, why did the change it ?
>
>
>J.O. Aho wrote:
I had the same problem, building my 2.4.22 kernel yesterday.
Seems you have to explicitly tell "make" to do it.
in "make menuconfig" you'll find the setting under "block devices"
Right now, as I type this, my RH9 box is building a kernel. I expect
an initrd image to appear in /boot.
On the RH site they mention this:
http://www.redhat.com/docs/manuals/...nel-initrd.html
If you do not work from the RPM package, it's not made automagically I
think.
Another thing I bumped into, is the disappearance of the include/asm
symlink.
It's erased by "make mrproper" and is should be build up again by the
Makefile.
Always follow the right order:
make clean
make mrproper
make menuconfig
make dep &> /home/you/make_dep.log
make bzImage &> /home/you/make_image.log
etc.
save your own configuration (result after make menuconfig) in you own
file. menuconfig has an option for that, eg. in your_kernel.config.
save it on a floppy for later.
just before doing "make menuconfig" (which uses .config for it's
suggestions) , you do
cp your_kernel_config .config
I'm new to this all, so check everything I said.
frgr
Erik
| |
| J.O. Aho 2004-01-23, 7:28 pm |
| Henrik Schack Jensen wrote:quote:
> Hi
> Have just tried to upgrade a Netfinity 5000 with Serveraid controller to
> the 2.4.20-20.9 kernel, hmm no big success the ramdisk image seems to be
> missing a lot of drivers including the Serveraid driver :-(
> Any clues on why all these drivers where ripped of the ramdisk, and what
> to do ?
man mkinitrd
| |
| Henrik Schack Jensen 2004-01-23, 7:28 pm |
| Well yes, I know I kan make my own ramdisk image, but usually the one
provided by RedHat is working fine, why did the change it ?
J.O. Aho wrote:quote:
> Henrik Schack Jensen wrote:
>
>
>
> man mkinitrd
>
>
| |
| Boris Glawe 2004-01-23, 7:28 pm |
| J.O. Aho wrote:quote:
> Henrik Schack Jensen wrote:
>
>
>
> I'm not sure if the image is premade or if it's created during the
> installation of the kernel rpm. Have you checked if the driver is
> included in the new kernel? I know that RedHat has decided to lessen the
> number of drivers in the default kernels and then include an additional
> rpm with "unsupported" drivers (unsupported by redhat).
>
>
> //Aho
>
rpm -qlp kernel-2.4.20-20.9.i686.rpm | grep initrd
does not return any results... so it seems to be created during installation.
maybe something went wrong then.
| |
| Henrik Schack Jensen 2004-01-23, 7:28 pm |
| Hmm I'll check that, thanx
/Henrik
Boris Glawe wrote:quote:
> J.O. Aho wrote:
>
>
> rpm -qlp kernel-2.4.20-20.9.i686.rpm | grep initrd
>
> does not return any results... so it seems to be created during
> installation. maybe something went wrong then.
>
| |
|
| On Wed, 27 Aug 2003 19:38:15 +0200, the right honourable Henrik Schack
Jensen <schack@tdconline.dk> wrote:
[QUOTE][color=darkred]
>Well yes, I know I kan make my own ramdisk image, but usually the one
>provided by RedHat is working fine, why did the change it ?
>
>
>J.O. Aho wrote:
I had the same problem, building my 2.4.22 kernel yesterday.
Seems you have to explicitly tell "make" to do it.
in "make menuconfig" you'll find the setting under "block devices"
Right now, as I type this, my RH9 box is building a kernel. I expect
an initrd image to appear in /boot.
On the RH site they mention this:
http://www.redhat.com/docs/manuals/...nel-initrd.html
If you do not work from the RPM package, it's not made automagically I
think.
Another thing I bumped into, is the disappearance of the include/asm
symlink.
It's erased by "make mrproper" and is should be build up again by the
Makefile.
Always follow the right order:
make clean
make mrproper
make menuconfig
make dep &> /home/you/make_dep.log
make bzImage &> /home/you/make_image.log
etc.
save your own configuration (result after make menuconfig) in you own
file. menuconfig has an option for that, eg. in your_kernel.config.
save it on a floppy for later.
just before doing "make menuconfig" (which uses .config for it's
suggestions) , you do
cp your_kernel_config .config
I'm new to this all, so check everything I said.
frgr
Erik
|
|
|
|
|