Red Hat Bugzilla – Bug 156899
cannot get Samsung ML-1740 usb printer to work
Last modified: 2007-11-30 17:11:05 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050416 Fedora/1.0.3-1.3.1 Firefox/1.0.3
Description of problem:
I'm trying to get a Samsung ML-1740 usb printer to work on my FC3 system (it has been suggested that it works as an "ML-1710")
lsusb reports (hwdata-0.145-1)
Bus 002 Device 007: ID 04e8:324c Samsung Electronics Co., Ltd
ML-1740 Laser Printer
(Note that I added the entry for 04e8:324c in /usr/share/hwdata/usb.ids by hand; suggested in some other bug report -- can't find it right now, my head is spinning)
kernel: usb 2-1: new full speed USB device using uhci_hcd and address 7
system-config-printer does not show any devices except /dev/lp0, and I have no /dev/usb directory...
Am I missing something obvious?
Version-Release number of selected component (if applicable):
Steps to Reproduce:
2. -> new
3. ---> Find no useful locally-connected devices
booting with 'pci=routeirq' does not affect this problem.
If /dev/usb/lp0 doesn't exist you have a kernel issue of some sort.
Please attach full dmesg and /proc/bus/usb/devices, taken with the printer
connected (do not drop them into the comments box).
'modprobe usblp' solved the problem, do you still want dmesg and
I see. Something is wrong with hotplug (FC3 does not use udevsend).
If the device was created after, it means that udev works right.
No, I do not need dmesg in this case. However, the /proc/bus/usb/devices
is always needed, to verify that the printer reports correct class, etc.
The driver should be loaded on hotplug. N.B. it makes no sense
to verify load-on-open on udev systems, because /dev/usb/lp0 is created
by udev when the driver is loaded.
What does this produce:
grep usblp /lib/modules/$(uname -r)/modules.usbmap
An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which
may contain a fix for your problem. Please update to this new kernel, and
report whether or not it fixes your problem.
If you have updated to Fedora Core 4 since this bug was opened, and the problem
still occurs with the latest updates for that release, please change the version
field of this bug to 'fc4'.
This bug has been automatically closed as part of a mass update.
It had been in NEEDINFO state since July 2005.
If this bug still exists in current errata kernels, please reopen this bug.
There are a large number of inactive bugs in the database, and this is the only
way to purge them.