From owner-freebsd-mips@freebsd.org Sun Dec 27 10:41:52 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 51041A521BF for ; Sun, 27 Dec 2015 10:41:52 +0000 (UTC) (envelope-from kamathanant@gmail.com) Received: from mail-io0-x22b.google.com (mail-io0-x22b.google.com [IPv6:2607:f8b0:4001:c06::22b]) (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 218B617EB for ; Sun, 27 Dec 2015 10:41:52 +0000 (UTC) (envelope-from kamathanant@gmail.com) Received: by mail-io0-x22b.google.com with SMTP id q126so285277137iof.2 for ; Sun, 27 Dec 2015 02:41:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=1ax4rOUMaOySHFq5+2ldjpcEtmuaWVgKvIwsJGsbKag=; b=f2mWbwlujKJmC5DYwZfpdlKNtQR3A8P52lLI3f/uJrGLc/RcQmdCtkdGr8oNwEzs0I y6o3OXPcFzKZaDhy9YwDjPBfBYpDYb3FJ2j0y/3+LoVXHyptBpgqZf9sibwvQ/IL5w4b OoGgLG0721i/g+KOThoc2XeZaWC9aWC/HIhKX7SI6dMl9nTvjHUkxnDa5PO+2CLaIzi5 zlrDjr5Yw8bbHWqxY2f3ceGnZYpIMXQ9N9+KaXtXlzyh5V9BB9qQeHJks4D0a2LPHSy2 NkxxpjsDIjT2NvaJ0R7NlNFf/FOe/rPp6BMtDaVsl0ufiVjN8Q2Wzj91R6z+I/YM+0Xu aznQ== X-Received: by 10.107.151.205 with SMTP id z196mr45445598iod.191.1451212911499; Sun, 27 Dec 2015 02:41:51 -0800 (PST) MIME-Version: 1.0 From: Anant Kamath Date: Sun, 27 Dec 2015 10:41:42 +0000 Message-ID: Subject: [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 10:41:52 -0000 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 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 > From owner-freebsd-mips@freebsd.org Sun Dec 27 17:37:14 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 3BA21A53750 for ; Sun, 27 Dec 2015 17:37:14 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-ig0-x22f.google.com (mail-ig0-x22f.google.com [IPv6:2607:f8b0:4001:c05::22f]) (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 0D8F81ACA for ; Sun, 27 Dec 2015 17:37:14 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-ig0-x22f.google.com with SMTP id ph11so134277367igc.1 for ; Sun, 27 Dec 2015 09:37:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=yBMjtM5mc6AzZyKKoZ9MqpMVYN9NyxDEY3VtM4TDk3A=; b=I4HngwkJdqe9mUUDL32Xcek5btmbcF38km1MTu1tEiu+nF2DHEJrfNzwQJ/RDOKAHD 1sL9Ihjw0uisYnghQ26j5eWWi2Xo3DjODcwPhMSKOenAx/C0LjPIM8M1GQTGEWz/vm8d G8v5g5uMvBF1zTAnDIsMiAot12reuIFEGhTxJmgvpmuXSSDWSmVhajfFAeLj55l1z8sb CWs3j9hCvGMV0EuROQyG2nBioNV0V/IcCIfdGslx1P7QU/vTHjWr3q9NmiN//LA3+lPI H8z2njzzYNcPMb2y3l329FpC90t1kVpWoCxwVEJs3wuoyg39bsr1ymk/da8e7YLpwpSV lqQw== MIME-Version: 1.0 X-Received: by 10.50.79.230 with SMTP id m6mr20638573igx.22.1451237833452; Sun, 27 Dec 2015 09:37:13 -0800 (PST) Received: by 10.36.121.202 with HTTP; Sun, 27 Dec 2015 09:37:13 -0800 (PST) In-Reply-To: References: Date: Sun, 27 Dec 2015 09:37:13 -0800 Message-ID: Subject: Re: [RT5350] Unable to login on an HLK-RM04 From: Adrian Chadd To: Anant Kamath Cc: "freebsd-mips@freebsd.org" Content-Type: text/plain; charset=UTF-8 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 17:37:14 -0000 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 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 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" From owner-freebsd-mips@freebsd.org Mon Dec 28 20:11:02 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 CCACAA54970 for ; Mon, 28 Dec 2015 20:11:02 +0000 (UTC) (envelope-from ray@ddteam.net) Received: from mail-lf0-x232.google.com (mail-lf0-x232.google.com [IPv6:2a00:1450:4010:c07::232]) (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 598E31C5C for ; Mon, 28 Dec 2015 20:11:02 +0000 (UTC) (envelope-from ray@ddteam.net) Received: by mail-lf0-x232.google.com with SMTP id y184so202995391lfc.1 for ; Mon, 28 Dec 2015 12:11:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ddteam-net.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; bh=aSuX3GQbargK8rpPGtspkUDqGYYF7VcHDgQ823aFH+4=; b=a5jfaILYdABRMJgzgRtfMliNJZA8CQSHs0/QXX5pXc6A2gN9IBilvXGC+pxUoO4fAw ok8GmSt6uVGfnWSMjrXjzkTO4LMuFKoyMZ+widKMNOx60FgeU+H8BFEUK1Jjc+6FjR2B GfyQAPqOq6tQls3Vlh8Moj6MI2vyKRX/TaA5By2UCiVACIqmwY5E/invZr9Veb4X1qy6 zTDMboJaKpkzLSOM0E7pFXYutAgsgnlu9bC+6zRb8s0Srjon2F4NeQJ+gLaFlVWW7Yaj m8xSwfZlP1UBkmSTt4FOIRGA2n7ua5cOkioGCfSi9gJ4x6LxGuhDJ4HC1kyhEPNfpNPm sjKQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-type:content-transfer-encoding; bh=aSuX3GQbargK8rpPGtspkUDqGYYF7VcHDgQ823aFH+4=; b=B+aCA3NtDWamFBT864qcJLCvpK41GUemxHBpowRllEo/AWOyt0UbVKDldg2GS6x05Y hLKbSRvS8TiyUnIXSkChPnAsA2QIvkm6GGRoeJWV5rqi5uetXp07SP5aCTx7cBojFqwV IcaH9Rq8o5TEf4fwx27Je6wB0vEU4j+Pt0DL6xn/kiw/lorY9sZJFCYHCNE8+0yPCxk4 LkBhtT7rgEqQCrniA3LjQfkzM32O55nnKM/u8SCHITWGp1A7P55rWuMQmJXiplvyDYUI ZeEAB5kSFSI+2gc/Ry8z6Nq+T+2H8dwcP811+SiqnUoaUpReZPrdIdtxkSzxZuB7RDGK Jy0g== X-Gm-Message-State: ALoCoQkmDtNFJzzT3pF/A4CjyLQsYXyM0DCLNS4BMnLHKal44uCZCqauNWI411IBzGB5+zh9yGE4FUskYJYw7lP1RPeSJcdfuQ== X-Received: by 10.25.21.40 with SMTP id l40mr13170692lfi.123.1451333460015; Mon, 28 Dec 2015 12:11:00 -0800 (PST) Received: from raynote.ddteam.net (0-211-52-37.pool.ukrtel.net. [37.52.211.0]) by smtp.gmail.com with ESMTPSA id ji3sm5486423lbc.37.2015.12.28.12.10.58 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 28 Dec 2015 12:10:59 -0800 (PST) Date: Mon, 28 Dec 2015 22:10:28 +0200 From: Aleksandr Rybalko To: Adrian Chadd Cc: Anant Kamath , "freebsd-mips@freebsd.org" Subject: Re: [RT5350] Unable to login on an HLK-RM04 Message-Id: <20151228221028.068b5baa6fb876d20821d338@ddteam.net> In-Reply-To: References: X-Mailer: Sylpheed 3.4.2 (GTK+ 2.24.25; amd64-portbld-freebsd11.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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: Mon, 28 Dec 2015 20:11:02 -0000 On Sun, 27 Dec 2015 09:37:13 -0800 Adrian Chadd wrote: > I'm on that today. > > please file bugs for both of those (can't login, and incorrect console device.) > > > -a I'm not sure how it done in Adrian's build, but I fix that problem few weeks ago for zrouter.org: http://hg.zrouter.org/hg/zrouter/rev/18651f8c0b45 Anant, please take a look, if it helps you too. > > > On 27 December 2015 at 04:31, Anant Kamath 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 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" > _______________________________________________ > 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" -- Aleksandr Rybalko From owner-freebsd-mips@freebsd.org Sat Jan 2 18:34:42 2016 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 D0727A5FB7C for ; Sat, 2 Jan 2016 18:34:42 +0000 (UTC) (envelope-from kamathanant@gmail.com) Received: from mail-io0-x235.google.com (mail-io0-x235.google.com [IPv6:2607:f8b0:4001:c06::235]) (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 9EAF21E19 for ; Sat, 2 Jan 2016 18:34:42 +0000 (UTC) (envelope-from kamathanant@gmail.com) Received: by mail-io0-x235.google.com with SMTP id o67so405897409iof.3 for ; Sat, 02 Jan 2016 10:34:42 -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 :cc:content-type; bh=d0omZG/8KJwH3gN6NneWPojPu5KwUGOcpQGic8WdQXw=; b=CjDGs1TPQgZmTM0pHCdmDOjJeXiYZY4NIII2zhiD5ye2+hAxC2ELxTFuCh2BVcLdiR 2Gvq84D/YLYlQoxDaDNpeZHKii7WrX1SOs4FS0opfjAsMvn7B85L+1Tq7+5m7pcjoSac Vwd6bPbdpe0hp0wxQhQeShSZS1s+wmhaaANvJHVqysLCuF5yWXx7R/2UYMx6Tgd7QTN1 wEAAp6JryvJE5rxhZxxYtKl5vfaiwhqstKw4CGRCTmcJAVVFLTuXBwUdQy5cQIZzMweP qlPVfWnaJXL90/LwFKjvagD9ehIdMRx/Wg4m8hNRKvTYUTWfzP2cG3wWyluEkc50ZUXZ xzzg== X-Received: by 10.107.34.79 with SMTP id i76mr19214983ioi.195.1451759681873; Sat, 02 Jan 2016 10:34:41 -0800 (PST) MIME-Version: 1.0 References: <20151228221028.068b5baa6fb876d20821d338@ddteam.net> In-Reply-To: <20151228221028.068b5baa6fb876d20821d338@ddteam.net> From: Anant Kamath Date: Sat, 02 Jan 2016 18:34:32 +0000 Message-ID: Subject: Re: [RT5350] Unable to login on an HLK-RM04 To: Aleksandr Rybalko , Adrian Chadd Cc: "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: Sat, 02 Jan 2016 18:34:43 -0000 Hi, This is resolved. I managed to login via the serial console and also via telnet. Turns out I was not using the build scripts correctly. Thank you Adrian and Aleksandr for your help. Cheers, Anant On Tue, Dec 29, 2015 at 1:41 AM Aleksandr Rybalko wrote: > On Sun, 27 Dec 2015 09:37:13 -0800 > Adrian Chadd wrote: > > > I'm on that today. > > > > please file bugs for both of those (can't login, and incorrect console > device.) > > > > > > -a > > I'm not sure how it done in Adrian's build, but I fix that problem few > weeks ago for zrouter.org: > http://hg.zrouter.org/hg/zrouter/rev/18651f8c0b45 > > Anant, please take a look, if it helps you too. > > > > > > > On 27 December 2015 at 04:31, Anant Kamath > 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 > 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 > " > > _______________________________________________ > > 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" > > > -- > Aleksandr Rybalko >