From owner-freebsd-arm@freebsd.org Sun Oct 2 04:10:59 2016 Return-Path: Delivered-To: freebsd-arm@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 E2F8EAC6133 for ; Sun, 2 Oct 2016 04:10:59 +0000 (UTC) (envelope-from russ.haley@gmail.com) Received: from mail-pa0-x22b.google.com (mail-pa0-x22b.google.com [IPv6:2607:f8b0:400e:c03::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 B4BF88A5 for ; Sun, 2 Oct 2016 04:10:59 +0000 (UTC) (envelope-from russ.haley@gmail.com) Received: by mail-pa0-x22b.google.com with SMTP id dw4so36920790pac.1 for ; Sat, 01 Oct 2016 21:10:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:content-transfer-encoding:message-id:date:subject:from :in-reply-to:references:to; bh=fjGPQbIObCvOzbWb0IEspMBV/hlAwgMBvD3y9zLok48=; b=hf5dD9u5wUQYRn+hGj9CrTz6A+OxlgVIzAvzfLggjp+T+J3wzm+wgxYuTrZxCfqQAt Bmlqkfl5/LVV6tXvDhLXhXMaSmXjyrX2yOLJzv48xhtmKYJ2tmUaOTZVUqVN6i5JRtnY nTYRXXpgXzssyy+Y5k36yQlFEz0Q+A1+VeYiYwugICPxOH5MiRzLZlQfsVagOVO2Ao+S frBOW3NfTnHPXHxTKpG+l7tC2ttPR3OlIRD3gPuWnlK3vB8HYYtdrUGKjJ8jFRBkwcpz rHBniSLsQWimr67XWrkciioHDLlHW+M2lL/tDTQwpB+kfOK4yKfxEB+PqFahYvKlA4yC 0VPw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:content-transfer-encoding :message-id:date:subject:from:in-reply-to:references:to; bh=fjGPQbIObCvOzbWb0IEspMBV/hlAwgMBvD3y9zLok48=; b=QEjn881oHUukBpobblqPWdzxt/FmRLrwGDa61y0/laaSzI2/4unMR494cXCRoPXED4 PLuV1vl5AbE2ExuUFhU4fKfIF4dl9fcdldvT0oIUDTSg1Tog/zi4TPDa9zASC5PvP83T 1bW8Ob0y3/ImyCfBeyNcJnlz7QLegGYSoqq5jZUgPWozlTxRs+bG7yY6fx1LG5xqC4h0 6bqLTIA0GiGH40Bd17zccVmaWPt1AQNrki29IkPTLMxK70UWDtFj45gMHjp1WsDVfwe+ B2CVI0y1Jow+fHQ+Nznx5tzcGYvq63qTfoZZuvS7DbPMtv/KWyQsVdwWrSukQYBz9pfl vSgA== X-Gm-Message-State: AA6/9RlOuHq+iCuvBS9OEBqMWU/L0grHKGt3RfmNTlGeiWXgMoDg4K0fjnm1Wsve23DFXg== X-Received: by 10.66.254.170 with SMTP id aj10mr25735490pad.124.1475381459053; Sat, 01 Oct 2016 21:10:59 -0700 (PDT) Received: from [127.0.0.1] ([216.113.200.184]) by smtp.gmail.com with ESMTPSA id d85sm24200682pfj.57.2016.10.01.21.10.57 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Sat, 01 Oct 2016 21:10:58 -0700 (PDT) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable X-Mailer: BlackBerry Email (10.3.2.2876) Message-ID: <20161002041057.5369938.26268.12936@gmail.com> Date: Sat, 01 Oct 2016 21:10:57 -0700 Subject: Re: FreeBSD on Pine64: ubldr for arm64 From: Russell Haley In-Reply-To: <57F0440A.4060709@felix-maurer.de> References: <57F0440A.4060709@felix-maurer.de> To: Felix Maurer , freebsd-arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Oct 2016 04:11:00 -0000 An alternative is to have the kernel in a fat partition and load it directl= y from u-boot. =E2=80=8ENot sure if that works with a pine64 board but it w= orks with other platforms. Not ideal if you want to manage your kernel from= the local system, but it gets you a booting board perhaps? Russ Sent=C2=A0from=C2=A0my=C2=A0BlackBerry=C2=A010=C2=A0smartphone=C2=A0on=C2= =A0the=C2=A0Virgin=C2=A0Mobile=C2=A0network. =C2=A0 Original Message =C2=A0 From: Felix Maurer Sent: Saturday, October 1, 2016 4:18 PM To: freebsd-arm@freebsd.org Subject: FreeBSD on Pine64: ubldr for arm64 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi, I am currently trying to build a FreeBSD image with Crochet to boot on the Pine64. Thanks to the sysutils/u-boot-pine64 port I already got a working SPL that starts U-Boot. The normal way to continue booting a image built by Crochet is to start ubldr. But at the moment there is no arm64 version of ubldr in the tree. The only thing I found about this is this diff: https://reviews.freebsd.org/D5512 . It has been lying around there since March and the last comments state that the changes are unnecessary now for the RPI3 because a way has been found to boot on a RPI3 without U-Boot. Now I have two questions: 1. Is there a chance for the diff to make it into the tree? Although it is no longer needed for the RPI3 it may be needed by other boards. 2. As an alternative: What is this mysterious way to boot without U-Boot and may this be possible for other boards like the Pine64? Regards, Felix -----BEGIN PGP SIGNATURE----- Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCgAGBQJX8EQKAAoJEEy46Yy6oqJ0ZZYQAIdDp6zwuCa7FsP1XGcOomnw qYftBWerVZZYuiXKrwtmAaKDY/OTn4WNwvEMUa5Zp4ny01QUV5DW+TcbDfdfV/9W T+dNOhsbzWbUvaK3U2y8fmrNs8TswtEENpFhlaPWNeloDqocFtvyvTKS7IQQYnMQ UFE+VPvMw9kZORKblNdQb4e4sGgQdq2QtyFaPmtrpzg8ax0NJFciRG7myhrVqQ5R kOClK5loPJSfSebN7YpePablGHjXyS/IKjtvds5VpDMe8jJ8b+dPmHCumeSJ6vor lccX6J+WXlLtdCeIBD8Z1TMT4XKX6Gz60WWMSf6XysNldkxl2y2k9mfSTTxGdygc SSDpRGZh7xqwySZhF6/7L6Wz/uwXp9iI94BgW+uTXlJ0+GARt+xR4ArNL4jYFED2 eLxvTyVVxt8lCVMJZAPdVH87SEB1MNEwzYzu8r7Hmj+5q9rUyv3bJeCnRPdf9XAP DQVRYvimVW7uR21REYlwb+uS/169As0g7LR5kk2zBbaemc8PcL4QAvyTNwpLWYfS qznwqcN1ca1Unoo9vn7zYPmBavKunobrbjl4GjKDh1kuOmWKx4C+LUj7qT8+yAY9 SgD/98Wl8QMTNmCdgICVMYHdyzDVO66WLBI48kbEESi1RT/ESbQAm6bCScl8h+Av /znPEvXG2SCueYu34EPF =3DCGiK -----END PGP SIGNATURE----- _______________________________________________ freebsd-arm@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-arm To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" From owner-freebsd-arm@freebsd.org Sun Oct 2 04:44:42 2016 Return-Path: Delivered-To: freebsd-arm@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 7EC16AC6873 for ; Sun, 2 Oct 2016 04:44:42 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x22c.google.com (mail-io0-x22c.google.com [IPv6:2607:f8b0:4001:c06::22c]) (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 3BB72632 for ; Sun, 2 Oct 2016 04:44:42 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x22c.google.com with SMTP id i202so12821764ioi.2 for ; Sat, 01 Oct 2016 21:44:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=1JZsi2n1Dul85ailQZtL9SeQgUgEjzRJhSzsxd+qfRM=; b=GjzPakYgDKPB+x5V5A+p667t8OiBXa8y8YlmxlF14ScBmjPYiYfUet2W0EkU4QXFZw 2X3kt/X8G0x7MEhh3Y3t9ujZAjY6qM9qEr9LY+xDYgtXIj40nJUF7UApd16/XGhzddbQ z9n9TZNhY1WRuOJr77L9qzvtI7LUi6jt64UgU8KLDWEBHaRBzs4u6GCJgRMCt5nLbja2 khm5s8dWDvDwDjbgh1olPOeJWw5EhsIhYCiDsd9CeStgI1a6hUmqbON8KG8VHbO5Ybjj faVCu4a/NGpfkAMmkWFnt3OYyWgoA9AG6Dbml9+XUdyYHgxlHJR2s5iyS2+7SO9Xi2lh /T7Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=1JZsi2n1Dul85ailQZtL9SeQgUgEjzRJhSzsxd+qfRM=; b=JJEZ6sOrPBA8aaI46GAEFIQZIUmAajPO1cUeUhek3EajFB+DETfRazriwFYBHJhJBN a3PQc5BA6+ZKz1Etc45TSHKjAfHW0EyM1XyTX1YlbgSGO0iWc3GA1iuG3Yg7XthvX68r MUOXipEtnb++yYWlYUGzEufyckxoZxYki1O2E6kihhtzGaGH8RfNzsDCgV2fvFNhdqk8 M1evS8A1l3OwEnzyD9M9Vso5oCGAmJiSVROZ6nJuY3lSQVQ212agAkykY3Bggal4/No2 p4QAVazJOar/3jL2VYgHjmYcoAl5BmDDsWZJiPidovNUk7sqUH0syiz6a5s/VIVHN1P2 lSgg== X-Gm-Message-State: AA6/9Rmy1S5sZAI0bGvr17HVPOVbvSFyFaAkMy1DbkdMPw7VwC2IOR/TGA0aljyRLPtm/0ECqaA40eMLOMwrQw== X-Received: by 10.107.135.202 with SMTP id r71mr3466279ioi.224.1475383481410; Sat, 01 Oct 2016 21:44:41 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.36.65.7 with HTTP; Sat, 1 Oct 2016 21:44:40 -0700 (PDT) X-Originating-IP: [50.253.99.174] In-Reply-To: <57F0440A.4060709@felix-maurer.de> References: <57F0440A.4060709@felix-maurer.de> From: Warner Losh Date: Sat, 1 Oct 2016 22:44:40 -0600 X-Google-Sender-Auth: vW-aEvJJ6pMimBx3ThMCwoEPGVM Message-ID: Subject: Re: FreeBSD on Pine64: ubldr for arm64 To: Felix Maurer Cc: "freebsd-arm@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Oct 2016 04:44:42 -0000 On Sat, Oct 1, 2016 at 5:17 PM, Felix Maurer wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > Hi, > > I am currently trying to build a FreeBSD image with Crochet to boot on > the Pine64. > > Thanks to the sysutils/u-boot-pine64 port I already got a working SPL > that starts U-Boot. The normal way to continue booting a image built by > Crochet is to start ubldr. But at the moment there is no arm64 version > of ubldr in the tree. > The only thing I found about this is this diff: > https://reviews.freebsd.org/D5512 . It has been lying around there since > March and the last comments state that the changes are unnecessary now > for the RPI3 because a way has been found to boot on a RPI3 without > U-Boot. Now I have two questions: > > 1. Is there a chance for the diff to make it into the tree? Although it > is no longer needed for the RPI3 it may be needed by other boards. > 2. As an alternative: What is this mysterious way to boot without U-Boot > and may this be possible for other boards like the Pine64? Both pine and rpi-3 use uboot to boot, but they use it to boot the UEFI implementation. There's a freebsd port for u-boot on pine64. There's also a github project to add support for pine64 to crochet, but I don't have the pointer... Warner > Regards, > Felix > -----BEGIN PGP SIGNATURE----- > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iQIcBAEBCgAGBQJX8EQKAAoJEEy46Yy6oqJ0ZZYQAIdDp6zwuCa7FsP1XGcOomnw > qYftBWerVZZYuiXKrwtmAaKDY/OTn4WNwvEMUa5Zp4ny01QUV5DW+TcbDfdfV/9W > T+dNOhsbzWbUvaK3U2y8fmrNs8TswtEENpFhlaPWNeloDqocFtvyvTKS7IQQYnMQ > UFE+VPvMw9kZORKblNdQb4e4sGgQdq2QtyFaPmtrpzg8ax0NJFciRG7myhrVqQ5R > kOClK5loPJSfSebN7YpePablGHjXyS/IKjtvds5VpDMe8jJ8b+dPmHCumeSJ6vor > lccX6J+WXlLtdCeIBD8Z1TMT4XKX6Gz60WWMSf6XysNldkxl2y2k9mfSTTxGdygc > SSDpRGZh7xqwySZhF6/7L6Wz/uwXp9iI94BgW+uTXlJ0+GARt+xR4ArNL4jYFED2 > eLxvTyVVxt8lCVMJZAPdVH87SEB1MNEwzYzu8r7Hmj+5q9rUyv3bJeCnRPdf9XAP > DQVRYvimVW7uR21REYlwb+uS/169As0g7LR5kk2zBbaemc8PcL4QAvyTNwpLWYfS > qznwqcN1ca1Unoo9vn7zYPmBavKunobrbjl4GjKDh1kuOmWKx4C+LUj7qT8+yAY9 > SgD/98Wl8QMTNmCdgICVMYHdyzDVO66WLBI48kbEESi1RT/ESbQAm6bCScl8h+Av > /znPEvXG2SCueYu34EPF > =CGiK > -----END PGP SIGNATURE----- > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" From owner-freebsd-arm@freebsd.org Sun Oct 2 07:19:59 2016 Return-Path: Delivered-To: freebsd-arm@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 C20E7AC6A1F for ; Sun, 2 Oct 2016 07:19:59 +0000 (UTC) (envelope-from tvijlbrief@gmail.com) Received: from mail-wm0-x231.google.com (mail-wm0-x231.google.com [IPv6:2a00:1450:400c:c09::231]) (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 544471DD3 for ; Sun, 2 Oct 2016 07:19:59 +0000 (UTC) (envelope-from tvijlbrief@gmail.com) Received: by mail-wm0-x231.google.com with SMTP id k125so95793926wma.1 for ; Sun, 02 Oct 2016 00:19:59 -0700 (PDT) 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; bh=bNjynmLT4pl1t3ZWZgFcNksRaqGHUi8rSUHqrJ6x7Hs=; b=czplxfxpxP5J+k5vNrfypRXIxdqjwTh496szq68WaF1Ljk0/pJe1vgsLIzJdcQ9RGY WwrLYCHLQaKXXoVe7p8ebswV3TdwvGP1R5CCWa9IzJttBZKJI2mXuilqKG102xONfOzF s3dFwCJEcqt2+RHvdTZWDJ20jS9H2G0RcjXYAKIoSNJzT40bhm/tysrHI7pgQEjkpxw0 4CYDTOLqbdtYGBkTQEGmBOAOJutnuZMghE1lVK9/BpPyi6X/2k5QGdOVYHOOuKlR4hT1 w5gZHQ40VAZqNE+Wwe2ZeTHaq0Ii3x+FH/JtaDqoCP+kHXUoXhZlFgXGIaj4CqjR0G2W KFww== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=bNjynmLT4pl1t3ZWZgFcNksRaqGHUi8rSUHqrJ6x7Hs=; b=IWSOlMdxknTO0ti/dcq/fkodrrsE9vXwvRb2EOw6IuaQqGne2a6C29pQHSnh6HI4va cYqKZHvEd0L8lS9CUwgoX0ToQ8jxs8yISMib0yn9M7jMASUtofdEQCG0Cn0FF3kqpkR0 bdl97dg10eEr6IvKnLq+aMAxKdp/OFjyP//p8hVhBttl8Fh91eXdXe6VLbxrEij3lD/d K6MoRV5U6fh615HPojb3Y6gF+a1f6VEU+EWHAFgXAW2Asj4/w8aOQnUgroaFfN2J2Kuv gDOTXeAb9jLwnbf09S6MBtzv/ooM0il77yAt/xH+VFBUe4e4PeepI84WIlOeLk8wEW7u kePw== X-Gm-Message-State: AA6/9Rlb8xk0VfDqawJebzSPKTtYIZlzlMqI7n7G5VsAKT/5newpVzOiNI/N32Zf0igKgTrBQB71ophJd+KVGQ== X-Received: by 10.194.238.170 with SMTP id vl10mr12192820wjc.18.1475392796584; Sun, 02 Oct 2016 00:19:56 -0700 (PDT) MIME-Version: 1.0 References: <57F0440A.4060709@felix-maurer.de> In-Reply-To: <57F0440A.4060709@felix-maurer.de> From: Tom Vijlbrief Date: Sun, 02 Oct 2016 07:19:45 +0000 Message-ID: Subject: Re: FreeBSD on Pine64: ubldr for arm64 To: Felix Maurer , freebsd-arm@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Oct 2016 07:19:59 -0000 I have a script which creates a bootable image: https://github.com/tomtor/image-freebsd-pine64 You can use the boot version from the Ubuntu image and change uEnv.txt and create an additional partition which holds the kernel image. So you skip ubldr. Note that the kernel boots, but I got none of the hardware devices working (I spend more time on the Odroid-C2) and haven't been working on it the last months... Op zo 2 okt. 2016 om 01:18 schreef Felix Maurer : > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > Hi, > > I am currently trying to build a FreeBSD image with Crochet to boot on > the Pine64. > > Thanks to the sysutils/u-boot-pine64 port I already got a working SPL > that starts U-Boot. The normal way to continue booting a image built by > Crochet is to start ubldr. But at the moment there is no arm64 version > of ubldr in the tree. > The only thing I found about this is this diff: > https://reviews.freebsd.org/D5512 . It has been lying around there since > March and the last comments state that the changes are unnecessary now > for the RPI3 because a way has been found to boot on a RPI3 without > U-Boot. Now I have two questions: > > 1. Is there a chance for the diff to make it into the tree? Although it > is no longer needed for the RPI3 it may be needed by other boards. > 2. As an alternative: What is this mysterious way to boot without U-Boot > and may this be possible for other boards like the Pine64? > > Regards, > Felix > -----BEGIN PGP SIGNATURE----- > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iQIcBAEBCgAGBQJX8EQKAAoJEEy46Yy6oqJ0ZZYQAIdDp6zwuCa7FsP1XGcOomnw > qYftBWerVZZYuiXKrwtmAaKDY/OTn4WNwvEMUa5Zp4ny01QUV5DW+TcbDfdfV/9W > T+dNOhsbzWbUvaK3U2y8fmrNs8TswtEENpFhlaPWNeloDqocFtvyvTKS7IQQYnMQ > UFE+VPvMw9kZORKblNdQb4e4sGgQdq2QtyFaPmtrpzg8ax0NJFciRG7myhrVqQ5R > kOClK5loPJSfSebN7YpePablGHjXyS/IKjtvds5VpDMe8jJ8b+dPmHCumeSJ6vor > lccX6J+WXlLtdCeIBD8Z1TMT4XKX6Gz60WWMSf6XysNldkxl2y2k9mfSTTxGdygc > SSDpRGZh7xqwySZhF6/7L6Wz/uwXp9iI94BgW+uTXlJ0+GARt+xR4ArNL4jYFED2 > eLxvTyVVxt8lCVMJZAPdVH87SEB1MNEwzYzu8r7Hmj+5q9rUyv3bJeCnRPdf9XAP > DQVRYvimVW7uR21REYlwb+uS/169As0g7LR5kk2zBbaemc8PcL4QAvyTNwpLWYfS > qznwqcN1ca1Unoo9vn7zYPmBavKunobrbjl4GjKDh1kuOmWKx4C+LUj7qT8+yAY9 > SgD/98Wl8QMTNmCdgICVMYHdyzDVO66WLBI48kbEESi1RT/ESbQAm6bCScl8h+Av > /znPEvXG2SCueYu34EPF > =CGiK > -----END PGP SIGNATURE----- > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" > From owner-freebsd-arm@freebsd.org Sun Oct 2 08:47:41 2016 Return-Path: Delivered-To: freebsd-arm@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 A4FECAC6FFA for ; Sun, 2 Oct 2016 08:47:41 +0000 (UTC) (envelope-from mikael.urankar@gmail.com) Received: from mail-vk0-x230.google.com (mail-vk0-x230.google.com [IPv6:2607:f8b0:400c:c05::230]) (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 510BDFC7 for ; Sun, 2 Oct 2016 08:47:41 +0000 (UTC) (envelope-from mikael.urankar@gmail.com) Received: by mail-vk0-x230.google.com with SMTP id b186so2031248vkb.1 for ; Sun, 02 Oct 2016 01:47:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=kmFdw9q21XpcxpPYok6k1Qq6VVp09jcxWsZmsZT0IOg=; b=fvcGNNCdorneebSeIEhMH1cKQUJru9+FwWHCrubdS6g94l0L5JJwoMjISK95nMCLzw YiwoyIXCmeqARL1f+OvFSjfTMkcY/iSt8u7LA1px7fi40ajJeH28i1iwgquoA1aLILE4 1tawT+1xlk1rELz3TxRGBSd6mZBD9ZcU0/I7FTXy18V7p5VNfc3s7aqMlYdz1jgAFAO2 xNj5vIr0oCGZhaN2CpSimponbzDzfVpPcDJF+MsTNHV+7Qg1O+0qXpEzRCMc/O4K7jxE scGmAtBYkj9+VScQnVsRAHRIpw6CKpVODOMcPb+v0jQf6hU2TgNzKXGtREC7WBXpQXoa lvOA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=kmFdw9q21XpcxpPYok6k1Qq6VVp09jcxWsZmsZT0IOg=; b=a8WGKSpss9f2gC1V+acu29xNh2x2qjMwDdD6ud2L95vOvFnyEWxwL7rtkhrSB4gLEK gnA1X4kcTAG2bDbU3JT1fgnzpHYtRGToD6qplSW6fdL2LsUOaXZRSp2JdjYONOvLcXYT DrvNXHqANLyRL/7teoIIjOjXgfCkP6KmbVB6HzJAZm2zz8ZXIehju9Dr+P9oa+nYPI6Q JXpfhxEOADx/8zNMOa3RvE6vqAjejff/bT6Li/zLozcZPvT5qW8Dma+UWrpz6H+ZrC/6 y0AXYwaERMEpfjG35MKmF2HcTg89/luwbQhaKWmWYeNrwzwIeKJiZ2pcZppLftXQQofN CYmw== X-Gm-Message-State: AA6/9RkqemEF8SHstgGUmt1wwHQjycE3qw3EM+2OsFyiszsRIfhoiMnxhxF+vvlzx/Qz7XBr5aEdpI4VmTDGJw== X-Received: by 10.31.234.194 with SMTP id i185mr3133615vkh.127.1475398060419; Sun, 02 Oct 2016 01:47:40 -0700 (PDT) MIME-Version: 1.0 Received: by 10.103.50.197 with HTTP; Sun, 2 Oct 2016 01:46:59 -0700 (PDT) In-Reply-To: References: <57F0440A.4060709@felix-maurer.de> From: =?UTF-8?Q?Mika=C3=ABl_Urankar?= Date: Sun, 2 Oct 2016 10:46:59 +0200 Message-ID: Subject: Re: FreeBSD on Pine64: ubldr for arm64 To: Warner Losh Cc: Felix Maurer , "freebsd-arm@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Oct 2016 08:47:41 -0000 2016-10-02 6:44 GMT+02:00 Warner Losh : > On Sat, Oct 1, 2016 at 5:17 PM, Felix Maurer wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA512 >> >> Hi, >> >> I am currently trying to build a FreeBSD image with Crochet to boot on >> the Pine64. >> >> Thanks to the sysutils/u-boot-pine64 port I already got a working SPL >> that starts U-Boot. The normal way to continue booting a image built by >> Crochet is to start ubldr. But at the moment there is no arm64 version >> of ubldr in the tree. >> The only thing I found about this is this diff: >> https://reviews.freebsd.org/D5512 . It has been lying around there since >> March and the last comments state that the changes are unnecessary now >> for the RPI3 because a way has been found to boot on a RPI3 without >> U-Boot. Now I have two questions: >> >> 1. Is there a chance for the diff to make it into the tree? Although it >> is no longer needed for the RPI3 it may be needed by other boards. >> 2. As an alternative: What is this mysterious way to boot without U-Boot >> and may this be possible for other boards like the Pine64? > > Both pine and rpi-3 use uboot to boot, but they use it to boot the > UEFI implementation. There's a freebsd port for u-boot on pine64. > There's also a github project to add support for pine64 to crochet, > but I don't have the pointer... here it is: https://github.com/wca/crochet/tree/add-pine64-support From owner-freebsd-arm@freebsd.org Sun Oct 2 10:07:06 2016 Return-Path: Delivered-To: freebsd-arm@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 C8849AD96F1 for ; Sun, 2 Oct 2016 10:07:06 +0000 (UTC) (envelope-from freebsd-arm@herveybayaustralia.com.au) Received: from mail.unitedinsong.com.au (mail.unitedinsong.com.au [150.101.178.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 89A6B35C for ; Sun, 2 Oct 2016 10:07:05 +0000 (UTC) (envelope-from freebsd-arm@herveybayaustralia.com.au) Received: from [192.168.0.177] (laptop3.herveybayaustralia.com.au [192.168.0.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.unitedinsong.com.au (Postfix) with ESMTPSA id 4F5CD62088 for ; Sun, 2 Oct 2016 19:56:57 +1000 (EST) To: freebsd-arm@FreeBSD.org From: Da Rock Subject: u-boot efi option Message-ID: <36160c78-9095-f716-8041-3eb7656642af@herveybayaustralia.com.au> Date: Sun, 2 Oct 2016 19:56:54 +1000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Oct 2016 10:07:06 -0000 Has anyone tried this option yet? I've heard someone got it going for slack, but I thought it sounded like it might make it easier for running freebsd. I'm currently trying to build a more current u-boot to test it. From owner-freebsd-arm@freebsd.org Sun Oct 2 10:37:14 2016 Return-Path: Delivered-To: freebsd-arm@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 1B15BAD9BB2 for ; Sun, 2 Oct 2016 10:37:14 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.blih.net", Issuer "mail.blih.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 6713EEEA for ; Sun, 2 Oct 2016 10:37:12 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) by mail.blih.net (OpenSMTPD) with ESMTP id 3251ff1f; Sun, 2 Oct 2016 12:37:04 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; s=mail; bh=HFaNhtheKpcXbA2e/oVEhDfSL9s=; b=rlk+dJe5lYx1nEvIcjOAwdb/8oNE XhjsQtZVBSZnVKp0Iy+JXAH7rplyBr5EyhNcfCfdQQ/oBhKAhEFrUiNN0NC0I9m+ hCw+7cFIGjJOjLs/mB6etB1slQPVO9GCZlaPgnzfI6t0pQqKt+eXxLpHPJAMam9y ebvHFCUu7sTEJPo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; q=dns; s= mail; b=lOiuaLt8WamH8zPl7kV/mxhCx6ssaknKcVdWt2eJ7iG+5qjIQKo8c+99 5/IVil2sXD/UXu3VjdbTM5YLqM5EgJ2XSDlvyWu+gDlhNAP6CvY3lE2nu9TmrSlj TnM2aaibu3IN/MEmlEOudN5zx81xHUpoVrp2oDjN5bvNroE/Ito= Received: from knuckles.blih.net (ip-54.net-82-216-203.roubaix.rev.numericable.fr [82.216.203.54]) by mail.blih.net (OpenSMTPD) with ESMTPSA id 27225dfc TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Sun, 2 Oct 2016 12:37:04 +0200 (CEST) Date: Sun, 2 Oct 2016 12:37:00 +0200 From: Emmanuel Vadot To: Da Rock Cc: freebsd-arm@FreeBSD.org Subject: Re: u-boot efi option Message-Id: <20161002123700.662f2868688b4b32465395aa@bidouilliste.com> In-Reply-To: <36160c78-9095-f716-8041-3eb7656642af@herveybayaustralia.com.au> References: <36160c78-9095-f716-8041-3eb7656642af@herveybayaustralia.com.au> X-Mailer: Sylpheed 3.5.1 (GTK+ 2.24.29; amd64-portbld-freebsd12.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Oct 2016 10:37:14 -0000 Hello, I've commited every needed change on our side, for uboot side you will need this patch : https://people.freebsd.org/~manu/u-boot_201609_efi.diff The only drawback is that you will need to have your partition aligned on 512kb boundaries on the mmc. I've successfully booted my beaglebone black and most of my Allwinner boards with UEFI. Some part of the uboot patch have started to be upstreamed, for the others I need to rework on some part before I upstream them. Cheers, On Sun, 2 Oct 2016 19:56:54 +1000 Da Rock wrote: > Has anyone tried this option yet? I've heard someone got it going for > slack, but I thought it sounded like it might make it easier for running > freebsd. > > I'm currently trying to build a more current u-boot to test it. > > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" -- Emmanuel Vadot From owner-freebsd-arm@freebsd.org Sun Oct 2 13:04:44 2016 Return-Path: Delivered-To: freebsd-arm@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 A8D27AD9AB2 for ; Sun, 2 Oct 2016 13:04:44 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-59.reflexion.net [208.70.210.59]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 40771A44 for ; Sun, 2 Oct 2016 13:04:43 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 29317 invoked from network); 2 Oct 2016 13:05:29 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 2 Oct 2016 13:05:29 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v8.00.0) with SMTP; Sun, 02 Oct 2016 09:04:42 -0400 (EDT) Received: (qmail 2102 invoked from network); 2 Oct 2016 13:04:42 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 2 Oct 2016 13:04:42 -0000 Received: from [192.168.0.105] (ip70-189-131-151.lv.lv.cox.net [70.189.131.151]) by iron2.pdx.net (Postfix) with ESMTPSA id ACB70EC8BC9; Sun, 2 Oct 2016 06:04:35 -0700 (PDT) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: FreeBSD status for/on ODroid-C2? Date: Sun, 2 Oct 2016 06:04:34 -0700 Message-Id: <61985953-493F-432C-888E-3F4A06BBCA38@dsl-only.net> Cc: freebsd-arm To: Tom Vijlbrief Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Oct 2016 13:04:44 -0000 [Context switching to ODroid-C2 from Pine64. . .] On 2016-Oct-2, at 12:19 AM, Tom Vijlbrief = wrote: > I have a script which creates a bootable image: >=20 > https://github.com/tomtor/image-freebsd-pine64 >=20 > You can use the boot version from the Ubuntu image and change uEnv.txt = and > create an additional partition which holds the kernel image. So you = skip > ubldr. >=20 > Note that the kernel boots, but I got none of the hardware devices = working > (I spend more time on the Odroid-C2) and haven't been working on it = the > last months... Anything worth reporting on the ODroid-C2 details for FreeBSD: what = works, what does not, what needs to be done to boot FreeBSD, and so on? = (I assume head [CURRENT-12 these days].) Looking around. . . https://github.com/tomtor/image-freebsd-c2 seems to have last been updated on May 7 (vs. = https://github.com/tomtor/image-freebsd-pine64 's April 17). https://github.com/tomtor/freebsd/tree/tc2 seems to have last been updated on June 17. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-arm@freebsd.org Sun Oct 2 14:17:36 2016 Return-Path: Delivered-To: freebsd-arm@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 77C1BAEF017 for ; Sun, 2 Oct 2016 14:17:36 +0000 (UTC) (envelope-from tvijlbrief@gmail.com) Received: from mail-wm0-x22f.google.com (mail-wm0-x22f.google.com [IPv6:2a00:1450:400c:c09::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 0ECF7D41 for ; Sun, 2 Oct 2016 14:17:36 +0000 (UTC) (envelope-from tvijlbrief@gmail.com) Received: by mail-wm0-x22f.google.com with SMTP id f193so64337190wmg.0 for ; Sun, 02 Oct 2016 07:17:35 -0700 (PDT) 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; bh=9zwI8k4ZDL5ilXLUf+jLd1Id96cPjqSadzPRFuk3FIY=; b=lIhX6DZVra1n596k97nhjH+8LUJNX8gwycBlhsN4n5w9I5x6aG9vaMkW0UnijP7kpi UpLI/YlS180z8HSGBGtsjZxp30clgXYV7FhTqee4lfnEAA6yYcejDF1+0o4/kGsKd85K Bi1ze6RD/zZImDs2e8rLzPqTLWsK2V6/KHrZdaMaAPWNK+U+CckJ96VhHnzAjp748Pur Ai/4M7CmdCoDHxTyxCDS9QKX02FhZc88IF0vVvQVbcEMrWYJ9VKHLIlMqYl+x8t2ZCy8 kHnduVMP2encdTA+pbZv5qxZidW6nQBjokuPf0hUPLW6igkO8fnaHtQyzgV4JBk9WqKh nkGA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=9zwI8k4ZDL5ilXLUf+jLd1Id96cPjqSadzPRFuk3FIY=; b=MeNc5NdqjjzDpfSYJQJo8l1cumSrGmh8IKq8a+q4uof62c6uvnW1ZqmNKc7/Fhaol/ iqEkfxV5G6AQO4DWtExQjuFWLaa8TC/dKA1J8WfMJH9dh6CDbu0FTULmcJ9EYL/d/RQk w1dGMQ4tJFMnYhwaKDvmoh/VcL6xajFdfNTLL42qcwWFASKL9qhsv/kafPszUCmxkABw pzeslO2Jfvg6/limciDiXlPOq2UP3BvB+wtJddyIs5yPJflVlGDmGJLG1dLEIjiC53wi yLEoySLSmMN2UovSt/hXGphQ1dBDPbz2BYETHShqyeRrvnWyQSb9UTLSzlscKtetDPKh qZAg== X-Gm-Message-State: AA6/9RkQc/ITVOHZwulZEfadATpxVdn8jgJC0HDDewabm1w6hJTsNH6w0DghOBsBPcc5K2kD2ksUF6I9zyHnKw== X-Received: by 10.194.18.137 with SMTP id w9mr2027708wjd.198.1475417853497; Sun, 02 Oct 2016 07:17:33 -0700 (PDT) MIME-Version: 1.0 References: <61985953-493F-432C-888E-3F4A06BBCA38@dsl-only.net> In-Reply-To: <61985953-493F-432C-888E-3F4A06BBCA38@dsl-only.net> From: Tom Vijlbrief Date: Sun, 02 Oct 2016 14:17:22 +0000 Message-ID: Subject: Re: FreeBSD status for/on ODroid-C2? To: Mark Millard Cc: freebsd-arm Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Oct 2016 14:17:36 -0000 No change (at least in my tree) since my last report on this list somewhere in May or June. The kernel boots with 4 cpus and working usb. I use an usb ethernet device and usb disk with the root filesysteem. Compiling and running ports works, but a build world fails randomly with a memory access error eg after running 15 minutes. I don't think it makes sense to work on this until a freebsd rpi3 arm64 port is officially supported... Op zo 2 okt. 2016 15:04 schreef Mark Millard : > [Context switching to ODroid-C2 from Pine64. . .] > > On 2016-Oct-2, at 12:19 AM, Tom Vijlbrief wrote: > > > I have a script which creates a bootable image: > > > > https://github.com/tomtor/image-freebsd-pine64 > > > > You can use the boot version from the Ubuntu image and change uEnv.txt > and > > create an additional partition which holds the kernel image. So you skip > > ubldr. > > > > Note that the kernel boots, but I got none of the hardware devices > working > > (I spend more time on the Odroid-C2) and haven't been working on it the > > last months... > > Anything worth reporting on the ODroid-C2 details for FreeBSD: what works, > what does not, what needs to be done to boot FreeBSD, and so on? (I assume > head [CURRENT-12 these days].) > > > Looking around. . . > > > https://github.com/tomtor/image-freebsd-c2 > > seems to have last been updated on May 7 (vs. > https://github.com/tomtor/image-freebsd-pine64 's April 17). > > > https://github.com/tomtor/freebsd/tree/tc2 > > seems to have last been updated on June 17. > > === > Mark Millard > markmi at dsl-only.net > > From owner-freebsd-arm@freebsd.org Sun Oct 2 15:16:03 2016 Return-Path: Delivered-To: freebsd-arm@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 3EE91AEF27F for ; Sun, 2 Oct 2016 15:16:03 +0000 (UTC) (envelope-from lists@felix-maurer.de) Received: from mail.felix-maurer.de (felix-maurer.de [IPv6:2a02:c200:1:10:3:0:7193:1]) by mx1.freebsd.org (Postfix) with ESMTP id 08F4F32D for ; Sun, 2 Oct 2016 15:16:03 +0000 (UTC) (envelope-from lists@felix-maurer.de) Received: from Felix-MBP.fritz.box (p2003008B2F5CE700D94B6D71FB913B91.dip0.t-ipconnect.de [IPv6:2003:8b:2f5c:e700:d94b:6d71:fb91:3b91]) by mail.felix-maurer.de (Postfix) with ESMTPSA id DBDBD1B8478F; Sun, 2 Oct 2016 17:15:06 +0200 (CEST) Message-ID: <57F124B0.9010902@felix-maurer.de> Date: Sun, 02 Oct 2016 17:16:00 +0200 From: Felix Maurer User-Agent: Postbox 5.0.3 (Macintosh/20160930) MIME-Version: 1.0 To: =?UTF-8?B?TWlrYcOrbCBVcmFua2Fy?= CC: Warner Losh , "freebsd-arm@freebsd.org" Subject: Re: FreeBSD on Pine64: ubldr for arm64 References: <57F0440A.4060709@felix-maurer.de> In-Reply-To: X-Enigmail-Version: 1.2.3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Oct 2016 15:16:03 -0000 Thank you for the link. This looks promising to me. I'll give it a try soon. Mikaël Urankar schrieb: > 2016-10-02 6:44 GMT+02:00 Warner Losh : >> On Sat, Oct 1, 2016 at 5:17 PM, Felix Maurer wrote: >>> Hi, >>> >>> I am currently trying to build a FreeBSD image with Crochet to boot on >>> the Pine64. >>> >>> Thanks to the sysutils/u-boot-pine64 port I already got a working SPL >>> that starts U-Boot. The normal way to continue booting a image built by >>> Crochet is to start ubldr. But at the moment there is no arm64 version >>> of ubldr in the tree. >>> The only thing I found about this is this diff: >>> https://reviews.freebsd.org/D5512 . It has been lying around there since >>> March and the last comments state that the changes are unnecessary now >>> for the RPI3 because a way has been found to boot on a RPI3 without >>> U-Boot. Now I have two questions: >>> >>> 1. Is there a chance for the diff to make it into the tree? Although it >>> is no longer needed for the RPI3 it may be needed by other boards. >>> 2. As an alternative: What is this mysterious way to boot without U-Boot >>> and may this be possible for other boards like the Pine64? >> Both pine and rpi-3 use uboot to boot, but they use it to boot the >> UEFI implementation. There's a freebsd port for u-boot on pine64. >> There's also a github project to add support for pine64 to crochet, >> but I don't have the pointer... > > here it is: > https://github.com/wca/crochet/tree/add-pine64-support From owner-freebsd-arm@freebsd.org Sun Oct 2 15:20:43 2016 Return-Path: Delivered-To: freebsd-arm@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 DC426AEF458 for ; Sun, 2 Oct 2016 15:20:43 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-61.reflexion.net [208.70.210.61]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8BC1B8E8 for ; Sun, 2 Oct 2016 15:20:42 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 21778 invoked from network); 2 Oct 2016 15:20:36 -0000 Received: from unknown (HELO mail-cs-02.app.dca.reflexion.local) (10.81.19.2) by 0 (rfx-qmail) with SMTP; 2 Oct 2016 15:20:36 -0000 Received: by mail-cs-02.app.dca.reflexion.local (Reflexion email security v8.00.0) with SMTP; Sun, 02 Oct 2016 11:20:36 -0400 (EDT) Received: (qmail 16295 invoked from network); 2 Oct 2016 15:20:36 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 2 Oct 2016 15:20:36 -0000 Received: from [192.168.0.105] (ip70-189-131-151.lv.lv.cox.net [70.189.131.151]) by iron2.pdx.net (Postfix) with ESMTPSA id 24571EC8BF3; Sun, 2 Oct 2016 08:20:35 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: FreeBSD status for/on ODroid-C2? From: Mark Millard In-Reply-To: Date: Sun, 2 Oct 2016 08:20:34 -0700 Cc: freebsd-arm Content-Transfer-Encoding: quoted-printable Message-Id: <15615670-92D1-4FA9-9E2D-C957119F348D@dsl-only.net> References: <61985953-493F-432C-888E-3F4A06BBCA38@dsl-only.net> To: Tom Vijlbrief X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Oct 2016 15:20:43 -0000 Thanks for the notes. On 2016-Oct-2, at 7:17 AM, Tom Vijlbrief = wrote: >=20 > No change (at least in my tree) since my last report on this list = somewhere in May or June. >=20 > The kernel boots with 4 cpus and working usb. I use an usb ethernet = device and usb disk with the root filesysteem. Compiling and running = ports works, but a build world fails randomly with a memory access error = eg after running 15 minutes. Sounds possibly similar to TARGET_ARCH=3Dpowerpc 's stack-handling SVR4 = ABI violation when world is built by clang 3.8.0 (bad clang code = generation). To get to the point of buildworld going through I had to = change the kernel to provide a so-called "red-zone" on the stack during = signal handling to protect the stack from being trashed. buildworld gets = extensive signals (SIGCHLD) and so without the "red-zone" it would = eventually get trashed addresses, far before getting near completion. [Context: buildkernel via gcc 4.2.1 but buildworld via clang 3.8.0 .] [Side note: I've tried aarch64 releng/11.0 (first RELEASE's raw) under = qemu on Ubuntu 16.04.1 on the ODroid-C2 but it gots periodic illegal = instructions in very basic operation, no builds active.] > I don't think it makes sense to work on this until a freebsd rpi3 = arm64 port is officially supported... [FYI: http://ameridroid.com/products/raspberry-pi-2-model-b-1gb-ram = lists the RPi2B as both "out of stock" and "discontinued" and has for = some time.] > Op zo 2 okt. 2016 15:04 schreef Mark Millard : > . . . > Anything worth reporting on the ODroid-C2 details for FreeBSD: what = works, what does not, what needs to be done to boot FreeBSD, and so on? = (I assume head [CURRENT-12 these days].) >=20 >=20 > Looking around. . . >=20 >=20 > https://github.com/tomtor/image-freebsd-c2 >=20 > seems to have last been updated on May 7 (vs. = https://github.com/tomtor/image-freebsd-pine64 's April 17). >=20 >=20 > https://github.com/tomtor/freebsd/tree/tc2 >=20 > seems to have last been updated on June 17. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-arm@freebsd.org Sun Oct 2 15:35:16 2016 Return-Path: Delivered-To: freebsd-arm@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 05A79AEF9C2 for ; Sun, 2 Oct 2016 15:35:16 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-68.reflexion.net [208.70.210.68]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A8998F85 for ; Sun, 2 Oct 2016 15:35:15 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 4235 invoked from network); 2 Oct 2016 15:35:56 -0000 Received: from unknown (HELO mail-cs-02.app.dca.reflexion.local) (10.81.19.2) by 0 (rfx-qmail) with SMTP; 2 Oct 2016 15:35:56 -0000 Received: by mail-cs-02.app.dca.reflexion.local (Reflexion email security v8.00.0) with SMTP; Sun, 02 Oct 2016 11:35:09 -0400 (EDT) Received: (qmail 9878 invoked from network); 2 Oct 2016 15:35:08 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 2 Oct 2016 15:35:08 -0000 Received: from [192.168.0.105] (ip70-189-131-151.lv.lv.cox.net [70.189.131.151]) by iron2.pdx.net (Postfix) with ESMTPSA id 4E5E0EC8BF3; Sun, 2 Oct 2016 08:35:07 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: FreeBSD status for/on ODroid-C2? From: Mark Millard In-Reply-To: <15615670-92D1-4FA9-9E2D-C957119F348D@dsl-only.net> Date: Sun, 2 Oct 2016 08:35:06 -0700 Cc: freebsd-arm Content-Transfer-Encoding: quoted-printable Message-Id: <3B20ED5E-BF22-428F-99E8-08CA1021A234@dsl-only.net> References: <61985953-493F-432C-888E-3F4A06BBCA38@dsl-only.net> <15615670-92D1-4FA9-9E2D-C957119F348D@dsl-only.net> To: Tom Vijlbrief X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Oct 2016 15:35:16 -0000 [Adding a clarification.] On 2016-Oct-2, at 8:20 AM, Mark Millard wrote: > Thanks for the notes. >=20 > On 2016-Oct-2, at 7:17 AM, Tom Vijlbrief = wrote: >>=20 >> No change (at least in my tree) since my last report on this list = somewhere in May or June. >>=20 >> The kernel boots with 4 cpus and working usb. I use an usb ethernet = device and usb disk with the root filesysteem. Compiling and running = ports works, but a build world fails randomly with a memory access error = eg after running 15 minutes. >=20 > Sounds possibly similar to TARGET_ARCH=3Dpowerpc 's stack-handling = SVR4 ABI violation when world is built by clang 3.8.0 (bad clang code = generation). To get to the point of buildworld going through I had to = change the kernel to provide a so-called "red-zone" on the stack during = signal handling to protect the stack from being trashed. buildworld gets = extensive signals (SIGCHLD) and so without the "red-zone" it would = eventually get trashed addresses, far before getting near completion. I see my wording was poor for indicating the staging: I was already = running a powerpc world built with clang 3.8.0's bad powerpc code = generation when I tried to buildworld and had the signal handling = problems (stack usage conflicts). The "red-zone" kernel hack allowed = such buildworld activity to reliably work despite the clang 3.8.0 based = bad code that was in use. > [Context: buildkernel via gcc 4.2.1 but buildworld via clang 3.8.0 .] >=20 > [Side note: I've tried aarch64 releng/11.0 (first RELEASE's raw) under = qemu on Ubuntu 16.04.1 on the ODroid-C2 but it gots periodic illegal = instructions in very basic operation, no builds active.] >=20 >> I don't think it makes sense to work on this until a freebsd rpi3 = arm64 port is officially supported... >=20 > [FYI: http://ameridroid.com/products/raspberry-pi-2-model-b-1gb-ram = lists the RPi2B as both "out of stock" and "discontinued" and has for = some time.] >=20 >> Op zo 2 okt. 2016 15:04 schreef Mark Millard : >> . . . >> Anything worth reporting on the ODroid-C2 details for FreeBSD: what = works, what does not, what needs to be done to boot FreeBSD, and so on? = (I assume head [CURRENT-12 these days].) >>=20 >>=20 >> Looking around. . . >>=20 >>=20 >> https://github.com/tomtor/image-freebsd-c2 >>=20 >> seems to have last been updated on May 7 (vs. = https://github.com/tomtor/image-freebsd-pine64 's April 17). >>=20 >>=20 >> https://github.com/tomtor/freebsd/tree/tc2 >>=20 >> seems to have last been updated on June 17. >=20 =3D=3D=3D Mark Millard markmi at dsl-only.net _______________________________________________ freebsd-arm@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-arm To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" From owner-freebsd-arm@freebsd.org Sun Oct 2 22:06:38 2016 Return-Path: Delivered-To: freebsd-arm@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 8FF38ADA6FB for ; Sun, 2 Oct 2016 22:06:38 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x243.google.com (mail-io0-x243.google.com [IPv6:2607:f8b0:4001:c06::243]) (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 667383E9 for ; Sun, 2 Oct 2016 22:06:38 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x243.google.com with SMTP id p26so2009673ioo.2 for ; Sun, 02 Oct 2016 15:06:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=anoepKcGHJNdDMUyKfTgSCsPXiqBYJaoIVjMdkAbKf8=; b=nwbM1D9/Jq9GFbw48zkUEr/x3/2B3v4CZ9I6PNf8NxD53pFVNDyRnH70nAPvxH6koP VRYSZIsoy4PpIB2slgrrzPkWvd1026KPAvlXa9EYevCpXj7q48zDE6CvAC9pHGBVUOf/ X5icSj74VH/r7isPWtWKZMOrWlIRijp64PgX5qfvmxexbecu00Vuljf5ZjlckdiAD6YV 0TSmMXxIRqzJxUXlXQlLTpsMo2s35VYNuyTASv+SkLFEtsf5PeMNknmXPH5723vsGSrG oihiR+w2OzOQSNiI4vzQbC4wbdRIoawoDSuVBfJTCpL2y9p8XerHTiqxetFMyyBLu9H9 BiBQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=anoepKcGHJNdDMUyKfTgSCsPXiqBYJaoIVjMdkAbKf8=; b=dtpbdaTKr2OIfHSR313z+R7bzLdcgP4gLm8TAyoptNhbADcMCSlGtsORlZIWKRFfGe 5oxd6L1HW1NLj36XGPM3FuZtfXKYUIPoQ2FKtDwv0jBZQyDk86S+d3YoRvXTSGsN6Atc MolvNDEbJ+y215xw1orQ201td9IL4WWcSvG9s4x69rzxmLNUlj9lWaUv7N2l1vXqQSh5 /Q3TjQp7EFh9rLX/cKGCozJtm4rByYaPFDyFWxpFIvoqg9qRdS/QHDNARaVhlLnmafnT KHCy5d92BUludj4KcZImOv9mJKJmMTkoI9wEfzIp8vxpONoCCruE8GdCwcZwv3Lw8XFu 2GQg== X-Gm-Message-State: AA6/9RnyDvCtJsfCLuGxy280z5SvUpaO5WYKk+b7wH1xWwezZuoD1xZxK7dW+1XMDWqNYri2YB7vU3OTNQMhEg== X-Received: by 10.107.30.11 with SMTP id e11mr19100402ioe.57.1475445997682; Sun, 02 Oct 2016 15:06:37 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.36.65.7 with HTTP; Sun, 2 Oct 2016 15:06:37 -0700 (PDT) X-Originating-IP: [50.253.99.174] In-Reply-To: <20161002123700.662f2868688b4b32465395aa@bidouilliste.com> References: <36160c78-9095-f716-8041-3eb7656642af@herveybayaustralia.com.au> <20161002123700.662f2868688b4b32465395aa@bidouilliste.com> From: Warner Losh Date: Sun, 2 Oct 2016 16:06:37 -0600 X-Google-Sender-Auth: VeXtshChV4xbs0z7eZYbw2EmG5k Message-ID: Subject: Re: u-boot efi option To: Emmanuel Vadot Cc: Da Rock , "freebsd-arm@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Oct 2016 22:06:38 -0000 How long do you think until this is mature enough we can cut over to it? There's issues with ubldr on newer u-boot version on some of the platforms we support. If we could cut over to this, that would be great. Warner On Sun, Oct 2, 2016 at 4:37 AM, Emmanuel Vadot wrote: > > Hello, > > I've commited every needed change on our side, for uboot side you will > need this patch : > https://people.freebsd.org/~manu/u-boot_201609_efi.diff > > The only drawback is that you will need to have your partition aligned > on 512kb boundaries on the mmc. > > I've successfully booted my beaglebone black and most of my Allwinner > boards with UEFI. > > Some part of the uboot patch have started to be upstreamed, for > the others I need to rework on some part before I upstream them. > > Cheers, > > On Sun, 2 Oct 2016 19:56:54 +1000 > Da Rock wrote: > >> Has anyone tried this option yet? I've heard someone got it going for >> slack, but I thought it sounded like it might make it easier for running >> freebsd. >> >> I'm currently trying to build a more current u-boot to test it. >> >> _______________________________________________ >> freebsd-arm@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-arm >> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" > > > -- > Emmanuel Vadot > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" From owner-freebsd-arm@freebsd.org Mon Oct 3 01:38:14 2016 Return-Path: Delivered-To: freebsd-arm@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 94FE0AD93DB; Mon, 3 Oct 2016 01:38:14 +0000 (UTC) (envelope-from jenkins-admin@FreeBSD.org) Received: from jenkins-9.freebsd.org (jenkins-9.freebsd.org [8.8.178.209]) by mx1.freebsd.org (Postfix) with ESMTP id 88D83818; Mon, 3 Oct 2016 01:38:14 +0000 (UTC) (envelope-from jenkins-admin@FreeBSD.org) Received: from jenkins-9.freebsd.org (localhost [127.0.0.1]) by jenkins-9.freebsd.org (Postfix) with ESMTP id 7D51D125; Mon, 3 Oct 2016 01:38:14 +0000 (UTC) Date: Mon, 3 Oct 2016 01:38:07 +0000 (GMT) From: jenkins-admin@FreeBSD.org To: rmacklem@FreeBSD.org, jenkins-admin@FreeBSD.org, freebsd-stable@FreeBSD.org, freebsd-arm@FreeBSD.org Message-ID: <645435186.6.1475458694527.JavaMail.jenkins@jenkins-9.freebsd.org> Subject: FreeBSD_STABLE_11-arm64 - Build #186 - Failure MIME-Version: 1.0 X-Jenkins-Job: FreeBSD_STABLE_11-arm64 X-Jenkins-Result: FAILURE Precedence: bulk Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Oct 2016 01:38:14 -0000 FreeBSD_STABLE_11-arm64 - Build #186 - Failure: Build information: https://jenkins.FreeBSD.org/job/FreeBSD_STABLE_11-arm64/186/ Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_STABLE_11-arm64/186/changes Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_STABLE_11-arm64/186/console Change summaries: 306609 by rmacklem: MFC: r304026 Update the nfsstats structure to include the changes needed by the patch in D1626 plus changes so that it includes counts for NFSv4.1 (and the draft of NFSv4.2). Also, make all the counts uint64_t and add a vers field at the beginning, so that future revisions can easily be implemented. There is code in place to handle the old vesion of the nfsstats structure for backwards binary compatibility. Subsequent commits will update nfsstat(8) to use the new fields. The end of the build log: [...truncated 115735 lines...] --- .depend --- echo newgrp.full: /usr/obj/arm64.aarch64/usr/src/tmp/usr/lib/libc.a /usr/obj/arm64.aarch64/usr/src/tmp/usr/lib/libcrypt.a /usr/obj/arm64.aarch64/usr/src/tmp/usr/lib/libutil.a >> .depend --- newgrp.o --- cc -B/usr/local/aarch64-freebsd/bin/ -O2 -pipe -g -MD -MF.depend.newgrp.o -MTnewgrp.o -std=gnu99 -fstack-protector-strong -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -Wmissing-variable-declarations -Wthread-safety -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-variable -Qunused-arguments -c /usr/src/usr.bin/newgrp/newgrp.c -o newgrp.o --- all_subdir_usr.sbin --- --- exmutex.o --- cc -B/usr/local/aarch64-freebsd/bin/ -O2 -pipe -DACPI_EXEC_APP -fno-strict-aliasing -I/usr/src/usr.sbin/acpi/acpidb/../../../sys -g -MD -MF.depend.exmutex.o -MTexmutex.o -std=gnu99 -fstack-protector-strong -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-variable -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-function -Wno-enum-conversion -Wno-unused-local-typedef -Qunused-arguments -c /usr/src/usr.sbin/acpi/acpidb/../../../sys/contrib/dev/acpica/components/executer/exmutex.c -o exmutex.o --- all_subdir_secure --- --- d1_srvr.po --- cc -B/usr/local/aarch64-freebsd/bin/ -pg -O2 -pipe -I/usr/src/secure/lib/libssl/../../../crypto/openssl -DTERMIOS -DANSI_SOURCE -DOPENSSL_THREADS -DDSO_DLFCN -DHAVE_DLFCN_H -DL_ENDIAN -I/usr/src/secure/lib/libssl/../../../crypto/openssl/crypto -MD -MF.depend.d1_srvr.po -MTd1_srvr.po -std=gnu99 -fstack-protector-strong -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-variable -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-function -Wno-enum-conversion -Wno-unused-local-typedef -Wno-switch -Wno-switch-enum -Wno-knr-promoted-parameter -Wno-parentheses -Qunused-arguments -c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/d1_srvr.c -o d1_srvr.po --- all_subdir_usr.bin --- --- newgrp.full --- cc -B/usr/local/aarch64-freebsd/bin/ -O2 -pipe -g -std=gnu99 -fstack-protector-strong -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -Wmissing-variable-declarations -Wthread-safety -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-variable -Qunused-arguments -o newgrp.full newgrp.o -lcrypt -lutil --- newgrp.1.gz --- gzip -cn /usr/src/usr.bin/newgrp/newgrp.1 > newgrp.1.gz --- newgrp.debug --- /usr/local/aarch64-freebsd/bin/objcopy --only-keep-debug newgrp.full newgrp.debug --- newgrp --- /usr/local/aarch64-freebsd/bin/objcopy --strip-debug --add-gnu-debuglink=newgrp.debug newgrp.full newgrp --- all_subdir_usr.bin/nfsstat --- ===> usr.bin/nfsstat (all) --- all_subdir_usr.sbin --- --- exnames.o --- cc -B/usr/local/aarch64-freebsd/bin/ -O2 -pipe -DACPI_EXEC_APP -fno-strict-aliasing -I/usr/src/usr.sbin/acpi/acpidb/../../../sys -g -MD -MF.depend.exnames.o -MTexnames.o -std=gnu99 -fstack-protector-strong -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-variable -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-function -Wno-enum-conversion -Wno-unused-local-typedef -Qunused-arguments -c /usr/src/usr.sbin/acpi/acpidb/../../../sys/contrib/dev/acpica/components/executer/exnames.c -o exnames.o --- all_subdir_usr.bin --- --- .depend --- echo nfsstat.full: /usr/obj/arm64.aarch64/usr/src/tmp/usr/lib/libc.a >> .depend --- nfsstat.o --- cc -B/usr/local/aarch64-freebsd/bin/ -O2 -pipe -DNFS -g -MD -MF.depend.nfsstat.o -MTnfsstat.o -std=gnu99 -fstack-protector-strong -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -Wmissing-variable-declarations -Wthread-safety -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-variable -Qunused-arguments -c /usr/src/usr.bin/nfsstat/nfsstat.c -o nfsstat.o /usr/src/usr.bin/nfsstat/nfsstat.c:301:4: error: array index 72 is past the end of the array (which contains 49 elements) [-Werror,-Warray-bounds] ext_nfsstats.srvrpccnt[NFSV4OP_SYMLINK], ^ ~~~~~~~~~~~~~~~ /usr/obj/arm64.aarch64/usr/src/tmp/usr/include/fs/nfs/nfsport.h:457:2: note: array 'srvrpccnt' declared here int srvrpccnt[NFSV4OP_NOPS + NFSV4OP_FAKENOPS]; ^ /usr/src/usr.bin/nfsstat/nfsstat.c:302:4: error: array index 73 is past the end of the array (which contains 49 elements) [-Werror,-Warray-bounds] ext_nfsstats.srvrpccnt[NFSV4OP_MKDIR], ^ ~~~~~~~~~~~~~ /usr/obj/arm64.aarch64/usr/src/tmp/usr/include/fs/nfs/nfsport.h:457:2: note: array 'srvrpccnt' declared here int srvrpccnt[NFSV4OP_NOPS + NFSV4OP_FAKENOPS]; ^ /usr/src/usr.bin/nfsstat/nfsstat.c:303:4: error: array index 74 is past the end of the array (which contains 49 elements) [-Werror,-Warray-bounds] ext_nfsstats.srvrpccnt[NFSV4OP_RMDIR], ^ ~~~~~~~~~~~~~ /usr/obj/arm64.aarch64/usr/src/tmp/usr/include/fs/nfs/nfsport.h:457:2: note: array 'srvrpccnt' declared here int srvrpccnt[NFSV4OP_NOPS + NFSV4OP_FAKENOPS]; ^ /usr/src/usr.bin/nfsstat/nfsstat.c:305:4: error: array index 75 is past the end of the array (which contains 49 elements) [-Werror,-Warray-bounds] ext_nfsstats.srvrpccnt[NFSV4OP_READDIRPLUS], ^ ~~~~~~~~~~~~~~~~~~~ /usr/obj/arm64.aarch64/usr/src/tmp/usr/include/fs/nfs/nfsport.h:457:2: note: array 'srvrpccnt' declared here int srvrpccnt[NFSV4OP_NOPS + NFSV4OP_FAKENOPS]; ^ /usr/src/usr.bin/nfsstat/nfsstat.c:310:4: error: array index 76 is past the end of the array (which contains 49 elements) [-Werror,-Warray-bounds] ext_nfsstats.srvrpccnt[NFSV4OP_MKNOD], ^ ~~~~~~~~~~~~~ /usr/obj/arm64.aarch64/usr/src/tmp/usr/include/fs/nfs/nfsport.h:457:2: note: array 'srvrpccnt' declared here int srvrpccnt[NFSV4OP_NOPS + NFSV4OP_FAKENOPS]; ^ /usr/src/usr.bin/nfsstat/nfsstat.c:311:4: error: array index 77 is past the end of the array (which contains 49 elements) [-Werror,-Warray-bounds] ext_nfsstats.srvrpccnt[NFSV4OP_FSSTAT], ^ ~~~~~~~~~~~~~~ /usr/obj/arm64.aarch64/usr/src/tmp/usr/include/fs/nfs/nfsport.h:457:2: note: array 'srvrpccnt' declared here int srvrpccnt[NFSV4OP_NOPS + NFSV4OP_FAKENOPS]; ^ /usr/src/usr.bin/nfsstat/nfsstat.c:312:4: error: array index 78 is past the end of the array (which contains 49 elements) [-Werror,-Warray-bounds] ext_nfsstats.srvrpccnt[NFSV4OP_FSINFO], ^ ~~~~~~~~~~~~~~ /usr/obj/arm64.aarch64/usr/src/tmp/usr/include/fs/nfs/nfsport.h:457:2: note: array 'srvrpccnt' declared here int srvrpccnt[NFSV4OP_NOPS + NFSV4OP_FAKENOPS]; ^ /usr/src/usr.bin/nfsstat/nfsstat.c:313:4: error: array index 79 is past the end of the array (which contains 49 elements) [-Werror,-Warray-bounds] ext_nfsstats.srvrpccnt[NFSV4OP_PATHCONF], ^ ~~~~~~~~~~~~~~~~ /usr/obj/arm64.aarch64/usr/src/tmp/usr/include/fs/nfs/nfsport.h:457:2: note: array 'srvrpccnt' declared here int srvrpccnt[NFSV4OP_NOPS + NFSV4OP_FAKENOPS]; ^ /usr/src/usr.bin/nfsstat/nfsstat.c:544:7: error: array index 80 is past the end of the array (which contains 49 elements) [-Werror,-Warray-bounds] ext_nfsstats.srvrpccnt[NFSV4OP_V3CREATE], ^ ~~~~~~~~~~~~~~~~ /usr/obj/arm64.aarch64/usr/src/tmp/usr/include/fs/nfs/nfsport.h:457:2: note: array 'srvrpccnt' declared here int srvrpccnt[NFSV4OP_NOPS + NFSV4OP_FAKENOPS]; ^ /usr/src/usr.bin/nfsstat/nfsstat.c:554:7: error: array index 72 is past the end of the array (which contains 49 elements) [-Werror,-Warray-bounds] ext_nfsstats.srvrpccnt[NFSV4OP_SYMLINK], ^ ~~~~~~~~~~~~~~~ /usr/obj/arm64.aarch64/usr/src/tmp/usr/include/fs/nfs/nfsport.h:457:2: note: array 'srvrpccnt' declared here int srvrpccnt[NFSV4OP_NOPS + NFSV4OP_FAKENOPS]; ^ /usr/src/usr.bin/nfsstat/nfsstat.c:555:7: error: array index 73 is past the end of the array (which contains 49 elements) [-Werror,-Warray-bounds] ext_nfsstats.srvrpccnt[NFSV4OP_MKDIR], ^ ~~~~~~~~~~~~~ /usr/obj/arm64.aarch64/usr/src/tmp/usr/include/fs/nfs/nfsport.h:457:2: note: array 'srvrpccnt' declared here int srvrpccnt[NFSV4OP_NOPS + NFSV4OP_FAKENOPS]; ^ /usr/src/usr.bin/nfsstat/nfsstat.c:556:7: error: array index 74 is past the end of the array (which contains 49 elements) [-Werror,-Warray-bounds] ext_nfsstats.srvrpccnt[NFSV4OP_RMDIR], ^ ~~~~~~~~~~~~~ /usr/obj/arm64.aarch64/usr/src/tmp/usr/include/fs/nfs/nfsport.h:457:2: note: array 'srvrpccnt' declared here int srvrpccnt[NFSV4OP_NOPS + NFSV4OP_FAKENOPS]; ^ /usr/src/usr.bin/nfsstat/nfsstat.c:558:7: error: array index 75 is past the end of the array (which contains 49 elements) [-Werror,-Warray-bounds] ext_nfsstats.srvrpccnt[NFSV4OP_READDIRPLUS], ^ ~~~~~~~~~~~~~~~~~~~ /usr/obj/arm64.aarch64/usr/src/tmp/usr/include/fs/nfs/nfsport.h:457:2: note: array 'srvrpccnt' declared here int srvrpccnt[NFSV4OP_NOPS + NFSV4OP_FAKENOPS]; ^ /usr/src/usr.bin/nfsstat/nfsstat.c:566:7: error: array index 76 is past the end of the array (which contains 49 elements) [-Werror,-Warray-bounds] ext_nfsstats.srvrpccnt[NFSV4OP_MKNOD], ^ ~~~~~~~~~~~~~ /usr/obj/arm64.aarch64/usr/src/tmp/usr/include/fs/nfs/nfsport.h:457:2: note: array 'srvrpccnt' declared here int srvrpccnt[NFSV4OP_NOPS + NFSV4OP_FAKENOPS]; ^ /usr/src/usr.bin/nfsstat/nfsstat.c:567:7: error: array index 77 is past the end of the array (which contains 49 elements) [-Werror,-Warray-bounds] ext_nfsstats.srvrpccnt[NFSV4OP_FSSTAT], ^ ~~~~~~~~~~~~~~ /usr/obj/arm64.aarch64/usr/src/tmp/usr/include/fs/nfs/nfsport.h:457:2: note: array 'srvrpccnt' declared here int srvrpccnt[NFSV4OP_NOPS + NFSV4OP_FAKENOPS]; ^ /usr/src/usr.bin/nfsstat/nfsstat.c:568:7: error: array index 78 is past the end of the array (which contains 49 elements) [-Werror,-Warray-bounds] ext_nfsstats.srvrpccnt[NFSV4OP_FSINFO], ^ ~~~~~~~~~~~~~~ /usr/obj/arm64.aarch64/usr/src/tmp/usr/include/fs/nfs/nfsport.h:457:2: note: array 'srvrpccnt' declared here int srvrpccnt[NFSV4OP_NOPS + NFSV4OP_FAKENOPS]; ^ /usr/src/usr.bin/nfsstat/nfsstat.c:569:7: error: array index 79 is past the end of the array (which contains 49 elements) [-Werror,-Warray-bounds] ext_nfsstats.srvrpccnt[NFSV4OP_PATHCONF], ^ ~~~~~~~~~~~~~~~~ /usr/obj/arm64.aarch64/usr/src/tmp/usr/include/fs/nfs/nfsport.h:457:2: note: array 'srvrpccnt' declared here int srvrpccnt[NFSV4OP_NOPS + NFSV4OP_FAKENOPS]; ^ /usr/src/usr.bin/nfsstat/nfsstat.c:719:4: error: array index 75 is past the end of the array (which contains 49 elements) [-Werror,-Warray-bounds] DELTA(srvrpccnt[NFSV4OP_READDIRPLUS])); ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ /usr/src/usr.bin/nfsstat/nfsstat.c:86:23: note: expanded from macro 'DELTA' #define DELTA(field) (nfsstats.field - lastst.field) ^ ~~~~~ /usr/obj/arm64.aarch64/usr/src/tmp/usr/include/fs/nfs/nfsport.h:457:2: note: array 'srvrpccnt' declared here int srvrpccnt[NFSV4OP_NOPS + NFSV4OP_FAKENOPS]; ^ /usr/src/usr.bin/nfsstat/nfsstat.c:719:4: error: array index 75 is past the end of the array (which contains 49 elements) [-Werror,-Warray-bounds] DELTA(srvrpccnt[NFSV4OP_READDIRPLUS])); ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ /usr/src/usr.bin/nfsstat/nfsstat.c:86:40: note: expanded from macro 'DELTA' #define DELTA(field) (nfsstats.field - lastst.field) ^ ~~~~~ /usr/obj/arm64.aarch64/usr/src/tmp/usr/include/fs/nfs/nfsport.h:457:2: note: array 'srvrpccnt' declared here int srvrpccnt[NFSV4OP_NOPS + NFSV4OP_FAKENOPS]; ^ 19 errors generated. *** [nfsstat.o] Error code 1 bmake[4]: stopped in /usr/src/usr.bin/nfsstat 1 error bmake[4]: stopped in /usr/src/usr.bin/nfsstat *** [all_subdir_usr.bin/nfsstat] Error code 2 bmake[3]: stopped in /usr/src/usr.bin 1 error bmake[3]: stopped in /usr/src/usr.bin *** [all_subdir_usr.bin] Error code 2 bmake[2]: stopped in /usr/src --- all_subdir_usr.sbin --- A failure has been detected in another branch of the parallel make bmake[5]: stopped in /usr/src/usr.sbin/acpi/acpidb *** [all] Error code 2 bmake[4]: stopped in /usr/src/usr.sbin/acpi 1 error bmake[4]: stopped in /usr/src/usr.sbin/acpi *** [all_subdir_usr.sbin/acpi] Error code 2 bmake[3]: stopped in /usr/src/usr.sbin 1 error bmake[3]: stopped in /usr/src/usr.sbin *** [all_subdir_usr.sbin] Error code 2 bmake[2]: stopped in /usr/src --- all_subdir_secure --- A failure has been detected in another branch of the parallel make bmake[5]: stopped in /usr/src/secure/lib/libssl *** [all] Error code 2 bmake[4]: stopped in /usr/src/secure/lib 1 error bmake[4]: stopped in /usr/src/secure/lib *** [all_subdir_secure/lib] Error code 2 bmake[3]: stopped in /usr/src/secure 1 error bmake[3]: stopped in /usr/src/secure *** [all_subdir_secure] Error code 2 bmake[2]: stopped in /usr/src --- all_subdir_lib --- A failure has been detected in another branch of the parallel make bmake[4]: stopped in /usr/src/lib/libsqlite3 *** [all_subdir_lib/libsqlite3] Error code 2 bmake[3]: stopped in /usr/src/lib 1 error bmake[3]: stopped in /usr/src/lib *** [all_subdir_lib] Error code 2 bmake[2]: stopped in /usr/src 4 errors bmake[2]: stopped in /usr/src *** [everything] Error code 2 bmake[1]: stopped in /usr/src 1 error bmake[1]: stopped in /usr/src *** [buildworld] Error code 2 make: stopped in /usr/src 1 error make: stopped in /usr/src Build step 'Execute shell' marked build as failure [WARNINGS] Skipping publisher since build result is FAILURE [PostBuildScript] - Execution post build scripts. [FreeBSD_STABLE_11-arm64] $ /bin/sh -xe /tmp/hudson1954720639212566030.sh + export 'PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin' + export 'jname=FreeBSD_STABLE_11-arm64' + echo 'clean up jail FreeBSD_STABLE_11-arm64' clean up jail FreeBSD_STABLE_11-arm64 + sudo jail -r FreeBSD_STABLE_11-arm64 + sudo ifconfig igb0 inet6 2610:1c1:1:607c::103:1 -alias + sudo umount FreeBSD_STABLE_11-arm64/usr/src + sudo umount FreeBSD_STABLE_11-arm64/dev + sudo rm -fr FreeBSD_STABLE_11-arm64 + true + sudo chflags -R noschg FreeBSD_STABLE_11-arm64 + sudo rm -fr FreeBSD_STABLE_11-arm64 Email was triggered for: Failure - Any Sending email for trigger: Failure - Any From owner-freebsd-arm@freebsd.org Mon Oct 3 07:51:34 2016 Return-Path: Delivered-To: freebsd-arm@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 13DB9AF3A2A for ; Mon, 3 Oct 2016 07:51:34 +0000 (UTC) (envelope-from soko.tica@gmail.com) Received: from mail-io0-x231.google.com (mail-io0-x231.google.com [IPv6:2607:f8b0:4001:c06::231]) (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 D01BBC1F for ; Mon, 3 Oct 2016 07:51:33 +0000 (UTC) (envelope-from soko.tica@gmail.com) Received: by mail-io0-x231.google.com with SMTP id i202so32396750ioi.2 for ; Mon, 03 Oct 2016 00:51:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to; bh=1W7/aBYtMN3nEydBug8ptwno/3tiKE59TbsfywQwLm8=; b=uZaIZi3tdZRXFDm9G3IpZ/cFrf74MVsQUnr8xIeibm6rAYpGXZgfqQ+0Ixjdci6NC1 X+TdmTY6ti1tWIGF/hm8cZJ9Vl+a2+X9npXEeaCyLUBs2bRpYBCi6cLeP4UA/4T/vbhB XK1F7JYwTHuPaOvtJEqvZi1oM5sItVLOsKilv3ND9zgyN6G70TnqBUFhVKgAZIFU5riH 4OQvYVV/LSZgRuubcQUdVpJgMmPEMeqIF9BYnEVkSoCR6kJ9HCKAl/4XwG8wtvb8e+NW jNYIrQlLCdwikI7txK9PbxOYMzKrUiQjzOHGk+EvhB/K+nLEJyIroYGorWnCmY0YUiuF 9seA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to; bh=1W7/aBYtMN3nEydBug8ptwno/3tiKE59TbsfywQwLm8=; b=Vk27hlnpiDHpIkUmqMmA8Is//QU8HP2b96BuF9KO0SefZhxaJADpyyEO1dLlyEMaGx n44/P8m4l/MeEax8b8PC81xgvlx46LBYY9kzmFieptSvL9pnsO98hIAGz4C3enBA3/z1 9K29xBY4G2SrrSNKdowXW9nHpfm86cj0G0nq4ajGocpZhQGDDiHSXpCLcSEVK90jgimY nhVYBKvmh24KCNMcIyI+CTADPJv+pcv3a4GGAFnQO45h1t85V/eR8MEtuoPzk13wjzzv H62GBMgOk1AmEjJQfD/EwukSc4D3gkifXxkUnIKZIqwlKVWqxy14/WTVkX9hzk9nEYyH 3+GA== X-Gm-Message-State: AA6/9RnNZSgUFbdD/cuiMMqhkeN7n9mdKkA4GmkRfPvZ0MVLqIjBHzA3GbCCN/YVdjGLMLWBiLQy1vkg646mCQ== X-Received: by 10.107.41.7 with SMTP id p7mr9239466iop.16.1475481093090; Mon, 03 Oct 2016 00:51:33 -0700 (PDT) MIME-Version: 1.0 Received: by 10.79.22.193 with HTTP; Mon, 3 Oct 2016 00:51:32 -0700 (PDT) Reply-To: soko.tica@gmail.com In-Reply-To: <1465920582.1188.145.camel@freebsd.org> References: <1465863644.1188.134.camel@freebsd.org> <20160614051509.GA50738@cicely7.cicely.de> <1465913904.1188.141.camel@freebsd.org> <1465920582.1188.145.camel@freebsd.org> From: "soko.tica" Date: Mon, 3 Oct 2016 09:51:32 +0200 Message-ID: Subject: Re: default root pass for bananapi To: freebsd-arm@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Oct 2016 07:51:34 -0000 Thanks for your support, I have finally managed to login through ssh freebsd pass freebsd. FreeBSD11-RC3 works on BananaPro (apart from HDMI), and I have discovered that I have a faulty USB to RS232 cable, so ssh was the only possibility left. On Tue, Jun 14, 2016 at 6:09 PM, Ian Lepore wrote: > On Tue, 2016-06-14 at 08:39 -0700, Russell Haley wrote: > > Would users be created as part of installworld? Anyone know where I > > would go to look for that (Makefile perhaps)? Is there documentation > > on how the images on the website are built? > > The images are built using the stuff in src/release. Creating users > would be done as extra work after installworld, but I don't know the > details of what's in the image-building scripts and configs. > > -- Ian > > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" > From owner-freebsd-arm@freebsd.org Mon Oct 3 08:33:11 2016 Return-Path: Delivered-To: freebsd-arm@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 F1433AF3739 for ; Mon, 3 Oct 2016 08:33:11 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.blih.net", Issuer "mail.blih.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 6AA11626 for ; Mon, 3 Oct 2016 08:33:10 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) by mail.blih.net (OpenSMTPD) with ESMTP id 0365d58c; Mon, 3 Oct 2016 10:33:07 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; s=mail; bh=E4zzJoqh8d4T/maAMoVoNr7MJPA=; b=NFc4Udcj/6sRLRgRgxB1uJulfbY7 OgVI6FYU8PJxkVDHYddbim9fhAhHcmoS1iDnmZIj3orKhyXavW0Wh0a9pdg+rI7b lDrYxeCNj0fYIguSgHEbXh3JNvc8J7FyUBf0xOif8YCsWo44TkgoTD3YEUU+iDfB VPHglD/FgjJtzeA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; q=dns; s= mail; b=E1tobXdjgODkx1x7nFkvMp5REjjQql6qAvthboMQE6DCFCmStuVnzGDy NTNOBylPfF6HkXDFmZ4o06DurPt3yBvQ4knlZE8ps3vTMroqoQS5vcwN2DRR5gX/ wkfj/rpD5+MOhq5xHc4vDLMgHMHVW41YloCu4iiFk5DtvxALuF0= Received: from arcadia.staff.bocal.org (163.5.251.145 [163.5.251.145]) by mail.blih.net (OpenSMTPD) with ESMTPSA id 7df2fe01 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Mon, 3 Oct 2016 10:33:07 +0200 (CEST) Date: Mon, 3 Oct 2016 10:32:47 +0200 From: Emmanuel Vadot To: Warner Losh Cc: Da Rock , "freebsd-arm@freebsd.org" Subject: Re: u-boot efi option Message-Id: <20161003103247.78ff7596607755ce0f204648@bidouilliste.com> In-Reply-To: References: <36160c78-9095-f716-8041-3eb7656642af@herveybayaustralia.com.au> <20161002123700.662f2868688b4b32465395aa@bidouilliste.com> X-Mailer: Sylpheed 3.5.0 (GTK+ 2.24.29; amd64-portbld-freebsd11.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Oct 2016 08:33:12 -0000 I've never had any problem with it (I know it doesn't really answer to your question). SuSe have switch to EFI (the main developer for U-Boot EFI is from SuSe), OpenBSD too. The main problem right now for people to test is that the partition on the arm images that we provide aren't aligned for it to work. I either need to fix the bug for non 512kb-aligned partition or aligned them in the release scripts. Also I don't know which ports-tree re@ is using for snapshots. I think that they use the latest quarterly for release and stable. So we have to be carefull when we will switch the ports to UEFI. In the meantime don't hesitate to test with my patch. If you have the correct dtb in /dtb/ on the msdos part U-Boot will load it. For booting automatically just put boot1.efi as /efi/boot/bootarm.efi On Sun, 2 Oct 2016 16:06:37 -0600 Warner Losh wrote: > How long do you think until this is mature enough we can cut over to it? > There's issues with ubldr on newer u-boot version on some of the platforms > we support. If we could cut over to this, that would be great. > > Warner > > On Sun, Oct 2, 2016 at 4:37 AM, Emmanuel Vadot wrote: > > > > Hello, > > > > I've commited every needed change on our side, for uboot side you will > > need this patch : > > https://people.freebsd.org/~manu/u-boot_201609_efi.diff > > > > The only drawback is that you will need to have your partition aligned > > on 512kb boundaries on the mmc. > > > > I've successfully booted my beaglebone black and most of my Allwinner > > boards with UEFI. > > > > Some part of the uboot patch have started to be upstreamed, for > > the others I need to rework on some part before I upstream them. > > > > Cheers, > > > > On Sun, 2 Oct 2016 19:56:54 +1000 > > Da Rock wrote: > > > >> Has anyone tried this option yet? I've heard someone got it going for > >> slack, but I thought it sounded like it might make it easier for running > >> freebsd. > >> > >> I'm currently trying to build a more current u-boot to test it. > >> > >> _______________________________________________ > >> freebsd-arm@freebsd.org mailing list > >> https://lists.freebsd.org/mailman/listinfo/freebsd-arm > >> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" > > > > > > -- > > Emmanuel Vadot > > _______________________________________________ > > freebsd-arm@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" -- Emmanuel Vadot From owner-freebsd-arm@freebsd.org Mon Oct 3 09:01:38 2016 Return-Path: Delivered-To: freebsd-arm@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 8A16DAF284C for ; Mon, 3 Oct 2016 09:01:38 +0000 (UTC) (envelope-from freebsd-arm@herveybayaustralia.com.au) Received: from mail.unitedinsong.com.au (mail.unitedinsong.com.au [150.101.178.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id F3B6D251 for ; Mon, 3 Oct 2016 09:01:37 +0000 (UTC) (envelope-from freebsd-arm@herveybayaustralia.com.au) Received: from [192.168.0.177] (laptop3.herveybayaustralia.com.au [192.168.0.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.unitedinsong.com.au (Postfix) with ESMTPSA id D925162090; Mon, 3 Oct 2016 19:01:32 +1000 (EST) Subject: Re: u-boot efi option To: Emmanuel Vadot , Warner Losh References: <36160c78-9095-f716-8041-3eb7656642af@herveybayaustralia.com.au> <20161002123700.662f2868688b4b32465395aa@bidouilliste.com> <20161003103247.78ff7596607755ce0f204648@bidouilliste.com> Cc: "freebsd-arm@freebsd.org" From: Da Rock Message-ID: Date: Mon, 3 Oct 2016 19:01:30 +1000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <20161003103247.78ff7596607755ce0f204648@bidouilliste.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Oct 2016 09:01:38 -0000 A few points that I'd like clarification on: 1. I'm not having much success on rpi3 with any images, but I'm working on my own 64bit anyway. I'm also trying to get a handle on what the process of running the system on the rpi3 actually is as well. Fun... :) So the 512kb alignment, why is that an issue? Perhaps I'm a little foggy, but isn't that simply a case of partitioning correctly? 2. I should have mentioned this initially (which is why I was checking efi status to see if I was banging on for no reason), but I'm having trouble (still) compiling u-boot version that has the efi capability (2016.09) - can't find . I've tried with clang (x18 error) and gcc to no avail. I tried leveraging ports, but it is not exactly cooperating either (I'll have to try some more diags on that). Anyone have a clue on how to get past this? -I doesn't work, or linking to /usr/local/include. 3. My other query was on the EFI boot process on arm. As I understood, the u-boot is equivalent to boot0? So that means boot1 should then be in the fat partition? Is that what you mean by /efi/boot/bootarm.efi? Or doesn't it need to be? Apologies if I sound like a complete goose, but I'm still new to all things arm yet - but learning fast :) On 03/10/2016 18:32, Emmanuel Vadot wrote: > I've never had any problem with it (I know it doesn't really answer to > your question). > SuSe have switch to EFI (the main developer for U-Boot > EFI is from SuSe), OpenBSD too. > > The main problem right now for people to test is that the partition > on the arm images that we provide aren't aligned for it to work. > > I either need to fix the bug for non 512kb-aligned partition or > aligned them in the release scripts. > > Also I don't know which ports-tree re@ is using for snapshots. I think > that they use the latest quarterly for release and stable. > So we have to be carefull when we will switch the ports to UEFI. > > In the meantime don't hesitate to test with my patch. > > If you have the correct dtb in /dtb/ on the msdos part U-Boot will load > it. > For booting automatically just put boot1.efi as /efi/boot/bootarm.efi > > On Sun, 2 Oct 2016 16:06:37 -0600 > Warner Losh wrote: > >> How long do you think until this is mature enough we can cut over to it? >> There's issues with ubldr on newer u-boot version on some of the platforms >> we support. If we could cut over to this, that would be great. >> >> Warner >> >> On Sun, Oct 2, 2016 at 4:37 AM, Emmanuel Vadot wrote: >>> Hello, >>> >>> I've commited every needed change on our side, for uboot side you will >>> need this patch : >>> https://people.freebsd.org/~manu/u-boot_201609_efi.diff >>> >>> The only drawback is that you will need to have your partition aligned >>> on 512kb boundaries on the mmc. >>> >>> I've successfully booted my beaglebone black and most of my Allwinner >>> boards with UEFI. >>> >>> Some part of the uboot patch have started to be upstreamed, for >>> the others I need to rework on some part before I upstream them. >>> >>> Cheers, >>> >>> On Sun, 2 Oct 2016 19:56:54 +1000 >>> Da Rock wrote: >>> >>>> Has anyone tried this option yet? I've heard someone got it going for >>>> slack, but I thought it sounded like it might make it easier for running >>>> freebsd. >>>> >>>> I'm currently trying to build a more current u-boot to test it. >>>> >>>> _______________________________________________ >>>> freebsd-arm@freebsd.org mailing list >>>> https://lists.freebsd.org/mailman/listinfo/freebsd-arm >>>> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" >>> >>> -- >>> Emmanuel Vadot >>> _______________________________________________ >>> freebsd-arm@freebsd.org mailing list >>> https://lists.freebsd.org/mailman/listinfo/freebsd-arm >>> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" > From owner-freebsd-arm@freebsd.org Mon Oct 3 09:55:06 2016 Return-Path: Delivered-To: freebsd-arm@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 A4FB7AC69BC for ; Mon, 3 Oct 2016 09:55:06 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-72.reflexion.net [208.70.210.72]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 67D4AC03 for ; Mon, 3 Oct 2016 09:55:05 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 1414 invoked from network); 3 Oct 2016 09:54:48 -0000 Received: from unknown (HELO rtc-sm-01.app.dca.reflexion.local) (10.81.150.1) by 0 (rfx-qmail) with SMTP; 3 Oct 2016 09:54:48 -0000 Received: by rtc-sm-01.app.dca.reflexion.local (Reflexion email security v8.00.0) with SMTP; Mon, 03 Oct 2016 05:55:03 -0400 (EDT) Received: (qmail 30539 invoked from network); 3 Oct 2016 09:55:02 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 3 Oct 2016 09:55:02 -0000 Received: from [192.168.0.105] (ip70-189-131-151.lv.lv.cox.net [70.189.131.151]) by iron2.pdx.net (Postfix) with ESMTPSA id 45F03EC770C; Mon, 3 Oct 2016 02:54:57 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: u-boot efi option From: Mark Millard In-Reply-To: Date: Mon, 3 Oct 2016 02:54:56 -0700 Cc: Emmanuel Vadot , Warner Losh , "freebsd-arm@freebsd.org" Message-Id: References: <36160c78-9095-f716-8041-3eb7656642af@herveybayaustralia.com.au> <20161002123700.662f2868688b4b32465395aa@bidouilliste.com> <20161003103247.78ff7596607755ce0f204648@bidouilliste.com> To: Da Rock X-Mailer: Apple Mail (2.3124) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Oct 2016 09:55:06 -0000 On 2016-Oct-3, at 2:01 AM, Da Rock wrote: > A few points that I'd like clarification on: >=20 > 1. I'm not having much success on rpi3 with any images, but I'm = working on my own 64bit anyway. I'm also trying to get a handle on what = the process of running the system on the rpi3 actually is as well. = Fun... :) So the 512kb alignment, why is that an issue? Perhaps I'm a = little foggy, but isn't that simply a case of partitioning correctly? >=20 > 2. I should have mentioned this initially (which is why I was checking = efi status to see if I was banging on for no reason), but I'm having = trouble (still) compiling u-boot version that has the efi capability = (2016.09) - can't find . I've tried with clang (x18 error) = and gcc to no avail. I tried leveraging ports, but it is not exactly = cooperating either (I'll have to try some more diags on that). Anyone = have a clue on how to get past this? -I doesn't work, or linking to = /usr/local/include. Looks to me like sys/_types.h normally exists: # find /usr/include -name _types.h -print=20 /usr/include/machine/_types.h /usr/include/sys/_types.h These two files are not the same by content and so are not equivalent so = /usr/include/sys/_types.h is likely the right one. Using an armv6 = stable/11 context the diff shows where the files came from in svn: < * $FreeBSD: stable/11/sys/arm/include/_types.h 301872 2016-06-13 = 16:48:27Z ian $ --- > * $FreeBSD: stable/11/sys/sys/_types.h 299571 2016-05-12 21:18:17Z = cem $ Note that /usr/local is not involved in the earlier = /usr/include/sys/_types.h path. [I've never tried to build u-boot 2016.09: the above is just a very = generic note about where to find sys/_types.h .] Without more details being presented it is not clear why /usr/include is = not being used as a place to look for sys/_types.h in your context. = (This wording presumes self-hosted builds instead of cross builds for = the path details.) That "not clear" status absent supporting details = may well be true for folks familiar with building 2016.09 as well. > 3. My other query was on the EFI boot process on arm. As I understood, = the u-boot is equivalent to boot0? So that means boot1 should then be in = the fat partition? Is that what you mean by /efi/boot/bootarm.efi? Or = doesn't it need to be? >=20 > Apologies if I sound like a complete goose, but I'm still new to all = things arm yet - but learning fast :) >=20 >=20 > On 03/10/2016 18:32, Emmanuel Vadot wrote: >> I've never had any problem with it (I know it doesn't really answer = to >> your question). >> SuSe have switch to EFI (the main developer for U-Boot >> EFI is from SuSe), OpenBSD too. >>=20 >> The main problem right now for people to test is that the partition >> on the arm images that we provide aren't aligned for it to work. >>=20 >> I either need to fix the bug for non 512kb-aligned partition or >> aligned them in the release scripts. >>=20 >> Also I don't know which ports-tree re@ is using for snapshots. I = think >> that they use the latest quarterly for release and stable. >> So we have to be carefull when we will switch the ports to UEFI. >>=20 >> In the meantime don't hesitate to test with my patch. >>=20 >> If you have the correct dtb in /dtb/ on the msdos part U-Boot will = load >> it. >> For booting automatically just put boot1.efi as = /efi/boot/bootarm.efi >>=20 >> On Sun, 2 Oct 2016 16:06:37 -0600 >> Warner Losh wrote: >>=20 >>> How long do you think until this is mature enough we can cut over = to it? >>> There's issues with ubldr on newer u-boot version on some of the = platforms >>> we support. If we could cut over to this, that would be great. >>>=20 >>> Warner >>>=20 >>> On Sun, Oct 2, 2016 at 4:37 AM, Emmanuel Vadot = wrote: >>>> Hello, >>>>=20 >>>> I've commited every needed change on our side, for uboot side you = will >>>> need this patch : >>>> https://people.freebsd.org/~manu/u-boot_201609_efi.diff >>>>=20 >>>> The only drawback is that you will need to have your partition = aligned >>>> on 512kb boundaries on the mmc. >>>>=20 >>>> I've successfully booted my beaglebone black and most of my = Allwinner >>>> boards with UEFI. >>>>=20 >>>> Some part of the uboot patch have started to be upstreamed, for >>>> the others I need to rework on some part before I upstream them. >>>>=20 >>>> Cheers, >>>>=20 >>>> On Sun, 2 Oct 2016 19:56:54 +1000 >>>> Da Rock wrote: >>>>=20 >>>>> Has anyone tried this option yet? I've heard someone got it going = for >>>>> slack, but I thought it sounded like it might make it easier for = running >>>>> freebsd. >>>>>=20 >>>>> I'm currently trying to build a more current u-boot to test it. . . . =3D=3D=3D Mark Millard markmi at dsl-only.net _______________________________________________ freebsd-arm@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-arm To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" From owner-freebsd-arm@freebsd.org Mon Oct 3 10:23:34 2016 Return-Path: Delivered-To: freebsd-arm@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 BA717AF32A0 for ; Mon, 3 Oct 2016 10:23:34 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.blih.net", Issuer "mail.blih.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 1FA6EF34 for ; Mon, 3 Oct 2016 10:23:33 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) by mail.blih.net (OpenSMTPD) with ESMTP id 1f5bcb67; Mon, 3 Oct 2016 12:23:30 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; s=mail; bh=s9lbAkhJWoOAvBM0Lipzl9VNmS4=; b=XVd8ZEbFSMRa4i5ImK3oMRMESUFm q2k+DHxiHTCdqOTnk//SurkvZrSoeEiv/IXHYlST3kRmnW9jEseYkldgreZGbNwv IHTo7Z70ah2/auzFJ4cS0RPHf7zakHO70nrdgBhpxT8R7txOH0DFaQPquGEvQWvw R7eAkI5bKd03aaI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; q=dns; s= mail; b=gOxdts/Nd9TDyLFlbPPt4uCtdlG7Q6AllaaHxYks6KwZHsYYD1BqtT9p G2oo5NqtHqT1tdfSjirqtae0t/LvLgHbCm6Fwyr1n9EpgM4j2RDDZTR1ce9QQRs4 YCGtHxt7RUZIyl+3XozoCXljMt4wtPZCHkr6u06+Qf/kknEIEi0= Received: from arcadia.staff.bocal.org (163.5.251.145 [163.5.251.145]) by mail.blih.net (OpenSMTPD) with ESMTPSA id e0819c91 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Mon, 3 Oct 2016 12:23:29 +0200 (CEST) Date: Mon, 3 Oct 2016 12:23:09 +0200 From: Emmanuel Vadot To: Da Rock Cc: Warner Losh , "freebsd-arm@freebsd.org" Subject: Re: u-boot efi option Message-Id: <20161003122309.6ab5f4b3c94c33355b682ade@bidouilliste.com> In-Reply-To: References: <36160c78-9095-f716-8041-3eb7656642af@herveybayaustralia.com.au> <20161002123700.662f2868688b4b32465395aa@bidouilliste.com> <20161003103247.78ff7596607755ce0f204648@bidouilliste.com> X-Mailer: Sylpheed 3.5.0 (GTK+ 2.24.29; amd64-portbld-freebsd11.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Oct 2016 10:23:34 -0000 On Mon, 3 Oct 2016 19:01:30 +1000 Da Rock wrote: > A few points that I'd like clarification on: > > 1. I'm not having much success on rpi3 with any images, but I'm working > on my own 64bit anyway. I'm also trying to get a handle on what the > process of running the system on the rpi3 actually is as well. Fun... :) > So the 512kb alignment, why is that an issue? Perhaps I'm a little > foggy, but isn't that simply a case of partitioning correctly? I don't know exactly to be honest, I have to read a lot of code. > 2. I should have mentioned this initially (which is why I was checking > efi status to see if I was banging on for no reason), but I'm having > trouble (still) compiling u-boot version that has the efi capability > (2016.09) - can't find . I've tried with clang (x18 error) > and gcc to no avail. I tried leveraging ports, but it is not exactly > cooperating either (I'll have to try some more diags on that). Anyone > have a clue on how to get past this? -I doesn't work, or linking to > /usr/local/include. - Install {arm,aarch64}-none-{eabi,elf}-{gcc,binutils} - cd uboot-src - gmake ARCH={arm,arm64} CROSS_COMPILE={arm,aarch64}-none-{eabi,elf}- XXX_defconfig - gmake ARCH={arm,arm64} CROSS_COMPILE={arm,aarch64}-none-{eabi,elf}- I've never tried with clang. > 3. My other query was on the EFI boot process on arm. As I understood, > the u-boot is equivalent to boot0? So that means boot1 should then be in > the fat partition? Is that what you mean by /efi/boot/bootarm.efi? Or > doesn't it need to be? U-Boot can be seen as BIOS/boot0 combined. Yes boot1.efi MUST be on the fat partition and by default an EFI firmware will load /efi/boot/boot${ARCH}.efi > Apologies if I sound like a complete goose, but I'm still new to all > things arm yet - but learning fast :) Don't worry, this motivate me more to do a page on the wiki about UEFI on arm :) > On 03/10/2016 18:32, Emmanuel Vadot wrote: > > I've never had any problem with it (I know it doesn't really answer to > > your question). > > SuSe have switch to EFI (the main developer for U-Boot > > EFI is from SuSe), OpenBSD too. > > > > The main problem right now for people to test is that the partition > > on the arm images that we provide aren't aligned for it to work. > > > > I either need to fix the bug for non 512kb-aligned partition or > > aligned them in the release scripts. > > > > Also I don't know which ports-tree re@ is using for snapshots. I think > > that they use the latest quarterly for release and stable. > > So we have to be carefull when we will switch the ports to UEFI. > > > > In the meantime don't hesitate to test with my patch. > > > > If you have the correct dtb in /dtb/ on the msdos part U-Boot will load > > it. > > For booting automatically just put boot1.efi as /efi/boot/bootarm.efi > > > > On Sun, 2 Oct 2016 16:06:37 -0600 > > Warner Losh wrote: > > > >> How long do you think until this is mature enough we can cut over to it? > >> There's issues with ubldr on newer u-boot version on some of the platforms > >> we support. If we could cut over to this, that would be great. > >> > >> Warner > >> > >> On Sun, Oct 2, 2016 at 4:37 AM, Emmanuel Vadot wrote: > >>> Hello, > >>> > >>> I've commited every needed change on our side, for uboot side you will > >>> need this patch : > >>> https://people.freebsd.org/~manu/u-boot_201609_efi.diff > >>> > >>> The only drawback is that you will need to have your partition aligned > >>> on 512kb boundaries on the mmc. > >>> > >>> I've successfully booted my beaglebone black and most of my Allwinner > >>> boards with UEFI. > >>> > >>> Some part of the uboot patch have started to be upstreamed, for > >>> the others I need to rework on some part before I upstream them. > >>> > >>> Cheers, > >>> > >>> On Sun, 2 Oct 2016 19:56:54 +1000 > >>> Da Rock wrote: > >>> > >>>> Has anyone tried this option yet? I've heard someone got it going for > >>>> slack, but I thought it sounded like it might make it easier for running > >>>> freebsd. > >>>> > >>>> I'm currently trying to build a more current u-boot to test it. > >>>> > >>>> _______________________________________________ > >>>> freebsd-arm@freebsd.org mailing list > >>>> https://lists.freebsd.org/mailman/listinfo/freebsd-arm > >>>> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" > >>> > >>> -- > >>> Emmanuel Vadot > >>> _______________________________________________ > >>> freebsd-arm@freebsd.org mailing list > >>> https://lists.freebsd.org/mailman/listinfo/freebsd-arm > >>> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" > > -- Emmanuel Vadot From owner-freebsd-arm@freebsd.org Mon Oct 3 11:37:33 2016 Return-Path: Delivered-To: freebsd-arm@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 C0E61AC6884; Mon, 3 Oct 2016 11:37:33 +0000 (UTC) (envelope-from jenkins-admin@FreeBSD.org) Received: from jenkins-9.freebsd.org (jenkins-9.freebsd.org [8.8.178.209]) by mx1.freebsd.org (Postfix) with ESMTP id A56853E8; Mon, 3 Oct 2016 11:37:33 +0000 (UTC) (envelope-from jenkins-admin@FreeBSD.org) Received: from jenkins-9.freebsd.org (localhost [127.0.0.1]) by jenkins-9.freebsd.org (Postfix) with ESMTP id AA50813B; Mon, 3 Oct 2016 11:37:33 +0000 (UTC) Date: Mon, 3 Oct 2016 11:37:32 +0000 (GMT) From: jenkins-admin@FreeBSD.org To: kib@FreeBSD.org, jenkins-admin@FreeBSD.org, freebsd-stable@FreeBSD.org, freebsd-arm@FreeBSD.org Message-ID: <539957058.11.1475494653705.JavaMail.jenkins@jenkins-9.freebsd.org> In-Reply-To: <645435186.6.1475458694527.JavaMail.jenkins@jenkins-9.freebsd.org> References: <645435186.6.1475458694527.JavaMail.jenkins@jenkins-9.freebsd.org> Subject: FreeBSD_STABLE_11-arm64 - Build #187 - Still Failing MIME-Version: 1.0 X-Jenkins-Job: FreeBSD_STABLE_11-arm64 X-Jenkins-Result: FAILURE Precedence: bulk Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Oct 2016 11:37:33 -0000 FreeBSD_STABLE_11-arm64 - Build #187 - Still Failing: Build information: https://jenkins.FreeBSD.org/job/FreeBSD_STABLE_11-arm64/187/ Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_STABLE_11-arm64/187/changes Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_STABLE_11-arm64/187/console Change summaries: 306629 by kib: MFC r306350: For machines which support PCID but not have INVPCID instruction, i.e. SandyBridge and IvyBridge, correct a race between pmap_activate() and invltlb_pcid_handler(). 306628 by kib: MFC r305978: Detect x2APIC mode on boot and obey it. 306627 by kib: MFC r305977: Be more strict when selecting between snapshot/regular mount. 306625 by kib: MFC r306334: Document thr_suspend(2) and thr_wake(2). MFC r306506: Reword the statement. 306624 by kib: MFC r306505: Add an article. The end of the build log: [...truncated 117149 lines...] --- all_subdir_usr.bin --- --- newgrp.full --- cc -B/usr/local/aarch64-freebsd/bin/ -O2 -pipe -g -std=gnu99 -fstack-protector-strong -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -Wmissing-variable-declarations -Wthread-safety -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-variable -Qunused-arguments -o newgrp.full newgrp.o -lcrypt -lutil --- all_subdir_secure --- --- all_subdir_secure/libexec/sftp-server --- ===> secure/libexec/sftp-server (all) --- all_subdir_usr.bin --- --- newgrp.1.gz --- gzip -cn /usr/src/usr.bin/newgrp/newgrp.1 > newgrp.1.gz --- all_subdir_secure --- --- .depend --- echo sftp-server.full: /usr/obj/arm64.aarch64/usr/src/tmp/usr/lib/libc.a /usr/obj/arm64.aarch64/usr/src/tmp/usr/lib/libprivatessh.a >> .depend --- all_subdir_usr.bin --- --- newgrp.debug --- --- all_subdir_secure --- --- sftp-server.o --- --- all_subdir_usr.bin --- /usr/local/aarch64-freebsd/bin/objcopy --only-keep-debug newgrp.full newgrp.debug --- all_subdir_secure --- cc -B/usr/local/aarch64-freebsd/bin/ -O2 -pipe -I/usr/src/secure/libexec/sftp-server/../../../crypto/openssh -include ssh_namespace.h -DHAVE_LDNS=1 -g -MD -MF.depend.sftp-server.o -MTsftp-server.o -std=gnu99 -fstack-protector-strong -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-variable -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-function -Wno-enum-conversion -Wno-unused-local-typedef -Wno-switch -Wno-switch-enum -Wno-knr-promoted-parameter -Wno-parentheses -Qunused-arguments -c /usr/src/secure/libexec/sftp-server/../../../crypto/openssh/sftp-server.c -o sftp-server.o --- all_subdir_usr.bin --- --- newgrp --- /usr/local/aarch64-freebsd/bin/objcopy --strip-debug --add-gnu-debuglink=newgrp.debug newgrp.full newgrp --- all_subdir_usr.bin/nfsstat --- ===> usr.bin/nfsstat (all) --- .depend --- echo nfsstat.full: /usr/obj/arm64.aarch64/usr/src/tmp/usr/lib/libc.a >> .depend --- nfsstat.o --- cc -B/usr/local/aarch64-freebsd/bin/ -O2 -pipe -DNFS -g -MD -MF.depend.nfsstat.o -MTnfsstat.o -std=gnu99 -fstack-protector-strong -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -Wmissing-variable-declarations -Wthread-safety -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-variable -Qunused-arguments -c /usr/src/usr.bin/nfsstat/nfsstat.c -o nfsstat.o /usr/src/usr.bin/nfsstat/nfsstat.c:301:4: error: array index 72 is past the end of the array (which contains 49 elements) [-Werror,-Warray-bounds] ext_nfsstats.srvrpccnt[NFSV4OP_SYMLINK], ^ ~~~~~~~~~~~~~~~ /usr/obj/arm64.aarch64/usr/src/tmp/usr/include/fs/nfs/nfsport.h:457:2: note: array 'srvrpccnt' declared here int srvrpccnt[NFSV4OP_NOPS + NFSV4OP_FAKENOPS]; ^ /usr/src/usr.bin/nfsstat/nfsstat.c:302:4: error: array index 73 is past the end of the array (which contains 49 elements) [-Werror,-Warray-bounds] ext_nfsstats.srvrpccnt[NFSV4OP_MKDIR], ^ ~~~~~~~~~~~~~ /usr/obj/arm64.aarch64/usr/src/tmp/usr/include/fs/nfs/nfsport.h:457:2: note: array 'srvrpccnt' declared here int srvrpccnt[NFSV4OP_NOPS + NFSV4OP_FAKENOPS]; ^ /usr/src/usr.bin/nfsstat/nfsstat.c:303:4: error: array index 74 is past the end of the array (which contains 49 elements) [-Werror,-Warray-bounds] ext_nfsstats.srvrpccnt[NFSV4OP_RMDIR], ^ ~~~~~~~~~~~~~ /usr/obj/arm64.aarch64/usr/src/tmp/usr/include/fs/nfs/nfsport.h:457:2: note: array 'srvrpccnt' declared here int srvrpccnt[NFSV4OP_NOPS + NFSV4OP_FAKENOPS]; ^ /usr/src/usr.bin/nfsstat/nfsstat.c:305:4: error: array index 75 is past the end of the array (which contains 49 elements) [-Werror,-Warray-bounds] ext_nfsstats.srvrpccnt[NFSV4OP_READDIRPLUS], ^ ~~~~~~~~~~~~~~~~~~~ /usr/obj/arm64.aarch64/usr/src/tmp/usr/include/fs/nfs/nfsport.h:457:2: note: array 'srvrpccnt' declared here int srvrpccnt[NFSV4OP_NOPS + NFSV4OP_FAKENOPS]; ^ /usr/src/usr.bin/nfsstat/nfsstat.c:310:4: error: array index 76 is past the end of the array (which contains 49 elements) [-Werror,-Warray-bounds] ext_nfsstats.srvrpccnt[NFSV4OP_MKNOD], ^ ~~~~~~~~~~~~~ /usr/obj/arm64.aarch64/usr/src/tmp/usr/include/fs/nfs/nfsport.h:457:2: note: array 'srvrpccnt' declared here int srvrpccnt[NFSV4OP_NOPS + NFSV4OP_FAKENOPS]; ^ /usr/src/usr.bin/nfsstat/nfsstat.c:311:4: error: array index 77 is past the end of the array (which contains 49 elements) [-Werror,-Warray-bounds] ext_nfsstats.srvrpccnt[NFSV4OP_FSSTAT], ^ ~~~~~~~~~~~~~~ /usr/obj/arm64.aarch64/usr/src/tmp/usr/include/fs/nfs/nfsport.h:457:2: note: array 'srvrpccnt' declared here int srvrpccnt[NFSV4OP_NOPS + NFSV4OP_FAKENOPS]; ^ /usr/src/usr.bin/nfsstat/nfsstat.c:312:4: error: array index 78 is past the end of the array (which contains 49 elements) [-Werror,-Warray-bounds] ext_nfsstats.srvrpccnt[NFSV4OP_FSINFO], ^ ~~~~~~~~~~~~~~ /usr/obj/arm64.aarch64/usr/src/tmp/usr/include/fs/nfs/nfsport.h:457:2: note: array 'srvrpccnt' declared here int srvrpccnt[NFSV4OP_NOPS + NFSV4OP_FAKENOPS]; ^ /usr/src/usr.bin/nfsstat/nfsstat.c:313:4: error: array index 79 is past the end of the array (which contains 49 elements) [-Werror,-Warray-bounds] ext_nfsstats.srvrpccnt[NFSV4OP_PATHCONF], ^ ~~~~~~~~~~~~~~~~ /usr/obj/arm64.aarch64/usr/src/tmp/usr/include/fs/nfs/nfsport.h:457:2: note: array 'srvrpccnt' declared here int srvrpccnt[NFSV4OP_NOPS + NFSV4OP_FAKENOPS]; ^ /usr/src/usr.bin/nfsstat/nfsstat.c:544:7: error: array index 80 is past the end of the array (which contains 49 elements) [-Werror,-Warray-bounds] ext_nfsstats.srvrpccnt[NFSV4OP_V3CREATE], ^ ~~~~~~~~~~~~~~~~ /usr/obj/arm64.aarch64/usr/src/tmp/usr/include/fs/nfs/nfsport.h:457:2: note: array 'srvrpccnt' declared here int srvrpccnt[NFSV4OP_NOPS + NFSV4OP_FAKENOPS]; ^ /usr/src/usr.bin/nfsstat/nfsstat.c:554:7: error: array index 72 is past the end of the array (which contains 49 elements) [-Werror,-Warray-bounds] ext_nfsstats.srvrpccnt[NFSV4OP_SYMLINK], ^ ~~~~~~~~~~~~~~~ /usr/obj/arm64.aarch64/usr/src/tmp/usr/include/fs/nfs/nfsport.h:457:2: note: array 'srvrpccnt' declared here int srvrpccnt[NFSV4OP_NOPS + NFSV4OP_FAKENOPS]; ^ /usr/src/usr.bin/nfsstat/nfsstat.c:555:7: error: array index 73 is past the end of the array (which contains 49 elements) [-Werror,-Warray-bounds] ext_nfsstats.srvrpccnt[NFSV4OP_MKDIR], ^ ~~~~~~~~~~~~~ /usr/obj/arm64.aarch64/usr/src/tmp/usr/include/fs/nfs/nfsport.h:457:2: note: array 'srvrpccnt' declared here int srvrpccnt[NFSV4OP_NOPS + NFSV4OP_FAKENOPS]; ^ /usr/src/usr.bin/nfsstat/nfsstat.c:556:7: error: array index 74 is past the end of the array (which contains 49 elements) [-Werror,-Warray-bounds] ext_nfsstats.srvrpccnt[NFSV4OP_RMDIR], ^ ~~~~~~~~~~~~~ /usr/obj/arm64.aarch64/usr/src/tmp/usr/include/fs/nfs/nfsport.h:457:2: note: array 'srvrpccnt' declared here int srvrpccnt[NFSV4OP_NOPS + NFSV4OP_FAKENOPS]; ^ /usr/src/usr.bin/nfsstat/nfsstat.c:558:7: error: array index 75 is past the end of the array (which contains 49 elements) [-Werror,-Warray-bounds] ext_nfsstats.srvrpccnt[NFSV4OP_READDIRPLUS], ^ ~~~~~~~~~~~~~~~~~~~ /usr/obj/arm64.aarch64/usr/src/tmp/usr/include/fs/nfs/nfsport.h:457:2: note: array 'srvrpccnt' declared here int srvrpccnt[NFSV4OP_NOPS + NFSV4OP_FAKENOPS]; ^ /usr/src/usr.bin/nfsstat/nfsstat.c:566:7: error: array index 76 is past the end of the array (which contains 49 elements) [-Werror,-Warray-bounds] ext_nfsstats.srvrpccnt[NFSV4OP_MKNOD], ^ ~~~~~~~~~~~~~ /usr/obj/arm64.aarch64/usr/src/tmp/usr/include/fs/nfs/nfsport.h:457:2: note: array 'srvrpccnt' declared here int srvrpccnt[NFSV4OP_NOPS + NFSV4OP_FAKENOPS]; ^ /usr/src/usr.bin/nfsstat/nfsstat.c:567:7: error: array index 77 is past the end of the array (which contains 49 elements) [-Werror,-Warray-bounds] ext_nfsstats.srvrpccnt[NFSV4OP_FSSTAT], ^ ~~~~~~~~~~~~~~ /usr/obj/arm64.aarch64/usr/src/tmp/usr/include/fs/nfs/nfsport.h:457:2: note: array 'srvrpccnt' declared here int srvrpccnt[NFSV4OP_NOPS + NFSV4OP_FAKENOPS]; ^ /usr/src/usr.bin/nfsstat/nfsstat.c:568:7: error: array index 78 is past the end of the array (which contains 49 elements) [-Werror,-Warray-bounds] ext_nfsstats.srvrpccnt[NFSV4OP_FSINFO], ^ ~~~~~~~~~~~~~~ /usr/obj/arm64.aarch64/usr/src/tmp/usr/include/fs/nfs/nfsport.h:457:2: note: array 'srvrpccnt' declared here int srvrpccnt[NFSV4OP_NOPS + NFSV4OP_FAKENOPS]; ^ /usr/src/usr.bin/nfsstat/nfsstat.c:569:7: error: array index 79 is past the end of the array (which contains 49 elements) [-Werror,-Warray-bounds] ext_nfsstats.srvrpccnt[NFSV4OP_PATHCONF], ^ ~~~~~~~~~~~~~~~~ /usr/obj/arm64.aarch64/usr/src/tmp/usr/include/fs/nfs/nfsport.h:457:2: note: array 'srvrpccnt' declared here int srvrpccnt[NFSV4OP_NOPS + NFSV4OP_FAKENOPS]; ^ /usr/src/usr.bin/nfsstat/nfsstat.c:719:4: error: array index 75 is past the end of the array (which contains 49 elements) [-Werror,-Warray-bounds] DELTA(srvrpccnt[NFSV4OP_READDIRPLUS])); ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ /usr/src/usr.bin/nfsstat/nfsstat.c:86:23: note: expanded from macro 'DELTA' #define DELTA(field) (nfsstats.field - lastst.field) ^ ~~~~~ /usr/obj/arm64.aarch64/usr/src/tmp/usr/include/fs/nfs/nfsport.h:457:2: note: array 'srvrpccnt' declared here int srvrpccnt[NFSV4OP_NOPS + NFSV4OP_FAKENOPS]; ^ /usr/src/usr.bin/nfsstat/nfsstat.c:719:4: error: array index 75 is past the end of the array (which contains 49 elements) [-Werror,-Warray-bounds] DELTA(srvrpccnt[NFSV4OP_READDIRPLUS])); ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ /usr/src/usr.bin/nfsstat/nfsstat.c:86:40: note: expanded from macro 'DELTA' #define DELTA(field) (nfsstats.field - lastst.field) ^ ~~~~~ /usr/obj/arm64.aarch64/usr/src/tmp/usr/include/fs/nfs/nfsport.h:457:2: note: array 'srvrpccnt' declared here int srvrpccnt[NFSV4OP_NOPS + NFSV4OP_FAKENOPS]; ^ 19 errors generated. *** [nfsstat.o] Error code 1 bmake[4]: stopped in /usr/src/usr.bin/nfsstat 1 error bmake[4]: stopped in /usr/src/usr.bin/nfsstat *** [all_subdir_usr.bin/nfsstat] Error code 2 bmake[3]: stopped in /usr/src/usr.bin 1 error bmake[3]: stopped in /usr/src/usr.bin *** [all_subdir_usr.bin] Error code 2 bmake[2]: stopped in /usr/src --- all_subdir_usr.sbin --- A failure has been detected in another branch of the parallel make bmake[5]: stopped in /usr/src/usr.sbin/acpi/iasl *** [all] Error code 2 bmake[4]: stopped in /usr/src/usr.sbin/acpi 1 error bmake[4]: stopped in /usr/src/usr.sbin/acpi *** [all_subdir_usr.sbin/acpi] Error code 2 bmake[3]: stopped in /usr/src/usr.sbin 1 error bmake[3]: stopped in /usr/src/usr.sbin *** [all_subdir_usr.sbin] Error code 2 bmake[2]: stopped in /usr/src --- all_subdir_secure --- A failure has been detected in another branch of the parallel make bmake[5]: stopped in /usr/src/secure/libexec/sftp-server *** [all_subdir_secure/libexec/sftp-server] Error code 2 bmake[4]: stopped in /usr/src/secure/libexec 1 error bmake[4]: stopped in /usr/src/secure/libexec *** [all_subdir_secure/libexec] Error code 2 bmake[3]: stopped in /usr/src/secure 1 error bmake[3]: stopped in /usr/src/secure *** [all_subdir_secure] Error code 2 bmake[2]: stopped in /usr/src --- all_subdir_lib --- A failure has been detected in another branch of the parallel make bmake[4]: stopped in /usr/src/lib/libsqlite3 *** [all_subdir_lib/libsqlite3] Error code 2 bmake[3]: stopped in /usr/src/lib 1 error bmake[3]: stopped in /usr/src/lib *** [all_subdir_lib] Error code 2 bmake[2]: stopped in /usr/src 4 errors bmake[2]: stopped in /usr/src *** [everything] Error code 2 bmake[1]: stopped in /usr/src 1 error bmake[1]: stopped in /usr/src *** [buildworld] Error code 2 make: stopped in /usr/src 1 error make: stopped in /usr/src Build step 'Execute shell' marked build as failure [WARNINGS] Skipping publisher since build result is FAILURE [PostBuildScript] - Execution post build scripts. [FreeBSD_STABLE_11-arm64] $ /bin/sh -xe /tmp/hudson4461814648424260392.sh + export 'PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin' + export 'jname=FreeBSD_STABLE_11-arm64' + echo 'clean up jail FreeBSD_STABLE_11-arm64' clean up jail FreeBSD_STABLE_11-arm64 + sudo jail -r FreeBSD_STABLE_11-arm64 + sudo ifconfig igb0 inet6 2610:1c1:1:607c::103:1 -alias + sudo umount FreeBSD_STABLE_11-arm64/usr/src + sudo umount FreeBSD_STABLE_11-arm64/dev + sudo rm -fr FreeBSD_STABLE_11-arm64 + true + sudo chflags -R noschg FreeBSD_STABLE_11-arm64 + sudo rm -fr FreeBSD_STABLE_11-arm64 Email was triggered for: Failure - Any Sending email for trigger: Failure - Any From owner-freebsd-arm@freebsd.org Mon Oct 3 13:47:07 2016 Return-Path: Delivered-To: freebsd-arm@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 50C8FAC6F50; Mon, 3 Oct 2016 13:47:07 +0000 (UTC) (envelope-from jenkins-admin@FreeBSD.org) Received: from jenkins-9.freebsd.org (jenkins-9.freebsd.org [8.8.178.209]) by mx1.freebsd.org (Postfix) with ESMTP id 44484C05; Mon, 3 Oct 2016 13:47:07 +0000 (UTC) (envelope-from jenkins-admin@FreeBSD.org) Received: from jenkins-9.freebsd.org (localhost [127.0.0.1]) by jenkins-9.freebsd.org (Postfix) with ESMTP id 7969313F; Mon, 3 Oct 2016 13:47:07 +0000 (UTC) Date: Mon, 3 Oct 2016 13:47:04 +0000 (GMT) From: jenkins-admin@FreeBSD.org To: rmacklem@FreeBSD.org, jenkins-admin@FreeBSD.org, freebsd-stable@FreeBSD.org, freebsd-arm@FreeBSD.org Message-ID: <1168940461.15.1475502427501.JavaMail.jenkins@jenkins-9.freebsd.org> In-Reply-To: <539957058.11.1475494653705.JavaMail.jenkins@jenkins-9.freebsd.org> References: <539957058.11.1475494653705.JavaMail.jenkins@jenkins-9.freebsd.org> Subject: FreeBSD_STABLE_11-arm64 - Build #188 - Fixed MIME-Version: 1.0 X-Jenkins-Job: FreeBSD_STABLE_11-arm64 X-Jenkins-Result: SUCCESS Precedence: bulk Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Oct 2016 13:47:07 -0000 FreeBSD_STABLE_11-arm64 - Build #188 - Fixed: Build information: https://jenkins.FreeBSD.org/job/FreeBSD_STABLE_11-arm64/188/ Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_STABLE_11-arm64/188/changes Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_STABLE_11-arm64/188/console Change summaries: 306633 by rmacklem: MFC: r304059 Update the man page to descibe the "-d" option added by r304058. This is a content change. 306632 by rmacklem: MFC: r304058, r304066, r304194 Update nfsstat.c to use the new kernel nfsstat structure and add the new "-d" flag from D1626. The man page will be updated in a subsequent commit. From owner-freebsd-arm@freebsd.org Mon Oct 3 13:55:39 2016 Return-Path: Delivered-To: freebsd-arm@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 5B7BEAF32CD for ; Mon, 3 Oct 2016 13:55:39 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x232.google.com (mail-it0-x232.google.com [IPv6:2607:f8b0:4001:c0b::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 22182242 for ; Mon, 3 Oct 2016 13:55:39 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x232.google.com with SMTP id r192so115759160ita.0 for ; Mon, 03 Oct 2016 06:55:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=s87Ttl9/AG+At/Ttyz8pzsk4MwNn29tLi1fvE01cB64=; b=gfjHayiPoBBYb2Tutfni22kMvgOtXVQwqLmjGB90MjOHIPkfX357sh9rFEVZFIqnTx sGiFzVebcFLqTMclUvynMtIMIqhYFAz4dAWILXqMuqaAYbjhnR41/Gmr8yUYNdo9alDi uV5PQfMiAKI2qZGGdyS0oBnrYHNYIKLNa7/0GTmeH7IbbesS/3Xn4wdD6++6w/TQPKn9 Aqf59pKmU4M2TUbuvaVcFj+3eRjIl2kBquVML2Qne+5FLnM+R+gVwstwEPJo+/2AVTmD gEYJipO9Hf73ZmL6/xSf17MtALMqOO6gQ6vefkcgQBKPkPdEHarPFWVjMibrXuNKFCUv E3BQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=s87Ttl9/AG+At/Ttyz8pzsk4MwNn29tLi1fvE01cB64=; b=GW307jiSiPE4OIYf/c4i4Rt0UE8LykbJAz3G/q07nWnXFlkOcBnb4ZuBot5VyphKco eSLiiy/rTcTusQtNnmesGjGtc3/F/LN8SBZRJgBP2j243Z0jSGz9LKrO2iAw7QsXg+oo GhEmzfF6PinuEW08zx4QZQLAEU+bbfuZY5H0GHNmQ5vos8ghHAxQ9r6SSgBpnIRjFKM0 MlOzvfFDlym2/fUWqPsTBdZMPFuW4IENpRJDm2uiIV46FJcDc/E9soe69y9ElrpFoeSv N1bMrCmTWmoUJluWjUm581BCdyg/JXo57j748xU3EW5sSIDAiNgxxpzgLi/zWmxIeFvB l88A== X-Gm-Message-State: AA6/9RmCVzsT4Hkh7kyJtjX+cbdYohZtC9vx4TNKXBgqHCThsWL4PRyYMnWI0w+h/8zmx59kamFFWeBA+DxVoA== X-Received: by 10.36.39.67 with SMTP id g64mr17547108ita.93.1475502938482; Mon, 03 Oct 2016 06:55:38 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.36.65.7 with HTTP; Mon, 3 Oct 2016 06:55:37 -0700 (PDT) X-Originating-IP: [69.53.245.200] In-Reply-To: <20161003122309.6ab5f4b3c94c33355b682ade@bidouilliste.com> References: <36160c78-9095-f716-8041-3eb7656642af@herveybayaustralia.com.au> <20161002123700.662f2868688b4b32465395aa@bidouilliste.com> <20161003103247.78ff7596607755ce0f204648@bidouilliste.com> <20161003122309.6ab5f4b3c94c33355b682ade@bidouilliste.com> From: Warner Losh Date: Mon, 3 Oct 2016 07:55:37 -0600 X-Google-Sender-Auth: fNQGRuJ8xKMkETcfWDhG4u7JOkY Message-ID: Subject: Re: u-boot efi option To: Emmanuel Vadot Cc: Da Rock , "freebsd-arm@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Oct 2016 13:55:39 -0000 Sounds like we should target 12 to be EFI only then, or at least EFI preferred with our infrastructure setup to cope. Why is there a 512k alignment requirement? Or is that just the typical 512k at the start of the disk is needed for uboot issue? Warner On Mon, Oct 3, 2016 at 4:23 AM, Emmanuel Vadot wrote: > On Mon, 3 Oct 2016 19:01:30 +1000 > Da Rock wrote: > >> A few points that I'd like clarification on: >> >> 1. I'm not having much success on rpi3 with any images, but I'm working >> on my own 64bit anyway. I'm also trying to get a handle on what the >> process of running the system on the rpi3 actually is as well. Fun... :) >> So the 512kb alignment, why is that an issue? Perhaps I'm a little >> foggy, but isn't that simply a case of partitioning correctly? > > I don't know exactly to be honest, I have to read a lot of code. > >> 2. I should have mentioned this initially (which is why I was checking >> efi status to see if I was banging on for no reason), but I'm having >> trouble (still) compiling u-boot version that has the efi capability >> (2016.09) - can't find . I've tried with clang (x18 error) >> and gcc to no avail. I tried leveraging ports, but it is not exactly >> cooperating either (I'll have to try some more diags on that). Anyone >> have a clue on how to get past this? -I doesn't work, or linking to >> /usr/local/include. > > - Install {arm,aarch64}-none-{eabi,elf}-{gcc,binutils} > - cd uboot-src > - gmake ARCH={arm,arm64} CROSS_COMPILE={arm,aarch64}-none-{eabi,elf}- > XXX_defconfig > - gmake ARCH={arm,arm64} CROSS_COMPILE={arm,aarch64}-none-{eabi,elf}- > > I've never tried with clang. > >> 3. My other query was on the EFI boot process on arm. As I understood, >> the u-boot is equivalent to boot0? So that means boot1 should then be in >> the fat partition? Is that what you mean by /efi/boot/bootarm.efi? Or >> doesn't it need to be? > > U-Boot can be seen as BIOS/boot0 combined. > Yes boot1.efi MUST be on the fat partition and by default an EFI > firmware will load /efi/boot/boot${ARCH}.efi > >> Apologies if I sound like a complete goose, but I'm still new to all >> things arm yet - but learning fast :) > > Don't worry, this motivate me more to do a page on the wiki about UEFI > on arm :) > >> On 03/10/2016 18:32, Emmanuel Vadot wrote: >> > I've never had any problem with it (I know it doesn't really answer to >> > your question). >> > SuSe have switch to EFI (the main developer for U-Boot >> > EFI is from SuSe), OpenBSD too. >> > >> > The main problem right now for people to test is that the partition >> > on the arm images that we provide aren't aligned for it to work. >> > >> > I either need to fix the bug for non 512kb-aligned partition or >> > aligned them in the release scripts. >> > >> > Also I don't know which ports-tree re@ is using for snapshots. I think >> > that they use the latest quarterly for release and stable. >> > So we have to be carefull when we will switch the ports to UEFI. >> > >> > In the meantime don't hesitate to test with my patch. >> > >> > If you have the correct dtb in /dtb/ on the msdos part U-Boot will load >> > it. >> > For booting automatically just put boot1.efi as /efi/boot/bootarm.efi >> > >> > On Sun, 2 Oct 2016 16:06:37 -0600 >> > Warner Losh wrote: >> > >> >> How long do you think until this is mature enough we can cut over to it? >> >> There's issues with ubldr on newer u-boot version on some of the platforms >> >> we support. If we could cut over to this, that would be great. >> >> >> >> Warner >> >> >> >> On Sun, Oct 2, 2016 at 4:37 AM, Emmanuel Vadot wrote: >> >>> Hello, >> >>> >> >>> I've commited every needed change on our side, for uboot side you will >> >>> need this patch : >> >>> https://people.freebsd.org/~manu/u-boot_201609_efi.diff >> >>> >> >>> The only drawback is that you will need to have your partition aligned >> >>> on 512kb boundaries on the mmc. >> >>> >> >>> I've successfully booted my beaglebone black and most of my Allwinner >> >>> boards with UEFI. >> >>> >> >>> Some part of the uboot patch have started to be upstreamed, for >> >>> the others I need to rework on some part before I upstream them. >> >>> >> >>> Cheers, >> >>> >> >>> On Sun, 2 Oct 2016 19:56:54 +1000 >> >>> Da Rock wrote: >> >>> >> >>>> Has anyone tried this option yet? I've heard someone got it going for >> >>>> slack, but I thought it sounded like it might make it easier for running >> >>>> freebsd. >> >>>> >> >>>> I'm currently trying to build a more current u-boot to test it. >> >>>> >> >>>> _______________________________________________ >> >>>> freebsd-arm@freebsd.org mailing list >> >>>> https://lists.freebsd.org/mailman/listinfo/freebsd-arm >> >>>> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" >> >>> >> >>> -- >> >>> Emmanuel Vadot >> >>> _______________________________________________ >> >>> freebsd-arm@freebsd.org mailing list >> >>> https://lists.freebsd.org/mailman/listinfo/freebsd-arm >> >>> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" >> > > > > -- > Emmanuel Vadot From owner-freebsd-arm@freebsd.org Mon Oct 3 16:54:10 2016 Return-Path: Delivered-To: freebsd-arm@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 5597CAF31C4 for ; Mon, 3 Oct 2016 16:54:10 +0000 (UTC) (envelope-from db@db.net) Received: from diana.db.net (diana.db.net [66.113.102.10]) by mx1.freebsd.org (Postfix) with ESMTP id 3D76B81D for ; Mon, 3 Oct 2016 16:54:10 +0000 (UTC) (envelope-from db@db.net) Received: from night.db.net (localhost [127.0.0.1]) by diana.db.net (Postfix) with ESMTP id E16FE2AA3A3; Mon, 3 Oct 2016 10:53:12 -0600 (MDT) Received: by night.db.net (Postfix, from userid 1000) id F08FD1CDE4; Mon, 3 Oct 2016 12:54:00 -0400 (EDT) Date: Mon, 3 Oct 2016 12:54:00 -0400 From: Diane Bruce To: Da Rock Cc: Emmanuel Vadot , Warner Losh , "freebsd-arm@freebsd.org" Subject: Re: u-boot efi option Message-ID: <20161003165400.GB30996@night.db.net> References: <36160c78-9095-f716-8041-3eb7656642af@herveybayaustralia.com.au> <20161002123700.662f2868688b4b32465395aa@bidouilliste.com> <20161003103247.78ff7596607755ce0f204648@bidouilliste.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.6.1 (2016-04-27) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Oct 2016 16:54:10 -0000 On Mon, Oct 03, 2016 at 07:01:30PM +1000, Da Rock wrote: > A few points that I'd like clarification on: I've stuck my rpi3 u-boot image at http://people.FreeBSD.org/~db/u-boot-rpi3.tgz I know @loos (Luiz) has started work on the DTS/DTB files for RPi3 so I have not actually done much poking at it other than confirm that I can get a u-boot plus a kernel to start booting. Hopefully @loos can update the dts work so the u-boot port for RPi3 can be finished. > > 1. I'm not having much success on rpi3 with any images, but I'm working > on my own 64bit anyway. I'm also trying to get a handle on what the > process of running the system on the rpi3 actually is as well. Fun... :) > So the 512kb alignment, why is that an issue? Perhaps I'm a little > foggy, but isn't that simply a case of partitioning correctly? I think this question was answered but the hack that's used on the Pine64 works. Why the need for 512Kb alignment still needs investigating. Diane -- - db@FreeBSD.org db@db.net http://www.db.net/~db From owner-freebsd-arm@freebsd.org Mon Oct 3 18:38:36 2016 Return-Path: Delivered-To: freebsd-arm@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 B1740AF3196 for ; Mon, 3 Oct 2016 18:38:36 +0000 (UTC) (envelope-from peter.garshtja@ambient-md.com) Received: from mail-io0-x22d.google.com (mail-io0-x22d.google.com [IPv6:2607:f8b0:4001:c06::22d]) (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 864B477A for ; Mon, 3 Oct 2016 18:38:36 +0000 (UTC) (envelope-from peter.garshtja@ambient-md.com) Received: by mail-io0-x22d.google.com with SMTP id j37so35914081ioo.3 for ; Mon, 03 Oct 2016 11:38:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ambient-md-com.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=vy9E6W4nGNpkXU/NfQEA7ChUawJwF2tyazAZ/hsHk5s=; b=k3+QP9bA20p4Lc2gZqrreH7z88o/P+SKcnoqXkUAgU5kO0l9XgGFiE0VyvCUXFBOyc XjVbCv5YS/vtF6ZqOdwXDf2H4pWb00pS0LFKwRufA3nkaRL3PK8u8WxkVak/YCxecwlR liadj2l5iAUqFuAlVVc7hvcnzvHkTqssbO24yIqnQhjKsfH9jxKIA3aefwmSEu4kmE57 uCyKGxTFRL1FzBhK8TzmeDbDvI6/jzMxrJpE3brL7FRppnLQtbmZSI+FgchR40bqLo0v +UG/GkdPxR1rLpiolr7qpeWxe6bbSpv6B6yQ3qL007Or3sNRfJf+roXS6DBIK8ywi3nw hL1g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=vy9E6W4nGNpkXU/NfQEA7ChUawJwF2tyazAZ/hsHk5s=; b=KVuoryy0+A4DoG03g7skzHh9ZjE/JsyTAt9PZQeP9u11hbbksuH3Xb+145cghBy7L2 MuoaXWYGxwB5W/UHp0LFJHwqtXWZWcScIsEofUfMqwMVNVm8EAT7+4ipdPaiBUBtxeea vzcXmkutA5/rZzU9TONQ0kBK9rlWv+FUCihjyF57LXKp/HwACXI1KTjSZccPK0mA552q r9MnKNLLgP8IZIerOzbiXlIOmgda7NBHHJsUShMuCcsuCC1FFWHZlxnHYPpwmV9Rg2TA oWydAVqG0Xa7movt9xWToPknkt87Ik7JYYBxo/ERgYPV7V1O8vIAnoWNborBAhckt1YX iW2g== X-Gm-Message-State: AA6/9RkUvGWhUd/c/FjUqcdHjttxk8KQ0YEU9TghD6Z0KQschGvKgub1vxeE2bzggNSe+JhfCIHaZ2ZcYyLjsw== X-Received: by 10.107.146.4 with SMTP id u4mr111761iod.34.1475519915232; Mon, 03 Oct 2016 11:38:35 -0700 (PDT) MIME-Version: 1.0 Received: by 10.79.6.204 with HTTP; Mon, 3 Oct 2016 11:38:34 -0700 (PDT) X-Originating-IP: [66.158.136.226] From: peter garshtja Date: Mon, 3 Oct 2016 14:38:34 -0400 Message-ID: Subject: RPI2 AP To: freebsd-arm@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Oct 2016 18:38:36 -0000 Greetings, im running freebsd 11 on rpi2 where i configured urtwn(wifi dongle) and ether interfaces to work in bridge mode. I built an AP and im experiencing weird issue - all stations that are connected to AP after a while start loosing the connection and are not able to reconnect anymore and only rebooting the rpi2 solves the issue. here is my hostapd.conf interface=wlan0 ctrl_interface=/var/run/hostapd ctrl_interface_group=wheel ssid=testap wpa=2 wpa_psk_file=/etc/hostapd.wpa_psk wpa_key_mgmt=WPA-PSK wpa_pairwise=CCMP also here is hostapd logs running in debug mode Configuration file: /etc/hostapd.conf ctrl_interface_group=0 (from group name 'wheel') BSS count 1, BSSID mask 00:00:00:00:00:00 (0 bits) Completing interface initialization hostapd_setup_bss(hapd=0x20863000 (wlan0), first=1) wlan0: Flushing old station entries wlan0: Deauthenticate all stations bsd_set_privacy: enabled=0 bsd_set_key: alg=0 addr=0x0 key_idx=0 set_tx=0 seq_len=0 key_len=0 bsd_del_key: key_idx=0 bsd_set_key: alg=0 addr=0x0 key_idx=1 set_tx=0 seq_len=0 key_len=0 bsd_del_key: key_idx=1 bsd_set_key: alg=0 addr=0x0 key_idx=2 set_tx=0 seq_len=0 key_len=0 bsd_del_key: key_idx=2 bsd_set_key: alg=0 addr=0x0 key_idx=3 set_tx=0 seq_len=0 key_len=0 bsd_del_key: key_idx=3 Using interface wlan0 with hwaddr 00:c6:d2:21:c9:34 and ssid "testap" bsd_set_ieee8021x: enabled=1 bsd_configure_wpa: enable WPA= 0x2 Get randomness: len=32 entropy=0 GMK - hexdump(len=32): [REMOVED] Get randomness: len=32 entropy=0 Key Counter - hexdump(len=32): [REMOVED] WPA: Delay group state machine start until Beacon frames have been configured bsd_set_privacy: enabled=1 bsd_set_opt_ie: set WPA+RSN ie (len 22) WPA: Start group state machine to set initial keys WPA: group state machine entering state GTK_INIT (VLAN-ID 0) Get randomness: len=16 entropy=0 GTK - hexdump(len=16): [REMOVED] WPA: group state machine entering state SETKEYSDONE (VLAN-ID 0) bsd_set_key: alg=3 addr=0x80be3 key_idx=1 set_tx=1 seq_len=0 key_len=16 wlan0: interface state UNINITIALIZED->ENABLED wlan0: AP-ENABLED wlan0: Setup of interface done. ctrl_iface not configured! wlan0: Event ASSOC (0) received wlan0: STA 00:13:ef:66:18:49 IEEE 802.11: associated STA included RSN IE in (Re)AssocReq New STA ap_sta_add: register ap_handle_timer timeout for 00:13:ef:66:18:49 (300 seconds - ap_max_inactivity) wlan0: STA 00:13:ef:66:18:49 WPA: event 1 notification bsd_set_key: alg=0 addr=0x20847008 key_idx=0 set_tx=1 seq_len=0 key_len=0 bsd_del_key: addr=00:13:ef:66:18:49 IEEE 802.1X: Ignore STA - 802.1X not enabled or forced for WPS wlan0: STA 00:13:ef:66:18:49 WPA: start authentication WPA: 00:13:ef:66:18:49 WPA_PTK entering state INITIALIZE bsd_set_key: alg=0 addr=0x20847008 key_idx=0 set_tx=1 seq_len=0 key_len=0 bsd_del_key: addr=00:13:ef:66:18:49 wlan0: STA 00:13:ef:66:18:49 IEEE 802.1X: unauthorizing port WPA: 00:13:ef:66:18:49 WPA_PTK_GROUP entering state IDLE WPA: 00:13:ef:66:18:49 WPA_PTK entering state AUTHENTICATION WPA: 00:13:ef:66:18:49 WPA_PTK entering state AUTHENTICATION2 WPA: Re-initialize GMK/Counter on first station Get randomness: len=32 entropy=1 GMK - hexdump(len=32): [REMOVED] Get randomness: len=32 entropy=0 Key Counter - hexdump(len=32): [REMOVED] Get randomness: len=16 entropy=0 GTK - hexdump(len=16): [REMOVED] bsd_set_key: alg=3 addr=0x80be3 key_idx=1 set_tx=1 seq_len=0 key_len=16 Get randomness: len=32 entropy=0 WPA: Assign ANonce - hexdump(len=32): 8a 5f 94 56 ac e3 d8 80 30 ae e6 fd ab ea 2f b8 fb ac 1e ce 89 b4 8f 7f d0 74 9a a2 32 d2 3a 9f WPA: 00:13:ef:66:18:49 WPA_PTK entering state INITPSK Searching a PSK for 00:13:ef:66:18:49 prev_psk=0x0 Searching a PSK for 00:13:ef:66:18:49 prev_psk=0x0 WPA: 00:13:ef:66:18:49 WPA_PTK entering state PTKSTART wlan0: STA 00:13:ef:66:18:49 WPA: sending 1/4 msg of 4-Way Handshake WPA: Send EAPOL(version=2 secure=0 mic=0 ack=1 install=0 pairwise=1 kde_len=0 keyidx=0 encr=0) WPA: Replay Counter - hexdump(len=8): 00 00 00 00 00 00 00 01 TX EAPOL - hexdump(len=99): 02 03 00 5f 02 00 8a 00 10 00 00 00 00 00 00 00 01 8a 5f 94 56 ac e3 d8 80 30 ae e6 fd ab ea 2f b8 fb ac 1e ce 89 b4 8f 7f d0 74 9a a2 32 d2 3a 9f 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 WPA: Use EAPOL-Key timeout of 1000 ms (retry counter 1) hostapd_new_assoc_sta: reschedule ap_handle_timer timeout for 00:13:ef:66:18:49 (300 seconds - ap_max_inactivity) wlan0: Event EAPOL_RX (24) received IEEE 802.1X: 121 bytes from 00:13:ef:66:18:49 IEEE 802.1X: version=1 type=3 length=117 WPA: Received EAPOL-Key from 00:13:ef:66:18:49 key_info=0x10a type=2 key_data_length=22 WPA: Received Key Nonce - hexdump(len=32): 9a 00 4b 91 0d 6d 86 0b 85 8d 05 ab 76 72 94 b2 8b ff 2b ee 7a b4 e9 db de af be 3f 17 99 ca c5 WPA: Received Replay Counter - hexdump(len=8): 00 00 00 00 00 00 00 01 wlan0: STA 00:13:ef:66:18:49 WPA: received EAPOL-Key frame (2/4 Pairwise) WPA: 00:13:ef:66:18:49 WPA_PTK entering state PTKCALCNEGOTIATING Searching a PSK for 00:13:ef:66:18:49 prev_psk=0x0 WPA: PTK derivation - A1=00:c6:d2:21:c9:34 A2=00:13:ef:66:18:49 WPA: Nonce1 - hexdump(len=32): 8a 5f 94 56 ac e3 d8 80 30 ae e6 fd ab ea 2f b8 fb ac 1e ce 89 b4 8f 7f d0 74 9a a2 32 d2 3a 9f WPA: Nonce2 - hexdump(len=32): 9a 00 4b 91 0d 6d 86 0b 85 8d 05 ab 76 72 94 b2 8b ff 2b ee 7a b4 e9 db de af be 3f 17 99 ca c5 WPA: PMK - hexdump(len=32): [REMOVED] WPA: PTK - hexdump(len=48): [REMOVED] WPA: KCK - hexdump(len=16): [REMOVED] WPA: KEK - hexdump(len=16): [REMOVED] WPA: TK - hexdump(len=16): [REMOVED] WPA: 00:13:ef:66:18:49 WPA_PTK entering state PTKCALCNEGOTIATING2 WPA: 00:13:ef:66:18:49 WPA_PTK entering state PTKINITNEGOTIATING bsd_get_seqnum: addr=00:00:00:00:00:00 idx=1 wlan0: STA 00:13:ef:66:18:49 WPA: sending 3/4 msg of 4-Way Handshake WPA: Send EAPOL(version=2 secure=1 mic=1 ack=1 install=1 pairwise=1 kde_len=46 keyidx=1 encr=1) WPA: Replay Counter - hexdump(len=8): 00 00 00 00 00 00 00 02 Plaintext EAPOL-Key Key Data - hexdump(len=56): [REMOVED] TX EAPOL - hexdump(len=155): 02 03 00 97 02 13 ca 00 10 00 00 00 00 00 00 00 02 8a 5f 94 56 ac e3 d8 80 30 ae e6 fd ab ea 2f b8 fb ac 1e ce 89 b4 8f 7f d0 74 9a a2 32 d2 3a 9f 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 93 9e 4e 4f 11 14 fd 90 c0 03 67 44 ef 3e 93 d3 00 38 d4 5a b4 e2 92 da 2f b6 9b be 78 99 f7 8a 80 65 f3 f0 7f bf 62 f5 1c 8c d0 af eb b6 e2 33 d1 8d b1 c1 c4 d9 d9 8b b2 f3 17 4f 3d 22 26 48 99 25 75 67 b6 96 4c 06 e5 ec WPA: Use EAPOL-Key timeout of 1000 ms (retry counter 1) wlan0: Event EAPOL_RX (24) received IEEE 802.1X: 99 bytes from 00:13:ef:66:18:49 IEEE 802.1X: version=1 type=3 length=95 WPA: Received EAPOL-Key from 00:13:ef:66:18:49 key_info=0x30a type=2 key_data_length=0 WPA: Received Key Nonce - hexdump(len=32): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 WPA: Received Replay Counter - hexdump(len=8): 00 00 00 00 00 00 00 02 wlan0: STA 00:13:ef:66:18:49 WPA: received EAPOL-Key frame (4/4 Pairwise) WPA: 00:13:ef:66:18:49 WPA_PTK entering state PTKINITDONE bsd_set_key: alg=3 addr=0x20847008 key_idx=0 set_tx=1 seq_len=0 key_len=16 wlan0: AP-STA-CONNECTED 00:13:ef:66:18:49 wlan0: STA 00:13:ef:66:18:49 IEEE 802.1X: authorizing port wlan0: STA 00:13:ef:66:18:49 RADIUS: starting accounting session 27FA1003-00000000 wlan0: STA 00:13:ef:66:18:49 WPA: pairwise key handshake completed (RSN) wlan0: Event ASSOC (0) received wlan0: STA 50:55:27:ff:dc:04 IEEE 802.11: associated STA included RSN IE in (Re)AssocReq New STA ap_sta_add: register ap_handle_timer timeout for 50:55:27:ff:dc:04 (300 seconds - ap_max_inactivity) wlan0: STA 50:55:27:ff:dc:04 WPA: event 1 notification bsd_set_key: alg=0 addr=0x20847208 key_idx=0 set_tx=1 seq_len=0 key_len=0 bsd_del_key: addr=50:55:27:ff:dc:04 IEEE 802.1X: Ignore STA - 802.1X not enabled or forced for WPS wlan0: STA 50:55:27:ff:dc:04 WPA: start authentication WPA: 50:55:27:ff:dc:04 WPA_PTK entering state INITIALIZE bsd_set_key: alg=0 addr=0x20847208 key_idx=0 set_tx=1 seq_len=0 key_len=0 bsd_del_key: addr=50:55:27:ff:dc:04 wlan0: STA 50:55:27:ff:dc:04 IEEE 802.1X: unauthorizing port WPA: 50:55:27:ff:dc:04 WPA_PTK_GROUP entering state IDLE WPA: 50:55:27:ff:dc:04 WPA_PTK entering state AUTHENTICATION WPA: 50:55:27:ff:dc:04 WPA_PTK entering state AUTHENTICATION2 Get randomness: len=32 entropy=2 WPA: Assign ANonce - hexdump(len=32): b5 18 65 7c 00 3b ef 61 e1 21 fc 93 f1 10 81 d5 2e 54 2c 24 d7 c2 24 07 b7 40 83 39 35 d9 ca 85 WPA: 50:55:27:ff:dc:04 WPA_PTK entering state INITPSK Searching a PSK for 50:55:27:ff:dc:04 prev_psk=0x0 Searching a PSK for 50:55:27:ff:dc:04 prev_psk=0x0 WPA: 50:55:27:ff:dc:04 WPA_PTK entering state PTKSTART wlan0: STA 50:55:27:ff:dc:04 WPA: sending 1/4 msg of 4-Way Handshake WPA: Send EAPOL(version=2 secure=0 mic=0 ack=1 install=0 pairwise=1 kde_len=0 keyidx=0 encr=0) WPA: Replay Counter - hexdump(len=8): 00 00 00 00 00 00 00 01 TX EAPOL - hexdump(len=99): 02 03 00 5f 02 00 8a 00 10 00 00 00 00 00 00 00 01 b5 18 65 7c 00 3b ef 61 e1 21 fc 93 f1 10 81 d5 2e 54 2c 24 d7 c2 24 07 b7 40 83 39 35 d9 ca 85 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 WPA: Use EAPOL-Key timeout of 1000 ms (retry counter 1) hostapd_new_assoc_sta: reschedule ap_handle_timer timeout for 50:55:27:ff:dc:04 (300 seconds - ap_max_inactivity) wlan0: Event EAPOL_RX (24) received IEEE 802.1X: 121 bytes from 50:55:27:ff:dc:04 IEEE 802.1X: version=1 type=3 length=117 WPA: Received EAPOL-Key from 50:55:27:ff:dc:04 key_info=0x10a type=2 key_data_length=22 WPA: Received Key Nonce - hexdump(len=32): 98 b8 fd 85 aa b9 9e 71 ed 30 bc a1 67 9a 7e 3f 08 10 16 3a a2 8a 68 e7 84 52 df 69 74 65 f4 cc WPA: Received Replay Counter - hexdump(len=8): 00 00 00 00 00 00 00 01 wlan0: STA 50:55:27:ff:dc:04 WPA: received EAPOL-Key frame (2/4 Pairwise) WPA: 50:55:27:ff:dc:04 WPA_PTK entering state PTKCALCNEGOTIATING Searching a PSK for 50:55:27:ff:dc:04 prev_psk=0x0 WPA: PTK derivation - A1=00:c6:d2:21:c9:34 A2=50:55:27:ff:dc:04 WPA: Nonce1 - hexdump(len=32): b5 18 65 7c 00 3b ef 61 e1 21 fc 93 f1 10 81 d5 2e 54 2c 24 d7 c2 24 07 b7 40 83 39 35 d9 ca 85 WPA: Nonce2 - hexdump(len=32): 98 b8 fd 85 aa b9 9e 71 ed 30 bc a1 67 9a 7e 3f 08 10 16 3a a2 8a 68 e7 84 52 df 69 74 65 f4 cc WPA: PMK - hexdump(len=32): [REMOVED] WPA: PTK - hexdump(len=48): [REMOVED] WPA: KCK - hexdump(len=16): [REMOVED] WPA: KEK - hexdump(len=16): [REMOVED] WPA: TK - hexdump(len=16): [REMOVED] WPA: 50:55:27:ff:dc:04 WPA_PTK entering state PTKCALCNEGOTIATING2 WPA: 50:55:27:ff:dc:04 WPA_PTK entering state PTKINITNEGOTIATING bsd_get_seqnum: addr=00:00:00:00:00:00 idx=1 wlan0: STA 50:55:27:ff:dc:04 WPA: sending 3/4 msg of 4-Way Handshake WPA: Send EAPOL(version=2 secure=1 mic=1 ack=1 install=1 pairwise=1 kde_len=46 keyidx=1 encr=1) WPA: Replay Counter - hexdump(len=8): 00 00 00 00 00 00 00 02 Plaintext EAPOL-Key Key Data - hexdump(len=56): [REMOVED] TX EAPOL - hexdump(len=155): 02 03 00 97 02 13 ca 00 10 00 00 00 00 00 00 00 02 b5 18 65 7c 00 3b ef 61 e1 21 fc 93 f1 10 81 d5 2e 54 2c 24 d7 c2 24 07 b7 40 83 39 35 d9 ca 85 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c4 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0 9f 82 19 14 e2 41 db 78 34 4d 67 73 0f 2d 98 00 38 36 24 6d a8 10 de 8c ce a9 6d f0 70 32 52 d9 e3 39 c4 a7 8e 5f de 51 7c 41 b0 37 6f e9 a7 14 be 1c 74 d4 06 e0 2d f9 b0 f2 09 86 cd 6c 79 57 24 fb 68 8b 61 46 20 ef a8 WPA: Use EAPOL-Key timeout of 1000 ms (retry counter 1) wlan0: Event EAPOL_RX (24) received IEEE 802.1X: 99 bytes from 50:55:27:ff:dc:04 IEEE 802.1X: version=1 type=3 length=95 WPA: Received EAPOL-Key from 50:55:27:ff:dc:04 key_info=0x30a type=2 key_data_length=0 WPA: Received Key Nonce - hexdump(len=32): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 WPA: Received Replay Counter - hexdump(len=8): 00 00 00 00 00 00 00 02 wlan0: STA 50:55:27:ff:dc:04 WPA: received EAPOL-Key frame (4/4 Pairwise) WPA: 50:55:27:ff:dc:04 WPA_PTK entering state PTKINITDONE bsd_set_key: alg=3 addr=0x20847208 key_idx=0 set_tx=1 seq_len=0 key_len=16 wlan0: AP-STA-CONNECTED 50:55:27:ff:dc:04 wlan0: STA 50:55:27:ff:dc:04 IEEE 802.1X: authorizing port wlan0: STA 50:55:27:ff:dc:04 RADIUS: starting accounting session 27FA1003-00000001 wlan0: STA 50:55:27:ff:dc:04 WPA: pairwise key handshake completed (RSN) ap_handle_timer: 00:13:ef:66:18:49 flags=0x23 timeout_next=0 wlan0: Station 00:13:ef:66:18:49 has been active 0s ago ap_handle_timer: register ap_handle_timer timeout for 00:13:ef:66:18:49 (311 seconds) wlan0: Event DISASSOC (1) received wlan0: STA 50:55:27:ff:dc:04 IEEE 802.11: disassociated wlan0: AP-STA-DISCONNECTED 50:55:27:ff:dc:04 wlan0: STA 50:55:27:ff:dc:04 WPA: event 2 notification bsd_set_key: alg=0 addr=0x20847208 key_idx=0 set_tx=1 seq_len=0 key_len=0 bsd_del_key: addr=50:55:27:ff:dc:04 ioctl[SIOCS80211, op=20, val=0, arg_len=7]: No such file or directory WPA: 50:55:27:ff:dc:04 WPA_PTK entering state DISCONNECTED WPA: 50:55:27:ff:dc:04 WPA_PTK entering state INITIALIZE bsd_set_key: alg=0 addr=0x20847208 key_idx=0 set_tx=1 seq_len=0 key_len=0 bsd_del_key: addr=50:55:27:ff:dc:04 ioctl[SIOCS80211, op=20, val=0, arg_len=7]: No such file or directory ioctl[SIOCS80211, op=21, val=0, arg_len=42]: No such file or directory wlan0: STA 50:55:27:ff:dc:04 IEEE 802.1X: unauthorizing port ap_free_sta: cancel ap_handle_timer for 50:55:27:ff:dc:04 wlan0: WPA rekeying GTK WPA: group state machine entering state SETKEYS (VLAN-ID 0) Get randomness: len=16 entropy=1 GTK - hexdump(len=16): [REMOVED] WPA: 00:13:ef:66:18:49 WPA_PTK_GROUP entering state REKEYNEGOTIATING wlan0: STA 00:13:ef:66:18:49 WPA: sending 1/2 msg of Group Key Handshake WPA: Send EAPOL(version=2 secure=1 mic=1 ack=1 install=0 pairwise=0 kde_len=24 keyidx=2 encr=1) WPA: Replay Counter - hexdump(len=8): 00 00 00 00 00 00 00 03 Plaintext EAPOL-Key Key Data - hexdump(len=32): [REMOVED] TX EAPOL - hexdump(len=131): 02 03 00 7f 02 13 82 00 10 00 00 00 00 00 00 00 03 33 ad e3 a9 95 d4 6b 93 4d df bd 96 90 a5 3f fe 58 7f 01 3e 53 1f 8e 23 3d c0 ef 35 a2 f4 5a df 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 af dd 11 ab e2 ed 9a a2 17 db 92 63 8a 84 6e 42 00 20 91 7f ca 02 21 28 c9 0d 9f 00 c4 09 da e8 73 88 07 0c 8d 5c 5b 30 64 b7 dd 02 35 a2 37 a1 63 e9 WPA: Use EAPOL-Key timeout of 1000 ms (retry counter 1) wpa_group_setkeys: GKeyDoneStations=1 wlan0: STA 00:13:ef:66:18:49 WPA: EAPOL-Key timeout WPA: 00:13:ef:66:18:49 WPA_PTK_GROUP entering state REKEYNEGOTIATING wlan0: STA 00:13:ef:66:18:49 WPA: sending 1/2 msg of Group Key Handshake WPA: Send EAPOL(version=2 secure=1 mic=1 ack=1 install=0 pairwise=0 kde_len=24 keyidx=2 encr=1) WPA: Replay Counter - hexdump(len=8): 00 00 00 00 00 00 00 04 Plaintext EAPOL-Key Key Data - hexdump(len=32): [REMOVED] TX EAPOL - hexdump(len=131): 02 03 00 7f 02 13 82 00 10 00 00 00 00 00 00 00 04 33 ad e3 a9 95 d4 6b 93 4d df bd 96 90 a5 3f fe 58 7f 01 3e 53 1f 8e 23 3d c0 ef 35 a2 f4 5a df 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 46 e1 ab 2c 2a 89 e4 5c cc 9a 7a f4 2f 17 c6 ce 00 20 91 7f ca 02 21 28 c9 0d 9f 00 c4 09 da e8 73 88 07 0c 8d 5c 5b 30 64 b7 dd 02 35 a2 37 a1 63 e9 WPA: Use EAPOL-Key timeout of 1000 ms (retry counter 2) wlan0: STA 00:13:ef:66:18:49 WPA: EAPOL-Key timeout WPA: 00:13:ef:66:18:49 WPA_PTK_GROUP entering state REKEYNEGOTIATING wlan0: STA 00:13:ef:66:18:49 WPA: sending 1/2 msg of Group Key Handshake WPA: Send EAPOL(version=2 secure=1 mic=1 ack=1 install=0 pairwise=0 kde_len=24 keyidx=2 encr=1) WPA: Replay Counter - hexdump(len=8): 00 00 00 00 00 00 00 05 Plaintext EAPOL-Key Key Data - hexdump(len=32): [REMOVED] TX EAPOL - hexdump(len=131): 02 03 00 7f 02 13 82 00 10 00 00 00 00 00 00 00 05 33 ad e3 a9 95 d4 6b 93 4d df bd 96 90 a5 3f fe 58 7f 01 3e 53 1f 8e 23 3d c0 ef 35 a2 f4 5a df 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b7 5d e8 3f 6b bf 64 aa e2 59 b4 0a 1b a7 82 06 00 20 91 7f ca 02 21 28 c9 0d 9f 00 c4 09 da e8 73 88 07 0c 8d 5c 5b 30 64 b7 dd 02 35 a2 37 a1 63 e9 WPA: Use EAPOL-Key timeout of 1000 ms (retry counter 3) wlan0: STA 00:13:ef:66:18:49 WPA: EAPOL-Key timeout WPA: 00:13:ef:66:18:49 WPA_PTK_GROUP entering state REKEYNEGOTIATING wlan0: STA 00:13:ef:66:18:49 WPA: sending 1/2 msg of Group Key Handshake WPA: Send EAPOL(version=2 secure=1 mic=1 ack=1 install=0 pairwise=0 kde_len=24 keyidx=2 encr=1) WPA: Replay Counter - hexdump(len=8): 00 00 00 00 00 00 00 06 Plaintext EAPOL-Key Key Data - hexdump(len=32): [REMOVED] TX EAPOL - hexdump(len=131): 02 03 00 7f 02 13 82 00 10 00 00 00 00 00 00 00 06 33 ad e3 a9 95 d4 6b 93 4d df bd 96 90 a5 3f fe 58 7f 01 3e 53 1f 8e 23 3d c0 ef 35 a2 f4 5a df 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 6c 5b f0 e9 64 c8 48 f9 98 3b f8 bc df 84 ad 99 00 20 91 7f ca 02 21 28 c9 0d 9f 00 c4 09 da e8 73 88 07 0c 8d 5c 5b 30 64 b7 dd 02 35 a2 37 a1 63 e9 WPA: Use EAPOL-Key timeout of 1000 ms (retry counter 4) wlan0: STA 00:13:ef:66:18:49 WPA: EAPOL-Key timeout WPA: 00:13:ef:66:18:49 WPA_PTK_GROUP entering state REKEYNEGOTIATING WPA: 00:13:ef:66:18:49 WPA_PTK_GROUP entering state KEYERROR WPA: group state machine entering state SETKEYSDONE (VLAN-ID 0) bsd_set_key: alg=3 addr=0x80be3 key_idx=2 set_tx=1 seq_len=0 key_len=16 wlan0: STA 00:13:ef:66:18:49 WPA: WPA_PTK: sm->Disconnect WPA: 00:13:ef:66:18:49 WPA_PTK entering state DISCONNECT wpa_sta_disconnect STA 00:13:ef:66:18:49 hostapd_wpa_auth_disconnect: WPA authenticator requests disconnect: STA 00:13:ef:66:18:49 reason 2 wlan0: AP-STA-DISCONNECTED 00:13:ef:66:18:49 wlan0: STA 00:13:ef:66:18:49 WPA: event 3 notification bsd_set_key: alg=0 addr=0x20847008 key_idx=0 set_tx=1 seq_len=0 key_len=0 bsd_del_key: addr=00:13:ef:66:18:49 ioctl[SIOCS80211, op=20, val=0, arg_len=7]: No such file or directory ap_sta_disconnect: reschedule ap_handle_timer timeout for 00:13:ef:66:18:49 (5 seconds - AP_MAX_INACTIVITY_AFTER_DEAUTH) WPA: 00:13:ef:66:18:49 WPA_PTK_GROUP entering state IDLE WPA: 00:13:ef:66:18:49 WPA_PTK entering state DISCONNECTED WPA: 00:13:ef:66:18:49 WPA_PTK entering state INITIALIZE bsd_set_key: alg=0 addr=0x20847008 key_idx=0 set_tx=1 seq_len=0 key_len=0 bsd_del_key: addr=00:13:ef:66:18:49 ioctl[SIOCS80211, op=20, val=0, arg_len=7]: No such file or directory ioctl[SIOCS80211, op=21, val=0, arg_len=42]: No such file or directory wlan0: STA 00:13:ef:66:18:49 IEEE 802.1X: unauthorizing port Removing STA 00:13:ef:66:18:49 from kernel driver wlan0: STA 00:13:ef:66:18:49 MLME: MLME-DEAUTHENTICATE.indication(00:13:ef:66:18:49, 2) wlan0: STA 00:13:ef:66:18:49 MLME: MLME-DELETEKEYS.request(00:13:ef:66:18:49) bsd_set_key: alg=0 addr=0x20847008 key_idx=0 set_tx=1 seq_len=0 key_len=0 bsd_del_key: addr=00:13:ef:66:18:49 ioctl[SIOCS80211, op=20, val=0, arg_len=7]: No such file or directory wlan0: Event DISASSOC (1) received wlan0: STA 00:13:ef:66:18:49 IEEE 802.11: disassociated wlan0: STA 00:13:ef:66:18:49 WPA: event 2 notification bsd_set_key: alg=0 addr=0x20847008 key_idx=0 set_tx=1 seq_len=0 key_len=0 bsd_del_key: addr=00:13:ef:66:18:49 ioctl[SIOCS80211, op=20, val=0, arg_len=7]: No such file or directory WPA: 00:13:ef:66:18:49 WPA_PTK entering state DISCONNECTED WPA: 00:13:ef:66:18:49 WPA_PTK entering state INITIALIZE bsd_set_key: alg=0 addr=0x20847008 key_idx=0 set_tx=1 seq_len=0 key_len=0 bsd_del_key: addr=00:13:ef:66:18:49 ioctl[SIOCS80211, op=20, val=0, arg_len=7]: No such file or directory ioctl[SIOCS80211, op=21, val=0, arg_len=42]: No such file or directory wlan0: STA 00:13:ef:66:18:49 IEEE 802.1X: unauthorizing port ap_free_sta: cancel ap_handle_timer for 00:13:ef:66:18:49 thanks, peter From owner-freebsd-arm@freebsd.org Thu Oct 6 16:10:15 2016 Return-Path: Delivered-To: freebsd-arm@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 100EABE9B74 for ; Thu, 6 Oct 2016 16:10:15 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.blih.net", Issuer "mail.blih.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 95D1CA84 for ; Thu, 6 Oct 2016 16:10:13 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) by mail.blih.net (OpenSMTPD) with ESMTP id 50db4203; Thu, 6 Oct 2016 18:10:05 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; s=mail; bh=g5GQK15lN8IyjW9fnQxlP0UWTZ8=; b=smY5IogyWeno5rn7HY39OezEKEQl aIaHrQfm6t2qCIwjw9FsV4d05GtJg96oCcNyIrxmxxMtM09V8IwQhU+MwxaaO+8J hpz0UIF1ZW1aArAbbGpK6Lg0Rp0I/RR/CNnmXNKASz0TVz/ji1Vx1JimTSR7g6S8 xtZsk6BLoUwdCC8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; q=dns; s= mail; b=K0bWy4d7ZwvfEMh8rmhIhLGTg1wTp5Zerd6j6wF2ATswiDfJ+m/+zhwV H1QeFGzIHv0xpRMAzl1dq2nWkmy6iGMBAcinmdacTXRxfHzIcwSOIliR4Qt7/9ou +0hYfNNLmsKXRSxfv3Y/phqnBPzmapWO36v4uig9vwF0c6MTrhc= Received: from knuckles.blih.net (ip-54.net-82-216-203.roubaix.rev.numericable.fr [82.216.203.54]) by mail.blih.net (OpenSMTPD) with ESMTPSA id 734c9bbf TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Thu, 6 Oct 2016 18:10:00 +0200 (CEST) Date: Thu, 6 Oct 2016 18:10:00 +0200 From: Emmanuel Vadot To: Warner Losh Cc: Da Rock , "freebsd-arm@freebsd.org" Subject: Re: u-boot efi option Message-Id: <20161006181000.b52d8a27d32dd25c31853948@bidouilliste.com> In-Reply-To: References: <36160c78-9095-f716-8041-3eb7656642af@herveybayaustralia.com.au> <20161002123700.662f2868688b4b32465395aa@bidouilliste.com> <20161003103247.78ff7596607755ce0f204648@bidouilliste.com> <20161003122309.6ab5f4b3c94c33355b682ade@bidouilliste.com> X-Mailer: Sylpheed 3.5.1 (GTK+ 2.24.29; amd64-portbld-freebsd12.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Oct 2016 16:10:15 -0000 Good news, everyone! I've just tested without alignment and it works. What doesn't work is taking the snapshot or release image and doing EFI with it. I did nothing special when creating the sd card : gpart create -s mbr da0 gpart add -t fat16 -s 50m -a 1m da0 gpart show da0 gpart add -t freebsd da0 gpart create -s bsd da0s2 gpart add -t freebsd-ufs da0s2 newfs /dev/da0s2a newfs_msdos -F16 /dev/da0s1 Now that I know everything works I'll look at the release scripts to see how to adapt them for EFI. On Mon, 3 Oct 2016 07:55:37 -0600 Warner Losh wrote: > Sounds like we should target 12 to be EFI only then, or at least EFI > preferred with our infrastructure setup to cope. > > Why is there a 512k alignment requirement? Or is that just the typical > 512k at the start of the disk is needed for uboot issue? > > Warner > > On Mon, Oct 3, 2016 at 4:23 AM, Emmanuel Vadot wrote: > > On Mon, 3 Oct 2016 19:01:30 +1000 > > Da Rock wrote: > > > >> A few points that I'd like clarification on: > >> > >> 1. I'm not having much success on rpi3 with any images, but I'm working > >> on my own 64bit anyway. I'm also trying to get a handle on what the > >> process of running the system on the rpi3 actually is as well. Fun... :) > >> So the 512kb alignment, why is that an issue? Perhaps I'm a little > >> foggy, but isn't that simply a case of partitioning correctly? > > > > I don't know exactly to be honest, I have to read a lot of code. > > > >> 2. I should have mentioned this initially (which is why I was checking > >> efi status to see if I was banging on for no reason), but I'm having > >> trouble (still) compiling u-boot version that has the efi capability > >> (2016.09) - can't find . I've tried with clang (x18 error) > >> and gcc to no avail. I tried leveraging ports, but it is not exactly > >> cooperating either (I'll have to try some more diags on that). Anyone > >> have a clue on how to get past this? -I doesn't work, or linking to > >> /usr/local/include. > > > > - Install {arm,aarch64}-none-{eabi,elf}-{gcc,binutils} > > - cd uboot-src > > - gmake ARCH={arm,arm64} CROSS_COMPILE={arm,aarch64}-none-{eabi,elf}- > > XXX_defconfig > > - gmake ARCH={arm,arm64} CROSS_COMPILE={arm,aarch64}-none-{eabi,elf}- > > > > I've never tried with clang. > > > >> 3. My other query was on the EFI boot process on arm. As I understood, > >> the u-boot is equivalent to boot0? So that means boot1 should then be in > >> the fat partition? Is that what you mean by /efi/boot/bootarm.efi? Or > >> doesn't it need to be? > > > > U-Boot can be seen as BIOS/boot0 combined. > > Yes boot1.efi MUST be on the fat partition and by default an EFI > > firmware will load /efi/boot/boot${ARCH}.efi > > > >> Apologies if I sound like a complete goose, but I'm still new to all > >> things arm yet - but learning fast :) > > > > Don't worry, this motivate me more to do a page on the wiki about UEFI > > on arm :) > > > >> On 03/10/2016 18:32, Emmanuel Vadot wrote: > >> > I've never had any problem with it (I know it doesn't really answer to > >> > your question). > >> > SuSe have switch to EFI (the main developer for U-Boot > >> > EFI is from SuSe), OpenBSD too. > >> > > >> > The main problem right now for people to test is that the partition > >> > on the arm images that we provide aren't aligned for it to work. > >> > > >> > I either need to fix the bug for non 512kb-aligned partition or > >> > aligned them in the release scripts. > >> > > >> > Also I don't know which ports-tree re@ is using for snapshots. I think > >> > that they use the latest quarterly for release and stable. > >> > So we have to be carefull when we will switch the ports to UEFI. > >> > > >> > In the meantime don't hesitate to test with my patch. > >> > > >> > If you have the correct dtb in /dtb/ on the msdos part U-Boot will load > >> > it. > >> > For booting automatically just put boot1.efi as /efi/boot/bootarm.efi > >> > > >> > On Sun, 2 Oct 2016 16:06:37 -0600 > >> > Warner Losh wrote: > >> > > >> >> How long do you think until this is mature enough we can cut over to it? > >> >> There's issues with ubldr on newer u-boot version on some of the platforms > >> >> we support. If we could cut over to this, that would be great. > >> >> > >> >> Warner > >> >> > >> >> On Sun, Oct 2, 2016 at 4:37 AM, Emmanuel Vadot wrote: > >> >>> Hello, > >> >>> > >> >>> I've commited every needed change on our side, for uboot side you will > >> >>> need this patch : > >> >>> https://people.freebsd.org/~manu/u-boot_201609_efi.diff > >> >>> > >> >>> The only drawback is that you will need to have your partition aligned > >> >>> on 512kb boundaries on the mmc. > >> >>> > >> >>> I've successfully booted my beaglebone black and most of my Allwinner > >> >>> boards with UEFI. > >> >>> > >> >>> Some part of the uboot patch have started to be upstreamed, for > >> >>> the others I need to rework on some part before I upstream them. > >> >>> > >> >>> Cheers, > >> >>> > >> >>> On Sun, 2 Oct 2016 19:56:54 +1000 > >> >>> Da Rock wrote: > >> >>> > >> >>>> Has anyone tried this option yet? I've heard someone got it going for > >> >>>> slack, but I thought it sounded like it might make it easier for running > >> >>>> freebsd. > >> >>>> > >> >>>> I'm currently trying to build a more current u-boot to test it. > >> >>>> > >> >>>> _______________________________________________ > >> >>>> freebsd-arm@freebsd.org mailing list > >> >>>> https://lists.freebsd.org/mailman/listinfo/freebsd-arm > >> >>>> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" > >> >>> > >> >>> -- > >> >>> Emmanuel Vadot > >> >>> _______________________________________________ > >> >>> freebsd-arm@freebsd.org mailing list > >> >>> https://lists.freebsd.org/mailman/listinfo/freebsd-arm > >> >>> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" > >> > > > > > > > -- > > Emmanuel Vadot -- Emmanuel Vadot From owner-freebsd-arm@freebsd.org Thu Oct 6 17:53:47 2016 Return-Path: Delivered-To: freebsd-arm@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 6B23EBEC1E5 for ; Thu, 6 Oct 2016 17:53:47 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x242.google.com (mail-it0-x242.google.com [IPv6:2607:f8b0:4001:c0b::242]) (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 30A41D3D for ; Thu, 6 Oct 2016 17:53:47 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x242.google.com with SMTP id l13so2179083itl.2 for ; Thu, 06 Oct 2016 10:53:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=VXbTyl6uw+lNFOmin1DaZL/Cdrfx8l4rKnTjg+0KbEY=; b=cwRkJjnWe2+wsVxeXgt1b20Zqt//WixNGXZMFQH8JOhuol44L5MqdMA1X1djjPctP+ q966rQcvLhpY1DhyZtAf7JKXJqXF1U97oCz7wZbOJ8LrPUOyIAOaZYoy0bXlIOk3SOsK 1Fzz71aHTjQDPrKx15qV7FMCGAhdQI5xTLwygvE1JFctlPeoiKI4REZ8oYFmQnhSHZWT RLNmfIqkihKdewnQUC8aOxhjC+D03uVuKJUkvqseN8T6TA4cJ1jC58ULDAletHEoOmwQ zzExRunzK1CNja10VTKrwNNYXfX55PzMAdr+tRKUzHf0vJd0pIgNXx0iavO0J9wK6jcD lUrw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=VXbTyl6uw+lNFOmin1DaZL/Cdrfx8l4rKnTjg+0KbEY=; b=MnVmhy7YsCCmoV3XjFkXVPtyxpyVXNHD9hVGFKGXIeMz6MOVevWSVYjFo/cYgINUNZ KJcamXZpMKT/R4m/tFrMT5FuqbVdCl6NKVT/khIf0su5Z2B4eoyeFyw+7MnpgB0ArC4l u1HeLEbflm9pPxN8eDXrejqZeYMmsC3GNl4dtmZVKGlgIj8uToQGmcglX0OI9C08Xrzn yubR955b5B1hEU7g6VFBe4STE3VNqh7KVmFqseDb6dJZ9jBmpi57sHijhgTCNTpxT5uP m9ugSj/R2kFMsEegItjAV2Ptjio7jSlXYhwHtQkbLYn/2kRa11nGALyDKDMtAShvz+3t NadA== X-Gm-Message-State: AA6/9RncmJ/rnmuZvxJ6zy5dqk2BdyFvTWdiicwhgh7QB84yVVahtPjQdtqBJVxUZHsLcN5xql5BElf1Sf8clw== X-Received: by 10.36.43.82 with SMTP id h79mr17277377ita.60.1475776426599; Thu, 06 Oct 2016 10:53:46 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.95.199 with HTTP; Thu, 6 Oct 2016 10:53:45 -0700 (PDT) X-Originating-IP: [69.53.245.200] In-Reply-To: <20161006181000.b52d8a27d32dd25c31853948@bidouilliste.com> References: <36160c78-9095-f716-8041-3eb7656642af@herveybayaustralia.com.au> <20161002123700.662f2868688b4b32465395aa@bidouilliste.com> <20161003103247.78ff7596607755ce0f204648@bidouilliste.com> <20161003122309.6ab5f4b3c94c33355b682ade@bidouilliste.com> <20161006181000.b52d8a27d32dd25c31853948@bidouilliste.com> From: Warner Losh Date: Thu, 6 Oct 2016 11:53:45 -0600 X-Google-Sender-Auth: W9cbpUJXJeAr3p_cw3W3l9f6jtw Message-ID: Subject: Re: u-boot efi option To: Emmanuel Vadot Cc: Da Rock , "freebsd-arm@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Oct 2016 17:53:47 -0000 I'd really like to merge the release and nanobsd (and crochet if they want to use it) building methods if at all possible. Warner On Thu, Oct 6, 2016 at 10:10 AM, Emmanuel Vadot wrote: > > Good news, everyone! > > I've just tested without alignment and it works. > What doesn't work is taking the snapshot or release image and doing > EFI with it. > I did nothing special when creating the sd card : > > gpart create -s mbr da0 > gpart add -t fat16 -s 50m -a 1m da0 > gpart show da0 > gpart add -t freebsd da0 > gpart create -s bsd da0s2 > gpart add -t freebsd-ufs da0s2 > newfs /dev/da0s2a > newfs_msdos -F16 /dev/da0s1 > > Now that I know everything works I'll look at the release scripts to > see how to adapt them for EFI. > > On Mon, 3 Oct 2016 07:55:37 -0600 > Warner Losh wrote: > >> Sounds like we should target 12 to be EFI only then, or at least EFI >> preferred with our infrastructure setup to cope. >> >> Why is there a 512k alignment requirement? Or is that just the typical >> 512k at the start of the disk is needed for uboot issue? >> >> Warner >> >> On Mon, Oct 3, 2016 at 4:23 AM, Emmanuel Vadot wrote: >> > On Mon, 3 Oct 2016 19:01:30 +1000 >> > Da Rock wrote: >> > >> >> A few points that I'd like clarification on: >> >> >> >> 1. I'm not having much success on rpi3 with any images, but I'm working >> >> on my own 64bit anyway. I'm also trying to get a handle on what the >> >> process of running the system on the rpi3 actually is as well. Fun... :) >> >> So the 512kb alignment, why is that an issue? Perhaps I'm a little >> >> foggy, but isn't that simply a case of partitioning correctly? >> > >> > I don't know exactly to be honest, I have to read a lot of code. >> > >> >> 2. I should have mentioned this initially (which is why I was checking >> >> efi status to see if I was banging on for no reason), but I'm having >> >> trouble (still) compiling u-boot version that has the efi capability >> >> (2016.09) - can't find . I've tried with clang (x18 error) >> >> and gcc to no avail. I tried leveraging ports, but it is not exactly >> >> cooperating either (I'll have to try some more diags on that). Anyone >> >> have a clue on how to get past this? -I doesn't work, or linking to >> >> /usr/local/include. >> > >> > - Install {arm,aarch64}-none-{eabi,elf}-{gcc,binutils} >> > - cd uboot-src >> > - gmake ARCH={arm,arm64} CROSS_COMPILE={arm,aarch64}-none-{eabi,elf}- >> > XXX_defconfig >> > - gmake ARCH={arm,arm64} CROSS_COMPILE={arm,aarch64}-none-{eabi,elf}- >> > >> > I've never tried with clang. >> > >> >> 3. My other query was on the EFI boot process on arm. As I understood, >> >> the u-boot is equivalent to boot0? So that means boot1 should then be in >> >> the fat partition? Is that what you mean by /efi/boot/bootarm.efi? Or >> >> doesn't it need to be? >> > >> > U-Boot can be seen as BIOS/boot0 combined. >> > Yes boot1.efi MUST be on the fat partition and by default an EFI >> > firmware will load /efi/boot/boot${ARCH}.efi >> > >> >> Apologies if I sound like a complete goose, but I'm still new to all >> >> things arm yet - but learning fast :) >> > >> > Don't worry, this motivate me more to do a page on the wiki about UEFI >> > on arm :) >> > >> >> On 03/10/2016 18:32, Emmanuel Vadot wrote: >> >> > I've never had any problem with it (I know it doesn't really answer to >> >> > your question). >> >> > SuSe have switch to EFI (the main developer for U-Boot >> >> > EFI is from SuSe), OpenBSD too. >> >> > >> >> > The main problem right now for people to test is that the partition >> >> > on the arm images that we provide aren't aligned for it to work. >> >> > >> >> > I either need to fix the bug for non 512kb-aligned partition or >> >> > aligned them in the release scripts. >> >> > >> >> > Also I don't know which ports-tree re@ is using for snapshots. I think >> >> > that they use the latest quarterly for release and stable. >> >> > So we have to be carefull when we will switch the ports to UEFI. >> >> > >> >> > In the meantime don't hesitate to test with my patch. >> >> > >> >> > If you have the correct dtb in /dtb/ on the msdos part U-Boot will load >> >> > it. >> >> > For booting automatically just put boot1.efi as /efi/boot/bootarm.efi >> >> > >> >> > On Sun, 2 Oct 2016 16:06:37 -0600 >> >> > Warner Losh wrote: >> >> > >> >> >> How long do you think until this is mature enough we can cut over to it? >> >> >> There's issues with ubldr on newer u-boot version on some of the platforms >> >> >> we support. If we could cut over to this, that would be great. >> >> >> >> >> >> Warner >> >> >> >> >> >> On Sun, Oct 2, 2016 at 4:37 AM, Emmanuel Vadot wrote: >> >> >>> Hello, >> >> >>> >> >> >>> I've commited every needed change on our side, for uboot side you will >> >> >>> need this patch : >> >> >>> https://people.freebsd.org/~manu/u-boot_201609_efi.diff >> >> >>> >> >> >>> The only drawback is that you will need to have your partition aligned >> >> >>> on 512kb boundaries on the mmc. >> >> >>> >> >> >>> I've successfully booted my beaglebone black and most of my Allwinner >> >> >>> boards with UEFI. >> >> >>> >> >> >>> Some part of the uboot patch have started to be upstreamed, for >> >> >>> the others I need to rework on some part before I upstream them. >> >> >>> >> >> >>> Cheers, >> >> >>> >> >> >>> On Sun, 2 Oct 2016 19:56:54 +1000 >> >> >>> Da Rock wrote: >> >> >>> >> >> >>>> Has anyone tried this option yet? I've heard someone got it going for >> >> >>>> slack, but I thought it sounded like it might make it easier for running >> >> >>>> freebsd. >> >> >>>> >> >> >>>> I'm currently trying to build a more current u-boot to test it. >> >> >>>> >> >> >>>> _______________________________________________ >> >> >>>> freebsd-arm@freebsd.org mailing list >> >> >>>> https://lists.freebsd.org/mailman/listinfo/freebsd-arm >> >> >>>> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" >> >> >>> >> >> >>> -- >> >> >>> Emmanuel Vadot >> >> >>> _______________________________________________ >> >> >>> freebsd-arm@freebsd.org mailing list >> >> >>> https://lists.freebsd.org/mailman/listinfo/freebsd-arm >> >> >>> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" >> >> > >> > >> > >> > -- >> > Emmanuel Vadot > > > -- > Emmanuel Vadot From owner-freebsd-arm@freebsd.org Fri Oct 7 20:37:03 2016 Return-Path: Delivered-To: freebsd-arm@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 16FC9BED52B; Fri, 7 Oct 2016 20:37:03 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-io0-x233.google.com (mail-io0-x233.google.com [IPv6:2607:f8b0:4001:c06::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 E741AA66; Fri, 7 Oct 2016 20:37:02 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-io0-x233.google.com with SMTP id j37so58769366ioo.3; Fri, 07 Oct 2016 13:37:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=7X8mpQ+mv9yBH8TNRouWfVp2FTG8cZgIBTQ5dW18PzQ=; b=TpDVsV+++60kSbMZhyAIdwpiKIcBzi6zPoQxt1fEZYD+erQCW3l7nfOt1L43tUYx5N UdUQOw779Eop7ef2ip4k0ZOE5G2JTQa5i9gqvLsqCHP9mQj5O3Do0aiMnSkOh5/vCaUp P9vIu1Z0zeqsuUFxDbDZTGCYoBfyZ8yFJ8/RZQbDhd4+mMA/VBZ6Q+S4SSxdrGp7Szwh OyJ+tHiPzbY71FsneYmZYbJnFB4FrKPL8uOUdTrvhfsXZhaxyoSTVLptHICnyz/+CmS4 pIYiYXnse1sYgOdvCDlrtbgSlU++E0Gz5Kj0z+8j2HVggA0rF4SpJY5rTsrsKFGhr5bl G3Hw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=7X8mpQ+mv9yBH8TNRouWfVp2FTG8cZgIBTQ5dW18PzQ=; b=i3k1T8w5xvXbGFP/+44PCVFOVcAo2w5AP+hmWIFQyXfDPfN1AfsnbxriKsEpw3nz4z 0V5W5TFbArHpT4HsEtRcUwU+tABdknBWcm5E/udHAxazrXM6WoqXUkoTs6KuSM+bYgjP exB6F7/3HMiPGx2/D9FsXSguCQjBewSxGNKaBP90bgjgGMSHqHArkcFxB1+FJnyhj51d wAKWXBWf7dCOrnZZcpQuyV+GBr688qtTSiGs6SKUX6V05J+4RkczVO/7vaMAhRz/qgnV /TCFy5W3/VWT6aCJb/ejh1uFcn2Prtvp2Y/kUX2GCIAogEy5/VMx/nW0hq4CXOQEsawK IIhQ== X-Gm-Message-State: AA6/9RkL+d/qGTWZUopvH/jPAlgb/7Odn0BRRiTCIbRo9W/tNza3jGugVK+ievnx2pnqhQLWU2sBiJow3CD2wA== X-Received: by 10.107.181.211 with SMTP id e202mr21373797iof.99.1475872571184; Fri, 07 Oct 2016 13:36:11 -0700 (PDT) MIME-Version: 1.0 Sender: adrian.chadd@gmail.com Received: by 10.36.141.129 with HTTP; Fri, 7 Oct 2016 13:36:09 -0700 (PDT) In-Reply-To: References: From: Adrian Chadd Date: Fri, 7 Oct 2016 13:36:09 -0700 X-Google-Sender-Auth: oVtOM_NbgbFnqaTIy7vx-Zc3HPk Message-ID: Subject: Re: RPI2 AP To: peter garshtja Cc: "freebsd-arm@freebsd.org" , "freebsd-wireless@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Oct 2016 20:37:03 -0000 + freebsd-wireless can you post a 'dmesg' output? That way we can see which urtwn NIC it is and whether it logged anything. -a On 3 October 2016 at 11:38, peter garshtja wrote: > Greetings, > > im running freebsd 11 on rpi2 where i configured urtwn(wifi dongle) and > ether interfaces to work in bridge mode. > I built an AP and im experiencing weird issue - all stations that are > connected to AP after a while start loosing the connection and are not able > to reconnect anymore and only rebooting the rpi2 solves the issue. > > here is my hostapd.conf > > interface=wlan0 > ctrl_interface=/var/run/hostapd > ctrl_interface_group=wheel > ssid=testap > wpa=2 > wpa_psk_file=/etc/hostapd.wpa_psk > wpa_key_mgmt=WPA-PSK > wpa_pairwise=CCMP > > also here is hostapd logs running in debug mode > > Configuration file: /etc/hostapd.conf > ctrl_interface_group=0 (from group name 'wheel') > BSS count 1, BSSID mask 00:00:00:00:00:00 (0 bits) > Completing interface initialization > hostapd_setup_bss(hapd=0x20863000 (wlan0), first=1) > wlan0: Flushing old station entries > wlan0: Deauthenticate all stations > bsd_set_privacy: enabled=0 > bsd_set_key: alg=0 addr=0x0 key_idx=0 set_tx=0 seq_len=0 key_len=0 > bsd_del_key: key_idx=0 > bsd_set_key: alg=0 addr=0x0 key_idx=1 set_tx=0 seq_len=0 key_len=0 > bsd_del_key: key_idx=1 > bsd_set_key: alg=0 addr=0x0 key_idx=2 set_tx=0 seq_len=0 key_len=0 > bsd_del_key: key_idx=2 > bsd_set_key: alg=0 addr=0x0 key_idx=3 set_tx=0 seq_len=0 key_len=0 > bsd_del_key: key_idx=3 > Using interface wlan0 with hwaddr 00:c6:d2:21:c9:34 and ssid "testap" > bsd_set_ieee8021x: enabled=1 > bsd_configure_wpa: enable WPA= 0x2 > Get randomness: len=32 entropy=0 > GMK - hexdump(len=32): [REMOVED] > Get randomness: len=32 entropy=0 > Key Counter - hexdump(len=32): [REMOVED] > WPA: Delay group state machine start until Beacon frames have been > configured > bsd_set_privacy: enabled=1 > bsd_set_opt_ie: set WPA+RSN ie (len 22) > WPA: Start group state machine to set initial keys > WPA: group state machine entering state GTK_INIT (VLAN-ID 0) > Get randomness: len=16 entropy=0 > GTK - hexdump(len=16): [REMOVED] > WPA: group state machine entering state SETKEYSDONE (VLAN-ID 0) > bsd_set_key: alg=3 addr=0x80be3 key_idx=1 set_tx=1 seq_len=0 key_len=16 > wlan0: interface state UNINITIALIZED->ENABLED > wlan0: AP-ENABLED > wlan0: Setup of interface done. > ctrl_iface not configured! > wlan0: Event ASSOC (0) received > wlan0: STA 00:13:ef:66:18:49 IEEE 802.11: associated > STA included RSN IE in (Re)AssocReq > New STA > ap_sta_add: register ap_handle_timer timeout for 00:13:ef:66:18:49 (300 > seconds - ap_max_inactivity) > wlan0: STA 00:13:ef:66:18:49 WPA: event 1 notification > bsd_set_key: alg=0 addr=0x20847008 key_idx=0 set_tx=1 seq_len=0 key_len=0 > bsd_del_key: addr=00:13:ef:66:18:49 > IEEE 802.1X: Ignore STA - 802.1X not enabled or forced for WPS > wlan0: STA 00:13:ef:66:18:49 WPA: start authentication > WPA: 00:13:ef:66:18:49 WPA_PTK entering state INITIALIZE > bsd_set_key: alg=0 addr=0x20847008 key_idx=0 set_tx=1 seq_len=0 key_len=0 > bsd_del_key: addr=00:13:ef:66:18:49 > wlan0: STA 00:13:ef:66:18:49 IEEE 802.1X: unauthorizing port > WPA: 00:13:ef:66:18:49 WPA_PTK_GROUP entering state IDLE > WPA: 00:13:ef:66:18:49 WPA_PTK entering state AUTHENTICATION > WPA: 00:13:ef:66:18:49 WPA_PTK entering state AUTHENTICATION2 > WPA: Re-initialize GMK/Counter on first station > Get randomness: len=32 entropy=1 > GMK - hexdump(len=32): [REMOVED] > Get randomness: len=32 entropy=0 > Key Counter - hexdump(len=32): [REMOVED] > Get randomness: len=16 entropy=0 > GTK - hexdump(len=16): [REMOVED] > bsd_set_key: alg=3 addr=0x80be3 key_idx=1 set_tx=1 seq_len=0 key_len=16 > Get randomness: len=32 entropy=0 > WPA: Assign ANonce - hexdump(len=32): 8a 5f 94 56 ac e3 d8 80 30 ae e6 fd > ab ea 2f b8 fb ac 1e ce 89 b4 8f 7f d0 74 9a a2 32 d2 3a 9f > WPA: 00:13:ef:66:18:49 WPA_PTK entering state INITPSK > Searching a PSK for 00:13:ef:66:18:49 prev_psk=0x0 > Searching a PSK for 00:13:ef:66:18:49 prev_psk=0x0 > WPA: 00:13:ef:66:18:49 WPA_PTK entering state PTKSTART > wlan0: STA 00:13:ef:66:18:49 WPA: sending 1/4 msg of 4-Way Handshake > WPA: Send EAPOL(version=2 secure=0 mic=0 ack=1 install=0 pairwise=1 > kde_len=0 keyidx=0 encr=0) > WPA: Replay Counter - hexdump(len=8): 00 00 00 00 00 00 00 01 > TX EAPOL - hexdump(len=99): 02 03 00 5f 02 00 8a 00 10 00 00 00 00 00 00 00 > 01 8a 5f 94 56 ac e3 d8 80 30 ae e6 fd ab ea 2f b8 fb ac 1e ce 89 b4 8f 7f > d0 74 9a a2 32 d2 3a 9f 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 > WPA: Use EAPOL-Key timeout of 1000 ms (retry counter 1) > hostapd_new_assoc_sta: reschedule ap_handle_timer timeout for > 00:13:ef:66:18:49 (300 seconds - ap_max_inactivity) > wlan0: Event EAPOL_RX (24) received > IEEE 802.1X: 121 bytes from 00:13:ef:66:18:49 > IEEE 802.1X: version=1 type=3 length=117 > WPA: Received EAPOL-Key from 00:13:ef:66:18:49 key_info=0x10a type=2 > key_data_length=22 > WPA: Received Key Nonce - hexdump(len=32): 9a 00 4b 91 0d 6d 86 0b 85 8d 05 > ab 76 72 94 b2 8b ff 2b ee 7a b4 e9 db de af be 3f 17 99 ca c5 > WPA: Received Replay Counter - hexdump(len=8): 00 00 00 00 00 00 00 01 > wlan0: STA 00:13:ef:66:18:49 WPA: received EAPOL-Key frame (2/4 Pairwise) > WPA: 00:13:ef:66:18:49 WPA_PTK entering state PTKCALCNEGOTIATING > Searching a PSK for 00:13:ef:66:18:49 prev_psk=0x0 > WPA: PTK derivation - A1=00:c6:d2:21:c9:34 A2=00:13:ef:66:18:49 > WPA: Nonce1 - hexdump(len=32): 8a 5f 94 56 ac e3 d8 80 30 ae e6 fd ab ea 2f > b8 fb ac 1e ce 89 b4 8f 7f d0 74 9a a2 32 d2 3a 9f > WPA: Nonce2 - hexdump(len=32): 9a 00 4b 91 0d 6d 86 0b 85 8d 05 ab 76 72 94 > b2 8b ff 2b ee 7a b4 e9 db de af be 3f 17 99 ca c5 > WPA: PMK - hexdump(len=32): [REMOVED] > WPA: PTK - hexdump(len=48): [REMOVED] > WPA: KCK - hexdump(len=16): [REMOVED] > WPA: KEK - hexdump(len=16): [REMOVED] > WPA: TK - hexdump(len=16): [REMOVED] > WPA: 00:13:ef:66:18:49 WPA_PTK entering state PTKCALCNEGOTIATING2 > WPA: 00:13:ef:66:18:49 WPA_PTK entering state PTKINITNEGOTIATING > bsd_get_seqnum: addr=00:00:00:00:00:00 idx=1 > wlan0: STA 00:13:ef:66:18:49 WPA: sending 3/4 msg of 4-Way Handshake > WPA: Send EAPOL(version=2 secure=1 mic=1 ack=1 install=1 pairwise=1 > kde_len=46 keyidx=1 encr=1) > WPA: Replay Counter - hexdump(len=8): 00 00 00 00 00 00 00 02 > Plaintext EAPOL-Key Key Data - hexdump(len=56): [REMOVED] > TX EAPOL - hexdump(len=155): 02 03 00 97 02 13 ca 00 10 00 00 00 00 00 00 > 00 02 8a 5f 94 56 ac e3 d8 80 30 ae e6 fd ab ea 2f b8 fb ac 1e ce 89 b4 8f > 7f d0 74 9a a2 32 d2 3a 9f 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 93 9e 4e 4f 11 14 fd 90 c0 > 03 67 44 ef 3e 93 d3 00 38 d4 5a b4 e2 92 da 2f b6 9b be 78 99 f7 8a 80 65 > f3 f0 7f bf 62 f5 1c 8c d0 af eb b6 e2 33 d1 8d b1 c1 c4 d9 d9 8b b2 f3 17 > 4f 3d 22 26 48 99 25 75 67 b6 96 4c 06 e5 ec > WPA: Use EAPOL-Key timeout of 1000 ms (retry counter 1) > wlan0: Event EAPOL_RX (24) received > IEEE 802.1X: 99 bytes from 00:13:ef:66:18:49 > IEEE 802.1X: version=1 type=3 length=95 > WPA: Received EAPOL-Key from 00:13:ef:66:18:49 key_info=0x30a type=2 > key_data_length=0 > WPA: Received Key Nonce - hexdump(len=32): 00 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > WPA: Received Replay Counter - hexdump(len=8): 00 00 00 00 00 00 00 02 > wlan0: STA 00:13:ef:66:18:49 WPA: received EAPOL-Key frame (4/4 Pairwise) > WPA: 00:13:ef:66:18:49 WPA_PTK entering state PTKINITDONE > bsd_set_key: alg=3 addr=0x20847008 key_idx=0 set_tx=1 seq_len=0 key_len=16 > wlan0: AP-STA-CONNECTED 00:13:ef:66:18:49 > wlan0: STA 00:13:ef:66:18:49 IEEE 802.1X: authorizing port > wlan0: STA 00:13:ef:66:18:49 RADIUS: starting accounting session > 27FA1003-00000000 > wlan0: STA 00:13:ef:66:18:49 WPA: pairwise key handshake completed (RSN) > > wlan0: Event ASSOC (0) received > wlan0: STA 50:55:27:ff:dc:04 IEEE 802.11: associated > STA included RSN IE in (Re)AssocReq > New STA > ap_sta_add: register ap_handle_timer timeout for 50:55:27:ff:dc:04 (300 > seconds - ap_max_inactivity) > wlan0: STA 50:55:27:ff:dc:04 WPA: event 1 notification > bsd_set_key: alg=0 addr=0x20847208 key_idx=0 set_tx=1 seq_len=0 key_len=0 > bsd_del_key: addr=50:55:27:ff:dc:04 > IEEE 802.1X: Ignore STA - 802.1X not enabled or forced for WPS > wlan0: STA 50:55:27:ff:dc:04 WPA: start authentication > WPA: 50:55:27:ff:dc:04 WPA_PTK entering state INITIALIZE > bsd_set_key: alg=0 addr=0x20847208 key_idx=0 set_tx=1 seq_len=0 key_len=0 > bsd_del_key: addr=50:55:27:ff:dc:04 > wlan0: STA 50:55:27:ff:dc:04 IEEE 802.1X: unauthorizing port > WPA: 50:55:27:ff:dc:04 WPA_PTK_GROUP entering state IDLE > WPA: 50:55:27:ff:dc:04 WPA_PTK entering state AUTHENTICATION > WPA: 50:55:27:ff:dc:04 WPA_PTK entering state AUTHENTICATION2 > Get randomness: len=32 entropy=2 > WPA: Assign ANonce - hexdump(len=32): b5 18 65 7c 00 3b ef 61 e1 21 fc 93 > f1 10 81 d5 2e 54 2c 24 d7 c2 24 07 b7 40 83 39 35 d9 ca 85 > WPA: 50:55:27:ff:dc:04 WPA_PTK entering state INITPSK > Searching a PSK for 50:55:27:ff:dc:04 prev_psk=0x0 > Searching a PSK for 50:55:27:ff:dc:04 prev_psk=0x0 > WPA: 50:55:27:ff:dc:04 WPA_PTK entering state PTKSTART > wlan0: STA 50:55:27:ff:dc:04 WPA: sending 1/4 msg of 4-Way Handshake > WPA: Send EAPOL(version=2 secure=0 mic=0 ack=1 install=0 pairwise=1 > kde_len=0 keyidx=0 encr=0) > WPA: Replay Counter - hexdump(len=8): 00 00 00 00 00 00 00 01 > TX EAPOL - hexdump(len=99): 02 03 00 5f 02 00 8a 00 10 00 00 00 00 00 00 00 > 01 b5 18 65 7c 00 3b ef 61 e1 21 fc 93 f1 10 81 d5 2e 54 2c 24 d7 c2 24 07 > b7 40 83 39 35 d9 ca 85 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 > WPA: Use EAPOL-Key timeout of 1000 ms (retry counter 1) > hostapd_new_assoc_sta: reschedule ap_handle_timer timeout for > 50:55:27:ff:dc:04 (300 seconds - ap_max_inactivity) > wlan0: Event EAPOL_RX (24) received > IEEE 802.1X: 121 bytes from 50:55:27:ff:dc:04 > IEEE 802.1X: version=1 type=3 length=117 > WPA: Received EAPOL-Key from 50:55:27:ff:dc:04 key_info=0x10a type=2 > key_data_length=22 > WPA: Received Key Nonce - hexdump(len=32): 98 b8 fd 85 aa b9 9e 71 ed 30 bc > a1 67 9a 7e 3f 08 10 16 3a a2 8a 68 e7 84 52 df 69 74 65 f4 cc > WPA: Received Replay Counter - hexdump(len=8): 00 00 00 00 00 00 00 01 > wlan0: STA 50:55:27:ff:dc:04 WPA: received EAPOL-Key frame (2/4 Pairwise) > WPA: 50:55:27:ff:dc:04 WPA_PTK entering state PTKCALCNEGOTIATING > Searching a PSK for 50:55:27:ff:dc:04 prev_psk=0x0 > WPA: PTK derivation - A1=00:c6:d2:21:c9:34 A2=50:55:27:ff:dc:04 > WPA: Nonce1 - hexdump(len=32): b5 18 65 7c 00 3b ef 61 e1 21 fc 93 f1 10 81 > d5 2e 54 2c 24 d7 c2 24 07 b7 40 83 39 35 d9 ca 85 > WPA: Nonce2 - hexdump(len=32): 98 b8 fd 85 aa b9 9e 71 ed 30 bc a1 67 9a 7e > 3f 08 10 16 3a a2 8a 68 e7 84 52 df 69 74 65 f4 cc > WPA: PMK - hexdump(len=32): [REMOVED] > WPA: PTK - hexdump(len=48): [REMOVED] > WPA: KCK - hexdump(len=16): [REMOVED] > WPA: KEK - hexdump(len=16): [REMOVED] > WPA: TK - hexdump(len=16): [REMOVED] > WPA: 50:55:27:ff:dc:04 WPA_PTK entering state PTKCALCNEGOTIATING2 > WPA: 50:55:27:ff:dc:04 WPA_PTK entering state PTKINITNEGOTIATING > bsd_get_seqnum: addr=00:00:00:00:00:00 idx=1 > wlan0: STA 50:55:27:ff:dc:04 WPA: sending 3/4 msg of 4-Way Handshake > WPA: Send EAPOL(version=2 secure=1 mic=1 ack=1 install=1 pairwise=1 > kde_len=46 keyidx=1 encr=1) > WPA: Replay Counter - hexdump(len=8): 00 00 00 00 00 00 00 02 > Plaintext EAPOL-Key Key Data - hexdump(len=56): [REMOVED] > TX EAPOL - hexdump(len=155): 02 03 00 97 02 13 ca 00 10 00 00 00 00 00 00 > 00 02 b5 18 65 7c 00 3b ef 61 e1 21 fc 93 f1 10 81 d5 2e 54 2c 24 d7 c2 24 > 07 b7 40 83 39 35 d9 ca 85 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > c4 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0 9f 82 19 14 e2 41 db 78 > 34 4d 67 73 0f 2d 98 00 38 36 24 6d a8 10 de 8c ce a9 6d f0 70 32 52 d9 e3 > 39 c4 a7 8e 5f de 51 7c 41 b0 37 6f e9 a7 14 be 1c 74 d4 06 e0 2d f9 b0 f2 > 09 86 cd 6c 79 57 24 fb 68 8b 61 46 20 ef a8 > WPA: Use EAPOL-Key timeout of 1000 ms (retry counter 1) > wlan0: Event EAPOL_RX (24) received > IEEE 802.1X: 99 bytes from 50:55:27:ff:dc:04 > IEEE 802.1X: version=1 type=3 length=95 > WPA: Received EAPOL-Key from 50:55:27:ff:dc:04 key_info=0x30a type=2 > key_data_length=0 > WPA: Received Key Nonce - hexdump(len=32): 00 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > WPA: Received Replay Counter - hexdump(len=8): 00 00 00 00 00 00 00 02 > wlan0: STA 50:55:27:ff:dc:04 WPA: received EAPOL-Key frame (4/4 Pairwise) > WPA: 50:55:27:ff:dc:04 WPA_PTK entering state PTKINITDONE > bsd_set_key: alg=3 addr=0x20847208 key_idx=0 set_tx=1 seq_len=0 key_len=16 > wlan0: AP-STA-CONNECTED 50:55:27:ff:dc:04 > wlan0: STA 50:55:27:ff:dc:04 IEEE 802.1X: authorizing port > wlan0: STA 50:55:27:ff:dc:04 RADIUS: starting accounting session > 27FA1003-00000001 > wlan0: STA 50:55:27:ff:dc:04 WPA: pairwise key handshake completed (RSN) > ap_handle_timer: 00:13:ef:66:18:49 flags=0x23 timeout_next=0 > wlan0: Station 00:13:ef:66:18:49 has been active 0s ago > ap_handle_timer: register ap_handle_timer timeout for 00:13:ef:66:18:49 > (311 seconds) > > wlan0: Event DISASSOC (1) received > wlan0: STA 50:55:27:ff:dc:04 IEEE 802.11: disassociated > wlan0: AP-STA-DISCONNECTED 50:55:27:ff:dc:04 > wlan0: STA 50:55:27:ff:dc:04 WPA: event 2 notification > bsd_set_key: alg=0 addr=0x20847208 key_idx=0 set_tx=1 seq_len=0 key_len=0 > bsd_del_key: addr=50:55:27:ff:dc:04 > ioctl[SIOCS80211, op=20, val=0, arg_len=7]: No such file or directory > WPA: 50:55:27:ff:dc:04 WPA_PTK entering state DISCONNECTED > WPA: 50:55:27:ff:dc:04 WPA_PTK entering state INITIALIZE > bsd_set_key: alg=0 addr=0x20847208 key_idx=0 set_tx=1 seq_len=0 key_len=0 > bsd_del_key: addr=50:55:27:ff:dc:04 > ioctl[SIOCS80211, op=20, val=0, arg_len=7]: No such file or directory > ioctl[SIOCS80211, op=21, val=0, arg_len=42]: No such file or directory > wlan0: STA 50:55:27:ff:dc:04 IEEE 802.1X: unauthorizing port > ap_free_sta: cancel ap_handle_timer for 50:55:27:ff:dc:04 > > wlan0: WPA rekeying GTK > WPA: group state machine entering state SETKEYS (VLAN-ID 0) > Get randomness: len=16 entropy=1 > GTK - hexdump(len=16): [REMOVED] > WPA: 00:13:ef:66:18:49 WPA_PTK_GROUP entering state REKEYNEGOTIATING > wlan0: STA 00:13:ef:66:18:49 WPA: sending 1/2 msg of Group Key Handshake > WPA: Send EAPOL(version=2 secure=1 mic=1 ack=1 install=0 pairwise=0 > kde_len=24 keyidx=2 encr=1) > WPA: Replay Counter - hexdump(len=8): 00 00 00 00 00 00 00 03 > Plaintext EAPOL-Key Key Data - hexdump(len=32): [REMOVED] > TX EAPOL - hexdump(len=131): 02 03 00 7f 02 13 82 00 10 00 00 00 00 00 00 > 00 03 33 ad e3 a9 95 d4 6b 93 4d df bd 96 90 a5 3f fe 58 7f 01 3e 53 1f 8e > 23 3d c0 ef 35 a2 f4 5a df 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 af dd 11 ab e2 ed 9a a2 17 > db 92 63 8a 84 6e 42 00 20 91 7f ca 02 21 28 c9 0d 9f 00 c4 09 da e8 73 88 > 07 0c 8d 5c 5b 30 64 b7 dd 02 35 a2 37 a1 63 e9 > WPA: Use EAPOL-Key timeout of 1000 ms (retry counter 1) > wpa_group_setkeys: GKeyDoneStations=1 > wlan0: STA 00:13:ef:66:18:49 WPA: EAPOL-Key timeout > WPA: 00:13:ef:66:18:49 WPA_PTK_GROUP entering state REKEYNEGOTIATING > wlan0: STA 00:13:ef:66:18:49 WPA: sending 1/2 msg of Group Key Handshake > WPA: Send EAPOL(version=2 secure=1 mic=1 ack=1 install=0 pairwise=0 > kde_len=24 keyidx=2 encr=1) > WPA: Replay Counter - hexdump(len=8): 00 00 00 00 00 00 00 04 > Plaintext EAPOL-Key Key Data - hexdump(len=32): [REMOVED] > TX EAPOL - hexdump(len=131): 02 03 00 7f 02 13 82 00 10 00 00 00 00 00 00 > 00 04 33 ad e3 a9 95 d4 6b 93 4d df bd 96 90 a5 3f fe 58 7f 01 3e 53 1f 8e > 23 3d c0 ef 35 a2 f4 5a df 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 46 e1 ab 2c 2a 89 e4 5c cc > 9a 7a f4 2f 17 c6 ce 00 20 91 7f ca 02 21 28 c9 0d 9f 00 c4 09 da e8 73 88 > 07 0c 8d 5c 5b 30 64 b7 dd 02 35 a2 37 a1 63 e9 > WPA: Use EAPOL-Key timeout of 1000 ms (retry counter 2) > wlan0: STA 00:13:ef:66:18:49 WPA: EAPOL-Key timeout > WPA: 00:13:ef:66:18:49 WPA_PTK_GROUP entering state REKEYNEGOTIATING > wlan0: STA 00:13:ef:66:18:49 WPA: sending 1/2 msg of Group Key Handshake > WPA: Send EAPOL(version=2 secure=1 mic=1 ack=1 install=0 pairwise=0 > kde_len=24 keyidx=2 encr=1) > WPA: Replay Counter - hexdump(len=8): 00 00 00 00 00 00 00 05 > Plaintext EAPOL-Key Key Data - hexdump(len=32): [REMOVED] > TX EAPOL - hexdump(len=131): 02 03 00 7f 02 13 82 00 10 00 00 00 00 00 00 > 00 05 33 ad e3 a9 95 d4 6b 93 4d df bd 96 90 a5 3f fe 58 7f 01 3e 53 1f 8e > 23 3d c0 ef 35 a2 f4 5a df 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b7 5d e8 3f 6b bf 64 aa e2 > 59 b4 0a 1b a7 82 06 00 20 91 7f ca 02 21 28 c9 0d 9f 00 c4 09 da e8 73 88 > 07 0c 8d 5c 5b 30 64 b7 dd 02 35 a2 37 a1 63 e9 > WPA: Use EAPOL-Key timeout of 1000 ms (retry counter 3) > wlan0: STA 00:13:ef:66:18:49 WPA: EAPOL-Key timeout > WPA: 00:13:ef:66:18:49 WPA_PTK_GROUP entering state REKEYNEGOTIATING > wlan0: STA 00:13:ef:66:18:49 WPA: sending 1/2 msg of Group Key Handshake > WPA: Send EAPOL(version=2 secure=1 mic=1 ack=1 install=0 pairwise=0 > kde_len=24 keyidx=2 encr=1) > WPA: Replay Counter - hexdump(len=8): 00 00 00 00 00 00 00 06 > Plaintext EAPOL-Key Key Data - hexdump(len=32): [REMOVED] > TX EAPOL - hexdump(len=131): 02 03 00 7f 02 13 82 00 10 00 00 00 00 00 00 > 00 06 33 ad e3 a9 95 d4 6b 93 4d df bd 96 90 a5 3f fe 58 7f 01 3e 53 1f 8e > 23 3d c0 ef 35 a2 f4 5a df 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 6c 5b f0 e9 64 c8 48 f9 98 > 3b f8 bc df 84 ad 99 00 20 91 7f ca 02 21 28 c9 0d 9f 00 c4 09 da e8 73 88 > 07 0c 8d 5c 5b 30 64 b7 dd 02 35 a2 37 a1 63 e9 > WPA: Use EAPOL-Key timeout of 1000 ms (retry counter 4) > wlan0: STA 00:13:ef:66:18:49 WPA: EAPOL-Key timeout > WPA: 00:13:ef:66:18:49 WPA_PTK_GROUP entering state REKEYNEGOTIATING > WPA: 00:13:ef:66:18:49 WPA_PTK_GROUP entering state KEYERROR > WPA: group state machine entering state SETKEYSDONE (VLAN-ID 0) > bsd_set_key: alg=3 addr=0x80be3 key_idx=2 set_tx=1 seq_len=0 key_len=16 > wlan0: STA 00:13:ef:66:18:49 WPA: WPA_PTK: sm->Disconnect > WPA: 00:13:ef:66:18:49 WPA_PTK entering state DISCONNECT > wpa_sta_disconnect STA 00:13:ef:66:18:49 > hostapd_wpa_auth_disconnect: WPA authenticator requests disconnect: STA > 00:13:ef:66:18:49 reason 2 > wlan0: AP-STA-DISCONNECTED 00:13:ef:66:18:49 > wlan0: STA 00:13:ef:66:18:49 WPA: event 3 notification > bsd_set_key: alg=0 addr=0x20847008 key_idx=0 set_tx=1 seq_len=0 key_len=0 > bsd_del_key: addr=00:13:ef:66:18:49 > ioctl[SIOCS80211, op=20, val=0, arg_len=7]: No such file or directory > ap_sta_disconnect: reschedule ap_handle_timer timeout for 00:13:ef:66:18:49 > (5 seconds - AP_MAX_INACTIVITY_AFTER_DEAUTH) > WPA: 00:13:ef:66:18:49 WPA_PTK_GROUP entering state IDLE > WPA: 00:13:ef:66:18:49 WPA_PTK entering state DISCONNECTED > WPA: 00:13:ef:66:18:49 WPA_PTK entering state INITIALIZE > bsd_set_key: alg=0 addr=0x20847008 key_idx=0 set_tx=1 seq_len=0 key_len=0 > bsd_del_key: addr=00:13:ef:66:18:49 > ioctl[SIOCS80211, op=20, val=0, arg_len=7]: No such file or directory > ioctl[SIOCS80211, op=21, val=0, arg_len=42]: No such file or directory > wlan0: STA 00:13:ef:66:18:49 IEEE 802.1X: unauthorizing port > Removing STA 00:13:ef:66:18:49 from kernel driver > wlan0: STA 00:13:ef:66:18:49 MLME: > MLME-DEAUTHENTICATE.indication(00:13:ef:66:18:49, 2) > wlan0: STA 00:13:ef:66:18:49 MLME: > MLME-DELETEKEYS.request(00:13:ef:66:18:49) > bsd_set_key: alg=0 addr=0x20847008 key_idx=0 set_tx=1 seq_len=0 key_len=0 > bsd_del_key: addr=00:13:ef:66:18:49 > ioctl[SIOCS80211, op=20, val=0, arg_len=7]: No such file or directory > wlan0: Event DISASSOC (1) received > wlan0: STA 00:13:ef:66:18:49 IEEE 802.11: disassociated > wlan0: STA 00:13:ef:66:18:49 WPA: event 2 notification > bsd_set_key: alg=0 addr=0x20847008 key_idx=0 set_tx=1 seq_len=0 key_len=0 > bsd_del_key: addr=00:13:ef:66:18:49 > ioctl[SIOCS80211, op=20, val=0, arg_len=7]: No such file or directory > WPA: 00:13:ef:66:18:49 WPA_PTK entering state DISCONNECTED > WPA: 00:13:ef:66:18:49 WPA_PTK entering state INITIALIZE > bsd_set_key: alg=0 addr=0x20847008 key_idx=0 set_tx=1 seq_len=0 key_len=0 > bsd_del_key: addr=00:13:ef:66:18:49 > ioctl[SIOCS80211, op=20, val=0, arg_len=7]: No such file or directory > ioctl[SIOCS80211, op=21, val=0, arg_len=42]: No such file or directory > wlan0: STA 00:13:ef:66:18:49 IEEE 802.1X: unauthorizing port > ap_free_sta: cancel ap_handle_timer for 00:13:ef:66:18:49 > > > thanks, > peter > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" From owner-freebsd-arm@freebsd.org Sat Oct 8 01:59:24 2016 Return-Path: Delivered-To: freebsd-arm@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 BE114BED7FA for ; Sat, 8 Oct 2016 01:59:24 +0000 (UTC) (envelope-from peter.garshtja@ambient-md.com) Received: from mail-io0-x22f.google.com (mail-io0-x22f.google.com [IPv6:2607:f8b0:4001:c06::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 892B4CC9 for ; Sat, 8 Oct 2016 01:59:24 +0000 (UTC) (envelope-from peter.garshtja@ambient-md.com) Received: by mail-io0-x22f.google.com with SMTP id q192so63790850iod.0 for ; Fri, 07 Oct 2016 18:59:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ambient-md-com.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to; bh=thYW2qUrWLtjgeDF87A4IXPah0IvyMwBgUEk9ENsV9I=; b=k8tidZ1ydQp3NdxJDIh/rwbgqlplmE2rh17KbcxyXCbdN6+Zx4ii9kjUarnXPvaPGn gGCy/SD6S7TgXVoTwnED5Nw1+v5hzkqvNHHdiAfXn8Z5g6jqPVCOFulfrE7ODbTuKzLB QT/61f8kULPkPfDXWcqm9BSNgKtBsp9SiINJPSzaYcDdnukhzYDIo6QJYQM/JEKQPHdc d2TIgzySnYEDMDFspzlwiaXPiNv5d7qyvVL6j7dptSUY/zKpQHDFFneqvIITDzO35af5 4YNc6xPl5kJtw/tOR8AudXM/kFMYyQ4BjElqsuQqHuPDfvSr/CRs38AUgi1zoLR+X/sL jkBg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to; bh=thYW2qUrWLtjgeDF87A4IXPah0IvyMwBgUEk9ENsV9I=; b=L82O9mN576FLhWkBRdz87FDkFOgDRFGVkSS12BlXXF1FnCJPYDwzAgY6To447Fh4D5 r/GWe1bS8Lv3Gab24hNKEFWPGmFbp25iGRXBAIFsBMjv6YQa8xz9mEdPX1Ja8JZKHnCe o5qFxCot/62vtXzdXOGSDjUS1+Tv4OR/435+4hxaEEoq7dtm2UAbxbwTd5LB6Ok4szCE Cy7K9/ZqmPRMR5DVXBM1qCUE4jMH5qmHxFk78VPNNkFhAfAlymGrg2EFXS3EH/COZzkd blzikJhj2IVmmDrLoqgqph/hvTCVxtmgv9Ourgw9yhHbKczhQHNUxNZeG/smY/yn2onF gd2A== X-Gm-Message-State: AA6/9Rl04B7mgw3ECBcb82Oq7XCEXDPKow8/QU9TNDGqfkeW22ZJYhh3PGprPQmdBKf/Hg== X-Received: by 10.107.168.148 with SMTP id e20mr9653402ioj.44.1475891963638; Fri, 07 Oct 2016 18:59:23 -0700 (PDT) Received: from [172.26.26.1] (ip69-17-224-25.vif.net. [69.17.224.25]) by smtp.googlemail.com with ESMTPSA id f201sm8727773ioe.28.2016.10.07.18.59.22 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 07 Oct 2016 18:59:23 -0700 (PDT) Subject: Re: RPI2 AP To: freebsd-arm@freebsd.org References: From: Peter Garshtja Message-ID: <3684c340-3020-31f7-64f1-babf90be8565@ambient-md.com> Date: Fri, 7 Oct 2016 21:59:35 -0400 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Oct 2016 01:59:24 -0000 Greetings, Here is uname - 11.0-RELEASE-p1 FreeBSD 11.0-RELEASE-p1 #0 r306544M Below is dmesg Copyright (c) 1992-2016 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 11.0-RELEASE-p1 #0 r306544M: Fri Sep 30 18:26:52 EDT 2016 ptg@rpi2:/root/crochet/work/obj/arm.armv6/usr/src/sys/RPI2 arm FreeBSD clang version 3.8.0 (tags/RELEASE_380/final 262564) (based on LLVM 3.8.0) VT: init without driver. sema_sysinit CPU: Cortex A7 rev 5 (Cortex-A core) Supported features: ARM_ISA THUMB2 JAZELLE THUMBEE ARMv4 Security_Ext WB enabled LABT branch prediction disabled LoUU:2 LoC:3 LoUIS:2 Cache level 1: 32KB/64B 4-way data cache WB Read-Alloc Write-Alloc 32KB/32B 2-way instruction cache Read-Alloc Cache level 2: 512KB/64B 8-way unified cache WB Read-Alloc Write-Alloc real memory = 989851648 (943 MB) avail memory = 956411904 (912 MB) FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs random: entropy device external interface kbd0 at kbdmux0 ofwbus0: simplebus0: mem 0x3f000000-0x3fffffff on ofwbus0 local_intc0: mem 0x40000000-0x400000ff on simplebus0 generic_timer0: on ofwbus0 Timecounter "ARM MPCore Timecounter" frequency 19200000 Hz quality 1000 Event timer "ARM MPCore Eventtimer" frequency 19200000 Hz quality 1000 intc0: mem 0xb200-0xb3ff on simplebus0 bcmwd0: mem 0x10001c-0x100027 on simplebus0 gpio0: mem 0x200000-0x2000af on simplebus0 gpio0: read-only pins: 46,48-53. gpio0: reserved pins: 48-53. gpiobus0: on gpio0 gpioled0: at pin 35 on gpiobus0 gpioled1: at pin 47 on gpiobus0 gpioc0: on gpio0 iichb0: mem 0x205000-0x20501f on simplebus0 iicbus0: on iichb0 iic0: on iicbus0 iichb1: mem 0x804000-0x80401f on simplebus0 iicbus1: on iichb1 iic1: on iicbus1 spi0: mem 0x204000-0x20401f on simplebus0 spibus0: on spi0 bcm_dma0: mem 0x7000-0x7fff,0xe05000-0xe05fff on simplebus0 mbox0: mem 0xb880-0xb8bf on simplebus0 sdhci_bcm0: mem 0x300000-0x3000ff on simplebus0 mmc0: on sdhci_bcm0 uart0: mem 0x201000-0x201fff on simplebus0 uart0: console (115200,n,8,1) vchiq0: mem 0xb800-0xb84f on simplebus0 vchiq: local ver 8 (min 3), remote ver 8. pcm0: on vchiq0 bcm283x_dwcotg0: mem 0x980000-0x99ffff on simplebus0 usbus0 on bcm283x_dwcotg0 cpulist0: on ofwbus0 cpu0: on cpulist0 bcm2835_cpufreq0: on cpu0 cpu1: on cpulist0 cpu2: on cpulist0 cpu3: on cpulist0 fb0: on ofwbus0 fbd0 on fb0 VT: initialize with new VT driver "fb". fb0: 1680x1050(1680x1050@0,0) 24bpp fb0: fbswap: 1, pitch 5040, base 0x3d384000, screen_size 5322240 cryptosoft0: Timecounters tick every 10.000 msec usbus0: 480Mbps High Speed USB v2.0 ugen0.1: at usbus0 uhub0: on usbus0 mmcsd0: 8GB at mmc0 41.6MHz/4bit/65535-block bcm2835_cpufreq0: ARM 600MHz, Core 250MHz, SDRAM 400MHz, Turbo OFF Release APs Trying to mount root from ufs:/dev/mmcsd0s2a [rw,noatime]... WARNING: / was not properly dismounted warning: no time-of-day clock registered, system time will not be set accurately uhub0: 1 port with 1 removable, self powered ugen0.2: at usbus0 uhub1: on usbus0 uhub1: MTT enabled uhub1: 5 ports with 4 removable, self powered random: unblocking device. ugen0.3: at usbus0 smsc0: on usbus0 smsc0: chip 0xec00, rev. 0002 miibus0: on smsc0 ukphy0: PHY 1 on miibus0 ukphy0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ue0: on smsc0 ue0: Ethernet address: b8:27:eb:f2:8e:4e ugen0.4: at usbus0 bridge0: Ethernet address: 02:fd:a6:82:73:00 ue0: changing name to 'mgmt' smsc0: chip 0xec00, rev. 0002 mgmt: link state changed to DOWN vlan0: changing name to 'wan' vlan1: changing name to 'lan' mgmt: link state changed to UP lan: link state changed to UP wan: link state changed to UP urtwn0: on usbus0 *urtwn0: MAC/BB RTL8188EU, RF 6052 1T1R *urtwn0: enabling 11n mgmt: link state changed to DOWN lan: link state changed to DOWN wan: link state changed to DOWN mgmt: link state changed to UP lan: link state changed to UP wan: link state changed to UP ieee80211_load_module: load the wlan_amrr module by hand for now. wlan0: Ethernet address: 00:c6:d2:21:c9:34 wlan0: promiscuous mode enabled bridge0: link state changed to UP pflog0: promiscuous mode enabled mgmt: promiscuous mode enabled lan: promiscuous mode enabled Thanks in advance, Peter On 10/7/2016 4:36 PM, Adrian Chadd wrote: > + freebsd-wireless > > can you post a 'dmesg' output? That way we can see which urtwn NIC it > is and whether it logged anything. > > > From owner-freebsd-arm@freebsd.org Sat Oct 8 04:51:01 2016 Return-Path: Delivered-To: freebsd-arm@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 C4066C050A6 for ; Sat, 8 Oct 2016 04:51:01 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-it0-x233.google.com (mail-it0-x233.google.com [IPv6:2607:f8b0:4001:c0b::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 8EDCB8A8 for ; Sat, 8 Oct 2016 04:51:01 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-it0-x233.google.com with SMTP id 189so5644865ity.1 for ; Fri, 07 Oct 2016 21:51:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=23HMKRpqMtettsWUJVsyfffZx4CCwiHAN7KtVkSOzq0=; b=UUA2C81uIZdUszVkibxftJWVPP9xluRd8KhvuAiNRUwtjmtxSMxPHG1k0ZmD0cGIEL zxLIyZlheykEe0mxpSJhzGug2KFdz7ZiTHlRYTON1/+0xisBhKnSy6U8AO2Vk1NlK4AR yE53HcUmlExZY2AxwvD/BiuTyZEA1eDf+L9CiCQfSDKHJCtHC6w+Vykp0xerJlpmLWx4 bVFaNr1rUIQLcP/bqocQYXE1TZ7YHBwqOW6neZogKKlIE2JmmGOffGYtf/Y4wipkBLsw 1d9GyIoezwoxRX0QVXOL261c8eave4B9TUKEBVZDn3SXTwkcBDoQ5ECucfMefCbc+GVA x2zA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=23HMKRpqMtettsWUJVsyfffZx4CCwiHAN7KtVkSOzq0=; b=V8neomofWhJAS1aJtWgZ/+OCA1QmIyOGhVuc8rRxKgAl+FjDgd5zTfqhXZBB8xSW7h 8/7cVjPm5DDAPRtkQ39XCTl7cOTlEXUf0O2v84KdShj45/W+CpSe01VbxXsShgdKVt+Z JpO5Dl/N3GrKaADN53jJOIHBEmXh2oDcwm4EhdDd4zvL+wB7uYIjAPizu+5XKDsQSNtF K5CGCRJP6yhI3yx0vu8loodsbCmfbJxSLmlX5fqunn0MVkwc+5kydxh4CdHw4oIIiThv ZhxTF7xGfDOJSOkH0NLdIuoGrrkcBxxoKtBDT7h/dQd9lArbc1Xb3ETEMfJ8WgNJNt0l TD3g== X-Gm-Message-State: AA6/9Rl63hhcmfGlX2D4/yH+/qhLkI4Cx2hCGFhzQggDYyLOigjyTm3kTjEF/CLn6BfSrhGYMLKEFmZ0qWQS9A== X-Received: by 10.36.127.140 with SMTP id r134mr1701218itc.29.1475902260959; Fri, 07 Oct 2016 21:51:00 -0700 (PDT) MIME-Version: 1.0 Received: by 10.36.141.129 with HTTP; Fri, 7 Oct 2016 21:51:00 -0700 (PDT) In-Reply-To: <3684c340-3020-31f7-64f1-babf90be8565@ambient-md.com> References: <3684c340-3020-31f7-64f1-babf90be8565@ambient-md.com> From: Adrian Chadd Date: Fri, 7 Oct 2016 21:51:00 -0700 Message-ID: Subject: Re: RPI2 AP To: Peter Garshtja Cc: "freebsd-arm@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Oct 2016 04:51:01 -0000 heh, try adding wlan_amrr_load="YES" to /boot/loader.conf and rebooting? -a On 7 October 2016 at 18:59, Peter Garshtja wrote: > Greetings, > > Here is uname - 11.0-RELEASE-p1 FreeBSD 11.0-RELEASE-p1 #0 r306544M > > > Below is dmesg > > > Copyright (c) 1992-2016 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 11.0-RELEASE-p1 #0 r306544M: Fri Sep 30 18:26:52 EDT 2016 > ptg@rpi2:/root/crochet/work/obj/arm.armv6/usr/src/sys/RPI2 arm > FreeBSD clang version 3.8.0 (tags/RELEASE_380/final 262564) (based on LLVM > 3.8.0) > VT: init without driver. > sema_sysinit > CPU: Cortex A7 rev 5 (Cortex-A core) > Supported features: ARM_ISA THUMB2 JAZELLE THUMBEE ARMv4 Security_Ext > WB enabled LABT branch prediction disabled > LoUU:2 LoC:3 LoUIS:2 > Cache level 1: > 32KB/64B 4-way data cache WB Read-Alloc Write-Alloc > 32KB/32B 2-way instruction cache Read-Alloc > Cache level 2: > 512KB/64B 8-way unified cache WB Read-Alloc Write-Alloc > real memory = 989851648 (943 MB) > avail memory = 956411904 (912 MB) > FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs > random: entropy device external interface > kbd0 at kbdmux0 > ofwbus0: > simplebus0: mem 0x3f000000-0x3fffffff on > ofwbus0 > local_intc0: mem 0x40000000-0x400000ff on > simplebus0 > generic_timer0: on ofwbus0 > Timecounter "ARM MPCore Timecounter" frequency 19200000 Hz quality 1000 > Event timer "ARM MPCore Eventtimer" frequency 19200000 Hz quality 1000 > intc0: mem 0xb200-0xb3ff on simplebus0 > bcmwd0: mem 0x10001c-0x100027 on simplebus0 > gpio0: mem 0x200000-0x2000af on simplebus0 > gpio0: read-only pins: 46,48-53. > gpio0: reserved pins: 48-53. > gpiobus0: on gpio0 > gpioled0: at pin 35 on gpiobus0 > gpioled1: at pin 47 on gpiobus0 > gpioc0: on gpio0 > iichb0: mem 0x205000-0x20501f on simplebus0 > iicbus0: on iichb0 > iic0: on iicbus0 > iichb1: mem 0x804000-0x80401f on simplebus0 > iicbus1: on iichb1 > iic1: on iicbus1 > spi0: mem 0x204000-0x20401f on simplebus0 > spibus0: on spi0 > bcm_dma0: mem 0x7000-0x7fff,0xe05000-0xe05fff on > simplebus0 > mbox0: mem 0xb880-0xb8bf on simplebus0 > sdhci_bcm0: mem 0x300000-0x3000ff on > simplebus0 > mmc0: on sdhci_bcm0 > uart0: mem 0x201000-0x201fff on simplebus0 > uart0: console (115200,n,8,1) > vchiq0: mem 0xb800-0xb84f on simplebus0 > vchiq: local ver 8 (min 3), remote ver 8. > pcm0: on vchiq0 > bcm283x_dwcotg0: mem > 0x980000-0x99ffff on simplebus0 > usbus0 on bcm283x_dwcotg0 > cpulist0: on ofwbus0 > cpu0: on cpulist0 > bcm2835_cpufreq0: on cpu0 > cpu1: on cpulist0 > cpu2: on cpulist0 > cpu3: on cpulist0 > fb0: on ofwbus0 > fbd0 on fb0 > VT: initialize with new VT driver "fb". > fb0: 1680x1050(1680x1050@0,0) 24bpp > fb0: fbswap: 1, pitch 5040, base 0x3d384000, screen_size 5322240 > cryptosoft0: > Timecounters tick every 10.000 msec > usbus0: 480Mbps High Speed USB v2.0 > ugen0.1: at usbus0 > uhub0: on usbus0 > mmcsd0: 8GB at mmc0 > 41.6MHz/4bit/65535-block > bcm2835_cpufreq0: ARM 600MHz, Core 250MHz, SDRAM 400MHz, Turbo OFF > Release APs > Trying to mount root from ufs:/dev/mmcsd0s2a [rw,noatime]... > WARNING: / was not properly dismounted > warning: no time-of-day clock registered, system time will not be set > accurately > uhub0: 1 port with 1 removable, self powered > ugen0.2: at usbus0 > uhub1: on > usbus0 > uhub1: MTT enabled > uhub1: 5 ports with 4 removable, self powered > random: unblocking device. > ugen0.3: at usbus0 > smsc0: on usbus0 > smsc0: chip 0xec00, rev. 0002 > miibus0: on smsc0 > ukphy0: PHY 1 on miibus0 > ukphy0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > ue0: on smsc0 > ue0: Ethernet address: b8:27:eb:f2:8e:4e > ugen0.4: at usbus0 > bridge0: Ethernet address: 02:fd:a6:82:73:00 > ue0: changing name to 'mgmt' > smsc0: chip 0xec00, rev. 0002 > mgmt: link state changed to DOWN > vlan0: changing name to 'wan' > vlan1: changing name to 'lan' > mgmt: link state changed to UP > lan: link state changed to UP > wan: link state changed to UP > urtwn0: on usbus0 > > *urtwn0: MAC/BB RTL8188EU, RF 6052 1T1R > > *urtwn0: enabling 11n > mgmt: link state changed to DOWN > lan: link state changed to DOWN > wan: link state changed to DOWN > mgmt: link state changed to UP > lan: link state changed to UP > wan: link state changed to UP > ieee80211_load_module: load the wlan_amrr module by hand for now. > wlan0: Ethernet address: 00:c6:d2:21:c9:34 > wlan0: promiscuous mode enabled > bridge0: link state changed to UP > pflog0: promiscuous mode enabled > mgmt: promiscuous mode enabled > lan: promiscuous mode enabled > > Thanks in advance, > > Peter > > On 10/7/2016 4:36 PM, Adrian Chadd wrote: >> >> + freebsd-wireless >> >> can you post a 'dmesg' output? That way we can see which urtwn NIC it >> is and whether it logged anything. >> >> >> > > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" From owner-freebsd-arm@freebsd.org Sat Oct 8 15:10:48 2016 Return-Path: Delivered-To: freebsd-arm@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 577A9C05216 for ; Sat, 8 Oct 2016 15:10:48 +0000 (UTC) (envelope-from peter.garshtja@ambient-md.com) Received: from mail-io0-x230.google.com (mail-io0-x230.google.com [IPv6:2607:f8b0:4001:c06::230]) (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 246357A7 for ; Sat, 8 Oct 2016 15:10:47 +0000 (UTC) (envelope-from peter.garshtja@ambient-md.com) Received: by mail-io0-x230.google.com with SMTP id r30so73309051ioi.1 for ; Sat, 08 Oct 2016 08:10:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ambient-md-com.20150623.gappssmtp.com; s=20150623; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to; bh=P1V7jJSw5kD8kTnA8yvnSwpf1V4vUBrKOKFAXGJ01z4=; b=cSLNK2mAm/n8LI2ROg4jZnb8Tdbe+HbXHiOPkVvOJjIY84jleZIxv0EAnK1388O960 A0uePn9Ma5ZUVph8g400wYofkxwAFhSXWI5qoOZzASu1/GTDrTNlHGI5KjM7mhOhyKV4 w6r6WG4aAFg0qveuMlsFwxsao0sa9g97A2PiJuryyKg8PBt0+tWi72tSqaXTBlO8DLdx rRz81OB4eqHrul4dNSJYB9qeiHlFeUnSzkOgKAU1aZSIItdhKf6y1RtsDR9Hdr7ck2FU iSZvgr5T3Gaemwe1agrxrwHSBgkMjyEXJLGhzWd0K507hdAm0zosJILxb/iJZdkPDgVC NCBg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to; bh=P1V7jJSw5kD8kTnA8yvnSwpf1V4vUBrKOKFAXGJ01z4=; b=K4qzuuN5tM3jmvr5gWZ6J9u+W/NJSJzI3TzT1N5kpUm3AxTuCWvJmEoHV8zb7VVo0g MBIy1bvz7sBHOZD0lEZKf0pO6Rq+yws9TwpGirORtvcWJ5yTm4DzC+WZpFnfx2eRbHQ/ ST1b5Hd/GYKVmBfBCw0Friz/ag8z/5/2Uf1OXeFH7NdHQ0LAjRBV27zTdrLE0dRFIyp9 pb89F/jrwOfgdUexg+jQY51xvdu8vmAITWa+tJ4XSRn9pjOlP2M3V6WooW7Y8c6CoOzp UvwilNbYgLHjaCpzE+864cEm67061Ej6FNMTiko8fcp3lEP4cOfgnf29ah5vuKQURDix nq7A== X-Gm-Message-State: AA6/9RmssD9LBq3CVDWW4Esy9vRloNrATHgnQqwT3hopj/uDL5glQs64sMWMLW0gqZitkQ== X-Received: by 10.107.48.3 with SMTP id w3mr31607769iow.226.1475939447178; Sat, 08 Oct 2016 08:10:47 -0700 (PDT) Received: from [172.26.26.1] (ip69-17-224-25.vif.net. [69.17.224.25]) by smtp.googlemail.com with ESMTPSA id c9sm9666138ioc.26.2016.10.08.08.10.46 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 08 Oct 2016 08:10:46 -0700 (PDT) Subject: Re: RPI2 AP To: Adrian Chadd References: <3684c340-3020-31f7-64f1-babf90be8565@ambient-md.com> Cc: "freebsd-arm@freebsd.org" From: Peter Garshtja Message-ID: <13052a1c-db9b-6e08-eb1a-d75b93c67c33@ambient-md.com> Date: Sat, 8 Oct 2016 11:11:00 -0400 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Oct 2016 15:10:48 -0000 Good Morning Adrian, I added and rebooted RPI2, but the result is the same *wlan_amrr_load="YES" to /boot/loader.conf* *ifconfig wlan0 list sta** **ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG** **50:55:27:ff:dc:04 1 5 54M 20.5 0 2482 38240 EPS AQE RSN WME** **00:13:ef:66:18:49 2 5 1M 14.0 0 7130 27104 EPS AQE RSN WME *After ~ 5 minutes all the stations were disconnected *10:43 # ifconfig wlan0 list sta** **10:43 # ifconfig wlan0 list sta** **10:43 #* WLAN interface details ------------------------------ *ifconfig wlan0 list caps** **drivercaps=591c541** **cryptocaps=b** **htcaps=6000c<> ------------------------------ * Kernel modules loaded* Id Refs Address Size Name 1 31 0xc0100000 9bfaec kernel 2 1 0xc0ac0000 a168 wlan_amrr.ko 3 7 0xc0acb000 59a18 wlan.ko 4 1 0xc46d2000 11000 if_bridge.ko 5 1 0xc46e3000 e000 bridgestp.ko 6 1 0xc4731000 d000 if_vlan.ko 7 1 0xc484c000 27000 if_urtwn.ko 8 1 0xc4774000 b000 firmware.ko 9 1 0xc46bf000 a000 pflog.ko 10 1 0xc4b2c000 3a000 pf.ko 11 1 0xc4e25000 9000 wlan_xauth.ko 12 1 0xc4888000 a000 wlan_wep.ko 13 1 0xc4ef9000 b000 wlan_tkip.ko 14 1 0xc4f0c000 e000 wlan_ccmp.ko *I have 2 different wifi dongles with the same chipset and the behavior is the same. Also here is the dmesg after reboot * **Copyright (c) 1992-2016 The FreeBSD Project.** **Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994** ** The Regents of the University of California. All rights reserved.** **FreeBSD is a registered trademark of The FreeBSD Foundation.** **FreeBSD 11.0-RELEASE-p1 #0 r306544M: Fri Sep 30 18:26:52 EDT 2016** **ptg@rpi2:/root/crochet/work/obj/arm.armv6/usr/src/sys/RPI2 arm** **FreeBSD clang version 3.8.0 (tags/RELEASE_380/final 262564) (based on LLVM 3.8.0)** **VT: init without driver.** **sema_sysinit** **CPU: Cortex A7 rev 5 (Cortex-A core)** ** Supported features: ARM_ISA THUMB2 JAZELLE THUMBEE ARMv4 Security_Ext** ** WB enabled LABT branch prediction disabled** **LoUU:2 LoC:3 LoUIS:2** **Cache level 1:** ** 32KB/64B 4-way data cache WB Read-Alloc Write-Alloc** ** 32KB/32B 2-way instruction cache Read-Alloc** **Cache level 2:** ** 512KB/64B 8-way unified cache WB Read-Alloc Write-Alloc** **real memory = 989851648 (943 MB)** **avail memory = 955379712 (911 MB)** **FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs** **random: entropy device external interface** **kbd0 at kbdmux0** **ofwbus0: ** **simplebus0: mem 0x3f000000-0x3fffffff on ofwbus0** **local_intc0: mem 0x40000000-0x400000ff on simplebus0** **generic_timer0: on ofwbus0** **Timecounter "ARM MPCore Timecounter" frequency 19200000 Hz quality 1000** **Event timer "ARM MPCore Eventtimer" frequency 19200000 Hz quality 1000** **intc0: mem 0xb200-0xb3ff on simplebus0** **bcmwd0: mem 0x10001c-0x100027 on simplebus0** **gpio0: mem 0x200000-0x2000af on simplebus0** **gpio0: read-only pins: 46,48-53.** **gpio0: reserved pins: 48-53.** **gpiobus0: on gpio0** **gpioled0: at pin 35 on gpiobus0** **gpioled1: at pin 47 on gpiobus0** **gpioc0: on gpio0** **iichb0: mem 0x205000-0x20501f on simplebus0** **iicbus0: on iichb0** **iic0: on iicbus0** **iichb1: mem 0x804000-0x80401f on simplebus0** **iicbus1: on iichb1** **iic1: on iicbus1** **spi0: mem 0x204000-0x20401f on simplebus0** **spibus0: on spi0** **bcm_dma0: mem 0x7000-0x7fff,0xe05000-0xe05fff on simplebus0** **mbox0: mem 0xb880-0xb8bf on simplebus0** **sdhci_bcm0: mem 0x300000-0x3000ff on simplebus0** **mmc0: on sdhci_bcm0** **uart0: mem 0x201000-0x201fff on simplebus0** **uart0: console (115200,n,8,1)** **vchiq0: mem 0xb800-0xb84f on simplebus0** **vchiq: local ver 8 (min 3), remote ver 8.** **pcm0: on vchiq0** **bcm283x_dwcotg0: mem 0x980000-0x99ffff on simplebus0** **usbus0 on bcm283x_dwcotg0** **cpulist0: on ofwbus0** **cpu0: on cpulist0** **bcm2835_cpufreq0: on cpu0** **cpu1: on cpulist0** **cpu2: on cpulist0** **cpu3: on cpulist0** **fb0: on ofwbus0** **fbd0 on fb0** **VT: initialize with new VT driver "fb".** **fb0: 1680x1050(1680x1050@0,0) 24bpp** **fb0: fbswap: 1, pitch 5040, base 0x3d384000, screen_size 5322240** **cryptosoft0: ** **Timecounters tick every 10.000 msec** **usbus0: 480Mbps High Speed USB v2.0** **ugen0.1: at usbus0** **uhub0: on usbus0** **mmcsd0: 8GB at mmc0 41.6MHz/4bit/65535-block** **bcm2835_cpufreq0: ARM 600MHz, Core 250MHz, SDRAM 400MHz, Turbo OFF** **Release APs** **Trying to mount root from ufs:/dev/mmcsd0s2a [rw,noatime]...** **warning: no time-of-day clock registered, system time will not be set accurately** **uhub0: 1 port with 1 removable, self powered** **ugen0.2: at usbus0** **uhub1: on usbus0** **uhub1: MTT enabled** **random: unblocking device.** **uhub1: 5 ports with 4 removable, self powered** **ugen0.3: at usbus0** **smsc0: on usbus0** **smsc0: chip 0xec00, rev. 0002** **miibus0: on smsc0** **ukphy0: PHY 1 on miibus0** **ukphy0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto** **ue0: on smsc0** **ue0: Ethernet address: b8:27:eb:f2:8e:4e** **ugen0.4: at usbus0** **bridge0: Ethernet address: 02:fd:a6:82:73:00** **ue0: changing name to 'mgmt'** **smsc0: chip 0xec00, rev. 0002** **mgmt: link state changed to DOWN** **vlan0: changing name to 'wan'** **vlan1: changing name to 'lan'** **mgmt: link state changed to UP** **lan: link state changed to UP** **wan: link state changed to UP** **urtwn0: on usbus0** **urtwn0: MAC/BB RTL8188EU, RF 6052 1T1R** **urtwn0: enabling 11n** **wlan0: Ethernet address: 00:c6:d2:21:c9:34** **wlan0: promiscuous mode enabled** **bridge0: link state changed to UP** **pflog0: promiscuous mode enabled** **mgmt: promiscuous mode enabled** **lan: promiscuous mode enabled**** ** ***Thanks, Peter On 10/8/2016 12:51 AM, Adrian Chadd wrote: > heh, try adding wlan_amrr_load="YES" to /boot/loader.conf and rebooting? > > > -a > > > On 7 October 2016 at 18:59, Peter Garshtja > wrote: >> Greetings, >> >> Here is uname - 11.0-RELEASE-p1 FreeBSD 11.0-RELEASE-p1 #0 r306544M >> >> >> Below is dmesg >> >> >> Copyright (c) 1992-2016 The FreeBSD Project. >> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 >> The Regents of the University of California. All rights reserved. >> FreeBSD is a registered trademark of The FreeBSD Foundation. >> FreeBSD 11.0-RELEASE-p1 #0 r306544M: Fri Sep 30 18:26:52 EDT 2016 >> ptg@rpi2:/root/crochet/work/obj/arm.armv6/usr/src/sys/RPI2 arm >> FreeBSD clang version 3.8.0 (tags/RELEASE_380/final 262564) (based on LLVM >> 3.8.0) >> VT: init without driver. >> sema_sysinit >> CPU: Cortex A7 rev 5 (Cortex-A core) >> Supported features: ARM_ISA THUMB2 JAZELLE THUMBEE ARMv4 Security_Ext >> WB enabled LABT branch prediction disabled >> LoUU:2 LoC:3 LoUIS:2 >> Cache level 1: >> 32KB/64B 4-way data cache WB Read-Alloc Write-Alloc >> 32KB/32B 2-way instruction cache Read-Alloc >> Cache level 2: >> 512KB/64B 8-way unified cache WB Read-Alloc Write-Alloc >> real memory = 989851648 (943 MB) >> avail memory = 956411904 (912 MB) >> FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs >> random: entropy device external interface >> kbd0 at kbdmux0 >> ofwbus0: >> simplebus0: mem 0x3f000000-0x3fffffff on >> ofwbus0 >> local_intc0: mem 0x40000000-0x400000ff on >> simplebus0 >> generic_timer0: on ofwbus0 >> Timecounter "ARM MPCore Timecounter" frequency 19200000 Hz quality 1000 >> Event timer "ARM MPCore Eventtimer" frequency 19200000 Hz quality 1000 >> intc0: mem 0xb200-0xb3ff on simplebus0 >> bcmwd0: mem 0x10001c-0x100027 on simplebus0 >> gpio0: mem 0x200000-0x2000af on simplebus0 >> gpio0: read-only pins: 46,48-53. >> gpio0: reserved pins: 48-53. >> gpiobus0: on gpio0 >> gpioled0: at pin 35 on gpiobus0 >> gpioled1: at pin 47 on gpiobus0 >> gpioc0: on gpio0 >> iichb0: mem 0x205000-0x20501f on simplebus0 >> iicbus0: on iichb0 >> iic0: on iicbus0 >> iichb1: mem 0x804000-0x80401f on simplebus0 >> iicbus1: on iichb1 >> iic1: on iicbus1 >> spi0: mem 0x204000-0x20401f on simplebus0 >> spibus0: on spi0 >> bcm_dma0: mem 0x7000-0x7fff,0xe05000-0xe05fff on >> simplebus0 >> mbox0: mem 0xb880-0xb8bf on simplebus0 >> sdhci_bcm0: mem 0x300000-0x3000ff on >> simplebus0 >> mmc0: on sdhci_bcm0 >> uart0: mem 0x201000-0x201fff on simplebus0 >> uart0: console (115200,n,8,1) >> vchiq0: mem 0xb800-0xb84f on simplebus0 >> vchiq: local ver 8 (min 3), remote ver 8. >> pcm0: on vchiq0 >> bcm283x_dwcotg0: mem >> 0x980000-0x99ffff on simplebus0 >> usbus0 on bcm283x_dwcotg0 >> cpulist0: on ofwbus0 >> cpu0: on cpulist0 >> bcm2835_cpufreq0: on cpu0 >> cpu1: on cpulist0 >> cpu2: on cpulist0 >> cpu3: on cpulist0 >> fb0: on ofwbus0 >> fbd0 on fb0 >> VT: initialize with new VT driver "fb". >> fb0: 1680x1050(1680x1050@0,0) 24bpp >> fb0: fbswap: 1, pitch 5040, base 0x3d384000, screen_size 5322240 >> cryptosoft0: >> Timecounters tick every 10.000 msec >> usbus0: 480Mbps High Speed USB v2.0 >> ugen0.1: at usbus0 >> uhub0: on usbus0 >> mmcsd0: 8GB at mmc0 >> 41.6MHz/4bit/65535-block >> bcm2835_cpufreq0: ARM 600MHz, Core 250MHz, SDRAM 400MHz, Turbo OFF >> Release APs >> Trying to mount root from ufs:/dev/mmcsd0s2a [rw,noatime]... >> WARNING: / was not properly dismounted >> warning: no time-of-day clock registered, system time will not be set >> accurately >> uhub0: 1 port with 1 removable, self powered >> ugen0.2: at usbus0 >> uhub1: on >> usbus0 >> uhub1: MTT enabled >> uhub1: 5 ports with 4 removable, self powered >> random: unblocking device. >> ugen0.3: at usbus0 >> smsc0: on usbus0 >> smsc0: chip 0xec00, rev. 0002 >> miibus0: on smsc0 >> ukphy0: PHY 1 on miibus0 >> ukphy0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto >> ue0: on smsc0 >> ue0: Ethernet address: b8:27:eb:f2:8e:4e >> ugen0.4: at usbus0 >> bridge0: Ethernet address: 02:fd:a6:82:73:00 >> ue0: changing name to 'mgmt' >> smsc0: chip 0xec00, rev. 0002 >> mgmt: link state changed to DOWN >> vlan0: changing name to 'wan' >> vlan1: changing name to 'lan' >> mgmt: link state changed to UP >> lan: link state changed to UP >> wan: link state changed to UP >> urtwn0: on usbus0 >> >> *urtwn0: MAC/BB RTL8188EU, RF 6052 1T1R >> >> *urtwn0: enabling 11n >> mgmt: link state changed to DOWN >> lan: link state changed to DOWN >> wan: link state changed to DOWN >> mgmt: link state changed to UP >> lan: link state changed to UP >> wan: link state changed to UP >> ieee80211_load_module: load the wlan_amrr module by hand for now. >> wlan0: Ethernet address: 00:c6:d2:21:c9:34 >> wlan0: promiscuous mode enabled >> bridge0: link state changed to UP >> pflog0: promiscuous mode enabled >> mgmt: promiscuous mode enabled >> lan: promiscuous mode enabled >> >> Thanks in advance, >> >> Peter >> >> On 10/7/2016 4:36 PM, Adrian Chadd wrote: >>> + freebsd-wireless >>> >>> can you post a 'dmesg' output? That way we can see which urtwn NIC it >>> is and whether it logged anything. >>> >>> >>> >> _______________________________________________ >> freebsd-arm@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-arm >> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org"