From owner-freebsd-mips@freebsd.org Sun Dec 27 12:31:51 2015 Return-Path: Delivered-To: freebsd-mips@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BE28BA52625 for ; Sun, 27 Dec 2015 12:31:51 +0000 (UTC) (envelope-from kamathanant@gmail.com) Received: from mail-ig0-x233.google.com (mail-ig0-x233.google.com [IPv6:2607:f8b0:4001:c05::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 90848195E for ; Sun, 27 Dec 2015 12:31:51 +0000 (UTC) (envelope-from kamathanant@gmail.com) Received: by mail-ig0-x233.google.com with SMTP id mv3so106968320igc.0 for ; Sun, 27 Dec 2015 04:31:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :content-type; bh=gR9s37F+G1BjXZsb1Tm5wWxwo26Td3NM3SNkUcTYde4=; b=KUSFrpfvmcxunKQNHfYruYyBK5sAy8yGTNAxNeneCZlv0z/CikQ40Mr5EQvgadts9o z0LKBZeQ1XqGe68J+g3NIwLrUbHc1IUp7MO7GfwMStbawRgaJekYlYSIJn52aMfgLOPw DZndDOsKFz4BuXJdoDJKcVe+TML7/9BXYMd2d2z+I7TFTy2KlJJ2n4DifPApKI4nksf3 N1M3GeB22idg9L6VueG62zw6gOVAY/2kqG79oJR5cUn+zzJkZS+ySxMTynB0V8Ba4kFP v68ASWB6nytIRBm2mJx6cBEBwFRmZ9WZoXMQP/2aws2xkm8wXQhV9dqLlMnmUnT1DuEy ufdg== X-Received: by 10.50.138.72 with SMTP id qo8mr49640288igb.31.1451219510818; Sun, 27 Dec 2015 04:31:50 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Anant Kamath Date: Sun, 27 Dec 2015 12:31:41 +0000 Message-ID: Subject: Re: [RT5350] Unable to login on an HLK-RM04 To: freebsd-mips@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Dec 2015 12:31:51 -0000 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 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 >