Contribute
Register

Boot Issues smbios and system identifier

Status
Not open for further replies.
Joined
Jun 28, 2011
Messages
25
Motherboard
GA-Z68MA-D2H-B3
CPU
3.19 GHz Intel Core i5
Graphics
AMD Radeon HD 6670
Mac
  1. MacBook Pro
Classic Mac
  1. 0
Mobile Phone
  1. iOS
Hello,

Within the past few days I have run into a number of problems with my system. The audio stopped working so I tried to reinstall via MultiBeast. I guess I didn't install my normal settings because my computer would not reboot and I have tried everything I know how in order to get it to do so.

A few problems I know definitely messed things up:
1. My system identifier changed from MacPro 3,1 to MacPro 5,1
---I found another thread to fix that, but apparently it did not do so and now my /Extra/smbios.plist is empty when I try to get to it via single user mode.

2. My identifier is now iMac 12,1
--I do not know how to change it without booting first and I cannot seem to do that at the moment.

3. My machine goes into kernal panic whenever I boot. None of my traditional boot flags have worked to this point. I have attached my -v boot screenshot


I am relatively a noob when it comes to this stuff, though I have had this machine running for a few years without too many issues. Please help!
 

Attachments

  • photo1.jpg
    photo1.jpg
    610.7 KB · Views: 195
Try boot with the UniBeast installer and use boot flags -v -x -f for booting OS X and if you can get to desktop you can try to corrent your messed up system.

Do you have a bootable backup? Comes in very handy in this type of situation. Or a TM backup you can restore?
 
Are you suggesting I install Mavericks again via Unibeast? I did that yesterday, but I could not (or do not know how to) boot into my Mavericks install to get to MultiBeast

I don't know how to really do any of this boot stuff besides flags, but I feel like I'm missing a way to get into my system. It's probably something really simple I don't know how to do
 
Are you suggesting I install Mavericks again via Unibeast? I did that yesterday, but I could not (or do not know how to) boot into my Mavericks install to get to MultiBeast

I don't know how to really do any of this boot stuff besides flags, but I feel like I'm missing a way to get into my system. It's probably something really simple I don't know how to do

Boot with the UniBeast USB. At the Chimera screen hit the space bar. Hit the right arrow key to move the selection hi-lite to your OS X HDD/SSD. type in

-v -x -f

and hit enter. This boots your OS X install verbose, with minimum kexts loaded, and forces the process to ignore the boot cache. This should get you to your desktop.
 
Thanks for your replies! This has been driving me mad! Okay I tried to write down and take pictures of exactly what I am doing so it's easier to diagnose where/if I'm going wrong.

-When booting my machine I hold F12 to bring up my boot menu device. I choose the USB-HDD in order to get to my UniBeast USB drive.

-The next screen that pops up is the USB or Mountain Lion choice. (Mountain Lion is still the name of my used-to-be-working Mavericks Operating System).

-I right-arrow over to my Mountain Lion (Mavericks) install and type in the boot flags suggested "-v -x -f" and then hit enter.

-The machine goes thru a long file process and at one point it states "Errors encountered while starting up the computer"

-It then goes through checking some more things and the last thing it appears do do is "Waiting for DSMOS..."
--It says something about falling back to old SMC mode and then the kernel panic is immediate after that.


My Questions:
1. Did I even do that process correctly? I honestly do not know.
2. Does anyone have any insight into this type of panic?

I really appreciate all the help so far!
 

Attachments

  • photo1.jpg
    photo1.jpg
    417.1 KB · Views: 148
  • photo2.jpg
    photo2.jpg
    489.3 KB · Views: 161
  • photo3.jpg
    photo3.jpg
    378.5 KB · Views: 147
  • photo4.jpg
    photo4.jpg
    366 KB · Views: 152
  • photo5.jpg
    photo5.jpg
    676 KB · Views: 156
  • photo6.jpg
    photo6.jpg
    686.9 KB · Views: 162
  • photo7.jpg
    photo7.jpg
    553.4 KB · Views: 185
Yep, you did it right:thumbup:

From the KP in the last screen, it doesn't like your gragpics card, which is strange because that SNB is usually a problem with nVidia cards and you have AMD...

Which CPU graphics do you have? If HD3000/4000/4600, suggest removig the AMD and booting same as you just did with the CPU graphics

Alternatively, boot -s and just rm the entire /Extra folder, then reboot using same method as you just did.
 
I cannot remember which onboard graphics I have, but I unplugged my graphics card and ran the HDMI straight from the motherboard to the monitor and I set the BIOS to look for onboard graphics first. (I had done that when I first had my machine a few years ago)

I went through the same process with the booting to the USB, flags "-v -x -f" , and it the panic occurred again.
 

Attachments

  • photo.JPG
    photo.JPG
    763.3 KB · Views: 142
I just saw the bottom of that reply, and I don't exactly understand that part.
"Alternatively, boot -s and just rm the entire /Extra folder, then reboot using same method as you just did."

-Should I add -s to the end of the "-v -x -f -s" or just "-s"
- I do not know what rm means and the extra folder... Could you explain?

Thanks!!
 
I just saw the bottom of that reply, and I don't exactly understand that part.
"Alternatively, boot -s and just rm the entire /Extra folder, then reboot using same method as you just did."

-Should I add -s to the end of the "-v -x -f -s" or just "-s"
- I do not know what rm means and the extra folder... Could you explain?

Thanks!!

-s boot into single user mode. use command line script typed in to remove the folder.
Do you have a selection in BIOS to enable/disable VT-d? If yes, try disable it.
 
-s boot into single user mode. use command line script typed in to remove the folder.
Do you have a selection in BIOS to enable/disable VT-d? If yes, try disable it.

Could you walk me thru the step by step how to do the command line script, specifically what to type and when to type it
 
Status
Not open for further replies.
Back
Top