Mikrotik CRS125

[Adrian Chadd]

Something is oddly broken there. I've not seen this on the mips32
boards but i haven't tried recently. I'll go spin up one later
tonight.

-a


On 17 January 2014 16:22, Joe Holden <lists at rewt.org.uk> wrote:
> On 17/01/2014 23:10, Warner Losh wrote:
>>
>>
>> On Jan 17, 2014, at 12:39 PM, Stanislav Sedov wrote:
>>
>>> On Fri, 17 Jan 2014 15:36:26 +0000
>>> Joe Holden <lists at rewt.org.uk> mentioned:
>>>
>>>> So, thought I'd have a crack at booting FreeBSD on it, got it booting
>>>> from nfs, but:
>>>>
>>>> Jan  1 00:06:13 crs125 getty[888]: tcsetattr /dev/ttyu0: Invalid
>>>> argument
>>>> Jan  1 00:06:13 crs125 getty[889]: tcsetattr /dev/ttyu0: Invalid
>>>> argument
>>>> Jan  1 00:06:13 crs125 getty[890]: tcsetattr /dev/ttyu0: Invalid
>>>> argument
>>>> Jan  1 00:06:13 crs125 getty[891]: tcsetattr /dev/ttyu0: Invalid
>>>> argument
>>>> Jan  1 00:06:14 crs125 getty[892]: tcsetattr /dev/ttyu0: Invalid
>>>> argument
>>>> Jan  1 00:06:14 crs125 init: getty repeating too quickly on port
>>>> /dev/ttyu0, sleeping 30 secs
>>>>
>>>
>>> This sounds like the kernel and world are inconsistent.  Are you
>>> sure you're not booting 10x world on HEAD kernel or vice versa?  I
>>> saw something similar once when I had unmatching world and kernel.
>>
>>
>> What does ls /dev/tty* tell you?
>>
>> Warner
>>
> What is expected really:
>
> root at crs125:~ # ls -la /dev/tty*
> crw-------  1 root  wheel  0x18 Jan  1 00:00 /dev/ttyu0
> crw-------  1 root  wheel  0x19 Jan  1 00:00 /dev/ttyu0.init
> crw-------  1 root  wheel  0x1a Jan  1 00:00 /dev/ttyu0.lock
>
> _______________________________________________
> freebsd-mips at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-mips
> To unsubscribe, send any mail to "freebsd-mips-unsubscribe at freebsd.org"