Re: TGX Plus on sun4c (IPX) problem

Le dim. 14 sept. 2025 à 13:20, Michael <[email protected]> a écrit :
> Does it lock up if you boot with the console on the onboard GX and the
> TGX+ present? If not, what happens if you send something to /dev/ttyF0?

Changing the sbus-prove-list to put 3 before 0 got me the onboard GX
as console, and everything worked fine.
I see the TGX+ as a 2 MiB (9.0 so pre-patch to see the 4 MiB
apparently) cgsix1 attached to /dev/fb1 as expected.

However...
* I only have one 13w3 -> VGA cable so no idea what the TGX+ is
displaying, if anything
* I can't write to /dev/ttyF0 or /dev/ttyF1 via echo+redirection
("/dev/ttyF0: Device not configured")
* I don't see a framebuffer image display or other fb tool in my old
pkgsrc (similar era to 9.0), and dd'ing to /dev/fb[01] is "operation
not supported"

Related to a previous question:
With a working GX as console, the first lines from the kernel are slow
to display and black-on-white.
As soon as the cgsix driver takes over, they display faster (yeah fb
acceleration!) as green-on-white.
That does not happen on the TGX+, the machine crashes before the
transition AFAICT - not sure if I saw any lines.
Does it mean that calling the PROM function doesn't work somehow ?

(I have a feeling, but it was a while ago, that I had the same issue
with the SBusFPGA when I briefly tried it in the IPX...)

Cordially,

Romain

### TGX+ as secondary
bash-5.0# dmesg |grep cgsix
[     1.000006] cgsix0 at sbus0 slot 3 offset 0x0 level 7: SUNW,501-1672, 1152 x
900, rev 8 (console)
[     1.000006] cgsix0: attached to /dev/fb0
[     1.000006] cgsix0: framebuffer size: 1 MB
[     1.000006] wsdisplay0 at cgsix0 kbdmux 1: console (std, vt100 emulation)
[     1.000006] cgsix1 at sbus0 slot 1 offset 0x0 level 7: SUNW,501-2253, 1152 x
900, rev 11
[     1.000006] cgsix1: attached to /dev/fb1
[     1.000006] cgsix1: framebuffer size: 2 MB
[     1.000006] wsdisplay1 at cgsix1 kbdmux 1
###

-- 
Romain Dolbeau