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: Tue, 11 Jun 2019 20:10:00 +0900	[thread overview]
Message-ID: <CAHZWWqpr3GM8Nf0QTkUYgpJk8FBHyiLRD1gouGepEMzaL5xLaA@mail.gmail.com> (raw)
In-Reply-To: <E36F149DBF8EE39BF8362139E1F1DEDA@eigenstate.org>

Hmm... it's still not working, (same error message)
although I'm not sure if I'm building the kernel source right.
Anyways, thanks for the suggestions and all the help,
I'll dig in more deep when I have time (I have to do some
work for my company for the time being...).

Thanks,
Joonhyeok Yeom

On Tue, Jun 11, 2019 at 12:51 AM <ori@eigenstate.org> wrote:
>
> > 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 */
>


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

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-10 15:51 ori
2019-06-11 11:10 ` 염준혁 [this message]
  -- 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  6:59 ori
2019-06-10  8:44 ` 염준혁
2019-06-10 10:58   ` 염준혁
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=CAHZWWqpr3GM8Nf0QTkUYgpJk8FBHyiLRD1gouGepEMzaL5xLaA@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).