SlackwareThis Forum is for the discussion of Slackware 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.
root@heracles:~# lsusb
Bus 5 Device 1: ID 0000:0000
Bus 4 Device 3: ID 058f:9360 Alcor Micro Corp.
Bus 4 Device 1: ID 0000:0000
Bus 3 Device 1: ID 0000:0000
Bus 2 Device 3: ID 045e:0040 Microsoft Corp. Wheel Mouse Optical
Bus 2 Device 1: ID 0000:0000
Bus 1 Device 1: ID 0000:0000
root@heracles:~#
which tells me not much... the printer I'm trying to detect is an HP
Laserjet 1020, and I've already done the "stuff" from
foo2zjs.rkkda.com.
Now on a hunch, I tried this:
mkdir /dev/usb
ln /dev/usbdev4.3 /dev/usb/lp0
but I don't think that actually does anything, plus, the /dev/usb
folder disappears on re-boot.
Distribution: Slackware64 14.2 and current, SlackwareARM current
Posts: 1,644
Rep:
Sounds funny that is says nothing about HP, that it looks like it has not been recognized at all, well nearly at all.
I searched a little bit this morning when I had some free time. It seems that the /dev/usb/lp0 is not always the right device name but that you have to adjust the commands (and one config file as I remember) to another one. It COULD be /dev/usblp0 (without the slash, might be a typo in the udev part of the printer installation?). See http://lists.freestandards.org/piper...06/007757.html about this.
according to the FAQ at http://www.linux-usb.org/FAQ.html#ts6 this could be a cable issue. The FAQ recommended trying the command
rmmod ehci-hcd
As soon as I did that, the printer became visible, /dev/usb/lp0 appeared, life is suddenly good why not.
I'll keep trying cables, maybe go & buy a new fancy one, but in the meantime,I'm going to try popping that line in rc.local and see if I can at least get the beasty going.
I just had to post again after reading more of the Linux USB FAQ.
This is a cheap 'hack' if you will that's masking your real problem.
That just removes USB 2.0 functionality from your USB root hub.
That "ehci-hcd" module controls your USB 2.0 controller, so now you
only have USB 1.0 functionality. Maybe you prefer 12 Mbps transfers
rather than 480 Mbps?
Have you ever tried plugging the printer into an USB port on the back
of your box that goes directly to your motherboard?
I tried every usb port on the box, but have mostly stuck to the ones in the back. I'm going to buy a new cable today to see if I can remove the "hack" and get full usb functionality back. Platinum/gold interweave, thorium contacts, etc., etc.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.