9front - general discussion about 9front
 help / color / mirror / Atom feed
From: 염준혁 <skhds1@gmail.com>
To: ori@eigenstate.org
Cc: 9front@9front.org
Subject: Re: [9front] Need help with configuring the Internet
Date: Mon, 10 Jun 2019 17:44:05 +0900	[thread overview]
Message-ID: <CAHZWWqo8ebbSFGSNgPXe3j5xo5pKdm-wFDPU40zqJO_JiubvEw@mail.gmail.com> (raw)
In-Reply-To: <B84F490AE864446FE0138BCEB26C3404@eigenstate.org>

This is what I have when I type in 'pci -v' :

0.31.6: net 02.00.00 8086/15bc 11 0:a1100000 131072
       Intel Corporation Ethernet Connection (7) I219-V

So I'm assuming this is the case where the driver is there,
and I just need to add the PCI ID to the driver?

On Mon, Jun 10, 2019 at 3:59 PM <ori@eigenstate.org> wrote:
>
> > 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.
>


  reply	other threads:[~2019-06-10  8:44 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-10  6:59 ori
2019-06-10  8:44 ` 염준혁 [this message]
2019-06-10 10:58   ` 염준혁
  -- strict thread matches above, loose matches on Subject: below --
2019-06-17  7:24 cinap_lenrek
2019-06-17  8:59 ` 염준혁
2019-06-17  6:58 cinap_lenrek
2019-06-17  7:21 ` 염준혁
2019-06-17  4:19 cinap_lenrek
2019-06-17  5:01 ` 염준혁
2019-06-17  6:45 ` 염준혁
2019-06-14  1:16 cinap_lenrek
2019-06-17  3:56 ` 염준혁
2019-06-13  8:48 ori
2019-06-14  0:52 ` 염준혁
2019-06-14 13:35   ` hiro
2019-06-11 16:15 ori
2019-06-12  1:14 ` 염준혁
2019-06-12  9:25   ` hiro
2019-06-11  9:49 vp
2019-06-11 13:26 ` 염준혁
2019-06-10 15:51 ori
2019-06-11 11:10 ` 염준혁
2019-06-10  6:54 ori
2019-06-10  6:43 vp
2019-06-10 12:47 ` Ethan Gardener
2019-06-07  5:00 ori
2019-06-10  4:46 ` 염준혁
2019-06-10  5:30   ` 염준혁
2019-06-07  4:46 염준혁
2019-06-07  5:34 ` [9front] " Stanley Lieber

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAHZWWqo8ebbSFGSNgPXe3j5xo5pKdm-wFDPU40zqJO_JiubvEw@mail.gmail.com \
    --to=skhds1@gmail.com \
    --cc=9front@9front.org \
    --cc=ori@eigenstate.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).