On 04/30/2011 04:08 PM, mike cloaked wrote:
> Until a few months ago my scanner attached to the usb port on my
> machine was working fine under F14.
>
> It needed a simple:
> Add two lines to /lib/udev/rules.d/65-libsane.rules under the Samsung Lines:
>
> # Samsung SCX-4500W
> ATTRS{idVendor}=="04e8", ATTRS{idProduct}=="342b", ENV{libsane_matched}="yes"
>
> and then firing up the Gimp I could scan immediately - however I have
> not used the scanner for a few months and today when I needed it there
> it is not recognised.
>
> I tried (as root):
>
> sane-find-scanner - and it gives:
>
> "found USB scanner (vendor=0x04e8 [Samsung Electronics Co., Ltd.],
> product=0x342b [SCX-4500W Series]) at libusb:001:002"
>
> but yet:
> "[root@home1 ~]# scanimage -L
>
> No scanners were identified. If you were expecting something different,
> check that the scanner is plugged in, turned on and detected by the
> sane-find-scanner tool (if appropriate). Please read the documentation
> which came with this software (README, FAQ, manpages)."
>
> My original config is still as it was (I checked) - and also the
> /etc/sane.d/dll.conf still contains the "xerox_mfp" entry at the
> bottom that used to be needed.
>
> I also made selinux permissive in case that was the issue - and it was
> the same -
>
> Does anyone know if something has changed in F14 recently that may
> have been the cause of this change to scanner recognition - or a way
> to work around this?
>
> Thanks
>
I have a Samsung printer and if you used the Samsung drivers Selinux 
will give you headaches . It won't let the printer print.

It appears that the USB port has found the Samsung printer, As SU do a   
setenforce 0; fixfiles -F restore; setenforce 1; reboot

If that does not work do a reinstall of drivers.
I had to do a  su- to get the drivers to install correctly .
-- 
users mailing list
[email protected]
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

Reply via email to