GoldenFalcon07
Posts: 6
Joined: Sun May 12, 2019 8:30 am

GLES Surface Error When Booting Raspberry Pi 3

Sun May 12, 2019 9:03 am

Upon booting my Raspberry Pie the splash screen plays fully. then the system crashes to an error screen that reads as follows:

LVL10 Error Creating SDL window.
Could not create GLES window surface
Lvl 10 renderer failed to initialize
Lvl 10 window failed to initialize

Before this error occurred I had deleted the # symbol from nano. An action which I now regret. Seeing as I have no idea what I'm doing. The YouTube tutorial I was watching said that this would clear up an issue I was having with my splash Screen. It did, but broke emulation station.

I am a novice user of the Raspberry Pi and have no idea what went wrong other than what is stated above. All I wan't is to play retro games on the Pi and have no interest in modding or tampering with the Pi's code anymore.

Any help would be greatly appreciated.

jamesh
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 22047
Joined: Sat Jul 30, 2011 7:41 pm

Re: GLES Surface Error When Booting Raspberry Pi 3

Sun May 12, 2019 10:28 am

So presumably you edited config.txt and removed the # from one of the lines in there, I suspect the GL driver line.

You need to use a card reader to read the SD card in another device, edit config.txt again and replace the #.

Or simply write a new SD card with whatever image you are using.
Principal Software Engineer at Raspberry Pi (Trading) Ltd.
Contrary to popular belief, humorous signatures are allowed. Here's an example...
"My grief counseller just died, luckily, he was so good, I didn't care."

GoldenFalcon07
Posts: 6
Joined: Sun May 12, 2019 8:30 am

Re: GLES Surface Error When Booting Raspberry Pi 3

Sun May 12, 2019 10:33 am

Thank you for the quick reply.

If anyone has the time could you help me through that process. I'm in front of my PC now, just need to edit the right line of code.

GoldenFalcon07
Posts: 6
Joined: Sun May 12, 2019 8:30 am

Re: GLES Surface Error When Booting Raspberry Pi 3

Sun May 12, 2019 11:03 am

When Trying to access the Micro USB two Drives appear, Boot and USB Drive J. Boot has nothing in the Config.txtn folder and Drive J says " You need to format in order to use drive J". I have no idea what I'm supposed to do to access the correct file.

Also more info on what I did if it helps:

I acessed the , "sudo nano /boot/config.txt" file and deleted the # symbol in front of "disable_overscan=1".

User avatar
rpdom
Posts: 14079
Joined: Sun May 06, 2012 5:17 am
Location: Chelmsford, Essex, UK

Re: GLES Surface Error When Booting Raspberry Pi 3

Sun May 12, 2019 11:12 am

GoldenFalcon07 wrote:
Sun May 12, 2019 11:03 am
Boot has nothing in the Config.txtn folder
config.txt is a file, not a folder (directory). That is the file you should edit. Something like Notepad++ is ideal for that, or it might work in wordpad.

Whatever you do, do NOT format the "J drive". That will destroy your Raspbian installation. Windows doesn't understand Linux disk formats and incorrectly states that they need to be formatted to Windows layouts.
Signature is on holiday.

GoldenFalcon07
Posts: 6
Joined: Sun May 12, 2019 8:30 am

Re: GLES Surface Error When Booting Raspberry Pi 3

Sun May 12, 2019 11:55 am

I have all of the software needed to edit the files, but I don't know which files to edit. The Config.txt file dose not show anything in it. 0kb's of data.
I am Accessing the Boot Drive. Not the J drive.

Other than that I have no idea what to do.

GoldenFalcon07
Posts: 6
Joined: Sun May 12, 2019 8:30 am

Re: GLES Surface Error When Booting Raspberry Pi 3

Sun May 12, 2019 12:23 pm

Would I be better off getting a new SD card and starting over, or would should I continue trying to fix it?

I can't believe deleting one small symbol causes this big an issue with retro pi.

Edit:
If I am understanding correctly on Microsoft OS, the "config.txt" file will show up as empty or it will not exist all together. Changes can be made to the internal files by adding things to the empty "config.txt" file.

Does anyone know how I do that, or if that is the right thing to do?

GoldenFalcon07
Posts: 6
Joined: Sun May 12, 2019 8:30 am

Re: GLES Surface Error When Booting Raspberry Pi 3

Sun May 12, 2019 12:49 pm

Also, does anyone have original base files for the config.txt. If I had those I could just copy and paste them and see if that works.

User avatar
rpdom
Posts: 14079
Joined: Sun May 06, 2012 5:17 am
Location: Chelmsford, Essex, UK

Re: GLES Surface Error When Booting Raspberry Pi 3

Sun May 12, 2019 1:54 pm

The Pi will usually boot with an empty config.txt file, but it is unusual for it to be completely empty. Even Windows OS should be able to read the file's contents and edit it.

I don't have an unmodified version of the file to hand, but I'm pretty sure that all entries are commented out by default, so an empty file should work.
Signature is on holiday.

Andyroo
Posts: 2827
Joined: Sat Jun 16, 2018 12:49 am
Location: Lincs U.K.

Re: GLES Surface Error When Booting Raspberry Pi 3

Sun May 12, 2019 11:37 pm

This is my config.txt

Code: Select all

# 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=1

# 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.
#arm_freq=800

# Uncomment some or all of these to enable the optional hardware interfaces
dtparam=i2c_arm=off
#dtparam=i2s=on
dtparam=spi=off

# Uncomment this to enable the lirc-rpi module
#dtoverlay=lirc-rpi

# Additional overlays and parameters are documented /boot/overlays/README

# Enable audio (loads snd_bcm2835)
dtparam=audio=on
Just be careful how you create it - do not use the normal Windows Notepad as it will add a <cr><lf> at the end of each line rather than just the Linux <lf> Notepad++ was free last time I looked and could be set to use <lf> only.
Need Pi spray - these things are breeding in my house...

Return to “Graphics programming”