68kMLA Classic Interface
This is a version of the 68kMLA forums for viewing on your favorite old mac. Visitors on modern platforms may prefer the main site.
| Click here to select a new forum. | | Photo Request : 5500, 6500 and TAM Logic Board | Posted by: joevt on 2025-12-05 00:32:45 For 6500 and some other Macs, mac-io needs to be replaced with the actual device path for the OHare chip.
For the 5500/6500/TAM it should be pci1/ohare
I updated the script in the probe-ids.txt.zip attachment. | Posted by: joevt on 2025-12-05 01:37:26 Ok, this one should work.
I switched to using find-package because dev and find-device do extra stuff like output a beep on failure or change the active-package which we don't need to do.
But find-package doesn't know about device aliases on B&W G3 so I have to get the mac-io alias manually from the /aliases node.
find-package on 5500/6500/TAM is ok with paths that use a device alias (such as pci1/ohare). | Posted by: MacJunky on 2025-12-05 17:54:59 Okay, here is what my 6500 spit back out using dl and the latest revision of your script.

F3000034: E0 30 10 7A :.0.z:
70345261
10141211
30341221
E0A4C2E1 | Posted by: joevt on 2025-12-06 04:00:14
Okay, here is what my 6500 spit back out using dl and the latest revision of your script. Thanks for that. The info should allow DingusPPC to get the gazelle ROM to select the correct ProductInfo for a pm6500.
calcids () {
local ohareid=$1
local idoffset=0
for theids in fp mon mb cpu; do
id0=${ohareid:0+$idoffset:2}
id4=${ohareid:0+$idoffset+2:2}
id2=${ohareid:0+$idoffset+4:2}
id1=${ohareid:0+$idoffset+6:2}
((idoffset+=8))
printf "%4s_id: %s %s %s %s %03X\n" $theids $id0 $id4 $id2 $id1 $(( ((0x$id0 & 0x70) << 2) | (0x$id4 & 0x30) | ((0x$id2 & 0x40) >> 3) | ((0x$id2 & 0x10) >> 2) | ((0x$id1 & 0x60) >> 5) ))
done
}
# real Power Mac 6500 from @MacJunky
# 6500/225. It has 8MB RAM soldered onboard, overclocked to 300MHz.
# It also has a non-functional Rage Pro Turbo PCI chip soldered onto it.
calcids 703452611014121130341221E0A4C2E1
fp_id: 70 34 52 61 1FF
mon_id: 10 14 12 11 054
mb_id: 30 34 12 21 0F5
cpu_id: E0 A4 C2 E1 1AB
# DingusPPC pm6500
calcids 707070701010101030303030F0F0F0F0
fp_id: 70 70 70 70 1FF
mon_id: 10 10 10 10 054
mb_id: 30 30 30 30 0F5
cpu_id: F0 F0 F0 F0 1FF
; table of ProductInfo.CPUIDValue and extended CPU_ID pairs
FFC15230: 3024 0054
FFC15234: 3024 01FF ; DingusPPC pm6500 has this extended CPU_ID of 01FF which is wrong.
FFC15238: 3023 0000
FFC1523C: 3023 01AB ; a real Power Mac 6500 should return this CPUIDValue
FFC15240: 302B 01DF
FFC15244: 302C 01FB
FFC15248: 302D 015E
FFC1524C: 302E 01D7
FFC15250: 302F 00F5
FFC15254: 303C 018B
FFC15258: 0000 0000
FFC1525C: 0000 0000
@powermax extracted these CPUIDValues from the gazelle ROM:
CPUID BoxFlag gestaltMachineType definition
---------------------------------------------------------
$303C $1FB 507 + 6 = 513 gestaltPowerMac6500
$302E $1FA 506 + 6 = 512 gestaltPowerMac5500
$3024 $1FA 506 + 6 = 512 gestaltPowerMac5500
$302B $1FA 506 + 6 = 512 gestaltPowerMac5500
$3023 $1FB 507 + 6 = 513 gestaltPowerMac6500
$302D $1FA 506 + 6 = 512 gestaltPowerMac5500
$302C $1FA 506 + 6 = 512 gestaltPowerMac5500
$3023 $34 52 + 6 = 58 gestaltPowerMac6400
$3024 $44 68 + 6 = 74 gestaltPowerMac5400
$302B $4C 76 + 6 = 82 unknown????? // boxRiscCentris650 (76)
$302C $44 68 + 6 = 74 gestaltPowerMac5400
$302E $44 68 + 6 = 74 gestaltPowerMac5400
$302D $44 68 + 6 = 74 gestaltPowerMac5400
$3020 $3D 61 + 6 = 67 gestaltPowerMac9500
$3021 $3E 62 + 6 = 68 gestaltPowerMac7500
$3022 $3F 63 + 6 = 69 gestaltPowerMac8500
$3001 $66 102 + 6 = 108 gestaltPowerMac7200
Looks like $3023 is the one that we want.
Anyone have a 6500 that uses $303C or returns cpu_id values that differs from those of @MacJunky ?
You can see these values in the Universal Tables that is dumped by my GitHub forks
68k-mac-rom-maps rom_fiend HexFiend
gestaltPowerMac6500 (513) ; Unknown (0x303C)
gestaltPowerMac5500 (512) ; Jumanji (cpuIDRISC|$302E) (0x302E)
gestaltPowerMac5500 (512) ; Unknown (0x3024)
gestaltPowerMac5500 (512) ; Zanzibar (cpuIDRISC|$302B) (0x302B)
gestaltPowerMac6500 (513) ; Unknown (0x3023)
gestaltPowerMac5500 (512) ; Zanzibar with hard power (cpuIDRISC|$302D) (0x302D)
gestaltPowerMac5500 (512) ; Zanzibar with SuperDrive (cpuIDRISC|$302C) (0x302C)
InfoWombat20
boxPDMEvt1 (68), gestaltPowerMac5400 (74) ; Unknown (0x3024)
boxRiscCentris650 (76) ; Zanzibar (cpuIDRISC|$302B) (0x302B)
boxPDMEvt1 (68), gestaltPowerMac5400 (74) ; Zanzibar with SuperDrive (cpuIDRISC|$302C) (0x302C)
boxPDMEvt1 (68), gestaltPowerMac5400 (74) ; Jumanji (cpuIDRISC|$302E) (0x302E)
boxPDMEvt1 (68), gestaltPowerMac5400 (74) ; Zanzibar with hard power (cpuIDRISC|$302D) (0x302D)
InfoTNTProto1
boxTesseractF (62), gestaltPowerMac7500 (68) ; PowerMac 7300 (cpuIDRISC|$3021) (0x3021)
boxTesseractC (63), gestaltPowerMac8500 (69) ; PowerMac 7600/8600/9600 (cpuIDRISC|$3022) (0x3022)
boxRiscQuadra610 (102), gestaltPowerMac7200 (108) ; PowerMac 7200 (cpuIDRISC|$3001) (0x3001)
Now we just need results from TAM, 5500, 5400, etc.
Could this info have been extracted from the schematics? Maybe. For the cpu_id part of the ID, we see that the probing algorithm sets the output of each of 3 pins to 0 in turn and the result is that pin should be read back as 0, at least in the case of a real Power Mac 6500. i.e. Without setting any of the 3 pins to 0, we get 110. Setting bit 2 to 0 should return 010. Setting bit 1 to 0 should return 100. Setting bit 0 to 0 should return 110 (no change since it's always 0).
Why does DingusPPC return 111 for the cpu_id bits? It thinks that an `emmo` input is connected to bit 0 like on Power Mac G3. | Posted by: joevt on 2025-12-06 04:35:36
Could this info have been extracted from the schematics? Maybe. Probably not. I don't see in the schematic how CPU_ID0 is set to 0 unless R165 is removed? Well, I don't think anyone's shown a photo of that location on a pm6500 yet. The photo at #12 is for a 5500. | Posted by: MacJunky on 2025-12-06 13:28:51
Probably not. I don't see in the schematic how CPU_ID0 is set to 0 unless R165 is removed? Well, I don't think anyone's shown a photo of that location on a pm6500 yet. The photo at #12 is for a 5500. You probably don't need this anymore, but if anyone is interested...
| Posted by: joevt on 2025-12-06 15:17:26
Why does DingusPPC return 111 for the cpu_id bits? It thinks that an `emmo` input is connected to bit 0 like on Power Mac G3. According to the code in HWInit of gazelle ROM, the emmo pin is connected to CPU_ID2 instead of CPU_ID0.
The emmo pin starts the Serial Test Manager which exists in many (all?) Power Mac ROMs. The string "Serial Test" exists starting from the first PCI Mac to the last 32-bit New World Mac ROM. Maybe it has a different name in the 64-bit New World ROMs. If it exists in earlier ROMs, it might not have a menu.
You probably don't need this anymore, but if anyone is interested...
View attachment 93086 R165 exists so CPU_ID should be pulled high so maybe CPU_ID0 is pulled low by whatever J18 "DirectConnect" (MLB system connector) is connected to? What is DirectConnect connected to? | Posted by: MacJunky on 2025-12-06 19:47:24 R165 is tied to ground through the chassis harness and Monitor Out Board. Actually this may or may not be of note... I don't have a 6500's Monitor Out Board, the one I'm using is from a Performa 631CD. My chassis harness is PN: 590-9997 and was advertised as being from a 6400. I haven't had the case and harness that my 6500 logic board came in for quite some time.
 | Posted by: joevt on 2025-12-07 00:14:16
R165 is tied to ground through the chassis harness and Monitor Out Board. Actually this may or may not be of note... I don't have a 6500's Monitor Out Board, the one I'm using is from a Performa 631CD. My chassis harness is PN: 590-9997 and was advertised as being from a 6400. I haven't had the case and harness that my 6500 logic board came in for quite some time.
View attachment 93092View attachment 93094
I see that the cables from the motherboard that you show in #46 for the non-SCSI side of the top half of J18 (S1 to S50) has a 6 line cable for S1 to S6 and a 34 line cable for S7 to S40 and a 7 line cable from S? to S?+6 (where S?+6 ≤ S50 probably S44 to S50)?
Anyway, BOXID0 is S18 which is line 12 of the 34 line cable which you have marked in the above picture.
Do you think the 6500's Monitor Out Board is similar to that of the Performa 631CD?
I can't find documentation or images for 590-9997.
There is a note on the schematics on sheet 22 for BOXID0 which says something like "Grounds signals from 3.3V to 5V" though the first word is hard to read. BOXID1 and BOXID2 have capacitors to ground C434 and C435 but the capacitor to ground for BOXID0 C430 says "NO STUFF" which means it doesn't exist? | Posted by: MacJunky on 2025-12-07 08:34:20 Unfortunately I can't find my own pictures of my 6500's old Monitor Out Board. Zone6400 used to host a picture for differentiating between the 6400's 922-2547 and 6500's 922-2996 boards. I've attached it for reference.

The 590-9997 harness I have now is as far as I can remember basically identical in appearance to what was in my 6500, though I don't think I had that one fully out of that particular case. The part number is printed on the IDE cable.
  
I don't think Page 22 of the schematic says C430 is "NO STUFF", I think that message is for C130, as it also specifies the same for C131 and C132. On my board I have C430 stuffed, and C130-C132, C440 not stuffed as per the schematic.
| Posted by: pizzigri on 2025-12-08 04:46:47 At home I basically have every AV board made, I have to track it down and I can post pictures. | Posted by: pizzigri on 2025-12-08 13:45:49 Argh, cannot fined the box where I buried those AV boards.
A question not related, but what does VT-A and VT-B mean on page 16 of the schematic? It specifies whether one or another R or C is stuffed, I have both a 5500 and a 6500 and both are VT-B according to what R is stuffed.
Last but not least, there seems to be a third rev of the 6500 board, that uses a slightly different layout (i.e at least one electrolithic cap is replaced by a tantalum) and also uses an updated video chip. | Posted by: pizzigri on 2025-12-08 14:08:41
That's my 6500/225. It has 8MB RAM soldered onboard, and I currently have it overclocked to 300MHz. It also has a non-functional Rage Pro Turbo PCI chip soldered onto it and is utilizing a Radeon 7000 as main display graphics card. Stupid question I know, but the Pro you soldered had all the correct resistor switched to power it at 3.3V right? Since I also am going to attempt this I just wanted to be sure. | Posted by: joevt on 2025-12-08 14:25:22
A question not related, but what does VT-A and VT-B mean on page 16 of the schematic? It specifies whether one or another R or C is stuffed, I have both a 5500 and a 6500 and both are VT-B according to what R is stuffed. ATI graphics chips have PCI vendor ID 0x1002 and a device ID that usually composes of two ASCII characters.
0x4750, // GP (Rage Pro)
0x4754, // GT (Rage II)
0x4756, // GW (Rage IIc)
0x4758, // GX
0x5654, // VT
I guess VT-A and VT-B are two types of ATI graphics chips with device ID 0x5654?
The letters don't always match the product name though:
https://admin.pci-ids.ucw.cz/read/PC/1002
4654 FT Mach64 VT
5354 ST Mach 64 VT
5654 VT Mach64 VT [Video Xpression]
5655 VU 264VT3 [Mach64 VT3]
5656 VV Mach64 VT4 [Video Xpression+]
A Rage 128 document at bitsavers explains that VT-A and VT-B are two versions of a chip with device ID for VT.
https://bitsavers.computerhistory.org/components/ati/Rage_128/Rage_128_GC_Spec.pdf
I don't know if the markings on the chips indicate which version it is:
https://www.ardent-tool.com/video/ATI_Chip_Markings.html
Besides components marked [A] or [B] in the 6500 schematic on sheet 16 are resistors marked [X] which have different values for GT-A2, VT-B, and GT-B but it doesn't say what to use for VT-A?
If you have a serial cable, then maybe you can dump some info from your 5500 or 6500 or other OHare/Heathrow/Paddington machines:
probe-ids:
https://68kmla.org/bb/index.php?thr...00-6500-and-tam-logic-board.46450/post-576941
lspci for Open Firmware, dump-device-tree, etc.:
https://tinkerdifferent.com/threads/apple-network-server-macos-based-roms-found.4756/post-42356 | Posted by: MacJunky on 2025-12-09 00:44:04
Stupid question I know, but the Pro you soldered had all the correct resistor switched to power it at 3.3V right? Since I also am going to attempt this I just wanted to be sure. I went through and changed resistors and checked voltages before swapping the chip. The original still ran during this process. I also populated LC Filter [A] connected to PLLVDD using parts from the PCI card.
Perhaps I should have done a larger dump earlier?
0 > unselect-dev ok
0 > dl ok
0 > ok
0 > dev pci1 ok
0 > lspci
00:0B.0 [106B:0001] [060000] 6B100100160080220300000608200000000000000000000000000000000000000000000000000000000
00:0E.0 [1002:5159] [030000] 02105951840090020000000308200000080000880104000000008180000000000000000000000000000
00007010:88000008.F8000008
00007014:00000401.FFFFFF01
00007018:80810000.FFFF0000
00007030:80820000.FFFE0001
00:10.0 [106B:0007] [FF0000] 6B10070016000082020000FF08200000000000F30000000000000000000000000000000000000000000
00008010:F3000000.FFF80000
00:11.0 [1011:0014] [020000] 11101400040080021100000200200000010400000000808000000000000000000000000000000000000
00008810:00000401.FFFFFF81
00008814:80800000.FFFFFF80
00008830:80840000.FFFC0001
ok
0 > dev pci2 can't find device ok
0 > dev / ls
FF828518: /PowerPC,603@0
FF828D90: /chosen@0
FF828F68: /memory@0
FF8290B0: /openprom@0
FF829170: /AAPL,ROM@FFC00000
FF829388: /options@0
FF829828: /aliases@0
FF829AC0: /packages@0
FF829B48: /deblocker@0,0
FF82A270: /disk-label@0,0
FF82A7E8: /obp-tftp@0,0
FF82CA58: /mac-files@0,0
FF82D178: /mac-parts@0,0
FF82D8D8: /aix-boot@0,0
FF82DD28: /fat-files@0,0
FF82F340: /iso-9660-files@0,0
FF82FCA8: /xcoff-loader@0,0
FF830560: /terminal-emulator@0,0
FF8305F8: /bandit@F2000000
FF831BE8: /ohare@10
FF832478: /mesh@10000
FF833FA0: /sd@0,0
FF834B88: /st@0,0
FF835800: /escc@13000
FF835958: /ch-a@13020
FF835F98: /ch-b@13000
FF8365D8: /awacs@14000
FF8366C0: /swim3@15000
FF837820: /nvram@60000
FF8378F0: /ata@20000
FF838F10: /via-cuda@16000
FF839B40: /adb@0,0
FF839C30: /keyboard@0,0
FF83A470: /mouse@1,0
FF83A730: /pram@0,0
FF83A7E0: /rtc@0,0
FF83AC80: /power-mgt@0,0
FF83B378: /pci106b,1@B
FF83B550: /ATY,BlueStar@E
FF851B60: /pci1011,14@11
ok
0 > devalias
pci1 /bandit@F2000000
fd /bandit/ohare/swim3
kbd /bandit/ohare/via-cuda/adb/keyboard
mouse /bandit/ohare/via-cuda/adb/mouse
screen /bandit/ATY,264GT
ttya /bandit/ohare/escc/ch-a
ttyb /bandit/ohare/escc/ch-b
scsi /bandit/ohare/mesh
scsi-int /bandit/ohare/mesh
ata /bandit/ohare/ata
ata-int /bandit/ohare/ata
ok
0 >
0 > dump-device-tree
/
PROPERTIES:
name device-tree
model Power Macintosh
compatible AAPL,e411
MacRISC
AAPL,cpu-id 10000000
#address-cells 00000001
#size-cells 00000001
clock-frequency 02FAF080
METHODS:
make-cpu-properties dma-sync dma-map-out dma-map-in dma-free
dma-alloc map-out map-in decode-unit close open
?pdm
/PowerPC,603@0
PROPERTIES:
name PowerPC,603
device_type cpu
reg 00000000 00000000
cpu-version 00071201
clock-frequency 10642AC0
timebase-frequency 00BEBC20
reservation-granularity 00000020
tlb-sets 00000020
tlb-size 00000040
d-cache-size 00004000
i-cache-size 00004000
d-cache-sets 00000080
i-cache-sets 00000080
i-cache-block-size 00000020
d-cache-block-size 00000020
existing 00000000 80000000 80000000 80000000
available 00000000 F2000000 F4000000 0B800000 FF900000 00300000
translations F2000000 00010000 F2000000 00000028 F2800000 00001000 F2800000 00000028
F2C00000 00001000 F2C00000 00000028 F3000000 01000000 F3000000 00000028
F8000000 00001000 F8000000 00000028 FF800000 00100000 00400000 00000010
FFC00000 00400000 FFC00000 00000000
METHODS:
translate modify unmap map release claim
close open
/chosen@0
PROPERTIES:
name chosen
stdin FF8DA840
stdout FF8DA700
memory FF8DD840
mmu FF8DD900
bootpath 00
bootargs 00
/memory@0
PROPERTIES:
name memory
device_type memory
reg 00000000 08800000
available 00000000 00400000 00500000 08300000
METHODS:
release claim close open
/openprom@0
PROPERTIES:
name openprom
model Open Firmware, 2.0.3
relative-addressing
/AAPL,ROM@FFC00000
PROPERTIES:
name AAPL,ROM
device_type rom
reg FFC00000 00400000
METHODS:
load open
/options@0
PROPERTIES:
name options
little-endian? 66616C73 6500
real-mode? 66616C73 6500
auto-boot? 74727565 00
diag-switch? 66616C73 6500
fcode-debug? 66616C73 6500
oem-banner? 66616C73 6500
oem-logo? 66616C73 6500
use-nvramrc? 66616C73 6500
real-base FFFFFFFF
real-size 00100000
virt-base FFFFFFFF
virt-size 00100000
load-base 00004000
pci-probe-list FFFFFFFF
screen-#columns 00000064
screen-#rows 00000028
selftest-#megs 00000000
boot-device 2F414150 4C2C524F 4D00
boot-file 00
diag-device 66643A64 69616773 00
diag-file 00
input-device 74747961 00
output-device 74747961 00
oem-banner 00
oem-logo 00
nvramrc 00
boot-command 626F6F74 00
/aliases@0
PROPERTIES:
name aliases
pci1 2F62616E 64697440 46323030 30303030 00
fd 2F62616E 6469742F 6F686172 652F7377 696D3300
kbd 2F62616E 6469742F 6F686172 652F7669 612D6375 64612F61 64622F6B 6579626F
61726400
mouse 2F62616E 6469742F 6F686172 652F7669 612D6375 64612F61 64622F6D 6F757365
00
screen 2F62616E 6469742F 4154592C 32363447 5400
ttya 2F62616E 6469742F 6F686172 652F6573 63632F63 682D6100
ttyb 2F62616E 6469742F 6F686172 652F6573 63632F63 682D6200
scsi 2F62616E 6469742F 6F686172 652F6D65 736800
scsi-int 2F62616E 6469742F 6F686172 652F6D65 736800
ata 2F62616E 6469742F 6F686172 652F6174 6100
ata-int 2F62616E 6469742F 6F686172 652F6174 6100
/packages@0
PROPERTIES:
name packages
METHODS:
open
/packages@0/deblocker@0,0
PROPERTIES:
name deblocker
METHODS:
empty-buffers write read seek close open
/packages@0/disk-label@0,0
PROPERTIES:
name disk-label
METHODS:
load offset close open file-str part-str
dma-free dma-alloc max-transfer block-size write-blocks read-blocks
/packages@0/obp-tftp@0,0
PROPERTIES:
name obp-tftp
METHODS:
dma-free dma-alloc max-transfer block-size read-blocks load
read close open
/packages@0/mac-files@0,0
PROPERTIES:
name mac-files
METHODS:
load close open
/packages@0/mac-parts@0,0
PROPERTIES:
name mac-parts
METHODS:
load close open
/packages@0/aix-boot@0,0
PROPERTIES:
name aix-boot
METHODS:
load close open
/packages@0/fat-files@0,0
PROPERTIES:
name fat-files
METHODS:
dir load open close read-blocks seek
read dma-free dma-alloc max-transfer block-size
/packages@0/iso-9660-files@0,0
PROPERTIES:
name iso-9660-files
METHODS:
load close open dir read offset
seek read-blocks block-size dma-free dma-alloc max-transfer
/packages@0/xcoff-loader@0,0
PROPERTIES:
name xcoff-loader
METHODS:
init-program close open
/packages@0/terminal-emulator@0,0
PROPERTIES:
name terminal-emulator
iso6429-1983-colors
/bandit@F2000000
PROPERTIES:
name bandit
device_type pci
model AAPL,343S1126
AAPL,interrupts 00000016
reg F2000000 02000000
#address-cells 00000003
#size-cells 00000002
clock-frequency 01FCA055
slot-names 0000E000 41310042 31004331 00
ranges 02000000 00000000 F3000000 F3000000 00000000 01000000
01000000 00000000 00000000 F2000000 00000000 00800000
02000000 00000000 80000000 80000000 00000000 10000000
02000000 00000000 90000000 90000000 00000000 10000000
bus-range 00000000 00000000
METHODS:
encode-unit decode-unit dma-sync dma-map-out dma-map-in dma-free
dma-alloc map-out map-in close open probe-slots
req-io-addr alloc-io-addr align-io-addr req-mem-addr alloc-mem-addr align-mem-addr
map-range add-range make-assigned-addresses allocate-addresses
add-package init-packages config-l! config-l@ config-w! config-w@
config-b! config-b@
/bandit@F2000000/ohare@10
PROPERTIES:
name ohare
device_type dbdma
model AAPL,343S0172
reg 00008000 00000000 00000000 00000000 00000000
02008010 00000000 F3000000 00000000 00100000
assigned-addresses 82008010 00000000 F3000000 00000000 00100000
ranges 00000000 02008010 00000000 F3000000 00100000
#address-cells 00000001
#size-cells 00000001
vendor-id 0000106B
device-id 00000007
revision-id 00000002
class-code 00FF0000
min-grant 00000000
max-latency 00000000
devsel-speed 00000001
METHODS:
dma-sync dma-map-out dma-map-in dma-free dma-alloc decode-unit
close open init-media-bay enable-scsi-terminators
/bandit@F2000000/ohare@10/mesh@10000
PROPERTIES:
name mesh
device_type scsi
model AAPL,343S1146
reg 00010000 00000100
00008000 00000200
clock-frequency 02FAF080
AAPL,interrupts 0000000C 00000000
AAPL,connector scsi
METHODS:
show-children set-tid-lun decode-unit close open dma-sync
dma-map-out dma-map-in dma-free dma-alloc retry-cmd error?
db-rem do-cmd reset-scsi set-timeout mesh-iooffset mesh-dmaoffset
/bandit@F2000000/ohare@10/mesh@10000/sd@0,0
PROPERTIES:
name sd
device_type block
METHODS:
load write read seek close open
write-blocks read-blocks max-transfer block-size dma-sync dma-map-out
dma-map-in dma-free dma-alloc
/bandit@F2000000/ohare@10/mesh@10000/st@0,0
PROPERTIES:
name st
device_type byte
METHODS:
load seek close open write read
write-blocks read-blocks block-size max-transfer write-eof dma-free
dma-alloc dma-sync dma-map-out dma-map-in
/bandit@F2000000/ohare@10/escc@13000
PROPERTIES:
name escc
device_type escc
reg 00013000 00001000
00008400 00000400
#address-cells 00000001
ranges
METHODS:
decode-unit close open
/bandit@F2000000/ohare@10/escc@13000/ch-a@13020
PROPERTIES:
name ch-a
device_type serial
AAPL,connector modem
reg 00013020 00000020
00008400 00000100
00008500 00000100
AAPL,interrupts 0000000F 00000004 00000005
METHODS:
write read read-ahead close open
/bandit@F2000000/ohare@10/escc@13000/ch-b@13000
PROPERTIES:
name ch-b
device_type serial
AAPL,connector printer
reg 00013000 00000020
00008600 00000100
00008700 00000100
AAPL,interrupts 00000010 00000006 00000007
METHODS:
write read read-ahead close open
/bandit@F2000000/ohare@10/awacs@14000
PROPERTIES:
name awacs
device_type sound
reg 00014000 00001000
00008800 00000100
00008900 00000100
AAPL,interrupts 00000011 00000008 00000009
/bandit@F2000000/ohare@10/swim3@15000
PROPERTIES:
name swim3
device_type block
AAPL,connector floppy
reg 00015000 00001000
00008100 00000100
AAPL,interrupts 00000013 00000001
METHODS:
load read seek eject close open
read-blocks max-transfer block-size dma-sync dma-map-out dma-map-in
dma-free dma-alloc
/bandit@F2000000/ohare@10/nvram@60000
PROPERTIES:
name nvram
device_type nvram
reg 00060000 00020000
existing 00000000 00002000
/bandit@F2000000/ohare@10/ata@20000
PROPERTIES:
name ata
device_type ata
AAPL,connector ata
compatible ohare-ata
reg 00020000 00002000
00008B00 00000200
AAPL,pio-timing 00000526 00000085 00000025 00000025 00000025 00000000 00000000 00000000
AAPL,interrupts 0000000D 00000002
METHODS:
dma-sync dma-map-out dma-map-in dma-free dma-alloc decode-unit
close open ata-command atapi-command reset-atapi-bus reset-ata-bus
use-ata-interface use-atapi-interface set-timer set-device-id
/bandit@F2000000/ohare@10/via-cuda@16000
PROPERTIES:
name via-cuda
device_type cuda
reg 00016000 00002000
AAPL,interrupts 00000012
METHODS:
get-mouse read-kbd close open read write
/bandit@F2000000/ohare@10/via-cuda@16000/adb@0,0
PROPERTIES:
name adb
device_type adb
AAPL,connector adb
METHODS:
close open
/bandit@F2000000/ohare@10/via-cuda@16000/adb@0,0/keyboard@0,0
PROPERTIES:
name keyboard
device_type keyboard
reg 00000000 00000000 00000000
METHODS:
read close open reset get-key-map
/bandit@F2000000/ohare@10/via-cuda@16000/adb@0,0/mouse@1,0
PROPERTIES:
name mouse
device_type mouse
reg 00000001 00000000 00000000
#buttons 00000001
METHODS:
get-event close open mouse-button mouse-dy mouse-dx
old-button
/bandit@F2000000/ohare@10/via-cuda@16000/pram@0,0
PROPERTIES:
name pram
device_type pram
reg 00000000 00000000 00000000
/bandit@F2000000/ohare@10/via-cuda@16000/rtc@0,0
PROPERTIES:
name rtc
device_type rtc
reg 00000000 00000000 00000000
METHODS:
set-time get-time close open
/bandit@F2000000/ohare@10/via-cuda@16000/power-mgt@0,0
PROPERTIES:
name power-mgt
device_type power-mgt
reg 00000000 00000000 00000000
/bandit@F2000000/pci106b,1@B
PROPERTIES:
name pci106b,1
vendor-id 0000106B
device-id 00000001
revision-id 00000003
class-code 00060000
min-grant 00000000
max-latency 00000000
devsel-speed 00000001
fast-back-to-back
reg 00005800 00000000 00000000 00000000 00000000
/bandit@F2000000/ATY,BlueStar@E
PROPERTIES:
vendor-id 00001002
device-id 00005159
revision-id 00000000
class-code 00030000
interrupts 00000001
min-grant 00000008
max-latency 00000000
subsystem-vendor-id 00001002
subsystem-id 00000908
devsel-speed 00000001
fast-back-to-back
AAPL,interrupts 00000019
AAPL,slot-name B1
fcode-rom-offset 00000000
EDID 00FFFFFF FFFFFF00 04721100 06340082 14120103 682F1E78 2EC585A4 59499A24
125054BF EF008180 8140714F 9500950F B30081C0 A9402139 9030621A 274068B0
3600D928 1100001C 000000FD 00384C1E 5210000A 20202020 20200000 00FC0041
63657220 58323233 570A2020 000000FF 004C415A 30393034 37333631 300A00CB
ATY,Flags 0717029B
ATY,RefCLK 00006978
ATY,MCLK 00028870
ATY,SCLK 00028870
width 00000320
height 00000258
linebytes 00000400
depth 00000008
display-type 43525400
device_type display
character-set 49534F38 3835392D 3100
iso6429-1983-colors
reg 00007000 00000000 00000000 00000000 00000000
02007030 00000000 00000000 00000000 00020000
42007010 00000000 00000000 00000000 08000000
02007018 00000000 00000000 00000000 00010000
name ATY,BlueStar
model ATY,RV100
ATY,Rom# 3131332D 38353530 352D3131 3000
ATY,Card# 3130392D 38353530 302D3030 00
ATY,Fcode 312E3836 00
driver,AAPL,MacOS,PowerPC
4A6F7921 70656666 70777063 00000001 B948891A 00000000 00000000 00000000
00030002 00000000 FFFFFFFF 00000000 0000C38C 0000C38C 0000C38C 000005B0
00040400 FFFFFFFF 00000000 00000EE8 00000EC0 00000B09 0000C940 02010400
FFFFFFFF 00000000 00000000 00000000 00000522 00000080 04040400 00000000
FFFFFFFF 00000000 FFFFFFFF 00000000 FFFFFFFF 00000000 00000004 00000027
00000001 00000140 00000158 000004F0 00000001 00000003 00000000 00000000
00000000 0000000D 00000000 00000000 00000010 00000000 00000000 00000012
0000000D 00000000 00000022 00000000 00000000 00000005 0000001F 00000000
... 0000D449 bytes total
power-consumption 00000000 00000000
assigned-addresses C2007010 00000000 88000000 00000000 08000000
82007030 00000000 80820000 00000000 00020000
82007018 00000000 80810000 00000000 00010000
METHODS:
close restore draw-logo write open set-depth
disable-videomode enable-videomode show-modes set-mode
mode# ddc2ci-monitor-off ddc2ci-monitor-on ddc2-get-byte
ddc2-send-byte ddc2-set-stop ddc2-set-start read-rectangle draw-rectangle fill-rectangle
get-colors set-colors color! color@ dimensions
/bandit@F2000000/pci1011,14@11
PROPERTIES:
vendor-id 00001011
device-id 00000014
revision-id 00000011
class-code 00020000
interrupts 00000001
min-grant 00000000
max-latency 00000000
devsel-speed 00000001
fast-back-to-back
AAPL,interrupts 00000016
AAPL,slot-name E1
name pci1011,14
reg 00008800 00000000 00000000 00000000 00000000
01008810 00000000 00000000 00000000 00000080
02008814 00000000 00000000 00000000 00000080
02008830 00000000 00000000 00000000 00040000
power-consumption 00000000 00000000
assigned-addresses 81008810 00000000 00000400 00000000 00000080
82008830 00000000 80840000 00000000 00040000
82008814 00000000 80800000 00000000 00000080
ok
0 > | Posted by: joevt on 2025-12-09 05:48:03
Perhaps I should have done a larger dump earlier?
0 > unselect-dev ok
00:0B.0 [106B:0001] [060000] 6B100100160080220300000608200000000000000000000000000000000000000000000000000000000 I didn't ask for the rest before. I just figure while one is in there, why not gather the other info from Open Firmware as well?
The width of your output was truncated to 120 characters. What terminal app did you use to capture it? My lspci for Open Firmware requires width 550 or word wrap.
Most of the useful bytes were captured. If I append enough zeros, then these are the parsed results:
00:0b.0 Host bridge [0600]: Apple Inc. Bandit PowerPC host bridge [106b:0001] (rev 03)
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ >SERR- <PERR- INTx-
Latency: 32, Cache Line Size: 32 bytes
00:0e.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] RV100 [Radeon 7000 / Radeon VE] [1002:5159] (prog-if 00 [VGA controller])
Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 32, Cache Line Size: 32 bytes
Region 0: Memory at 88000000 (32-bit, prefetchable) [disabled]
Region 1: I/O ports at 0400 [disabled]
Region 2: Memory at 80810000 (32-bit, non-prefetchable) [disabled]
00007010:88000008.f8000008 Region 0: Memory at 88000000 (32-bit, prefetchable) [size=128M]
00007014:00000401.ffffff01 Region 1: I/O ports at 0400 [size=256]
00007018:80810000.ffff0000 Region 2: Memory at 80810000 (32-bit, non-prefetchable) [size=64K]
00007030:80820000.fffe0001 Expansion ROM at 80820000 [disabled] [size=128K]
00:10.0 Unassigned class [ff00]: Apple Inc. O'Hare I/O [106b:0007] (rev 02)
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR+ INTx-
Latency: 32, Cache Line Size: 32 bytes
Region 0: Memory at f3000000 (32-bit, non-prefetchable)
00008010:f3000000.fff80000 Region 0: Memory at f3000000 (32-bit, non-prefetchable) [size=512K]
00:11.0 Ethernet controller [0200]: Digital Equipment Corporation DECchip 21041 [Tulip Pass 3] [1011:0014] (rev 11)
Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 32
Region 0: I/O ports at 0400 [disabled]
Region 1: Memory at 80800000 (32-bit, non-prefetchable) [disabled]
00008810:00000401.ffffff81 Region 0: I/O ports at 0400 [size=128]
00008814:80800000.ffffff80 Region 1: Memory at 80800000 (32-bit, non-prefetchable) [size=128]
00008830:80840000.fffc0001 Expansion ROM at 80840000 [disabled] [size=256K]
You have rev 02 of O'Hare. Others have reported having rev 01. I wonder how they differ?
Is that Ethernet controller in a regular slot or the COM slot? I think the latter, since regular slots would have device numbers < 0x10. Is it a COM slot card that Apple made?
You said your built-in ATI Rage Pro Turbo is non-functional. Normally, it would be at bus:device.function 00:12.0 like below (but I'm not sure that this example is the same ATI device as your Rage Pro Turbo):
00:12.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Mach64 GT/GT-B [3D Rage I/II] [1002:4754] (rev 41) (prog-if 00 [VGA controller])
Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 32 (2000ns min), Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 0
Region 0: Memory at 81000000 (32-bit, non-prefetchable) [disabled]
Region 1: I/O ports at 2000 [disabled]
00009010:81000000.ff000000 Region 0: Memory at 81000000 (32-bit, non-prefetchable) [size=16M]
00009014:00002001.ffffff01 Region 1: I/O ports at 2000 [size=256] | Posted by: LightBulbFun on 2025-12-09 15:30:13
That's my 6500/225. It has 8MB RAM soldered onboard, and I currently have it overclocked to 300MHz. It also has a non-functional Rage Pro Turbo PCI chip soldered onto it and is utilizing a Radeon 7000 as main display graphics card.
Have you checked if the Power Macintosh 6500 BootROM has a suitable fCode image for the ATI Rage Pro? without it, it will just appear like an unflashed PC PCI card in a mac
its for similar reasons, that if you put a Wallstreet CPU card into a PDQ it will boot, but with no video, since the Wallstreet has no ROM for the PDQ's newer ATI video chip | Posted by: MacJunky on 2025-12-09 16:28:56
The width of your output was truncated to 120 characters. What terminal app did you use to capture it? My lspci for Open Firmware requires width 550 or word wrap.
You have rev 02 of O'Hare. Others have reported having rev 01. I wonder how they differ?
Is that Ethernet controller in a regular slot or the COM slot? I think the latter, since regular slots would have device numbers < 0x10. Is it a COM slot card that Apple made? Sorry about that, I forgot to enable wrapping. I was trying out minicom for this one and it has the option but I missed it.
If you'd like a fresh proper dump just say the word.
Yep, Apple branded COMM slot card.
Have you checked if the Power Macintosh 6500 BootROM has a suitable fCode image for the ATI Rage Pro? without it, it will just appear like an unflashed PC PCI card in a mac I don't think I'm capable of figuring that one out myself, I'm waiting for someone smarter to put their chip on in the other thread about upgrading ATi chip & VRAM. https://68kmla.org/bb/index.php?thr...-6500-and-possible-ati-rage-pro-upgrade.50635 | Posted by: joevt on 2025-12-09 18:48:35
If you'd like a fresh proper dump just say the word. I would accept a fresh proper dump to see if anything interesting exists beyond byte 41.
Standard PCI config registers are at least 64 bytes. All 256 is useful when a device uses config space for other registers or defines PCI capabilities.
Have you checked if the Power Macintosh 6500 BootROM has a suitable fCode image for the ATI Rage Pro? without it, it will just appear like an unflashed PC PCI card in a mac The Gazelle ROM (Open Firmware 2.0.3) has fcode for ATI device ID 0x4754
The chip in @MacJunky 's pm6500 is not detected at all (vendor/device ID for the PCI bus number:device number is FFFF:FFFF) which is a different problem. If the chip is detected but doesn't have device ID 0x4754, then we can make a nvramrc patch to make the 0x4754 fcode image load for that chip. That would be useful only if the new chip is compatible with that fcode. If it isn't, then a different fcode image would need to be loaded from disk or a new ROM SIMM would need to be created and installed to override the built in ROM. | Posted by: MacJunky on 2025-12-09 19:59:02 This is with line wrap enabled.
There are some other differences in that I put back R133, and have drives connected for testing to see if adding a custom alias for the Radeon 7000 helps with the crashing while running RAVE accelerated games that the 6500 is known for.(and we have some other thread somewhere about)
But I don't know what I am doing or what the real problem is, so don't mind me, I'm just screwing around.
Open Firmware, 2.0.3
To continue booting the MacOS type:
BYE<return>
To continue booting from the default boot device type:
BOOT<return>
ok
0 > unselect-dev ok
0 > dl ok
A > ok
A > dev pci1 ok
A > lspci
00:0B.0 [106B:0001] [060000] 6B100100160080220300000608200000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000040080000000000000C0000030000000017000000000000001F0000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000
00:0E.0 [1002:5159] [030000] 02105951840090020000000308200000080000880104000000008180000000000000000000000000000
0000002100809000082805000000000000000FF010800000000000000000000000000021008090100020600000000025020000002002F00020000000
000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000
00007010:88000008.F8000008
00007014:00000401.FFFFFF01
00007018:80810000.FFFF0000
00007030:80820000.FFFE0001
00:10.0 [106B:0007] [FF0000] 6B10070016000082020000FF08200000000000F30000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000
00008010:F3000000.FFF80000
00:11.0 [1011:0014] [020000] 11101400040080021100000200200000010400000000808000000000000000000000000000000000000
0000000000000000084800000000000000000FE01000000FF00000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000
00008810:00000401.FFFFFF81
00008814:80800000.FFFFFF80
00008830:80840000.FFFC0001
ok
A > dev / ls
FF828518: /PowerPC,603@0
FF828D90: /chosen@0
FF828F68: /memory@0
FF8290B0: /openprom@0
FF829170: /AAPL,ROM@FFC00000
FF829388: /options@0
FF829888: /aliases@0
FF829B20: /packages@0
FF829BA8: /deblocker@0,0
FF82A2D0: /disk-label@0,0
FF82A848: /obp-tftp@0,0
FF82CAB8: /mac-files@0,0
FF82D1D8: /mac-parts@0,0
FF82D938: /aix-boot@0,0
FF82DD88: /fat-files@0,0
FF82F3A0: /iso-9660-files@0,0
FF82FD08: /xcoff-loader@0,0
FF8305C0: /terminal-emulator@0,0
FF830658: /bandit@F2000000
FF831C48: /ohare@10
FF8324D8: /mesh@10000
FF834000: /sd@0,0
FF834BE8: /st@0,0
FF835860: /escc@13000
FF8359B8: /ch-a@13020
FF835FF8: /ch-b@13000
FF836638: /awacs@14000
FF836720: /swim3@15000
FF837880: /nvram@60000
FF837950: /ata@20000
FF838F48: /ata-disk@0,0
FF83A090: /via-cuda@16000
FF83ACC0: /adb@0,0
FF83ADB0: /keyboard@0,0
FF83B5F0: /mouse@1,0
FF83B8B0: /pram@0,0
FF83B960: /rtc@0,0
FF83BE00: /power-mgt@0,0
FF83C510: /pci106b,1@B
FF83C6E8: /ATY,BlueStar@E
FF852CF8: /pci1011,14@11
ok
A > devalias
pci1 /bandit@F2000000
fd /bandit/ohare/swim3
kbd /bandit/ohare/via-cuda/adb/keyboard
mouse /bandit/ohare/via-cuda/adb/mouse
screen /bandit/ATY,BlueStar@E
ttya /bandit/ohare/escc/ch-a
ttyb /bandit/ohare/escc/ch-b
scsi /bandit/ohare/mesh
scsi-int /bandit/ohare/mesh
ata /bandit/ohare/ata
ata-int /bandit/ohare/ata
ok | | < 3 > |
|