Re: [9fans] 9pccpu: can't open /dev/sdXX/nvram
when the hex numbers count in (2), it means its reading the kernel file from the disk into memory. 9fronts 9boot loader uses the bios for all device access. to read a single 512 byte block of data from a harddrive (or usb flash drives as they are emulated as harddrives by the bios), we switch from 32bit protected mode to realmode, do the bios call and return to protected mode copying the block from stack in low memory to its final destination. doing these single block reads might be inefficient with your bios implementation. tho it never has been a problem with ide/sata harddrives or cdroms. when it takes long from (1) to (2), this could be a problem with the usleep() code. after we read plan9.ini, we wait a bit for keyboard input so one can interrupt the automatic boot process. maybe that wait loop is not working right? > Gesendet: Donnerstag, 16. Mai 2013 um 02:16 Uhr > Von: arisawa > An: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net> > Betreff: Re: [9fans] 9pccpu: can't open /dev/sdXX/nvram > > Hello Erik, > > the problem is not in transmission speed of network. > mine is based on 9front. > messages that come from booting process is as follows: > (1) the content in plan9.ini. > (2) then single letter hexadecimal messages 0 1 ... a b .. f 0 1 ... > (3) and then "boot". the message comes from bootfat. > (4) finally "Plan9" message from the loaded kernel. > > the message (2) is very slow and takes much time to finish. > I suspect bootfat takes too much time to find a specified kernel in fat > partition. > the time is mother board dependent. > my new one is sufficiently fast, but old one (GA-G31M-S2L) is irritatingly > slow. > > Kenji Arisawa > > P.S. > I accessed http://ftp.9atom.org/other/9paecpu to try your 9atom. > however I got "Object not found". > > > On 2013/05/16, at 6:18, erik quanstrom wrote: > > > On Wed May 15 16:57:59 EDT 2013, aris...@ar.aichi-u.ac.jp wrote: > >> > >> PXE + (nvram on usb flash) is much faster than usb flash only boot. > > > > my experience has been that usb flash boot can be faster due > > to networking quirks. for example, spanning tree or even switch uplink > > connect times can be measured in many seconds. > > > > - erik > >
[9fans] Installing Go
Anyone has installed Go, the source code has Makefiles and bash scripts for building, it doesn´t seem to be for plan9.
Re: [9fans] Installing Go
Sorry, you also need to get the tip (use hg to get the latest without saying you want a release) In arm you will need lucio´s patch. On Fri, May 17, 2013 at 12:32 AM, Gorka Guardiola wrote: > You have a script called all.rc which does the work. > > G. > > > > On Fri, May 17, 2013 at 12:31 AM, lamg wrote: > >> Anyone has installed Go, the source code has Makefiles and bash >> scripts for building, it doesn´t seem to be for plan9. >> >> > > > -- > - curiosity sKilled the cat > -- - curiosity sKilled the cat
Re: [9fans] Installing Go
You have a script called all.rc which does the work. G. On Fri, May 17, 2013 at 12:31 AM, lamg wrote: > Anyone has installed Go, the source code has Makefiles and bash > scripts for building, it doesn´t seem to be for plan9. > > -- - curiosity sKilled the cat
Re: [9fans] Installing Go
To Gorka, specially, but anybody else who may wish to know: > Sorry, you also need to get the tip (use hg to get the > latest without saying you want a release) > In arm you will need lucio´s patch. I've been caught up in a lot of different things and haven't been able to focus on Go for Plan 9, but I'll try to re-focus in the next few days. I'll try out the 1.1 release as soon as I get a chance and report back here with the outcome. ++L
Re: [9fans] Installing Go
If all fails, you can try out what worked for me some time ago:
version go-93dc7f0e302b compiles out-of the box.
Prerequisites:
kernel post-Aug2012
8* suite post-March2012
VERSION file is needed if hg is not installed.
Mercurial is only needed to generate the top-level VERSION file.
You can work around this by creating the file yourself after
pulling the code from the repository.
Either create a fake VERSION file
echo fake >VERSION
or one that matches what the dist tool would have printed. With sh:
v=`hg log -r tip --template '+{node|short} {date|date}'`
echo devel $v >VERSION
Afterwards you can run tar to generate an archive that can
be moved to any system and built without Mercurial.
Cd to go/src and run:
make.rc
---
++pac
On Fri, May 17, 2013 at 7:07 AM, wrote:
> To Gorka, specially, but anybody else who may wish to know:
>
> > Sorry, you also need to get the tip (use hg to get the
> > latest without saying you want a release)
> > In arm you will need lucio´s patch.
>
> I've been caught up in a lot of different things and haven't been able
> to focus on Go for Plan 9, but I'll try to re-focus in the next few
> days.
>
> I'll try out the 1.1 release as soon as I get a chance and report back
> here with the outcome.
>
> ++L
>
>
>
