dalby

for the rest, i dont find anything... then again, my main question is, how can i still boot with that new kernel? it seems to forget it it is there, once its booted its being saved as the default kernel

thanks for the answer, yes i did the update-grub command i am going through the logs, already found why the vserver crashes with the original kernel:: ov 6 03:17:02 Hetch kernel: ----------- [cut here ] --------- [please bite here ] --------- Nov 6 03:17:02 Hetch kernel: Kernel BUG at kernel/vserver/context.c:140 Nov 6 03:17:02 Hetch kernel: invalid opcode: 0000 [4] SMP Nov 6 03:17:02 Hetch kernel: CPU 1 Nov 6 03:17:03 Hetch kernel: Modules linked in: vmnet parport_pc parport vmmon ipv6 cpufreq_conservative cpufreq_stats cpufreq_ondemandfreq_userspace loop dm_mirror dm_snapshot dm_

i have updated from debian lenny to debian squeeze, installed a new (custom) kernel to run vservers. for some reason grub keeps booting the old kernel (i do not have console access, only ssh) , it should boot Linux 2.6.32-5-vserver-amd64 but it boots Linux 2.6.18-6-vserver-amd64… when rebooting after installing the first time, the system hung, and i rebooted and the old kernel was loaded i guess, how to reset? anyone knows? Thanks in advance! -(~:#)-> cat /boot/grub/grub.cfg # # DO NOT EDIT THIS FILE # # It is automatically generated by grub-mkconfig using t