Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

AHCI bootcamp with Velocity solo x2

Thanks for your info!

snarfquest said:
MacPro 2012
Velocity Solo x2
Samsung 500gb SSD boot drive on the Velocity card. OSX only.
Bay 4 1tb Seagate SSD hybrid drive Windows 7 64bit Bootcamp drive.

Since Mavericks GM and installing Bootcamp 5.1 my system now boots seamlessly between the 2 OS's.
Click to expand...

What was your hick-up in OS X 10.8.x ? Are there new (updated) drivers avaliable in BCA 5.1 under Mavericks?

Cheers

Off topic: any problems with non compatible major applications running in Mavericks?
 
BDM STUDIOS NL said:
Thanks for your info!



What was your hick-up in OS X 10.8.x ? Are there new (updated) drivers avaliable in BCA 5.1 under Mavericks?

Cheers

Off topic: any problems with non compatible major applications running in Mavericks?
Click to expand...
The bootcamp 5.1 support files for our MP 3,1 models haven't been on the update server for a week now. I've asked other users with 3,1 on the mavericks sub forum here to see if they can download it but so far I've had no reply!

https://forums.macrumors.com/threads/1655072/
 
BDM STUDIOS NL said:
Thanks for your info!



What was your hick-up in OS X 10.8.x ? Are there new (updated) drivers avaliable in BCA 5.1 under Mavericks?

Cheers

Off topic: any problems with non compatible major applications running in Mavericks?
Click to expand...

Under 10.8.5 with the Velocity installed the system would black screen when trying to boot Windows.
 
pastrychef said:
I don't understand how OS X can affect the way Windows boots.
Click to expand...

In my case OSX is refusing to go into bios emulation mode (black screen) on bootcamp with the SSD in the solo, if Apricorn come up with no solution I'm going to mod the AHCI kexts hackintosh style so Mac OS thinks the drives are fixed and not removable as both the mac and windows volumes show as removable under 10.9. No time to do that just yet so I'll hang on until I get bootcamp 5.1.

Never had to hackintosh a real mac before :D
 
But how would changing how OS X sees the drives help you boot in to Windows?

During startup, if you already had your Windows drive set as the startup device, it will never read anything from your OS X drive. It will go directly to the Windows drive.
 
I'm still very confused (disappointed) why Sonnet, Appricorn, OWC and others all make SATAIII add-ons for the Mac with NO decent RAID and/or Bootcamp support. :confused:

They must have been watching MacRumors too, to see that the majority of the users are trying to config them for both OS X & Bootcamp Windows 7 or 8!

Well......
 
@pastrychef Yes, but nobody knows why! That's my confusion here. What's the significant diverence between a 3.1 and 4.1/5.1 regarding PCIe receiving SATAIII hardware and we all use the same standard bootcamp drivers Was this issue even investigated by the makers of these cards? Just wondering...
 
Apricorn replied:

The Mac 3,1 model seems to behave differently than others and it seems to be the most troublesome of the Mac Pros in regards to the Solo card, and especially with boot camp. Our customers seem to all have different experiences.

Remove the Marvell WHQL drivers that you installed. It is not needed.

Some options to try:

Install Windows on a separate SSD that is mounted on the sled and connected to the motherboard. Keep OSX on Solo X2. Reinstall Windows on the boot camp partition that already exists, with the drive connected to the Solo. Use the option key to change OS afterwards.
Uninstall boot camp and install virtualization software like Parallels or Fusion.

I sent this email over to our engineering team so if they see a solution then they will provide it to you.

None of which will solve my issue booting both off OS off the same SSD in the solo. I said I'm an advanced user and can fiddle with kexts so I reckon I'll wait for engineering seeing I'm busy till the weekend anyway to start serious troubleshooting. Hopefully bootcamp 5.1 will be available to download by then...
 
@pastrychef I have a 5,1 and HAD the same problem that 3,1 people have. My Macpro is brand new. I only just bought it ~3 months ago.
 
@ snarfquest:

You are unable to boot to your Bootcamp drive/partition? Did you use the Bootcamp assistant to install Windows?

@BDM STUDIO NL:

When I last inquired about this issue with Apricorn, the person whom I spoke with blamed the EFI on 3,1s.
 
pastrychef said:
But how would changing how OS X sees the drives help you boot in to Windows?

During startup, if you already had your Windows drive set as the startup device, it will never read anything from your OS X drive. It will go directly to the Windows drive.
Click to expand...

I had similar problems booting windows years ago when SATA drives/controllers first came out with certain types of BIOS and the controllers were flagging the drives as removable, it would either fail to display the bios and hang or bsod instantly. It's a very similar problem only with Mac EFI this time. First port of call I think will be hackintosh land seeing if rEFInd can get the black screen bios emulation fired up. Following that fiddling with the AHCI kexts to make my disks permanently fixed running off the solo in Mavericks. As it's likely to be the last officially supported Mac OS on the 3,1 until a cheap 4 or 5,1 crosses my path it's something I want to fix and stay fixed till I retire it!
 
I don't think making the drives appear as permanent drives rather than removables in OS X will have any effect on booting in to Windows. Even if you have no OS X drive/partition in the computer, you can still boot in to Windows.
 
Thanks all for yor replies and insights! I really hope Gav gets this solved....

I'm not an engineer but answers from Appricorn with "it seems, and perhaps" gives me goosebumps!!! ;(
 
I have a macpro 4,1 (5,1) firmware.

I have OSX 10 on a 512gb SSD (bay 1) and Windows 8 on a second physical 180gb SSD (bay 2).

Occasionally, when I go to the boot menu (by pressing option at startup) and selecting the windows drive, the computer will hang and will not boot the volume. When it starts doing this, usually the only way to get it to boot windows is to select the windows drive as the startup volume in OSX and then reboot.

The only thing that fixes it is to re-install the bootcamp drivers in windows. Once I do that, everything goes back to normal and I'm able to boot BC with the boot menu.

I'm not sure what happens on the windows side (or volume) that makes this necessary.
 
Hey guys, just went through this hell with my Velocity Solo x1. I have a 3,1 with the latest Mavericks and (originally) Windows 7. Installed my Solo, and instantly, Win7 would BSoD. I can safely say that Windows 8 does NOT have the BSoD problem that 7 did on my system. Oddly enough, Windows 8 is uh, "not supported" on my system, but I mean, if we all had a dollar for every time we did something that "wasn't supported" on our Mac Pros... But anyway, the AHCI drivers in Windows 8 are native, just install 8 instead of 7 in Boot Camp. Sure the interface is blah, but all the drivers work and it runs great. I'm running 8.1 off an internal SATA bay with a Fusion Drive software created between my Solo card and a SATA bay. Can't access my HFS+ drives, but I'm almost certain it's because they're a CoreStorage volume and not because of the Solo. Hope this helped.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back