Jump to content

Is boot-132 a silver bullet ?  

2 members have voted

  1. 1. Does it work for your hardware as long as you can find a kext ?

    • Yes
      1
    • No
      1
    • Depends - see my response
      0


4 posts in this topic

Recommended Posts

Hello,

 

Let me first state that generic.iso works very well for a Retail DVD Leopard install on this machine. However, I have no network (Network card - Broadcom NetXtreme 5754 (device id 167a). Downloaded the kext from A.A.'s post on :

 

http://forum.insanelymac.com/index.php?sho...4987&st=660

 

Added in kexts to the kexts in generic.iso to get the following kexts in "initrd.img"/Extra/Extensions :

 

ACPIPS2Nub.kext

AppleAC97Audio.kext

AppleACPIPlatform.kext

AppleAHCIPort.kext

AppleAPIC.kext

AppleAzaliaAudio.kext

AppleGenericPCATA.kext

AppleIntelIntegratedFramebuffer.kext

AppleNForceATA.kext

ApplePS2Controller.kext

AppleSMBIOS.kext

AppleVIAATA.kext

ElliottAppleIntelGMA950LegacyEnabler.kext

IO80211Family.kext

IONetworkingFamily.kext

IntelCPUPMDisabler.kext

NVkush.kext

Natit.kext

SMBIOSEnabler.kext

dsmos.kext

lspcidrv.kext

 

Found that superhai's method on mac (using my iDeneb hackintosh) does not work (probably has something to do with Mac using capital case) :

 

http://forum.insanelymac.com/index.php?s=&...st&p=803725

 

So, I downloaded the latest version of syslinux (v 2.72 ?), compiled it on my linux machine, copied isolinux.bin, threw in pc-efiv9+chameleon's boot (getting ambitious there), and kept the old mboot.c32 (could not find it in the new syslinux), and made another iso (after moving isolinux.cfg out of the folder into root) :

 

(on my linux machine)

 

$mkisofs -o ../custom.iso -b isolinux.bin -c boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table ./

 

Burnt this. Booted - this time the thing boots, but I get a bad apple (circle with cross in it) on booting into the previously installed version of Leopard that I installed using generic.iso.

 

I have one suspect - two driver files in IONetworkingFamily.kext :

 

Apple3Com3C90x.kext AppleRTL8139Ethernet.kext

AppleBCM5701Ethernet.kext AppleRTL8169Ethernet.kext

AppleBCM5751Ethernet.kext AppleUSBEthernet.kext

AppleBCM5754Ethernet.kext AppleYukon.kext

AppleGMACEthernet.kext Apple_DEC21x4Ethernet.kext

AppleIntel8254XEthernet.kext

 

Now, generic.iso does not have a IONetworkingFamily.kext (which is present in the retail install). What I have done above is that I have taken A.A.'s BCM5751 patched for 5754 and copied it to a BCM5754 (changing Info.plist etc.).

 

Could this be the cause of my bad apple ?

 

I think it is a pity that generic.iso does not contain commonly present networking drivers like atheros and broadcom cards (very very common in Dells and Acers). I guess I am trying to fix that problem by doing all this, but is anyone willing to help me test / fix these problems ? We can then share some improved generic.iso joy (assuming I am not missing someone else's work) with the rest of folks here.

 

Thanks for the forthcoming help (getting hopeful as I think I am just a teeny little bit away from getting this to work).

 

My reason for choosing the pcefi v9+ chameleon boot instead of the July version of the boot (in generic.iso) is that I :

 

1. Want to keep these extra extensions away from the system extensions.

2. Want to have hibernate supported.

 

As a stop gap, would it suffice if I simply booted in with generic.iso, used a USB stick (assuming USB is working) to install the pcefiv9+chameleon 1.0.12 bootloader and put the extra extensions I need in /System/Library/Extra/Extensions ?

Is there a way to go into verbose mode / single user mode with this kind of setup ?

 

When I boot using a 132 boot cd, my only option is to select 80 for the first hard drive. I want to find out where the boot process is stopping with the modified boot-132 CD to fix the problem.

Is there a way to go into verbose mode / single user mode with this kind of setup ?

 

When I boot using a 132 boot cd, my only option is to select 80 for the first hard drive. I want to find out where the boot process is stopping with the modified boot-132 CD to fix the problem.

 

Any one ?

×
×
  • Create New...