Remove text from boot specially just before emulationstation starts to load

Clyde

@blonqe Did you do all steps in this post?

In addition, you could try #5 of the first answer in this Q&A, and change loglevel=3 to loglevel=0 in your /boot/cmdline.txt.

blonqe

@clyde said in Remove text from boot specially just before emulationstation starts to load:

@blonqe Did you do all steps in this post?

In addition, you could try #5 of the first answer in this Q&A, and change loglevel=3 to loglevel=0 in your /boot/cmdline.txt.

@Clyde thanks for the info, were getting closer ;) I went through the whole post on the link you provided, removing the kernel info helped remove one of the lines.

I'm left now with the top line stating the last time I logged in and that's it.

If I can get this removed that's everything.

Clyde

@blonqe Did you execute this command?

touch ~/.hushlogin

(#5 of the Q&A I linked above)

blonqe

@clyde said in Remove text from boot specially just before emulationstation starts to load:

@blonqe Did you execute this command?
touch ~/.hushlogin
(#5 of the Q&A I linked above)

@Clyde yeah I've tried everything in the link you provided, so I'm not sure what else to do?

It's really annoying as everything is clean, apart from this one line of txt :(

mitu

@blonqe are you executing the command above as user pi or as root ? Should be as the pi user.

blonqe

@mitu said in Remove text from boot specially just before emulationstation starts to load:

@blonqe are you executing the command above as user pi or as root ? Should be as the pi user.

@Clyde @mitu thanks very much for both of your help, I was inputting as root and not pi user, soon as I changed to pi it worked ;)

I have a clean setup now, cheers guys

Clyde

@blonqe Have fun. :)

herb_fargus

@clyde I've updated the wiki page with a more definitive boot text removal.

https://github.com/RetroPie/RetroPie-Setup/wiki/FAQ#how-do-i-hide-the-boot-text

Clyde

@herb_fargus Nicely done and well arranged! One detail about touch ~/.hushlogin: Could you mention that it has to be either executed as the user pi or used with the full path, in case someone tries to use it while logged in as root, like the TO of this thread did at first? Alternatively, you could use the full path in your example right away. Thanks!

herb_fargus

@clyde people really shouldn't be messing with things logged in as root if they don't know what they are doing. Tis what sudo is for. Plus I run things on my pc which has a different username so I try and keep paths agnostic. I could probably make a note about the user though

Clyde

@herb_fargus Being a long-time *buntu user, I'm absolutely with you on the root/sudo issue. A note may prevent some questions, though. Do as you please. :)