1 |
On Sun, 2019-02-17 at 15:18 +0000, Mick wrote: |
2 |
> On Sunday, 17 February 2019 14:26:41 GMT IMAP wrote: |
3 |
> |
4 |
> > It doesn't show anything. Apparently the printer is just not there, |
5 |
> > except |
6 |
> > for its USB interface. |
7 |
> > |
8 |
> > 1. I tried setting CONFIG_USB_ANNOUNCE_NEW_DEVICES=y, and a few other |
9 |
> > things (diff attached), and now I get more info in dmesg: |
10 |
> > |
11 |
> > [ 91.472049] usb 3-5.1: new full-speed USB device number 7 using |
12 |
> > xhci_hcd |
13 |
> > [ 91.561360] usb 3-5.1: New USB device found, idVendor=0482, |
14 |
> > idProduct=000e |
15 |
> > [ 91.561363] usb 3-5.1: New USB device strings: Mfr=1, Product=2, |
16 |
> > SerialNumber=3 |
17 |
> > [ 91.561364] usb 3-5.1: Product: Kyocera Mita FS-1020D |
18 |
> > [ 91.561366] usb 3-5.1: Manufacturer: Kyocera Mita |
19 |
> > [ 91.561367] usb 3-5.1: SerialNumber: XAX5X26731 |
20 |
> > |
21 |
> > So the printer is definitely there; I just need more splinters under my |
22 |
> > fingernails. |
23 |
> |
24 |
> In case you missed this, did you build net-print/cups with USE="usb" |
25 |
> enabled? |
26 |
|
27 |
Yes: |
28 |
[ebuild R ] net-print/cups-2.2.7::gentoo USE="X acl dbus pam ssl |
29 |
threads usb -debug -java -kerberos -lprng-compat -python (-selinux) -static- |
30 |
libs -systemd -xinetd -zeroconf" ABI_X86="(64) -32 (-x32)" |
31 |
PYTHON_TARGETS="python2_7" 0 KiB |
32 |
|
33 |
I've just remerged it, but to no avail. |
34 |
|
35 |
-- |
36 |
Regards, |
37 |
Peter. |