@Ranma doesn't log level 0 remove all text?

I don't think stty would help here, but try adding quiet to the cmdline.txt line, this should suppress the boot messages. See more options at https://retropie.org.uk/docs/FAQ/#how-do-i-hide-the-boot-text.

@sebar said in SD card not booting in Zero W, in 3B it does:

Why insist on this old System? It contains tweaks, which I am not able to reproduce.

We don't support 3rd party systems, we don't know how they've been configured and set-up.
Your image has a special kernel, which might as well not work on a Pi 0 if it was optimized for the Pi3 CPU.

Found it, thanks!

I solved it!

https://retropie.org.uk/forum/topic/4057/can-t-remove-text-in-bootscreen/14

Add "clear" as the first line in /opt/retropie/configs/all/autostart.sh. Never seen that tip anywhere other than that thread, but it worked!

@Cakedaddy is there any fix for this? Having the identical issue...

Thanks for your time herb_fargus. I have a feeling that if I replace the cmdline.txt with the following it will sort itself out:

dwc_otg.lpm_enable=0 console=serial0,115200 console=tty2 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait quiet loglevel=3 logo.nologo consoleblank=0 plymouth.enable=0

This is just to get back to the original problem of finding out why sudo apt-get update is returning the attached errors!!

This is an old issue but, I have something to add. The button response, is only accepted right after the dialog/launching.png disappears. There is it seems, either a huge delay, or joy2key won't trigger until the end of the script. I'm guessing this could be fixed, its worth fixing. Additional features should be added to run command as well, though I can't think of any good ones right now.