[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: grub2 can't see my linux kernel file

From: j t
Subject: Re: grub2 can't see my linux kernel file
Date: Tue, 12 Jan 2010 20:42:37 +0000

On Tue, Jan 12, 2010 at 7:21 PM, Jordan Uggla <address@hidden> wrote:
> Yes, the "out of disk" error you had in the beginning suggests that
> there is a BIOS limitation, but since things are still not working
> with the ata module there must also be another problem.
> Do you have a separate /boot partition? Could you attach your
> /boot/grub/grub.cfg ?

Hi Jordan.

Yes, I do have a separate boot partition, but it's slightly more
complicated than that. The machine is an IBM Thinkpad X31 with one
40GB harddrive with 6 partitions on it:

~# fdisk -l /dev/hda

Disk /dev/hda: 40.0 GB, 40007761920 bytes
240 heads, 63 sectors/track, 5168 cylinders
Units = cylinders of 15120 * 512 = 7741440 bytes
Disk identifier: 0x1f253ddf

   Device Boot      Start         End      Blocks   Id  System
/dev/hda1               1           4       30208+  83  Linux
/dev/hda2   *           5        1500    11309760    7  HPFS/NTFS
/dev/hda3            1501        1565      491400   82  Linux swap / Solaris
/dev/hda4            1566        5168    27238680    5  Extended
/dev/hda5            1566        3547    14983888+  83  Linux
/dev/hda6            3548        5168    12254728+  83  Linux

/dev/hda1 is my principal boot partition, where I install grub(2).
Since I only use /dev/hda1 to hold grub, there's only a /boot/grub
directory which holds all the grub files (there is nothing else in
that partition). My /boot/grub/grub.cfg which looks like this:

set timeout=5
set debug=1
set pager=all

# Set default boot entry as Entry 0
set default=saved

menuentry "WinXP (hda2 11GB)" {
  chainloader (hd0,2)+1

menuentry "Debian (hda5 16GB) chaining" {
  chainloader (hd0,5)+1

menuentry "Debian (hda5 16GB) direct" {
  linux (hd0,5)/boot/vmlinuz-2.6.26-2-686 root=/dev/hda5 ro
  initrd (hd0,5)/boot/initrd.img-2.6.26-2-686

menuentry "NewDebian (hda6 16GB) chaining" {
  chainloader (hd0,6)+1

menuentry "NewDebian (hda6 16GB) direct" {
  linux (hd0,6)/boot/vmlinuz-2.6.26-2-686 root=/dev/hda6 ro
  initrd (hd0,6)/boot/initrd.img-2.6.26-2-686

The other partitions should be self-explanatory from the partition
list / grub.cfg. My real debian installations are in hda5 and hda6.
Also, while I'm running one of my debian installations, /dev/hda1 is
not mounted - I hope this makes sense.

Do you know if there is any way to debug the problem with the ata module?

With kindest regards,


Attachment: grub.cfg
Description: Binary data

reply via email to

[Prev in Thread] Current Thread [Next in Thread]