BY: hikey
DATE: 2004-Feb-01 02:27
SUBJECT: RE: SPS2UScreenInit() requirements; memcard-linuxHi mrm,
Very interesting. I'll have to give it a go myself, been meaning to do that for a while.
There are several things to try:
- Press Ctrl-C repeatedly to make sure the program has stopped.
- Type "reset" to reset the terminal. That may be enough to get the text back on screen.
- Type the "Ctrl-V escape C enter" sequence, it's a harder terminal reset.
- Type "setcrtmode vesa" (or pal). That will bring the text back in most cases.
- Before running the program, when you still have the text on screen: press alt-f2 to change virtual console. If this works, log in (or not if there isn't a getty), and you could use it to kill the program later.
How about writing debug info to a file ? Do you have a writable file system ?
You could always make the keyboard leds blink in your code to make sure the program actually runs.
You could hack the sps2util file to remove some of the initialisation stuff that tries to be nice to linux, I had some screen init code that would do it brutally that could work for you, I'll see if I can dig it out. Needless to say in that case don't even consider trying to run several grpahics programs at once, it'd only be asking for trouble. |
SPS2UScreenInit() requirements; memcard-linux