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

Re: DebDebian/Debian/GNU Linux Developer | storm [at] debian.org GNU Linux Developer | storm [at] debian.org ian build



Bradley Alexander schreef:
I'm having a hard time building from the installer-cd image. I don't think its a problem with the installer itself, because I have built other boxes with these images. I'm hoping that someone can find something that I have missed.

My hardware is a VA Linux 2U box (the label says "2200 series"), dual PIII/750s, 512MB, dual 9GB WD/Compaq SCSI drives.

I have built with the following debian-installer versions: rc1, rc2, 20050213.

rc2 apparently did not load the aic7xxx driver properly, because early in the install, it would come up with a "no installation media found" error. With rc1 and 20050213, it detected and loaded the drivers fine. The problem I am currently having is although the base install goes great, and I am able to complete the install, including setting up partitions, with no errors. However, when it tries to do the reboot, it comes up with the following error:

   Booting 'Debian GNU/Linux, kernel 2.6.8-2-386 '

root  (hd0,1)
  Filesystem tye is ext2fs, barttion type 0x83
kernel  /boot/vmlinuz-2.6.8-2-386 root=/dev/sda2 ro
      [Linux-bzImage, setup=0x1400, size=0x10a624]
initrd   /boot/initrdimg-2.6.8-2-386
      [Linux-initrd @ 0x1fbaa000 0x436000 bytes]
savedefault
boot
Uncompressing Linux...

crc error

  -- System halted

Okay, here's something new...It attempted to boot this time and got
RAMDISK: cramfs filesystem found at block 0
RAMDISK: Loading 4312 blocks [1 disk] into ram disk... done.
VFS: Mounted root (cramfs filesystem) readonly.
Error -3 while decompressing!
c0352495(2081)->dfafc000(4096)
/bin/sh: reloaction error: /bin/sh: symbol getpid, version GLIBC_2.0 not defined in file libc.so.6 with link time reference
VFS: Cannot open root device "sda2" or unonown-bloc(0,0)
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0)

Anyone seen this behavior before?

Yes, I think you need to build a new initrd. Edit your driver into /etc/mkinitrd/modules and read "man mkinitrd".

Often, you need to boot with a CD, mount, chroot, and use the [version] option. Use a kernel-name from /lib/modules. Your command will be something like: "mkinitrd 2.6.8-2-686".

Bye,
Paul.






Reply to: