[Gutsy] Samsung ML 2010 USB printer not detected

Please provide the output of the printing bug info script for some basic information about your printing setup. The printingbug info script can be found here: https://wiki.ubuntu.com/PrintingBugInfoScript.

Hello,

for some reason I cannot reproduce the bug, since the printer doesn't become recognized under Gibbon. Nevertheless I attach the the bug info as you wished.

I can't figure out what I did wrong. I have never had any problems with ML-2010 neither under Feisty nor under Debian Etch. However, under Debian Testing and Gutsy Gibbon the printer "strikes" somehow.

Maybe there is a problem with my hardware. Yesterday I got the printer installed but it printed the messages cited above, so I reported the bug. Today I could install the printer after having booted Gibbon from the Live CD and it printed fine. But after installation on the hard disk the system can't find the printer as you can see in the bug info.
Than I installed all updates and tried again with the same result. I've also tested it with different USB cables but it didn't help either. Should I raise the issue on the forum? Or maybe some packages are missing? But I did the default installation.

Best regards,
Dimitri Jakobi

Your printer doesn't seem to be detected at all, could be your hardware that start failing.
Can you follow the "Printer detection" steps described here: https://wiki.ubuntu.com/DebuggingPrintingProblems and attach the requested information.

Hello, thanks for your suggestion. I've followed the instructions on https://wiki.ubuntu.com/DebuggingPrintingProblems, the results are in the attachment. My steps:

1. started the live CD (Gibbon);
2. got installed Samsung ML 2010 (this time everything ran well);
3. tried a print job (a couple of letters from gedit: “file | print | ML-2010 | OK”);
4. nothing happened;
5. then I did the tests described in the wiki following the instructions step by step (see attachment). To my surprise, while making the tests the printer started to print the job I sent to it a couple of minutes beforehand.
6. then I've repeated the all the procedure once again but this time everything failed again. The jobs are pending all the time. The results of the second test are here:
-----------------------------------------------
ubuntu@ubuntu:~$ lsmod | grep usb
usblp 15104 0
usbhid 29536 0
hid 28928 1 usbhid
usbcore 137864 5 usblp,usbhid,ehci_hcd,ohci_hcd
ubuntu@ubuntu:~$ tail -f /var/log/messages
Aug 19 20:50:45 ubuntu kernel: [ 1289.344000] usb 1-4: new full speed USB device using ohci_hcd and address 28
Aug 19 20:50:46 ubuntu kernel: [ 1289.560000] usb 1-4: configuration #1 chosen from 1 choice
Aug 19 20:50:46 ubuntu kernel: [ 1289.568000] /build/buildd/linux-source-2.6.22-2.6.22/drivers/usb/class/usblp.c: usblp0: USB Bidirectional printer dev 28 if 0 alt 0 proto 2 vid 0x04E8 pid 0x326C
Aug 19 20:51:15 ubuntu kernel: [ 1319.228000] usb 1-4: USB disconnect, address 28
Aug 19 20:51:15 ubuntu kernel: [ 1319.228000] /build/buildd/linux-source-2.6.22-2.6.22/drivers/usb/class/usblp.c: usblp0: removed
Aug 19 20:51:15 ubuntu kernel: [ 1319.404000] usb 1-4: new full speed USB device using ohci_hcd and address 29
Aug 19 20:51:16 ubuntu kernel: [ 1319.616000] usb 1-4: configuration #1 chosen from 1 choice
Aug 19 20:51:16 ubuntu kernel: [ 1319.628000] /build/buildd/linux-source-2.6.22-2.6.22/drivers/usb/class/usblp.c: usblp0: USB Bidirectional printer dev 29 if 0 alt 0 proto 2 vid 0x04E8 pid 0x326C
Aug 19 20:51:30 ubuntu kernel: [ 1334.484000] usb 1-4: USB disconnect, address 29
Aug 19 20:51:30 ubuntu kernel: [ 1334.484000] /build/buildd/linux-source-2.6.22-2.6.22/drivers/usb/class/usblp.c: usblp0: removed
Aug 19 20:51:51 ubuntu kernel: [ 1355.536000] usb 1-4: new full speed USB device using ohci_hcd and address 30
Aug 19 20:51:52 ubuntu kernel: [ 1355.748000] usb 1-4: configuration #1 chosen from 1 choice
Aug 19 20:51:52 ubuntu kernel: [ 1355.760000] /build/buildd/linux-source-2.6.22-2.6.22/drivers/usb/class/usblp.c: usblp0: USB Bidirectional printer dev 30 if 0 alt 0 proto 2 vid 0x04E8 pid 0x326C

ubuntu@ubuntu:~$ lpinfo -v
network socket
network beh
direct hpfax
direct hp
network http
network ipp
network lpd
direct parallel:/dev/lp0
direct usb://Samsung/ML-2010
direct scsi
network smb
ubuntu@ubuntu:~$
-----------------------------------------------
As I said, under earlier versions of Ubuntu resp. Debian everything runs out of the box.
I hope the will help.
Best regards,
dj3

Please use the latest Gutsy Live CD (tribe 4) to test, as many problems could already been solved.
Did you install all the Gutsy updates on the hard disc installation?
Do you see anything in your CUPS_error log of the hard disc installation as described in DebuggingPrintingProblems when your printer fails?

My Samsung ML 2010 doesn't work after upgrading to Gutsy from Feisty.
It isn't detected by any cups frontends. (kde system settings, gnome-cups-manager).

It was working fine with Feisty.

Viktor,
Please attach the output of the printing bug info script and your cups error_log as described here: https://wiki.ubuntu.com/DebuggingPrintingProblems in seperate uncompressed attachments.

Viktor,
Is your printer detected in the CUPS web interface if you go to http://localhost:631 in your web browser.
Can you attach the output of the following command:
$ lpinfo -v

I cannot add the printer from the web interface. It is the same problem: USB is not an option as connection.

This is the result of the three printer debug commands from https://wiki.ubuntu.com/DebuggingPrintingProblems :

thyra@thyra-desktop:~$ lpinfo -v
network socket
network beh
direct hpfax
direct hp
network http
network ipp
network lpd
direct parallel:/dev/lp0
file cups-pdf:/
direct scsi
network smb

thyra@thyra-desktop:~$ lsmod | grep usb
usblp 15104 0
usbcore 138248 4 usblp,ehci_hcd,uhci_hcd

thyra@thyra-desktop:~$ tail -f /var/log/messages
Sep 11 21:07:27 thyra-desktop kernel: [ 186.094746] usb 4-1: new full speed
USB device using uhci_hcd and address 3
Sep 11 21:07:28 thyra-desktop kernel: [ 186.268649] usb 4-1: configuration #1
chosen from 1 choice
Sep 11 21:07:28 thyra-desktop kernel: [
186.275598] /build/buildd/linux-source-2.6.22-2.6.22/drivers/usb/class/usblp.c:
usblp0: USB Bidirectional printer dev 3 if 0 alt 0 proto 2 vid 0x04E8 pid
0x326C

Solved.
It is a problem with the new kernel in gutsy.

You can fix it by installing the sysfsutils package and adding the line:
module/usbcore/parameters/autosuspend = -1
to /etc/sysfs.conf

I found the solution in this thread:
http://<email address hidden>/msg491383.html

Reassigning to linux-source-2.6.22

For me this looks like similar to #112030. Though I couldn't get my printer running without modifying udev's aliases file to create symlink from /dev/usblp0 to the proper place inside /dev/bus/usb in Feisty. But after getting it to be detected by cups I had to force install the package by Till Kamppeter to get something else printed than the same error the original reported had.

Perhaps this has something to do with bug 35638?

This one could fix still in Gutsy: Seed the sysfsutils and add the line "module/usbcore/parameters/autosuspend = -1" to the default /etc/sysfs.conf.

That printer is working really fine for me with the splix driver. I don't know if this can help.

I had similar troubles. Eventually I got it to work. See http://uwstopia.nl/blog/2007/11/getting-my-samsung-ml-2010-printer-to-work for a description.

I am assigning this bug to the 'ubuntu-kernel-team' per their bug policy. For future reference you can learn more about their bug policy at https://wiki.ubuntu.com/KernelTeamBugPolicies .

The problem with Samsung ML 2010 seems to be solved in Gusty 7.10 final.
As to me, I have never had any problems with the printer since the official release of Gusty 7.10.

Thanks for the update dj3. I'm going to close this report per you last comment. Please continue to report and future bugs that you may find. Thanks!

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.