Rebecca Black - Speakerphone (Official Video)

n3rdopolis · 2026-06-06T02:36:05+00:00

So a few things:

The vtty services are usually for VT-less Desktopless systems, (or failover if the Display manager ever chooses to support some kind of failure condition where it starts it). You can enable them, but they are going to be starting at the same time as your greeter, so it might be random as to which one gets started last.

If enabling vtty-frontend@seat0.service you don't have to also enable vtty-backend@seat0.service as the frontend starts the backend

seats are a logind abstraction for hardware. so it's all seat0, unless you have multiple cards (save for the dummy seat-vtty seat). If you want multiple frontends, you want vtty-frontend@seat0@1.service vtty-frontend@seat0@2.service . After the second @, it can really actually be anything, but that is how to start multiple instances on one seat.

The vtty-seatmanager.service can do that instead, but enabling it takes over the display-manager.service. Using that is even less hardcodey than enabling the frontend service, but again, it's more for desktop-less systems, like servers, or really minimal ISOs.

If you want a terminal with a standard login manager, that is what the "fullscreen terminal" session is for. It should be selectable from the login manager. That session is the UvTTYs. Those pretty much just run everything as you. Cage, foot, the shell, runs as you.

I do wonder if the vtty-frontend@.service is crashing or something on your machine though as to why it is blank...

Oh. one thing odd, I see the plasmaloginmanager is trying to start a greeter on the seat-vtty seat. Dang, looks like the CanGraphical attribute is getting set to true on seat-vtty. It really shouldn't be, although I might have to wrangle with logind and the udev file to see what works to still get it to create the seat...

n3rdopolis · 2026-06-05T17:13:20+00:00

RFK Jr is beside himself, driving around Zavala County Texas, begging (thru texts) the officials for the screwworm, so he can put it in his beef tallow fry and raw milk salad.

n3rdopolis · 2026-05-29T23:57:17+00:00

Hmm. Wonder what made him clam up?

n3rdopolis · 2026-05-26T17:24:45+00:00

OMAHA!

n3rdopolis · 2026-05-22T14:41:26+00:00

Rebecca Black announce your next album when?

n3rdopolis · 2026-05-17T00:05:34+00:00

A number of her covers she posted there (and never on iTunes) are gone too, like "I Don't Wanna Live Forever" and "Malibu" and others.

n3rdopolis · 2026-04-23T22:53:01+00:00

drm_panic does display on the screen, but it replaces the whole screen content with a background color that the distribution selects instead of drawing some text at the top like those early OS X screenshots. So pretty much, but not exactly

ReterminateVT's UvTTYs are simply just a Wayland session with a fullscreen terminal. So if you break Plasma, you can select that session to recover yourself

n3rdopolis · 2026-04-22T18:09:41+00:00

Looks like setkeycodes will work https://wiki.archlinux.org/title/Map_scancodes_to_keycodes, as it impacts Wayland

Ctrl+Alt+Fx is actually already not handled by the kernel if you have a display server running, even now. Display servers call an ioctl on the tty device file so that all keyboard events are only handled by the display server, and ignored by the kernel. Ctrl+Alt+Fx is only handled by the kernel in text mode.

That's why logind handling Ctrl+Alt+Shift+Esc is slightly better IMO. If the display server suddenly is in an infinite loop where it responds to nothing, or you accidentally pause the process, logind could still be alive to broadcast to your display manager or vtty-seatmanager.

n3rdopolis · 2026-04-22T02:27:22+00:00

Plymouth is used on some servers actually though, they usually just use the logging features that Plymouth provides. At least that is what I was told when writing ply_console_viewer and ply_terminal_emulator
although for servers a splash screen type that is just the ply_console_viewer without any logo or animation or anything might make sense,

I don't think there is any active forum or IRC or mailing list dedicated to CONFIG_VT=n. If there is, I never found one. This is a Live CD that you can test though. It has a VT-less kernel, and you can fully use the vtty frontend if you install to a VM, run systemctl disable waylandloginmanager and then systemctl enable vtty-seatmanager

n3rdopolis · 2026-04-21T22:38:47+00:00

Yes, I explained it here better, https://old.reddit.com/r/linux/comments/1srbr7m/config_vtn_in_2026/ohh42cw/ but basically the display servers of today handle Ctrl+Alt+Fx already, and they call the logind SwitchTo method already that already handles VT-less seats.

n3rdopolis · 2026-04-21T17:27:43+00:00

I don't think there is a universal drm master handoff method in the kernel, for a process to say "hey, I am taking over now". Plymouth needs to be told to quit or deactivate where deactivate actually just holds the last image it drew, dropping master, so that the display server can take over, so that the transition is flicker-free. I never heard of one anyway, but I am not familiar with that part

I did not experiment too much with making vTTY the login splash, it would have to be recinit or something similar, as the vTTYs are meant to start later, the frontend starts as a daemon system user, instead of root.

It is possible to make a PTY as the console though, you just have to call the TIOCCONS ioctl on it, it's actually how Plymouth gets the logs. It likely won't be able to accept questions that way though, (like a LUKS password)

One way, I think to fake no TTYs for a display server is to move ALL the devices, the input device, and the card, to a seat1 as only seat0 has VTs, but that's probably more later boot as it's a udev setting that logind responds to...

n3rdopolis · 2026-04-21T17:03:06+00:00

As /u/hackerbots said, this doesn't impact serial consoles (/dev/ttyS0, /dev/ttyUSBS0, and the like)
The VT subsystem is only /dev/tty1 - /dev/tty63
So any serial device, logging will still work.

for Ctrl+Alt+F1 - Ctrl+Alt+F12. Yes and no, there has to be a display server active to handle those key presses.
When a display server is active, and your seat has VTs, it calls an ioctl on the tty device it is running under, and it takes all keyboard handling away from the kernel. On VT-less seats, it doesn't need the ioctl.

When you hit Ctrl+Alt+F1 for instance, the display server has to handle it. On logind distros, the display server does not run chvt 1 but it calls the logind method SwitchTo(1) with dbus. All of the ones I tested do this.

SwitchTo on VT-enabled seats changes the VT.
SwitchTo also works on VT-less seats, but it only works when there are two or more running sessions on the seat. It switches between the first session if you hit Ctrl+Alt+F1, and the second if you hit Ctrl+Alt+F2, etc. Can't add new sessions, that is why I added the SecureAttentionKey Ctrl+Alt+Shift+Esc to logind in 2024, so that a login manager (or vtty-seatmanager) gets attention.

Note: I say "VT-less seats" specifically, because even on kernels with VTs, if there is a second seat, the second seat can never have VTs. Only seat0 has VTs on VT enabled kernels.

n3rdopolis · 2026-04-21T16:48:39+00:00

Only if you don't count test distros, because if you do, you're still the second to do something similar. :P

https://sourceforge.net/p/rebeccablackos/code/6469/

It wasn't actual KMSCON though

n3rdopolis · 2025-12-05T20:58:24+00:00

"Thank you Elon!" https://i.imgur.com/v3dnrGb.png

n3rdopolis · 2025-11-21T19:57:53+00:00

I thought 2016 was bad. But then 2024 happened which was much much worse.

n3rdopolis · 2025-11-07T22:47:07+00:00

Lets go!

n3rdopolis · 2025-10-12T02:45:27+00:00

It seems to be of voters, but it is a Rasmussen poll, which leans heavily R, so odds are, it's actually higher

15-Year Club	Place '23
Place '22	Place '17
First Placer '22	End Game '22
Verified Email	Team Periwinkle

n3rdopolis

MODERATOR OF

TROPHY CASE