From owner-freebsd-arm@freebsd.org Sun Mar 10 22:07:40 2019 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 63A4C1543B19 for ; Sun, 10 Mar 2019 22:07:40 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: from out.migadu.com (out.migadu.com [91.121.223.63]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.migadu.com", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9239D69BF3 for ; Sun, 10 Mar 2019 22:07:39 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: (Migadu outbound); Sun, 10 Mar 2019 22:06:24 +0000 Received: from [192.168.1.141] ([62.122.208.146]) by out.migadu.com (Haraka/2.8.16) with ESMTPSA id 226BFB91-4C7C-49EE-8C50-5BD0BC0F0D4F.1 envelope-from (authenticated bits=0) (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 verify=FAIL); Sun, 10 Mar 2019 22:06:24 +0000 Date: Mon, 11 Mar 2019 01:06:20 +0300 From: Greg V Subject: Re: ARM Graviton AWS Processor (AMI Image) To: Martin Karrer Cc: freebsd-arm@freebsd.org, freebsd-hackers@freebsd.org, freebsd-cloud@freebsd.org Message-Id: <1552255580.21373.0@unrelenting.technology> In-Reply-To: <1548182399.2864.0@smtp.migadu.com> References: <79CC79B9-81AF-4563-BABE-429E6A57F476@bmalum.com> <010201686fe5047f-ed14af85-2b25-4480-a62a-a893f062eedd-000000@eu-west-1.amazonses.com> <010201686fe5047f-ed14af85-2b25-4480-a62a-a893f062eedd-000000@eu-west-1.amazo> X-Mailer: geary/master~gfcf07ad4 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable DKIM-Signature: v=1; a=rsa-sha256; bh=yFeukkt+RUN+oEqF1Ne+PZL5JrtX8FnxvXapLRyw2ig=; c=relaxed/simple; d=unrelenting.technology; h=from:subject:date:to; s=default; b=bO0c5gqCPwVq1Ip/7e9PLoCHqgYYn+WFSTytDddDRgn8sznjfCFWXKFXpa9DhrllgGrw463zaQfRMiT/1OlO7SQzvzRa2NHj6dm1G77lvRPWfWrgsf8hSF5S6rGRDWLq9jlwNuVmlxOttP38e/z9gyPeZOt4iqwvejLF6Rlf8FU= X-Rspamd-Queue-Id: 9239D69BF3 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=unrelenting.technology header.s=default header.b=bO0c5gqC; dmarc=pass (policy=none) header.from=unrelenting.technology; spf=pass (mx1.freebsd.org: domain of greg@unrelenting.technology designates 91.121.223.63 as permitted sender) smtp.mailfrom=greg@unrelenting.technology X-Spamd-Result: default: False [-6.63 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[unrelenting.technology:s=default]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; R_SPF_ALLOW(-0.20)[+ip4:91.121.223.63]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; TO_DN_SOME(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[unrelenting.technology:+]; DMARC_POLICY_ALLOW(-0.50)[unrelenting.technology,none]; MX_GOOD(-0.01)[cached: aspmx1.migadu.com]; NEURAL_HAM_SHORT(-0.99)[-0.989,0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; IP_SCORE(-2.64)[ip: (-9.89), ipnet: 91.121.0.0/16(-4.11), asn: 16276(0.84), country: FR(-0.01)]; ASN(0.00)[asn:16276, ipnet:91.121.0.0/16, country:FR]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Mar 2019 22:07:40 -0000 On Tue, Jan 22, 2019 at 9:39 PM, Greg V =20 wrote: > On Mon, Jan 21, 2019 at 1:11 PM, Martin Karrer =20 > wrote: >> My question is if there are any plans yet to support the Graviton=20 >> ARM =7Finstances of AWS? >>=20 >> We have a heavy load on FreeBSD and would also use the ARM=20 >> instances. =7FAre there any other interested parties? >=20 > I have tried this. It should work very well in theory, e.g. the=20 > network card driver (if_ena) compiles with no changes for aarch64,=20 > and in fact NetBSD has ported this driver and is up and running on=20 > these instances: https://dmesgd.nycbug.org/index.cgi?do=3Dview&id=3D4623 >=20 > But my result with FreeBSD was: nothing on the console after=20 > loader.efi hands control to the kernel. > [=E2=80=A6] Hello everyone, big update: FreeBSD/aarch64 on Amazon EC2 a1 (AWS Graviton) instances WORKS! https://dmesgd.nycbug.org/index.cgi?do=3Dview&id=3D4813 And you can try it (well, my -CURRENT build, NO WARRANTY etc) right now: ami-0c2829a0b82a62ca6 in eu-west-1 (Ireland) ----- So, what I had to do / what should be done / how others can help get=20 this into a finished state: 1. Serial console: - I fixed it: https://reviews.freebsd.org/D19507 - (I learned some things about UARTs and their support in FreeBSD,=20 should write a blog post about that) 2. aarch64 build configuration: - if_ena network driver module should be enabled:=20 https://reviews.freebsd.org/D18372 - NVMe driver should be enabled in the GENERIC kernel config (device=20 nvme, device nvd) - BTW, why not also go with hw.nvme.use_nvd=3D"0" by default on=20 aarch64, IIRC that was done on powerpc64 3. VM image build system: - GPT+EFI should be used (amd64 was GPT with no EFI, and aarch64 was=20 MBR with EFI (???)): https://reviews.freebsd.org/D18371 - bsdec2-image-upload --arm64 flag should be supported: included=20 above ^^ - ec2.conf: amazon-ssm-agent shouldn't be installed when building=20 for aarch64 TARGET, since that's written in Go, and Go isn't ported to=20 FreeBSD/aarch64 yet:=20 https://github.com/myfreeweb/freebsd/commit/5b530ebf7385d8320b9076cf84f50aa= d01689bc=20 (untested patch, I actually used an interactive shell in between the=20 image build commands) - qemu-aarch64-static should be used for preinstalling pkgs when=20 chrooting into the image: rough version included above ^^ 4. ENA (Elastic Network Adapter) driver: - it works - except there's something funky with interrupt activation, and it=20 hits panic("Attempt to double activation of resource id: %u\n", res_id)=20 (for the management IRQ) on boot, so I applied the obvious silly=20 workaround of "don't panic":=20 https://github.com/myfreeweb/freebsd/commit/a7e7c6e48cdbdb0fdc6c4e0ba633922= 62938e62c - but still, it doesn't properly reactivate interrupts (and the box=20 becomes unreachable over the net) after going down and up again =E2=80=94=20 guess what does that on boot? dhclient applying the big jumbo MTU =E2=80=94= =20 so I set dhclient.conf to reject MTU changes:=20 https://github.com/myfreeweb/freebsd/commit/03ec4d417b0b4252285baaf4e294cc6= d8c870f7f Would be great if someone familiar with interrupts and stuff could help=20 debug the ena driver and make it work without these hacks :) = From owner-freebsd-arm@freebsd.org Sun Mar 10 19:00:13 2019 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D9B0D153DD92 for ; Sun, 10 Mar 2019 19:00:12 +0000 (UTC) (envelope-from mlist@nlned.nl) Received: from vps.zwn24.nl (vps.zwn24.nl [207.180.220.156]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "zwn24.nl", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id ADAA789B51 for ; Sun, 10 Mar 2019 19:00:11 +0000 (UTC) (envelope-from mlist@nlned.nl) Received: from vps.zwn24.nl (vps.zwn24.nl [207.180.220.156]) by vps.zwn24.nl (Postfix) with ESMTP id 7615F29DEB for ; Sun, 10 Mar 2019 20:00:01 +0100 (CET) Received: from [192.168.178.183] (541a7d62.cm-5-3b.dynamic.ziggo.nl [84.26.125.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by vps.zwn24.nl (Postfix) with ESMTPSA id 192F629DEA for ; Sun, 10 Mar 2019 20:00:01 +0100 (CET) User-Agent: Microsoft-MacOutlook/10.10.7.190210 Date: Sun, 10 Mar 2019 19:59:59 +0100 Subject: FreeBSD-images From: Jack Raats To: FreeBSD ARM Message-ID: Thread-Topic: FreeBSD-images Mime-version: 1.0 X-Virus-Scanned: ClamAV using ClamSMTP on vps.zwn24.nl X-Rspamd-Queue-Id: ADAA789B51 X-Spamd-Bar: +++ Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of mlist@nlned.nl designates 207.180.220.156 as permitted sender) smtp.mailfrom=mlist@nlned.nl X-Spamd-Result: default: False [3.54 / 15.00]; ARC_NA(0.00)[]; SUBJECT_ENDS_SPACES(0.50)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; DMARC_NA(0.00)[nlned.nl]; NEURAL_SPAM_MEDIUM(0.84)[0.836,0]; RCPT_COUNT_ONE(0.00)[1]; IP_SCORE(0.73)[asn: 51167(3.65), country: DE(-0.01)]; TO_DN_ALL(0.00)[]; MX_GOOD(-0.01)[nlned.nl]; NEURAL_SPAM_LONG(0.82)[0.821,0]; NEURAL_SPAM_SHORT(0.86)[0.862,0]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; ASN(0.00)[asn:51167, ipnet:207.180.220.0/23, country:DE]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Mar 2019 19:00:13 -0000 Hi, Every night my server makes a fresh FreeBSD 12.0-STABLE image for the raspberry pi 2 en 3. You can download it at https://jarasoft.net/rpi Gr., Jack From owner-freebsd-arm@freebsd.org Sun Mar 10 17:10:40 2019 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6E158153A237 for ; Sun, 10 Mar 2019 17:10:40 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C6BFF85578 for ; Sun, 10 Mar 2019 17:10:39 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id x2AHATwL064372 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 10 Mar 2019 10:10:29 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id x2AHASRD064371; Sun, 10 Mar 2019 10:10:28 -0700 (PDT) (envelope-from fbsd) Date: Sun, 10 Mar 2019 10:10:28 -0700 From: bob prohaska To: freebsd-arm@freebsd.org Subject: Multiport USB hubs/switches on Raspberry Pi Message-ID: <20190310171028.GA64290@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.24 (2015-08-30) X-Rspamd-Queue-Id: C6BFF85578 X-Spamd-Bar: +++ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [3.76 / 15.00]; ARC_NA(0.00)[]; WWW_DOT_DOMAIN(0.50)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_SPAM_SHORT(0.89)[0.892,0]; IP_SCORE(0.17)[ip: (0.61), ipnet: 50.1.16.0/20(0.31), asn: 7065(-0.02), country: US(-0.07)]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[zefox.net]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.33)[0.334,0]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[cached: www.zefox.net]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_SPAM_LONG(0.48)[0.479,0]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US]; MID_RHS_MATCH_FROM(0.00)[]; MID_RHS_WWW(0.50)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Mar 2019 17:10:40 -0000 Does anyone have experience using multiport USB hubs on freebsd-arm, specifically in the context of Raspberry Pi 2 or 3? I'm interested in trying to use a hub/switch (not sure there's a difference in the case of USB) to construct a terminal server for serial console access on a small cluster of Pi's. I'd want about seven or eight ports, each holding a USB-serial adapter that would then connect to the GPIO UART pins on one Pi in the cluster. I've used both USB 3.0 and USB 1.1 hubs, and in both cases odd things seem to happen from time to time. One potential example is https://www.amazon.com/AmazonBasics-Port-USB-2-0-Hub/dp/B00GGYU46O/ref=sxin_2?keywords=powered+usb+hub&pd_rd_i=B00GGYU46O&pd_rd_r=83f1e3f0-a1e6-40aa-bdd8-aa86a7c0b360&pd_rd_w=foNmt&pd_rd_wg=ncKZR&pf_rd_p=0395a9fd-d124-46c0-a48f-d8582ed1a45c&pf_rd_r=2P9WWPAZGMAA29NMVVV2&qid=1552234319&s=gateway If anyone has experience along these lines or a suggestion for/against particular USB devices or versions I'd be curious to know. Thanks for reading, bob prohaska From owner-freebsd-arm@freebsd.org Mon Mar 11 04:49:48 2019 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B893B152F293 for ; Mon, 11 Mar 2019 04:49:48 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [195.149.99.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "raven.bwct.de", Issuer "raven.bwct.de" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 2DC138164D; Mon, 11 Mar 2019 04:49:46 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.15.2/8.15.2) with ESMTPS id x2B4ngZW099017 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 11 Mar 2019 05:49:43 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cicely.de; s=default; t=1552279784; bh=QlGKOkIX3V8l2v3laKSuh+Go+OZq8UFH5vBk7TgiWGE=; h=Date:From:To:Cc:Subject:Reply-To:References:In-Reply-To; b=mACnLzqIvWdDl8d8aTizvxjwLlm6Td5R/BXtEo6XNovQPSXuxbiU5A3ZqlmrUg75W ffZwdFqrISnZDbdELFxThRe7waYr1gWQFDtf+4oYcE6ykr1OuXPy4bolbmkPgI64pt s9xsYWp2/IKkZtfA51bNxJdUTPqfH5BhOonTDAwU= Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.5/8.14.4) with ESMTP id x2B4nc7P016461 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 11 Mar 2019 05:49:38 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.15.2/8.15.2) with ESMTP id x2B4ncXR054066; Mon, 11 Mar 2019 05:49:38 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.15.2/8.15.2/Submit) id x2B4ncNl054065; Mon, 11 Mar 2019 05:49:38 +0100 (CET) (envelope-from ticso) Date: Mon, 11 Mar 2019 05:49:38 +0100 From: Bernd Walter To: Ian Lepore Cc: bob prohaska , freebsd-arm@freebsd.org Subject: Re: Editing on the serial console Message-ID: <20190311044937.GB51206@cicely7.cicely.de> Reply-To: ticso@cicely.de References: <20190307035427.GA42903@www.zefox.net> <580addeeb90cc317cc65f69bdc39c549a5852806.camel@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <580addeeb90cc317cc65f69bdc39c549a5852806.camel@freebsd.org> X-Operating-System: FreeBSD cicely7.cicely.de 12.0-STABLE amd64 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=4.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9 autolearn=ham version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de X-Rspamd-Queue-Id: 2DC138164D X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=pass header.d=cicely.de header.s=default header.b=mACnLzqI X-Spamd-Result: default: False [-0.99 / 15.00]; ARC_NA(0.00)[]; HAS_REPLYTO(0.00)[ticso@cicely.de]; R_DKIM_ALLOW(-0.20)[cicely.de:s=default]; RCVD_COUNT_FIVE(0.00)[5]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; MV_CASE(0.50)[]; NEURAL_HAM_LONG(-0.98)[-0.981,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[cicely.de]; REPLYTO_DOM_NEQ_FROM_DOM(0.00)[]; TO_DN_SOME(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[cicely.de:+]; MX_GOOD(-0.01)[mx1.bwct.de]; RCVD_IN_DNSWL_NONE(0.00)[3.99.149.195.list.dnswl.org : 127.0.20.0]; NEURAL_HAM_SHORT(-0.15)[-0.145,0]; NEURAL_HAM_MEDIUM(-0.05)[-0.055,0]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:21461, ipnet:195.149.99.0/24, country:DE]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(-0.00)[country: DE(-0.01)] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Mar 2019 04:49:49 -0000 On Thu, Mar 07, 2019 at 07:46:57AM -0700, Ian Lepore wrote: > On Wed, 2019-03-06 at 19:54 -0800, bob prohaska wrote: > > Editing files in single-user mode on the serial console > > is non-trivial. Both vi and ee have problems displaying > > the file, ed doesn't really try so it works but isn't > > much fun. Is there a better option? When the machine > > boots single-user it reports "can't read /etc/termcap", > > is something misconfigured? > > > > I'm dealing with Raspberry Pi, but am not sure if that's > > the source of the difficulty. > > > > Thanks for reading, > > > > bob prohaska > > > > > > A lot of things work together (or fail to) to cause trouble for apps > that do full-screen terminal stuff. A big part of it is what you're > using as a terminal program. Using cu(1) from an xterm window works > well if you set TERM=xterm in the env (of course you need a termcap > file as you noted). > > Another thing that causes problems is when your terminal window size > isn't known to vi or whatever app is running. You can fix that by > manually doing 'stty rows NN cols NN' to set the right values. I usually don't waste time to setup all that stuff and just use ed(1). It only makes sense to do so if you have to spend more time on the serial console. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-arm@freebsd.org Mon Mar 11 05:01:10 2019 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CEBE6152FA64 for ; Mon, 11 Mar 2019 05:01:10 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [195.149.99.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "raven.bwct.de", Issuer "raven.bwct.de" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id F2A0781DB2 for ; Mon, 11 Mar 2019 05:01:09 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.15.2/8.15.2) with ESMTPS id x2B4i8II098900 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 11 Mar 2019 05:44:09 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cicely.de; s=default; t=1552279449; bh=gWW4STb5dkm1uWRbngF7auNO1oRtdOjG45aD2anQXJM=; h=Date:From:To:Cc:Subject:Reply-To:References:In-Reply-To; b=kn8i2QEDOcfXTpKtZx9lFMS3VgLCpdAxUEiJVYCHOQsoMVJWBtYk3IUQnonKY5qef PjTOqEjWi8K2m5/4T1Cuov2HypLOZUn33xIL9aelvzO/ZYvcBQ7XtHQQB+JGorxSRY ZHj6RTZXmXqlPK6DylAnmoNY8zJpyIDd2QCv12wk= Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.5/8.14.4) with ESMTP id x2B4i58x016382 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 11 Mar 2019 05:44:05 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.15.2/8.15.2) with ESMTP id x2B4i5JF054036; Mon, 11 Mar 2019 05:44:05 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.15.2/8.15.2/Submit) id x2B4i4na054035; Mon, 11 Mar 2019 05:44:04 +0100 (CET) (envelope-from ticso) Date: Mon, 11 Mar 2019 05:44:04 +0100 From: Bernd Walter To: bob prohaska Cc: freebsd-arm@freebsd.org Subject: Re: Multiport USB hubs/switches on Raspberry Pi Message-ID: <20190311044402.GA51206@cicely7.cicely.de> Reply-To: ticso@cicely.de References: <20190310171028.GA64290@www.zefox.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190310171028.GA64290@www.zefox.net> X-Operating-System: FreeBSD cicely7.cicely.de 12.0-STABLE amd64 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=4.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9 autolearn=ham version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de X-Rspamd-Queue-Id: F2A0781DB2 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=pass header.d=cicely.de header.s=default header.b=kn8i2QED X-Spamd-Result: default: False [-0.74 / 15.00]; ARC_NA(0.00)[]; HAS_REPLYTO(0.00)[ticso@cicely.de]; R_DKIM_ALLOW(-0.20)[cicely.de:s=default]; RCVD_COUNT_FIVE(0.00)[5]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; MV_CASE(0.50)[]; NEURAL_HAM_LONG(-0.99)[-0.990,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[cicely.de]; REPLYTO_DOM_NEQ_FROM_DOM(0.00)[]; NEURAL_SPAM_SHORT(0.40)[0.399,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[cicely.de:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[3.99.149.195.list.dnswl.org : 127.0.20.0]; MX_GOOD(-0.01)[cached: mx1.bwct.de]; NEURAL_HAM_MEDIUM(-0.34)[-0.342,0]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:21461, ipnet:195.149.99.0/24, country:DE]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(-0.00)[country: DE(-0.01)] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Mar 2019 05:01:11 -0000 On Sun, Mar 10, 2019 at 10:10:28AM -0700, bob prohaska wrote: > Does anyone have experience using multiport USB hubs on freebsd-arm, > specifically in the context of Raspberry Pi 2 or 3? USB hubs work fine on Raspberries and they better should, since one is integrated on most of them. I run a Pi3B+ on my Pick an Place machine to hook up all the IO boards. Works fine, just recently upgraded from a Pi2. [51]pnp-gcode.cicely.de# usbconfig ugen0.1: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen0.2: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (2mA) ugen0.3: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (2mA) ugen0.4: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (2mA) ugen0.5: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (90mA) ugen0.6: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (90mA) ugen0.7: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (100mA) ugen0.8: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (96mA) ugen0.9: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (96mA) ugen0.10: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (90mA) ugen0.11: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (100mA) ugen0.12: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (100mA) ugen0.13: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (500mA) ugen0.14: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (100mA) [52]pnp-gcode.cicely.de# uname -a FreeBSD pnp-gcode.cicely.de 12.0-RELEASE FreeBSD 12.0-RELEASE r341666 GENERIC arm64 > I'm interested in trying to use a hub/switch (not sure there's a > difference in the case of USB) to construct a terminal server for > serial console access on a small cluster of Pi's. I'd want about > seven or eight ports, each holding a USB-serial adapter that would > then connect to the GPIO UART pins on one Pi in the cluster. I've > used both USB 3.0 and USB 1.1 hubs, and in both cases odd things > seem to happen from time to time. One potential example is > > > https://www.amazon.com/AmazonBasics-Port-USB-2-0-Hub/dp/B00GGYU46O/ref=sxin_2?keywords=powered+usb+hub&pd_rd_i=B00GGYU46O&pd_rd_r=83f1e3f0-a1e6-40aa-bdd8-aa86a7c0b360&pd_rd_w=foNmt&pd_rd_wg=ncKZR&pf_rd_p=0395a9fd-d124-46c0-a48f-d8582ed1a45c&pf_rd_r=2P9WWPAZGMAA29NMVVV2&qid=1552234319&s=gateway I can't speak for this specific hub, but many hubs are build marginal, especially when it comes to power delivery. In this special case I'm a bit sceptical supplying 10 port with that power supply and tiny connector. The hub I use on the pick and place machine is a bare PCB with 5V input from a big supply. For important stuff, especially if I need them to supply devices, I use hubs with higher input voltage and internal 5V regulator. Exsys has some nice ones, but they are not the only vendor. Exsys also has a big 19" hub, if that matters for your case. My suggestion is to use USB uarts, which can hold a serial number, such as uftdi or uslcom based. This makes it easier to wire them via devd. E.g. I have something like this in my devd.conf for a CP2102: attach 0 { device-name "uslcom[0-9]+"; match "sernum" "TTL01"; match "interface" "0"; action "rm /dev/ttluart1; ln -s /dev/cua$ttyname /dev/ttluart1"; }; And for a FT4232: attach 0 { device-name "uftdi[0-9]+"; match "sernum" "FTXO1CJC"; match "interface" "0"; action "rm /dev/manson_psu9; ln -s /dev/cua$ttyname /dev/manson_psu9"; }; attach 0 { device-name "uftdi[0-9]+"; match "sernum" "FTXO1CJC"; match "interface" "1"; action "rm /dev/manson_psu10; ln -s /dev/cua$ttyname /dev/manson_psu10"; }; attach 0 { device-name "uftdi[0-9]+"; match "sernum" "FTXO1CJC"; match "interface" "2"; action "rm /dev/x1; ln -s /dev/cua$ttyname /dev/x1"; }; attach 0 { device-name "uftdi[0-9]+"; match "sernum" "FTXO1CJC"; match "interface" "3"; action "rm /dev/x2; ln -s /dev/cua$ttyname /dev/x2"; }; > If anyone has experience along these lines or a suggestion for/against > particular USB devices or versions I'd be curious to know. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-arm@freebsd.org Mon Mar 11 08:35:25 2019 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0A46A15375A4 for ; Mon, 11 Mar 2019 08:35:25 +0000 (UTC) (envelope-from mw@semihalf.com) Received: from mail-qk1-x72f.google.com (mail-qk1-x72f.google.com [IPv6:2607:f8b0:4864:20::72f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1BDEB8A608 for ; Mon, 11 Mar 2019 08:35:23 +0000 (UTC) (envelope-from mw@semihalf.com) Received: by mail-qk1-x72f.google.com with SMTP id z13so2194350qki.2 for ; Mon, 11 Mar 2019 01:35:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=semihalf-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=m+q2GQObguL+4V8sNF9RM4VFdlQStOagmq6ejfw/Wr4=; b=OjDNekRdXDXT/wpHYnZyj8a/hKPR5qch2In9TTHFDKKJtIu6d6xXMPmGyxQlYM81mF WXE2iUn+CsN2lXUdx2vCUy5inxqyaxWSleiXmt1cCb1WiPjpU2dsA09xLO5pAxZB/yzN JxDRibvS+r3fz41VywSF1rK0ujZmxXbuIimiLn/vi7wUJZKdqQbDIprfNxMpYauE6qlh a8c10CA0DDaY6okZ6amaVmak6y0MY01ni1m82r4r/axADNgvavJreqTNMH4OZPCvk9Ac oTwFCTVzP0bVL+8SmdP2qku+MhIkv+OB5kS8mCRWeedg1l9oMVboR8+Z3Hst35JJxjMA QA6g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=m+q2GQObguL+4V8sNF9RM4VFdlQStOagmq6ejfw/Wr4=; b=YQWrQA2b3SlNIV58jrD65qNQWq28DnyBH9CDpD4C2kSlKpUOP1gLorN5a0u6OKKyOV ZLbOm+8zlrcggyDmm5oqHiAcJv4CrVHm6jWmtBDflQe2SDhnGrxjmYbgsjTTZP1uli+/ Lkiz0G//6H44e9Usw/7SIPfF8gjBjSK7L3D4Fw1rR0tT10JSgQ8rIefy+R1w+UNX35L0 pTHxEzpAyXCDIb6m0ibXNVS8VCpE2O0C9M2BtSenW1Z6RPjMsnemRlzmSrMD/6d1S0CF yFxGTyA1yUmZs0wVM1dVth3T25UfchGV1MUJyiMT8pm9zWgfkrZGYNM8kUC3BejEuyq0 rH/A== X-Gm-Message-State: APjAAAUJDwbZ988ECKHlrlM2/2LV3WZwsDU/6RWXQUw8bs/BaK4m7TO/ 4oExfLxOUNfpqSQXmbkMWkWhv4HK5RLy07ApHXiadX5n X-Google-Smtp-Source: APXvYqwFJ2utru3PKH+z0Sn7GS0FiYgWuWfiFnzAmZVvet7lHa88iAwbhk9taPaXcE0ftefKCG5HNDTtxYQmHg2b+ow= X-Received: by 2002:a37:b105:: with SMTP id a5mr23047025qkf.298.1552293322323; Mon, 11 Mar 2019 01:35:22 -0700 (PDT) MIME-Version: 1.0 References: <79CC79B9-81AF-4563-BABE-429E6A57F476@bmalum.com> <010201686fe5047f-ed14af85-2b25-4480-a62a-a893f062eedd-000000@eu-west-1.amazonses.com> <010201686fe5047f-ed14af85-2b25-4480-a62a-a893f062eedd-000000@eu-west-1.amazo> <1548182399.2864.0@smtp.migadu.com> <1552255580.21373.0@unrelenting.technology> In-Reply-To: <1552255580.21373.0@unrelenting.technology> From: Marcin Wojtas Date: Mon, 11 Mar 2019 09:35:11 +0100 Message-ID: Subject: Re: ARM Graviton AWS Processor (AMI Image) To: Greg V Cc: Martin Karrer , "Matushevsky, Alexander" , =?UTF-8?Q?Micha=C5=82_Krawczyk?= , =?UTF-8?B?UmFmYcWCIEtvemlr?= , freebsd-arm@freebsd.org, freebsd-cloud@freebsd.org, freebsd-hackers@freebsd.org X-Rspamd-Queue-Id: 1BDEB8A608 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=semihalf-com.20150623.gappssmtp.com header.s=20150623 header.b=OjDNekRd X-Spamd-Result: default: False [-6.11 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.997,0]; R_DKIM_ALLOW(-0.20)[semihalf-com.20150623.gappssmtp.com:s=20150623]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; DMARC_NA(0.00)[semihalf.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[semihalf-com.20150623.gappssmtp.com:+]; MX_GOOD(-0.01)[ASPMX2.GOOGLEMAIL.com,ALT2.ASPMX.L.GOOGLE.com,ASPMX.L.GOOGLE.com,ALT1.ASPMX.L.GOOGLE.com,ASPMX3.GOOGLEMAIL.com]; RCPT_COUNT_SEVEN(0.00)[8]; RCVD_IN_DNSWL_NONE(0.00)[f.2.7.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; R_SPF_NA(0.00)[]; NEURAL_HAM_SHORT(-0.94)[-0.935,0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; IP_SCORE(-2.87)[ip: (-9.45), ipnet: 2607:f8b0::/32(-2.74), asn: 15169(-2.07), country: US(-0.07)] Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Mar 2019 08:35:25 -0000 +FreeBSD ENA maintainers W dniu pon., 11.03.2019 o 00:40 Greg V napisa=C5=82(a): > > On Tue, Jan 22, 2019 at 9:39 PM, Greg V > wrote: > > On Mon, Jan 21, 2019 at 1:11 PM, Martin Karrer > > wrote: > >> My question is if there are any plans yet to support the Graviton > >> ARM instances of AWS? > >> > >> We have a heavy load on FreeBSD and would also use the ARM > >> instances. Are there any other interested parties? > > > > I have tried this. It should work very well in theory, e.g. the > > network card driver (if_ena) compiles with no changes for aarch64, > > and in fact NetBSD has ported this driver and is up and running on > > these instances: https://dmesgd.nycbug.org/index.cgi?do=3Dview&id=3D462= 3 > > > > But my result with FreeBSD was: nothing on the console after > > loader.efi hands control to the kernel. > > [=E2=80=A6] > > Hello everyone, big update: > > FreeBSD/aarch64 on Amazon EC2 a1 (AWS Graviton) instances WORKS! > > https://dmesgd.nycbug.org/index.cgi?do=3Dview&id=3D4813 > > And you can try it (well, my -CURRENT build, NO WARRANTY etc) right now: > > ami-0c2829a0b82a62ca6 in eu-west-1 (Ireland) > > ----- > > So, what I had to do / what should be done / how others can help get > this into a finished state: > > 1. Serial console: > - I fixed it: https://reviews.freebsd.org/D19507 > - (I learned some things about UARTs and their support in FreeBSD, > should write a blog post about that) > > 2. aarch64 build configuration: > - if_ena network driver module should be enabled: > https://reviews.freebsd.org/D18372 > - NVMe driver should be enabled in the GENERIC kernel config (device > nvme, device nvd) > - BTW, why not also go with hw.nvme.use_nvd=3D"0" by default on > aarch64, IIRC that was done on powerpc64 > > 3. VM image build system: > - GPT+EFI should be used (amd64 was GPT with no EFI, and aarch64 was > MBR with EFI (???)): https://reviews.freebsd.org/D18371 > - bsdec2-image-upload --arm64 flag should be supported: included > above ^^ > - ec2.conf: amazon-ssm-agent shouldn't be installed when building > for aarch64 TARGET, since that's written in Go, and Go isn't ported to > FreeBSD/aarch64 yet: > > https://github.com/myfreeweb/freebsd/commit/5b530ebf7385d8320b9076cf84f50= aad01689bc > (untested patch, I actually used an interactive shell in between the > image build commands) > - qemu-aarch64-static should be used for preinstalling pkgs when > chrooting into the image: rough version included above ^^ > > 4. ENA (Elastic Network Adapter) driver: > - it works > - except there's something funky with interrupt activation, and it > hits panic("Attempt to double activation of resource id: %u\n", res_id) > (for the management IRQ) on boot, so I applied the obvious silly > workaround of "don't panic": > > https://github.com/myfreeweb/freebsd/commit/a7e7c6e48cdbdb0fdc6c4e0ba6339= 2262938e62c > - but still, it doesn't properly reactivate interrupts (and the box > becomes unreachable over the net) after going down and up again =E2=80=94 > guess what does that on boot? dhclient applying the big jumbo MTU =E2=80= =94 > so I set dhclient.conf to reject MTU changes: > > https://github.com/myfreeweb/freebsd/commit/03ec4d417b0b4252285baaf4e294c= c6d8c870f7f > > > Would be great if someone familiar with interrupts and stuff could help > debug the ena driver and make it work without these hacks :) > > > _______________________________________________ > 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 Mar 11 01:55:19 2019 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AAEB31527D22 for ; Mon, 11 Mar 2019 01:55:19 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1a.eu.mailhop.org (outbound1a.eu.mailhop.org [52.58.109.202]) (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 876B4724A3 for ; Mon, 11 Mar 2019 01:55:18 +0000 (UTC) (envelope-from ian@freebsd.org) ARC-Seal: i=1; a=rsa-sha256; t=1552269316; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=eKOj41vU1gss4WLZMVJAotSpOqw5gTZlfjn7hc9ZUNSA+tVlb+nozsP9r7ogXhoAh/yq0s9Tp4R6P Q7rGqzj7kd8SQrqjTbMSl6mEL3M9LbEW6mvRMepQRpkSJa6uY+MRRPBK3D/y1oAO7OQrZAMfRy5O8N su5porcG43fKg0lfFeDn45FZgYN6loZweLNd9hElYLjzSMN3KOYAum3x8BP7UB0l5LtBDPMcVtmdkC 5TTwOSmwK79v4TyAsolPgDqgnLqD+a9kyxT9qIdzjw60MS2EtlKsxpu0dTv6Bq8vhudAm63g+o0PDy LSY+8BgFVDIft1rqW0tV4qa5p7Lts/g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=arc-outbound20181012; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:to:from:subject:message-id:dkim-signature:from; bh=FsAWXboFWaULGO1+LrtjBa6awOyQqZwciNWg3gSU5N4=; b=gBRahjFemzqCxnPZ3GfjMRPod6trdyb+BelcpXMJn3yXwIaLeoU4dCo5F5VeWfgPyyc/tf/zt+803 AVgNw0S1N9Zt4JVd/3ybf7zlYJnxcPtfcviNQEE8wB5PojTM/u8shf8gjqUaQDLHUv54j0SgdESIoC iEsfFJGQ/D8HyZo9lURj2MexK5ZQZnGXM0Zs5v8bjLMrmjrPdNjAt41Wgkeg6NreBVckOtFDFNCP55 komuF9y/DjweqrGH+LozExLB08KWRSdIVTaQkLPDjH2K4H9Tf1++s4VFHmHP6RxI4OavUixE/R61N/ kxFJ9NnbqMNBrdT8vdsBcyLTDvpx2+w== ARC-Authentication-Results: i=1; outbound2.eu.mailhop.org; spf=softfail smtp.mailfrom=freebsd.org smtp.remote-ip=67.177.211.60; dmarc=none header.from=freebsd.org; arc=none header.oldest-pass=0; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=dkim-high; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:to:from:subject:message-id:from; bh=FsAWXboFWaULGO1+LrtjBa6awOyQqZwciNWg3gSU5N4=; b=DuV7LHmQ/g3GNNDzEgfy3oQ+ZJDVaHoNyzO6RAhk7Rk3/xQX1E4emgBnqWKFSm9yqDTojQVbvYg0O b1rZbahQzZtCGd5cRvSLvCmEfaeBMWHEeiV7z47cCldIMyS/oRGPWEzlpu6LHtze4uvZ9dyVDSjQI+ LStRTcYq1miu2lJrp7vO61rZxlOrOT9w1t20GkL1u3hspHn43NRgQYCv4BuDcFWBcwpJ46CUReHN+u dQigxzziF16hjzH3XDLTDXmaF2NKPJA8LgUGSgi1WBuX637gk7+ZTYHTepHsfDgIbxpGDj1+tPLCif qA2xSUqbGOL0gJ4Y2CXqHdqfVxPH+BA== X-MHO-RoutePath: aGlwcGll X-MHO-User: b462b7a5-43a0-11e9-803b-31925da7267c X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound2.eu.mailhop.org (Halon) with ESMTPSA id b462b7a5-43a0-11e9-803b-31925da7267c; Mon, 11 Mar 2019 01:55:14 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id x2B1tAao041276; Sun, 10 Mar 2019 19:55:10 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <6310a6e3dab9c3dfae7d23a6784f9d71f9728117.camel@freebsd.org> Subject: Re: Multiport USB hubs/switches on Raspberry Pi From: Ian Lepore To: bob prohaska , freebsd-arm@freebsd.org Date: Sun, 10 Mar 2019 19:55:10 -0600 In-Reply-To: <20190310171028.GA64290@www.zefox.net> References: <20190310171028.GA64290@www.zefox.net> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5 FreeBSD GNOME Team Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 876B4724A3 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.98 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.98)[-0.984,0]; ASN(0.00)[asn:16509, ipnet:52.58.0.0/15, country:US] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Mar 2019 01:55:19 -0000 On Sun, 2019-03-10 at 10:10 -0700, bob prohaska wrote: > Does anyone have experience using multiport USB hubs on freebsd-arm, > specifically in the context of Raspberry Pi 2 or 3? > > I'm interested in trying to use a hub/switch (not sure there's a > difference in the case of USB) to construct a terminal server for > serial console access on a small cluster of Pi's. I'd want about > seven or eight ports, each holding a USB-serial adapter that would > then connect to the GPIO UART pins on one Pi in the cluster. I've > used both USB 3.0 and USB 1.1 hubs, and in both cases odd things > seem to happen from time to time. One potential example is > > > https://www.amazon.com/AmazonBasics-Port-USB-2-0-Hub/dp/B00GGYU46O/ref=sxin_2?keywords=powered+usb+hub&pd_rd_i=B00GGYU46O&pd_rd_r=83f1e3f0-a1e6-40aa-bdd8-aa86a7c0b360&pd_rd_w=foNmt&pd_rd_wg=ncKZR&pf_rd_p=0395a9fd-d124-46c0-a48f-d8582ed1a45c&pf_rd_r=2P9WWPAZGMAA29NMVVV2&qid=1552234319&s=gateway > > > If anyone has experience along these lines or a suggestion > for/against > particular USB devices or versions I'd be curious to know. > > Thanks for reading, > > bob prohaska > I know I've connected a hub to an rpi and didn't have any trouble with it. Probably best to use a hub that has its own power brick. Also, you can get multi-port usb-serial adapters. This is my fave: https://www.amazon.com/dp/B004ETDC8K/ There are also models that are more the size and shape of a usb hub, with DB9 connectors around the edges. If you need to connect up to four bare boards like other RPIs that have .1 headers, I spotted this cool thing: https://www.amazon.com/dp/B07JW4J7KJ -- Ian From owner-freebsd-arm@freebsd.org Mon Mar 11 16:58:06 2019 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 199C415261D1 for ; Mon, 11 Mar 2019 16:58:06 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id ACFA66FDC4 for ; Mon, 11 Mar 2019 16:58:04 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (localhost [127.0.0.1]) by gndrsh.dnsmgr.net (8.13.3/8.13.3) with ESMTP id x2BGw1DJ010446; Mon, 11 Mar 2019 09:58:01 -0700 (PDT) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: (from freebsd-rwg@localhost) by gndrsh.dnsmgr.net (8.13.3/8.13.3/Submit) id x2BGw1dV010445; Mon, 11 Mar 2019 09:58:01 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201903111658.x2BGw1dV010445@ gndrsh.dnsmgr.net> Subject: Re: Multiport USB hubs/switches on Raspberry Pi In-Reply-To: <20190310171028.GA64290@www.zefox.net> To: bob prohaska Date: Mon, 11 Mar 2019 09:58:01 -0700 (PDT) CC: freebsd-arm@freebsd.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Rspamd-Queue-Id: ACFA66FDC4 X-Spamd-Bar: ++++ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [4.29 / 15.00]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_SPAM_SHORT(0.85)[0.853,0]; NEURAL_HAM_LONG(-0.13)[-0.133,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[dnsmgr.net]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.97)[0.972,0]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[cached: gndrsh.dnsmgr.net]; RCPT_COUNT_TWO(0.00)[2]; INVALID_MSGID(1.70)[]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:13868, ipnet:69.59.192.0/19, country:US]; RCVD_TLS_LAST(0.00)[]; IP_SCORE(0.00)[ip: (0.05), ipnet: 69.59.192.0/19(0.03), asn: 13868(0.01), country: US(-0.07)] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Mar 2019 16:58:06 -0000 > Does anyone have experience using multiport USB hubs on freebsd-arm, > specifically in the context of Raspberry Pi 2 or 3? > > I'm interested in trying to use a hub/switch (not sure there's a > difference in the case of USB) to construct a terminal server for > serial console access on a small cluster of Pi's. I'd want about > seven or eight ports, each holding a USB-serial adapter that would > then connect to the GPIO UART pins on one Pi in the cluster. I've > used both USB 3.0 and USB 1.1 hubs, and in both cases odd things > seem to happen from time to time. One potential example is > > > https://www.amazon.com/AmazonBasics-Port-USB-2-0-Hub/dp/B00GGYU46O/ref=sxin_2?keywords=powered+usb+hub&pd_rd_i=B00GGYU46O&pd_rd_r=83f1e3f0-a1e6-40aa-bdd8-aa86a7c0b360&pd_rd_w=foNmt&pd_rd_wg=ncKZR&pf_rd_p=0395a9fd-d124-46c0-a48f-d8582ed1a45c&pf_rd_r=2P9WWPAZGMAA29NMVVV2&qid=1552234319&s=gateway > > > If anyone has experience along these lines or a suggestion for/against > particular USB devices or versions I'd be curious to know. I am going to say some EE general issues that people run into when trying to do this. a) Good power is a must, you must provide adaquate power to all parts of any system, and that power must be delivered without IR losses or drops. (Much of the PC consumer stuff horribly overloads wires, connectors, and under utilizies proper filter capacitors (aka, the "bad caps" situation has more to do with not using proper caps than it has to do with any defects in the caps them selves, run near any caps current rating and it is dead in about 2000 hours.) I would suggest adding 5x-10x what ever the current input filter cap on each item in your cluster is to clean up the local noise. Do not try to deliver power over 24 (2 amps) or even 22 (3 amps) awg wire! Most wall warts use 24 awg wire, at an ampacity of 2 amps your just asking for lots of noise and sag. b) Good ground is as important as a), one must design a proper star connected ground layout when doing this type of stuff, any loops in the layout must be broken. Noise must be minimized on this ground system. Ground noise is a direct loss of signal noise margin, and at 3.3V ttl levels it takes very little noise to destroy the signal. c) Central power. Trying to do complicated large blobs of things like this that are powered from a bunch of wall warts is just a royal pita to get a and b right, so it is usually much better to have 1 power source for all of it. (One person resopnded to the thread about there pick and place machine, I am sure that this is what he has done in it.) > Thanks for reading, > bob prohaska -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-arm@freebsd.org Tue Mar 12 23:21:40 2019 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 647861542AEC for ; Tue, 12 Mar 2019 23:21:40 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A2B0D8B876 for ; Tue, 12 Mar 2019 23:21:39 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id x2CNKcaZ002202 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 12 Mar 2019 16:20:39 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id x2CNKcn3002201; Tue, 12 Mar 2019 16:20:38 -0700 (PDT) (envelope-from fbsd) Date: Tue, 12 Mar 2019 16:20:38 -0700 From: bob prohaska To: freebsd-arm@freebsd.org Subject: Can't read GPT header on rpi3 Message-ID: <20190312232038.GA2084@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.24 (2015-08-30) X-Rspamd-Queue-Id: A2B0D8B876 X-Spamd-Bar: ++++ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [4.47 / 15.00]; ARC_NA(0.00)[]; WWW_DOT_DOMAIN(0.50)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_SPAM_SHORT(0.82)[0.816,0]; IP_SCORE(0.16)[ip: (0.60), ipnet: 50.1.16.0/20(0.30), asn: 7065(-0.03), country: US(-0.07)]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[zefox.net]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.69)[0.692,0]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[cached: www.zefox.net]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_SPAM_LONG(0.92)[0.916,0]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US]; MID_RHS_MATCH_FROM(0.00)[]; MID_RHS_WWW(0.50)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Mar 2019 23:21:40 -0000 When rebooting an rpi3 running -current as of a couple days ago the console sometimes reports Scanning disk mmc@7e300000.blk... Scanning disk usb_mass_storage.lun0... *** ERROR: Can't read GPT header *** part_get_info_efi: *** ERROR: Invalid GPT *** *** ERROR: Can't read GPT header *** part_get_info_efi: *** ERROR: Invalid Backup GPT *** *** ERROR: Can't read GPT header *** part_get_info_efi: *** ERROR: Invalid GPT *** *** ERROR: Can't read GPT header *** and gets stuck in the loop. Power-cycling the Pi3 seems to clear the difficulty. The microSD card is relatively new, a Samsung Evo + 128GB. It's only happened about three times, so statistics are somewhat lacking. If anybody's got a suggestion for things to check please do. Thanks for reading, bob prohaska From owner-freebsd-arm@freebsd.org Thu Mar 14 10:10:50 2019 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 94187153C08C for ; Thu, 14 Mar 2019 10:10:50 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 27E1C70344 for ; Thu, 14 Mar 2019 10:10:50 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 71A6C74EB for ; Thu, 14 Mar 2019 10:10:49 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x2EAAnlw041733 for ; Thu, 14 Mar 2019 10:10:49 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x2EAAndD041732 for freebsd-arm@FreeBSD.org; Thu, 14 Mar 2019 10:10:49 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-arm@FreeBSD.org Subject: [Bug 236523] No FQDN ping from a Jail with NAT and ipfw Date: Thu, 14 Mar 2019 10:10:49 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: arm X-Bugzilla-Version: 12.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: joneum@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-arm@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Mar 2019 10:10:50 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D236523 Bug ID: 236523 Summary: No FQDN ping from a Jail with NAT and ipfw Product: Base System Version: 12.0-RELEASE Hardware: arm64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: arm Assignee: freebsd-arm@FreeBSD.org Reporter: joneum@FreeBSD.org Is there a Bug / Problem with NAT and ipfw on arm64? This config works with amd64 on FreeBSD12.0 It does not work on a RaspberryPi 3 with FreeBSD 12.0 and CURRENT / arm64 Config: /etc/rc.conf hostname=3D"rpi3project.local" keymap=3Dde ifconfig_ue0=3D"inet 192.168.2.90 netmask 255.255.255.0" defaultrouter=3D"192.168.2.1" sshd_enable=3D"YES" ntpdate_enable=3D"YES" ntpd_enable=3D"YES" # Set dumpdev to "AUTO" to enable crash dumps, "NO" to disable dumpdev=3D"AUTO" jail_enable=3D"YES" sendmail_enable=3D"NONE" sendmail_submit_enable=3D"NO" sendmail_outbound_enable=3D"NO" sendmail_msp_queue_enable=3D"NO" #IPFW firewall_enable=3D"YES" #firewall_type=3D"open" firewall_nat_enable=3D"YES" firewall_script=3D"/etc/ipfw.conf" #NAT cloned_interfaces=3D"lo1" ifconfig_lo1_alias0=3D"inet 10.0.0.1 netmask 255.255.255.0" gateway_enable=3D"YES" growfs_enable=3D"YES" ###################### /etc/jail.conf: exec.start=3D"/bin/sh /etc/rc"; exec.stop=3D"/bin/sh /etc/rc.shutdown"; exec.clean; mount.devfs; interface=3D"lo1"; jail1icinga { host.hostname =3D "jail1icinga.local"; path =3D /usr/jails/jail1icinga; ip4.addr =3D "10.0.0.1"; allow.raw_sockets=3D1; allow.chflags; allow.mount.procfs; allow.mount.devfs; } ######################### /etc/ipfw.conf: cmd=3D"/sbin/ipfw -q" lan_if=3D"ue0" ipaddr=3D"192.168.2.30/24" vm_net=3D"10.0.0.0/28" $cmd flush $cmd queue flush $cmd pipe flush $cmd add 10 check-state $cmd add 20 allow all from me to $vm_net setup keep-state # NAT $cmd nat 1 config if $lan_if $cmd add 50 nat 1 all from $vm_net to not $vm_net $cmd add 60 nat 1 all from any to $ipaddr $cmd add 70 allow all from any to any ##################### /etc/resolv.conf (maihost + jail) nameserver 192.168.2.1 ##################### # jls JID IP Address Hostname Path 1 10.0.0.1 jail1icinga.local /usr/jails/jail1icinga # jexec 1 csh root@jail1icinga:/ # ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8): 56 data bytes 64 bytes from 8.8.8.8: icmp_seq=3D0 ttl=3D124 time=3D16.328 ms 64 bytes from 8.8.8.8: icmp_seq=3D1 ttl=3D124 time=3D16.232 ms root@jail1icinga:/ # ping www.google.de ping: cannot resolve www.google.de: Host name lookup failure ####################### On a FreeBSD 12.0 / amd64 with the same config (copy) into the jail: ot # jexec 1 csh root@jail1icinga:/ # ping www.google.de PING www.google.de (172.217.16.131): 56 data bytes 64 bytes from 172.217.16.131: icmp_seq=3D0 ttl=3D57 time=3D17.520 ms 64 bytes from 172.217.16.131: icmp_seq=3D1 ttl=3D57 time=3D17.293 ms ^C --=20 You are receiving this mail because: You are the assignee for the bug.=