2009/9/19 Srdjan Todorovic todorovic.s@googlemail.com:

Hi,

2009/9/19 Srdjan Todorovic todorovic.s@googlemail.com:

...

The grub screen shows:

Booting 'Slamd 64 12.2 Linux 2.6.31-srki'  root (hd0,1)    Filesystem type is ext2fs, partition type 0x83  kernel  /boot/slamd64-2.6.31srki root=/dev/sda2

Error 15: File not found

Managed to boot it using the grub command line, using the same settings.

Here's the menu.lst file - can anyone spot anything wrong in there?

Thanks Srdjan

default 3 timeout 30 splashimage=(hd0,0)/boot/grub/splash.xpm.gz

title Gentoo Linux 2.6.30-r4 root (hd0,0) kernel /boot/kernel2.6.30-gentoo-r4srki root=/dev/sda1 # title Gentoo Linux 2.6.30-r4 (rescue) root (hd0,0) kernel /boot/kernel2.6.30-gentoo-r4srki root=/dev/sda1 init=/bin/bb # title Slamd 64 12.2 Linux 2.6.30-cfq root (hd0,1) kernel /boot/slamd64-2.6.30-cfq root=/dev/sda2 # title Slamd 64 12.2 Linux 2.6.31-srki root (hd0,1) kernel /boot/slamd64-2.6.31srki root=/dev/sda2

Are you 110% sure there's no typo? Should the new kernel line be:

kernel /boot/slamd64-2.6.31-srki root=/dev/sda2 (with an extra dash)

... rather than ...

kernel /boot/slamd64-2.6.31srki root=/dev/sda2

This would be consistent with the name in its title line and with the name of your cfq kernel ... :)

Cheers,

Safe

On Sat, 2009-09-19 at 22:09 +0100, Srdjan Todorovic wrote:

Hi all,

Decided to give Linux 2.6.31 a go to see if it fixes the annoying I/O slowness bug I've been having for a long time.

Compiled it, installed the modules and copied the kernel image to the correct place in what is effectively /boot

  title Slamd 64 12.2 Linux 2.6.30-cfq
  root (hd0,1)
  kernel /boot/slamd64-2.6.30-cfq root=/dev/sda2

  title Slamd 64 12.2 Linux 2.6.31-srki
  root (hd0,1)
  kernel /boot/slamd64-2.6.31srki root=/dev/sda2

The first entry works and I can boot it. The second entry does not work and I get a "Error 15: File not found"

Interestingly I had a "Error 15: File not found" error when I tried kernel 2.6.31 but in my case I had used the Debian tool to build a kernel package and then install it.

Wondering if the installation had silently failed due to running out of space I delete the oldest kernel image which I never use from aptitude and tried installing the 2.6.31 package again whereupon the error went away.

I still don't know if the disk space idea was correct or whether there is some other problem, for example a limit to the number of menu entries etc. or something else that re-installing the package fixed.

Regards, Steve.

On Thu, 2009-09-24 at 13:25 +0100, Srdjan Todorovic wrote:

On 23/09/2009, Steve Fosdick lists@pelvoux.nildram.co.uk wrote:

...

Wondering if the installation had silently failed due to running out of space I delete the oldest kernel image which I never use from aptitude and tried installing the 2.6.31 package again whereupon the error went away.

Do you know if grub version has been updated?

I didn't notice a grub update between the last time grub config would have been altered by a kernel installation and the first attempt at 2.6.31.

...

I still don't know if the disk space idea was correct or whether there is some other problem, for example a limit to the number of menu entries etc. or something else that re-installing the package fixed.

Did you try booting using grub command line rather than the menu?

No, I tried an older kernel that was still in the menu and that worked fine.

I've 'fixed' the problem by installing grub2 (which is still beta apparently), and spending a while converting the syntax to the new format. This seems to work, but I'm not sure what the original problem was (which irritates me for not knowing).

For me the problem happenned with grub2.

The grub developers didn't really want to help unless I was running grub2 so perhaps this is a grub-legacy bug...

Regards, Srdjan

---

main@lists.alug.org.uk http://www.alug.org.uk/ http://lists.alug.org.uk/mailman/listinfo/main Unsubscribe? See message headers or the web site above!