From: 염준혁 <skhds1@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] Need help with configuring the Internet
Date: Mon, 17 Jun 2019 12:56:21 +0900 [thread overview]
Message-ID: <CAHZWWqrn=m3yFRHh_Gh701qsTON8Gsfk=BcaTpgc9Y_LL9t59g@mail.gmail.com> (raw)
In-Reply-To: <01866E9EE3B6FD0B8643B9CCD10CE59B@felloff.net>
Sorry for the late response. I was busy with the company work
(and got exhausted after), so I wasn't able to touch the system.
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.
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...
Anyways, the Internet still does not work..
Running /bin/inst/main, then typing in 'confignet' returns "Could not
find ethernet card".
I checked the line for ether82563.c at line 1986 (this is where I
modified, according to ori's solution)
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.
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...
Oh, and thanks for your help. After I somehow get the Internet
working, I'll try the bootloader trick.
Thanks,
Joonhyeok Yeom.
On Fri, Jun 14, 2019 at 10:17 AM <cinap_lenrek@felloff.net> wrote:
>
>
> > 4. (I'm not sure if i did 9fs 9fat again..)
>
> > rm /n/9fat/9bootfat
> > cp /386/9bootfat /n/9fat/
> > chmod +al /n/9fat/9bootfat # defrag magic
>
> this is unnecessary. as you'r reinstalling the BOOTLOADER here.
> it changes so unfrequently that; i'd say unless you need it fixed;
> you never need todo this.
>
> > One thing I didn't do, was mk install one more time on
> > /sys/src/9/pc64. I assumed mk install on
> > /sys/src will create every necessary binaries, including the ones for
> > /sys/src/9/pc64. So is that
> > a necessary step?
>
> yes, this is necessary. running mk in /sys/src only compiles the
> userspace binaries (and libraries) for the current $objtype arch.
> however, there are multiple kernels per architecture so these
> need to be build explicitely.
>
> the kernel build copies some userspace programs into the kernel
> during build such as disk fileservers and utilities like
> ipconfig. it also shares libc with userspace. so having
> /sys/src built is a prerequirement for then building a kernel.
>
> anyway, to build the kernel you just do:
>
> cd /sys/src/9/pc64
> mk install
>
> then the resulting kernel file is /amd64/9pc64 which you can
> then copy to 9fat:
>
> 9fs 9fat
> cp /amd64/9pc64 /n/9fat
>
> now you can reboot. hit any key until you see the > prompt
> (this is the bootloader) and then type:
>
> bootfile=9pc64
> boot
>
> you'r now running amd64 kernel. if that worked, you can mount
> 9fat again and change plan9.ini to always point to 9pc64
> instead of the 386 kernel (9pc) by changingt the bootfile=
> line.
>
> a little trick. the plan9 partition has the 9fat right
> at its start. so it is possible to mount the 9fat from
> linux or windows. this can be handy in case you need to
> edit plan9.ini... or restore a working kernel in case you
> messed one up. so you might skip the bootloader step
> above and edit bootfile= line in plan9.ini right away
> if you have some other way to access the 9fat.
>
> good luck.
>
> --
> cinap
next prev parent reply other threads:[~2019-06-17 3:56 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-14 1:16 cinap_lenrek
2019-06-17 3:56 ` 염준혁 [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-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='CAHZWWqrn=m3yFRHh_Gh701qsTON8Gsfk=BcaTpgc9Y_LL9t59g@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).