--- Begin Message ---
Rainer Dorsch a *crit :
> Guillaume,
>
> I have seen in a post of you in deja news, that you are running linux on a max
> 9500. Are you using quik to boot it? If yes, could you send me the output of
stock 9500/132 with dual 604e nPower 360+ from Daystar (running on both
processors under linux)
>
> nvsetenv on your system.
Here it is :
little-endian? false
real-mode? false
auto-boot? true
diag-switch? false
fcode-debug? false
oem-banner? false
oem-logo? false
use-nvramrc? true
real-base 0x3f00000
real-size 0x100000
virt-base 0xffffffff
virt-size 0x100000
load-base 0x4000
pci-probe-list 0xffffffff
screen-#columns 0x64
screen-#rows 0x28
selftest-#megs 0x0
boot-device scsi-int/sd@0:0
boot-file
diag-device fd:diags
diag-file
input-device ttya
output-device ttya
oem-banner
oem-logo
nvramrc : '& get-token drop ;
: >& dup @ 6 << 6 >>a -4 and + ;
: & na+ >& ;
6ED '& execute
0 value mi
: mmr " map-range" mi if my-self $call-method else $call-parent
then ;
89B '& ' mmr BRpatch
: mcm -1 to mi $call-method 0 to mi ;
8CB '& 1E na+ ' mcm BLpatch
: maa -1 to mi 1D swap ;
8C9 '& 5 na+ ' maa BLpatch
8C9 '& 134 + ' 1 BLpatch
8CD '& 184 + dup 14 + >& BRpatch
8C6 '& 7C + ' u< BLpatch
0 value yn
: y yn 0= if dup @ to yn then ;
8CB '& ' y BRpatch
' y 28 + 8CB '& 8 + BRpatch
: z yn ?dup if over ! 0 to yn then ;
8CC '& ' z BRpatch
' z 2C + 8CC '& 8 + BRpatch
boot-command begin ['] boot catch 1000 ms cr again
what's interesting is:
boot-device scsi-int/sd@0:0
don't need to explain this...
boot-command begin ['] boot catch 1000 ms cr again
like this tou don't have to reset the computer when it is cold booting
input-device ttya
output-device ttya
unfortunately, I couldn't find good values for these, kbd works but I can't
output to the ATI (too much PCO slots...)
eventually you put the name of your kernel image in boot-file (quik can read it
according to the man page)
Bye,
GoM
--- End Message ---