Here is a step by step workaround for André Barmasse and other swiss users - like me - who cannot use their Kobil M-Identity USB device on Ubuntu since Karmic. Please note : I have NOT tested this on Lucid. However it works on Karmic.
First, make sure your Kobil device is not plugged in.
Step 1 : Create a rule file suitable for the Kobil M-IDentity device
The Migros Bank suggest on their website to change the default udev rule.
Although this would probably work, I find it pretty risky as it will grant read/write priviledges to everyone for devices matching the default rule.
Instead I suggest to create a specific rule for the Kobil device and insert it in /etc/udev/user.rules as shown below
-> sudo gedit /etc/udev/user.rules
Then in the editor, copy and paste the following lines :
Step 3 - Check if the device is "seen" by Ubuntu
Plug the Kobil device and wait a few seconds.
If a window containing the Kobil files pops up after pluging the device, just close it.
In a terminal, type :
-> dmesg
You should see something like :
................................
[ 4919.751556] generic-usb 0003:0D46:4081.0009: hiddev96,hidraw2: USB HID v1.00 Device [KOBIL Systems mIDentity XL] on usb-0000:00:04.0-1/input1
[ 4924.742426] usb-storage: device scan complete
[ 4924.749361] scsi 15:0:0:0: CD-ROM KOBIL mIDentity 0001 PQ: 0 ANSI: 0
[ 4925.085346] sr1: scsi3-mmc drive: 11x/59x writer cd/rw caddy
[ 4925.085590] sr 15:0:0:0: Attached scsi CD-ROM sr1
[ 4925.085724] sr 15:0:0:0: Attached scsi generic sg2 type 5
[ 4925.751348] ISO 9660 Extensions: Microsoft Joliet Level 3
[ 4925.786328] ISO 9660 Extensions: RRIP_1991A
................................
Note the device name assigned by the system to the Kobil device. In this example : sr1
Step 4 - The Kobil device should have been mounted automatically. Check this and unmount it.
In a terminal type :
-> mount | grep '/dev/srX'
(where srX should be replaced by the device name found at step 2)
You should get something like :
/dev/srX on /media/M-IDentity type iso9660 (ro,nosuid,nodev,uhelper=devkit,uid=1000,gid=1000,iocharset=utf8,mode=0400,dmode=0500)
Unmount the device by typing :
-> sudo unmount /dev/srX
Finally mount the device on the mountpoint created at step 2 above :
-> mount /dev/srX /media/M-IDentity
You should now be able to open the shortcut "M-IDentity" and double-click on the executable "Start_M-IDentity_Linux" to run the M-Bancnet utility.
When you're finished, unmount the kobil device before removing it :
-> sudo umount /dev/srX
That's it !
In the future you only need to repeat steps 3 and 4.
Bear in mind that this is ONLY a workaround, and by the way, not a very clean one. This issue should really be handled some day. Anyway, I hope this could help.
Hello
Here is a step by step workaround for André Barmasse and other swiss users - like me - who cannot use their Kobil M-Identity USB device on Ubuntu since Karmic. Please note : I have NOT tested this on Lucid. However it works on Karmic.
First, make sure your Kobil device is not plugged in.
Step 1 : Create a rule file suitable for the Kobil M-IDentity device
The Migros Bank suggest on their website to change the default udev rule. user.rules as shown below
Although this would probably work, I find it pretty risky as it will grant read/write priviledges to everyone for devices matching the default rule.
Instead I suggest to create a specific rule for the Kobil device and insert it in /etc/udev/
-> sudo gedit /etc/udev/ user.rules
Then in the editor, copy and paste the following lines :
####### ####### ####### ####### ####### ####### ####### ###### ="usb_device" , GOTO="user_ rules_end"
BUS!="usb", ACTION!="add", SUBSYSTEM!
# Kobil mIDentity XL USB =="0d46" , SYSFS{idProduct }=="4081" , MODE="666", GROUP="plugdev"
SYSFS{idVendor}
LABEL=" user_rules_ end" ####### ####### ####### ####### ####### ####### ######
#######
Save the file and close gedit
Restart udev (-> sudo service udev restart) or simply reboot your computer.
------- ------- ------- ------- ------- ------- ------- ------- ------- ------
Step 2 - Create a valid persistent mount point for the Kobil device
In a terminal, type :
-> sudo mkdir /media/M-IDentity
------- ------- ------- ------- ------- ------- ------- ------- ------- -------
Step 3 - Check if the device is "seen" by Ubuntu
Plug the Kobil device and wait a few seconds.
If a window containing the Kobil files pops up after pluging the device, just close it.
In a terminal, type :
-> dmesg
You should see something like :
....... ....... ....... ....... .... 4081.0009: hiddev96,hidraw2: USB HID v1.00 Device [KOBIL Systems mIDentity XL] on usb-0000: 00:04.0- 1/input1 ....... ....... ....... ....
[ 4919.751556] generic-usb 0003:0D46:
[ 4924.742426] usb-storage: device scan complete
[ 4924.749361] scsi 15:0:0:0: CD-ROM KOBIL mIDentity 0001 PQ: 0 ANSI: 0
[ 4925.085346] sr1: scsi3-mmc drive: 11x/59x writer cd/rw caddy
[ 4925.085590] sr 15:0:0:0: Attached scsi CD-ROM sr1
[ 4925.085724] sr 15:0:0:0: Attached scsi generic sg2 type 5
[ 4925.751348] ISO 9660 Extensions: Microsoft Joliet Level 3
[ 4925.786328] ISO 9660 Extensions: RRIP_1991A
.......
Note the device name assigned by the system to the Kobil device. In this example : sr1
------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ----
Step 4 - The Kobil device should have been mounted automatically. Check this and unmount it.
In a terminal type :
-> mount | grep '/dev/srX'
(where srX should be replaced by the device name found at step 2)
You should get something like : nodev,uhelper= devkit, uid=1000, gid=1000, iocharset= utf8,mode= 0400,dmode= 0500)
/dev/srX on /media/M-IDentity type iso9660 (ro,nosuid,
Unmount the device by typing :
-> sudo unmount /dev/srX
Finally mount the device on the mountpoint created at step 2 above :
-> mount /dev/srX /media/M-IDentity
You should now be able to open the shortcut "M-IDentity" and double-click on the executable "Start_ M-IDentity_ Linux" to run the M-Bancnet utility.
When you're finished, unmount the kobil device before removing it :
-> sudo umount /dev/srX
That's it !
In the future you only need to repeat steps 3 and 4.
Bear in mind that this is ONLY a workaround, and by the way, not a very clean one. This issue should really be handled some day. Anyway, I hope this could help.
Cheers