On Tue, Apr 13, 2004 at 06:04:14PM +0200, maximilian attems wrote: > > If the base system has installed successfully (and it won't with current > > images on alpha), the aboot installer should be run automatically. > waiting for a bug closure for some more testing, > on the mailinglist i saw an upload of a new kernel, > so i hope the scsi bug is resolved. > (allthough #237884 is still pending, > marcelo added a stxcpy fix to 2.4.26-rc3 as did linus in current) I don't see that there's been a new 2.4 kernel-image upload yet for alpha, but I'm sure this fix will be included whenever there is one. > > Did you specify an initrd option on your boot line? The kernels shipped > > with Debian have only minimal filesystem support compiled in -- you will > > need the initrd to be able to mount your root filesystem. > used the initrd option > but forgot to put a /etc/aboot.conf inside of this root filesystem > perhaps thats fatal? The aboot.conf file is just a convenient way to manage kernel boot options, it's not a requirement for a bootable system. A typical aboot.conf file installed by d-i would be: 0:3/vmlinuz ro initrd=/initrd.img root=/dev/sda3 1:3/vmlinuz.old ro initrd=/initrd.img.old root=/dev/sda3 This is for a root partition of /dev/sda3, with your kernel images located on the same partition. Passing everything after "0:" to aboot's "boot" command should let you boot with the same results. -- Steve Langasek postmodern programmer
Attachment:
signature.asc
Description: Digital signature