I still fight my kobil usb pro card reader (for hbci online bank connections), and have no more idea left.
While it could be a permission problem in usage of serial / usb devices, I may need some help. So if someone is curious in solving different problems, has the time left to read my posting, or is just kind enough to help another arch user in a question of totally minor interest for the community... - kobil's support told me I should use a more matured linux and kernel, not to mention suse ... :evil:
I don't won't to see suse can do things better than arch. Could this be true?
So, here is what I found out so far:
· Kernels between 2.4 and 2.6 must be patched to include a kernel module, while kernels prior to 2.4.18 will not work, and the code is already included in 2.6.
· You have to copy and install some drivers
· copy included libct.so to /usr/lib/
· The first time you try to use it, a .CT_devices is written in /home/username. The file should be changed to fit your needs.
· with tail -f /var/log/messages you should recieve a message like
Okt 16 12:07:18 localhost devlabel: devlabel service started/restarted Oct 16 12:07:21 localhost kernel: hub.c: new USB device 00:1f.2-2, assigned address 11 Oct 16 12:07:21 localhost kernel: usbserial.c: KOBIL USB smart card terminal converter detected Oct 16 12:07:21 localhost kernel: usbserial.c: KOBIL USB smart card terminal converter now attached to ttyUSB0 (or usb/tts/0 for devfs)
I never got that one, I get no message at all, plugging and unplugging the device :!:
· Using this :?: information, .CT_devices has to be edited:
GetPortType=#0 SetPortType=#0 DefaultPortType=#0 DefaultProtocollType=#0 UseOnlyDefaultProtocoll=#0 B1DTRLow=#50 B1DSRRespActive=#2000 PnPChar=#150 B1WaitForPnPString=#1500 KaanWaitForPnPString=#600 Port1=COM;/dev/ttyUSB0;1;0;serial reader at /dev/ttyUSB0: Kaan/SecOVID/TWIN
:arrow: All I ever fetched was a logfile entrie in the kernel log files:
... Feb 20 16:20:10 lemone kernel: Manufacturer: KOBIL Feb 20 16:20:10 lemone kernel: Product: USB Adapter K Feb 20 16:20:10 lemone kernel: usb.c: unhandled interfaces on device Feb 20 16:20:10 lemone kernel: usb.c: USB device 3 (vend/prod 0xd46/0x2012) is not claimed by any active driver. ... Feb 20 16:20:12 lemone kernel: usb.c: kusbd: /sbin/hotplug add 3 Feb 20 16:20:12 lemone kernel: usb.c: kusbd policy returned 0xfffffffe Feb 20 16:20:12 lemone kernel: hub.c: port 2, portstatus 100, change 0, 12 Mb/s Feb 20 16:20:12 lemone kernel: hub.c: port 3, portstatus 301, change 1, 1.5 Mb/s Feb 20 16:20:12 lemone kernel: hub.c: port 3 connection change Feb 20 16:20:12 lemone kernel: hub.c: port 3, portstatus 301, change 1, 1.5 Mb/s
[b] · May it be a permission problem? Any idea hot to add needed permissions on what device?
· May I need another kernel module? This is usb-serial stuff. Ther might be some dependencies.
· Why can't I fetch information from tail -f /var/log/messages/?[/b]
I would be glad for some advice, hint, idea - and don't know how I should ever show reciprocation.
Frumpus ♥ addict
What is the error message? How exactly do you try to access the device?
Does /dev/usb/tts/0 exist? If so, what are its permissions?
After you plug in the device is the module loaded correctly (lsmod)?
I have discovered that all of mans unhappiness derives from only one source, not being able to sit quietly in a room
- Blaise Pascal
a) the folder was not available.
b) the modul was not started (why did the kernel recognize the device then ...)
c) the rights are mixed up by my palm settings if not device 0 IS my palm, but "cat /dev/usb/tts/0" while trying to hotsync brings nothing:
ls -l /dev/usb/tts/
crw-rw---- 1 root palm 188, 0 1970-01-01 01:00 0
# Register palm device to /dev/pilot and grant access to palm group REGISTER ^usb/tts/1$ CFUNCTION GLOBAL mksymlink $devname pilot REGISTER ^usb/tts/.* PERMISSIONS root.palm 0660 REGISTER ^pilot$ PERMISSIONS root.palm 0660 UNREGISTER ^usb/tts/1$ CFUNCTION GLOBAL unlink pilot
Now, that I loaded the kobil_sct modul by hand, it seems my palm won't sync anymore. I guess the palm device entry in devfsd.conf mixes my usb devices up. I fear, my knowledge of base linux is to low to sort this out.
I should know which device is palm, which is kobil and - not hard enough? - which is my camera.
I tried to hotsync my palm and my camera, now I have /dev/ust/tts/0,1,2 and nothing works anymore. Seems you hit my problem, xentac.
Frumpus ♥ addict
Stupid devfs vs. personal asininity.
I fought several days now against the problem to need consistent names for my devices. Sometimes, /dev/usb/tts/0 is my camera, sometimes it is my palm, and sometimes it is my kobil card reader - depending what is connected to the machine while booting. Therefore, I think with devfs, I have no chance to fix this issue.
As long as no one blames me to be a blithering idiot (the idiot of the month? Could be worth a new poll) I am near to throw devfs towards the garbage can.
As far as I figured out, udev has the power to handle devices in a better way. Any comments from udev users if udev may help me fix my problems?
Frumpus ♥ addict