From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-ua1-f67.google.com ([209.85.222.67]) by ewsd; Mon Jun 17 02:45:49 EDT 2019 Received: by mail-ua1-f67.google.com with SMTP id s4so3090219uad.7 for <9front@9front.org>; Sun, 16 Jun 2019 23:45:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=OCAb6e4YK19mOUP6V60SZV7kKvEOH8dTWbOeIw4jBFM=; b=bvWoKr5kHVOHn48glue9vVj8dJ4+QK/+HzOtLm8+mp33MiuwlIacpsZbD6GxJQZjVd HjKjGtOIZJHRkDUKMdFvyj0Ak4PCU+mlBkV3WlzTCDhakrYmlKVMDl5MzqMvQS8cteUm Of4xkucNJ6wCEVo0mbir37yG94jMoVfhKYatTX6i9gUperaIILkBMIOCJxSzOlATk3CL wMJgFMLWzZAK8yIjNFjoaePH3oXUBa8oy4Ljh8m5m9tKwBRuwnl4vFwNM1r7PI3PKJFC tYTF58wpdM+I39OBmZ98MrrPU48EBTA2Ix606Z/2unDtxYRck4UFQnxVFBN1SNsiPSOn ynpA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=OCAb6e4YK19mOUP6V60SZV7kKvEOH8dTWbOeIw4jBFM=; b=p+jssdtpnE8JX0Rmy1peBsZN5PPp0zxBK5l3r9V1y7Bo5F4nUWEYxdSBGCxHGVtJGJ sOfa/2YUqKMJlBbAW8GLOyV1AJRxLu+8hl9x6tkjNlXi7OmKPWek8a/0vx9OOBQTs6yq nWAGoGiXClDYIqLcwm0dQ+7LatCpvBMr58ibXt56vbPOGwNfRC59a5s2kDbv2wBAJMyK BHwJkjP8QHOy7kbiVbrXHcjcJ04NXZEDIO94xdTJPu6NI76giXIF/v/62n925GWT8SNd T73yPNNvE4afheLkG44fdaRyq6eR60vL+jgC2CaEuDLfyzzfJqulfZptGpyQKrV14zyD vUqg== X-Gm-Message-State: APjAAAXCfzut6S3HfeOb7TNDfJrl+QKp9P4Seqzk0C9e5MFpiFbC5a9U MAST4aH0tZPRc15HELA1Jp5ay0PEkPPO0y40NlHlaftj X-Google-Smtp-Source: APXvYqxYCR6QZ3vreSKQ8TaRdahJKyVa7/iGKdvOCvZAsodAPjpPgkzADSgOn5iCCXL/TcqJ7ABwjzM2oXalUnB3eko= X-Received: by 2002:ab0:22c3:: with SMTP id z3mr7884778uam.51.1560753945418; Sun, 16 Jun 2019 23:45:45 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: =?UTF-8?B?7Je87KSA7ZiB?= Date: Mon, 17 Jun 2019 15:45:35 +0900 Message-ID: Subject: Re: [9front] Need help with configuring the Internet To: 9front@9front.org Content-Type: text/plain; charset="UTF-8" List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: lifecycle-scale method controller 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 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