i have the same problem when i built kernel 2.6.14.
and the previous working kernel is 2.6.11 form Fedora Code 4
anyone give me any adviece? thanks
On Thu, 2006-06-15 at 13:35 +0100, Barry Scott wrote:
> On my HP dc7600U having patch around the MCG problem
> I now get a bit further. Previous working kernel was 2.6.16
> from Fedora Code 4.
>
> I see:
>
> Uncompressing Linux... Ok, botinh the kernel.
> Red Hat nash version 4.2.15 starting
> Reading all physical volumes. This may take a while...
> No volume groups found
> Unable to find volume group "VolGroup00"
> ERROR: /bin/lvm exited abnormally with value 5 ! (pid 351)
>
> Then a few more errors and Kernel panic
>
> Where would the problem be?
>
> Barry
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
>
>
freegnu wrote:
> i have the same problem when i built kernel 2.6.14.
> and the previous working kernel is 2.6.11 form Fedora Code 4
>
> anyone give me any adviece? thanks
>
>
> On Thu, 2006-06-15 at 13:35 +0100, Barry Scott wrote:
>
>> On my HP dc7600U having patch around the MCG problem
>> I now get a bit further. Previous working kernel was 2.6.16
>> from Fedora Code 4.
>>
>> I see:
>>
>> Uncompressing Linux... Ok, botinh the kernel.
>> Red Hat nash version 4.2.15 starting
>> Reading all physical volumes. This may take a while...
>> No volume groups found
>> Unable to find volume group "VolGroup00"
>> ERROR: /bin/lvm exited abnormally with value 5 ! (pid 351)
>>
>> Then a few more errors and Kernel panic
>>
>> Where would the problem be?
>>
>> Barry
>>
>>
You have to rebuild the initrd to match the kernel and its modules.
As the kernel develops the initrd scripts need to change to match changes
in modules required to support the disks for the new kernel.
I've no experience with 2.6.11 to 2.6.14. We now use 2.6.21
and know a bit about how to support it on FC4.
What we did to find differences was to run later versions of Fedora Core
that support the kernel we want to use out of the box. Then we break open
the initrd and see what the differences are between the old and new initrd
files.
Barry
yes, i have rebuilt the initrd by the command: /sbin/mkinitrd
--builtin=ata_piix /boot/initrd-2.6.14.img initrd-2.6.14
On Fri, 2007-05-25 at 10:36 +0100, Barry Scott wrote:
> freegnu wrote:
> > i have the same problem when i built kernel 2.6.14.
> > and the previous working kernel is 2.6.11 form Fedora Code 4
> >
> > anyone give me any adviece? thanks
> >
> >
> > On Thu, 2006-06-15 at 13:35 +0100, Barry Scott wrote:
> >
> >> On my HP dc7600U having patch around the MCG problem
> >> I now get a bit further. Previous working kernel was 2.6.16
> >> from Fedora Code 4.
> >>
> >> I see:
> >>
> >> Uncompressing Linux... Ok, botinh the kernel.
> >> Red Hat nash version 4.2.15 starting
> >> Reading all physical volumes. This may take a while...
> >> No volume groups found
> >> Unable to find volume group "VolGroup00"
> >> ERROR: /bin/lvm exited abnormally with value 5 ! (pid 351)
> >>
> >> Then a few more errors and Kernel panic
> >>
> >> Where would the problem be?
> >>
> >> Barry
> >>
> >>
> You have to rebuild the initrd to match the kernel and its modules.
> As the kernel develops the initrd scripts need to change to match changes
> in modules required to support the disks for the new kernel.
> I've no experience with 2.6.11 to 2.6.14. We now use 2.6.21
> and know a bit about how to support it on FC4.
yes, i have rebuilt the initrd by the command:
/sbin/mkinitrd --builtin=ata_piix /boot/initrd-2.6.14.img initrd-2.6.14
>
> What we did to find differences was to run later versions of Fedora Core
> that support the kernel we want to use out of the box. Then we break open
> the initrd and see what the differences are between the old and new initrd
> files.
how did you analysis the differences? the constent of the file is scale
of two.
>
> Barry
>
>