I have this problem as well. I'm pretty sure I didn't do anything
wrong. I installed Debian on /dev/sda6 (JFS) with swap on /dev/sda7. I
went through the install several times, but both GRUB and LILO install
would always fail (I tried to install the booloaders to the root fs
superblock, not the MBR).
I already have lilo on the MBR (from /dev/sda3), so I just added
debian to that lilo with the following parameters:
image = /vmlinuz
root = /dev/sda6
label = Debian64
initrd = /initrd.img
# addappend = "resume=/dev/sda7 "
read-only
Lilo loads the kernel (it takes an unusual amount of time, but I don't
know what's normal for 64-bit kernels or debian).
Then the kernel stops with these messages
RAMDISK: couldn't find valid RAM disk image starting at 0
List of all partitions:
No filesystem could mount root, tried:
Kernel Panic - not syncing: VFS: unable to mount root FS on
unknown-block (8,6)
I had the PCI error as well.
It's the default amd64 kernel.
On Jan 25, 9:44 pm, Aka <[email protected]> wrote:
> It's a lenny default kernel AMD64.
>
> -rw-r--r-- 1 root root 1755696 Nov 5 05:32 /boot/vmlinuz-2.6.26-2-
> amd64
> -rw-r--r-- 1 root root 6670848 Jan 6 19:20 /boot/initrd.img-2.6.26-2-
> amd64
>
> On 25 jan, 19:56, [email protected] wrote:
>
> > First problem is that it can't load the ramdisk. Second problem is that
> > the drivers for your rootfs filesystem are not built into the kernel
> > (they're modules, most likely). This second one isn't a problem usually,
> > because the modules can be loaded from the ramdisk. Since that failed,
> > the kernel can't understand your filesystem and chokes.
>
> > Is this a custom kernel? Or one of the lenny defaults?
>
> > On Mon, Jan 25, 2010 at 11:22:55AM -0800, Aka wrote:
> > > Hi,
>
> > > I have a serious boot problem with debian lenny, I use LILO. Grub has
> > > problems too.
> > > Can please someone help me ?
>
> > > 1. At debian install time, both LILO and lenny couldn't be installed.
> > > 2. So, I used rescue mode (on install CD).
>
> > > Here you have what happens.
>
> > > 1. I disconnect all my HDD's except the one of lenny ; 2 partitions :
> > > 1 for '/' and 1 for swap.
> > > 2. On booting with install CD, I mount '/dev/sda1/ for '/', all OK.
> > > 3. I enter in the shell, and a first thing is strange :
>
> > > 'df' prints /dev/sdc1 (and not sda1) as '/' ??
> > > (Normaly, this drive is the third and is /dev/sdc when I connect my
> > > 3 HDD's)
>
> > > 4. I run lilo ; with lenny lilo.conf
>
> > > lba32
> > > boot=/dev/sda
> > > root=/dev/sda1
> > > prompt
> > > timeout=50
> > > map=/boot/map
>
> > > # loader=chain-loader # this don't change anything
>
> > > vga=normal
> > > image=/boot/vmlinuz-2.6.26-2-amd64
> > > label="lenny_1D"
> > > initrd=/boot/initrd.img-2.6.26-2-amd64
> > > read-only
>
> > > 5. When I reboot, I have a kernel panic with this message :
>
> > > ramdisk: couldn't find valid ram disk image starting at 0
> > > list of all partitions:
> > > ... # I don't remember the line, and the last one is :
> > > Kernel Panic - not syncing: VFS: unable to mount root FS on
> > > unknown block (...) # some numbers
>
> > > 6. Etch is OK on the same computer...
>
> > > 0. When I installed lenny, the first line I saw was :
>
> > > [ [0.260762 PCI ] cannot alocate ressource region 0 for device
> > > 0000:00:00:0
>
> > > I am not sure for the quite text (it goes fast, but :
> > > - The first number is correct,
> > > - 'region' is '0' and
> > > - 'device' is "a lot of" 0.
>
> > > PS:
> > > debian:/home/amel# lspci
> > > 00:00.0 Host bridge: Advanced Micro Devices [AMD] AMD-8151
> > > System Controller (rev 13)
> > > 00:01.0 PCI bridge: Advanced Micro Devices [AMD] AMD-8151 AGP
> > > Bridge (rev 13)
>
> > > Can please someone help me ?
>
> > > Thanks, best regards,
> > > Amka
>
> > > --
> > > You received this message because you are subscribed to the Linux Users
> > > Group.
> > > To post a message, send email to [email protected]
> > > To unsubscribe, send email to [email protected]
> > > For more options, visit our group
> > > athttp://groups.google.com/group/linuxusersgroup
>
>
--
You received this message because you are subscribed to the Linux Users Group.
To post a message, send email to [email protected]
To unsubscribe, send email to [email protected]
For more options, visit our group at
http://groups.google.com/group/linuxusersgroup
