Re: [9front] Need help with configuring the Internet

[cinap_lenrek@felloff.net]

> 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