1 |
Dale <rdalek1967 <at> gmail.com> writes: |
2 |
|
3 |
> |
4 |
> Howdy, |
5 |
> |
6 |
> This is confusing. A month or so ago, my HP 5300C scanner worked just |
7 |
> fine. |
8 |
|
9 |
|
10 |
Hello Dale, |
11 |
|
12 |
I always keep old (very old) backups of the config file in |
13 |
/etc/cups to see if when a software upgrade occurs, or |
14 |
I have to use the admin page of cups to update/modify/test |
15 |
print/scanner hardware. So it's an easy check therein, if |
16 |
you kept old copies in /etc/cups. Sometimes newer versions |
17 |
of cups do not work well with older or obscure features of |
18 |
various printers/scanners. |
19 |
|
20 |
As far as USB goes, the device's device driver could have been |
21 |
change or it, as a legacy (usb) device became a new part of |
22 |
one of the "unified" device drivers. You'll have to research that |
23 |
or build a new/test kernel with all sorts of USB drivers enabled. |
24 |
You definately have a usb issue, at the very least. |
25 |
|
26 |
If those (2) ideas do not bear fruit, find a "usb sniffer" and use |
27 |
that. You might have to go to a windows box to test the scanner too. |
28 |
Not likely, but the usb chip could have went bad.... |
29 |
|
30 |
http://vusb-analyzer.sourceforge.net/ |
31 |
http://sourceforge.net/projects/usbsnoop/ |
32 |
|
33 |
or general usb tools (may) help: |
34 |
app-admin/usbview |
35 |
sys-apps/usbmon |
36 |
sys-apps/usbutils |
37 |
etc...... |
38 |
............many more usb sniffer too................. |
39 |
|
40 |
Just eliminate the possibilities. |
41 |
I'd test it on a windows box if necessary too. |
42 |
|
43 |
|
44 |
This all begs the question of how it was set up : |
45 |
(after the usb issue is resolved). |
46 |
|
47 |
hplip, cups, *sane*, ??? |
48 |
|
49 |
hth, |
50 |
James |