Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[MacTron]

I know that there was a few failed tries of booting Mac Os 9 on Mac Mini G4 with the iMic "Universal ROM" . I don't have any of this Macs nowadays, but I have a new suggestion if someone one is willing to try. I think the failure is because the G4 CPU is a 7447 or a 7448, so it needs the Openfirware Patch alongside the iMic "Universal ROM".
The Open Firmware commands needed are for just changing in the Device Tree the G4 CPU 7447 by 7455 or any other G4 CPU that the Mac Os 9 System knows about it . As we usually have to do when we use the 7447 or 7448 in a CPU upgrade card.
This commands were published around here... somewhere...

BTW: For the the Mac Os 8.6 fans, with this commands and a easy mod on the Mac Os ROM, may be we can boot the Mac Os 8.6 (the Sawtooth version) in to most of the Macintosh G4 family (up to QuickSilver)

*******************************************************************************************************

IMPORTANT: for those who do not want to read the many pages of this topic,
The Mac Mini OS 9.2.2 (v9 ISO Image) for booting the Mac Mini with all updates can be downloaded here:

Mac Mini Install CD Image (Version 9):
http://macos9lives.com/smforum/index.php?topic=4365.msg30502#msg30502
http://macos9lives.com/smforum/index.php?action=downloads;sa=view;down=2
*******************************************************************************************************

And, it's changed again.
Now visit http://macos9lives.com/downloads for the download.

[Knezzen]

It's worth a try! I have a 1.42ghz Mac Mini G4 here. I'll rig it up tomorrow for some tests

[mrhappy]

That would be very cool!

[MacTron]

Bad news, it seems that this was tried already, but failed 

https://www.thinkclassic.org/viewtopic.php?id=46&p=5

... but it seems that they have some success with the eMac 1.25

[Protools5LEGuy]

There were 4 Minis (PPC) http://www.everymac.com/systems/apple/mac_mini/index-macmini.html
All the seem to share the Radeon 9200 with 16 or 32 or 64 gigs of VRAM.

They all have 10/100 ethernet, DVI output and a pair of USB.

[Custos]

Just got a 1.25GHz model. There has got to be some way of getting it to boot os9. 

[Protools5LEGuy]

4 Models with 7447a proc.

http://www.everymac.com/systems/apple/mac_mini/specs/mac_mini_g4_1.25.html

http://www.everymac.com/systems/apple/mac_mini/specs/mac_mini_g4_1.42.html

http://www.everymac.com/systems/apple/mac_mini/specs/mac_mini_g4_1.33.html

http://www.everymac.com/systems/apple/mac_mini/specs/mac_mini_g4_1.5.html

The first 3 have 32 and the last 64 Mb of RAM in the same ATI 9200 that is the last ATI (at least the PCI one) that has Mac OS 9 drivers.

As MacTron said, it should need some open firmware commands to allow those 7447a proc. run in 9.

Is the northbridge, MPX, MaxBuss chipset the same than on MDD/iMac G4?

[nanopico]

4 Models with 7447a proc.

http://www.everymac.com/systems/apple/mac_mini/specs/mac_mini_g4_1.25.html

http://www.everymac.com/systems/apple/mac_mini/specs/mac_mini_g4_1.42.html

http://www.everymac.com/systems/apple/mac_mini/specs/mac_mini_g4_1.33.html

http://www.everymac.com/systems/apple/mac_mini/specs/mac_mini_g4_1.5.html

The first 3 have 32 and the last 64 Mb of RAM in the same ATI 9200 that is the last ATI (at least the PCI one) that has Mac OS 9 drivers.

As MacTron said, it should need some open firmware commands to allow those 7447a proc. run in 9.

Is the northbridge, MPX, MaxBuss chipset the same than on MDD/iMac G4?

The northbridge/chipset in the mac mini is the same that was used in the G4 iBook and All but the last revision of the G4 PowerBooks.
It's the Intrepid chip.

[androda]

By the way, anyone got a G4 mini?

Hello everyone, forum newbie here.

I just recently bought a G4 mini because of the work you guys are doing here.     It's the 1.33Ghz model, with the original restore discs (10.4.2).  I'm willing to assist in testing things on my mini as I have time.

[ELN]

Hello everyone, forum newbie here.

I just recently bought a G4 mini because of the work you guys are doing here.     It's the 1.33Ghz model, with the original restore discs (10.4.2).  I'm willing to assist in testing things on my mini as I have time.

Very selfless -- thank you!

These are some instructions that a person with an Ethernet-connected unsupported machine can follow to produce an embarrassment of debug output.

Download and burn the "Unsupported G4" image from here: http://macos9lives.com/smforum/index.php?topic=2143.0. I have instructed one user, by private message, to use an image that was probably not going to work. My apologies to that user.

Start the test machine with cmd-opt-O-F held down, until you reach the Open Firmware prompt. Choose an IP address that is on your local network but preferably outside your router's DHCP assignment range. The address 192.168.0.255 is a safe bet, and I will use it in this example. Enter the Open Firmware command (including the oddly-placed spaces):

Code: [Select]

" enet:telnet,192.168.0.255" io
On a separate OS X or Linux machine, open a terminal and Telnet into the test machine with this command:

Code: [Select]

telnet 192.168.0.255
Then, enter these commands into your terminal:

Code: [Select]

dev /
.properties
5303ffff encode-int " AAPL,debug" property
boot cd:,\\tbxi
And post the output! (Or use a pastebin-like service if you think it's too long for the forum.)

[androda]

Here's the output from telnet:

Code: [Select]

ok
0 > dev /  ok
0 > .properties
model                   PowerMac10,2
compatible              PowerMac10,2
                        MacRISC3
                        Power Macintosh

serial-number           TA9
                        G86041P6TA9
customer-sw-config
pid#                    00000282
scb#                    00000001
display-config-info     00000000 00000001
name                    device-tree
copyright               Copyright 1983-2005 Apple Computer, Inc. All Rights Reserved
device_type             bootrom
system-id               0000000000000
#address-cells          00000001
#size-cells             00000001
clock-frequency         09eb1a55
AAPL,add-fcode-file     xt=^ff86.4150
 ok
0 > 5303ffff encode-int " AAPL,debug" property  ok
0 > boot cd:,\\tbxi  can't OPEN: cd:,\\tbxi
Can't open device or file
 ok
0 > boot cd:,\\tbxi  can't OPEN: cd:,\\tbxi
Can't open device or file
 ok
0 >

I heard the CD drive spin up when I ran the command "boot cd:,\\tbxi", so it did check the disc.  As you can see, I tried the command twice and got the same results.

After this, out of curiosity I ran the command 'boot' and this is the output it gave me:

Code: [Select]

0 > boot load-size=2a8c4 adler32=86b8074c

parsing <CHRP-BOOT>

evaluating <BOOT-SCRIPT>

Following this output, the mini booted into OS X.

I did not enter all that stuff about load-size and adler32.  It just appeared after I typed 'boot' and pressed enter.  After booting into OS X, the disc was read as 'MacOS9Lives' and it had a system folder and Mac OS ROM and everything.  So I think it was burned correctly.

I think we should move to this thread for more work on this subject: http://macos9lives.com/smforum/index.php/topic,2408.0.html

[nanopico]

Here's the output from telnet:

Code: [Select]

ok
0 > dev /  ok
0 > .properties
model                   PowerMac10,2
compatible              PowerMac10,2
                        MacRISC3
                        Power Macintosh

serial-number           TA9
                        G86041P6TA9
customer-sw-config
pid#                    00000282
scb#                    00000001
display-config-info     00000000 00000001
name                    device-tree
copyright               Copyright 1983-2005 Apple Computer, Inc. All Rights Reserved
device_type             bootrom
system-id               0000000000000
#address-cells          00000001
#size-cells             00000001
clock-frequency         09eb1a55
AAPL,add-fcode-file     xt=^ff86.4150
 ok
0 > 5303ffff encode-int " AAPL,debug" property  ok
0 > boot cd:,\\tbxi  can't OPEN: cd:,\\tbxi
Can't open device or file
 ok
0 > boot cd:,\\tbxi  can't OPEN: cd:,\\tbxi
Can't open device or file
 ok
0 >

I heard the CD drive spin up when I ran the command "boot cd:,\\tbxi", so it did check the disc.  As you can see, I tried the command twice and got the same results.

After this, out of curiosity I ran the command 'boot' and this is the output it gave me:

Code: [Select]

0 > boot load-size=2a8c4 adler32=86b8074c

parsing <CHRP-BOOT>

evaluating <BOOT-SCRIPT>

Following this output, the mini booted into OS X.

I did not enter all that stuff about load-size and adler32.  It just appeared after I typed 'boot' and pressed enter.  After booting into OS X, the disc was read as 'MacOS9Lives' and it had a system folder and Mac OS ROM and everything.  So I think it was burned correctly.

I think we should move to this thread for more work on this subject: http://macos9lives.com/smforum/index.php/topic,2408.0.html

the load-size, parsing and evaluating lines are pretty standard no matter what OS you try to boot.  Both 9 and X use a CHRP script for initial loading all that says is that it's working to boot something.

It is booting X because it doesn't like something with the CD or it doesn't find a valid ROM file.  I've heard of Open firmware not mapping the CD alias correctly.  You can try ide1:,\\tbxi
Or you can try the full path to the ROM (if it is in a System Folder in the root)
Example...
boot " cd:,\System Folder\Mac OS ROM:tbxi" if that fails replace cd with ide1.

[ELN]

And if *that* fails, try this:

Code: [Select]

boot cd:,\System%20Folder\Mac%20OS%20ROM
But I suspect that your CD or your drive is no good. So if that doesn't work, I have something else for you to try.

[androda]

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

[androda]

My guess is that we need to do the NVRAM modification that's noted on the ThinkClassic forums:
https://www.thinkclassic.org/viewtopic.php?pid=4863#p4863

But even that didn't get them past the grey screen.

[androda]

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

[ELN]

Wow indeed. It's getting pretty close.

[androda]

Tried a few things this morning:
* The modified Mac OS ROM from post 120 on this page: https://www.thinkclassic.org/viewtopic.php?id=46&p=5
* The script to change processor version numbers from here: https://www.thinkclassic.org/viewtopic.php?pid=4863#p4863
* Different flag values for the AAPL,debug property (trying to get more information)
* 'words': http://pastebin.com/tRhitb8U

But alas - still stuck at the grey OS 9 screen, just like the person in the second thinkclassic link above who tested their mini.

[nanopico]

Tried a few things this morning:
* The modified Mac OS ROM from post 120 on this page: https://www.thinkclassic.org/viewtopic.php?id=46&p=5
* The script to change processor version numbers from here: https://www.thinkclassic.org/viewtopic.php?pid=4863#p4863
* Different flag values for the AAPL,debug property (trying to get more information)
* 'words': http://pastebin.com/tRhitb8U

But alas - still stuck at the grey OS 9 screen, just like the person in the second thinkclassic link above who tested their mini.

The ROM I posted here http://macos9lives.com/smforum/index.php/topic,2727.msg19816.html#msg19816
Is a modified version of the one you linked to, but it contains the scripts to update the processor version so you would not need to do that manually.

[androda]

The ROM I posted here http://macos9lives.com/smforum/index.php/topic,2727.msg19816.html#msg19816
Is a modified version of the one you linked to, but it contains the scripts to update the processor version so you would not need to do that manually.

When I try to download the file from http://www.gnerder.com/files/rom.sit I get a 404 not found error.