Yes, this sounds like a permissions issue. I have not checked Suse 9.0, but Suse 10.0 had a similar issue with permmissions. So, the following info may apply.
On some older Linux distros the standard
/etc/udev/rules.d/55-hpmud.rules file will not work (ie: Suse 10.0). The
reason for this is the usbfs uses /proc/bus/usb/ instead of
/dev/bus/usb/. Since udev is designed to support /dev not /proc device
files, normal udev rules will not work. Thus the /proc/bus/usb/ device
file privileges are not set correctly.
In order to support /proc/bus/usb/ based systems a custom rules file can
be used. See the attached rules file. This rules file is product-id
based. Once the product-id is verified the correct /proc/bus/usb/
privileges will be set.
The example only has one rule line for the Laserjet 3050 product-id
0x3217 (ie: SYSFS{idProduct}=="3217"). In order to support other HP
devices, new rules lines must be added.
New devices can be added by duplicating the LJ 3050 rules line and
changing the product-id. Use lsusb to determine the actual product-id
for other devices.
Once your edit is complete replace the old
/etc/udev/rules.d/55-hpmud.rules file with the new rules file.
Unplug/plug your usb device, the new rule will be executed, then the
correct privileges for the device file at /proc/bus/usb/ should be set.
Correct privileges can be checked with "ls -l /proc/bus/usb/.../..."
command.
-dave
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf
> Of Lothar Gb.
> Sent: Thursday, August 30, 2007 12:21 AM
> To: [email protected]
> Subject: [Hplip-help] Device Files and Permissions under SuSE 9.0
>
> Hi,
>
> i have an OfficeJet Pro 7580 and compiled and installed
> hplip-2.7.7 on my SuSE 9.0 system.
>
> I have a problem with scanning. The comand 'scanimage -L'
> works only if i loged in as root. I think this is a
> permission problem. To fix this i first tried to find out
> wich device files are used. Obviously the files in /dev/usb
> are not responsible because setting all permissions to
> crwxrwrxrwx (only for test cases) don't fix my problem.
> Scanning (under root) even works if i remove the /dev/usb-directory.
>
> After some googeling if found out, that the device files
> /dev/bus/... might be used. Theses files are not on my
> system. Furthermore i am not able to create these device
> files, because minor numbers greater than 255 are necessary,
> but my mknod only process the lower 8 bit of the minor number given.
>
> Can anybody help?
>
> Thanks for your answers.
>
> Kind regards,
> Lothar
>
>
> --------------------------------------------------------------
> -----------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and
> a browser.
> Download your FREE copy of Splunk now >>
> http://get.splunk.com/ _______________________________________________
> HPLIP-Help mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/hplip-help
>
55-hpmud-suse10.rules
Description: 55-hpmud-suse10.rules
------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________ HPLIP-Help mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/hplip-help
