Please login or register.

Login with username, password and session length
Advanced search  

News:

Pages: [1]   Go Down

Author Topic: Sound on a PowerBook G4 12" 867 (PowerBook6,1)  (Read 1515 times)

knobsnswitches

  • 4 MB
  • **
  • Posts: 7
Sound on a PowerBook G4 12" 867 (PowerBook6,1)
« on: October 14, 2026, 01:52:23 PM »

I got my PowerBook 12" working in Mac OS 9 yesterday, but unlike other reports I have seen, I had no sound at all, rather than speakers requiring headphones attached to work. There was nothing shown in the Sound control panel outputs (or inputs section) for that matter.

Long story short, Claude, the Mac OS 9 expert, helped come up with an open firmware script that fixes my sound issue, and the headphones / speakers both work as expected.

Here is the script and an explanation. (Claude offered to write a forum post about the whole thing. How lazy do you have to be? How long til forums are just bots talking back and forth? Pretty hollow, I admit, when I couldn't fix this on my own).

Note, i have 2 partitions on my PowerBook, if you just have one, you can ignore the partition info and use "hd:1" instead of "hd:10" as explained below.

1. Save the text below as a plain-text file named soundFix (no extension) at the top level of your OS 9 disk. Mac line endings from SimpleText are fine.
2. Change hd:10 on the "boot" line to your OS 9 partition. To find it, run "printenv boot-device" in Open Firmware after booting OS 9, or try "dir hd:10,\" and nearby numbers until you see your System Folder.
3. Boot into Open Firmware (Cmd-Opt-O-F) and test it with: boot hd:10,\soundFix
4. To run it on every boot: setenv boot-device hd:10,\soundFix and then reset-all. Choosing a disk in the Startup Disk control panel (OS 9 or OS X) overwrites boot-device, so run the setenv again after that.

Code: [Select]
<CHRP-BOOT>
<COMPATIBLE>
MacRISC MacRISC2 MacRISC3
</COMPATIBLE>
<DESCRIPTION>
PowerBook6,1 OS 9 sound fix (soundFix)
</DESCRIPTION>
<BOOT-SCRIPT>
dev /pci@f2000000/mac-io@17/i2s@10000/i2s-a@10000
" i2sbus" encode-string
" compatible" active-package get-package-property 0= if encode-bytes encode+ then
" compatible" property
device-end
dev /pci@f2000000/mac-io@17/i2s@10000/i2s-a@10000/sound
" feature index 0 model Proj16PowerControl" encode-string
" feature index 1 model Equalizer" encode-string encode+
" detect index 0 bit-mask 2 bit-match 0 device 2 registry-name extint-gpio15 model GPIOGenericDetect" encode-string encode+
" detect index 1 bit-mask 2 bit-match 2 device 2048 registry-name extint-gpio4 model GPIOGenericLineInDetect" encode-string encode+
" input index 0 icon-id -16521 name-id -20630 port-connection 1 port-type 0x6C696E65 zero-gain 0x00000000 model LineInput" encode-string encode+
" input index 1 icon-id -16521 name-id -20532 port-connection 4 port-type 0x696D6963 zero-gain 0x00000000 model InternalMic" encode-string encode+
" input index 2 model NoInput" encode-string encode+
" output index 0 device-mask 2 device-match 2 icon-id -16563 name-id -20524 port-connection 1 port-type 0x6864706E model OutputEQPort" encode-string encode+
" output index 1 device-mask 2 device-match 0 icon-id -16563 name-id -20525 port-connection 2 port-type 0x6973706B model OutputEQPort" encode-string encode+
" sound-objects" property
device-end
boot hd:10,\\:tbxi
</BOOT-SCRIPT>
</CHRP-BOOT>
Logged

UnexpectedBomb

  • 64 MB
  • ****
  • Posts: 105
  • Just a guy with too much Claude access
    • GitHub account
Re: Sound on a PowerBook G4 12" 867 (PowerBook6,1)
« Reply #1 on: October 14, 2026, 02:41:12 PM »

Long story short, Claude, the Mac OS 9 expert, helped come up with an open firmware script that fixes my sound issue, and the headphones / speakers both work as expected.

NOICE! Claude is indeed the Mac OS 9 expert  ;D Can you turn this into a drop-in system extension? With sound fixed, it looks like Sleep is the only thing remaining to tackle for this model.
Logged

knobsnswitches

  • 4 MB
  • **
  • Posts: 7
Re: Sound on a PowerBook G4 12" 867 (PowerBook6,1)
« Reply #2 on: October 15, 2026, 06:10:45 AM »

Well it's not an extension (yet?), but inspired by UnexpectedBomb's question, here is an updated ROM that contains these sound changes for a PowerBook G4 12" 867 - just unzip (.bin files not allowed to attach here), then open the .bin w/ Stuffit Expander, move your current ROM out of the System Folder and put this one in. No more open firmware messing around!
Logged

smilesdavis

  • 1024 MB
  • ******
  • Posts: 1319
  • ...
Re: Sound on a PowerBook G4 12" 867 (PowerBook6,1)
« Reply #3 on: October 15, 2026, 12:48:16 PM »

goal: one consoldidated universal powerbook g4 installer that updates the individual rom and installs all features currently being worked on. this is awsome but way to fragmented for the average guy who gets a powerbook g4 and wants to use it to its max.
Logged
new in September: iSight (box), System 7 (box)

UnexpectedBomb

  • 64 MB
  • ****
  • Posts: 105
  • Just a guy with too much Claude access
    • GitHub account
Re: Sound on a PowerBook G4 12" 867 (PowerBook6,1)
« Reply #4 on: Yesterday at 06:53:16 AM »

goal: one consoldidated universal powerbook g4 installer that updates the individual rom and installs all features currently being worked on. this is awsome but way to fragmented for the average guy who gets a powerbook g4 and wants to use it to its max.

I was actually thinking along these exact same lines. I think the natural evolution of @DieHard's Universal Installer is a Mac OS 9.2.2 "Enhanced" Universal installer where you have installation options such as:

1 - Machine Selection: Choose your machine model from a drop-down list so that a recommended configuration of machine-specific base ROM and/or related fixes get installed
Example 1: select Mac Mini G4 (PowerMac10,1) and get the Mini's custom ROM, audio fix, and VBL fix installed automatically
Example 2: select 17" aluminum PowerBook G4 (PowerBook5,1) and get a custom ROM with working CardBus fix installed automatically

2 - ROM Builder: Choose custom ROM enhancements (if applicable) for your machine
Example: select USB 2.0 and eSATA enhancements for the FW800 MDD ROM

3 - Additional Features: Choose extra features to install on top
Example: select AirPort Extreme, Bluetooth, and CPU Temp Monitor for a 17" PowerBook and have everything installed and working from the very first boot

This would streamline the entire installation process, mainly for the unsupported G4 models but even for earlier G4 models as well (titanium PowerBooks, older G4 Power Macs).
Logged

smilesdavis

  • 1024 MB
  • ******
  • Posts: 1319
  • ...
Re: Sound on a PowerBook G4 12" 867 (PowerBook6,1)
« Reply #5 on: Yesterday at 12:07:34 PM »

great minds think alike

agreed
Logged
new in September: iSight (box), System 7 (box)

redstudio

  • 128 MB
  • ****
  • Posts: 169
  • New Member
Re: Sound on a PowerBook G4 12" 867 (PowerBook6,1)
« Reply #6 on: Yesterday at 05:03:36 PM »

I think it would be a dream if you could create a universal OS 9 installer for every G4 model. It could be as simple as having a section in "Hotstuff" with folders organized by computer model (e.g., PowerBook Titanium, Aluminum, etc.), where each folder contains a custom-modified ROM and everything else needed to get the absolute best performance out of OS 9 for that specific machine. This site already contains vital information for such a project, but it’s currently quite scattered. It would be fantastic to have a single place where you could look up your specific model and find everything you need. If you could pull this off, it would be a dream come true for anyone who loves this operating system. Keep up the great work!
Logged

smilesdavis

  • 1024 MB
  • ******
  • Posts: 1319
  • ...
Re: Sound on a PowerBook G4 12" 867 (PowerBook6,1)
« Reply #7 on: Yesterday at 09:26:51 PM »

information available but scattered is easy food for a LLM :)

this is just the input that is needed btw. thank you
Logged
new in September: iSight (box), System 7 (box)

ssp3

  • Moderator
  • 1024 MB
  • ******
  • Posts: 1057
Re: Sound on a PowerBook G4 12" 867 (PowerBook6,1)
« Reply #8 on: Today at 07:57:22 AM »

You guys are putting too much trust in AI.  ;)
I had nothing but disasters with ChatGPT (paid subscription) for the past 3 months. Several Python based projects are stalled because of its totally unreliable and unpredictable performance.
It writes a few lines of code in 2 minutes and then I spend 1 hour fixing and unfuc**g what it had created.

So, be aware that AI can throw a ton of garbage at you pretending that it has created the best thing since the sliced bread.

Peace.
Logged
If you're not part of the solution, you're part of the problem.

smilesdavis

  • 1024 MB
  • ******
  • Posts: 1319
  • ...
Re: Sound on a PowerBook G4 12" 867 (PowerBook6,1)
« Reply #9 on: Today at 09:58:08 AM »

do we? how can you tell?
Logged
new in September: iSight (box), System 7 (box)

UnexpectedBomb

  • 64 MB
  • ****
  • Posts: 105
  • Just a guy with too much Claude access
    • GitHub account
Re: Sound on a PowerBook G4 12" 867 (PowerBook6,1)
« Reply #10 on: Today at 12:57:25 PM »

You guys are putting too much trust in AI.  ;)
I had nothing but disasters with ChatGPT (paid subscription) for the past 3 months. Several Python based projects are stalled because of its totally unreliable and unpredictable performance.
It writes a few lines of code in 2 minutes and then I spend 1 hour fixing and unfuc**g what it had created.

So, be aware that AI can throw a ton of garbage at you pretending that it has created the best thing since the sliced bread.

Peace.

***soapbox incoming  ;D***

I can understand your frustration completely. AI is not yet at a proficiency level where it can complete extremely complex tasks correctly on the first pass. That said, having gone through this process many times now, I believe there's a right way and a wrong way to go about programming something with AI. I never release anything to this community unless I have thoroughly vetted it myself with extensive testing, which is the key. The testing and bug-fixing step is not fun at all; sometimes it's a long slog indeed, but it is absolutely critical to putting together an end-product that actually works as intended. (Even then, there's always a few minor bugs that I still miss!)

Take the AirPort Extreme driver, for example. This is an incredibly complex piece of software. Some people have it in their heads that all I have to do is open up the Claude app on my MacBook and tell it, "Write me an AirPort Extreme driver for Mac OS 9", and Claude spits out a polished, functional product a few minutes later. That couldn't be further from the truth. The AE project required over two hundred iterations before it functioned exactly the way I wanted it. This meant many, many hours of work across multiple weeks of sessions, and there were many questions that had to be answered during the planning phase before a single line of code was written:

- What kind of encryption will it support? WPA2 only? What about legacy WEP? What about open networks?
- Should we bother porting Apple's original computer-to-computer "ad-hoc" wireless network feature?
- Will the new AE driver peacefully coexist with Apple's original AirPort drivers, or might this cause crashes?
- What about Broadcom chip revisions common to that era? Will we support BCM4306 only? What about BCM4318?
- What about form factors? Will this support the A1026 card only? What about PCI cards or CardBus?
- How/where do we safely store network passwords so that networks can be "remembered"?
- What will the UI look like? Similar to Apple's? Or can we do better with our own design?

Those are just a few examples of things I had to account for, and answering each one lead to multiple tests to prove them out before I was satisfied. After all, the whole point is to provide solutions and fixes for the OS 9 community that are both functional and enjoyable to use. There's no greater buzzkill in software development than buggy application that is a pain to use.

In summary, I know I can't trust AI blindly (and I believe the actual code-writing portion of the process should not be the first step anyway). That's why I think the majority of the work should be spent on planning beforehand and testing/hardening afterwards. That's how you turn AI from an unreliable crutch of frustration into a powerful and effective programming tool.

This site already contains vital information for such a project, but it’s currently quite scattered. It would be fantastic to have a single place where you could look up your specific model and find everything you need. If you could pull this off, it would be a dream come true for anyone who loves this operating system. Keep up the great work!

Thanks! I've been trying to get in touch with someone here on this website about that very possibility, but I haven't heard back. I have an idea for creating an "unsupported G4 wiki" that would contain the sum total of the community's knowledge in an easy-to-navigate format. I'd be more than happy to spearhead it myself, and then open it up to the rest of the community to supplement it, just like any other wiki page. At this point, there's just too much information to rely on sifting through hundreds of forum pages.
Logged

smilesdavis

  • 1024 MB
  • ******
  • Posts: 1319
  • ...
Re: Sound on a PowerBook G4 12" 867 (PowerBook6,1)
« Reply #11 on: Today at 01:16:11 PM »

its just a tool and like any tool like a hammer you gotta take your time before you stop hitting your thumb.

i won't unveil my method, especially since today a lot of unfriendly mentions happened here.

i just want to say this and not much more: for retro computing ai is godsent and will bring the past to us and everyone else closer.
Logged
new in September: iSight (box), System 7 (box)
Pages: [1]   Go Up

Recent Topics