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

Re: Booting a C360 with a graphic console

Jean-Pierre HOFER wrote:
I am trying to netboot (tftpboot) a C360 (PDC revision 1.5) with the current
The GSC graphic adapter is a HP A4071B (Revision 8.04/11), connected to a
fixed frequency monitor (1280x1024 @ 72 Hz).

HP A4071B is a (see include/asm-parisc/grfioctl.h):
S9000_ID_HCRX  0x2BCB015A  /* Hyperdrive/Hyperbowl (A4071A) Graphics

But it isn't succesfull :
> ...
Information: No console specified on kernel comman line. This is normal.
PALO will choose the console currently used by firmware (graphics).Current
command line:
0/linux initrd=0/ramdisk console-tty0 sti=10/0/4/0 sti_font=VGA8x16 TERM=linux
 0: 0/linux
 1: initrd=0/ramdisk
 2: console=tty0
 3: sti=10/0/4/0
 4: sti_font=VGA8x16
 5: TERM=linux

? b

start_kernel(): bug: interrupts were enabled early
Console: colour dummy device 160x64

Then, any text disappear from the display.
The Tux don't appear.
There are some horizontal erratic strings on the screen during 2 - 3 seconds
(similar to the ones during the probing of the graphic adapter through the PDC).
The machine do apparently not hang, since the first LED on the front panel is
beating, but there is no longer any display.

Which kernel is this?

Is this patch included (it's in Linus' tree):

commit 62347218243179a6ab03fe9f965a5819c4714bf8
Author: Helge Deller <deller@gmx.de>
Date:   Mon Mar 10 11:44:01 2008 -0700

    stifb: fix crash A1439A CRX (Rattler) graphics card

    Fix kernel crash when stifb driver is used with a A1439A CRX
    (Rattler) graphics card.  (Reference:
    Signed-off-by: Helge Deller <deller@gmx.de>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

I suspect that the graphic adapter is no longer driven with the 72 Hz video
mode after the point where the Tux should appear, but perhaps with the more
"modern" mode of 75 Hz VESA. Is there a way to verify that and to pass a
parameter to the kernel in order to operate the graphic adapter with a
definite video mode at boot time ?

Unlikely, as stifb and the other drivers don't set any other video mode than the one which is enabled by PDC BIOS at boot.

The other questionable point is about the sti argument; the PDC is listing the
graphic adapter with the following parameters :
	Path: GRAPHICS(1)
	Decimal: 8/4
But the proposed PALO command line contains the argument "sti=10/0/4/0".
What is the right argument ? 10/0/4/0 ? 8/4 ? GRAPHICS(1) ? Or is this
parameter irrelevant if there is only one graphic adapter ?

Do you maybe have multiple cards in your machine ?

Maybe try "stifb=bpp:8" (default to 8bpp) ?


Reply to: