Re: upgrading the kernel in debian etch from 2.6.18 to 2.6.29
Joey L a écrit :
>
> make-kpkg -rfakeroot --initrd --revision=custom.1.0 kernel_image
> sudo dpkg -i ../linux-image-2.6.29custom1.0_....deb
>
> Maybe that should sort things out. Let me know if you face further
> problems.
>
>
>
>
> Sorry - i tried to run that command but it gave an error - something
> that rfakeroot is not a command..so i had to look at the man pages and
> came up with:
>
>
> make-kpkg --rootcmd fakeroot --initrd --revision=custom.1.1 kernel_image
>
>
> that is the exact command.
>
> and then did:
> sudo dpkg -i ../linux-image-2.6.29custom1.0_....deb
>
>
> But i still got the error about can finding vg_maingroup which i believe
> is my main filesystem.
>
> I should tell you that i have a mirrored boot drive and then i have a
> raid5 setup where the rest of the operating system is on.
>
> I did go into the /boot directory and deleted the previous files:
> config-2.6.29 initrd.img-2.6.29 System.map-2.6.29 vmlinuz-2.6.29
>
> and then ran:
> make-kpkg --rootcmd fakeroot --initrd --revision=custom.1.1 kernel_image
> dpkg -i ../linux-image-2.6.29custom1.0_....deb
>
> as is.
>
> Is there a way to differeniate between the different kernels i am
> building - but using the same version??
>
> thanks
>
>
>
>
>
fakeroot make-kpkg --initrd --append-to-version -mykernel --revision 1
kernel-image kernel-headers
Change the "mykernel" string and revision number to differentiate your
builds.
You are booting from a lvm it seems, maybe with root on lvm. Do you have
a separate /boot ? Anyway, I take that you have everything needed
installed (lvm2 ?) and your kernel is configured with lvm support.
Another point to check is change in device naming between 2.6.18 and
2.6.29, it's likely that any hd* will become sd* with the new kernel, so
change your /etc/fstab and /boot/grub/menu.lst and /boot/grub/device.map
accordingly.
Tom
Reply to: