HP ProBook 6460b SD Card Not Working !!!!

[benzebulth]

hi i'm running Mavericks on my Probook 6460b, all work great with PBI. I'm using Chameleon r2377 for boot but my SD card steal not work and it is a big problem for me cause i'm working a lot with SD Card.

In System Information, in Card Reader i have nothing




It's weird cause in DPCIManager, my Card Reader show like in the next Screenshot.



I tried a lot of method but still not work so please help me.

Thank you

 

[RehabMan]

hi i'm running Mavericks on my Probook 6460b, all work great with PBI. I'm using Chameleon r2377 for boot but my SD card steal not work and it is a big problem for me cause i'm working a lot with SD Card.

In System Information, in Card Reader i have nothing

View attachment 109732


It's weird cause in DPCIManager, my Card Reader show like in the next Screenshot.

View attachment 109733

I tried a lot of method but still not work so please help me.

Thank you

Put a compatible card in the reader and it should work. It will not show in System Information in any circumstance.

 

[benzebulth]

thank's for you'r reply but what your mean with a compatible card. Cause i have a 1gb,8,16 and 32 and all of them don't work

 

[RehabMan]

thank's for you'r reply but what your mean with a compatible card. Cause i have a 1gb,8,16 and 32 and all of them don't work

I have a 16GB SDHC card and it works.

You should make sure the drivers are loading. Check in iroeg.

 

[philip_petev]

Hm, it seems I'm not the only one... Something happened with mine too after the 10.9.5 update and now it doesn't work too. I've tried to use the JMicron kext from both places (/S/L/E and EFI/Clover/kexts) and the result is one and the same: the kext seems to be loaded according to Kext Wizard, but when I insert a card (I have one 8 GB SDHC and one 32 MB SD), nobody's home. I guess it's pointless to say it works perfectly in Windows (so it's not hardware failure or something).

 

[RehabMan]

Hm, it seems I'm not the only one... Something happened with mine too after the 10.9.5 update and now it doesn't work too. I've tried to use the JMicron kext from both places (/S/L/E and EFI/Clover/kexts) and the result is one and the same: the kext seems to be loaded according to Kext Wizard, but when I insert a card (I have one 8 GB SDHC and one 32 MB SD), nobody's home. I guess it's pointless to say it works perfectly in Windows (so it's not hardware failure or something).

You can't trust Kext Wizard or 'kextstat'. Check in ioreg to be sure the driver is attached to the device.

 

[philip_petev]

You mean this:

And when I insert any of my cards, the picture becomes this:

A new branch appears under the current branch (HSSDDeviceSDMem). Well, it looks like it should work, but it doesn't, no device appears in Finder and that happens in both 10.9.5 and 10.10.

 

[RehabMan]

You mean this:

And when I insert any of my cards, the picture becomes this:

A new branch appears under the current branch (HSSDDeviceSDMem). Well, it looks like it should work, but it doesn't, no device appears in Finder and that happens in both 10.9.5 and 10.10.

Your first shot looks good. Second shot... not so much.

Here's how it should be:

 

[philip_petev]

Your first shot looks good. Second shot... not so much.

Here's how it should be:
View attachment 109770

Now, when I look at your shot, I realize where's the problem. I didn't know that JMB38X.kext and HSSDBlockStorage.kext are pair. I must have deleted it without notice. Just reinstalled it and now the card reader works. Both however don't work, if they are injected from Clover.

 

[RehabMan]

Now, when I look at your shot, I realize where's the problem. I didn't know that JMB38X.kext and HSSDBlockStorage.kext are pair. I must have deleted it without notice. Just reinstalled it and now the card reader works.

Yes, both are needed.

Both however don't work, if they are injected from Clover.

It is why I don't use Clover/kexts for my main partition and I install everything into /S/L/E. Kext injection does not work when dependencies are not in the kernel cache. So... it simply doesn't work all the time and is therefore a waste of time.