Towitoko Chipdrive USB init failed

Bug #569006 reported by asheenlevrai
30
This bug affects 6 people
Affects Status Importance Assigned to Milestone
towitoko (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Plugging the Towitoko CHIPDRIVE micro 130 v4.30A USB SmartCard reader results in:

04789060 hotplug_libhal.c:307:get_driver() Looking a driver for VID: 0x067B, PID: 0x2303
00000032 hotplug_libhal.c:342:HPAddDevice() Adding USB device: usb_device_67b_2303_noserial_if0
01001277 readerfactory.c:1024:RFInitializeReader() Attempting startup of Towitoko Chipdrive USB 00 00 using /usr/lib/pcsc/drivers/towitoko.bundle/Contents/Linux/libtowitoko.so.2.0.0
00000240 readerfactory.c:846:RFBindFunctions() Loading IFD Handler 2.0
01480284 readerfactory.c:1050:RFInitializeReader() Open Port 200000 Failed (usb:067b/2303:libhal:/org/freedesktop/Hal/devices/usb_device_67b_2303_noserial_if0)
00000034 readerfactory.c:914:RFUnloadReader() Unloading reader driver.
00000072 readerfactory.c:233:RFAddReader() Towitoko Chipdrive USB init failed.
00000016 hotplug_libhal.c:397:HPAddDevice() Failed adding USB device: usb_device_67b_2303_noserial_if0

The device was tested on Windows XP and works properly.

Another device (iMono Mobile Express CP611) works (using monosim 1.5.2) with my present configuration (Ubuntu 9.10).

pcsc-lite package version : "Version: 1.5.3-1ubuntu1"

ProblemType: Bug
Architecture: amd64
Date: Fri Apr 23 15:45:02 2010
DistroRelease: Ubuntu 9.10
Package: pcscd 1.5.3-1ubuntu1
ProcEnviron:
 LANG=fr_CH.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-20.58-generic
SourcePackage: pcsc-lite
Uname: Linux 2.6.31-20-generic x86_64
XsessionErrors:
 (gnome-settings-daemon:1851): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:1851): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (nautilus:1948): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (polkit-gnome-authentication-agent-1:1972): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (firefox:2093): GLib-WARNING **: g_set_prgname() called multiple times

Revision history for this message
asheenlevrai (asheenlevrai) wrote :
Revision history for this message
Ludovic Rousseau (ludovic-rousseau+ubuntu-one) wrote :

It is not a bug in pcsc-lite but in the libtowitoko.so.2.0.0 driver (package libtowitoko2)

affects: pcsc-lite (Ubuntu) → towitoko (Ubuntu)
Revision history for this message
asheenlevrai (asheenlevrai) wrote :

so... I'm f*“#d? I can trash my SC reader?
:-(
because there's no way a new version of the driver comes out...
Am I wrong?

thanx
-a-

Revision history for this message
Barry de Graaff (barrydegraaff) wrote :

Hello asheenlevrai,

I am afraid so, the original developer Carlos Prados Bocos left years ago and I am not getting a reply from the maintainer at debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603130
Since the device is old, I don't expect much activity and I am not willing to invest time in the driver. Since the Towitoko readers are to expensive.

If you need your reader fast, I suggest you buy a new one. Read tutorial here:
http://www.barrydegraaff.tk/index.php?page=files/Archive/Linux%20Sim%20Card%20reader/index.html#Still%20Looking

The chip card reader support in Linux fluctuates a lot. So after an update devices may loose functionality or stop working at all. Currently the Towitoko driver is broken.

Revision history for this message
Barry de Graaff (barrydegraaff) wrote :

You can probably get the Towitoko card reader working when you install an older version of pcsc-lite,

but then you will eventually (over time) end in dependancy problems

Changed in towitoko (Ubuntu):
status: New → Confirmed
Revision history for this message
asheenlevrai (asheenlevrai) wrote :

?? was does that mean? that it is confirmed that I'm screwed? ;-)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.