From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-vs1-f68.google.com ([209.85.217.68]) by ewsd; Sun Jun 16 23:56:34 EDT 2019 Received: by mail-vs1-f68.google.com with SMTP id l20so5262287vsp.3 for <9front@9front.org>; Sun, 16 Jun 2019 20:56:32 -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=IedzMv74nRmjE+d3+v4n4Ejt/ELBgkGBHU03AF/HBZk=; b=pr00gjaK9p6RdeMVPndyAZZLOhGBG/I3zmdq0x+d272xC9pCOkO8H1e3lxy7HfdTkr ycbCEl+KZL9erHmp90kOO0Ks5yZZoA1jQLat7FRHY9TCikm59W2m0OZp0GUizoiuc0jH 3DoC9xutA+BUVhkcgn6n3c6fQBcFANf5Y51R86CzLOdex5LLGiUzPaKS05vNsxj2ckEg UF2F4m7XIg9MIqOvBoebg66QxBckR9/Ub+RhT0V6hAbsvKjIUDZMnXIuThkqjpDamiNO axYFad6EV3f0V421F3zexcjXqV3KOT7THsiFMvIX1+vzh3K+LjbFuWY6XtqEpEa7jd+x fy9Q== 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=IedzMv74nRmjE+d3+v4n4Ejt/ELBgkGBHU03AF/HBZk=; b=YnXm8EpiYI7f38x3EE3/3ZXN6IvCgzBOl9jxszvYI9fhr6Knn3/1ykgjDFTC8mE75P J++0hnPoQuw/8yAR8jA6yXotU/rBMS0RA8F6jP2ix/HDn8Mao8vBlvA0z19sl9hX6zfN MBEw9yHZW5ajRwQEjPvrqUT5lO+xv0Shm/IXPOKQ5SmB3EW4BdOJ0/kfkrE9ab8CL3A0 zxo9RRh6DmpaUZsPupThLt2eL52nHZikw21eU3G83oR5nXApeduSKdEUHxZLsA7Th4nO 09kPFpm2+5+5Mp2DTdz8BU00Fx+ViW//nYXUCpdyHgM6ok6+XZHYf0NMe4LyMVXYsc5d 49VQ== X-Gm-Message-State: APjAAAXx9l5Z3w97Q3+ZpNHmI6XmpA31g6AfKIfpWuvDBErVHfusrogg LkkaVfqK07+FZxbf5N1/C+EIT5Zkxx7ZbH/36yq5/g== X-Google-Smtp-Source: APXvYqzh4wwXPzbPfk5esctABnY6kBrb0e3QlrJ6LgJ49SP8UgXp5osak39TYUxzZ80ADtK0yYZW/w3CoyUity3nVpA= X-Received: by 2002:a67:cd14:: with SMTP id u20mr10229239vsl.36.1560743791260; Sun, 16 Jun 2019 20:56:31 -0700 (PDT) MIME-Version: 1.0 References: <01866E9EE3B6FD0B8643B9CCD10CE59B@felloff.net> In-Reply-To: <01866E9EE3B6FD0B8643B9CCD10CE59B@felloff.net> From: =?UTF-8?B?7Je87KSA7ZiB?= Date: Mon, 17 Jun 2019 12:56:21 +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: leveraged persistence locator 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 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