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

Re: installing lenny on m68k/amiga



On Fri, Mar 20, 2009 at 04:37:10PM -0500, Stephen R Marenka wrote:
> On Fri, Mar 20, 2009 at 01:35:42PM +0100, Christian T. Steigies wrote:
> > On Thu, Mar 19, 2009 at 09:19:28PM +0100, Christian T. Steigies wrote:
> > > Hi,
> > > I have tried to setup debian on my Amiga again with CD image from Nov 24
> > > 2008 and the Debian GNU/Linux 5.0 "0" - Unofficial m68k NETINST Binary-1
> > > from 20080401-05:07. With both of them it is not possible to install debian
> > > without performing some changes on the CD. 
> > [...]
> > > The lenny kernel (2.6.24) does not seem to have a driver for my Blizzard2060
> > > SCSI card, 2.6.26 also does not recognize my SCSI card.
> > > isofs is not built in, so that the installer can not access the installation
> > > CD. I think that was the point where I also gave up last time.
> > [...]
> > 
> > I tried again using 2.6.18-4-amiga instead, but it seems I am using the
> > wrong ramdisksize. I started with 9000, now I am at 1000000, but I always
> > gget messages like these, with "want" = 4 * "limit" + 8
> > 
> > ram0: rw=0, want=12891144, limit=3222784
> > 
> > Should I uncompress the initrd as well? Do I have to write the initrd to a
> > spare partition? Or is this initrd not compatibable with the kernel version?
> 
> Which exact url are you using and what exact command line? The initrd's 
> haven't needed a ramdisksize since the switch to initramfs, I believe.
> 
> To uncompress it you need: 
> 	zcat initrd | cpio -iv

6280k

amiboot -d -k vmlinux-2.6.18-amiga -r initrd.gz video=amifb:pal-lace root=/dev/ram fb=false ramdisk_size=20000 debian-installer/framebuffer=false 

Maybe the switch to initramfs is the problem, is this supported by 2.6.18? 
I think I never activated initramfs, I thought it would not work on m68k.

Another try with 2.6.24 and 2.6.26 get past this point, ie the installer
starts, I can select the region, but it then fails mounting the CD-Rom. The
drive is detected by the kernel, I suspect this is due to a missing isofs
driver. I guess I should build a new kernel image...

Christian


Reply to: