I found something on a french Plan 9 translation site about dd'ing my nvram from my PC to a file in /sys/src/9/kw then building.
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.bootdirboot$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 flashnvramlinkether1116 ethermiiarchkwethermedium# no flash yet for guruplugflashkw eccloopbackmediumnetdevmediumusbehci# sheeva plug, openrd-client, guruplug and others# based on marvell's kirkwood socdevrootconsenvpipeprocmntsrvduprtcarchssltlscapkprofaoesdflash# pnp pciether netifip arp chandial ip ipv6 ipaux iproute netlog nullmedium pktmedium ptclbsum inferno## draw screen vga vgax## mouse mouse## vga# kbmap## kbinuartusbOn 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=plugLet me see what that includes. Maybe my sources are just really old.DaveOn 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
>>
>>