upgrading the ibook clamshell's L2 cache to 1MB

guess what, i am actually typing this on the ibook right now... the modern web doesn't feel so usable but 68kmla forums on its modern layout works alright. also i still need to fix the nvram values for displaying the correct clock and bus speed (400MHz, 100MHz)
maybe some day i should put a 7410 in here..... lol. that is, if i get better at reballing.
Picture 1.png
 
got the bus speed set correctly in the config block, now the CPU is being properly recognized at its true speed.
maybe, when i do more practice, and improve upon my skills... i should definitely put a G4 into this computer
PXL_20260618_174157256.jpg
 
tried using the GUI tool but to no avail, the program doesn't recognize my bootrom hardware which is weird. what linux live CD should i use to get the flashrom program?
Did you try to open a file?

Config Block Editor can open files with creator of cbif and type brom or ROM . These can be a 1MiB firmware dump. You should get a firmware dump before and after modifying so you can compare before and after.

It can open individual config blocks with type:creator of cbif:bbce. These are 128 bytes. Maybe 256 byte? Firmware updaters have config blocks for many models (128 bytes per model - the second 128 bytes is unique to your machine).

It can open Firmware Updater scripts with type:creator TEXT:MPS . The scripts begin with Open Firmware code and contain compressed versions of the firmware and config blocks for each model.

I believe Config Block Editor 1.1 is limited to firmware updaters 4.4.8 and earlier. 4.5.5d2 and later changed the format to include separate drivers for different models. Although Config Block Editor 1.1 can't open all the firmware updaters, it can open config blocks extracted from the firmware updaters or config blocks in firmware dumps for all the versions, but I don't know if the parsing of later config block versions is correct.

Config Block Editor can open files of type APPL, I don't know what this one is.
File type kinds:
cbif Config Block image file
TEXT Motorola S-Records Config Block file
APPL Self-Updating Config Block image file

What's a "Motorola S-Records Config Block file"? This is not a Firmware Updater script?
What's a "Self-Updating Config Block image file"

About dialog text:
Code:
Allows editing of the BootROM Config Block on Core99-based machines. To use, simply edit the Config Block values, hit enter to record the change, and then click Update. BootROM image files and Config Block image files can be dropped onto either the application icon or the main window to import their contents.
Engineering:
   Bob Bradley
Special Thanks:
   Ernie Beernik, Derrick Carty, Chuck Childs, John Hall, Ron Hochsprung, 
   Nick King, Al Kossow, Mike Larson, Dave Martin, Stuart Russell, Dave Wong
 
i was able to edit the ROM directly using the program, i just had to hold power and command while turning it on until i hear a long beep. i was also able to get everything working as i stated earlier.
 
i wonder how fast this will be with a 600mhz G4 7410 in it. i know i'll need a fan and a better heatsink (not sure what will work though)... just not sure how exactly i'll go about connecting it to power
 
there is GUI tool config block editor, that leaked recently, for editing this sort of stuff, but I have not personally messed with it much other then finding it in the CD and poking at it a bit


I must be seriously out of date. How the heck does one download a useful disk image from that archive? I got the 700+ MB file just called "Bandit" but it doesn't seem to have any usable file type, such as ISO Image or such.
 
I must be seriously out of date. How the heck does one download a useful disk image from that archive? I got the 700+ MB file just called "Bandit" but it doesn't seem to have any usable file type, such as ISO Image or such.
There's a .cue file which says that the corresponding binary file is a single track CD with block size 2352. Just convert it to 2048 byte sized blocks.

Each CD blocks begins with a 16 byte header (like this: 00ff ffff ffff ffff ffff ff00 0002 0001 and ends with 2352-16-2048=288 byte footer.

I'm using macOS Monterey with FuseHFS to mount the HFS partition.
Code:
# convert the CD
lang=C perl -0777 -pe 's/.{16}(.{2048}).{288}/$1/msg' "Bandit 18" > "Bandit 18.dmg"

# mount the dmg
hdiutil attach "Bandit 18.dmg"
/dev/disk16         	Apple_partition_scheme         	
/dev/disk16s1       	Apple_partition_map            	
/dev/disk16s2       	Apple_Driver43                 	
/dev/disk16s3       	Apple_Driver43_CD              	
/dev/disk16s5       	Apple_Driver_ATAPI             	
/dev/disk16s6       	Apple_Driver_ATAPI             	
/dev/disk16s7       	Apple_Patches                  	
/dev/disk16s9       	Apple_HFS                      	/Volumes/Untitled

# view the filesystem in the Finder (FuseHFS uses "Untitled" for the mount point name instead of the name of the volume which is "Bandit 18")
open /Volumes/Untitled
 
There's a .cue file which says that the corresponding binary file is a single track CD with block size 2352. Just convert it to 2048 byte sized blocks.

Each CD blocks begins with a 16 byte header (like this: 00ff ffff ffff ffff ffff ff00 0002 0001 and ends with 2352-16-2048=288 byte footer.

I'm using macOS Monterey with FuseHFS to mount the HFS partition.
Code:
# convert the CD
lang=C perl -0777 -pe 's/.{16}(.{2048}).{288}/$1/msg' "Bandit 18" > "Bandit 18.dmg"

# mount the dmg
hdiutil attach "Bandit 18.dmg"
/dev/disk16             Apple_partition_scheme            
/dev/disk16s1           Apple_partition_map               
/dev/disk16s2           Apple_Driver43                    
/dev/disk16s3           Apple_Driver43_CD                 
/dev/disk16s5           Apple_Driver_ATAPI                
/dev/disk16s6           Apple_Driver_ATAPI                
/dev/disk16s7           Apple_Patches                     
/dev/disk16s9           Apple_HFS                          /Volumes/Untitled

# view the filesystem in the Finder (FuseHFS uses "Untitled" for the mount point name instead of the name of the volume which is "Bandit 18")
open /Volumes/Untitled
i renamed the extensionless file to .bin and used the .cue to burn it to a CD
 
Thank you folks. I'll give these ideas a try. I'm much more of a hardware guy. Will this work on Windows? I think the latest MAC OSX machine I have runs 10.5.
 
i wonder how fast this will be with a 600mhz G4 7410 in it. i know i'll need a fan and a better heatsink (not sure what will work though)... just not sure how exactly i'll go about connecting it to power

Perhaps @herd can give us more information, but I believe these iBooks use a 3.3V cache, which is incompatible with the MPC7410; only the MPC7400 can be used. The MPC7410 can be used if the model doesn't have an L2 cache.
 
Back
Top