Jump to content
  • Announcements

    • Allan

      Forum Rules   04/13/2018

      Hello folks! As some things are being fixed, we'll keep you updated. Per hour the Forum Rules don't have a dedicated "Tab", so here is the place that we have our Rules back. New Users Lounge > [READ] - InsanelyMac Forum Rules - The InsanelyMac Staff Team. 
~Eureka

CardBus/PCMCIA PC Cards for Leopard

1,073 posts in this topic

Recommended Posts

Hello,

 

Here is the IOPCCardFamily file that I have worked on today. I complied the source files offered from Apple and also fixed some bugs. You do not have to edit the info.plist to match your machine. If your pccard shows "IOPCCardBridge::start failed", you can give it a try.

 

How to use?

  • Backup your original IOPCCardFamily driver (and IOPCIFamily driver)
  • Replace your IOPCCardFamily driver (and IOPCIFamily driver) with the attached one that contains all necessary modifications
  • Reboot
  • As root, type "dmesg | grep PC"; you should see something being found

Welcome to try it. Don't forget to backup the old files before trying it.

 

[iMPORTANT]

If you get the kernel panic, PLEASE check if you have replaced the following files to make your cardbus slot working before:

 

AppleACPIPlatform

AppleAPIC

IOACPIFamily

 

If you did, you probably need to find a way to restore those files first.

If you still get kernel panic, you can take the picture of it if possible. Thanks.

 

[KNOWN ISSUES]

It may cause kernel panic with AGPGart installed.....

If you have the error message "IOPCCardBridge::checkBridgeBusIDs invalid sub/cardbus/pci settings of 0x0" before trying the rev3 file, it still may not work after trying the rev3 file.

Chun-Nan

 

Kext File: IOPCCardFamily_chunnan_rev3.zip

Source Code: IOPCCardFamily_48_chunnan.zip

 

[uPDATE]

1/17/2008: rev6 and source code update

Please replace IOPCCardFamily and IOPCIFamily at the same time.

You DO NOT have to edit info.plist because it will use "ADP2,1" by default.

If you are using other revisions, please update to rev6.

If possible, let me know the result. Thanks.

 

IOPCCardFamily_chunnan_Leopard_rev6.zip

IOPCCardFamily_chunnan_Leopard_rev6_src.zip

 

1/30/2008: rev7 and source code update

Please replace IOPCCardFamily and IOPCIFamily at the same time.

You DO NOT have to edit info.plist because it will use "ADP2,1" by default.

If you are using other revisions, please update to rev7.

If possible, let me know the result. Thanks.

 

IOPCCardFamily_chunnan_Leopard_rev7.zip

IOPCCardFamily_chunnan_Leopard_rev7_src.zip

 

2/7/2008: rev8 and source code update

Please replace IOPCCardFamily and IOPCIFamily at the same time.

You DO NOT have to edit info.plist because it will use "ADP2,1" by default.

If you are using other revisions, please update to rev8.

If possible, let me know the result. Thanks.

 

IOPCCardFamily_chunnan_Leopard_rev8.zip

IOPCCardFamily_chunnan_Leopard_rev8_src.zip

 

5/25/2008: beta3 installation package update

Please choose IOPCCardFamily and IOPCIFamily at the same time.

If possible, let me know the result. Thanks.

PCCard.10.5.2.beta3.zip

 

11/30/2008: beta IOPCMCIAFamily update

http://www.mediafire.com/chunnan

 

 

==========

{ "Cirrus PD6729", IS_CIRRUS|IS_PCI, ID(CIRRUS, 6729) }

{ "Cirrus PD6730", IS_CIRRUS|IS_PCI, PCI_VENDOR_ID_CIRRUS, -1 }

{ "Cirrus PD6832", IS_CIRRUS|IS_CARDBUS, ID(CIRRUS, 6832) }

{ "ENE 1211", IS_TI|IS_CARDBUS, ID(ENE, 1211) } <= new added

{ "ENE 1225", IS_TI|IS_CARDBUS, ID(ENE, 1225) } <= new added

{ "ENE 1410", IS_TI|IS_CARDBUS, ID(ENE, 1410) } <= new added

{ "ENE 710/2/4", IS_TI|IS_CARDBUS, ID(ENE, 1411) } <= new added

{ "ENE 712/4", IS_TI|IS_CARDBUS, ID(ENE, 1412) } <= new added

{ "ENE 1420", IS_TI|IS_CARDBUS, ID(ENE, 1420) } <= new added

{ "ENE 720/2/4", IS_TI|IS_CARDBUS, ID(ENE, 1421) } <= new added

{ "ENE 722/4", IS_TI|IS_CARDBUS, ID(ENE, 1422) } <= new added

{ "O2Micro OZ6729", IS_O2MICRO|IS_PCI|IS_VG_PWR, ID(O2, 6729) }

{ "O2Micro OZ6730", IS_O2MICRO|IS_PCI|IS_VG_PWR, ID(O2, 6730) }

{ "O2Micro OZ6832/33", IS_O2MICRO|IS_CARDBUS, ID(O2, 6832) }

{ "O2Micro OZ6836/60", IS_O2MICRO|IS_CARDBUS, ID(O2, 6836) }

{ "O2Micro OZ6812", IS_O2MICRO|IS_CARDBUS, ID(O2, 6812) }

{ "O2Micro OZ6922", IS_O2MICRO|IS_CARDBUS, ID(O2, 6922) }

{ "O2Micro OZ6933/711E1", IS_O2MICRO|IS_CARDBUS, ID(O2, 6933) }

{ "O2Micro OZ6912/711E0", IS_O2MICRO|IS_CARDBUS, ID(O2, 6912) }

{ "O2Micro OZ711EC1/M1", IS_O2MICRO|IS_CARDBUS, ID(O2, 7112) }

{ "O2Micro OZ711EC1", IS_O2MICRO|IS_CARDBUS, ID(O2, 7113) }

{ "O2Micro OZ711M1/MC1", IS_O2MICRO|IS_CARDBUS, ID(O2, 7114) }

{ "O2Micro OZ711MP1/MS1", IS_O2MICRO|IS_CARDBUS, ID(O2, 7134) } <= new added

{ "O2Micro OZ711EZ1", IS_O2MICRO|IS_CARDBUS, ID(O2, 7135) } <= new added

{ "O2Micro OZ711SP1", IS_O2MICRO|IS_CARDBUS, ID(O2, 7136) } <= new added

{ "O2Micro OZ711E2", IS_O2MICRO|IS_CARDBUS, ID(O2, 71E2) }

{ "O2Micro OZ711M2", IS_O2MICRO|IS_CARDBUS, ID(O2, 7212) }

{ "O2Micro OZ711M3/MC3", IS_O2MICRO|IS_CARDBUS, ID(O2, 7223) }

{ "O2Micro OZ711MP3/MS3", IS_O2MICRO|IS_CARDBUS, ID(O2, 7233) } <= new added

{ "Ricoh RL5C465", IS_RICOH|IS_CARDBUS, ID(RICOH, RL5C465) }

{ "Ricoh RL5C466", IS_RICOH|IS_CARDBUS, ID(RICOH, RL5C466) }

{ "Ricoh RL5C475", IS_RICOH|IS_CARDBUS, ID(RICOH, RL5C475) }

{ "Ricoh RL5C476", IS_RICOH|IS_CARDBUS, ID(RICOH, RL5C476) }

{ "Ricoh RL5C477", IS_RICOH|IS_CARDBUS, ID(RICOH, RL5C477) } <= new added

{ "Ricoh RL5C478", IS_RICOH|IS_CARDBUS, ID(RICOH, RL5C478) }

{ "SMC 34C90", IS_CARDBUS, ID(SMC, 34C90) }

{ "TI 1130", IS_TI|IS_CARDBUS, ID(TI, 1130) }

{ "TI 1131", IS_TI|IS_CARDBUS, ID(TI, 1131) }

{ "TI 1031", IS_TI|IS_CARDBUS, ID(TI, 1031) }

{ "TI 1210", IS_TI|IS_CARDBUS, ID(TI, 1210) }

{ "TI 1211", IS_TI|IS_CARDBUS, ID(TI, 1211) }

{ "TI 1220", IS_TI|IS_CARDBUS, ID(TI, 1220) }

{ "TI 1221", IS_TI|IS_CARDBUS, ID(TI, 1221) }

{ "TI 1225", IS_TI|IS_CARDBUS, ID(TI, 1225) }

{ "TI 1250A", IS_TI|IS_CARDBUS, ID(TI, 1250A) }

{ "TI 1251A", IS_TI|IS_CARDBUS, ID(TI, 1251A) }

{ "TI 1251B", IS_TI|IS_CARDBUS, ID(TI, 1251B) }

{ "TI 1410", IS_TI|IS_CARDBUS, ID(TI, 1410) }

{ "TI 1420", IS_TI|IS_CARDBUS, ID(TI, 1420) }

{ "TI 1450", IS_TI|IS_CARDBUS, ID(TI, 1450) }

{ "TI 1451", IS_TI|IS_CARDBUS, ID(TI, 1451) }

{ "TI 1510", IS_TI|IS_CARDBUS, ID(TI, 1510) }

{ "TI 1520", IS_TI|IS_CARDBUS, ID(TI, 1520) }

{ "TI 1620", IS_TI|IS_CARDBUS, ID(TI, 1620) }

{ "TI 4410", IS_TI|IS_CARDBUS, ID(TI, 4410) }

{ "TI 4450", IS_TI|IS_CARDBUS, ID(TI, 4450) }

{ "TI 4451", IS_TI|IS_CARDBUS, ID(TI, 4451) }

{ "TI 4510", IS_TI|IS_CARDBUS, ID(TI, 4510) }

{ "TI 4520", IS_TI|IS_CARDBUS, ID(TI, 4520) }

{ "TI 7410", IS_TI|IS_CARDBUS, ID(TI, 7410) }

{ "TI 7510", IS_TI|IS_CARDBUS, ID(TI, 7510) }

{ "TI 7610", IS_TI|IS_CARDBUS, ID(TI, 7610) }

{ "TI 7420", IS_TI|IS_CARDBUS, ID(TI, 7510) } <= new added

{ "TI 7620", IS_TI|IS_CARDBUS, ID(TI, 7610) } <= new added

{ "TI XX12", IS_TI|IS_CARDBUS, ID(TI, XX12) }

{ "TI XX21", IS_TI|IS_CARDBUS, ID(TI, XX21) } <= new added

{ "TI 6515", IS_TI|IS_CARDBUS, ID(TI, 6515) } <= new added

{ "Toshiba ToPIC95-A", IS_CARDBUS|IS_TOPIC, ID(TOSHIBA, TOPIC95_A) }

{ "Toshiba ToPIC95-B", IS_CARDBUS|IS_TOPIC, ID(TOSHIBA, TOPIC95_:blink: }

{ "Toshiba ToPIC97", IS_CARDBUS|IS_TOPIC, ID(TOSHIBA, TOPIC97) }

{ "Toshiba ToPIC100", IS_CARDBUS|IS_TOPIC, ID(TOSHIBA, TOPIC100) }

==========

I don't know if the new added devices will work or not. However, you can give it a try and let me know the result. In addition, if your pccard slot works under linux and it is not listed on the above the list (and if you believe it may work under mac), let me know the device id and I will try to add it to the next revision.

Share this post


Link to post
Share on other sites

Chun-nan,

 

 

First, thanks a lot for your work :-)

 

I was just starting to try and do something similar, but from the looks of it you know FAR more than I do.. ;-)

 

 

 

I've tried this myself (my own compile from your source, my device id isn't in the supported list), and it causes a kernel panic, much like what a couple of people were seeing in the old/other thread.

Seems to be just after it launches AppleACPIPS2Nub (or whatever the kext is called, I forget now.. Definitely the ps2nub one..).

 

 

I'm going to compile the development (I assume this is the debug version) target shortly, and will try with it.

 

 

So you know, my controller is an o2micro.. OZ711EZ1. It's supported fine in Linux, but not in osx because the headers they're using are too old.

 

 

Any input you have, questions, or things to try would be appreciated :)

 

Thanks,

EqUaTe

Share this post


Link to post
Share on other sites
Chun-nan,

 

 

First, thanks a lot for your work :-)

 

I was just starting to try and do something similar, but from the looks of it you know FAR more than I do.. ;-)

 

 

 

I've tried this myself (my own compile from your source, my device id isn't in the supported list), and it causes a kernel panic, much like what a couple of people were seeing in the old/other thread.

Seems to be just after it launches AppleACPIPS2Nub (or whatever the kext is called, I forget now.. Definitely the ps2nub one..).

 

 

I'm going to compile the development (I assume this is the debug version) target shortly, and will try with it.

 

 

So you know, my controller is an o2micro.. OZ711EZ1. It's supported fine in Linux, but not in osx because the headers they're using are too old.

 

 

Any input you have, questions, or things to try would be appreciated :)

 

Thanks,

EqUaTe

 

Hi EqUaTe,

 

It will be a good idea to compile the source to the development because you may have more ideas where it cause the kernel panic.

 

I checked the source (modules/o2micro.h) and it seemed that your card is not listed in it. You can try to add your card to the list by using the same format as other cards. (You need to add your cards in three different place inside o2micro.h. Go through the o2micro.h and you will know the format.)

 

However, I don't have o2micro.. OZ711EZ1 myself so I cannot test it and I don't know if it will work or not.

 

Chun-Nan

Share this post


Link to post
Share on other sites

Great work Chun-Nan.

 

I have a multicard reader on my Dell Laptop (SD, MMC, MS, etc) and it is Ricoh chipset based and it is attached on the PCI bus instead of the USB. I am wondering if this could work, what do you think?

Share this post


Link to post
Share on other sites
Hi EqUaTe,

 

It will be a good idea to compile the source to the development because you may have more ideas where it cause the kernel panic.

 

I checked the source (modules/o2micro.h) and it seemed that your card is not listed in it. You can try to add your card to the list by using the same format as other cards. (You need to add your cards in three different place inside o2micro.h. Go through the o2micro.h and you will know the format.)

 

However, I don't have o2micro.. OZ711EZ1 myself so I cannot test it and I don't know if it will work or not.

 

Chun-Nan

 

 

Hey,

 

I've already added it. I've compiled the development version, but haven't had a chance to play with it yet.

I'll be giving it a go hopefully later tonight.

 

Would the dmesg from your debug version of IOPCIFamily.kext help diagnosis at all?

When I try things again I do plan on getting better documentation - I couldn't really at the time as I needed things to be working for later that day..

 

Hopefully your kext can become as thorough and as capable as the pcmcia-cs stuff is :)

Especially given as this kext is based off of that ^_^

As I said, the controller is supported in linux with pcmcia-cs, which is why I'm hopeful that we can get it to work with this kext.

 

Again, thanks for your work!

 

I'll report back later.

 

Cheers,

EqUaTe

Share this post


Link to post
Share on other sites

Works fine on a Thinkpad R60, detected my Buffalo WLI-CB-G54HP PCMCIA as airport and straight on my wireless network.

 

Thanks very much.

Share this post


Link to post
Share on other sites

Chun-nan,

 

Bit more info - looks as if the PCCardFamily almost loads properly, then something happens, or something else tries to load and it goes bang..

 

I'm attaching a screenshot of the output.. However, I may have gotten SOME useful info out of it.. The IO and Mem ranges that osx sees the controller as using.. ;) (At least, I hope that's what those details are! :( )

 

Any ideas from this point?

 

Thanks,

EqUaTe

 

 

post-25855-1200176130_thumb.jpg

Share this post


Link to post
Share on other sites
Chun-nan,

 

Bit more info - looks as if the PCCardFamily almost loads properly, then something happens, or something else tries to load and it goes bang..

 

I'm attaching a screenshot of the output.. However, I may have gotten SOME useful info out of it.. The IO and Mem ranges that osx sees the controller as using.. :) (At least, I hope that's what those details are! ;) )

 

Any ideas from this point?

 

Thanks,

EqUaTe

 

 

post-25855-1200176130_thumb.jpg

 

Hi EqUaTe,

 

Try to do this to see if anything changes:

 

1. Open IOPCCardBridge.cpp

2. Search the following string and remark it:

if (!settings) settings = OSDynamicCast(OSDictionary, config->getObject("Test Machine"));

3. Open Info-IOPCCardFamily.plist

4. Under Configuration Settings, use the same format and add your machine name, I/O Port Ranges, and Memory Ranges.

5. Compile and load it.

 

OR

1. Open IOPCCardBridge.cpp

2. Search the following string and replace "Test Machine" with "ADP2,1":

if (!settings) settings = OSDynamicCast(OSDictionary, config->getObject("Test Machine"));

3. Compile and load it.

 

Let me know the result.

 

Chun-Nan

Share this post


Link to post
Share on other sites

Cool, will try this in a few minutes.

 

Just to be sure, I'll try both, starting with the 2nd method.

Share this post


Link to post
Share on other sites

Ok, the second method changes the ranges that the pccard stuff mentions, but it still panics.

 

The first option (w/o adding a section to the Info.plist) also causes a panic - it looks like it's still autodetecting the ranges as well.

 

I'll try it again tomorrow, after adding stuff to Info.plist.

 

 

Any other suggestions?

 

Off to bed now, so will have a go at some point tomorrow.

Share this post


Link to post
Share on other sites

first of all THANX for your kext!

worked fine but it needs a bit of tuning for 02micro controllers.

i own O2 Micro, Inc. OZ711MP1/MS1 vendor:device 1217:7134

 

Equate this is for you and for o2micro owners:

 

step 1: check in system profile the model of your machine (i.e. i'm using efi and my model is: "TravelMate 8210")

edit the plist file of iopccardfamily.kext and add your machine id in the configuration settings.

(actually the plist has only ADP2,1 ; >PowerBook1,1 ; etc.).

is possible also to insert the memory address of o2micro, ripping them from any linux distro, but is not necessary (the default values of ADP2,1 memory and i/o addresses worked fine for me)

 

step 2 (this is needed ONLY if your device id is not present in supported devices): with hex editor open the file iopccardfamily that is stored into the iopccardfamily.kext

look for the hex string 1712 (yes, is the vendor id reversed 1217 --- 1712).

you will find a long list of o2micro supported devices, 17122962 (o2micro 1217 device id 6229) , 17123A67 (o2micro 1217 device id 673A), 17123668 , etc

simply overwrite one device id with yours.

in my case i've choosen the 17121471, and ive pasted mine (7134 reversed --- 3471), so the new hex become: 17123471

 

if everything is ok you'll get a brand new pcmcia slot ready to work ! :(

 

another important thing i've noticed: for me the bios update was an usefull help. Without the upgrade, same edited kext won't work.

Share this post


Link to post
Share on other sites
first of all THANX for your kext!

worked fine but it needs a bit of tuning for 02micro controllers.

i own O2 Micro, Inc. OZ711MP1/MS1 vendor:device 1217:7134

 

...

 

So this is your PCMCIA Controller?

 

 

...

 

step 2 (this is needed ONLY if your device id is not present in supported devices): with hex editor open the file iopccardfamily that is stored into the iopccardfamily.kext

look for the hex string 1712 (yes, is the vendor id reversed 1217 --- 1712).

you will find a long list of o2micro supported devices, 17122962 (o2micro 1217 device id 6229) , 17123A67 (o2micro 1217 device id 673A), 17123668 , etc

simply overwrite one device id with yours.

in my case i've choosen the 17121471, and ive pasted mine (7134 reversed --- 3471), so the new hex become: 17123471

 

if everything is ok you'll get a brand new pcmcia slot ready to work ! :)

 

another important thing i've noticed: for me the bios update was an usefull help. Without the upgrade, same edited kext won't work.

 

Yeah!!! I think that is the hint and what we're looking for all the time, also for other chips...

 

Did you find other VEN there, e.g. 1180 (8011) and e.g. DEV ID 0476 (7604)?

Share this post


Link to post
Share on other sites

afaik there is also a list of supported devices in text mode.

those are the "default" supported pcmcia i've found in the hex files:

Intel 82092AA...Omega Micro 82C092G.Cirrus PD6729...Cirrus PD6730...Cirrus PD6832...O2Micro OZ6729..O2Micro OZ6730..O2Micro OZ6832/33...O2Micro OZ6836/60...O2Micro OZ6812..O2Micro OZ6912/711E0....O2Micro OZ6933/711E1....O2Micro OZ711EC1/M1.O2Micro OZ711EC1....O2Micro OZ711M1.O2Micro OZ711E2.O2Micro OZ711M2.O2Micro OZ711M3.Ricoh RL5C465...Ricoh RL5C466...Ricoh RL5C475...Ricoh RL5C476...Ricoh RL5C478...SMC 34C90...TI 1130.TI 1131.TI 1031.TI 1210.TI 1211.TI 1220.TI 1221.TI 1225.TI 1250A....TI 1251A....TI 1251B....TI 1410.TI 1420.TI 1450.TI 1451.TI 1510.TI 1520.TI 1620.TI 4410.TI 4450.TI 4451.TI 4510.TI 4520.TI 7410.TI 7510.TI 7610.TI XX12.TI XX21.Toshiba ToPIC95-A...Toshiba ToPIC95-B...Toshiba ToPIC97.Toshiba ToPIC100

 

if your vendor id is included, you're a lucky one, so prolly a simple device id edit is enough.

If not, no cules, only an expert like chun-nan can help you

Share this post


Link to post
Share on other sites

you need to use an hex editor.

open the iopccardfamily file into the contest/macos/ folder that is inside iopccardfamily.kext

i've looked for your vendor id (8011)and there are some: (i've simply used the search hex value 8011)

80116504

80116604

80117504

80117604

80117804

 

choose the most similar to yours and change it

Share this post


Link to post
Share on other sites

Oh man, i'm really a dumb lol

 

I thought we're speaking about IOPCIFamily, cause this is the problem...

There is something wrong to PCIFamily, because my PCMCIA doesn't start...

 

With a hacked old one it starts...so we have to edit vanilla Leo PCIFamily to get Ricoh Chipset running...but i don't know what :hysterical:

 

PS: My ID is inside IOPCCardFamily (80117604) already :)

Share this post


Link to post
Share on other sites
first of all THANX for your kext!

worked fine but it needs a bit of tuning for 02micro controllers.

i own O2 Micro, Inc. OZ711MP1/MS1 vendor:device 1217:7134

 

Equate this is for you and for o2micro owners:

 

step 1: check in system profile the model of your machine (i.e. i'm using efi and my model is: "TravelMate 8210")

edit the plist file of iopccardfamily.kext and add your machine id in the configuration settings.

(actually the plist has only ADP2,1 ; >PowerBook1,1 ; etc.).

is possible also to insert the memory address of o2micro, ripping them from any linux distro, but is not necessary (the default values of ADP2,1 memory and i/o addresses worked fine for me)

 

First off, nice try, but not so good for me :-/

As I understand it, you shouldn't need to modify chun-nan's rev3 kext for this - it's supposed to essentially autodetect them (at least, that's how I understood it..)

 

step 2 (this is needed ONLY if your device id is not present in supported devices): with hex editor open the file iopccardfamily that is stored into the iopccardfamily.kext

look for the hex string 1712 (yes, is the vendor id reversed 1217 --- 1712).

you will find a long list of o2micro supported devices, 17122962 (o2micro 1217 device id 6229) , 17123A67 (o2micro 1217 device id 673A), 17123668 , etc

simply overwrite one device id with yours.

in my case i've choosen the 17121471, and ive pasted mine (7134 reversed --- 3471), so the new hex become: 17123471

 

if everything is ok you'll get a brand new pcmcia slot ready to work ! :)

 

another important thing i've noticed: for me the bios update was an usefull help. Without the upgrade, same edited kext won't work.

 

I did give this a shot, but it made no difference.

I've been compiling from chun-nan's source mostly, and saw the same results doing this - a kernel panic.

My reason for compiling from source was because the ID wasn't present.

 

 

Chun-nan:

 

Pretty sure I've now tried both of your suggestions, to no avail. The first option didn't seem to make any difference, so I may have done something wrong.

The second option changed the IO & mem ranges shown in the panic, but from what I could tell that was it.

What would you recommend for checking the IO & Mem ranges? So far I've tried Windows, Debian/sid, Ubuntu Gutsy 64bit, Kanotix Thorhammer RC7.

Debian & Kanotix give the same results, Gutsy gives another set, and Windows gives a third. I suspect that if I tried the 32bit Gutsy I'd get the same results as with Debian & Kanotix - all three are Debian-based.

 

Just to make sure - when using the source, I should extract the tarball, then copy the two cpp files in your archive into the extracted tarball, replacing the existing ones?

 

Do you have any other suggestions?

At this point I'm willing to try just about anything - there's nothing on the osx install that I can't recover or afford to lose, so if I end up having to blow it away and start over, I can live with that. In fact, I plan on it.. (The partition it's on just now is a bit too small :P )

 

Thanks guys!

 

EqUaTe

Share this post


Link to post
Share on other sites

omg thank you soo much now my pcmia slot 104c:8039 works on my VAIO

however my pcixx12 Texas Instruments 5-in-1 Multimedia Card Reader does not 104c:803b

Share this post


Link to post
Share on other sites
Great work Chun-Nan.I have a multicard reader on my Dell Laptop (SD, MMC, MS, etc) and it is Ricoh chipset based and it is attached on the PCI bus instead of the USB. I am wondering if this could work, what do you think?
Hi macgirl,I think the multicard reader needs another driver to make it function.....Chun-Nan
omg thank you soo much now my pcmia slot 104c:8039 works on my VAIOhowever my pcixx12 Texas Instruments 5-in-1 Multimedia Card Reader does not 104c:803b
Hi kamikazi,I think the multicard reader needs another driver to make it function.....Chun-Nan
First off, nice try, but not so good for me :-/As I understand it, you shouldn't need to modify chun-nan's rev3 kext for this - it's supposed to essentially autodetect them (at least, that's how I understood it..)I did give this a shot, but it made no difference.I've been compiling from chun-nan's source mostly, and saw the same results doing this - a kernel panic.My reason for compiling from source was because the ID wasn't present.Chun-nan:Pretty sure I've now tried both of your suggestions, to no avail. The first option didn't seem to make any difference, so I may have done something wrong.The second option changed the IO & mem ranges shown in the panic, but from what I could tell that was it.What would you recommend for checking the IO & Mem ranges? So far I've tried Windows, Debian/sid, Ubuntu Gutsy 64bit, Kanotix Thorhammer RC7.Debian & Kanotix give the same results, Gutsy gives another set, and Windows gives a third. I suspect that if I tried the 32bit Gutsy I'd get the same results as with Debian & Kanotix - all three are Debian-based.Just to make sure - when using the source, I should extract the tarball, then copy the two cpp files in your archive into the extracted tarball, replacing the existing ones?Do you have any other suggestions?At this point I'm willing to try just about anything - there's nothing on the osx install that I can't recover or afford to lose, so if I end up having to blow it away and start over, I can live with that. In fact, I plan on it.. (The partition it's on just now is a bit too small ;) )Thanks guys!EqUaTe
Hi EqUaTe,After few days studying the source codes, I found out the key problem may be on IOPCIFamily (thanks those who helped me to test). I have uploaded the rev4 and you can give it a try.Chun-Nan

Share this post


Link to post
Share on other sites

Thanks Chun-Nan!

 

Will give it a shot shortly. Have to go out soon, so may not be until this afternoon, but here's hoping!

 

 

EqUaTe

Share this post


Link to post
Share on other sites

Hi Chun-Nan,

 

I've just tried it, but still the same error ;)

 

I don't have to put my IO and memory windows values into IOPCCard Info.plist ?

 

Regards,

Mariusz.

Share this post


Link to post
Share on other sites
Hi Chun-Nan,

 

I've just tried it, but still the same error ;)

 

I don't have to put my IO and memory windows values into IOPCCard Info.plist ?

 

Regards,

Mariusz.

 

Did you replace IOPCIFamily.kext AND IOPCCardFamily.kext ?

 

No, you shouldn't have to edit the plist at all.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Recently Browsing   0 members

    No registered users viewing this page.

×