Re: usb-scanner-cameras kernel-2.6.22 and udev-095 problem
On Wed, Jun 06, 2007 at 10:11:20PM -0500, [EMAIL PROTECTED] wrote: > greg > with CONFIG_USB_DEVICE_CLASS=y > scanner /dev/scanner- show up xsane is working now > > SCANNER PROBLEM SOLVED Great, thanks for verifying this. This config option is by default enabled, so you need to work hard to disable it :) thanks, greg k-h - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: usb-scanner-cameras kernel-2.6.22 and udev-095 problem
greg with CONFIG_USB_DEVICE_CLASS=y scanner /dev/scanner- show up xsane is working now SCANNER PROBLEM SOLVED thanx xboom - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: usb-scanner-cameras kernel-2.6.22 and udev-095 problem
greg this is part of my config (we are talking now 2.6.22-rc4-200706042030-cfq7 #160 SMP PREEMPT Mon Jun 4 20:55:02 CDT 2007 x86_64 x86_64 x86_64 GNU/Linux) CONFIG_USB_DEVICEFS=y # CONFIG_USB_DEVICE_CLASS is not set - # CONFIG_USB_DYNAMIC_MINORS is not set CONFIG_USB_SUSPEND=y # CONFIG_USB_OTG is not set i disabled libusual in my config # CONFIG_USB_LIBUSUAL is not set with libusual=y my usb-harddrives doesn't show up on desktop after boot until i cycle one off/on and from this moment all of them start showing up with libusual not set -usb-harddrives shows up but this doesn't affect scanners btw scanners are working with standard fc7 86-x64 kernel xboom - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: usb-scanner-cameras kernel-2.6.22 and udev-095 problem
greg this is part of my config (we are talking now 2.6.22-rc4-200706042030-cfq7 #160 SMP PREEMPT Mon Jun 4 20:55:02 CDT 2007 x86_64 x86_64 x86_64 GNU/Linux) CONFIG_USB_DEVICEFS=y # CONFIG_USB_DEVICE_CLASS is not set - # CONFIG_USB_DYNAMIC_MINORS is not set CONFIG_USB_SUSPEND=y # CONFIG_USB_OTG is not set i disabled libusual in my config # CONFIG_USB_LIBUSUAL is not set with libusual=y my usb-harddrives doesn't show up on desktop after boot until i cycle one off/on and from this moment all of them start showing up with libusual not set -usb-harddrives shows up but this doesn't affect scanners btw scanners are working with standard fc7 86-x64 kernel xboom - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: usb-scanner-cameras kernel-2.6.22 and udev-095 problem
greg with CONFIG_USB_DEVICE_CLASS=y scanner /dev/scanner- show up xsane is working now SCANNER PROBLEM SOLVED thanx xboom - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: usb-scanner-cameras kernel-2.6.22 and udev-095 problem
On Wed, Jun 06, 2007 at 10:11:20PM -0500, [EMAIL PROTECTED] wrote: greg with CONFIG_USB_DEVICE_CLASS=y scanner /dev/scanner- show up xsane is working now SCANNER PROBLEM SOLVED Great, thanks for verifying this. This config option is by default enabled, so you need to work hard to disable it :) thanks, greg k-h - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: usb-scanner-cameras kernel-2.6.22 and udev-095 problem
On Tue, Jun 05, 2007 at 07:20:14PM -0500, [EMAIL PROTECTED] wrote: > sorry for not responding i was busy (i updated my sys to fc7) > on fc7-i386 and on fc-x86-64(2.6.22-rc4-cfq7 SMP PREEMPT x86_64 GNU/Linux) i > can't see usb scanner > i test this with hp-6300 and aqfa snapscan-1212u > non of them triger creation /dev/scanner-x device > xsane cannot see this scanner without this i assume. Is CONFIG_USB_DEVICE_CLASS enabled in this kernel? Are _any_ files showing up in /dev/bus/usb/? thanks, greg k-h - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: usb-scanner-cameras kernel-2.6.22 and udev-095 problem
sorry for not responding i was busy (i updated my sys to fc7) on fc7-i386 and on fc-x86-64(2.6.22-rc4-cfq7 SMP PREEMPT x86_64 GNU/Linux) i can't see usb scanner i test this with hp-6300 and aqfa snapscan-1212u non of them triger creation /dev/scanner-x device xsane cannot see this scanner without this i assume. (btw for fc7 guys scons is not signed and test-mpeg2 is not working with raw1394) xboom - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: usb-scanner-cameras kernel-2.6.22 and udev-095 problem
On Tue, Jun 05, 2007 at 02:18:26PM +0200, Michal Piotrowski wrote:
> Hi,
>
> On 24/05/07, Greg KH <[EMAIL PROTECTED]> wrote:
> > On Thu, May 17, 2007 at 07:00:58PM -0500, [EMAIL PROTECTED] wrote:
> > > greg
> > >
> > > and part of /etc/udev/rules.d/60-libsane.rules
> > >
> > > ...
> > > ACTION!="add", GOTO="libsane_rules_end"
> > > SUBSYSTEM!="usb_device", GOTO="libsane_rules_end"
> > >
> > > # Hewlett-Packard ScanJet 4100C
> > > SYSFS{idVendor}=="03f0", SYSFS{idProduct}=="0101", SYMLINK+="scanner-%k"
> > > # Hewlett-Packard Photosmart S20 (C5101A) | Hewlett-Packard Photosmart
> > S20xi
> > > (C7150A)
> > > SYSFS{idVendor}=="03f0", SYSFS{idProduct}=="0102", SYMLINK+="scanner-%k"
> > > # Hewlett-Packard ScanJet 4200C | Hewlett-Packard ScanJet 4200Cxi |
> > > Hewlett-Packard ScanJet 4200Cse
> > > SYSFS{idVendor}=="03f0", SYSFS{idProduct}=="0105", SYMLINK+="scanner-%k"
> > > # Hewlett-Packard ScanJet 6200C | Hewlett-Packard ScanJet 6250C
> > > SYSFS{idVendor}=="03f0", SYSFS{idProduct}=="0201", SYMLINK+="scanner-%k"
> > > # Hewlett-Packard ScanJet 3300c
> > > SYSFS{idVendor}=="03f0", SYSFS{idProduct}=="0205", SYMLINK+="scanner-%k"
> > > # Hewlett-Packard ScanJet 4300c
> > > SYSFS{idVendor}=="03f0", SYSFS{idProduct}=="0305", SYMLINK+="scanner-%k"
> > > # Hewlett-Packard ScanJet 5200C
> > > SYSFS{idVendor}=="03f0", SYSFS{idProduct}=="0401", SYMLINK+="scanner-%k"
> > > # Hewlett-Packard ScanJet 3400c
> > > SYSFS{idVendor}=="03f0", SYSFS{idProduct}=="0405", SYMLINK+="scanner-%k"
> > > # Hewlett-Packard ScanJet 2100C
> > > SYSFS{idVendor}=="03f0", SYSFS{idProduct}=="0505", SYMLINK+="scanner-%k"
> > > # Hewlett-Packard ScanJet 6300C | Hewlett-Packard ScanJet 6350C |
> > > Hewlett-Packard ScanJet 6390C
> > > SYSFS{idVendor}=="03f0", SYSFS{idProduct}=="0601", SYMLINK+="scanner-%k"
> > > # Hewlett-Packard ScanJet 2200C
> > > SYSFS{idVendor}=="03f0", SYSFS{idProduct}=="0605", SYMLINK+="scanner-%k"
> > >
> > > ...
> > > # Dell 1600n
> > > SYSFS{idVendor}=="413c", SYSFS{idProduct}=="5250", SYMLINK+="scanner-%k"
> > >
> > > LABEL="libsane_rules_end"
> >
> >
> > I don't see anything odd there at all.
> >
> > Can you run 'git bisect' to try to narrow down to the patch that caused
> > the problem?
>
> Any progress with this bug?
I haven't heard back from Art, and nothing looks wrong in the rules file
above...
thanks,
greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: usb-scanner-cameras kernel-2.6.22 and udev-095 problem
On Tue, Jun 05, 2007 at 02:18:26PM +0200, Michal Piotrowski wrote:
Hi,
On 24/05/07, Greg KH [EMAIL PROTECTED] wrote:
On Thu, May 17, 2007 at 07:00:58PM -0500, [EMAIL PROTECTED] wrote:
greg
and part of /etc/udev/rules.d/60-libsane.rules
...
ACTION!=add, GOTO=libsane_rules_end
SUBSYSTEM!=usb_device, GOTO=libsane_rules_end
# Hewlett-Packard ScanJet 4100C
SYSFS{idVendor}==03f0, SYSFS{idProduct}==0101, SYMLINK+=scanner-%k
# Hewlett-Packard Photosmart S20 (C5101A) | Hewlett-Packard Photosmart
S20xi
(C7150A)
SYSFS{idVendor}==03f0, SYSFS{idProduct}==0102, SYMLINK+=scanner-%k
# Hewlett-Packard ScanJet 4200C | Hewlett-Packard ScanJet 4200Cxi |
Hewlett-Packard ScanJet 4200Cse
SYSFS{idVendor}==03f0, SYSFS{idProduct}==0105, SYMLINK+=scanner-%k
# Hewlett-Packard ScanJet 6200C | Hewlett-Packard ScanJet 6250C
SYSFS{idVendor}==03f0, SYSFS{idProduct}==0201, SYMLINK+=scanner-%k
# Hewlett-Packard ScanJet 3300c
SYSFS{idVendor}==03f0, SYSFS{idProduct}==0205, SYMLINK+=scanner-%k
# Hewlett-Packard ScanJet 4300c
SYSFS{idVendor}==03f0, SYSFS{idProduct}==0305, SYMLINK+=scanner-%k
# Hewlett-Packard ScanJet 5200C
SYSFS{idVendor}==03f0, SYSFS{idProduct}==0401, SYMLINK+=scanner-%k
# Hewlett-Packard ScanJet 3400c
SYSFS{idVendor}==03f0, SYSFS{idProduct}==0405, SYMLINK+=scanner-%k
# Hewlett-Packard ScanJet 2100C
SYSFS{idVendor}==03f0, SYSFS{idProduct}==0505, SYMLINK+=scanner-%k
# Hewlett-Packard ScanJet 6300C | Hewlett-Packard ScanJet 6350C |
Hewlett-Packard ScanJet 6390C
SYSFS{idVendor}==03f0, SYSFS{idProduct}==0601, SYMLINK+=scanner-%k
# Hewlett-Packard ScanJet 2200C
SYSFS{idVendor}==03f0, SYSFS{idProduct}==0605, SYMLINK+=scanner-%k
...
# Dell 1600n
SYSFS{idVendor}==413c, SYSFS{idProduct}==5250, SYMLINK+=scanner-%k
LABEL=libsane_rules_end
I don't see anything odd there at all.
Can you run 'git bisect' to try to narrow down to the patch that caused
the problem?
Any progress with this bug?
I haven't heard back from Art, and nothing looks wrong in the rules file
above...
thanks,
greg k-h
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: usb-scanner-cameras kernel-2.6.22 and udev-095 problem
sorry for not responding i was busy (i updated my sys to fc7) on fc7-i386 and on fc-x86-64(2.6.22-rc4-cfq7 SMP PREEMPT x86_64 GNU/Linux) i can't see usb scanner i test this with hp-6300 and aqfa snapscan-1212u non of them triger creation /dev/scanner-x device xsane cannot see this scanner without this i assume. (btw for fc7 guys scons is not signed and test-mpeg2 is not working with raw1394) xboom - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: usb-scanner-cameras kernel-2.6.22 and udev-095 problem
On Tue, Jun 05, 2007 at 07:20:14PM -0500, [EMAIL PROTECTED] wrote: sorry for not responding i was busy (i updated my sys to fc7) on fc7-i386 and on fc-x86-64(2.6.22-rc4-cfq7 SMP PREEMPT x86_64 GNU/Linux) i can't see usb scanner i test this with hp-6300 and aqfa snapscan-1212u non of them triger creation /dev/scanner-x device xsane cannot see this scanner without this i assume. Is CONFIG_USB_DEVICE_CLASS enabled in this kernel? Are _any_ files showing up in /dev/bus/usb/? thanks, greg k-h - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: usb-scanner-cameras kernel-2.6.22 and udev-095 problem
On Thu, May 17, 2007 at 07:00:58PM -0500, [EMAIL PROTECTED] wrote:
> greg
>
> and part of /etc/udev/rules.d/60-libsane.rules
>
> ...
> ACTION!="add", GOTO="libsane_rules_end"
> SUBSYSTEM!="usb_device", GOTO="libsane_rules_end"
>
> # Hewlett-Packard ScanJet 4100C
> SYSFS{idVendor}=="03f0", SYSFS{idProduct}=="0101", SYMLINK+="scanner-%k"
> # Hewlett-Packard Photosmart S20 (C5101A) | Hewlett-Packard Photosmart S20xi
> (C7150A)
> SYSFS{idVendor}=="03f0", SYSFS{idProduct}=="0102", SYMLINK+="scanner-%k"
> # Hewlett-Packard ScanJet 4200C | Hewlett-Packard ScanJet 4200Cxi |
> Hewlett-Packard ScanJet 4200Cse
> SYSFS{idVendor}=="03f0", SYSFS{idProduct}=="0105", SYMLINK+="scanner-%k"
> # Hewlett-Packard ScanJet 6200C | Hewlett-Packard ScanJet 6250C
> SYSFS{idVendor}=="03f0", SYSFS{idProduct}=="0201", SYMLINK+="scanner-%k"
> # Hewlett-Packard ScanJet 3300c
> SYSFS{idVendor}=="03f0", SYSFS{idProduct}=="0205", SYMLINK+="scanner-%k"
> # Hewlett-Packard ScanJet 4300c
> SYSFS{idVendor}=="03f0", SYSFS{idProduct}=="0305", SYMLINK+="scanner-%k"
> # Hewlett-Packard ScanJet 5200C
> SYSFS{idVendor}=="03f0", SYSFS{idProduct}=="0401", SYMLINK+="scanner-%k"
> # Hewlett-Packard ScanJet 3400c
> SYSFS{idVendor}=="03f0", SYSFS{idProduct}=="0405", SYMLINK+="scanner-%k"
> # Hewlett-Packard ScanJet 2100C
> SYSFS{idVendor}=="03f0", SYSFS{idProduct}=="0505", SYMLINK+="scanner-%k"
> # Hewlett-Packard ScanJet 6300C | Hewlett-Packard ScanJet 6350C |
> Hewlett-Packard ScanJet 6390C
> SYSFS{idVendor}=="03f0", SYSFS{idProduct}=="0601", SYMLINK+="scanner-%k"
> # Hewlett-Packard ScanJet 2200C
> SYSFS{idVendor}=="03f0", SYSFS{idProduct}=="0605", SYMLINK+="scanner-%k"
>
> ...
> # Dell 1600n
> SYSFS{idVendor}=="413c", SYSFS{idProduct}=="5250", SYMLINK+="scanner-%k"
>
> LABEL="libsane_rules_end"
I don't see anything odd there at all.
Can you run 'git bisect' to try to narrow down to the patch that caused
the problem?
thanks,
greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: usb-scanner-cameras kernel-2.6.22 and udev-095 problem
On Thu, May 17, 2007 at 07:00:58PM -0500, [EMAIL PROTECTED] wrote:
greg
and part of /etc/udev/rules.d/60-libsane.rules
...
ACTION!=add, GOTO=libsane_rules_end
SUBSYSTEM!=usb_device, GOTO=libsane_rules_end
# Hewlett-Packard ScanJet 4100C
SYSFS{idVendor}==03f0, SYSFS{idProduct}==0101, SYMLINK+=scanner-%k
# Hewlett-Packard Photosmart S20 (C5101A) | Hewlett-Packard Photosmart S20xi
(C7150A)
SYSFS{idVendor}==03f0, SYSFS{idProduct}==0102, SYMLINK+=scanner-%k
# Hewlett-Packard ScanJet 4200C | Hewlett-Packard ScanJet 4200Cxi |
Hewlett-Packard ScanJet 4200Cse
SYSFS{idVendor}==03f0, SYSFS{idProduct}==0105, SYMLINK+=scanner-%k
# Hewlett-Packard ScanJet 6200C | Hewlett-Packard ScanJet 6250C
SYSFS{idVendor}==03f0, SYSFS{idProduct}==0201, SYMLINK+=scanner-%k
# Hewlett-Packard ScanJet 3300c
SYSFS{idVendor}==03f0, SYSFS{idProduct}==0205, SYMLINK+=scanner-%k
# Hewlett-Packard ScanJet 4300c
SYSFS{idVendor}==03f0, SYSFS{idProduct}==0305, SYMLINK+=scanner-%k
# Hewlett-Packard ScanJet 5200C
SYSFS{idVendor}==03f0, SYSFS{idProduct}==0401, SYMLINK+=scanner-%k
# Hewlett-Packard ScanJet 3400c
SYSFS{idVendor}==03f0, SYSFS{idProduct}==0405, SYMLINK+=scanner-%k
# Hewlett-Packard ScanJet 2100C
SYSFS{idVendor}==03f0, SYSFS{idProduct}==0505, SYMLINK+=scanner-%k
# Hewlett-Packard ScanJet 6300C | Hewlett-Packard ScanJet 6350C |
Hewlett-Packard ScanJet 6390C
SYSFS{idVendor}==03f0, SYSFS{idProduct}==0601, SYMLINK+=scanner-%k
# Hewlett-Packard ScanJet 2200C
SYSFS{idVendor}==03f0, SYSFS{idProduct}==0605, SYMLINK+=scanner-%k
...
# Dell 1600n
SYSFS{idVendor}==413c, SYSFS{idProduct}==5250, SYMLINK+=scanner-%k
LABEL=libsane_rules_end
I don't see anything odd there at all.
Can you run 'git bisect' to try to narrow down to the patch that caused
the problem?
thanks,
greg k-h
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: usb-scanner-cameras kernel-2.6.22 and udev-095 problem
greg
and part of /etc/udev/rules.d/60-libsane.rules
...
ACTION!="add", GOTO="libsane_rules_end"
SUBSYSTEM!="usb_device", GOTO="libsane_rules_end"
# Hewlett-Packard ScanJet 4100C
SYSFS{idVendor}=="03f0", SYSFS{idProduct}=="0101", SYMLINK+="scanner-%k"
# Hewlett-Packard Photosmart S20 (C5101A) | Hewlett-Packard Photosmart
S20xi (C7150A)
SYSFS{idVendor}=="03f0", SYSFS{idProduct}=="0102", SYMLINK+="scanner-%k"
# Hewlett-Packard ScanJet 4200C | Hewlett-Packard ScanJet 4200Cxi |
Hewlett-Packard ScanJet 4200Cse
SYSFS{idVendor}=="03f0", SYSFS{idProduct}=="0105", SYMLINK+="scanner-%k"
# Hewlett-Packard ScanJet 6200C | Hewlett-Packard ScanJet 6250C
SYSFS{idVendor}=="03f0", SYSFS{idProduct}=="0201", SYMLINK+="scanner-%k"
# Hewlett-Packard ScanJet 3300c
SYSFS{idVendor}=="03f0", SYSFS{idProduct}=="0205", SYMLINK+="scanner-%k"
# Hewlett-Packard ScanJet 4300c
SYSFS{idVendor}=="03f0", SYSFS{idProduct}=="0305", SYMLINK+="scanner-%k"
# Hewlett-Packard ScanJet 5200C
SYSFS{idVendor}=="03f0", SYSFS{idProduct}=="0401", SYMLINK+="scanner-%k"
# Hewlett-Packard ScanJet 3400c
SYSFS{idVendor}=="03f0", SYSFS{idProduct}=="0405", SYMLINK+="scanner-%k"
# Hewlett-Packard ScanJet 2100C
SYSFS{idVendor}=="03f0", SYSFS{idProduct}=="0505", SYMLINK+="scanner-%k"
# Hewlett-Packard ScanJet 6300C | Hewlett-Packard ScanJet 6350C |
Hewlett-Packard ScanJet 6390C
SYSFS{idVendor}=="03f0", SYSFS{idProduct}=="0601", SYMLINK+="scanner-%k"
# Hewlett-Packard ScanJet 2200C
SYSFS{idVendor}=="03f0", SYSFS{idProduct}=="0605", SYMLINK+="scanner-%k"
...
# Dell 1600n
SYSFS{idVendor}=="413c", SYSFS{idProduct}=="5250", SYMLINK+="scanner-%k"
LABEL="libsane_rules_end"
xboom
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: usb-scanner-cameras kernel-2.6.22 and udev-095 problem
On Thu, May 17, 2007 at 12:05:44PM -0500, [EMAIL PROTECTED] wrote:
> greg
>
> >> You didn't answer my, "what distro are you using" question. Also, what
> package created the udev rule that creates the above symlink?
>
> distro fc6
> Linux xxx.xxx 2.6.22-rc1-200705170855cfq6-g0479ea0e #134 SMP PREEMPT Thu May
> 17 09:13:26 CDT 2007 x86_64 x86_64 x86_64 GNU/Linux
You answered the first question above, not the second :(
> 2.6.20
>
> $ udevtest /class/usb_device/usbdev2.10
> main: looking at device '/class/usb_device/usbdev2.10' from subsystem
> 'usb_device'
> run_program: '/bin/sh -c 'K=usbdev2.10; K=${K#usbdev}; printf
> bus/usb/%03i/%03i ${K%%.*} ${K#*.}''
> run_program: '/bin/sh' (stdout) 'bus/usb/002/010'
> run_program: '/bin/sh' returned with status 0
> udev_rules_get_name: rule applied, 'usbdev2.10' becomes 'bus/usb/002/010'
> udev_rules_get_name: add symlink 'scanner-usbdev2.10'
> udev_device_event: device '/class/usb_device/usbdev2.10' already in
> database, validate currently present symlinks
> udev_node_add: creating device node '/dev/bus/usb/002/010', major = '189',
> minor = '137', mode = '0644', uid = '0', gid = '0'
> udev_node_add: creating symlink '/dev/scanner-usbdev2.10' to
> 'bus/usb/002/010'
> main: run: 'socket:/org/kernel/udev/monitor'
> main: run: '/lib/udev/udev_run_devd'
> main: run: 'socket:/org/freedesktop/hal/udev_event'
> main: run: '/sbin/pam_console_apply /dev/bus/usb/002/010
> /dev/scanner-usbdev2.10'
And if you run that 'udevtest' command on 2.6.21 what happens?
Again, you have not shown me the udev rule that adds that symlink, is it
something you added by hand, or something that Fedora added to the rules
file?
thanks,
greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: usb-scanner-cameras kernel-2.6.22 and udev-095 problem
greg
You didn't answer my, "what distro are you using" question. Also, what
package created the udev rule that creates the above symlink?
distro fc6
Linux xxx.xxx 2.6.22-rc1-200705170855cfq6-g0479ea0e #134 SMP PREEMPT
Thu May 17 09:13:26 CDT 2007 x86_64 x86_64 x86_64 GNU/Linux
2.6.20
$ udevtest /class/usb_device/usbdev2.10
main: looking at device '/class/usb_device/usbdev2.10' from subsystem
'usb_device'
run_program: '/bin/sh -c 'K=usbdev2.10; K=${K#usbdev}; printf
bus/usb/%03i/%03i ${K%%.*} ${K#*.}''
run_program: '/bin/sh' (stdout) 'bus/usb/002/010'
run_program: '/bin/sh' returned with status 0
udev_rules_get_name: rule applied, 'usbdev2.10' becomes 'bus/usb/002/010'
udev_rules_get_name: add symlink 'scanner-usbdev2.10'
udev_device_event: device '/class/usb_device/usbdev2.10' already in
database, validate currently present symlinks
udev_node_add: creating device node '/dev/bus/usb/002/010', major =
'189', minor = '137', mode = '0644', uid = '0', gid = '0'
udev_node_add: creating symlink '/dev/scanner-usbdev2.10' to 'bus/usb/002/010'
main: run: 'socket:/org/kernel/udev/monitor'
main: run: '/lib/udev/udev_run_devd'
main: run: 'socket:/org/freedesktop/hal/udev_event'
main: run: '/sbin/pam_console_apply /dev/bus/usb/002/010
/dev/scanner-usbdev2.10'
xboom
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: usb-scanner-cameras kernel-2.6.22 and udev-095 problem
greg
You didn't answer my, what distro are you using question. Also, what
package created the udev rule that creates the above symlink?
distro fc6
Linux xxx.xxx 2.6.22-rc1-200705170855cfq6-g0479ea0e #134 SMP PREEMPT
Thu May 17 09:13:26 CDT 2007 x86_64 x86_64 x86_64 GNU/Linux
2.6.20
$ udevtest /class/usb_device/usbdev2.10
main: looking at device '/class/usb_device/usbdev2.10' from subsystem
'usb_device'
run_program: '/bin/sh -c 'K=usbdev2.10; K=${K#usbdev}; printf
bus/usb/%03i/%03i ${K%%.*} ${K#*.}''
run_program: '/bin/sh' (stdout) 'bus/usb/002/010'
run_program: '/bin/sh' returned with status 0
udev_rules_get_name: rule applied, 'usbdev2.10' becomes 'bus/usb/002/010'
udev_rules_get_name: add symlink 'scanner-usbdev2.10'
udev_device_event: device '/class/usb_device/usbdev2.10' already in
database, validate currently present symlinks
udev_node_add: creating device node '/dev/bus/usb/002/010', major =
'189', minor = '137', mode = '0644', uid = '0', gid = '0'
udev_node_add: creating symlink '/dev/scanner-usbdev2.10' to 'bus/usb/002/010'
main: run: 'socket:/org/kernel/udev/monitor'
main: run: '/lib/udev/udev_run_devd'
main: run: 'socket:/org/freedesktop/hal/udev_event'
main: run: '/sbin/pam_console_apply /dev/bus/usb/002/010
/dev/scanner-usbdev2.10'
xboom
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: usb-scanner-cameras kernel-2.6.22 and udev-095 problem
On Thu, May 17, 2007 at 12:05:44PM -0500, [EMAIL PROTECTED] wrote:
greg
You didn't answer my, what distro are you using question. Also, what
package created the udev rule that creates the above symlink?
distro fc6
Linux xxx.xxx 2.6.22-rc1-200705170855cfq6-g0479ea0e #134 SMP PREEMPT Thu May
17 09:13:26 CDT 2007 x86_64 x86_64 x86_64 GNU/Linux
You answered the first question above, not the second :(
2.6.20
$ udevtest /class/usb_device/usbdev2.10
main: looking at device '/class/usb_device/usbdev2.10' from subsystem
'usb_device'
run_program: '/bin/sh -c 'K=usbdev2.10; K=${K#usbdev}; printf
bus/usb/%03i/%03i ${K%%.*} ${K#*.}''
run_program: '/bin/sh' (stdout) 'bus/usb/002/010'
run_program: '/bin/sh' returned with status 0
udev_rules_get_name: rule applied, 'usbdev2.10' becomes 'bus/usb/002/010'
udev_rules_get_name: add symlink 'scanner-usbdev2.10'
udev_device_event: device '/class/usb_device/usbdev2.10' already in
database, validate currently present symlinks
udev_node_add: creating device node '/dev/bus/usb/002/010', major = '189',
minor = '137', mode = '0644', uid = '0', gid = '0'
udev_node_add: creating symlink '/dev/scanner-usbdev2.10' to
'bus/usb/002/010'
main: run: 'socket:/org/kernel/udev/monitor'
main: run: '/lib/udev/udev_run_devd'
main: run: 'socket:/org/freedesktop/hal/udev_event'
main: run: '/sbin/pam_console_apply /dev/bus/usb/002/010
/dev/scanner-usbdev2.10'
And if you run that 'udevtest' command on 2.6.21 what happens?
Again, you have not shown me the udev rule that adds that symlink, is it
something you added by hand, or something that Fedora added to the rules
file?
thanks,
greg k-h
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: usb-scanner-cameras kernel-2.6.22 and udev-095 problem
greg
and part of /etc/udev/rules.d/60-libsane.rules
...
ACTION!=add, GOTO=libsane_rules_end
SUBSYSTEM!=usb_device, GOTO=libsane_rules_end
# Hewlett-Packard ScanJet 4100C
SYSFS{idVendor}==03f0, SYSFS{idProduct}==0101, SYMLINK+=scanner-%k
# Hewlett-Packard Photosmart S20 (C5101A) | Hewlett-Packard Photosmart
S20xi (C7150A)
SYSFS{idVendor}==03f0, SYSFS{idProduct}==0102, SYMLINK+=scanner-%k
# Hewlett-Packard ScanJet 4200C | Hewlett-Packard ScanJet 4200Cxi |
Hewlett-Packard ScanJet 4200Cse
SYSFS{idVendor}==03f0, SYSFS{idProduct}==0105, SYMLINK+=scanner-%k
# Hewlett-Packard ScanJet 6200C | Hewlett-Packard ScanJet 6250C
SYSFS{idVendor}==03f0, SYSFS{idProduct}==0201, SYMLINK+=scanner-%k
# Hewlett-Packard ScanJet 3300c
SYSFS{idVendor}==03f0, SYSFS{idProduct}==0205, SYMLINK+=scanner-%k
# Hewlett-Packard ScanJet 4300c
SYSFS{idVendor}==03f0, SYSFS{idProduct}==0305, SYMLINK+=scanner-%k
# Hewlett-Packard ScanJet 5200C
SYSFS{idVendor}==03f0, SYSFS{idProduct}==0401, SYMLINK+=scanner-%k
# Hewlett-Packard ScanJet 3400c
SYSFS{idVendor}==03f0, SYSFS{idProduct}==0405, SYMLINK+=scanner-%k
# Hewlett-Packard ScanJet 2100C
SYSFS{idVendor}==03f0, SYSFS{idProduct}==0505, SYMLINK+=scanner-%k
# Hewlett-Packard ScanJet 6300C | Hewlett-Packard ScanJet 6350C |
Hewlett-Packard ScanJet 6390C
SYSFS{idVendor}==03f0, SYSFS{idProduct}==0601, SYMLINK+=scanner-%k
# Hewlett-Packard ScanJet 2200C
SYSFS{idVendor}==03f0, SYSFS{idProduct}==0605, SYMLINK+=scanner-%k
...
# Dell 1600n
SYSFS{idVendor}==413c, SYSFS{idProduct}==5250, SYMLINK+=scanner-%k
LABEL=libsane_rules_end
xboom
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: usb-scanner-cameras kernel-2.6.22 and udev-095 problem
On Wed, May 16, 2007 at 02:58:22PM -0500, [EMAIL PROTECTED] wrote: > greg > > CONFIG_SYSFS_DEPRECATED=Y > > check that we have > rwxrwxrwx 1 root root 15 May 16 13:43 scanner-usbdev2.12 -> > bus/usb/002/012 > > in /dev directory after usb-scanner connection for kernel-2.6.20 > we don't have this for kernel-2.6.22 Who creates that? udev? What udev rule does that? Can you run 'udevtest' to see what is supposed to be matching here? Odds are you have a broken rule somehow. > > 2.6.20 usb-scanner connect > > # /usr/sbin/udevmonitor > > UEVENT[1179340996.886805] > add@/devices/pci:00/:00:0b.1/usb2/2-2/2-2.2 > UEVENT[1179340996.886864] add@/class/usb_endpoint/usbdev2.12_ep00 > UEVENT[1179340996.887438] > add@/devices/pci:00/:00:0b.1/usb2/2-2/2-2.2/2-2.2:1.0 > UEVENT[1179340996.887467] add@/class/usb_endpoint/usbdev2.12_ep81 > UEVENT[1179340996.887484] add@/class/usb_endpoint/usbdev2.12_ep02 > UEVENT[1179340996.887499] add@/class/usb_endpoint/usbdev2.12_ep83 > UEVENT[1179340996.887514] add@/class/usb_device/usbdev2.12 > UDEV [1179340996.921506] > add@/devices/pci:00/:00:0b.1/usb2/2-2/2-2.2 > UDEV [1179340996.936005] add@/class/usb_endpoint/usbdev2.12_ep00 > UDEV [1179340996.960144] add@/class/usb_endpoint/usbdev2.12_ep81 > UDEV [1179340996.963672] add@/class/usb_endpoint/usbdev2.12_ep02 > UDEV [1179340996.967439] add@/class/usb_endpoint/usbdev2.12_ep83 > UDEV [1179340997.240934] > add@/devices/pci:00/:00:0b.1/usb2/2-2/2-2.2/2-2.2:1.0 > UDEV [1179340997.473142] add@/class/usb_device/usbdev2.12 This last device is correct, and what your udev rule should be using to create your symlink. You didn't answer my, "what distro are you using" question. Also, what package created the udev rule that creates the above symlink? thanks, greg k-h - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: usb-scanner-cameras kernel-2.6.22 and udev-095 problem
greg CONFIG_SYSFS_DEPRECATED=Y check that we have rwxrwxrwx 1 root root 15 May 16 13:43 scanner-usbdev2.12 -> bus/usb/002/012 in /dev directory after usb-scanner connection for kernel-2.6.20 we don't have this for kernel-2.6.22 2.6.20 usb-scanner connect # /usr/sbin/udevmonitor UEVENT[1179340996.886805] add@/devices/pci:00/:00:0b.1/usb2/2-2/2-2.2 UEVENT[1179340996.886864] add@/class/usb_endpoint/usbdev2.12_ep00 UEVENT[1179340996.887438] add@/devices/pci:00/:00:0b.1/usb2/2-2/2-2.2/2-2.2:1.0 UEVENT[1179340996.887467] add@/class/usb_endpoint/usbdev2.12_ep81 UEVENT[1179340996.887484] add@/class/usb_endpoint/usbdev2.12_ep02 UEVENT[1179340996.887499] add@/class/usb_endpoint/usbdev2.12_ep83 UEVENT[1179340996.887514] add@/class/usb_device/usbdev2.12 UDEV [1179340996.921506] add@/devices/pci:00/:00:0b.1/usb2/2-2/2-2.2 UDEV [1179340996.936005] add@/class/usb_endpoint/usbdev2.12_ep00 UDEV [1179340996.960144] add@/class/usb_endpoint/usbdev2.12_ep81 UDEV [1179340996.963672] add@/class/usb_endpoint/usbdev2.12_ep02 UDEV [1179340996.967439] add@/class/usb_endpoint/usbdev2.12_ep83 UDEV [1179340997.240934] add@/devices/pci:00/:00:0b.1/usb2/2-2/2-2.2/2-2.2:1.0 UDEV [1179340997.473142] add@/class/usb_device/usbdev2.12 --- /dev $ ls -l total 0 crw--- 1 test root 14, 12 May 16 13:39 adsp crw--- 1 test root 14, 4 May 16 13:39 audio drwxr-xr-x 3 root root 60 May 16 13:39 bus lrwxrwxrwx 1 root root3 May 16 13:39 cdrom -> hdc lrwxrwxrwx 1 root root3 May 16 13:39 cdrom-hdc -> hdc lrwxrwxrwx 1 root root3 May 16 13:39 cdrw -> hdc lrwxrwxrwx 1 root root3 May 16 13:39 cdrw-hdc -> hdc lrwxrwxrwx 1 root root3 May 16 13:39 cdwriter -> hdc lrwxrwxrwx 1 root root3 May 16 13:39 cdwriter-hdc -> hdc crw--- 1 test root 5, 1 May 16 13:40 console lrwxrwxrwx 1 root root 11 May 16 13:39 core -> /proc/kcore drwxr-xr-x 4 root root 80 May 16 13:39 cpu drwxr-xr-x 6 root root 120 May 16 13:39 disk drwxr-xr-x 2 root root 60 May 16 13:39 dri crw--- 1 test root 14, 3 May 16 13:39 dsp lrwxrwxrwx 1 root root3 May 16 13:39 dvd -> hdc lrwxrwxrwx 1 root root3 May 16 13:39 dvd-hdc -> hdc lrwxrwxrwx 1 root root3 May 16 13:39 dvdrw -> hdc lrwxrwxrwx 1 root root3 May 16 13:39 dvdrw-hdc -> hdc lrwxrwxrwx 1 root root3 May 16 13:39 dvdwriter -> hdc lrwxrwxrwx 1 root root3 May 16 13:39 dvdwriter-hdc -> hdc lrwxrwxrwx 1 root root 13 May 16 13:39 fd -> /proc/self/fd crw-rw-rw- 1 root root 1, 7 May 16 13:39 full srwx-- 1 test root0 May 16 13:40 gpmctl brw--- 1 test disk 22, 0 May 16 13:39 hdc crw--- 1 root root 10, 228 May 16 13:39 hpet prw--- 1 root root0 May 16 13:40 initctl drwxr-xr-x 2 root root 220 May 16 13:40 input crw--- 1 root root 1, 11 May 16 13:39 kmsg srw-rw-rw- 1 root root0 May 16 13:40 log brw-r- 1 root disk 7, 0 May 16 13:39 loop0 brw-r- 1 root disk 7, 1 May 16 13:39 loop1 brw-r- 1 root disk 7, 2 May 16 13:39 loop2 brw-r- 1 root disk 7, 3 May 16 13:39 loop3 brw-r- 1 root disk 7, 4 May 16 13:39 loop4 brw-r- 1 root disk 7, 5 May 16 13:39 loop5 brw-r- 1 root disk 7, 6 May 16 13:39 loop6 brw-r- 1 root disk 7, 7 May 16 13:39 loop7 lrwxrwxrwx 1 root root 13 May 16 13:39 MAKEDEV -> /sbin/MAKEDEV drwxr-xr-x 2 root root 100 May 16 08:39 mapper crw--- 1 root root 10, 227 May 16 13:39 mcelog brw-r- 1 root disk 9, 0 May 16 13:40 md0 crw-r- 1 root kmem 1, 1 May 16 13:39 mem crw--- 1 test root 14, 0 May 16 13:39 mixer drwxr-xr-x 2 root root 60 May 16 13:39 net crw-rw-rw- 1 root root 1, 3 May 16 13:39 null crw-rw 1 root root 10, 144 May 16 13:39 nvram crw-rw 1 root lp99, 0 May 16 13:39 parport0 crw-rw 1 root lp99, 1 May 16 13:39 parport1 crw-rw 1 root lp99, 2 May 16 13:39 parport2 crw-rw 1 root lp99, 3 May 16 13:39 parport3 crw-r- 1 root kmem 1, 4 May 16 13:39 port crw--- 1 root root 108, 0 May 16 13:39 ppp crw-rw-rw- 1 root tty5, 2 May 16 13:46 ptmx drwxr-xr-x 2 root root0 May 16 08:39 pts lrwxrwxrwx 1 root root4 May 16 13:39 ram -> ram1 brw-r- 1 root disk 1, 0 May 16 08:39 ram0 brw-r- 1 root disk 1, 1 May 16 08:39 ram1 brw-r- 1 root disk 1, 10 May 16 08:39 ram10 brw-r- 1 root disk 1, 11 May 16 08:39 ram11 brw-r- 1 root disk 1, 12 May 16 08:39 ram12 brw-r- 1 root disk 1, 13 May 16 08:39 ram13 brw-r- 1 root disk 1, 14 May 16 08:39 ram14 brw-r- 1 root disk 1, 15 May 16 08:39 ram15 brw-r- 1 root disk 1, 2 May 16 08:39 ram2 brw-r- 1 root disk 1, 3 May 16 08:39 ram3 brw-r- 1 root disk 1, 4 May 16 08:39 ram4 brw-r- 1 root disk 1, 5 May 16 08:39 ram5 brw-r- 1 root
Re: usb-scanner-cameras kernel-2.6.22 and udev-095 problem
greg CONFIG_SYSFS_DEPRECATED=Y check that we have rwxrwxrwx 1 root root 15 May 16 13:43 scanner-usbdev2.12 - bus/usb/002/012 in /dev directory after usb-scanner connection for kernel-2.6.20 we don't have this for kernel-2.6.22 2.6.20 usb-scanner connect # /usr/sbin/udevmonitor UEVENT[1179340996.886805] add@/devices/pci:00/:00:0b.1/usb2/2-2/2-2.2 UEVENT[1179340996.886864] add@/class/usb_endpoint/usbdev2.12_ep00 UEVENT[1179340996.887438] add@/devices/pci:00/:00:0b.1/usb2/2-2/2-2.2/2-2.2:1.0 UEVENT[1179340996.887467] add@/class/usb_endpoint/usbdev2.12_ep81 UEVENT[1179340996.887484] add@/class/usb_endpoint/usbdev2.12_ep02 UEVENT[1179340996.887499] add@/class/usb_endpoint/usbdev2.12_ep83 UEVENT[1179340996.887514] add@/class/usb_device/usbdev2.12 UDEV [1179340996.921506] add@/devices/pci:00/:00:0b.1/usb2/2-2/2-2.2 UDEV [1179340996.936005] add@/class/usb_endpoint/usbdev2.12_ep00 UDEV [1179340996.960144] add@/class/usb_endpoint/usbdev2.12_ep81 UDEV [1179340996.963672] add@/class/usb_endpoint/usbdev2.12_ep02 UDEV [1179340996.967439] add@/class/usb_endpoint/usbdev2.12_ep83 UDEV [1179340997.240934] add@/devices/pci:00/:00:0b.1/usb2/2-2/2-2.2/2-2.2:1.0 UDEV [1179340997.473142] add@/class/usb_device/usbdev2.12 --- /dev $ ls -l total 0 crw--- 1 test root 14, 12 May 16 13:39 adsp crw--- 1 test root 14, 4 May 16 13:39 audio drwxr-xr-x 3 root root 60 May 16 13:39 bus lrwxrwxrwx 1 root root3 May 16 13:39 cdrom - hdc lrwxrwxrwx 1 root root3 May 16 13:39 cdrom-hdc - hdc lrwxrwxrwx 1 root root3 May 16 13:39 cdrw - hdc lrwxrwxrwx 1 root root3 May 16 13:39 cdrw-hdc - hdc lrwxrwxrwx 1 root root3 May 16 13:39 cdwriter - hdc lrwxrwxrwx 1 root root3 May 16 13:39 cdwriter-hdc - hdc crw--- 1 test root 5, 1 May 16 13:40 console lrwxrwxrwx 1 root root 11 May 16 13:39 core - /proc/kcore drwxr-xr-x 4 root root 80 May 16 13:39 cpu drwxr-xr-x 6 root root 120 May 16 13:39 disk drwxr-xr-x 2 root root 60 May 16 13:39 dri crw--- 1 test root 14, 3 May 16 13:39 dsp lrwxrwxrwx 1 root root3 May 16 13:39 dvd - hdc lrwxrwxrwx 1 root root3 May 16 13:39 dvd-hdc - hdc lrwxrwxrwx 1 root root3 May 16 13:39 dvdrw - hdc lrwxrwxrwx 1 root root3 May 16 13:39 dvdrw-hdc - hdc lrwxrwxrwx 1 root root3 May 16 13:39 dvdwriter - hdc lrwxrwxrwx 1 root root3 May 16 13:39 dvdwriter-hdc - hdc lrwxrwxrwx 1 root root 13 May 16 13:39 fd - /proc/self/fd crw-rw-rw- 1 root root 1, 7 May 16 13:39 full srwx-- 1 test root0 May 16 13:40 gpmctl brw--- 1 test disk 22, 0 May 16 13:39 hdc crw--- 1 root root 10, 228 May 16 13:39 hpet prw--- 1 root root0 May 16 13:40 initctl drwxr-xr-x 2 root root 220 May 16 13:40 input crw--- 1 root root 1, 11 May 16 13:39 kmsg srw-rw-rw- 1 root root0 May 16 13:40 log brw-r- 1 root disk 7, 0 May 16 13:39 loop0 brw-r- 1 root disk 7, 1 May 16 13:39 loop1 brw-r- 1 root disk 7, 2 May 16 13:39 loop2 brw-r- 1 root disk 7, 3 May 16 13:39 loop3 brw-r- 1 root disk 7, 4 May 16 13:39 loop4 brw-r- 1 root disk 7, 5 May 16 13:39 loop5 brw-r- 1 root disk 7, 6 May 16 13:39 loop6 brw-r- 1 root disk 7, 7 May 16 13:39 loop7 lrwxrwxrwx 1 root root 13 May 16 13:39 MAKEDEV - /sbin/MAKEDEV drwxr-xr-x 2 root root 100 May 16 08:39 mapper crw--- 1 root root 10, 227 May 16 13:39 mcelog brw-r- 1 root disk 9, 0 May 16 13:40 md0 crw-r- 1 root kmem 1, 1 May 16 13:39 mem crw--- 1 test root 14, 0 May 16 13:39 mixer drwxr-xr-x 2 root root 60 May 16 13:39 net crw-rw-rw- 1 root root 1, 3 May 16 13:39 null crw-rw 1 root root 10, 144 May 16 13:39 nvram crw-rw 1 root lp99, 0 May 16 13:39 parport0 crw-rw 1 root lp99, 1 May 16 13:39 parport1 crw-rw 1 root lp99, 2 May 16 13:39 parport2 crw-rw 1 root lp99, 3 May 16 13:39 parport3 crw-r- 1 root kmem 1, 4 May 16 13:39 port crw--- 1 root root 108, 0 May 16 13:39 ppp crw-rw-rw- 1 root tty5, 2 May 16 13:46 ptmx drwxr-xr-x 2 root root0 May 16 08:39 pts lrwxrwxrwx 1 root root4 May 16 13:39 ram - ram1 brw-r- 1 root disk 1, 0 May 16 08:39 ram0 brw-r- 1 root disk 1, 1 May 16 08:39 ram1 brw-r- 1 root disk 1, 10 May 16 08:39 ram10 brw-r- 1 root disk 1, 11 May 16 08:39 ram11 brw-r- 1 root disk 1, 12 May 16 08:39 ram12 brw-r- 1 root disk 1, 13 May 16 08:39 ram13 brw-r- 1 root disk 1, 14 May 16 08:39 ram14 brw-r- 1 root disk 1, 15 May 16 08:39 ram15 brw-r- 1 root disk 1, 2 May 16 08:39 ram2 brw-r- 1 root disk 1, 3 May 16 08:39 ram3 brw-r- 1 root disk 1, 4 May 16 08:39 ram4 brw-r- 1 root disk 1, 5 May 16 08:39 ram5 brw-r- 1 root disk 1, 6 May
Re: usb-scanner-cameras kernel-2.6.22 and udev-095 problem
On Wed, May 16, 2007 at 02:58:22PM -0500, [EMAIL PROTECTED] wrote: greg CONFIG_SYSFS_DEPRECATED=Y check that we have rwxrwxrwx 1 root root 15 May 16 13:43 scanner-usbdev2.12 - bus/usb/002/012 in /dev directory after usb-scanner connection for kernel-2.6.20 we don't have this for kernel-2.6.22 Who creates that? udev? What udev rule does that? Can you run 'udevtest' to see what is supposed to be matching here? Odds are you have a broken rule somehow. 2.6.20 usb-scanner connect # /usr/sbin/udevmonitor UEVENT[1179340996.886805] add@/devices/pci:00/:00:0b.1/usb2/2-2/2-2.2 UEVENT[1179340996.886864] add@/class/usb_endpoint/usbdev2.12_ep00 UEVENT[1179340996.887438] add@/devices/pci:00/:00:0b.1/usb2/2-2/2-2.2/2-2.2:1.0 UEVENT[1179340996.887467] add@/class/usb_endpoint/usbdev2.12_ep81 UEVENT[1179340996.887484] add@/class/usb_endpoint/usbdev2.12_ep02 UEVENT[1179340996.887499] add@/class/usb_endpoint/usbdev2.12_ep83 UEVENT[1179340996.887514] add@/class/usb_device/usbdev2.12 UDEV [1179340996.921506] add@/devices/pci:00/:00:0b.1/usb2/2-2/2-2.2 UDEV [1179340996.936005] add@/class/usb_endpoint/usbdev2.12_ep00 UDEV [1179340996.960144] add@/class/usb_endpoint/usbdev2.12_ep81 UDEV [1179340996.963672] add@/class/usb_endpoint/usbdev2.12_ep02 UDEV [1179340996.967439] add@/class/usb_endpoint/usbdev2.12_ep83 UDEV [1179340997.240934] add@/devices/pci:00/:00:0b.1/usb2/2-2/2-2.2/2-2.2:1.0 UDEV [1179340997.473142] add@/class/usb_device/usbdev2.12 This last device is correct, and what your udev rule should be using to create your symlink. You didn't answer my, what distro are you using question. Also, what package created the udev rule that creates the above symlink? thanks, greg k-h - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: usb-scanner-cameras kernel-2.6.22 and udev-095 problem
On Tue, May 15, 2007 at 12:42:56PM -0500, [EMAIL PROTECTED] wrote: > Linux 2.6.22-rc1-gfaa8b6c3 #130 SMP PREEMPT Tue May 15 08:45:16 CDT 2007 > x86_64 x86_64 x86_64 GNU/Linux > > udev.x86_64 095 > > usb hotplug/udev cannot correctly register usb/scanners, usb/cameras > udev doesn't create devices in /dev like /dev/scanner etc > but we can see devices in /proc/bus/usb/devices Wait, we have not had a /dev/scanner since the 2.4 days. For all of the 2.6 releases, usb scanners are controlled from userspace by xscane, not the kernel. > ... > T: Bus=02 Lev=02 Prnt=03 Port=01 Cnt=02 Dev#= 10 Spd=12 MxCh= 0 > D: Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 > P: Vendor=03f0 ProdID=0601 Rev= 1.00 > S: Manufacturer=Hewlett-Packard > S: Product=HP ScanJet 6300C > S: SerialNumber=xx > C:* #Ifs= 1 Cfg#= 1 Atr=60 MxPwr= 0mA > I:* If#= 0 Alt= 0 #EPs= 3 Cls=00(>ifc ) Sub=00 Prot=00 Driver=(none) > E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms > E: Ad=02(O) Atr=02(Bulk) MxPS= 16 Ivl=0ms > E: Ad=83(I) Atr=03(Int.) MxPS= 1 Ivl=250ms > ... > > it works OK with kernel-2.6.20 What works ok? Xscane? Or some external kernel driver? > can update udev to version 111 help solve this problem ??? Do you have CONFIG_SYSFS_DEPRECATED enabled? If not, please read the help entry for it and enable it. Please let me know if this solves your problem or not. Also, what distro release are you using? thanks, greg k-h - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: usb-scanner-cameras kernel-2.6.22 and udev-095 problem
On Tue, 15 May 2007, [EMAIL PROTECTED] wrote: > > it works OK with kernel-2.6.20 > > can update udev to version 111 help solve this problem ??? Before that, can you pinpoint more closely when the problem appeared? Is it there in 2.6.21 already? Bisect a few times to narrow it down even further? git bisect start git bisect good v2.6.20 git bisect bad .. go, gadget, go! Linus - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
usb-scanner-cameras kernel-2.6.22 and udev-095 problem
Linux 2.6.22-rc1-gfaa8b6c3 #130 SMP PREEMPT Tue May 15 08:45:16 CDT 2007 x86_64 x86_64 x86_64 GNU/Linux udev.x86_64 095 usb hotplug/udev cannot correctly register usb/scanners, usb/cameras udev doesn't create devices in /dev like /dev/scanner etc but we can see devices in /proc/bus/usb/devices ... T: Bus=02 Lev=02 Prnt=03 Port=01 Cnt=02 Dev#= 10 Spd=12 MxCh= 0 D: Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=03f0 ProdID=0601 Rev= 1.00 S: Manufacturer=Hewlett-Packard S: Product=HP ScanJet 6300C S: SerialNumber=xx C:* #Ifs= 1 Cfg#= 1 Atr=60 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 3 Cls=00(>ifc ) Sub=00 Prot=00 Driver=(none) E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=02(O) Atr=02(Bulk) MxPS= 16 Ivl=0ms E: Ad=83(I) Atr=03(Int.) MxPS= 1 Ivl=250ms ... it works OK with kernel-2.6.20 can update udev to version 111 help solve this problem ??? xboom - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
usb-scanner-cameras kernel-2.6.22 and udev-095 problem
Linux 2.6.22-rc1-gfaa8b6c3 #130 SMP PREEMPT Tue May 15 08:45:16 CDT 2007 x86_64 x86_64 x86_64 GNU/Linux udev.x86_64 095 usb hotplug/udev cannot correctly register usb/scanners, usb/cameras udev doesn't create devices in /dev like /dev/scanner etc but we can see devices in /proc/bus/usb/devices ... T: Bus=02 Lev=02 Prnt=03 Port=01 Cnt=02 Dev#= 10 Spd=12 MxCh= 0 D: Ver= 1.00 Cls=00(ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=03f0 ProdID=0601 Rev= 1.00 S: Manufacturer=Hewlett-Packard S: Product=HP ScanJet 6300C S: SerialNumber=xx C:* #Ifs= 1 Cfg#= 1 Atr=60 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 3 Cls=00(ifc ) Sub=00 Prot=00 Driver=(none) E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=02(O) Atr=02(Bulk) MxPS= 16 Ivl=0ms E: Ad=83(I) Atr=03(Int.) MxPS= 1 Ivl=250ms ... it works OK with kernel-2.6.20 can update udev to version 111 help solve this problem ??? xboom - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: usb-scanner-cameras kernel-2.6.22 and udev-095 problem
On Tue, 15 May 2007, [EMAIL PROTECTED] wrote: it works OK with kernel-2.6.20 can update udev to version 111 help solve this problem ??? Before that, can you pinpoint more closely when the problem appeared? Is it there in 2.6.21 already? Bisect a few times to narrow it down even further? git bisect start git bisect good v2.6.20 git bisect bad .. go, gadget, go! Linus - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: usb-scanner-cameras kernel-2.6.22 and udev-095 problem
On Tue, May 15, 2007 at 12:42:56PM -0500, [EMAIL PROTECTED] wrote: Linux 2.6.22-rc1-gfaa8b6c3 #130 SMP PREEMPT Tue May 15 08:45:16 CDT 2007 x86_64 x86_64 x86_64 GNU/Linux udev.x86_64 095 usb hotplug/udev cannot correctly register usb/scanners, usb/cameras udev doesn't create devices in /dev like /dev/scanner etc but we can see devices in /proc/bus/usb/devices Wait, we have not had a /dev/scanner since the 2.4 days. For all of the 2.6 releases, usb scanners are controlled from userspace by xscane, not the kernel. ... T: Bus=02 Lev=02 Prnt=03 Port=01 Cnt=02 Dev#= 10 Spd=12 MxCh= 0 D: Ver= 1.00 Cls=00(ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=03f0 ProdID=0601 Rev= 1.00 S: Manufacturer=Hewlett-Packard S: Product=HP ScanJet 6300C S: SerialNumber=xx C:* #Ifs= 1 Cfg#= 1 Atr=60 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 3 Cls=00(ifc ) Sub=00 Prot=00 Driver=(none) E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=02(O) Atr=02(Bulk) MxPS= 16 Ivl=0ms E: Ad=83(I) Atr=03(Int.) MxPS= 1 Ivl=250ms ... it works OK with kernel-2.6.20 What works ok? Xscane? Or some external kernel driver? can update udev to version 111 help solve this problem ??? Do you have CONFIG_SYSFS_DEPRECATED enabled? If not, please read the help entry for it and enable it. Please let me know if this solves your problem or not. Also, what distro release are you using? thanks, greg k-h - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
