Searching \ for '[OT] udev rules for openSuse 10.2 for PICkit 2 and' in subject line. ()
Make payments with PayPal - it's fast, free and secure! Help us get a faster server
FAQ page: www.piclist.com/techref/microchip/devices.htm?key=pic
Search entire site for: 'udev rules for openSuse 10.2 for PICkit 2 and'.

Exact match. Not showing close matches.
PICList Thread
'[OT] udev rules for openSuse 10.2 for PICkit 2 and'
2007\02\03@103717 by Xiaofan Chen

face picon face
Just wondering if there are some openSuse user here in the list.

I have some problems to get udev rules working under openSuse 10.2.

I am now using the same udev rules like Ubuntu 6.06/6.10 detailed in
piklab.sourceforge.net/wiki/index.php/Port_connection_problems.
The udev/PAM combination does not work under openSuse 10.2 so that
I am using the same udev rules as Ubuntu 6.06/6.10.

mcuee@localhost:/etc/udev/rules.d> groups mcuee
users dialout video microchip
mcuee@localhost:/etc/udev/rules.d> cat /etc/udev/rules.d/026_microchip.rules
#PICKit
SYSFS{idVendor}=="04d8", SYSFS{idProduct}=="0032", MODE="0660",
GROUP="microchip"
#PICKit2
SYSFS{idVendor}=="04d8", SYSFS{idProduct}=="0033", MODE="0660",
GROUP="microchip"
#ICD2
SYSFS{idVendor}=="04d8", SYSFS{idProduct}=="8000", MODE="0660",
GROUP="microchip"
#ICD21
SYSFS{idVendor}=="04d8", SYSFS{idProduct}=="8001", MODE="0660",
GROUP="microchip"

However, the result is not as expected.
mcuee@localhost:/etc/udev/rules.d> lsusb
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 031: ID 04d8:8000 Microchip Technology, Inc. In-Circuit Debugger
Bus 002 Device 030: ID 04d8:0033 Microchip Technology, Inc.
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
mcuee@localhost:/etc/udev/rules.d> ls -la /dev/bus/usb/002
total 0
drwxr-xr-x 2 root root           100 2007-02-01 20:46 .
drwxr-xr-x 5 root root           100 2007-02-02 03:43 ..
crw-r--r-- 1 root root      189, 128 2007-02-02 03:43 001
crw-r--r-- 1 root microchip 189, 157 2007-02-01 20:45 030
crw-r--r-- 1 root microchip 189, 158 2007-02-01 20:46 031

Instead of 660, the permission is 644 so a normal user can not run
pk2/pyk with PICkit 2.

2007\02\03@205846 by Tachyon

picon face
I use SuSE.

First, you should try and make these modifications through YaST and not
manually. Unless you disable SuSEconfig (and therefore YaST) most of the
modifications you make manually will be overwritten. You can still make
manual modifications, but if you look, most config files will have
comments listing what external file you should edit to add manual scripts.
Anyway, in YaST check the system options. If you wish to use PAM, make
sure it is enabled and configured.
Next, use the SDB (if you have it installed, otherwise use the newer one
on the website) and search on udev configuration.
I don't believe doing it the 'Ubuntu way' will work.

Anyway, that said, I believe 10.2 uses hotplug, but I'm not positive as
I'm still using 9.3Pro and 10.1 Open.
Check http://en.opensuse.org/SDB:SUSE_Linux_Hotplug_System_Overview

Hope this helps, if not let me know and I'll dig more into my 'grey
archives'.

Xiaofan Chen wrote:
{Quote hidden}

2007\02\04@002544 by Xiaofan Chen

face picon face
On 2/4/07, Tachyon <spam_OUTtherealtachyonTakeThisOuTspamgmail.com> wrote:
> I use SuSE.

Thanks. This is the first time I am trying out openSuse.

I can not find anything about udev in YaST. I will try harder.

>
> Anyway, that said, I believe 10.2 uses hotplug, but I'm not positive as
> I'm still using 9.3Pro and 10.1 Open.
> Check http://en.opensuse.org/SDB:SUSE_Linux_Hotplug_System_Overview
>

I can not find /etc/hotplug or /etc/sysconfig/hotplug in the system so I
think they are using udev.

Regards,
Xiaofan

2007\02\04@033144 by Xiaofan Chen

face picon face
On 2/4/07, Xiaofan Chen <.....xiaofancKILLspamspam@spam@gmail.com> wrote:
> I can not find /etc/hotplug or /etc/sysconfig/hotplug in the system so I
> think they are using udev.
>

After a bit of tweaking, I find out the solution. This time Google does not
help though...

The default rules 50-udev-default rules is setting 0644 for the libusb
device. Therefore I have to rename the original
026-microchip.rules to 76-microchip.rules to get 0660 permission.

mcuee@localhost:/etc/udev/rules.d> tail 50-udev-default.rules
...
# libusb device access
SUBSYSTEM=="usb_device", ACTION=="add", PROGRAM="/bin/sh -c 'K=%k;
K=$${K#usbdev}; printf bus/usb/%%03i/%%03i $${K%%%%.*} $${K#*.}'",
NAME="%c", MODE="0644"
...

mcuee@localhost:/etc/udev/rules.d> cat 76_microchip.rules
#PICKit
SYSFS{idVendor}=="04d8", SYSFS{idProduct}=="0032", MODE="0660",
GROUP="microchip"
#PICKit2
SYSFS{idVendor}=="04d8", SYSFS{idProduct}=="0033", MODE="0660",
GROUP="microchip"
#ICD2
SYSFS{idVendor}=="04d8", SYSFS{idProduct}=="8000", MODE="0660",
GROUP="microchip"
#ICD21
SYSFS{idVendor}=="04d8", SYSFS{idProduct}=="8001", MODE="0660",
GROUP="microchip"

mcuee@localhost:/etc/udev/rules.d> ls -la /dev/bus/usb/002
total 0
drwxr-xr-x 2 root root           100 2007-02-04 16:19 .
drwxr-xr-x 5 root root           100 2007-02-04 23:10 ..
crw-r--r-- 1 root root      189, 128 2007-02-04 23:10 001
crw-rw---- 1 root microchip 189, 131 2007-02-04 16:18 004
crw-rw---- 1 root microchip 189, 132 2007-02-04 16:20 005

By the way, it seems to me that there are no YaST modules which
are taking care of this. And there is not pam-console modules so that
the Fedora Core 5/6 way is not working.

Regards,
Xiaofan

More... (looser matching)
- Last day of these posts
- In 2007 , 2008 only
- Today
- New search...