Comment 27 for bug 35638
Revision history for this message
| Stanley Sokolow (overbyte) wrote Re: Hl-1050 is not detected properly | #27 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
My 'uname -a' output for the 3 installations I've tried it on (Ubuntu 7.04, Ubuntu 6.10, and OpenSUSE 10.2, respectively):
Linux Northgate-U704 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux
Linux Northgate-U610 2.6.17-10-generic #2 SMP Fri Oct 13 18:45:35 UTC 2006 i686 GNU/Linux
Linux Northgate-oS102 2.6.18.2-34-default #1 SMP Mon Nov 27 11:46:27 UTC 2006 i686 i686 i386 GNU/Linux
Here's more specific information. I tried each of the installations on the same hardware other than swapping out the primary hard disk on which Linux was installed as a clean installation, not an upgrade. It's a 2.2 GHz Celeron system with 512 MB of memory. Starting with the printer in sleep mode, I ran a watch command with default 2 sec intervals on the command 'lpinfo -v'. When I say that the printer was "visible", I mean that the appropriate line appears in the output of lpinfo showing "direct usb://Brother/
On Ubuntu 7.04, the printer started visible and stayed visible for a long time (15 minutes) at which time I pressed the wake-up button on the printer. The printer went "ready" (its LED lit steadily) and was still visible. 4 seconds later it went invisible, 6 seconds later visible, 19 seconds later invisible, and so on. Seemingly at random intervals, ranging from a few seconds to 30 seconds, it changes from visible to invisible and back to visible and so on. This was also true on Ubuntu 6.10 and OpenSUSE 10.2, with one difference: On SUSE, the sleeping printer starts invisible, whereas on Ubuntu it starts visible. On all three systems, unplugging, waiting about 10 seconds and replugging the USB cable, or turning off the printer and back on again, causes the printer to become visible but the cycling resumes at random intervals. The cycling continues even when the printer goes back into sleep mode.
If it would help as a regression test, I can replace the Ubuntu 6.10 or OpenSUSE 10.2 with a clean installation of earlier Linux releases and test again. I have quite a few earlier releases from SUSE, Ubuntu, Mandrake, and Red Hat, in my archives.