On 13/09/2007, Suffield, David <[EMAIL PROTECTED]> wrote:
>
> Sorry to hear you are still having scanning problems. I would not bother
> buying a new hub. Running with USB 1.1 might be useful feedback, but I
> have see no PSC2200 USB 2.0 issues. I would look at the mother board.
>
> Are you using a newer mother board? Some old clone mother boards had
> non-standard or buggy USB hardware. These boards may work with Windows,
> but not with Linux. Check the web for known issues.
>
> Instead of using the built-in USB hardware on the mother board, try
> installing a USB PCI card. The USB card may work better with Linux.
>
> What mother board(s) are you using? We use brand name PCs for testing,
> but maybe somebody on the list can make a recommendation.
>
> -dave
>
> ________________________________
>
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Will
> Hawes
> Sent: Thursday, September 13, 2007 3:38 AM
> To: hplip-help@lists.sourceforge.net
> Subject: Re: [Hplip-help] Scanning problem
>
>
> On 03/01/2007, Will Hawes <[EMAIL PROTECTED]> wrote:
>
> On 03/01/07, Aaron <[EMAIL PROTECTED]> wrote:
> > On 1/2/07, Will Hawes <[EMAIL PROTECTED]> wrote:
> > > On 21/12/06, Suffield, David <
> [EMAIL PROTECTED]> wrote:
> > > > The following syslog message tells me that hpiod
> is timing out waiting
> > > > for USB data from the scanner.
> > > >
> > > > Dec 18 15:28:28 gateway hpiod: unable to read
> MlcReverseCmd header:
> > > > Resource temporarily unavailable
> > > > Dec 18 15:28:28 gateway hpiod: invalid MlcCredit
> from peripheral, trying
> > > > miser Dec 18 15:29:13 gateway hpiod: unable to
> read MlcReverseCmd
> > > > header:
> > > > Resource temporarily unavailable
> > > > Dec 18 15:29:13 gateway hpiod: invalid MlcCredit
> from peripheral Dec 18
> > > > 15:29:14 gateway hpiod: device cleanup
> > > > uri=hp:/usb/PSC_2200_Series?serial=MY283D26QH0G
> > > >
> > > > Are you getting this syslog message consistently
> every time you start a
> > > > scan job from xsane or scanimage?
> > >
> > > Yes, every time without exception.
> > >
> > > > If so this may be caused by your USB hardware.
> Eliminate any USB hubs
> > > > and plug your PSC 2210 directly into the PC. Some
> cheap USB hubs (and
> > > > some mother boards) do not support 1284.4 well.
> 1284.4 support is needed
> > > > for scanning. 1284.4 is not needed for printing.
> > >
> > > The printer is (and always has been) connected
> directly via the OEM
> > > USB cable. If the printer is connected to a Windows
> box using the same
> > > cable, both printing and scanning work fine.
> > >
> > > The motherboard is the one that was used for a
> previous Ubuntu
> > > Dapper/HPLIP 0.9.7 install for which scanning worked
> OK.
> > >
> > > I've now set up a fresh Dapper installation on a
> separate machine and
> > > installed HPLIP 1.6.12 following the instructions at
>
> > > http://hplip.sourceforge.net. Attempting to scan
> gives me the same
> > > MlcCredit errors described earlier.
> > >
> > > Is there anything else I can do to diagnose this
> further?
> > >
> > > Will
>
> > Has your printer 'ever' worked with linux? If so
> when? If not, do
> > you happen to have a usb hub (1.0 or 1.1 not usb 2.0)
> that you could
> > try to connect to the printer though?
> >
> > A
>
> Printing always did (and still does) work with pretty
> much every
> combination of Ubuntu/HPLIP I've tried.
>
> Scanning has only ever worked on one Ubuntu Dapper
> install with HPLIP
> 0.9.7 , but although I've tried to reproduce this setup
> on the very
> same machine it doesn't any longer. :-/
>
> I don't think there's a USB hub kicking around here
> anywhere, but for
> what they cost I can buy one if you think it would help.
> What's the
> thinking here - could this problem be related to the use
> of USB 2.0
> ports on the motherboard?
>
> Thanks
>
> Will
>
>
>
>
> It's been a while, but I never did get this solved. I've today
> reproduced identical behaviour on a new machine with different spec
> motherboard, this time running a fresh install of Ubuntu 7.04 (feisty).
>
> If the problem is that both these motherboards have poor 1284.4
> support, will using a suitable USB hub circumvent the problem, or is the
> only solution to use a different motherboard?
>
> Assuming a hub could work, please could you let me know what
> type I should obtain, ie. USB 1.0, 1.1 or 2.0, anything specific I need
> to look for on the packaging in terms of supported features?
The motherboard is an Elitegroup GeForce6100SM-M.
I've now tried attaching the device via an Adaptec AUA-2000LP PCI-to-USB
controller, with no change in behaviour whatsoever.
Any ideas?
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
HPLIP-Help mailing list
HPLIP-Help@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hplip-help
