Removing boot text - Pi 400
-
Hi all, hoping you can help. Trying to do a fresh install of Retropie on my Pi 400. I flash the latest image just fine and boot it up. I update the whole thing then it shows me it's now version 4.8.9, All underlying packages are also updated. I figure as the last release was a couple of years ago, this is prudent but let me know it not.
Anyway - I follow my usual guides I keep to remove the boot up text, but when I do this I'm finding that I can no longer boot. I also change a couple of parameters so that the Pi runs in 720p (emulation typically works better in the past when this is set) and an overclock. Also there's a setting I change for the overscan as it's in a box onscreen until I do (usually).
I've added the files here that I've amended. Please could someone advise where I'm going wrong? All I get after these changes is a multi-coloured screen which then goes black and stays there ad infinitum. My suspicion is my guides are now outdated but I can find no other, more recent solutions. Many thanks all.
cmdline.txt dwc_otg.lpm_enable=0 console=serial0,115200 console=tty3 root=PARTUUID=xxxxxxxx-xx rootfstype=ext4 quiet loglevel=3 logo.nologo vt.global_cursor_default=0
config.txt # For more options and information see # http://rpf.io/configtxt # Some settings may impact device functionality. See link above for details # uncomment if you get no picture on HDMI for a default "safe" mode #hdmi_safe=1 # uncomment this if your display has a black border of unused pixels visible # and your display can output without overscan disable_overscan=1 # uncomment the following to adjust overscan. Use positive numbers if console # goes off screen, and negative if there is too much border #overscan_left=16 #overscan_right=16 #overscan_top=16 #overscan_bottom=16 # uncomment to force a console size. By default it will be display's size minus # overscan. #framebuffer_width=1280 #framebuffer_height=720 # uncomment if hdmi display is not detected and composite is being output #hdmi_force_hotplug=1 # uncomment to force a specific HDMI mode (this will force VGA) hdmi_group=1 hdmi_mode=4 # uncomment to force a HDMI mode rather than DVI. This can make audio work in # DMT (computer monitor) modes hdmi_drive=2 # uncomment to increase signal to HDMI, if you have interference, blanking, or # no display #config_hdmi_boost=4 # uncomment for composite PAL #sdtv_mode=2 #uncomment to overclock the arm. 700 MHz is the default. over_voltage=6 arm_freq=2000 v3d_freq=750 # Uncomment some or all of these to enable the optional hardware interfaces #dtparam=i2c_arm=on #dtparam=i2s=on #dtparam=spi=on # Uncomment this to enable infrared communication. #dtoverlay=gpio-ir,gpio_pin=17 #dtoverlay=gpio-ir-tx,gpio_pin=18 # Additional overlays and parameters are documented /boot/overlays/README # Enable audio (loads snd_bcm2835) dtparam=audio=on [pi4] # Enable DRM VC4 V3D driver on top of the dispmanx display stack dtoverlay=vc4-fkms-v3d max_framebuffers=2 [all] #dtoverlay=vc4-fkms-v3d overscan_scale=1
-
Remove the oveclock and try to find the configuration for 'quiet' boot without it.
-
Thanks for replying. Will give that a go, thanks. So, the cmdline.txt is otherwise looking OK?
-
Thank you. Pointing me towards my overclock revealed the culprit. I was using my old Pi 3 commands which are not relevant to the Pi 400. Stupidly I had:
v3d_freq=750
rather than:
gpu_freq=750
Changing this fixed the boot. My thanks again.
-
@Ranma doesn't log level 0 remove all text?
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.