From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eigenstate.org ([206.124.132.107]) by ewsd; Mon Jun 10 02:59:07 EDT 2019
Received: from eigenstate.org (localhost [127.0.0.1])
	by eigenstate.org (OpenSMTPD) with ESMTP id f9c529f9;
	Sun, 9 Jun 2019 23:59:06 -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=G8zEyMbC8k2v
	+dUSf6QnN6jELJA=; b=Commbu4aFJsYOna5M6ud97X6uZIDvuRILJy5sybvJsnA
	1Bl6e734IFjLQlGEMHGaZKyjbEvd2+CPpJ5oAvqAu2aeQxCInIR3vYgZJKN8ZXXq
	ImAjUTt3qwEqbzXwaZfAgALW3np72WicAwiGfLz7L3SoxD+6MiOyDRBPKZzStL4=
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=mSr7hTF9XcuOPHR1s+i
	Pzh39TqiZ9yhdrL1ugUluNbWDYmhXfWNDehT5AjPGOoS2oHvuT8qFwiRyqbadDOi
	fkLiZKw9iCV1XsksHsxp/WhQ852RuYF+dK2t4Q9xn3YtlhF+p8EnxSnve4IY8FfD
	oy7hARbWOMfsBgFJIkuEpdGo=
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 c2a49ccb (TLSv1.2:ECDHE-RSA-AES256-SHA:256:NO);
	Sun, 9 Jun 2019 23:59:06 -0700 (PDT)
Message-ID: <B84F490AE864446FE0138BCEB26C3404@eigenstate.org>
To: skhds1@gmail.com, ori@eigenstate.org
CC: 9front@9front.org
Subject: Re: [9front] Need help with configuring the Internet
Date: Sun, 9 Jun 2019 23:59:05 -0700
From: ori@eigenstate.org
In-Reply-To: CAHZWWqr2DGCSFXQk7GBBgUiE53gF_uvzAy9S3Yua4Di0XLmX4g@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: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: proxy standard pipelining control 

> Aside from all this, I managed to run confignet!
> It was done simply by running "main" on /bin/inst.
> The message I got was
> 
> "Could not find ethernet card"
> 
> This system used to run Linux and Internet worked then, so
> I'm guessing it's lack of drivers or something similar. I'm going to
> have to do a little more digging for this... (for one, I don't even know
> which ethernet card I have on my system).

Yes, you're probably right. it's likely to need a patch. Often, the
change is just adding a new PCI ID to a driver that already exists.

`pci -v` will tell you what card you have. You should see a line
like:

	0.25.0:	net  02.00.00 8086/1502   5 0:f7c00000 131072 1:f7c39000 4096 2:0000f081 32
		Intel Corporation 82579LM Gigabit Network Connection (Lewisville)

 From there, we can tell if it's a variation of something a driver
already exists for or not.