Comment 101 for bug 35638

I see your problem, remember it is the printer talking to the computer, Hall
has nothing to do with that. It's an old printer trying to connect to on a
new(er) computer. There must a reason for the cups people to put time into
that setup. If it happens great if not you will need to try another means,
ie a network print server for any computer on that network.
I HAD A R51 and have replaced it with a T61 just recently. Nobody uses
printer ports now all are USB. The going backwards is the problem you need
to solve. The R51 has a parallel printer port.
good luck

On Fri, Apr 11, 2008 at 5:56 PM, dracon <email address hidden> wrote:

> George,
> Nope. Sorry for the confusion, but I quoted a previous post (who had said
> they had a R51..may have been you) and said I had the same problem, which I
> do. I id'ed the problem with my user assembled desktop with a INTELS865PERL
> motherboard. It has a Parallel port that I have reserved. The laptop is my
> daughter's and it does not have a para/port. Don't have the Make/model handy
> at the moment but when she comes over (frequently) she attaches the printer
> for output....hense the usb adapter cable. It's not uinreasonable to want
> this hardware to work and the HP4 is a horse of a printer with a great
> engine. Not getting rid of that beauty anytime soon.
> Anyway, this combination ought to work in LINUX. Muffing around the
> problem by rearranging hardware doesn't really address the issue of the
> adapter cable support deficiency.
> Thanks for the responses.
>
> I'm trying to find a way to get to the hal folks to see if they can help
> with the issue. There are several threads out there with various
> descriptions of this issue and most have no clue where the genesis of
> the problem is. If it's not hal it below that level. I really do not
> think it is cups but that it is were the low level hardware detection is
> occurring....Since the cable itself is being correctly identified as a
> printer, it seems probable that a timing change in the logic would be
> all that is required to fix this.
>
> Wish I knew more about linux internals (only in a brief weak moment, then
> I get a beer and think about the beach)
> If I find an answer I'll post it back here..Hope you don't have to buy
> another printer to get this fixed. That is not exactly what I would call a
> "it just works" solution.
> Later,
> Bill
>
> --
> Printer is not detected properly over USB
> https://bugs.launchpad.net/bugs/35638
> You received this bug notification because you are a direct subscriber
> of the bug.
>