Re: Problem during the reboot phase (netinst mage 2004-05-16)
Hello Stex,
SteX wrote:
On Sun, May 16, 2004 at 01:19:41PM +0000, Joel Soete wrote:
Hi Joel,
well I found the solution!
Partition Start(MB) End(MB) Id Type
1 1 33 f0 Palo
2 34 157 83 ext2
5 158 818 83 ext2
6 819 1910 83 ext2
7 1911 2005 82 swap
PALO(F0) partition contains:
0/vmlinux64 6666431 bytes @ 0x48000
Excuse me but I don't have enough time experiment new d-i (so I have no
clue of default partitioning), but I recently work on palo-1.5 and it
seems that in fact palo don't find '/boot/vmlinux'; it could be because:
- it is not install at all
- it doesn't stand at the expected place (ie into /boot).
In the first case just reboot in interactive mode and choose to boot on
'0/vmlinux64' and try to re-install the kernel you want.
Here it is! to change the boot command in order to make the system boot
from PALO partition and not from /boot/...
So the final string (interact with IPL) must be
0/vmlinux64 root=/dev/md2 HOME=/ console=ttyS0 TERM=vt100
Yes '0/vmlinux64' is what is called 'recovery kernel' in palo.conf and
stand in 'PALO' partition (specific to parisc linux).
Now that you reach to boot it would be nice that you have a look in
/boot where you would find the usual kernel vmlinux (and also where you
would put other testing kernel before 'production'). And 'df -k' would
also shows a 'boot' fs like:
/dev/sda2 123699 66119 51193 57% /boot
/dev/sda5 1692128 1209236 396936 76% /
(size came from my own system) and I put in my /etc/palo.conf something
like:
--commandline=2/vmlinux root=/dev/sda5 HOME=/ TERM=vt100
--init-partitioned=/dev/sda
(check carefully that sda2 is well your /boot and sda5 your / (ie your
root partition); I just append TERM for you)
and just re-run palo (without parameter it will take /etc/palo.conf as
default in which you say which disk to use: sda).
That said, palo is a bit like grub, it doesn't need to be run each time
you want to use or test a new kernel (like required lilo): just put it
in your /boot with another name like vmlinux-2.6.6-pa3, interupt the
boot and just change the boot cmd with 2/vmlinux-2.6.6-pa3 and b ;-)
Just re-run palo to put in place a new palo, a new kernel that you fill
enough tested and robust for you.
the vt102 terminal get my console *dirty* of character, therefore I prefer
vt100 with seem a little bit *cleaner*.
In the syslog of the installer i found:
root=/dev/ram init=/linuxrc console=ttyS0 TERM=vt100 palo_kernel=0/vmlinux64
Well depends of your actual terminal with hp terminal emulating vt200
and a terminal emulation like minicom vt200 works fine for me.
Unfortunately I found:
May 16 11:51:20 (none) syslog.warn klogd: iosapic: hpa not registered for
Hewlett-Packard Company Visualize FX4
...
May 16 11:51:20 (none) syslog.warn klogd: stifb: Unsupported gfx card id
0x2fc1066b
Yes, it's a know issue: it seems to be a licence pb :_(
But Grant seems to confident to obtain something :-)
But there are reports of succesfull use of some pci aty and voodoo2 gfx
card. (have a look in this ml or in the parisc-linux ml)
For my part I was luckyless: I try an aty but it was a card for a sun
and its initialisation is different then a pc model :_(
It is a pity that the graph card is not supported. However i found a
document, in the hp site if I remember well, about how to recompile OpenGL
drivers for hp workstation. Do you know if it is possible also under
debian?
Well, I hack a bit this stuff and reach to re-compile the Xhp server but
I nerver reach to find how to implement /dev/crt0 ;)
But that was only (not applicable for FX4) in the hope to improve the
color dep of gfx encounter on 712, c110 or b180.
And even if I work much more on this stuff, it will not help a lot
because it would also required to change app libs to use actually more
colors.
Unfortunately the only reasonable hope is Grant .
Regards,
Joel
Reply to: