kern/147082: [uart] Serial ports unusable

[Mayo Jordanov]

On 2010-05-26, at 12:42 , remko at FreeBSD.org wrote:

> Synopsis: [uart] Serial ports unusable
> 
> State-Changed-From-To: open->feedback
> State-Changed-By: remko
> State-Changed-When: Wed May 26 19:42:36 UTC 2010
> State-Changed-Why: 
> I send my working serial line to Mayo, set status to feedback
> 
> http://www.freebsd.org/cgi/query-pr.cgi?pr=147082

I'm gona re-reply here, to preserve the history.

>>> How-To-Repeat:
>> 1) Edit /etc/ttys, do the ttyu0 line reads:
>> ttyu0	"/usr/libexec/getty std.9600"	vt100	on secure
>> 2) kill -HUP 1
>> 3) Try connecting to it with terminal application
> 
> 
> /etc/ttys
> console    "/usr/libexec/getty Pc"         cons25  on  secure
> 
> /boot/loader.conf
> console="comconsole"
> 
> That enabled serial access to my Soekris device running on FreeBSD8(PFsense), it also works for several remote machines I have.
> 
> Can you confirm that you have these settings in loader.conf and rebooted?!
> 
> -- 
> /"\   Best regards,                        | remko at FreeBSD.org
> \ /   Remko Lodder                      | remko at EFnet
> X    http://www.evilcoder.org/    |
> / \   ASCII Ribbon Campaign    | Against HTML Mail and News

test# cat /boot/loader.conf 
console="comconsole"

looking at the /etc/ttys entry you pasted above, will that enable serial console? That looks like a regular console on the machine itself.

I have rebooted numerous times, and I do get the kernel messages during boot on serial up to the point where getty starts (presumably... I see portion of the messages as nics are getting setup and then nothing).

I have some machines where serial works fine, but I have some machines where it doesn't and behaves the same way as described above. If necessary, I can provide access to a troublesome machine.

Thanks,
mayo