Solved getty: open /dev/ttyu0: No such file or directory?

fredvs

fredvs

Hello.

After boot, before login, there is that message =>
Code: 
getty: open /dev/ttyu0: No such file or directory

Then login can be done without problem.

What does that message mean ?

Thanks.

Fre;D
 
Last edited by a moderator:
It seems that devfs(8) isn't creating ttyu0 in /dev.
Code: 
getty: open /dev/ttyu0: No such file or directory
What machine processor architecture are you using?

uname -p output tells you this.

Note that the uname -a output provides more information
Code: 
% uname -a
FreeBSD bsd.nix 10.2-RELEASE-p2 FreeBSD 10.2-RELEASE-p2 #1: Wed Aug 26 00:22:21 CEST 2015     cjpm@bsd.nix:/usr/obj/usr/src/sys/GENERIC  amd64
Read uname(1) man page for details.
 
cpm said:
What machine processor architecture are you using?
Click to expand...
Hello and thanks for help.
The machine is a Netbook Toshiba Satellite NB10, with Pentium M and 4 GB of ram.
uname -p:
Code: 
x86_64
cpm said:
It seems that devfs(8) isn't creating
Click to expand...

Yes, it is very strange.
That problem appears only with VirtualBox.
With VMware, with exactly same config, ttyu0 is created in /dev.

Also I do not understand why, with same config in VirtualBox and VMware, in VirtualBox, at booting, I get as first message:
Code: 
gptboot: error 1 lba 11439007
gptboot: unable to read backup GPT header.
...
console comconsole failed to initialize.
Then, after a short moment, boot continue and I can login and load startx without problems.
Note that, with VMware, those error messages do not appear.

Thanks.

Fred.
 
Hello.

Sorry to come back with the error =>
fredvs said:
gptboot: error 1 lba 11439007 gptboot: unable to read backup GPT header. ... console comconsole failed to initialize.
Click to expand...

After Googling, I find this => same problem

So, to resume:
with VirtualBox, if disk is:
IDE (ada0) => no problem
SCSI (da0) => problems with gpt header

With VMware, no problems, IDE or SCSI

If that error is not lethal, (because boot is ok), is it possible to hide that message ?

Thanks.

Fre;D
 
tobik said:
Regarding /dev/ttyu0: By default VirtualBox VMs don't have an enabled serial port. Check if it is enabled.
Click to expand...
Yep, thanks.

Yes, I did it yesterday and it solved, indeed, /dev/ttyu0 problems:

Enabling serial port message disappear.

Huh, is it forbidden to delete all lines referring to /dev/ttyu* in /etc/ttys config file?
 
cpm said:
You can put a comment symbol (#) at the beginning of the line representing each virtual console.
https://www.freebsd.org/doc/handbook/consoles.html#consoles-virtual
Click to expand...
OK, thanks.

According to the FreeBSD Handbook:
Do not comment out the line for the system console ttyv0. Note that the last virtual console (ttyv8) is used to access the graphical environment if Xorg. Note that the last virtual console (ttyv8) is used to access the graphical environment if Xorg
Click to expand...
Huh, I have commented all ttyu0 (no problems with ttyv*) => What is the difference between ttyu and ttyv?

Concretely, the only thing that I noticed after commenting all ttyu is no more errors messages.

Fre;D
 
They are character devices. According to FreeBSD Handbook, serial ports are named /dev/ttyuN and /dev/cuauN where N is the port number, starting from zero and the first virtual console is named ttyv0.

Read Chapter 25. Serial Communications for more details.
 
You must log in or register to reply here.
Back
Top