Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 22 Jan 2014 00:02:55 -0800
From:      Adrian Chadd <adrian@freebsd.org>
To:        Joe Holden <lists@rewt.org.uk>
Cc:        "freebsd-mips@freebsd.org" <freebsd-mips@freebsd.org>
Subject:   Re: Mikrotik CRS125
Message-ID:  <CAJ-VmokWQJWqQT_-c5buZrVteLwwZfYqYa%2BynxRpRmDovpb7hQ@mail.gmail.com>
In-Reply-To: <52DD2312.5070605@rewt.org.uk>
References:  <52D94DFA.1090002@rewt.org.uk> <20140117113957.ad3166f3f267a182ee344316@FreeBSD.org> <65734554-982B-4E5E-8662-3775A2FB76B9@bsdimp.com> <52D9C946.1080301@rewt.org.uk> <CAJ-VmonEpK_kmQZm=SicA5XDCuRQN7mgzJu%2BAHU043-w=MBb_Q@mail.gmail.com> <52DD2312.5070605@rewt.org.uk>

next in thread | previous in thread | raw e-mail | index | archive | help
I don't; sorry. Not besides what's in the DB120 configuration file.



-a


On 20 January 2014 05:22, Joe Holden <lists@rewt.org.uk> wrote:
> You wouldn't happen to know what I need to prod to make the switch work do
> you?
>
> arswitch1: <Atheros AR9340 Ethernet Switch> on mdio1
> arswitch1: ar9340_hw_global_setup: MII
> arswitch1: ar9340_hw_global_setup: PHY4 - Local
> arswitch1: attaching PHY 0 failed
> arswitch1: attaching PHY 1 failed
> arswitch1: attaching PHY 2 failed
> arswitch1: attaching PHY 3 failed
> device_attach: arswitch1 attach returned 6
>
> Theres a bigger switch connected to arge0 afaics, arge1 sees no traffic so
> might just be for control...
>
>
> On 18/01/2014 02:12, Adrian Chadd wrote:
>>
>> 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@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@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@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@freebsd.org mailing list
>>> http://lists.freebsd.org/mailman/listinfo/freebsd-mips
>>> To unsubscribe, send any mail to "freebsd-mips-unsubscribe@freebsd.org"
>
>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmokWQJWqQT_-c5buZrVteLwwZfYqYa%2BynxRpRmDovpb7hQ>