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

Bug#242659: d-i errors on alpha



On Fri, Apr 09, 2004 at 10:44:46AM +0200, maximilian attems wrote:
> thanks for your response and usefull bugs pointer!

> On Thu, 08 Apr 2004, Steve Langasek wrote:

> > > 3) at this stage i strongly missed a menu-entry for aboot at d-i!!

> > (!)  I'll have to take a look at this; last I was able to test, aboot
> > showed up right where it was supposed to in the menu, you just can't get
> > it to run from the menu unless the base install has completed
> > successfully.

> 2 curious questions:
> * what is base install supposed to do ..  beside dpkg -i the base deb?
> i had at this stage a working chroot with apt-get inside
> and could install sshd for example.

It is not "the base deb", but "the base debs".  The base install gives
you a minimal installed system using debootstrap and the standard Debian
packages that are part of the base system.  Note that being able to
chroot into it doesn't guarantee that the base install completed
successfully.

If the base system has installed successfully (and it won't with current
images on alpha), the aboot installer should be run automatically.

> * abootconf /dev/sda 2 showed some strange lseek error,
> (the machine is abootable .. had previously woody)
> swriteboot /dev/sda bootlx vmlinuz -f1
> worked (modulo pathes for kernel and bootlx)
> at this stage i probably forgot to write a nice aboot.conf
> and the INSTALL file from aboot recommends to use
> swriteboot -c2 /dev/sda bootlx

Can you be more specific regarding the "strange lseek error"?  It sounds
below like aboot was successfully installed to your hard drive, so it
may not be a problem.

> the problem now was that the kernel panicked, because it couldn't find
> it's root fs .. tried lots of bootargs from aboot 
> root=/scsi/host0/bus0/target0/lun0/part2 .. or root=/dev/sda2
> in combination with the initrd=/boot/initrd.gz arg.
> does a devfs=no help at that point ?
> tried also to boot via dka d-i cdrom or a woody rescue floppy disk ..

> forgot to mention that i used bsd disklabels to partition this 
> harddisk .. had a first empty partition of 50 mb and the rest for 
> root. 

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.

-- 
Steve Langasek
postmodern programmer

Attachment: signature.asc
Description: Digital signature


Reply to: