Don't use Stuffit to extract zips, it isn't the best at it.
Have you installed drivers for the ethernet portion?
I was hoping the ethernet driver would be the same has the one on the current ethernet card I use because the IC on both cards are the same number
It's about patching open firmware to get the bridge chips working. You've done that now. You're now having driver issues.
Combo cards are weird, and FW and USB can be weird and don't show properly. I'm surprised I can't see the ethernet.
Or, perhaps, start a new thread with your page 12 solution posted on top. Then that thread can be stickied and locked.I worry that this thread should have been locked with the solution posted at the end to keep it useful. It's less confusing then and if people are having issues implementing it they can spin up a new thread (for example, your issue was actually initially a problem with decompressing the file, and is now driver issues, neither... Are directly applicable to the firmware patch)
The tricky thing is that the solution that this thread is about is now buried on page 12 of 17 on this thread. It is getting harder and harder to find, and I'm the one that posted the applet
name nvram
device_type nvram
reg 0001D000 00000010
0001F000 00000200
existing 00000000 00002000I don't remember where this came from:
/bandit@F2000000/ohare@10/nvram@60000
PROPERTIES:
name nvram
device_type nvram
reg 00060000 00020000
existing 00000000 00002000{$PRAGMAC MARK -}
CONST
_ExpansionManager = $AAF3;
{$DEFINEC SIZE_CODE(size)
ORD((size) = 4) * kFourByteCode + ORD((size) = 2) * kTwoByteCode + ORD((size) = 1) * kOneByteCode
}
{$DEFINEC RESULT_SIZE(sizeCode)
BSL(sizeCode, kResultSizePhase)
}
{$DEFINEC STACK_ROUTINE_PARAMETER(whichParam, sizeCode)
BSL( sizeCode, kStackParameterPhase + ((whichParam) - 1) * kStackParameterWidth )
}
CONST
uppReadNVRAMProcInfo = kD0DispatchedPascalStackBased
+ RESULT_SIZE(SIZE_CODE(sizeof(SignedByte)))
+ STACK_ROUTINE_PARAMETER(1, SIZE_CODE(sizeof(Integer)))
+ STACK_ROUTINE_PARAMETER(2, SIZE_CODE(sizeof(LongInt)));
uppWriteNVRAMProcInfo = kD0DispatchedPascalStackBased
+ STACK_ROUTINE_PARAMETER(1, SIZE_CODE(sizeof(Integer)))
+ STACK_ROUTINE_PARAMETER(2, SIZE_CODE(sizeof(LongInt)))
+ STACK_ROUTINE_PARAMETER(3, SIZE_CODE(sizeof(SignedByte)));
kReadNVRAMSelector = $022E;
kWriteNVRAMSelector = $032F;
FUNCTION ReadNVRAMByte(offset: LongInt): SignedByte;
{$IFC TARGET_OS_MAC AND TARGET_CPU_68K AND NOT TARGET_RT_MAC_CFM}
INLINE $303C, $022E, $AAF3;
{$ELSEC}
BEGIN
ReadNVRAMByte := CallUniversalProc( GetToolboxTrapAddress( _ExpansionManager ), uppReadNVRAMProcInfo, kReadNVRAMSelector, offset);
END;
{$ENDC}
PROCEDURE WriteNVRAMByte(offset: LongInt; value: SignedByte);
{$IFC TARGET_OS_MAC AND TARGET_CPU_68K AND NOT TARGET_RT_MAC_CFM}
INLINE $303C, $032F, $AAF3;
{$ELSEC}
BEGIN
IF CallUniversalProc( GetToolboxTrapAddress( _ExpansionManager ), uppWriteNVRAMProcInfo, kWriteNVRAMSelector, offset, value ) = 0 THEN;
END;
{$ENDC}
Do you have a link for the OrangeLink FW patcher?
I extracted the patch info with this:
derez PCIBridgePatch > PCIBridgePatch.r
# No code in the resources.
mpw dumppef -do All -pi u PCIBridgePatch > PCIBridgePatch.dumppef.txt
# There's an nvram script in the PiData.
perl -nE '
if (/Unpacked PiData/../^$/) {
if (/^ *[0-9A-F]+ +([0-9A-F ]{72}) /) { print $1 . "\n" }
}
' \
PCIBridgePatch.dumppef.txt | xxd -p -r | perl -007 -pE 's/\r/\n/g;s/\x00+/|\n/g;' > PCIBridgePatch.pidata.txt
# Convert the PiData to txt (replacing nulls with |\n)supress-banner probe-all install-console
: config-l! " config-l!" $call-parent ; : config-l@ " config-l@" $call-parent ;
: check-node my-space " config-l@" $call-parent dup d# 16 >> swap h# 0000FFFF and
my-space d# 8 + " config-l@" $call-parent d# 8 >> h# 60400 = swap h# 1668 = and swap h# 100 = and ;
: my-make-properties make-properties 0 alloc-here 0 " pci" encode-cat my-space h# 2c + config-l@ -rot
2 pick h# FFFF and (u.) encode-cat " ," encode-cat rot d# 16 >> (u.) encode-cat
2dup swap 3 + swap bounds do i c@ h# 40 > if i c@ h# 20 + i c! then loop device-name
0 0 encode-2ints " power-consumption" property 0 0 my-space encode-3ints 0 0 encode-2ints encode+
0 0 my-space 2 d# 24 << or h# 10 + encode-3ints 1000 0 encode-2ints encode+ encode+ " reg" property ;
: make-nodes " assigned-addresses" delete-property
my-space dup 18 + 10100 swap config-l! 4 + dup config-l@ h# FFFFFFF4 and 2 or swap config-l!
new-device 0 0 " c,0" set-args my-make-properties 0 100000 20 claim-real swap drop dup
dup 100000 " map-range" $call-parent dup my-space h# 10 + config-l!
dup 0 my-space h# 82 d# 24 << or h# 10 + encode-3ints 1000 0 encode-2ints encode+
" assigned-addresses" property finish-device
new-device 0 0 " d,0" set-args my-make-properties dup 1000 + my-space h# 10 + config-l!
dup 1000 + 0 my-space h# 82 d# 24 << or h# 10 + encode-3ints 1000 0 encode-2ints encode+
" assigned-addresses" property finish-device
dup dup h# 10 >> or my-space h# 20 + config-l! my-space h# 3c + dup config-l@ h# 800000 or swap config-l!
" ranges" delete-property dup 0 h# 82000000 encode-3ints rot 0 h# 82000000 encode-3ints
h# 100000 0 encode-2ints encode+ encode+ " ranges" property my-space h# 18 + config-l@
dup 8 >> h# ff and swap d# 16 >> h# ff and encode-2ints " bus-range" property ;
: x ['] select-dev catch if 2drop else check-node if make-nodes then then ;
" pci1/@d" x " pci1/@e" xdump-device-tree for each patch and compare. Otherwise, there's nothing to do here except maybe figure out the real Open Firmware bug (since the patch created in this thread is just a work-around and not a real fix).
