[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-parisc
Subject:    Re: HP FireGL-UX on C3700 - Framebuffer loses signal.
From:       Helge Deller <deller () gmx ! de>
Date:       2018-09-26 21:24:11
Message-ID: 97debd66-fdff-0f83-d999-69ef09e31434 () gmx ! de
[Download RAW message or body]

On 26.09.2018 23:11, Robert Gadsdon wrote:
> On 09/25/2018 05:55 PM, John David Anglin wrote:
> > On 2018-09-25 5:48 PM, John David Anglin wrote:
> > > There are a couple of options to specify on the linux command line.
> > Turns out palo fills the options in automatically:
> > 
> > palo.conf:
> > --commandline=2/vmlinux root=UUID=308b2a95-a065-4da1-b755-7dc4f607e602 \
> > initrd=2/initrd.img HOME=/ 
> > dmesg:
> > [    0.000000] Kernel command line: \
> > root=UUID=308b2a95-a065-4da1-b755-7dc4f607e602 HOME=/ console=tty0 sti=10/4/3/0 \
> > sti_font=VGA8x16 TERM=linux palo_kernel=2/vmlinux 
> That turned out to be the problem - PALO was not 'automagically' adding the \
> parameters to the kernel command line, although it had done this for the FX2 card.. \
>  I added the 'sti=10/4/3/0 sti_font=VGA8x16 TERM=linux' parameters manually, and \
> the card is now recognised correctly:

Why wasn't it added by palo?
Are you maybe running on serial console and thus palo didn't added it?
Which palo version is installed?
You can update palo in the boot sector via running "palo".
See: https://git.kernel.org/pub/scm/linux/kernel/git/deller/palo.git/

Helge
 
> 01:05.0 Display controller: Hewlett-Packard Company A4977A Visualize EG (rev 03)
> Flags: 66MHz, medium devsel
> Memory at fffffffffa000000 (32-bit, non-prefetchable) [size=32M]
> Expansion ROM at fffffffff4800000 [disabled] [size=64K]
> Kernel driver in use: sti
> 
> - and the system boots into text mode, and the stifb module loads (Kernel \
> 4.19-rc5): 
> # modprobe stifb
> Console: switching to colour frame buffer device 160x64
> fb0: stifb 1280x1024-8 frame buffer device, PCI_GRAFFITIX1280, id: 2d08c0a7, mmio: \
> 0xfffffffffa100000 
> Sadly, there seems - as you mentioned - to be no Xorg support..


[prev in list] [next in list] [prev in thread] [next in thread]