So from the picture alone, can you diagnose the problem?
twitter.com/jason_koebler/
This Tweet is unavailable.
1
1
Conversation
Replying to
So this is clearly a corruption and it's not that central, or the system would never have booted this far.
1
Replying to
It also is not static, as you can see some "o"s are translated into "g" and others aren't. Corruption in lookup table therefore unlikely.
1
Replying to
no idea how these chars appear on the screen in this mode but maybe something is futzing a line in the video memory that contains them?
1
Replying to
Further evidence: when you look at the corrupted chars, they are all <char-8> (N -> F, n -> f, i -> a)
Replying to
My guess: something is randomly stickying the 4th most significant bit of the char to 1 during a lookup. Broken line in the bus?
1
1
Replying to
4th least significant bit*
Well if you think ASCII instead of bytes it doesn't matter anyway.
1
Show replies