TTY no longer available after upgrade to 5.7.3 - Plymouth splash is seen.

[oshunluvr]

Anyone else seeing this? I can no longer go to CTRL-ALT-F1 thru F6. This started with the upgrade that took me to 5.7.3. Attempting to go to any TTY - both before logging in or after.


All I get now is the Plymouth splash screen on all the TTYs.


Any suggestions on how to fix this?

[MoonRise]

Hmmmm, hard to say. CTRL-ALT-F1 to F6 seems to work here. I wouldn't know where to begin to look though.

[GreyGeek]

I'm running 16.04 with Neon running on top. Plasma5 is 5.7.3.
Here are the Plymouth files installed on my box:

[oshunluvr]

Looks like plymouthd continues to run after boot up - using 25% CPU. I can kill it, but the TTYs still don't work.

[vinnywright]

I am not seeing this @hear ,,,,,all TTY's working as expected and switching back to TTY7 (theGUI) ,,,,,well except for a second of scrambled graphics until it recovers the display .

O and plymouthd is not running after I log in

vinny@vinny-Bonobo-Extreme:~$ ps aux | grep plymouthd
vinny 8340 0.0 0.0 14224 964 pts/3 S+ 11:17 0:00 grep --color=auto plymouthd

that line is just "grep"

VINNY

[GreyGeek]

I am not seeing this @hear ,,,,,all TTY's working as expected and switching back to TTY7 (theGUI) ,,,,,well except for a second of scrambled graphics until it recovers the display .

O and plymouthd is not running after I log in



that line is just "grep"

VINNY

"He's dead, Jim!"
As this systemd log shows:

[oshunluvr]

No, he's not...

[GreyGeek]

Stop the "waiting" service and see of your TTY's come back.

[vinnywright]

No, he's not...

I have the same ,,,,,,,,,,,,



but TTY's still work



and you would not believe the the hoops I jumped through to get the frame buffer to work IE:/dev/fb0 ,,,,,so I could get a shot of a TTY ,,,,, LOL

Vinny

[Snowhog]

...you would not believe the the hoops I jumped through to get the frame buffer to work IE:/dev/fb0 ,,,,,so I could get a shot of a TTY ,,,,, LOL

Vinny

But you will tell us, right?

[vinnywright]

But you will tell us, right?

well since you ask ,,,,,I will try ,,,it's was late .

I think it went something like this

echo "fbcon" | sudo tee -a /etc/initramfs-tools/modules
echo "vesafb" | sudo tee -a /etc/initramfs-tools/modules

then

sudo update-initramfs -u -k all

then

sudo hwinfo --framebuffer

"hwinfo"had to be installed ,,,,,,,we look hear to get the hex# of the supported resolutions .

@hear I get this

vinny@vinny-Bonobo-Extreme:~$ sudo hwinfo --framebuffer
[sudo] password for vinny: 
02: None 00.0: 11001 VESA Framebuffer                           
  [Created at bios.459]
  Unique ID: rdCR.ttXOVweMIC5
  Hardware Class: framebuffer
  Model: "NVIDIA GK104 Board - 20530004"
  Vendor: "NVIDIA Corporation"
  Device: "GK104 Board - 20530004"
  SubVendor: "NVIDIA"
  SubDevice: 
  Revision: "Chip Rev"
  Memory Size: 14 MB
  Memory Range: 0xd1000000-0xd1dfffff (rw)
  Mode 0x0300: 640x400 (+640), 8 bits
  Mode 0x0301: 640x480 (+640), 8 bits
  Mode 0x0303: 800x600 (+800), 8 bits
  Mode 0x0305: 1024x768 (+1024), 8 bits
  Mode 0x0307: 1280x1024 (+1280), 8 bits
  Mode 0x030e: 320x200 (+640), 16 bits
  Mode 0x030f: 320x200 (+1280), 24 bits
  Mode 0x0311: 640x480 (+1280), 16 bits
  Mode 0x0312: 640x480 (+2560), 24 bits
  Mode 0x0314: 800x600 (+1600), 16 bits
  Mode 0x0315: 800x600 (+3200), 24 bits
  Mode 0x0317: 1024x768 (+2048), 16 bits
  Mode 0x0318: 1024x768 (+4096), 24 bits
  Mode 0x031a: 1280x1024 (+2560), 16 bits
  Mode 0x031b: 1280x1024 (+5120), 24 bits
  Mode 0x0330: 320x200 (+320), 8 bits
  Mode 0x0331: 320x400 (+320), 8 bits
  Mode 0x0332: 320x400 (+640), 16 bits
  Mode 0x0333: 320x400 (+1280), 24 bits
  Mode 0x0334: 320x240 (+320), 8 bits
  Mode 0x0335: 320x240 (+640), 16 bits
  Mode 0x0336: 320x240 (+1280), 24 bits
  Mode 0x033d: 640x400 (+1280), 16 bits
  [COLOR=#ff0000]Mode 0x033e: 640x400 (+2560), 24 bits[/COLOR]
  Mode 0x034b: 1920x1080 (+1920), 8 bits
  Mode 0x034c: 1920x1080 (+3840), 16 bits
  Mode 0x034d: 1920x1080 (+7680), 24 bits
  Mode 0x0360: 1280x800 (+1280), 8 bits
  Mode 0x0361: 1280x800 (+5120), 24 bits
  Config Status: cfg=new, avail=yes, need=no, active=unknown

I chose to use the line in red ,,,,, "0x033e"

we then reboot and insert "vga=0x033e" in the linux boot line of the grub menu after "quiet splash and vthandoff ,,,or whatever .

and all the TTY's are in the mode of Mode 0x033e: 640x400 (+2560), 24 bits.

then install fbcat or befor you do all this ,,,,,,,wile in the TTY you just use fbcat to grab whats in the framebuffer and direct it to a file .

fbcat only outputs in .ppm format so after you have your shot.ppm use convert to chang to .png or whatever ,,,"convert" is part of the "imagemagick"

so it could be a one liner from in the TTY

sudo fbcat > myshot.ppm && convert myshot.ppm myshot.png

but all this gobeldy gook doesn't help @oshunluvr very much I don't suppose

VINNY

[vinnywright]

just a side note and strange occurrence on the framebuffer deal ,,,,,,,,,,,

when I make it active with the "vga=0x034d" boot code ,,,,, I get a totally different plymouth boot splash ,,,,,,,,,,,,,,,,,,,,,,,,,





not the plane blue background white letters and progress bar progressing across the bottom of the screen.


did you ever fix this @oshunluvr ?

VINNY

[oshunluvr]

No, but it fixed itself just today. I was literally minutes away from a re-install to resolve this issue when after the last reboot before reinstalling, the TTYs came back. Today, I installed Virtualbox, libnotify-bin, and namebench and updated VLC. Seems unlikely that any of those was the fix, but whatever - I'm happy for the moment.

I currently have not re-enabled plymouth at boot up.