From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eigenstate.org ([206.124.132.107]) by ewsd; Mon Jun 10 11:51:55 EDT 2019 Received: from eigenstate.org (localhost [127.0.0.1]) by eigenstate.org (OpenSMTPD) with ESMTP id 667f44b4; Mon, 10 Jun 2019 08:51:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=eigenstate.org; h= message-id:to:cc:subject:date:from:in-reply-to:mime-version :content-type:content-transfer-encoding; s=mail; bh=u5/s/+wPjE4H fOlTDToyqVFLnO0=; b=crOLPlcyHsQFLmv1vH3fBsu46RmFNApdT4vSX8hteYtw QmhvzaUShGkaqQa2G6f6gdUYbg3C22rctfi8ow8/ERsdXy6qNhIjT0oW3q/4tWid YeWWco0TP7WKOXl6jRKFiv5azDwrTuz6J8tx3JySwwG6QA4J8SyRTS7k6WCXi5Q= DomainKey-Signature: a=rsa-sha1; c=nofws; d=eigenstate.org; h=message-id :to:cc:subject:date:from:in-reply-to:mime-version:content-type :content-transfer-encoding; q=dns; s=mail; b=RGdjzoYqXCxt5bBEbBk TBIKdH6qVRebFZeA8ExFh7iG3HEZv3Zwoi1lKZqS57cBIk5RBxz0b0Reo58LDTEZ pIthCseSVOx/ICsLFUS5ROK/lwS5vZIcrJzWavTVWG2JOCHACbDEDBQutn8VjLh+ hZ0Y/xhix5sXza/LwG7HYex8= Received: from abbatoir.hsd1.ca.comcast.net (c-76-21-119-139.hsd1.ca.comcast.net [76.21.119.139]) by eigenstate.org (OpenSMTPD) with ESMTPSA id 0d563db3 (TLSv1.2:ECDHE-RSA-AES256-SHA:256:NO); Mon, 10 Jun 2019 08:51:42 -0700 (PDT) Message-ID: To: skhds1@gmail.com, ori@eigenstate.org CC: 9front@9front.org Subject: Re: [9front] Need help with configuring the Internet Date: Mon, 10 Jun 2019 08:51:41 -0700 From: ori@eigenstate.org In-Reply-To: CAHZWWqqdVghJ9hgdirfuaBy+niydFdnRcM4r5qQpbCppMCwS9g@mail.gmail.com 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: social ORM package cache factory > Looking at http://fqa.9front.org/fqa3.html#3.2.3.1 (list of known > working hardware) > I can't seem to find the Ethernet hardware with vid/did of 8086/15bc. > The motherboard I'm using is relatively new (B360 D3H), so > I'm guessing either the fqa is not updated yet or the appropriate > driver isn't yet implemented. I'll try looking around for some more > information... If it was known to be working, you wouldn't have to add the PCI ID to the driver. Still, it looks like a new ID for a known chip. Try this change: diff -r b703b47e2940 sys/src/9/pc/ether82563.c --- a/sys/src/9/pc/ether82563.c Sat Jun 08 15:56:03 2019 +0930 +++ b/sys/src/9/pc/ether82563.c Mon Jun 10 08:50:44 2019 -0700 @@ -1987,6 +1987,7 @@ case 0x1570: /* i219-v */ case 0x15b8: /* i219-v */ case 0x15b9: /* i219-lm */ + case 0x15bc: /* i219-v */ case 0x15d6: /* i219-v */ case 0x15d7: /* i219-lm */ case 0x15d8: /* i219-v */