#289 closed defect (fixed)
F17 syslog filling up with "/dev/ttyS0: not a character device"
| Reported by: | ezyang | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | Fedora 17 |
| Component: | internals | Keywords: | |
| Cc: |
Description
Not sure what it means. Currently syslog-ng has it muted but we should figure out what is going on.
Change History (5)
comment:1 Changed 12 years ago by ezyang
comment:2 Changed 12 years ago by ezyang
Removing /etc/systemd/system/getty.target.wants/getty@tty1.service doesn't appear to do anything.
comment:3 Changed 12 years ago by ezyang
OK, the problem appears to be Grub is passing console=ttyS0 to the kernel:
root=UUID=859724e0-423b-4d08-a971-6b37456f952c ro rd.md=0 rd.lvm=0 rd.dm=0 console=hvc0 KEYTABLE=us console=ttyS0 rd.luks=0 SYSFONT=True LANG=en_US.UTF-8 rhgb quiet
This is causing the agetty process to be spawned.
comment:4 Changed 12 years ago by ezyang
OK, so we can fix it by editing /etc/default/grub and removing console=ttyS0 and running grub2-mkconfig -o /boot/grub2/grub.cfg. I'm not sure if this means we should version that file. Can we fix Kickstart?
comment:5 Changed 12 years ago by ezyang
- Resolution set to fixed
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
My guess is that it's a variant of http://xen.1045712.n5.nabble.com/dev-tty-not-a-character-device-after-reboot-td2566103.html
However, we're in systemd land, so there's no inittab to edit.