syncapi issues - was RE: PC/SC kernel panic with Omnikey 5321

> -----Original Message-----
> From: muscle-bounces@...
> [mailto:muscle-bounces@...] On Behalf Of
> Osborn, Justin D.
> Sent: Wednesday, May 09, 2007 1:23 PM
> To: Jason Grant; MUSCLE
> Subject: RE: [Muscle] PC/SC kernel panic with Omnikey 5321
>
> Jason,
>      Success!  I updated RH 9 to 2.4.34.4 (the latest stable
> 2.4 kernel), installed version of 2.3.0 of the Omnikey
> driver, and it worked.  Pcscd loaded the proper driver when
> the reader was inserted with no kernel panic.  When I ran
> testpcsc and placed the card on the reader, I got data back.
>
> Before I upgraded I tried the old kernel with v. 2.3.0 of the
> Omnikey driver and got a slightly less verbose kernel panic,
> enough to figure out that the panic was occurring in the
> uhci_hcd module.  So my guess is that the problem was a bug
> in the USB uhci module that the Omnikey driver happening to
> be invoking.
>
> Now I just have to write my application... :-)
>
> Many thanks!
> Justin
>
> --
> Justin D. Osborn
> Software Engineer
> Information Operations
> JHU/APL
>  
>
> > -----Original Message-----
> > From: Jason Grant [mailto:expires07@...]
> > Sent: Tuesday, May 08, 2007 7:21 PM
> > To: MUSCLE; Osborn, Justin D.
> > Subject: Re: [Muscle] PC/SC kernel panic with Omnikey 5321
> >
> > Hi Justin,
> >
> > I'm using the following configuration:
> >
> >  * pcsc-lite 1.40
> >  * ifdokrfid_lnx-2.3.0.tar.gz
> >  * kernel 2.4.21-47.ELsmp (RHEL3)
> >
> > and it has been working well for a couple of months.  Major issue
> > encountered was the previous version of the driver
> producing "card not
> > transacted" errors when 60-byte APDUs were requested via the "Read
> > Data"
> > command, but I worked with Omnikey support to resolve this, and the
> > current version of the driver (above) works well for me.  
> Minor issue
> > is that I have encountered pcscd failing to shutdown
> (intermittent),
> > and I suspect that it is related to the current version of
> the driver.  
> > Mailed the Omnikey guys about this, but have heard nothing.
> >
> > Jason.
> >
> > Osborn, Justin D. wrote:
> > > Hi all,
> > >        I'm trying to get the RFID interface of an Omnikey
> > 5321 reader
> > > working with pcscd.  For reasons outside of my control, I'm stuck
> > > using a 2.4 kernel (RH 9).  I downloaded pcsc-lite 1.4.0,
> > as well as
> > > the RFID driver available from Omnikey.  When I ran
> > pcsc-lite it gave
> > > me a message about hotplug support disabled with the
> > Omnikey driver,
> > > so I assume it loaded the driver properly.  However, as soon as I
> > > insert the reader, I get a kernel panic.  It all happens
> > too quickly
> > > to see any useful messages.
> > >
> > > Is this a possible configuration?  Do current versions of
> pcsc-lite
> > > support a 2.4 kernel or do I need an older version?
> > >
> > > I have an email in to Omnikey, but on the first round they
> > just told
> > > me to upgrade my kernel, which I can't.
> > >
> > > If this isn't possible, are there any suggestions for
> > alternatives?  
> > > My goal is to integrate this with a Java application, so I
> > eventually
> > > need to get a Java API in place.  One possibility may be
> > librfid which
> > > supports the Omnikey 5321, but I guess I'd probably have
> to write a
> > > JNI library.
> > >
> > > Please excuse my muscle/pcsc/smart card newbie-ness. :-)
> > >
> > > Thanks,
> > > Justin
> > >
> > > --
> > > Justin D. Osborn
> > > Software Engineer
> > > Information Operations
> > > JHU/APL
> > >
> > > _______________________________________________
> > > Muscle mailing list
> > > Muscle@...
> > > http://lists.drizzle.com/mailman/listinfo/muscle
> > >
> > >
> > >  
> >
> >
> > -----------------
> > Utiba Pty Ltd
> > This message has been scanned for viruses and dangerous content by
> > Utiba mail server and is believed to be clean.
> >
> >
>
> _______________________________________________
> Muscle mailing list
> Muscle@...
> http://lists.drizzle.com/mailman/listinfo/muscle
>