From: David Leimbach <leimy2k@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] plan 9 on the guruplug
Date: Mon, 30 Aug 2010 23:43:27 -0700 [thread overview]
Message-ID: <AANLkTi=ChtZjfSJfipRuB0Sck7-EBpd5beN7VYV_kXUD@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikUFXhcUgn4eHgoMHn646+hFFuj8f2rdHiR7y8L@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3863 bytes --]
The part that confuses me right now is the following set of comments in the
plug configuration file with respect to flash and nvram.
Do I need nvram or not? nvram appears to be where my boot process dies.
bootdir
boot$CONF.out boot
/arm/bin/ip/ipconfig
/arm/bin/auth/factotum
# /arm/bin/paqfs
/arm/bin/usb/usbd
# nvram not needed any longer, it's in flash
nvram
link
ether1116 ethermii
archkw
ethermedium
# no flash yet for guruplug
flashkw ecc
loopbackmedium
netdevmedium
usbehci
# sheeva plug, openrd-client, guruplug and others
# based on marvell's kirkwood soc
dev
root
cons
env
pipe
proc
mnt
srv
dup
rtc
arch
ssl
tls
cap
kprof
aoe
sd
flash
# pnp pci
ether netif
ip arp chandial ip ipv6 ipaux iproute netlog nullmedium pktmedium ptclbsum
inferno
## draw screen vga vgax
## mouse mouse
## vga
# kbmap
## kbin
uart
usb
On Mon, Aug 30, 2010 at 8:52 PM, David Leimbach <leimy2k@gmail.com> wrote:
> plug included nvram, so I'm not sure what's going on. Still trying to
> figure out if I should just be able to mount this thing from another machine
> to test.
>
>
> On Mon, Aug 30, 2010 at 8:48 PM, David Leimbach <leimy2k@gmail.com> wrote:
>
>> I just built the CONF=plug
>>
>> Let me see what that includes. Maybe my sources are just really old.
>>
>> Dave
>>
>>
>> On Mon, Aug 30, 2010 at 8:46 PM, Skip Tavakkolian <9nut@9netics.com>wrote:
>>
>>> do you compile in an nvram (that includes the correct rights?)
>>>
>>> > On Mon, Aug 30, 2010 at 7:01 PM, erik quanstrom <quanstro@quanstro.net
>>> >wrote:
>>> >
>>> >> > Just got one of these today, and I suspect my problem has nothing to
>>> do
>>> >> with
>>> >> > the guruplug and everything to do with the fact that I've never set
>>> up
>>> >> any
>>> >> > PXE bootable systems before to mount a Plan 9 CPUAUTHFS service.
>>> >> >
>>> >> > I'm getting
>>> >> > "ktrace /kernel/path 0x60806f34 0x6095cf30 0x6095cf6d # pc, sp,
>>> linkion
>>> >> > refused"
>>> >> >
>>> >> > I'm thinking that I don't have / either exported in a way I know how
>>> to
>>> >> use
>>> >> > it remotely or that I have another fundamental configuration issue.
>>> >> >
>>> >> > I'm wondering if there's a way to use either Inferno or the same
>>> plan 9
>>> >> > installation to test whatever needs testing to validate that I'll be
>>> able
>>> >> to
>>> >> > remotely boot my guruplug.
>>> >>
>>> >> once you've validated that you have a reasonable
>>> >> ipnet in /lib/ndb/local covering your network (that's
>>> >> been my problem many times; verify with ndb/ipquery
>>> >> especially that you have a fs= entry), and you've tried
>>> >> adding -Dd to bootargs (adding verbosity to
>>> >> ip/ipconfig), i usually starting hacking in debug
>>> >> messages to /sys/src/9/boot, to taste, until
>>> >> i can reduce things down to a nice consummé.
>>> >>
>>> >> if you're loading the kernel, you've gotten pretty far,
>>> >> so it sounds like dhcp/tftpd themselves are properly
>>> >> configured.
>>> >>
>>> >
>>> > Yes, the kernel loads, and prompts me for an IP for a filesystem. I
>>> enter
>>> > one, and it goes through authid, authdom, secstore and password
>>> prompts,
>>> > then it dumps me off into kdumpland
>>> >
>>> > "ktrace /kernel/path 0x60806f34 0x6095cf30 0x6095cf6d # pc, sp,
>>> > linkion refused"
>>> >
>>> > It was pretty easy to get it this far. I'm just wondering if I have my
>>> > filesystem server set up the way I originally thought, and if there is
>>> a way
>>> > to do some basic test of that.
>>> >
>>> > Example, can I attach an Inferno OS to my Plan 9 to validate if other
>>> Plan 9
>>> > instances *should* work.
>>> >
>>> > Dave
>>> >
>>> >
>>> >>
>>> >> bon appitit.
>>> >>
>>> >> - julia child
>>> >>
>>> >>
>>>
>>>
>>>
>>
>
[-- Attachment #2: Type: text/html, Size: 8659 bytes --]
next prev parent reply other threads:[~2010-08-31 6:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-31 1:45 David Leimbach
2010-08-31 2:01 ` erik quanstrom
2010-08-31 3:35 ` David Leimbach
2010-08-31 3:46 ` Skip Tavakkolian
2010-08-31 3:48 ` David Leimbach
2010-08-31 3:52 ` David Leimbach
2010-08-31 6:43 ` David Leimbach [this message]
2010-08-31 6:59 ` David Leimbach
2010-08-31 7:26 ` David Leimbach
2010-08-31 13:07 ` erik quanstrom
2010-08-31 15:07 ` David Leimbach
2010-08-31 18:19 ` David du Colombier
2010-08-31 19:52 ` David Leimbach
2010-08-31 23:06 ` hiro
2010-09-06 11:49 ` Christian Neukirchen
2010-08-31 23:14 ` David Leimbach
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='AANLkTi=ChtZjfSJfipRuB0Sck7-EBpd5beN7VYV_kXUD@mail.gmail.com' \
--to=leimy2k@gmail.com \
--cc=9fans@9fans.net \
/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).