CDMA modem (CF2031) failures

For the last few weeks I have been really pounding my head over this problem
with the Sprint CDMA modem I have recently bought.

If anyone is interested this is the card:

    http://www.growell.co.kr/telecom/product/pr_sub2.htm

It acts as a normal serial card so theoretically it should work fine with the
serial_cs driver.

By default it did not work with my pcmcia config:

    Jan 9 01:12:55 universe kernel: Testing ttyS0 (0x03f8, 0x0000)...
    Jan 9 01:12:55 universe kernel: serial: ttyS0: simple autoconfig failed (ff, ff)
    Jan 9 01:12:55 universe kernel: register_serial(): autoconfig failed
    Jan 9 01:12:55 universe kernel: serial_cs: register_serial() at 0x03f8, irq 3 failed

Then I added the following line in /etc/pcmcia/config.opts

    exclude port 0x3f8-0x3ff

Which obviously makes sense...

Now it registers just fine:

    ttyS01 at port 0x02f8 (irq = 3) is a 16C950/954

So all is well and good.  But the problem is that now I can't communicate with
the card.  Both minicom and pppd fail to talk to the card and I can't even

how to debug a "get dev info on socket 0 failed" error?

What does "bind" mean, what binds to what or for what reason?  And why doesn't 
it work?

Environment: am embedded system with an Intel PXA250 processor (that's some 
ARM like processor)
Linux 2.4.19-rmk4-pxa2
pcmcia-cs 3.2.3

I'm using the kernel-modules, in /etc/modules.conf there is a line "alias 
alias ide_cs ide-cs pc_debug=9".

Question: is this correct?   Why aren't those drivers named equally?  It's a 
pain-in-the-ass to have an ide-cs.o and ide_cs.o 

Anyway, when I boot without any card and call dmesg, then I see:

ds.c 1.112 2001/10/13 00:08:28 (David Hinds)
cs: bind_device(): client 0xc0376a60, sock 0, dev Driver Services
cs: register_client(): client 0xc0376a60, sock 0, dev Driver Services
cs: bind_device(): client 0xc0376b60, sock 1, dev Driver Services
cs: register_client(): client 0xc0376b60, sock 1, dev Driver Services
Looking up port of RPC 100003/2 on 192.168.233.1
Looking up port of RPC 100005/1 on 192.168.233.1
VFS: Mounted root (nfs filesystem).
Mounted devfs on /dev
Freeing init memory: 80K
ds_open(socket 0)
ds_open(socket 1)
ds_open(socket 2)
ds_open(socket 2)

bad link

In the Programmer's Guide the last link (in the section "Where to Go for More 
Information") is broken, it points to

http://pcmcia-cs.sourceforge.net/pcmcia-cs.sourceforge.net/specs

but should point to

http://pcmcia-cs.sourceforge.net/specs

-------------------------------------------------------
This SF.net email is sponsored by: Scholarships for Techies!
Can't afford IT training? All 2003 ictp students receive scholarships.
Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more.
www.ictp.com/training/sourceforge.asp

Re: how to debug a "get dev info on socket 0 failed" error?

On Wed, Jan 22, 2003 at 11:01:06AM +0100, Holger Schurig wrote:
> 
> Environment: am embedded system with an Intel PXA250 processor (that's some 
> ARM like processor)
> Linux 2.4.19-rmk4-pxa2
> pcmcia-cs 3.2.3
> 
> I'm using the kernel-modules, in /etc/modules.conf there is a line "alias 
> alias ide_cs ide-cs pc_debug=9".
>
> Question: is this correct?   Why aren't those drivers named equally?  It's a 
> pain-in-the-ass to have an ide-cs.o and ide_cs.o 

No this line is not correct.  Yes it was a pain in the ass when some
idiot renamed ide_cs in the kernel tree to ide-cs without knowing the
implications of that.  But there is no longer any ide_cs driver; I
changed the name in the pcmcia-cs package six months ago.  The 3.2.3
package has only ide-cs and the config file only refers to ide-cs.

> cardmgr[248]: executing: 'modprobe ide_cs'

Your /etc/pcmcia/config file is not the one provided with the 3.2.3
pcmcia-cs package.  Do a proper install and the error will go away.

-- Dave

-------------------------------------------------------
This SF.net email is sponsored by: Scholarships for Techies!
Can't afford IT training? All 2003 ictp students receive scholarships.
Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more.

Oops report

P3-1ghz Dell Inspiron 4100
640 megs ram
RedHat 8.0
Kernel 2.4.21-pre4-ac3
alsa-cvs (intel-08x10 & vxpocket)
kernel pcmcia
linux-wlan (linksys wifi)

Reproducible crash when trying record on vxpocket. I believe other things
have been unstable and have caused crashes as well.

Here is some Oops from messages that I decoded.

TIA,
-asher

ksymoops 2.4.5 on i686 2.4.21-pre3-ac4.  Options used
     -V (default)
     -k /proc/ksyms (default)
     -l /proc/modules (default)
     -o /lib/modules/2.4.21-pre3-ac4/ (default)
     -m /boot/System.map-2.4.21-pre3-ac4 (default)

Warning: You did not tell me where to find symbol information.  I will
assume that the log matches the kernel and modules that are running
right now and I'll use the default options above for symbol resolution.
If the current kernel and/or modules do not match the log, you can get
more accurate output by telling me the kernel version and where to find

"timed out during reset" with calluna ATA HDD

Hi there,

I am using pcmcia cs with a 2.4.20 kernel on my embedded (mpc8xx) system.

It's working fine!

HDDs, ethernet, wavelan, flash cards... evrything is fine!

If only...

One particular model of calluna ATA HDD is making trouble! It's the 650MB, Type II.

Especialy after power on when the card was already inserted, I get

cs: socket c0f7e800 timed out during reset.  Try increasing setup_delay.

Usually "cardctl eject" followed by a reboot works.

Increasing setup_delay does _not_ help! I increased all timeout by factor 10 - 
still the same.

Any ideas?

Anyone seen the same?

What could I do?

Why is it working after a reboot?

Thanks a million!

Re: "timed out during reset" with calluna ATA HDD

On Tue, Jan 28, 2003 at 02:31:56PM +0100, Steven Scholz wrote:
> 
> One particular model of calluna ATA HDD is making trouble! It's the 650MB, 
> Type II.
> 
> Especialy after power on when the card was already inserted, I get
> 
> cs: socket c0f7e800 timed out during reset.  Try increasing setup_delay.
> 
> Usually "cardctl eject" followed by a reboot works.

How about just "cardctl eject" followed by "cardctl insert"?

> Increasing setup_delay does _not_ help! I increased all timeout by factor 10 
> - still the same.

Hmmm.  My next suggestion was going to be to increase some of the
other timing parameters, specifically vcc_settle, unreset_delay,
and/or unreset_limit.

> Why is it working after a reboot?

Maybe it just has a 30% chance of not working, so a reboot will
usually fix it by chance?

-- Dave

-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!

Re: "timed out during reset" with calluna ATA HDD

David Hinds schrieb:
> On Tue, Jan 28, 2003 at 02:31:56PM +0100, Steven Scholz wrote:
> 
>>One particular model of calluna ATA HDD is making trouble! It's the 650MB, 
>>Type II.
>>
>>Especialy after power on when the card was already inserted, I get
>>
>>cs: socket c0f7e800 timed out during reset.  Try increasing setup_delay.
>>
>>Usually "cardctl eject" followed by a reboot works.
> 
> 
> How about just "cardctl eject" followed by "cardctl insert"?
Nope. Does not work. (well maybe one in a million)

> 
>>Increasing setup_delay does _not_ help! I increased all timeout by factor 10 
>>- still the same.
> Hmmm.  My next suggestion was going to be to increase some of the
> other timing parameters, specifically vcc_settle, unreset_delay,
> and/or unreset_limit.
:o) Sorry!

>>Why is it working after a reboot?
> Maybe it just has a 30% chance of not working, so a reboot will
> usually fix it by chance?

But every other card works. Even an old calluna!

Re: "timed out during reset" with calluna ATA HDD

On Wed, Jan 29, 2003 at 09:54:25AM +0100, Steven Scholz wrote:
> 
> David Hinds schrieb:
> >On Tue, Jan 28, 2003 at 02:31:56PM +0100, Steven Scholz wrote:
> >
> >>One particular model of calluna ATA HDD is making trouble! It's the 650MB, 
> >>Especialy after power on when the card was already inserted, I get
> >>
> >>cs: socket c0f7e800 timed out during reset.  Try increasing setup_delay.
> >>
> >>Usually "cardctl eject" followed by a reboot works.
> >
> >How about just "cardctl eject" followed by "cardctl insert"?
>
> Nope. Does not work. (well maybe one in a million)

Well, that's completely bizarre, and I can't come up with a theory
that makes any sense at all.  I think you'll have to take it up with
someone who knows more about this platform, because it seems like some
sort of weird interaction between the bridge device and the socket
driver.

> I suppose that "cardctl eject" somehow "configures" the pcmcia hardware 
> (m8xx), and maybe the card itself. So that after a reboot everything is 
> fine.

How about if you shut down and restart the PCMCIA subsystem, rather
than reboot?

-- Dave

low level tools to access attribute memory

Are there any low-level tools that can give me information about the PCMCIA 
Attribute memory area?   So that I can check if the supposed contents of 
these areas are correct?

I so far assume that the CIS structures are saved there, right?

-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com