Re: daily images for PA-RISC/HPPA
On Sat, Jan 10, 2004 at 01:17:56PM +0000, Richard Hirst wrote:
> On Fri, Jan 09, 2004 at 08:21:17AM +0100, Thorsten Sauter wrote:
> >
> > Hello debian-installer's :-),
> >
> > I have setup daily images for the HPPA architecture on paer.debian.org.
> > The images creates cdrom, netboot and a lif image from source. As
> > usually everything is available here:
> > http://people.debian.org/~tsauter/d-i/images-hppa/daily/
> >
> > I hope, we can build daily cdrom images as well.
> >
> > I have tested the images on the following machine types (always tftpboot
> > via lif image): 9000/712-60 and 9000/712-80.
> >
> > Please test the images.
>
> netboot.lif seems to have a rather strange cmdline:
>
> TERM=linux console=tty initrd=netboot-initrd.gz ramdisk_size=8192 root=/dev/rd/0 initrd=0/linuxrc devfs=mount,all rw
>
> I couldn't find "initrd=0/linuxrc" anywhwere in the d-i source.
>
> The crdom-image.img seems to have a more sane cmdline, but I still had
> to use palo to edit it to add "root=/dev/ram devfs=mount,dall" before it
> would get anywhere. I had to remove TERM=linux as well, because palo
> locked up if I included all those params. palo has a history of locking
> up when you edit the cmdline, unfortunately.
>
> Anyway, after that, it booted and mounted the initrd, and then looped
> complaining that it couldn't find various kernel modules, and reporting
> 'segmentation fault'.
>
> This was on a B180, STI console.
The SEGV is in "frontend", looks like a null pointer deref. I switched
to text frontend, fixed d-i to actually make a lifimage for netboot (I
guess you created yours manually?), and tried again. I havn't submitted
my change yet.
Getting further now, currently running debootstrap, installing unstable.
Couldn't partition disks because there is no [c]fdisk udeb installed.
parted won't work for hppa because we need to create a partition of type
'F0' and parted can't do that. I skipped that step and used my
existing partitions. IIRC this is a problem with fdisk-udeb priority.
It gets pulled in on i386 anyway because lilo-installer wants it (at
least, that is what I recall), but doesn't get pulled in for hppa. I
think the easy answer is to include it in the pkg-lists for hppa.
Richard
Reply to: