Again, this happens after KMS modules load which also load console frame buffer modules, though I haven't had any problems reading the font. If you don't want to use KMS for some reason you have to boot with nomodeset and probably use vesa.Even when the frame buffer does not get messed up, the text console fonts, which were previously readable, suddenly become microscopic during the boot sequence, making it hard to tell what is going on when there is a problem in getting to X and a desktop, or in the reboot/shutdown sequence, when there is a failure to save.
This applies to Fatdog64 as well, but different knowledge is required. Fatdog64 has almost nothing to do with Puppy, nearly everything is different.Puppy has always impressed me with the ability to fall back to some lower level of operation where it is possible to isolate a problem well enough that knowledgeable people can fix it quickly.
We would like to have Fatdog64 work on everything automatically. But of course that's not going to happen. We've made design choices which will work well on most hardware and not on others. Puppy has done the same. However the well supported hardware will vary between the two.