Yes, I checked twice to have all files needed. However, here's the "ls
-al /boot" result:


drwxr-xr-x  3 root root     4096 giu 28 07:49 .
drwxr-xr-x 24 root root     4096 giu 20 17:18 ..
-rw-r--r--  1 root root   795624 mag 22 01:22 abi-3.2.0-24-generic
-rw-r--r--  1 root root   795624 giu 21 21:04 abi-3.2.0-25-generic
-rw-r--r--  1 root root   147378 mag 22 01:22 config-3.2.0-24-generic
-rw-r--r--  1 root root   147390 giu 21 21:04 config-3.2.0-25-generic
drwxr-xr-x  4 root root    12288 giu 28 08:04 grub
-rw-r--r--  1 root root 14111997 mag 24 08:32 initrd.img-3.2.0-24-generic
-rw-r--r--  1 root root 14113838 giu 28 07:49 initrd.img-3.2.0-25-generic
-rw-r--r--  1 root root   176764 nov 27  2011 memtest86+.bin
-rw-r--r--  1 root root   178944 nov 27  2011 memtest86+_multiboot.bin
-rw-------  1 root root  2252950 mag 22 01:22 System.map-3.2.0-24-generic
-rw-------  1 root root  2252950 giu 21 21:04 System.map-3.2.0-25-generic
-rw-------  1 root root  4864224 mag 22 01:22 vmlinuz-3.2.0-24-generic
-rw-------  1 root root  4865248 giu 21 21:04 vmlinuz-3.2.0-25-generic

As far as I can understand, everything is ok.

In the weekend I'll check the manual boot of faulty kernel versions. If you 
agree, I'll do as follows:
0. load kernel 3.2.0-24
1. disinstall (apt-get purge) 3.2.0-25-lp....-v6 (and also headers)
2. download again v1 and install it using dpkg.
3. reboot.
4. at reboot stop grub and manually load kernel v1 as already shortly mentioned.
5. check if it boots.
loop points 1->5 for every version (from 1 to 6) and report results in a short 
table.
6. reboot and load again 3.2.0-24

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1013647

Title:
  no boot at kernel load 3.2.0-25-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1013647/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to