[Feisty]no way to install kernel 2-6-20-14 on AMD 64 machine

after some update though adept still the same problem when coming to the installation of kernel 2-6-20-14-23 ; hereafter attached is what I get from synaptic when trying to install linux-image-2.6.20-14-generic :

Sélection du paquet linux-image-2.6.20-14-generic précédemment désélectionné.
(Lecture de la base de données... 219822 fichiers et répertoires déjà installés.)
Dépaquetage de linux-image-2.6.20-14-generic (à partir de .../linux-image-2.6.20-14-generic_2.6.20-14.23_amd64.deb) ...
Done.
Paramétrage de linux-image-2.6.20-14-generic (2.6.20-14.23) ...
Running depmod.
update-initramfs: Generating /boot/initrd.img-2.6.20-14-generic
The provided postinst hook script [/sbin/update-grub] could not be run.
dpkg : erreur de traitement de linux-image-2.6.20-14-generic (--configure) :
 le sous-processus post-installation script a retourné une erreur de sortie d'état 2
Des erreurs ont été rencontrées pendant l'exécution :
 linux-image-2.6.20-14-generic
E: Sub-process /usr/bin/dpkg returned an error code (1)
Un paquet n'a pas pu être installé. Tentative de récupération :
Paramétrage de linux-image-2.6.20-14-generic (2.6.20-14.23) ...
Running depmod.
update-initramfs: Generating /boot/initrd.img-2.6.20-14-generic
The provided postinst hook script [/sbin/update-grub] could not be run.
dpkg : erreur de traitement de linux-image-2.6.20-14-generic (--configure) :
 le sous-processus post-installation script a retourné une erreur de sortie d'état 2
I am using lilo and this bug may be related to the fact that grub is not found I will try to switch back to grub and report waht I am to after this new try.
Regards

Actually there was a grub issue which is unormal as to the installation of a kernel ; I switched from lilo to grub ; now it starts booting but stops with no error messages ; the last lines displayed in console do no help to understand the problem ; I tried to remove and reinstall this kernel but I am still facing the same issue.

I think I will wait for the next kernel to be proposed as an update and then decide what to do.
Regards.

I have installed in parallel Feisty from a CD (Beta version) ; in this case kernel 2-6-20-15 is booting with no problem ; I am really puzzled ; basically the main difference between the 2 installation is that :
- with upgrade procedure (update_manager) the main / partition (here /dev/sda1 SATA HD) is not reformatted,
- with fresh installation / partition (here /dev/hda1 SATA HD) is reformatted.

With the upgraded distro the only kernel booting sofar is 2-6-17-10 from Edgy ; any freshsly installed kernel such as 2-6-20-15 may use modules not compatible with the partition as is ?

What I can try to do is copy /dev/sda1 on another freshly formatted partition and change accordingly fstab and check whether my upgraded distro is then bootable with kernel 2-6-20-15.

Some comments on all this would be greatly apreciated.

To be further investigated

This works for me:
$ sudo mv /sbin/update-grub /sbin/update-grub-backup
$ sudo ln -s /usr/sbin/update-grub.real /sbin/update-grub

I am processing this answer message from a freshly installed Feisty on hda1, hda2 and hda3 partitions ; for the time being no way to boot any kernel from up-dated Edgy installed on sda1, sda3 and sda6 partitions even with kernel 2.6.17-10 which is left from Edgy ; it is really difficult to undestand what is going on as after some various tries and modification as I have related for this past days ; I had a few correct boot sessions until again the same problems reapear all of them stopping the boot ; I think now it has to be with fsck not compatible with old partitions but I am not sure ; I will to try your GRUB solutions though I do not beleive it is a fix because it has to do only with boot loader installation and even with LILO I cannot boot ; anyways if you know how I can apply your fix to my bugged updated Feisty from this current feisty I will proceed.

Globally on AMD 64 machines it is a real disaster at least on updated Edgy ; I was really suprised that after reporting bugs from pre-released Feisty I never got any update when Feisty was released on 19 04 2007 as they had not made any corrections !
Regards.

joorus as expecyted this trick :
$ sudo mv /sbin/update-grub /sbin/update-grub-backup
$ sudo ln -s /usr/sbin/update-grub.real /sbin/update-grub
does not work on my up-graded FEdgy to Feisty ; by the way where did yo get this information.

I still think the problem is related to a combination fsck ATA disks as my updraded distro is installed on SATA HD where Edgy worked fine until I upgraded ; I am on AMD 64 machine and I do not know whether this is also a problem on i-586 machines with SATA HD.
Thanks for you help anyways.

i had found an error in "/sbin/update-grub" script. I've found that this script redirect to "/usr/sbin/update-grub.real" so i created a symbolic link to this file. On my system (originally dapper, upgraded to edgy and now to feisty) the problem was within this script, so this "fix" resolved it. As you said, this issue needs more research. Good Luck. (Sorry for my English)

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

*This is an automated response*

This bug report is being closed because we received no response to the previous request for information. Please reopen this if it is still an issue in the actively developed pre-release of Jaunty Jackalope 9.04 - http://cdimage.ubuntu.com/releases/jaunty . To reopen the bug report simply change the Status of the "linux" task back to "New".