this weekend I updated the OS on my laptop from OS 10.3 to 11.2.
Most things worked fine … and quickly … but I have issues with some USB devices.
Printers and everthing that works like a Memory Stick, HD (camera, mobile phone) are OK.
But after the update to 11.2 I can neither use my scanner anymore nor my Garmin GPS device.
Both devices are listed with ‘lsusb’ correctly. But applications are not able to find/access them.
For the GPS device I do not know how to do more tests. The application (gpsman) that worked fine with 10.3 does not find it anymore.
The Scanner is detected by Xsane or Skanlite and also the driver can be installed with Yast when plugged in. But a test fails with “sane_start: Error during Device I/O”.
‘sane-find-scanner’ also lists the device correctly. As a normal user it complains that there is no write access for usblib to the usb device. As root this error does not appear. It can be avoided temporarily by setting chmod 777 to all /dev/bus/usb entries. Then ‘sane-find-scanner’ does not show any errors.
But the applications do not work.
I already added the normal user to the “lp” group as shown in the /etc/udev/rules.d/55-libsane.rules and tried to give access to the usb-devices in /etc/fstab … all without success.
As I have two USB devices (Scanner, GPS) that worked fine with 10.3 but are not an external HD (or similar), I assume that someting has changed with the handling of USB devices from 10.3 to 11.2.
Any hint, description or tutorial on that issue woul make me happy.
today I started my machine with two different Knoppix live CD’s.
Knoppix 6.2 (Kernel 2.6.31.6) also does not address the scanner.
With an older version Knoppix 5.1.1 (Kernel 2.6.19) the scanner works on the same hardware. With Suse 10.3 it did as well, with 11.2 it doesn’t. >:(
I now wonder if at least the Scanner problem is related to the new kernel or if the problem is a modified handling of USB devices?
Is it possible that fdi-files with certain policies are required?
Today I also installed a package called sane-autoconfig*.This package brings a file /etc/hal/fdi/policies/20thirdparty/80-scanner.fdi.
This file is not configured at all.
In addition to that there is a file /etc/udev/rules.d/56-sane-backends-autoconfig.rules
Does anybody know if these files need to be configured/modified in order to use different USB devices?
Is my problem related to the kernel or to USB handling.
I’m also seeing the same problem after upgrading from 11.1 to 11.2. I can’t get a stills camera to mount in /var/log/messages all I get is;
Dec 12 11:41:36 scott kernel: 2877.696048] usb 1-10: new high speed USB device using ehci_hcd and address 15
Dec 12 11:41:36 scott kernel: 2877.834033] usb 1-10: New USB device found, idVendor=054c, idProduct=033e
Dec 12 11:41:36 scott kernel: 2877.834050] usb 1-10: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Dec 12 11:41:36 scott kernel: 2877.834056] usb 1-10: Product: DSC-W150
Dec 12 11:41:36 scott kernel: 2877.834061] usb 1-10: Manufacturer: Sony
Dec 12 11:41:36 scott kernel: 2877.834066] usb 1-10: SerialNumber: D352202290EF
Dec 12 11:41:36 scott kernel: 2877.834371] usb 1-10: configuration #1 chosen from 2 choices
Dec 12 11:41:36 scott kernel: 2877.835664] scsi19 : SCSI emulation for USB Mass Storage devices
Dec 12 11:41:36 scott kernel: 2877.836141] usb-storage: device found at 15
Dec 12 11:41:36 scott kernel: 2877.836145] usb-storage: waiting for device to settle before scanning
and as you say lsusb shows the device, I’ve been playing around with fstab after reading some other forum posts of other folks with similar problems (no resolution) and I just have;
I am having similar problems with a scanner after upgrading from openSuSE 11.1 to 11.2. The scanner works as a sane device but can’t be accessed directly with scanbuttond. I can scan with XSane, etc but scanbuttond does not see the scanner. It worked well in 11.1.
It appears that 11.2 uses a new version of libusb (libusb1) together with a separate ‘compatibility’ library to allow older applications to work with it. There are obviously a few areas where the library is not fully compatible with the earlier libusb0; resulting in scanbuttond not finding the scanner
I fixed the problem by replacing the supplied compatibility library (libusb-0_1-4) with the earlier libusb0 - libusb-0_1-4-0.1.12-140.1.
I have the same problem with a Samsung camera, most times it just hangs with “waiting for device to settle before scanning” .
But firs time it looks like it should work(this is dmesg when connecting it for the first time):
[11903.552170] usb 2-1: new full speed USB device using ohci_hcd and address 2
[11903.770160] usb 2-1: New USB device found, idVendor=0839, idProduct=10bd
[11903.770249] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[11903.770269] usb 2-1: Product: Samsung Digital Camera
[11903.770286] usb 2-1: Manufacturer: Samsung Digital Camera
[11903.770793] usb 2-1: configuration #1 chosen from 2 choices
[11903.784971] scsi5 : SCSI emulation for USB Mass Storage devices
[11903.786244] usb-storage: device found at 2
[11903.786257] usb-storage: waiting for device to settle before scanning
[11904.815339] scsi 5:0:0:0: Direct-Access Samsung Digital Camera PQ: 0 ANSI: 0 CCS
[11904.816304] sd 5:0:0:0: Attached scsi generic sg2 type 0
[11904.817590] usb-storage: device scan complete
[11904.852300] sd 5:0:0:0: [sdb] 3862528 512-byte logical blocks: (1.97 GB/1.84 GiB)
[11904.859175] sd 5:0:0:0: [sdb] Write Protect is off
[11904.859267] sd 5:0:0:0: [sdb] Mode Sense: 00 06 00 00
[11904.859278] sd 5:0:0:0: [sdb] Assuming drive cache: write through
[11904.892211] sd 5:0:0:0: [sdb] Assuming drive cache: write through
[11904.892333] sdb: sdb1
[11904.922149] sd 5:0:0:0: [sdb] Assuming drive cache: write through
[11904.922246] sd 5:0:0:0: [sdb] Attached SCSI removable disk
But /dev/sdb doesn’t appear
a working computer(netbook with arch) prints the same, but on this one /dev/sdb doesn’t appear, and for some reason /dev/disks/by_id/Samsung_camera_something appears and points to a non-existant /dev/sdb1.
PD:I tried to move libgphoto in /usr/share/hal and it did nothing, also tried with digikam and gtkam with no luck (some I/o error)