spaceinvaderParticipant03/12/2016 at 11:15Post count: 67
I don’t know what has happened, but suddenly my retropie boots with the image too big and out of the limits of my tv.
I thought I’d changed some configuration, so I started again with a fresh sd image and the same.
I’ve also tried in a different TV and the same.
What has happened?mydriazeParticipant03/13/2016 at 17:28Post count: 28
Have you check your HDMI cable? Pretty sure it’s not the right answer, but who knows, give it a try.herbfargusMember03/13/2016 at 17:40Post count: 1858
There are overscan values you can play with in /boot/config.txtspaceinvaderParticipant03/14/2016 at 12:14Post count: 67
Tried with a brand new hdmi cable and the same.
I know I can try changing the overscan values, but I don’t understand why before with a new sd imagen it always took the right resolution itself and now it does not…
Anyway, thanks.dankcushionsParticipant03/14/2016 at 12:43Post count: 432
My suspicion is that later firmware updates have changed how overscan works on the pi. i had to change my overscan configuration with the pi3 and 3.6, but the GPU is the same so there shouldn’t be a hardware reason for that (?). so i think maybe the firmware is different in this regard.spaceinvaderParticipant03/14/2016 at 13:05Post count: 67
I forgot to say that the same problem occurs with older images, such as 3.5, 3.4, …
So I don’t relieve it is because of the firmware.
Anyway I’ll try another hdmi_mode…mydriazeParticipant03/14/2016 at 22:44Post count: 28
Even with a fresh 3.6 install? That’s not possible, theorically.spaceinvaderParticipant03/23/2016 at 12:38Post count: 67
Sorry mydriaze. I hadn’t seeen tour response.
Yes, even with a fresh image. It seems like before my tv’s resolution was correctly detected and automaticly put on the config.txt file and now it is not…shakzParticipant03/31/2016 at 18:04Post count: 2
I think there are a couple things you can try.
You will need to edit your /boot/config.txt file
The default settings are as follows.
# 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=1
It sounds like you may need to uncomment force_hotplug. If you dont know how to use vi or edit files in linux just run this.
sudo perl -p -i -e 's/#hdmi_force_hotplug=1/hdmi_force_hotplug=1/g' /boot/config.txt
That just turns this.
so the pie will read it after bootup.
Reboot and see if this works.
If not reverse it running the following command.
sudo perl -p -i -e 's/hdmi_force_hotplug=1/#hdmi_force_hotplug=1/g' /boot/config.txt
Next you can try forcing the pie into 1080p mode. With the following commands. Again they are just uncommenting the variables so your machine will read them on the next boot.
Not sure where you are from so here are the NA and EU setups.
for NTSC (North American TVs 60Hz)
sudo perl -p -i -e 's/#hdmi_group=1/hdmi_group=1/g' /boot/config.txt sudo perl -p -i -e 's/#hdmi_mode=1/hdmi_mode=16/g' /boot/config.txt
to switch back tp default from NTSC settings.
sudo perl -p -i -e 's/hdmi_group=1/#hdmi_group=1/g' /boot/config.txt sudo perl -p -i -e 's/hdmi_mode=16/#hdmi_mode=1/g' /boot/config.txt
for PAL (European TVs 50Hz)
sudo perl -p -i -e 's/#hdmi_group=1/hdmi_group=1/g' /boot/config.txt sudo perl -p -i -e 's/#hdmi_mode=1/hdmi_mode=31/g' /boot/config.txt
To go back to default from pal settings
sudo perl -p -i -e 's/hdmi_group=1/#hdmi_group=1/g' /boot/config.txt sudo perl -p -i -e 's/hdmi_mode=31/#hdmi_mode=1/g' /boot/config.txt
You can see the values here.
Hope this helps you!spaceinvaderParticipant03/31/2016 at 20:30Post count: 67
Yes, I solved the problema editting config.txt and changing hdmi mode to 16, but I don’t understand why before I didn’t need to change it, it seemed like on first boot the correct resolution was detected and now it doesn’t…
Anyway many thanks for the help!
- The forum ‘Video Output on RetroPie’ is closed to new topics and replies.