Re: HP 712 Installation story + iee0 going OACTIVE..

On Sun, 16 Oct 2005 15:28:49 +0200
"Martin S. Weber" <[email protected]> wrote:

> Sysinst attempt #2, partitioning for hd booting this time (i.e.
> leaving space at the front of the disk -- this should go into the
> release notes!); Installation works great. I then  also got the right
> order of the LIF-dd and the disklabel commands to enable disk-booting
> and basically am happy now.
You should not need any dd-LIF-to-disk and unused space at the beginning
of the disk. You should use the two stage boot code that can be instaled
with "disklabel -B" or installboot.

> During some pkgsrc builds I've also found out how to distinguish
> 'non-working' iee0 from 'working' iee0 - if it's broken, instead of
> flag "RUNNING" it has"OACTIVE" set.
Hmmm. OK, I have to look at hp700 again. As the PS/2 keyboard and the
iee(4) driver are growen out of my brain I feel a slight responsibility
for them. ;-)

> I'm also kind of surprised that there's no X delivered for King Gecko.
Yes, no X-Server for hp700 and don't expect one in the near future. :-(

> Whatever exact version of X delivered by Debian, they *do* support the
> 1024x768x8 framebuffer with xfree. So obviously it is supported but we
> lack some imports? Or is that related to linux console framebuffer /
> fbdev? (In the meantime I guess that's it. Linux driver support.
> yeehaa :( )
You are right. The Linux-hppa X-Server uses the generic Linux
framebuffer device. This is a plain, dumb, unaccelerated framebuffer. A
friend run KDE on a 715/64 with 256 MB RAM (max for this machine) and it
was ssslllooowww. Mostly due to the sluggish framebuffer. Even the text
console, that seems to use the kernel framebuffer too, on my much faster
B2000 with its 400 MHz PA8500 is ssslllooowww when running Linux.
-- 


tschüß,
       Jochen

Homepage: http://www.unixag-kl.fh-kl.de/~jkunz/