Contribute
Register

black screen - no boot - multi beast 4.3.0 update :(

Status
Not open for further replies.
Joined
Nov 1, 2010
Messages
8
Motherboard
Asus P7H57D-evo
CPU
i5 - 760
Graphics
nvidia - asus ENGT240
Mac
  1. MacBook Pro
Classic Mac
  1. 0
Mobile Phone
  1. iOS
Ok, so I'm totally miffed! I decided with a somewhat working system that I would get rid of the hiss and poplin my audio with the DSDT & multi beast 4.3.0 - Realtek 989a. I had to do a BIOS update to the DSDT BIOS firmware, v1606. After that I put everything back to AHCI and S3 etc etc.

Anyways, after that my system didn't boot even with the rBoot. I booted up the 'installer' partition and renamed the DSDT.aml file to DSDT.old with the terminal rebooted and still nothing. I can only boot with rBoot! I've try dropping back to multi beast 4.2.1 and rerunning the easyBeast.
Any help is greatly appreciated.
:)

EDIT: Since I don't even get Chimera to load I'm thinning something must have happened to boot order... No I changed the order and all the same. Boot flags? I'm not sure how OSX put this I have my root on /dev/disk2
Code:
hack-Pro:/ hpbenton$ mount
/dev/disk2s2 on / (hfs, local, journaled)
devfs on /dev (devfs, local, nobrowse)
/dev/disk5s2 on /Volumes/RAID (hfs, local, journaled)
/dev/disk4 on /Volumes/Mirror (hfs, local, journaled)
/dev/disk3s2 on /Volumes/hack-time (hfs, local, journaled)
map -hosts on /net (autofs, nosuid, automounted, nobrowse)
map auto_home on /home (autofs, automounted, nobrowse)
afp_0AKsEP3ecAdj0NzVbK1M5BoQ-1.2d000003 on /Volumes/Macintosh HD (afpfs, nobrowse)
/dev/disk6s1s2 on /Volumes/rBoot (hfs, local, nodev, nosuid, read-only, noowners)
/dev/disk2s3 on /Volumes/Installer (hfs, local, journaled)
hack-Pro:/ hpbenton$ ls /dev/disk2*
/dev/disk2	/dev/disk2s1	/dev/disk2s2	/dev/disk2s3
fdisk: 1> print
Disk: /dev/rdisk2	geometry: 121601/255/63 [1953525168 sectors]
Offset: 0	Signature: 0xAA55
         Starting       Ending
 #: id  cyl  hd sec -  cyl  hd sec [     start -       size]
------------------------------------------------------------------------
 1: EE 1023 254  63 - 1023 254  63 [         1 - 1953525167] <Unknown ID>
 2: 00    0   0   0 -    0   0   0 [         0 -          0] unused      
 3: 00    0   0   0 -    0   0   0 [         0 -          0] unused      
 4: 00    0   0   0 -    0   0   0 [         0 -          0] unused      
fdisk: 1> abort
So I'm not used to seeing frisk work like this, so I don't know where to check for the boot flag? Is it using logical partitions?
PS getting close to doing a reinstall!
 
Ok so.... reinstalled and nothing! Still the black screen flashing cursor :( Really have no idea now.
Someone asked if the system booted regularly after the BIOS update-- yes it did. All drives functioned and everything. Chimera just isn't loading -- WHY :crazy: :banghead:
 
SOLVED -Re: black screen - no boot - multi beast 4.3.0 updat

:crazy: :crazy: :oops: :oops:
So not quite sure why but after looking at my boot order of my drives I saw that my drive wasn't getting booted first. It was after the BIOS update,... so... can DSDT's change boot order ??? :confused:
 
Status
Not open for further replies.
Back
Top