Date: Sun, 27 Dec 2015 09:37:13 -0800 From: Adrian Chadd <adrian.chadd@gmail.com> To: Anant Kamath <kamathanant@gmail.com> Cc: "freebsd-mips@freebsd.org" <freebsd-mips@freebsd.org> Subject: Re: [RT5350] Unable to login on an HLK-RM04 Message-ID: <CAJ-VmokOFHaK7EbBwwQHKwop-QJSh%2Be8Bj3qHYs38zVMu2VwUg@mail.gmail.com> In-Reply-To: <CAH0miJCEt%2B%2B0MvOPqkEbKRkGzha9VKeQqwW538jRb7eW1%2BE7Wg@mail.gmail.com> References: <CAH0miJALwjxDGBYn2g6spzmHXAzWSFq-3vVU0%2By8vxu__f-Wkg@mail.gmail.com> <CAH0miJCEt%2B%2B0MvOPqkEbKRkGzha9VKeQqwW538jRb7eW1%2BE7Wg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I'm on that today. please file bugs for both of those (can't login, and incorrect console device.) -a On 27 December 2015 at 04:31, Anant Kamath <kamathanant@gmail.com> wrote: > Changing /etc/ttys to use ttyu1 instead of ttyu0 makes the login prompt > work (it gets displayed). > > However, no username seems to be valid. (I tried root, user) > > Configuring /etc/ttys to autologin like this: > > ttyu1 "/usr/libexec/getty al.57600" vt100 on secure > > also fails. (It results in an infinited failed login loop) > > After fixing the network settings in the image (to use rt0 instead of > arge0, and enabling the if_bridge device in the kernconf), I can now > connect via telnet, but telnet too rejects the credentials (login: user, > blank password; login: root, blank password; login: root, password:root > fails) > > ( New boot message: http://pastebin.com/qYcBR0bq ) > > I think this is now more an issue that I should post here: > https://github.com/freebsd/freebsd-wifi-build > but I welcome any help if I'm missing something really obvious. > > Regards, > Anant > > > > On Sun, Dec 27, 2015 at 3:52 PM Anant Kamath <kamathanant@gmail.com> wrote: > >> Hi, >> >> I was trying to get FreeBSD to work on a HiLink HLK-RM04 which has a >> RT5350 SoC (and 32MB RAM, 8MB Flash) for the past couple of weeks in my >> free time. OpenWRT has so far worked splendidly on this. >> >> I had tried the RT305X kernel (which booted after removing the BOOTP >> options) but couldn't get my mfsroot image to mount. >> >> Then I was genuinely surprised when a new RT5350 conf and other bits got >> added just a couple of days ago (and then I found this mailing list and the >> other threads about it). >> >> So I tried the new kernconf (configured with MFS_IMAGE and >> GEOM_UNCOMPRESS) with a mfsroot image created using Adrian Chadd's >> freebsd-wifi-buiild and tftpbooted it. >> (I also had to do this: >> https://github.com/freebsd/freebsd-wifi-build/issues/9) >> >> The md0.ulzma image gets mounted, however the prompt ends here: >> >> ..... >> ifconfig: interface bridge0 does not exist >> bridge0: done >> *** inetd >> *** Done! >> >> Output on the terminal freezes here. >> (Full boot message here : http://pastebin.com/gkkBsJDn) >> >> Is the init complete at this point? I'm not getting any login prompt after >> this. >> How does one access the console from here (over serial)? >> >> Also, I understand that this rt5350 support is work-in-progress, and would >> love to help with the effort. >> >> Regards, >> Anant Kamath >> > _______________________________________________ > freebsd-mips@freebsd.org mailing list > https://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-VmokOFHaK7EbBwwQHKwop-QJSh%2Be8Bj3qHYs38zVMu2VwUg>