LinuxQuestions.org - /dev/tty1 no longer exists

- Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)

- - /dev/tty1 no longer exists (https://www.linuxquestions.org/questions/linux-newbie-8/dev-tty1-no-longer-exists-259644/)

/dev/tty1 no longer exists

After successfully installing SuSE 9.2 pro on my dell latitude laptop last week, I played around with 'suspend to disk' yesterday fand tested it a few times and it worked - was able to suspend, and recover. Great.

Then I decided to do my first 'YOU' (YaST Online Update). Seemed to go well, in that all messages were fine.

However, on reboot, I had all kinds of issues with the file system - reiserfs, reporting bad blocks, etc. With help from this forum, I was able to 'fix' this and reboot (ran reiserfsck with the --rebuild-tree option).

Now, my 'only' problem is that tty1 does not work. After booting successfully all the way into the gui, when I ctrl-alt-F1 to tty1, it shows the tail-end of the boot process, but is non-responsive, and there is a message that appears every 5 mins or so - INIT: Id "1" respawning too fast: disabled for 5 minutes'.

Doing a grep on messages, I see a lot of 'linux mingetty [xxx]: /dev/tty1: No such file or directory' lines.

looking in /dev, there are tty0, tty2, tty3, etc but no tty1 ...

So somehow /dev/tty1 is gone ... how do I recover it?

Is this likely to be a consequence of the suspend to disk experiments, the online update, or some random failure in my filesystem ...?

Thanks!

It can be re-created with 'mknod /dev/tty1 c 4 1' (creates a character device, major number 4, minor 1. The ownership should be root:root, permission 0600. If your dev files are created by an auto-system like udev, this won't survive a reboot. You'll need to check your udev config (/etc/udev directory) if that's the case.

Edit to add: Suspend to disk may be the culprit here -- I've heard of it doing wacky things, and it's not fully bug-free yet.

Quote:

Originally posted by btmiller
It can be re-created with 'mknod /dev/tty1 c 4 1' (creates a character device, major number 4, minor 1. The ownership should be root:root, permission 0600.

Thanks a lot! I ran the mknod command, and re-created the device. I want to double-check your instructions on ownership and permissions ...

Right after creating the device (mknod...), ls -l tty? showed this (first three devices only shown):

Code:

crw--w----  1 root      root 4, 0 Nov 20 10:01 tty0

crw-rw----  1 root      tty  4, 1 Nov 26 22:35 tty1

crw--w----  1 root      tty  4, 2 Nov 26 22:44 tty2

Then I issue 'chmod tty1 0600', and the files look like this:

Code:

crw--w----  1 root      root 4, 0 Nov 20 10:01 tty0

crw-------  1 root      tty  4, 1 Nov 26 22:35 tty1

crw--w----  1 root      tty  4, 2 Nov 26 22:44 tty2

So my first verification is, should tty1 really be different from tty0 and tty2?

Next, I issue 'chown .root tty1', and the files look like this:

Code:

crw--w----  1 root      root 4, 0 Nov 20 10:01 tty0

crw-------  1 root      root 4, 1 Nov 26 22:35 tty1

crw--w----  1 root      tty  4, 2 Nov 26 22:55 tty2

So ownership on tty0 and tty1 is different from tty2 and above?

THanks again!

The way I usually see it is that terminals with no one logged in have permission 600. Those with a user logged in have permissions 640 root:tty so that anyone in the tty group can write tpo the terminal (this is for the write or wall programs). Ithink getty or login sets that all up when you login, but I'm not 100% certain.