[Guide] SurfacePro 1 & 2 Osx-Android-Windows multiboot

[StefanoMacOSX]

Here is a new version. The sources are in the tarball, the kext is in the .zip file. Please delete the old one (/System/Library/Extensions/Avastar.kext) before upgrading!

 

I've cleaned up the kext, removed the "gibberish" and separated it from the Wlan stuff which may have caused issues. So now the kext is named "AvastarFwLoader.kext".  Additionally, the kext should now automatically unload itself once the firmware is uploaded. License is GPLv2 except for Marvell's firmware, which is proprietary but freely redistributable.

 

 

On the Wlan side... well, the source tar ball now contains a partially reverse engineered IO80211Controller.h header that is compatible with Mavericks, which is a first step.... I now think that porting the Avastar driver from Linux should be easier than e.g. the Intel Wi-Fi driver, because the Avastar driver doesn't call into the Linux 802.11 stack or anything like that. Still, it's probably a month's work just to get scanning working, and a year or so for a driver that can actually connect to anything. So I'm stopping there, I just don't have that much time.

 

Great work JAPE!!!

It Works PERFECTLY!!

Now bluetooth works perfectly without usb dongle!

When you will have time, please make a kext for internal Wi-Fi!

In this way, our Surface Pro 2 will be perfect for OSX!

 

Very very thanks!

[caleidosCope]

Thanks, i liked the politness of this blog as much as the infos i came here in

the first place. I guess the system i need has a keyboard but no touchpanel

where i will be a happy B'camper for the next years. I like the Surfaces

... so there are options... use the SurfacePro Type-Cover (2)... or while hackintosching and having bluetooh avail (thanks jape)... use any BT-keyboard that fits your needs.

... screen-size... look at mythamp's setup.

... but the "eierlegendewollmilchsau   ... egg-laying, milk-bearing woolly sow" isnt out there yet...

[whoareyou]

Patiently awaiting a way to use WiFi/Bluetooth without USB dongle, very excited to see the bluetooth progress! ,cuz i need my usb port open, also, waiting for a touch driver that isnt $100... as much s i love the Surface Pro, im thinking itll be easier to go get a different laptop/tablet hybrid for future hackintoshing

[knod]

[surface2OSX]

 

Just a reminder for all new SF2P OSX Bluetooth users out there (many thanks jape!):

 

If you have a Mac running nearby, you can easily access it's WiFi/LAN connection over Bluetooth via System Preferences -> Sharing -> Internet Sharing on that Mac. It's still Bluetooth though so for me it gives my Surface only about 1Mbit (out of my 100) over Bluetooth. This still works fairly well for surfing and regular stuff - but at least you get access to the USB-port if needed.

 

Maybe this is obvious to most, but I still think it's worth mentioning.

 

 

Again, thanks for all the hard work all!

[munakib]

Thanks for sharing that idea knod, I was actually considering all possible options including buying bluetooth-lan access points which are very rare (most of them are also expensive). So your solution is much simpler provided there is a mac lying around.

[surface2OSX]

 

Just a reminder for all new SF2P OSX Bluetooth users out there (many thanks jape!):

 

If you have a Mac running nearby, you can easily access it's WiFi/LAN connection over Bluetooth via System Preferences -> Sharing -> Internet Sharing on that Mac. It's still Bluetooth though so for me it gives my Surface only about 1Mbit (out of my 100) over Bluetooth. This still works fairly well for surfing and regular stuff - but at least you get access to the USB-port if needed.

 

Maybe this is obvious to most, but I still think it's worth mentioning.

 

 

Again, thanks for all the hard work all!

[counter5th]

Thanks for sharing that idea knod, I was actually considering all possible options including buying bluetooth-lan access points which are very rare (most of them are also expensive). So your solution is much simpler provided there is a mac lying around.

Or a phone, like an iPhone!

[hamido123]

My surface runs osx with all working but touch

I noticed that if i hold 4 fingers the 5ths finger works like a normal touch input

[knod]

@counter5th

 

The problem with using an non-jailbroken iPhone for this is that it only shares your cellular connection, not WiFi - even if it's connected to a WiFi network. You can overcome this by jailbreaking, but then you have to buy additional stuff in Cydia to get it to work.

[counter5th]

@knod

 

Yeah, I use mywi. It's great.

[JahStories]

@hamido123

 

 

without commercial touch-base drivers, thats the only way to use the touch-screen, and pen is not calibratable

 

 

@about bt teathering

 

for iPhone or Android teathering, bluetooth would be fine, but for heavy home internet use (streaming, downloading etc) it would be too slow and with a very short range, uncomparable to the wifi performances.

 

i just suggest you guys to get an Hub like this one and a nano usb wifi adapter

 

(if you are interested, just search: "surface hub" on Amazon)

 

have a good day!

[hamido123]

@ jahstories

Is there any hope that we will get this working for everyone in near future?

[JahStories]

Honestly,

 

it's really too early, i think that the main reason is that there aren't real apple x86 tablets yet,

even the hackintosh community is too young on tablets, we could say that the surfacepro is actually the first one...

 

more x86 tablets means more chances that someone write the driver.

 

 

 

The Bug's Sheet has been updated

 

Now there are two sheets, one with the fixed bugs + solutions and the other one with the few little bugs we still have.

 

thanks to thatoneging that created the shared xls.

 

Please if you find a bug add it to the list.

 

Thanks to everyone too! what a great comunity!

 

 

 

Surface pro 3 rumors

 

 

Rules reminder:

 

1

 

NO SUPPORT IF YOU USE OTHER GUIDES OR FILES PACKAGE.

 

Please don't post parallel guides, if you want to improve it write me a PM.

 

2

 

when you ask for help, Please remember to attach the right badge on the top of your post,

one of these:

 (surfaceosx) (surface2osx) (surfacewin) (surface2win) (androsurface) (androsurface2)

 

3

 

Add to your signature, including, processor and other infos

you can use this as reference, just change the yellow text with your actual configuration.

 

Microsoft SurfacePro 1 OS:Windows, Android Cpu:u4000 Gpu:HD4000 Ram:4gb 1333  WiFi:external usb SSD:128gb

[caleidosCope]

@ jahstories

Is there any hope that we will get this working for everyone in near future?

sorry for "banging the party".

You mean a fix for the pen and touch?

IMHO - NO free solution! There is a solution... the touchbase-drivers. Really worth the money, if you need it! And they cost what they cost, because there is no free-solution.

Same thing with the built in onscreen-keyboard... if you need a "really working" OS-keyboard you probably have to invest some buck in the TouchStrokes-keyboard (pheew ....expensive)

 

Think about, having a MacBookAir, wanting to have a tablet with it... you have to update a Wacom-Intous (or a cintiq)... from this point of view, the TB-driver is a bargain. And works flawlessly. The Surface is in my case like a little cintiq, with a computer "onboard". For this, a bargain too.

 

Isnt there a actual "come together, we buy ten"-post in this thread?!

 

on the other hand... assuming that all 80 japes-bt-enabler-downloader have a running system AND purchased the TB-driver... that’s +7000€ for a "driver-edit"...

come on TouchBase-Dave ... cut the prices!!!   Your early adopters wont mind.

[floflood]

... so there are options... use the SurfacePro Type-Cover (2)... or while hackintosching and having bluetooh avail (thanks jape)... use any BT-keyboard that fits your needs.

... screen-size... look at mythamp's setup.

... but the "eierlegendewollmilchsau ... egg-laying, milk-bearing woolly sow" isnt out there yet...

Yes, that's true (about the sow/is that a common expression in english, too?).

But anyway, the Surface does a lot. Cintiq/Wacom,Touch,USB3,SD+MDPort.

My next time Hackintoshing might be with a Chomabook using an i3 CPU

[jape]

Actually HID drivers for the pen/multitouch are way easier than e.g. the Wi-Fi drivers, which I remind you, are highly improbable to ever be developed in time the before the Surface Pro is obsolete. Maybe if someone started sending free SFPros to key OSX86ers....

 

In the meantime, I will try to guess what's wrong with the OS X HID drivers.

Edited May 7, 2014 by jape

[JahStories]

@jape

 

many people would like a free driver  and even a free surface 

(totally sure that "key OSX86ers" could fix everything)

 

the first hackintosh camed out of one man hand after only two days of work, request in super secret by Steve Jobs, if i remeber it right, it was a sony vaio with an early pre-macintel x86 tiger version

link i've found

 

btw it has to be said that the actual touch base stylus driver is 100 times superior than any wacom utility i've ever seen

and the touch driver got a lot of cool personalizations and the magic trackpad emulation make even games works.

 

personally, i think it's a very good driver+utility and worth the money. (i payed for it even if i was helping them "alpha testing" the driver)

 

@flofood 

 

have you heard about the rumors of a 12" inch surface pro tablet?

 

i opened a thread check it out.

[aardvark23]

(surface2osx)

 

Great work JAPE!!!

It Works PERFECTLY!!

Now bluetooth works perfectly without usb dongle!

When you will have time, please make a kext for internal Wi-Fi!

In this way, our Surface Pro 2 will be perfect for OSX!

 

Very very thanks!

 

Hello, NewBee here.  Actually, I've been lurking for some time while trying to get the beast running.

 

Did I do the badge this properly.

 

Anyhow, am I missing something wrt the Avastar running on a fat boy (SP2 512GB) of recent production?  When I load the AvastraFwLoader.kext on my machine, it gripes about being unable to read/write the pipe.  When I look up the product id under that other OS, I see it as 0x2044, not 0x2043.  Changing the ID in the info.plist and rebuilding didn't seem to help.  Do I need another kext?

 

Also, FYI, I got a Juiced USB 3.0 dongle hub with a 1Gb Ethernet port.  The first time it came up, which is immediately after installing the driver (ASIX 88179), the Ethernet port in the Surface Dock also came up.  It did that precisely once.  I've never seen it activate again, but I did use it for several hours.  I'm still trying to figure out the magic there.  Any ideas?

 

Another anomaly in the hw inventory is that I see a SAM under the main USB.  It's 0x045e:0x07a9.  It doesn't appear to be terminated anywhere on the case.

[caleidosCope]

Yes, that's true (about the sow/is that a common expression in english, too?).

But anyway, the Surface does a lot. Cintiq/Wacom,Touch,USB3,SD+MDPort.

My next time Hackintoshing might be with a Chomabook using an i3 CPU

... about the sow... i am not sure...there were several options for the translation (google) ... but... sounds cool in german, and it does too in english

 

My next time hackintosh will be a SurfacePro 3 !!! 

[JahStories]

@aardvark23

 

Welcome to the forum

perfect badge and signature 

 

Probably you have a new or particular revision with different "chipsets"

 

maybe jape can help for the bt, for touch and pen (SAM) have you tried touchbase trial driver?

 

p.s.

 

how much that beast cost?

[jape]

Anyhow, am I missing something wrt the Avastar running on a fat boy (SP2 512GB) of recent production?  When I load the AvastraFwLoader.kext on my machine, it gripes about being unable to read/write the pipe.  When I look up the product id under that other OS, I see it as 0x2044, not 0x2043.  Changing the ID in the info.plist and rebuilding didn't seem to help.  Do I need another kext?

 

No -- don't change the product ID on the kext.

 

If the product ID is 0x2044 on your device then the firmware has been uploaded succesfully. Either the kext works as it should OR you warm-rebooted from Windows. In any case, check System Preferences -> Bluetooth.

 

To clear the currently uploaded firmware, you may need to poweroff the machine. After that you'll see the PID is 0x2043 again.

 

 

Also, FYI, I got a Juiced USB 3.0 dongle hub with a 1Gb Ethernet port.  The first time it came up, which is immediately after installing the driver (ASIX 88179), the Ethernet port in the Surface Dock also came up.  It did that precisely once.  I've never seen it activate again, but I did use it for several hours.  I'm still trying to figure out the magic there.  Any ideas?

With the MS Surface Adapter I need to plug it in after OS X has booted. It won't enumerate it if it's plugged in while booting.

 

 

 

Another anomaly in the hw inventory is that I see a SAM under the main USB.  It's 0x045e:0x07a9.  It doesn't appear to be terminated anywhere on the case.

This is normal.

[aardvark23]

@aardvark23

 

Welcome to the forum

perfect badge and signature 

 

Probably you have a new or particular revision with different "chipsets"

 

maybe jape can help for the bt, for touch and pen (SAM) have you tried touchbase trial driver?

 

p.s.

 

how much that beast cost?

With the dock, it was around 2K clams.  Ouch.  So much for my nephews inheritance.  But, all things considered, it's actually pretty snappy with the extra memory and ssd space.  It runs VMware Workstation under that other OS with OS X running as a client and it isn't painful.

 

I tried the TouchBase drivers, but it killed the use of the WindowsLogo button combined with the volume down rocker to raise the intensity of the screen backlight, so I took it back off.  That brings up another question.  Does anyone have the keyboard backlight working.  Yeah, I know about the anemic battery, but I'm blind in one and and can't see out the other.  It helps the handicapped...

 

SAM is pen? Sorry, I thought it was the secure access method controller for one of those finger print reader thingies.

 

Oh, and the other thing about running OS X on the Surface is that when the scheisters call (about twice a day now), claiming to be from Windows Tech Support and want me to hold down the windows key on the keyboard and then press "R", I get to tell them it pops the email screen up.  The reply is "that's impossible".  Click.  Goodbye.

No -- don't change the product ID on the kext.

 

If the product ID is 0x2044 on your device then the firmware has been uploaded succesfully. Either the kext works as it should OR you warm-rebooted from Windows. In any case, check System Preferences -> Bluetooth.

 

To clear the currently uploaded firmware, you may need to poweroff the machine. After that you'll see the PID is 0x2043 again.

 

With the MS Surface Adapter I need to plug it in after OS X has booted. It won't enumerate it if it's plugged in while booting.

 

 

This is normal.

Jape, that fixed the dock ethernet.  But it's still unreliable. It comes up sometimes, but not always.

 

The product id for the bt came from Windows, so that explains why it differs.  When I do a hardware inventory under OS X, the bt device doesn't even show up under the USB display.  I still get the messages about not being able to read/write the pipe followed by one about being unable to load the firmware.

 

Thanks!

[floflood]

....the first hackintosh camed out of one man hand...

 

....have you heard about the rumors of a 12" inch surface pro tablet?

 

 

That's interesting, i've never heard about Vaios running MacOS 8/9

on 604/G3. That time i myself had a G3 Mac Clone by SuperMac

http://www.lowendmac.com/supermacs/s900.shtml

These official clones quickly vanished, they had been to expensive.

Why buying a 3rd party clone when the original is priced the same.

 

Rumors of 12,9" models are nice. 13" is a good size for the eyes.

[JahStories]

those were official apple licensed product !

 

the vaio running osx was just an experiment and was running osx not os8 or 9.

[aardvark23]

 

>Jape, that fixed the dock ethernet.  But it's still unreliable. It comes up sometimes, but not always.

 

>The product id for the bt came from Windows, so that explains why it differs.  When I do a hardware inventory under OS X, the bt >device doesn't even show up under the USB display.  I still get the messages about not being able to read/write the pipe followed by >one about being unable to load the firmware.

 

OK, more research on this shows that neither the dock ethernet nor the avastar bt will enumerate for me when the SP 2 is in the dock.  I need to remove the machine from the dock and let it sit for at least 30 seconds.  Then power it on and cold boot it.  The BT then works after about a 30 second wait, and the dock ethernet comes up as soon as you put the machine into the dock and slap the dock's ears together.

[minimojoman]

So for some reason my Windows 8 partition is still there but does not show up on clover boot screen anymore.  I have no idea what I did.  How can I edit clover so that it displays the windows 7 partition again? I cannot figure it out.  I hope I dont have to reinstall windows 8 again.  Any help would be appreciated!! :-)

 

 

Surface pro 1