Getty problems since last update
-
Updated last night (snap is (i386) built on Fri Jan 21 06:52:27 EST 2011) and my lsystem-log is filled with this:
Jan 22 14:53:04 init: getty repeating too quickly on port /dev/ttyu0, sleeping 30 secs Jan 22 14:53:04 init: getty repeating too quickly on port /dev/ttyu0, sleeping 30 secs Jan 22 14:52:34 getty[6235]: login_tty /dev/ttyu0: Inappropriate ioctl for device Jan 22 14:52:34 getty[6235]: login_tty /dev/ttyu0: Inappropriate ioctl for device Jan 22 14:52:34 init: getty repeating too quickly on port /dev/ttyu0, sleeping 30 secs Jan 22 14:52:34 init: getty repeating too quickly on port /dev/ttyu0, sleeping 30 secs Jan 22 14:52:03 init: getty repeating too quickly on port /dev/ttyu0, sleeping 30 secs Jan 22 14:52:03 init: getty repeating too quickly on port /dev/ttyu0, sleeping 30 secs Jan 22 14:52:03 getty[42779]: tcsetattr /dev/ttyu0: Device not configured Jan 22 14:52:03 getty[42779]: tcsetattr /dev/ttyu0: Device not configured Jan 22 14:51:33 init: getty repeating too quickly on port /dev/ttyu0, sleeping 30 secs Jan 22 14:51:33 init: getty repeating too quickly on port /dev/ttyu0, sleeping 30 secs Jan 22 14:51:33 getty[40023]: tcsetattr /dev/ttyu0: Device not configured Jan 22 14:51:33 getty[40023]: tcsetattr /dev/ttyu0: Device not configured Jan 22 14:51:03 init: getty repeating too quickly on port /dev/ttyu0, sleeping 30 secs Jan 22 14:51:03 init: getty repeating too quickly on port /dev/ttyu0, sleeping 30 secs Jan 22 14:50:33 init: getty repeating too quickly on port /dev/ttyu0, sleeping 30 secs Jan 22 14:50:33 init: getty repeating too quickly on port /dev/ttyu0, sleeping 30 secs Jan 22 14:50:33 getty[7831]: login_tty /dev/ttyu0: Inappropriate ioctl for device Jan 22 14:50:33 getty[7831]: login_tty /dev/ttyu0: Inappropriate ioctl for device Jan 22 14:49:33 getty[42261]: open /dev/ttyu0: No such file or directory Jan 22 14:49:33 getty[42261]: open /dev/ttyu0: No such file or directory Jan 22 14:49:02 init: getty repeating too quickly on port /dev/ttyu0, sleeping 30 secs Jan 22 14:49:02 init: getty repeating too quickly on port /dev/ttyu0, sleeping 30 secs Jan 22 14:48:32 init: getty repeating too quickly on port /dev/ttyu0, sleeping 30 secsI have enabled before the serial console in "System" -"Advanced". Disabled it again to see if anything changes, but nothing. Same as before.
-
If you're still having trouble then search the forums. I had this problem and posted the solution already.
GB
-
yep, your right. Answer was there.
This time that corruption was on a full install, its not a nanobsd, so maybe that check would be applied to any kind of install, not only nanobsd?
Thanks for your answer.
-
Update:
When i have "This will enable the first serial port with 9600/8/N/1 " ticked, with every update the log is filled with mentioned entries.
So a check of /etc/gettytab brought this error (if its one):default:\ ::cb:ce:ck:lc:fd#1000:im=\r\n%s/%m (%h) (%t)\r\n\r\n:sp#1200:\ :if=/etc/issue:I deleted the first colon and restarted getty.
Check of the other entry as mentioned here (http://forum.pfsense.org/index.php/topic,31151.msg161251.html#msg161251) was ok, only the baud-rate differed. Was 115200, i changed to 9600.Now i get this:
Jan 26 15:27:40 init: getty repeating too quickly on port /dev/ttyu0, sleeping 30 secs Jan 26 15:27:40 init: getty repeating too quickly on port /dev/ttyu0, sleeping 30 secs Jan 26 15:27:10 getty[8307]: login_tty /dev/ttyu0: Inappropriate ioctl for device Jan 26 15:27:10 getty[8307]: login_tty /dev/ttyu0: Inappropriate ioctl for deviceOnly disabling the serial console helps to get rid of this errors. So at the moment i can't use the serial console. :(
-
This is definitly broken!
I have with every update a doubel colon in m gettytab! Should i open a bug-report? Is there any other person having this feature?
Its annoying!Serial console is still not usable!
-
That entry is supposed to start with two colons, at least it does on all my installs.
I don't see any errors like that at all, and my VMs with serial console turned on work great.
