Mavericks does not recognize ExpressCard

Looks like Mavericks doesn't support the ExpressCard/34 interface on my mid-2010 17" MacBook Pro.

Apple...if you're listening...I use the ExpressCard/34 to transfer photos and don't want to go backwards to transferring via USB2.

Apple...please add ExpressCard/34 support to Mavericks. I'm going back to Mountain Lion for now.

Same problem here!

I already tried everything that I could... Installed new kexts, reboot, reboot, drivers, nothing.

And I have also Kernel Panics when I boot the system with the cards pluged.

I don´t use SSD cards, but esata card and usb 3.0 card.

In OSX 10.8.5 everything is working. I tried to copy the drivers from Mountain Lion without sucess.

Seems that have a bug that block the acess to ExpressCard in Macbook 17" mid 2010 or whatever.

Hope the solution come soon or keep going with Mountain Lion forever...

Same here. Express card Filemate 48 GB ultra ssd doesn't work.

Mid 2010 Macbook Pro 17" - Sonnet Tempo Edge SATA pro6Gb & Wintec Filemate 128Gb - both not working. I contacted support for both companies.

Wintec says it's an Apple issue and closed my support ticket.

Sonnet has not responded.

As far as I know, there are no user-installable drivers for these cards. Please correct me if I'm wrong, as I'd like to find a solution... the SATA card is used for backups and the Wintec Filemate is extra storage for my iTunes library and documents.

Please send Apple Feedback if you do have this problem.

http://www.apple.com/feedback/

Wintec 128GB SSD in ExpressCard port. Interesting results here: card works flawlessly under Mavericks on a 17" 2008 MBP. Does not work on 17" mid 2010 MBP. This has to be a driver for the later ExpressCard hardware.

Same issue here folks.

I have two USB 3 cards and an E-Sata PC34 Express card that are no longer recognized in my very expensive MBP17" mid 2010 model (Apple identifier is MacBookPro6,1). The E-Sata card has never needed 3rd party drivers and has been recognized by the built in drivers since 10.6.8 to 10.8.x.

Apple must have "forgot" to add in the base PC34 Express Card driver support, because if you use the System Profiler app, it says there are no PCI Express Card slots in my MBP17" and no PC Card shows up on the Menu Bar either when insterted.

Good thing Mavericks is "Free", because if they had charged me money for this type of "innovation" (I'm guessing this is one of those 200+ "features" they have added to Mavericks, right?), I'd be a Severely PO'd old man.

Just another way that Apple has let us all down doing inadequate testing on their own hardware as they dumb down the Mac interface until it reaches parity with iOS on an iPod.

Maybe I found a solution for my ExpressCards (JMicron chipset jmb363) that was not working after I installed Mavericks.

I have the same MAC than you PO_OLD_MAN and I tried many things for days, testing, booting and doing some tricks. After a week I manage to back my eSata ExpressCard work properly again. Just my GMYLE USB 3.0 doesn´t work properly. It mount but when I try to copy in and copy some files Finder returns a Error Code -36 (cannot write or read from the disk).

So, I did the following:

1)Install (using the Multibeast software) the drivers 3rd Party esata, 3rd Party sata and USB 3.0 Universal.

2)Reboot the system

3)Go to your Mavericks /System/Lybrary/Extensions and delete the kext IOPCIFamily.kext

4)From a installed system of Mountain Lion go to the same folder /System/Lybrary/Extensions and copy the same file (IOPCIFamily.kext) to a pen drive or other place.

5) Back in Mavericks, download the Kext Wizard software and run it.

6) Go to the tab instalation and drag the kext copied form Mountain Lion inside the white box in the window software.

7) Install the kext.

8) Go to the Maintenance tab and select System/Library/Extension (Repair Permitions and Rebuild Cache) and Execute.

9) Reboot the system and conect the eSata HDD.

You´ll have your esata working again.

(I didn´t test everything yet but at least is mounted in Mavericks and I have my esata working again.

Hope that don´t cause other problems.)

I have not upgraded to Mavericks yet and have a Sonnet Tempo SATA Express 34 card. Mine is not the Pro model. There is an installer associated with this card that installs a kext file called SiliconImage3132.kext in System/Library/Extensions/. This file is invariably ejected by new OS installs as being incompatible and put in a folder labeled as such as the root of the boot drive.

I have traditionally just copied this file back to its correct location and the card has worked just fine. Maybe this is a change for Mavericks, but it is worth a look and a try for some Sonnet card users.

I have a Late 2011 17" MacBook Pro, and I have 3 ExpressCard 34 cards for it. One card is a 21-in-1 media card reader, and it seems to be working perfectly under Mavericks. The other 2 are E-Sata cards, and they both rely on the ancient SiliconImage3132 chipset. When installing Mavericks, the Kernerl Extension (kext) was removed and placed in the "incompatible software" folder (just liek with Mountain Lion). Much like with Mountain Lion, I re-installed the driver (using v1.2.6 release Nov 2012 I beleive) from SIIG, and both of those cards are working for me as well.

I would guess that you need to find updated drivers for your cards, or buy newer/supported cards...

Thanks for the suggestions, but the issue isn't missing drivers.

No PC34 cards are even recognized on a MBP 17" 2010 model. It is specific to the 2010 model, if you have a 2011 or a 2009 and earlier model, then you don't have this issue.

The Apple System Profiler doesn't even admist the Mac 2010 have PC34 slots in your Mac. If you insert a PC34 card, it should show up as a PC Card on the menu bar and should also show up in the System Profiler as a generic PC Card. Even if your card has no drivers, it still shows up in System Profiler. The profiler also indicates if your PC34 card has drivers or not too, so it;s handy checking on them too.

So what Apple did was "forgot" to include the PC34 Express card slot driver in 10.9 - which sure speaks volumes about them doing any backwards testing on their own most expensive hardware.

I have already talked to CalDigit about this and they confirmed this is an issue with only the MBP 2010 models.

I have also filed a developers bug report with Apple too yesterday. Of course I have 41 bug still pending, so when this gets fixed is anyones guess as no new Mac models have PC34 slots.

Luckily for me, I only need Mavericks for software testing and my day to day System is still 10.6.8 on a separate partition. So when apple pushes out the next update, it hopefully will be fixed.

My MacBook Pro 15" Early 2008 (MacBook Pro4,1) running under Mavericks recognises my Kensington 7-in-1 media reader for express card (33407EU) with an SD card inserted in the reader. It appears under Hardware/USB with Product ID 00x715, Vendor ID 0x5e3 (Genesys Logic, Inc.), Version 94.12. This card is still available for sale at £15 on Amazon UK.

Anyone with this card find it doesn't work on their MacBook Pro?

Thank You!

I have a mid-2010 17" MacBook Pro, and after upgrading from ML 10.8.5 to Mavericks last night, I can verify this issue. I have an RME Digiface soundcard connected with their HDSPe Express Card to the MBP's ExpressCard slot. When I boot up the computer, it won't recognize the hardware at all (I'm using RME's latest drivers with Mavericks support).

I followed your instructions and copied the ML 10.8.5 version of IOPCIFamily.kext file from my Time Machine backups on top of the Mavericks version using Kext Wizard, and rebooted. Everything works again!

I guess this is the only way to fix the problem until Apple releases an update. *sigh*

For me, too, the flaw seems to be in Mavericks' ExpressCard support for this model:

MacBook Pro 17" Mid 2010

aka MacBook Pro 6,1

A Google Search for "expresscard mavericks" is turning up reports all over the place, but comparable MacBooks both newer and older don't appear to be affected.

My own ExpressCard is an eSATA controller from Sonnet; it's AHCI compliant so it doesn't even need a driver but that presumes the OS is behaving itself, which it isn't. I spoke to a tech at Sonnet who was able to corroborate my findings. He suggested that Apple is aware of this.

I'm too paranoid to attempt that hack above but I'm bookmarking this thread in case 10.9.1 doesn't fix the issue.