From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from cmo-0000.xspmail.jp ([202.238.198.166]) by ewsd; Sun Oct 20 02:15:28 EDT 2019 Received: from cmr-0002.xspmail.jp ([202.238.198.119]) by cmo with ESMTP id M4T2i4j51eKiSM4UviHD64; Sun, 20 Oct 2019 15:15:25 +0900 Received: from pi3L.jitaku.localdomain ([180.146.252.131]) by cmr with ESMTPA id M4UviGwDSWSOFM4UviObyx; Sun, 20 Oct 2019 15:15:25 +0900 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hera.eonet.ne.jp; s=x01; t=1571552125; i=kokamoto@hera.eonet.ne.jp; bh=LoS/d2EagpAhGkeNI7DlFvevO3gD6tXKC4Q2SmiR++0=; h=To:Subject:Date:From:In-Reply-To; b=rv5+czecTYo0482tQi+wD2wkdTLQCnvnPGKuhlzEJJI5VletfdIU4Txy9cvuJqnfC hMnaD80onXzkxp1+U1jV+C6YtfiLVYdHjCNto0rRgEy3vbegEOMwBXUoiIxpcezBna XMZtOE6Xyg3P3XO+DhW51z6QxBY5YH9bYplHySkF6+US4A/O8IAm8gAwPltiU+Fr9b 7TgUb/lR9RN3pfgUOQJDnMXWnrmv3TVc9MZzDc45wDQbBO81UrhixRAjwTmwNM5Twb q6z7HrXb7ZMRBx1BtF8KIIH5lkNJQbAG9a3dWliiTTNgff1Ozchb0R7iLVT/rxy65x 9dkMQSZlzxAuQ== Message-ID: To: 9front@9front.org Subject: Re: [9front] unofficial sdcard image for raspberry pi 4 testing Date: Sun, 20 Oct 2019 15:15:23 +0900 From: kokamoto@hera.eonet.ne.jp In-Reply-To: D2026DDA13664A93755448D8C6889272@felloff.net MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="upas-tifwdlaoecjjuitlkmmtapcfbh" List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: flexible deep-learning solution This is a multi-part message in MIME format. --upas-tifwdlaoecjjuitlkmmtapcfbh Content-Disposition: inline Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Don't warry. I'm doing it with pleasure, though I cannot concentrate myself not so long time... My problem seems to be in the difference between /net/ether0 for Richard's case and /net/etherU0 for 9front's case. I'll investigate deeper, though it may take long time... Have a good chance, cinap! Kenji --upas-tifwdlaoecjjuitlkmmtapcfbh Content-Type: message/rfc822 Content-Disposition: inline Return-Path: 9front-bounces@ewsd.inri.net Received: from cmi-0002.m.xspmail.jp (LHLO cmi-0002.xspmail.jp) (100.120.21.3) by zmbs-0041.m.xspmail.jp with LMTP; Sun, 20 Oct 2019 09:38:10 +0900 (JST) Received: from ewsd.inri.net ([107.191.116.128]) by cmi with ESMTP id LzEXibOUNgZccLzEXiMOZh; Sun, 20 Oct 2019 09:38:09 +0900 X-Country-Code: US Authentication-Results: cmi-0002.xspmail.jp; dmarc=none header.from=felloff.net; x-token-a=none; x-token-b=none Received-SPF: PASS identity=mailfrom; envelope-from="9front-bounces@ewsd.inri.net" Received: from duke.felloff.net ([216.126.196.34]) by ewsd; Sat Oct 19 20:38:04 EDT 2019 Message-ID: Date: Sun, 20 Oct 2019 02:37:56 +0200 From: cinap_lenrek@felloff.net To: 9front@9front.org In-Reply-To: FFBB6AF6C5C0855DE9737D5BF30E0CAC@hera.eonet.ne.jp MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: self-healing HTML element persistence backend Subject: Re: [9front] unofficial sdcard image for raspberry pi 4 testing Reply-To: 9front@9front.org Precedence: bulk 9front has a generic wifi layer that handles the wifi protocol details such as logging on to an access point and encryption. richard millers raspberry pi wifi driver was written in a different environemnt. so our aux/wpa, which is used to establish encryption keys to a wpa/wpa2 wirelss nework might be incompatible to richard millers driver. the error message sounds like the driver does not understand the "essid" control message wich aux/wpa uses to select the wifi network to scan and associate to by essid string. i'm currently moving to spain and have no time to look into this. sorry. -- cinap --upas-tifwdlaoecjjuitlkmmtapcfbh--