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

Re: State of the PA-RISC/HPPA port (August 2013)

On 3-Aug-13, at 11:41 PM, Dave Land wrote:

After talking with Helge off-list, I finally got my box (Visualize J6750) to boot to the 'real' OS on the HDD, but I'm still working out some issues with palo, so it will actually find the working root partition without intervention from me. ;)

The root= parameter mostly works for me. However, different kernels sometimes change the order of disk discovery when you have multiple drives. Helge thinks it would be easy to specify file system by uuid. This would work well for non recovery situations. Another thought is to specify the root partition
by number assuming it has to be on same drive as boot kernel.

I have an inexpensive portable USB drive connected to one of my systems. It comes up as /dev/sda
at boot and messes up the drive order.  Not exactly plug and play...

After a kernel decides which drive order to use, I boot manually setting root=/dev/sdXY to the correct drive and partition. Then, I edit /etc/palo.conf to correct the root setting and rerun palo. One can use the palo -f option to specify a specific conf file if one has multiple boot drives.

I'm not sure the "new" ext2/ext3 scheme described on the wiki works. I tried it yesterday. After running the palo command to make a filesystem on the F0 partition, I wasn't able to mount it. So, I went back to
old hidden partition scheme.

There is a small bug decompressing gzipped kernels. I see error message at end of process but it
doesn't seem to affect the boot.  This cuts kernel size by about 1/3.

John David Anglin	dave.anglin@bell.net

Reply to: