From: Max Euer <m.euer@zonnet.nl>
To: linux-hotplug@vger.kernel.org
Subject: udev: USB Printers not printing [solved]
Date: Tue, 19 Apr 2016 16:38:02 +0000 [thread overview]
Message-ID: <57165EEA.20701@zonnet.nl> (raw)
Dear Sirs!
I am no computer expert at all, only an ordinary Linux user for 16 years.
I noticed that with the introduction of udev a couple of years ago some things
stopped working:
notably my USB printer: lpq: queue-name:no daemon present.
This was not the case when udev was prevented from starting at boot time.
Well, you may say 'Why's he clinging on to this old dilapidated lpr thingy?'
I won't bore you with the reason why.
I could not find a solution on the internet but a hint in the udev documentation
made me do this:
creating a device-node usblp0 in /lib/udev/devices/ did the trick.
I might also mention that even the cd-player device did not work with an
ordinary program like alsaplayer for the same reason: /dev/cdrom not being present.
[udev created a cdrom1 but it is not used]
Remains the question of how to create those device-nodes.
I could only do it by booting without udev by doing
cp -a /dev/usblp0{cdrom} /lib/udev/devices/
[MAKEDEV refuses to run when udev is on]
I won't mention other strange behaviours like udev renaming my only eth card
from eth0 to eth1 but that was easy to fix.[pardon me for having it mentioned
anyway]
Hoping this information has been of mild interest to you but for an ordinary
user those common devices not working are a real pain in the ass;
I remain, with compliments
Yours truly
--
Max Euer - Oud Lemiers 18 - NL6295AT Lemiers -
T (NL 06)1840 3128 - F (NL 084)716 4118 - E m.euer@zonnet.nl
reply other threads:[~2016-04-19 16:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=57165EEA.20701@zonnet.nl \
--to=m.euer@zonnet.nl \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).