Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Here's the section of Allend's post/thread's you can try that.
And try the other link as well that he posted and see if that helps.(post #45)
Just found a solution that worked for me after seeing this. https://wiki.archlinux.org/index.php...de_permissions
I created a custom udev rule in a file /etc/udev/rules.d/10-usbprinter.rules containing
Quote:
ATTR{idVendor}=="04f9", ATTR{idProduct}=="0169", MODE:="0660", GROUP:="lp"
After rebooting, I now have printing and scanning working with my Brother DCP-110C.
To get the idVendor and idProduct values look at the output of 'lsusb'
It works whether usblp is blacklisted or not.
ferrari, you're a genius. I haven't thought of that - I switched to a notebook with USB 3.0 and eSATA ports, and THAT may be the reason. My dmesg is still:
Code:
[ 1048.119556] usb 1-1.1: new full-speed USB device number 6 using ehci_hcd
[ 1048.215663] usb 1-1.1: New USB device found, idVendor=04f9, idProduct=01ea
[ 1048.215668] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=3
[ 1048.215670] usb 1-1.1: SerialNumber: 000M9N675233
[ 1048.217291] usblp0: USB Bidirectional printer dev 6 if 0 alt 0 proto 2 vid 0x04F9 pid 0x01EA
But I think that may be the reason! Should I contact SANE or Brother first?
I remember scanner working flawlessly under Arch and Ubuntu some months ago, so it is possible, and I suspect some newer version of... sane? kernel? broke the compatibility.
Quote:
I switched to a notebook with USB 3.0 and eSATA ports, and THAT may be the reason.
If you had mentioned the hardware change earlier, it would have helped. I was labouring under the assumption that only software problems were involved.
I was labouring under the assumption that only software problems were involved.
And I the same; among-est other general diagnostic troubleshooting skills/tasks. (a list I have that I go through all of the task's (run cmds) to help to confirm output and make either an educated guess or complete confirmation that something is either missing or non-funtional)
I'm really sorry for not having thought of this before - I wasn't expecting otherwise working USB 3.0 ports to be the cause.
Let's not get ahead of ourselves. We don't know that this is the cause yet, until you can test with a USB 2.0 controller.
For reference, I get similar (expected) output to yours when my DCP-7055 is connected:
Code:
# dmesg|tail
[ 1246.087450] usb 2-1: new high-speed USB device number 3 using ehci_hcd
[ 1246.206916] usb 2-1: New USB device found, idVendor=04f9, idProduct=0248
[ 1246.206927] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=3
[ 1246.206933] usb 2-1: SerialNumber: E69893D1N337394
[ 1246.245917] usblp0: USB Bidirectional printer dev 3 if 0 alt 0 proto 2 vid 0x04F9 pid 0x0248
[ 1246.245963] usbcore: registered new interface driver usblp
I have USB 2.0 and USB 1.0 ports using the ehci_hcd and uhci_hcd drivers respectively. (USB 3.0 is supported by the xhci_hcd kernel driver.) You can list your USB controller hardware with
And since 'full speed' implies a USB 1.0 could we rule out 3.0 USB with Dusk Glows output?
This just reflects what the controller detects attached to it, not what it is capable of. For example, I have a USB keyboard dongle that gets reported like this
Code:
[ 2334.982071] usb 7-2: new full-speed USB device number 2 using uhci_hcd
[ 2335.154066] usb 7-2: New USB device found, idVendor=046d, idProduct=c52e
[ 2335.154070] usb 7-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2335.154073] usb 7-2: Product: USB Receiver
[ 2335.154075] usb 7-2: Manufacturer: Logitech
I was just surprised that the DCP-7030 USB interface appears as a 'full speed' type, rather than a 'high speed' type, since it has a USB 2.0 interface (as does my DCP-7055). That's why I wondered about how the printer is attached, or perhaps the cable is the issue. The other thing is that I'm not sure if a USB 3.0 host controller can cope with USB 1.0 peripheral devices or hubs, but as I say the printer interface should be detected as 'high speed'.
Without wanting to confuse the issue, and without knowing details about how the printer is attached, I note from here that
Quote:
But with USB 3.0, even though the plug and PC connections look the same at a casual glance, they're not as compatible as the older models. Instead of the earlier version’s four wires, the USB 3.0 cable has eight wires. One is power, one is for the ground, two are for USB 2.0 data, and the remaining four wires are for “SuperSpeed” data. If you take a closer look, you'll see that one edge of the plug is colored blue. The end that plugs into your USB 3.0 device — drive, scanner, printer, camera, whatever — is incompatible with a USB 2.0 device. So, while you can plug a USB 2.0 device with a USB 2.0 cable into a USB 3.0 port or a USB 3.0 device with a USB 3.0 cable into a USB 2.0 port, you can't use a USB 3.0 cable to connect a USB 2.0 device. Got that? The bottom line is you can't mindlessly switch USB cables the way you used to.
I've checked it, and it's right. Scanner works perfectly with other laptops with USB 2.0 ports. I have only 3.0 and eSATA in mine, and don't use any hubs.
Code:
pawel@autumn:~$ lspci -nnk |grep USB -A3
00:1a.0 USB controller [0c03]: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 [8086:1c2d] (rev 05)
Subsystem: Dell Device [1028:04b0]
Kernel driver in use: ehci_hcd
00:1b.0 Audio device [0403]: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller [8086:1c20] (rev 05)
--
00:1d.0 USB controller [0c03]: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 [8086:1c26] (rev 05)
Subsystem: Dell Device [1028:04b0]
Kernel driver in use: ehci_hcd
00:1f.0 ISA bridge [0601]: Intel Corporation HM67 Express Chipset Family LPC Controller [8086:1c4b] (rev 05)
--
0b:00.0 USB controller [0c03]: Texas Instruments TUSB73x0 SuperSpeed USB 3.0 xHCI Host Controller [104c:8241] (rev 02)
Subsystem: Dell Device [1028:04b0]
Kernel driver in use: xhci_hcd
Code:
dmesg after plugging in:
[ 298.621538] usb 2-2: USB disconnect, device number 2
[ 307.641633] usb 2-2: new full-speed USB device number 3 using xhci_hcd
[ 307.677268] usb 2-2: New USB device found, idVendor=04f9, idProduct=01ea
[ 307.677273] usb 2-2: New USB device strings: Mfr=0, Product=0, SerialNumber=3
[ 307.677276] usb 2-2: SerialNumber: 000M9N675233
What's interesting it uses xhci_hcd and it still claims it's just a full-speed USB.
I've informed Brother, and will write a short letter to SANE-devel updating my status.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.