Topic: Mac OS 9 booting on: Mac mini G4 (Detailed Posts) (Read 702033 times)

Daniel · « **Reply #60 on:** October 05, 2017, 05:26:57 PM »

The name Expansion Bus Mgr suggests that something is making some incorrect assumptions about pci.

How is it failing? Is it looping forever? Did it jump to an uninitialized pointer? Did it fall off the end of its code into another function? Did it notice a problem and abort? Those seem to be the most likely crash behaviors.

nanopico · « **Reply #61 on:** October 06, 2017, 05:55:35 AM »

I was equating Expansion Bus Mgr to the ADB Bus. It's a made up name from ELN I believe.

ELN · « **Reply #62 on:** October 06, 2017, 10:06:49 PM »

The Manager in question is definitely the Expansion Bus Manager. I named the function "FIRSTFUNC" only because it sits at the very start of the Manager code.

This morning I have identified about half of the external entry points to the Manager (all via the AAF3 ExpansionBusDispatch trap, so not from the Start Manger). Check the repo. But my disassembly of the "FIRSTFUNC" still looks like this:

Code: [Select]

                      EXPANSIONBUSMGRFIRSTFUNC:
42160  4E56 0000                 Link      A6, #$0
42164  4EBA 742A                 Jsr       (* + $742C)
42168  4EBA 5074                 Jsr       __g__EXPANSIONBUSMGR_VEC0110
4216C  4EBA 2E82                 Jsr       (* + $2E84)
42170  4E5E                      Unlk      A6
42172  4E75                      Rts

It calls three functions, all within the Expansion Bus Mgr. The use of otherwise-rare JSR instructions, and the superfluous LINK/UNLK pair, reveal this to be a compiled C function. Indeed, most of the Manager is in C.

Here is a brief overview of the three functions being called:

1. Offset $49590

last function in Manager
makes NameRegistry calls
also called from unexplored function at offset $47F62
4 strings: "pci", "device-type", "name", "device-tree"

2. Offset $471DE

vector $208c/$0110 (no known name)
no other callers
1 string: "aapl,pci"

3. Offset $44FF0

no other callers
1 string: "driver-reg,AAPL,MacOS,PowerPC"

ELN · « **Reply #63 on:** October 06, 2017, 10:34:08 PM »

And here is a test ROM that squeezes debug strings between those three calls.

Expected output:

Code: [Select]

Reset system - Into the 68K fire: 0002d032 6806c9e8 
 VMAllocateMemory - creating area at 0x69000000 00080000 
 CreateArea [ 69000000 6907ffff ] ID 00170001 placed ... created
*68k: Entered fake FirstFunc
*68k: returned from 49590
*68k: returned from 471DE
*68k: returned from 44FF0 ... returning

Daniel · « **Reply #64 on:** October 07, 2017, 06:42:02 PM »

Looking at Androda's debug output, these lines caught my eye:

Code: [Select]

-- Initializing ADB information.
---- Virtual (USB-emulated) ADB detected!

The device tree has a pseudo-hid node:

Code: [Select]

ff95c4f8: /pseudo-hid
ff95c5b0:   /keyboard
ff95cc30:   /mouse
ff95d0d8:   /eject-key

And the word list contains '_adb-ihandle'.
The following are the posts that contain or link to the info I used, in the order I used them.

Quote from: androda on May 18, 2016, 05:44:07 AM

Using my Beige G3 as the driver, I restored the MacOS9Lives disc onto the Mini's hard drive. Then I booted into Open Firmware and enabled the debug output. Then I ran "mac-boot" and WOW is that a lot of debug output. It's captured here:

http://pastebin.com/GVKGjPaH

Quote from: androda on May 18, 2016, 04:17:25 AM

Specifying the entire path to the Mac OS ROM gave me different results:

Code: [Select]
0 > 5303ffff encode-int " AAPL,debug" property ok 0 > boot " cd:,\System Folder\Mac OS ROM:tbxi" load-size=2a8c4 adler32=639f2646 parsing <CHRP-BOOT> evaluating <BOOT-SCRIPT>
After these lines printed out, the OS X grey apple logo screen appeared and the Mini basically just hung there doing nothing. No additional output appeared in the console.

I know the combo drive is good in the Mini because it can read discs without an issue. I think the disc I burned is good as well, because all the expected contents show up when the disc is in the drive in the mini. But my beige g3's DVD drive doesn't read the disc - maybe the drive is just too old now.

Other things of interest: the entire device tree
Code: [Select]
0 > dev / ok 0 > ls ff899330: /cpus ff8995c0: /PowerPC,G4@0 ff899a28: /l2-cache ff89aa80: /chosen ff89ac20: /memory@0 ff89ae20: /openprom ff89af80: /client-services ff89c1b0: /rom@ff800000 ff89c368: /boot-rom@fff00000 ff89c560: /macos ff89c5f0: /options ff89c680: /aliases ff89e570: /packages ff89e608: /deblocker ff89ef58: /disk-label ff89ffc0: /obp-tftp ff8aabb0: /telnet ff8ab460: /mac-parts ff8aea88: /mac-files ff8b1c20: /hfs-plus-files ff8b7330: /fat-files ff8bab08: /iso-9660-files ff8bb918: /bootinfo-loader ff8bd588: /xcoff-loader ff8be058: /macho-loader ff8c0ec0: /pe-loader ff8c18c8: /elf-loader ff8c3818: /usb-hid-class ff8c6380: /usb-ms-class ff8c90d0: /usb-audio-class ff936bd0: /sbp2-disk ff93a740: /ata-disk ff93cd08: /atapi-disk ff93f328: /bootpath-search ff945960: /terminal-emulator ff945a28: /firewire-disk-mode ff95c4f8: /pseudo-hid ff95c5b0: /keyboard ff95cc30: /mouse ff95d0d8: /eject-key ff95d4d0: /pseudo-sound ff95d660: /multiboot ff9727b8: /diagnostics ff972850: /xmodem ff975218: /nvram@fff04000 ff9768f8: /uni-n@f8000000 ff976ab0: /hw-clock ff978048: /i2c@f8001000 ff978c48: /cereal@1c0 ff979340: /pci@f0000000 ff9ce978: /uni-north-agp@b ff9cec40: /ATY,RockHopper2Parent@10 ff9dd290: /ATY,RockHopper2_A@0 ff97a508: /pci@f2000000 ff97c8e0: /mac-io@17 ff97dd70: /interrupt-controller@40000 ff97dfe8: /gpio@50 ff97e5a8: /modem-reset@1d ff97e700: /modem-power@1c ff97e858: /extint-gpio1@9 ff97ea38: /programmer-switch@11 ff97efc0: /gpio5@6f ff97f140: /gpio6@70 ff97f2c0: /extint-gpio15@67 ff97f4b0: /escc-legacy@12000 ff97f6d8: /ch-a@12004 ff97f888: /ch-b@12000 ff97fa38: /escc@13000 ff97fc70: /ch-a@13020 ff980880: /ch-b@13000 ff9813e8: /i2s@10000 ff9815d0: /i2s-a@10000 ff981988: /sound ff9df600: /i2s-b@11000 ff981af8: /timer@15000 ff981ca0: /via-pmu@16000 ff985500: /pmu-i2c ff9864f0: /temp-monitor@190 ff986af8: /local@0 ff986c90: /remote@1 ff987230: /rtc ff987900: /power-mgt ff9dfd10: /usb-power-mgt ff987b40: /pmu-pwm-fans ff988078: /fan ff9882c0: /i2c@18000 ff988ee8: /cereal@1c0 ff9895e0: /ata-3@20000 ff98c300: /disk ff99c0e0: /usb@1a ff9a4a00: /usb@1b ff9ad378: /usb@1b,1 ff9de320: /hub@1 ff9de5b8: /keyboard@1 ff9de9e0: /mouse@2 ff9b5cf0: /usb@1b,2 ff97b708: /pci@f4000000 ff9b6178: /ata-6@d ff9b9360: /disk ff9b99c8: /firewire@e ff9c90a0: /ethernet@f ff9dfe60: /ethernet-phy ok
And all the aliases for hardware: apparently the graphics card is called a 'RockHopper'??

Code: [Select]
0 > devalias pci0 /pci@f0000000 agp /pci@f0000000 pci1 /pci@f2000000 pci2 /pci@f4000000 uni-n /uni-n ui2c /uni-n/i2c ui2c-serial /uni-n/i2c/cereal keyboard /pseudo-hid/keyboard mouse /pseudo-hid/mouse sound /pseudo-sound eject-key /pseudo-hid/eject-key nvram /nvram enet /pci@f4000000/ethernet fw /pci@f4000000/firewire cpu0 /cpus/@0 cpu1 /cpus/@1 pci /pci@f2000000 usb0 /pci@f2000000/usb@1b,1 usb1 /pci@f2000000/usb@1b usb-1a /pci@f2000000/@18 usb-1b /pci@f2000000/@19 usb-1c /pci@f2000000/@1a usb-2a /pci@f2000000/@1b usb-2b /pci@f2000000/@1b,1 usb-2c /pci@f2000000/@1b,2 hd /pci@f4000000/ata-6@d/disk@0 cd /pci@f4000000/ata-6@d/disk@1 ide0 /pci@f2000000/mac-io@17/ata-3@20000/disk@0 ide1 /pci@f2000000/mac-io@17/ata-3@20000/disk@1 ultra0 /pci@f2000000/mac-io@17/ata-4@1f000/disk@0 ultra1 /pci@f2000000/mac-io@17/ata-4@1f000/disk@1 mac-io /pci@f2000000/mac-io@17 mpic /pci@f2000000/mac-io@17/interrupt-controller scca /pci@f2000000/mac-io@17/escc/ch-a sccb /pci@f2000000/mac-io@17/escc/ch-b ki2c /pci@f2000000/mac-io@17/i2c ki2c-serial /pci@f2000000/mac-io@17/i2c/cereal via-pmu /pci@f2000000/mac-io@17/via-pmu rtc /pci@f2000000/mac-io@17/via-pmu/rtc pi2c /pci@f2000000/mac-io@17/via-pmu/pmu-i2c wireless /pci@f2000000/mac-io@17/@30000 usb2 /pci@f2000000/usb@1a fans /pci@f2000000/mac-io@17/via-pmu/pmu-pwm-fans first-boot /pci@f4000000/ata-6@d/disk second-boot /pci@f2000000/mac-io@17/ata-3@20000/disk last-boot /pci@f4000000/ethernet screen /pci@f0000000/ATY,RockHopper2Parent@10/ATY,RockHopper2_A@0

Quote from: androda on May 18, 2016, 04:17:25 AM

Specifying the entire path to the Mac OS ROM gave me different results:

Code: [Select]
0 > 5303ffff encode-int " AAPL,debug" property ok 0 > boot " cd:,\System Folder\Mac OS ROM:tbxi" load-size=2a8c4 adler32=639f2646 parsing <CHRP-BOOT> evaluating <BOOT-SCRIPT>
After these lines printed out, the OS X grey apple logo screen appeared and the Mini basically just hung there doing nothing. No additional output appeared in the console.

I know the combo drive is good in the Mini because it can read discs without an issue. I think the disc I burned is good as well, because all the expected contents show up when the disc is in the drive in the mini. But my beige g3's DVD drive doesn't read the disc - maybe the drive is just too old now.

Other things of interest: the entire device tree
Code: [Select]
0 > dev / ok 0 > ls ff899330: /cpus ff8995c0: /PowerPC,G4@0 ff899a28: /l2-cache ff89aa80: /chosen ff89ac20: /memory@0 ff89ae20: /openprom ff89af80: /client-services ff89c1b0: /rom@ff800000 ff89c368: /boot-rom@fff00000 ff89c560: /macos ff89c5f0: /options ff89c680: /aliases ff89e570: /packages ff89e608: /deblocker ff89ef58: /disk-label ff89ffc0: /obp-tftp ff8aabb0: /telnet ff8ab460: /mac-parts ff8aea88: /mac-files ff8b1c20: /hfs-plus-files ff8b7330: /fat-files ff8bab08: /iso-9660-files ff8bb918: /bootinfo-loader ff8bd588: /xcoff-loader ff8be058: /macho-loader ff8c0ec0: /pe-loader ff8c18c8: /elf-loader ff8c3818: /usb-hid-class ff8c6380: /usb-ms-class ff8c90d0: /usb-audio-class ff936bd0: /sbp2-disk ff93a740: /ata-disk ff93cd08: /atapi-disk ff93f328: /bootpath-search ff945960: /terminal-emulator ff945a28: /firewire-disk-mode ff95c4f8: /pseudo-hid ff95c5b0: /keyboard ff95cc30: /mouse ff95d0d8: /eject-key ff95d4d0: /pseudo-sound ff95d660: /multiboot ff9727b8: /diagnostics ff972850: /xmodem ff975218: /nvram@fff04000 ff9768f8: /uni-n@f8000000 ff976ab0: /hw-clock ff978048: /i2c@f8001000 ff978c48: /cereal@1c0 ff979340: /pci@f0000000 ff9ce978: /uni-north-agp@b ff9cec40: /ATY,RockHopper2Parent@10 ff9dd290: /ATY,RockHopper2_A@0 ff97a508: /pci@f2000000 ff97c8e0: /mac-io@17 ff97dd70: /interrupt-controller@40000 ff97dfe8: /gpio@50 ff97e5a8: /modem-reset@1d ff97e700: /modem-power@1c ff97e858: /extint-gpio1@9 ff97ea38: /programmer-switch@11 ff97efc0: /gpio5@6f ff97f140: /gpio6@70 ff97f2c0: /extint-gpio15@67 ff97f4b0: /escc-legacy@12000 ff97f6d8: /ch-a@12004 ff97f888: /ch-b@12000 ff97fa38: /escc@13000 ff97fc70: /ch-a@13020 ff980880: /ch-b@13000 ff9813e8: /i2s@10000 ff9815d0: /i2s-a@10000 ff981988: /sound ff9df600: /i2s-b@11000 ff981af8: /timer@15000 ff981ca0: /via-pmu@16000 ff985500: /pmu-i2c ff9864f0: /temp-monitor@190 ff986af8: /local@0 ff986c90: /remote@1 ff987230: /rtc ff987900: /power-mgt ff9dfd10: /usb-power-mgt ff987b40: /pmu-pwm-fans ff988078: /fan ff9882c0: /i2c@18000 ff988ee8: /cereal@1c0 ff9895e0: /ata-3@20000 ff98c300: /disk ff99c0e0: /usb@1a ff9a4a00: /usb@1b ff9ad378: /usb@1b,1 ff9de320: /hub@1 ff9de5b8: /keyboard@1 ff9de9e0: /mouse@2 ff9b5cf0: /usb@1b,2 ff97b708: /pci@f4000000 ff9b6178: /ata-6@d ff9b9360: /disk ff9b99c8: /firewire@e ff9c90a0: /ethernet@f ff9dfe60: /ethernet-phy ok
And all the aliases for hardware: apparently the graphics card is called a 'RockHopper'??

Code: [Select]
0 > devalias pci0 /pci@f0000000 agp /pci@f0000000 pci1 /pci@f2000000 pci2 /pci@f4000000 uni-n /uni-n ui2c /uni-n/i2c ui2c-serial /uni-n/i2c/cereal keyboard /pseudo-hid/keyboard mouse /pseudo-hid/mouse sound /pseudo-sound eject-key /pseudo-hid/eject-key nvram /nvram enet /pci@f4000000/ethernet fw /pci@f4000000/firewire cpu0 /cpus/@0 cpu1 /cpus/@1 pci /pci@f2000000 usb0 /pci@f2000000/usb@1b,1 usb1 /pci@f2000000/usb@1b usb-1a /pci@f2000000/@18 usb-1b /pci@f2000000/@19 usb-1c /pci@f2000000/@1a usb-2a /pci@f2000000/@1b usb-2b /pci@f2000000/@1b,1 usb-2c /pci@f2000000/@1b,2 hd /pci@f4000000/ata-6@d/disk@0 cd /pci@f4000000/ata-6@d/disk@1 ide0 /pci@f2000000/mac-io@17/ata-3@20000/disk@0 ide1 /pci@f2000000/mac-io@17/ata-3@20000/disk@1 ultra0 /pci@f2000000/mac-io@17/ata-4@1f000/disk@0 ultra1 /pci@f2000000/mac-io@17/ata-4@1f000/disk@1 mac-io /pci@f2000000/mac-io@17 mpic /pci@f2000000/mac-io@17/interrupt-controller scca /pci@f2000000/mac-io@17/escc/ch-a sccb /pci@f2000000/mac-io@17/escc/ch-b ki2c /pci@f2000000/mac-io@17/i2c ki2c-serial /pci@f2000000/mac-io@17/i2c/cereal via-pmu /pci@f2000000/mac-io@17/via-pmu rtc /pci@f2000000/mac-io@17/via-pmu/rtc pi2c /pci@f2000000/mac-io@17/via-pmu/pmu-i2c wireless /pci@f2000000/mac-io@17/@30000 usb2 /pci@f2000000/usb@1a fans /pci@f2000000/mac-io@17/via-pmu/pmu-pwm-fans first-boot /pci@f4000000/ata-6@d/disk second-boot /pci@f2000000/mac-io@17/ata-3@20000/disk last-boot /pci@f4000000/ethernet screen /pci@f0000000/ATY,RockHopper2Parent@10/ATY,RockHopper2_A@0

ELN · « **Reply #65 on:** October 10, 2017, 06:19:14 PM »

Quote from: ELN on October 06, 2017, 10:34:08 PM

And here is a test ROM that squeezes debug strings between those three calls.
Code: [Select]
Anyone able to try it?

ELN · « **Reply #66 on:** October 19, 2017, 02:54:00 AM »

Bumpity bump. We're making some progress here but we need testers!

Philgood · « **Reply #67 on:** October 19, 2017, 01:23:06 PM »

I have a mini Mac at work. Will try to help you.

ELN · « **Reply #68 on:** October 25, 2017, 07:41:49 PM »

Any luck? I posted a ROM a few weeks ago that still hasn't been tested.

Philgood · « **Reply #69 on:** October 26, 2017, 04:34:33 AM »

Can you guide me a little bit how i can do that?
I have a mini mac at work and could bring another mac laptop if its needed for the remote console output.

nanopico · « **Reply #70 on:** October 26, 2017, 05:57:03 AM »

Quote from: Philgood on October 26, 2017, 04:34:33 AM

Can you guide me a little bit how i can do that?
I have an mini mac at work and could bring another mac laptop if its needed for the remote console output.

Have a second Mac that can boot OS 9.
Start the mini in target disc mode.
Connect to second mac.
Download this http://macos9lives.com/smforum/index.php/topic,2143.0.html and run from the second Mac, but use the mini's disc as the install location.
Remove the installed ROM from the mini and replace with the special one provided here.
Reboot the mini into open firmware.
I don't know if all the right OF commands are in this ROM to enable boot so you might need to change the compatibility property at the root of the device tree and the cpu version in the cpu node of the device tree.
Then just type boot.

nanopico · « **Reply #71 on:** October 26, 2017, 05:58:36 AM »

Quote from: ELN on October 25, 2017, 07:41:49 PM

Any luck? I posted a ROM a few weeks ago that still hasn't been tested.

Sorry I have not gotten to this either. Been too busy making a totally awesome TRON costume for my son.

Philgood · « **Reply #72 on:** October 26, 2017, 02:30:26 PM »

Will this render the OS installation unusable afterwards?
Is there a way to reinstall the original ROM after I did that ?

Daniel · « **Reply #73 on:** October 26, 2017, 03:27:15 PM »

Everything will be fine. Neither the mac mini nor the system you use to install os9 will be affected by this meddling. As long as you don't mess with the nvram, all changes will be easily reversible.

nanopico · « **Reply #74 on:** October 27, 2017, 06:51:25 AM »

Quote from: Philgood on October 26, 2017, 02:30:26 PM

Will this render the OS installation unusable afterwards?
Is there a way to reinstall the original ROM after I did that ?

Actually it depends on the format of the drive. The drive will need to be formatted with OS 9 drivers, which it probably doesn't so you would have to reformat.
And which original ROM are you asking about? The OS 9 one which will not work at all?

But yes it is not permanent.

ry755 · « **Reply #75 on:** October 27, 2017, 09:59:13 PM »

I could also help with testing, but I don't really want to do anything that could possibly brick it. (I don't have the money to buy a new one, I'm just a broke teenager

)

ELN · « **Reply #76 on:** October 28, 2017, 12:54:47 AM »

Don’t worry, this absolutely won’t brick it.

Philgood · « **Reply #77 on:** October 28, 2017, 09:10:06 AM »

Quote from: nanopico on October 27, 2017, 06:51:25 AM

Quote from: Philgood on October 26, 2017, 02:30:26 PM
Will this render the OS installation unusable afterwards?
Is there a way to reinstall the original ROM after I did that ?

Actually it depends on the format of the drive. The drive will need to be formatted with OS 9 drivers, which it probably doesn't so you would have to reformat.
And which original ROM are you asking about? The OS 9 one which will not work at all?

But yes it is not permanent.

You're absolutely right. There is no ROM...my bad. Thanks a lot.

ELN · « **Reply #78 on:** November 06, 2017, 05:06:38 AM »

Interestingly, QEMU boots quite happily with FIRSTFUNC nopped out completely. But before we try that on the mini, could somebody please please please try that Mac OS ROM file that I recently posted?

tooloudtoowide · « **Reply #79 on:** December 01, 2017, 05:42:10 AM »

hi, I have next to me MacMini 1.42 with Restore OSX 10.4 and of course Classic enviroment for 9.2.2.

What will be steps to test/hack it to be able to boot in MacOS9? Anyone got success on MacMini?

[Software]	New version of the Hotline Connect client HotStuff released! by Knezzen	Today at 01:23:39 AM
[Development & Programming]	Grabing resources off a program by joevt	Yesterday at 05:17:54 PM
[Software]	Virtual PC Disks by Jubadub	Yesterday at 11:52:32 AM
[Development & Programming]	Think C, docs, and OS 9 by Jubadub	Yesterday at 11:48:24 AM
[Development & Programming]	Binge compiling Mac software by Jubadub	Yesterday at 10:18:55 AM
[Development & Programming]	Embedded database recommendations? by Jubadub	Yesterday at 09:56:15 AM
[Development & Programming]	I made Modern API Documentation for Mac OS 9. by sentient06	Yesterday at 07:28:23 AM
[Development & Programming]	Classic implementation of 'modern' tech by sentient06	Yesterday at 07:19:25 AM

News:

Author Topic: Mac OS 9 booting on: Mac mini G4 (Detailed Posts) (Read 702033 times)

Recent Topics