VGXT EEPROM VOF bad checksum - Printable Version
+- IRIX Network Forums (//forums.irixnet.org)
+-- Forum: SGI/MIPS (//forums.irixnet.org/forum-3.html)
+--- Forum: Hardware/Triage/Repair (//forums.irixnet.org/forum-11.html)
+--- Thread: VGXT EEPROM VOF bad checksum (/thread-1876.html)
+- IRIX Network Forums (//forums.irixnet.org)
+-- Forum: SGI/MIPS (//forums.irixnet.org/forum-3.html)
+--- Forum: Hardware/Triage/Repair (//forums.irixnet.org/forum-11.html)
+--- Thread: VGXT EEPROM VOF bad checksum (/thread-1876.html)
VGXT EEPROM VOF bad checksum - dstep - 02-17-2020
Hello
I have trouble with VGXT. It displays only at boot but not X. There is message about checksum error at system start and about bogus GM command at X start. I guess I need to find bad EEPROM IC or ICs and than find correct firmware for it and then flash it.
Can anybody help please?
RE: VGXT EEPROM VOF bad checksum - jan-jaap - 02-17-2020
The VOF is the output format (thing "mode line") for the graphics.
You can set it from IRIX, try "/usr/gfx/setmon 60HZ" for the default, 1280x1024 @ 60HZ
That's probably the format you've got now, but with a bit of luck the warning will be gone.
RE: VGXT EEPROM VOF bad checksum - CB_HK - 02-17-2020
dstep,
You and I are having VERY similar issues with out VGXT boards. I've been trying to get mine working for quite a while. Since I took a break I'm back at it. If I uncover anything that will help I'll be sure to post it for you!
That said, I'll take a look at what exact errors I'm having. Hopefully we can both resolve our issues!
RE: VGXT EEPROM VOF bad checksum - dstep - 02-18-2020
My power up VGXT messages:
NOTE: PROM checksum (0x53d012)
PASS: PROM checksum test
NOTE: SRAM walking 1 test
NOTE: SRAM address test
NOTE: SRAM pattern test
PASS: SRAM tests
NOTE: got SRAM stack
NOTE: DRAM walking 1 test
NOTE: DRAM addr test
NOTE: DRAM pattern test
NOTE: PROM checksum (0x53d012)
PASS: PROM checksum test
NOTE: SRAM walking 1 test
NOTE: SRAM address test
NOTE: SRAM pattern test
PASS: SRAM tests
NOTE: got SRAM stack
NOTE: DRAM walking 1 test
NOTE: DRAM addr test
NOTE: DRAM pattern test
NOTE: DRAM cycle type test
PASS: DRAM tests
NOTE: clearing all DRAM...
NOTE: DMA smoke test
NOTE: DMA walking 1 test
NOTE: DMA addr test
NOTE: DMA pattern test
PASS: DMA tests
NOTE: SBCC walking 1 test
PASS: SBCC tests
NOTE: got DRAM stack
NOTE: DMA smoke test
NOTE: DMA walking 1 test
NOTE: DMA addr test
NOTE: DMA pattern test
PASS: DMA tests
NOTE: PROM based diag done
GM PROM (Wed Oct 16 22:00:23 PDT 1991)
Unknown imp revision (IR_CONFIG = 0x00000000)
GM PROM (Wed Oct 16 22:00:23 PDT 1991)
gm3.u - Thu Nov 3 19:54:43 PST 1994
gmcmd(): bogus GM command from:0x9001d040
INTR received, but no cmd set
<debug> no disassembler in GM PROM
gmon>
And "c" for continue or "q" for exit/reset did not help
Some time there is no "bad checksum" message but get "bogus GM command..."
One time I got:
GM PROM (Wed Oct 16 22:00:23 PDT 1991)
gm3.u - Thu Nov 3 19:54:43 PST 1994
GE jumped to bad address:0x0
<debug> no disassembler in GM PROM
gmon> c
Vertical retrace timed-out!
with the same result - no X display
(02-17-2020, 04:07 PM)jan-jaap Wrote: The VOF is the output format (thing "mode line") for the graphics.
You can set it from IRIX, try "/usr/gfx/setmon 60HZ" for the default, 1280x1024 @ 60HZ
That's probably the format you've got now, but with a bit of luck the warning will be gone.
It seems I have tried this, and 30HZ and all the options from man page )))
Thanks for the tip anyway. I will try it one more time. It seems to me that the behavior of the VGXT changes a little when it warms up. One time I got "GE jumped to bad address:0x0" message instead of "gmcmd(): bogus GM command from:0x9001d040"
RE: VGXT EEPROM VOF bad checksum - CB_HK - 02-18-2020
(02-18-2020, 03:56 PM)dstep Wrote: My power up VGXT messages:
NOTE: PROM checksum (0x53d012)
PASS: PROM checksum test
NOTE: SRAM walking 1 test
NOTE: SRAM address test
NOTE: SRAM pattern test
PASS: SRAM tests
NOTE: got SRAM stack
NOTE: DRAM walking 1 test
NOTE: DRAM addr test
NOTE: DRAM pattern test
NOTE: PROM checksum (0x53d012)
PASS: PROM checksum test
NOTE: SRAM walking 1 test
NOTE: SRAM address test
NOTE: SRAM pattern test
PASS: SRAM tests
NOTE: got SRAM stack
NOTE: DRAM walking 1 test
NOTE: DRAM addr test
NOTE: DRAM pattern test
NOTE: DRAM cycle type test
PASS: DRAM tests
NOTE: clearing all DRAM...
NOTE: DMA smoke test
NOTE: DMA walking 1 test
NOTE: DMA addr test
NOTE: DMA pattern test
PASS: DMA tests
NOTE: SBCC walking 1 test
PASS: SBCC tests
NOTE: got DRAM stack
NOTE: DMA smoke test
NOTE: DMA walking 1 test
NOTE: DMA addr test
NOTE: DMA pattern test
PASS: DMA tests
NOTE: PROM based diag done
GM PROM (Wed Oct 16 22:00:23 PDT 1991)
Unknown imp revision (IR_CONFIG = 0x00000000)
GM PROM (Wed Oct 16 22:00:23 PDT 1991)
gm3.u - Thu Nov 3 19:54:43 PST 1994
gmcmd(): bogus GM command from:0x9001d040
INTR received, but no cmd set
<debug> no disassembler in GM PROM
gmon>
And "c" for continue or "q" for exit/reset did not help
Some time there is no "bad checksum" message but get "bogus GM command..."
One time I got:
GM PROM (Wed Oct 16 22:00:23 PDT 1991)
gm3.u - Thu Nov 3 19:54:43 PST 1994
GE jumped to bad address:0x0
<debug> no disassembler in GM PROM
gmon> c
Vertical retrace timed-out!
with the same result - no X display
I've had a recurring issue with "Vertical retrace timed-out!" as well. It only makes the issue more odd considering the fact that I've reinstalled the OS components that I need and IRIX has no problem seeing the gfx (just lists it as unmanaged).
I hope that the issue is somehow still software related and not a problem with the boards (for either of us!).