I'm running a Raspbian Buster server with no Xserver. I want to display wallpaper on a connected television but /dev/tty1 keeps over writing /dev/fb0 either with a blinking cursor or just refreshing randomly 60 seconds later after I make the cursor invisible (from getty@tty1.service). My new strategy is to completely prevent /dev/tty1 from ever writing to the framebuffer.

Thanks for any help.

  • Is there any reason that you can't just use a X server or Wayland server? Which will handle tty problem for you Aug 13 '19 at 1:19
  • I'd prefer to avoid the overhead and I'm testing writing images to the framebuffer directly.
    – deanresin
    Aug 13 '19 at 1:21
  • 1
    @mosvy interesting. I think I will test your idea soon. But I have solved my problem I think by disabling the getty@tty1.service and then making tty1 cursor invisible. It seems to be working.
    – deanresin
    Aug 13 '19 at 2:08
  • 2
    The problem with disabling that getty@tty1.service and no cross-over serial cable around is that you may not be able to access your device if ssh or anything else goes wrong.
    – mosvy
    Aug 13 '19 at 2:11
  • 2
    If something goes wrong you can always boot recovery mode from grub and get an emergency shell. Aug 13 '19 at 18:26

To stop /dev/tty1 from overwriting the buffer I'm using

systemctl stop getty@tty1.service and then make the cursor invisible with..

/usr/bin/tput civis > /dev/tty1

This allows me access to console after reboot should I lose access via ssh.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.