the default is 0 so it is not really required to add the 0.
Funny. When I issue a "cardctl resume" command, I always get a "ioctl(): Device or resource busy" error message (which I also get when performing a cardctl resume 1, i.e. when I resume the (already operating) microdrive).
Likewise, when I issue "cardctl suspend", it does suspend both slots, not just the #0 slot, and if I don't immediately resume the #1 slot the Zaurus crashes, of course, whenever it tries to access any file on the microdrive.
So with my setup, at least, the cardctl command doesn't default to 0. I'm using Cacko 1.23 beta ROM on the 3000.
That is some strange logic within cardctl and some cards. When inserting, some cards come up suspended and others resumed. And many programs assume that it is in the "right" state initially. And that will conflict.
Yeah, that's what I finally figured out... Not a big deal but back when I was trying to configure the card it didn't make my life easy!
Hm. Is that for voice or for data calls or both? It might be the antenna - if it is broken the signal quality is very bad and it might be very dependent on small movements of the card (especially indoors). You could try to test that with AT+CSQ=?
I'll try reinstalling minicom (haven't done so since I installed the latest beta of the Cacko ROM) and check. The card would work fine in "standby" (i.e. when not connected), but it woulnd't keep a GPRS connection for long, either in my Zaurus or in my laptop PC, with no particular movement of either device - although that last point might be harder to confirm as a bad electrical contact would suffer from the sligtest vibration... Thanks for your suggestion, anyway!
