9front - general discussion about 9front
 help / color / mirror / Atom feed
From: 염준혁 <skhds1@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] Need help with configuring the Internet
Date: Mon, 17 Jun 2019 15:45:35 +0900	[thread overview]
Message-ID: <CAHZWWqrw77_0fyNn0ydkeFy4LdqaHy-HVJgxhwUGnZo0PAp_Eg@mail.gmail.com> (raw)
In-Reply-To: <C5BC8AB39EE5ABB5C75E3FD406D33B70@felloff.net>

Or perhaps there is another way to configure the net without
running confignet? I merely tried that because that was the
install step that failed...

ip/ipconfig doesn't work, but it's probably because dhcp doesn't work
in this network (I have to manually type in the ip addresses for other
systems too).
The output is:
ipconfig: no success with DHCP

As for ls /net/ether*, there is a /net/ether0, so I guess there is
ethernet afterall?
The first step for troubleshooting at
http://fqa.9front.org/fqa6.html#6.2.8 told me to do
"cat /net/ndb", which returned nothing, so I just assumed ethernet is
not working here.

Also, I should provide you cat /dev/kmseg with a screenshot, since the
messages are long
(I'm actually seeing a lot of "failed"..). However, I'm unsure of how
to attach the picture
on a mailing list like this. Is using sites like imgur.com ok?

Thanks,
Joonhyeok Yeom

On Mon, Jun 17, 2019 at 1:20 PM <cinap_lenrek@felloff.net> wrote:
>
> > I followed your instructions until reboot. What I usually do
> > for reboot is just hit ctrl+alt+del, then wait a few seconds until Plan9
> > Console pops up. Is this not the right way to reboot the system?
> > I saw this method somewhere on the Internet although I can't recall where.
>
> its fine for a netbooted terminal. for a fileserver or a terminal
> with a local disk, this can cause filesystem corruption. the way to
> reboot a machine with disk is fshalt(8).
>
> > Other than that, echo $objtype returns amd64 (I did change plan9.ini
> > to point to amd64),
> > and also the short terminal output that pops up before Plan9 Console
> > does say boot=9pc64 somewhere in the middle. So up to this point, I'm
> > assuming the
> > kernel file loaded is 64-bit Intel...
>
> looks good.
>
> > Anyways, the Internet still does not work..
>
> i have not followed that coversation.
>
> > Running /bin/inst/main, then typing in 'confignet' returns "Could not
> find ethernet card".
>
> i dont understand, you already have a installation? theres no official
> amd64 install disk. if you just want to see what ethernet devices have
> been detected you can just do:
>
> ls /net/ether*
>
> to get ip by dhcp on the first interface, you run:
>
> ip/ipconfig
>
> > I checked the line for ether82563.c at line 1986 (this is where I
> > modified, according to ori's solution)
>
> if you are unsure, you can put a "print("XXX\n");" statement there
> before the: "return i219;":
>
> how was the 0x15bc device id determined?
>
> > and the line is still there (case 0x15bc:), so I believe the changes
> > applied, although it's hard for me
> > to check if it applied to the kernel binary I'm currently running it with.
>
> ... add a print statement is the best test here... you can disassemble
> kernel binary and check, but it is unclear if that is the actual binary
> being run.
>
> > Maybe merely adding a case wasn't enough to get rid of the "Could not
> > find ethernet card"?
> > Although I expected at least some other error message when I applied
> > this change...
>
> possible, check the kernel prints:
>
> cat /dev/kmesg
>
> --
> cinap


  parent reply	other threads:[~2019-06-17  6:45 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-17  4:19 cinap_lenrek
2019-06-17  5:01 ` 염준혁
2019-06-17  6:45 ` 염준혁 [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-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: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=CAHZWWqrw77_0fyNn0ydkeFy4LdqaHy-HVJgxhwUGnZo0PAp_Eg@mail.gmail.com \
    --to=skhds1@gmail.com \
    --cc=9front@9front.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).