Menu
▾
▴
hpoj-devel
|
From: Obi-Wan <bv...@in...> - 2001-05-26 06:13:10
|
I forgot to mention that printing works fine using lprng / DJ8xx / HPIJS,
so I know the device is hooked up OK. dll.conf contains only "net" and "hp".
# cat /etc/sane.d/hp.conf
mlc:mlcpp0
option connect-ptal
# lsmod
Module Size Used by
ieee12844pp 15520 0
ieee12844 13008 1 [ieee12844pp]
parport_probe 3520 0
(parport and parport_pc are compiled into the kernel)
> Per the instructions in the error message:
>
> # hpo get OID_STATUS_MSG_LINE1_PART1
> Error 0 (system error 110) in file mlccon.c, line 263:
> Unexpected Error, please post a bug report to hpo...@so...
>
> # hpo devid
> Error 5 (system error 110) in file mlccon.c, line 93:
> Connection to peripheral lost
>
> # cat /proc/parport/0/autoprobe
> CLASS:PRINTER;
> MODEL:PSC 500;
> MANUFACTURER:HEWLETT-PACKARD;
> DESCRIPTION:Hewlett-Packard PSC 500;
> COMMAND SET:MLC,PCL,PML,SCL;
>
> # scanimage -V
> scanimage (sane-backends) 1.0.4
>
> # uname -a
> Linux tatooine 2.2.16 #7 Thu Aug 31 02:09:34 CDT 2000 i586 unknown
>
> Anything else you need from me, email direct. I'm not on the devel list.
>
> -- Obi-Wan
>
> --
> Ben "Obi-Wan" Hollingsworth ob...@je...
> The stuff of earth competes for the allegiance I owe only to the
> Giver of all good things, so if I stand, let me stand on the
> promise that You will pull me through. -- Rich Mullins
>
--
Ben "Obi-Wan" Hollingsworth ob...@je...
The stuff of earth competes for the allegiance I owe only to the
Giver of all good things, so if I stand, let me stand on the
promise that You will pull me through. -- Rich Mullins
|
|
From: <pa...@rc...> - 2001-05-30 18:59:53
|
Ben "Obi-Wan" Hollingsworth wrote: > Per the instructions in the error message: > > # hpo get OID_STATUS_MSG_LINE1_PART1 > Error 0 (system error 110) in file mlccon.c, line 263: > Unexpected Error, please post a bug report to hpo...@so... > > # hpo devid > Error 5 (system error 110) in file mlccon.c, line 93: > Connection to peripheral lost ... > printing works fine using lprng / DJ8xx / HPIJS, > so I know the device is hooked up OK. Hi, Ben. Do any error messages appear in syslog (/var/log/messages) when you do this? Also, when you print using the hpijs DJ8xx driver, are you printing to /dev/lp0 or /dev/ptal-printd/mlc_mlcpp0? David |
|
From: Obi-Wan <bv...@in...> - 2001-05-30 19:59:24
|
OK, I'm on the devel list now.
>> # hpo get OID_STATUS_MSG_LINE1_PART1
>> Error 0 (system error 110) in file mlccon.c, line 263:
>> Unexpected Error, please post a bug report to hpo...@so...
>>
>> # hpo devid
>> Error 5 (system error 110) in file mlccon.c, line 93:
>> Connection to peripheral lost
> ...
>> printing works fine using lprng / DJ8xx / HPIJS,
>> so I know the device is hooked up OK.
>
> Hi, Ben. Do any error messages appear in syslog (/var/log/messages) when
> you do this? Also, when you print using the hpijs DJ8xx driver, are you
> printing to /dev/lp0 or /dev/ptal-printd/mlc_mlcpp0?
Printing to /dev/lp0.
There are a number of related entries in a number of different log
files, but I was messing with the config all night, and this was a
few days ago, so I don't remember which messages apply to my current
configuration. I'll try it again tonight (hopefully) and see what
the logs turn up.
This is a Debian 2.2 (unstable) distribution, BTW.
I would also like to add that I think this HP/Linux co-venture for
drivers is awesome. I bought my PSC 500 some time ago, against the
advice of some who knew better than I, and I had been regretting it
almost from day one because scanning didn't work & printing was crappy.
With the new HPIJS driver, printing is now great, and I anticipate
scanning will work equally well before long. I wish I had the time
to code to the project. I've got the skills, but not the time.
-- Obi-Wan
--
Ben "Obi-Wan" Hollingsworth ob...@je...
The stuff of earth competes for the allegiance I owe only to the
Giver of all good things, so if I stand, let me stand on the
promise that You will pull me through. -- Rich Mullins
|
|
From: <pa...@rc...> - 2001-05-30 20:17:24
|
Ben "Obi-Wan" Hollingsworth wrote:
> Printing to /dev/lp0.
>
> There are a number of related entries in a number of different log
> files, but I was messing with the config all night, and this was a
> few days ago, so I don't remember which messages apply to my current
> configuration. I'll try it again tonight (hopefully) and see what
> the logs turn up.
>
> This is a Debian 2.2 (unstable) distribution, BTW.
Hi, "Obi-Wan". :-) Since you're running "unstable" Debian, then perhaps
you should try "unstable" hpoj from CVS. It has a new user-mode I/O driver
(ptal-mlcd), which I expect will either work better or at least will provide
better diagnostics.
Note that once you have the hpoj software running, you should print to
/dev/ptal-printd/XXXXXX ("XXXXXX" varies between hpoj-0.7 and hpoj-CVS)
instead of /dev/lp0.
> I would also like to add that I think this HP/Linux co-venture for
> drivers is awesome. I bought my PSC 500 some time ago, against the
> advice of some who knew better than I, and I had been regretting it
> almost from day one because scanning didn't work & printing was crappy.
> With the new HPIJS driver, printing is now great, and I anticipate
> scanning will work equally well before long.
Thanks for your comments. I'm glad that you're now happy with your PSC 500
(pending further setup of scanning, of course).
> I wish I had the time
> to code to the project. I've got the skills, but not the time.
Even if you don't have time for coding, any testing/feedback you can give
on the development code in CVS will be extremely valuable as I prepare for
the next stable release (0.8) in the next few months.
David
|
|
From: Obi-Wan <bv...@in...> - 2001-05-30 23:00:47
|
> Hi, "Obi-Wan". :-) Since you're running "unstable" Debian, then perhaps
> you should try "unstable" hpoj from CVS. It has a new user-mode I/O driver
> (ptal-mlcd), which I expect will either work better or at least will provide
> better diagnostics.
I'll give that a shot in upcoming days.
> Note that once you have the hpoj software running, you should print to
> /dev/ptal-printd/XXXXXX ("XXXXXX" varies between hpoj-0.7 and hpoj-CVS)
> instead of /dev/lp0.
Uh... OK. Why?
--
Ben "Obi-Wan" Hollingsworth ob...@je...
The stuff of earth competes for the allegiance I owe only to the
Giver of all good things, so if I stand, let me stand on the
promise that You will pull me through. -- Rich Mullins
|
|
From: Obi-Wan <bv...@in...> - 2001-05-31 08:29:48
|
> Hi, "Obi-Wan". :-) Since you're running "unstable" Debian, then perhaps
> you should try "unstable" hpoj from CVS. It has a new user-mode I/O driver
> (ptal-mlcd), which I expect will either work better or at least will provide
> better diagnostics.
Well, I grabbed the CVS tree at about 5pm CDT Wednesday and installed it.
Scanning now works great. Printing doesn't work at all, using either
/dev/lp0 or /dev/ptal-printd/mlc_par_psc500. :-(
Given the choice, I'd prefer to have a printer.
Both ptal-mcld and ptal-print dump copious amounts of debugging info
to the shell, even with the stock install (./configure --without-usb).
So much so that it overflowed my scrollback buffer. Before I send
thousands of lines of useless stuff to the list, is there anything
in particular that you'd like to see?
--
Ben "Obi-Wan" Hollingsworth ob...@je...
The stuff of earth competes for the allegiance I owe only to the
Giver of all good things, so if I stand, let me stand on the
promise that You will pull me through. -- Rich Mullins
|
|
From: <pa...@rc...> - 2001-05-30 23:11:58
|
Ben "Obi-Wan" Hollingsworth wrote in response to me:
> > Note that once you have the hpoj software running, you should print to
> > /dev/ptal-printd/XXXXXX ("XXXXXX" varies between hpoj-0.7 and hpoj-CVS)
> > instead of /dev/lp0.
>
> Uh... OK. Why?
Because /dev/lp0 goes directly to the parallel port, bypassing (and probably
conflicting with) ptal-mlcd, which is also trying to drive the parallel port.
The "ptal-printd" daemon, mentioned in PRINT-HOWTO, provides a similar
interface to /dev/lp0, although with a different path, and routes the print
job data through ptal-mlcd.
David
|
|
From: <pa...@rc...> - 2001-05-31 09:00:56
|
Ben "Obi-Wan" Hollingsworth wrote: > Well, I grabbed the CVS tree at about 5pm CDT Wednesday and installed it. > Scanning now works great. Printing doesn't work at all, using either > /dev/lp0 or /dev/ptal-printd/mlc_par_psc500. :-( > > Given the choice, I'd prefer to have a printer. Hang in there, Ben. There's got to be a way to get both working. :-) > Both ptal-mcld and ptal-print dump copious amounts of debugging info > to the shell, even with the stock install (./configure --without-usb). Is there any reason why you used the "--without-usb" switch? There's nothing wrong with using it, of course, but if you found a build problem that needs it as a workaround then I'd like to fix it. > So much so that it overflowed my scrollback buffer. Before I send > thousands of lines of useless stuff to the list, is there anything > in particular that you'd like to see? Well, not knowing what's on the menu, it's hard to know what to order. :-) For starters, you could run the "script" command and invoke ptal-mlcd and ptal-printd (after making sure any old instances are killed off). Then try printing something that causes the error messages to spew. Once it has quieted down, you can exit the shell spawned by script and send the resulting "typescript" file. If it's really big you can send it just to me (both to dav...@hp... and pa...@rc...), but other than that we can keep this discussion on the mailing list. David |
|
From: Obi-Wan <bv...@in...> - 2001-05-31 16:47:53
|
>> Both ptal-mcld and ptal-print dump copious amounts of debugging info
>> to the shell, even with the stock install (./configure --without-usb).
>
> Is there any reason why you used the "--without-usb" switch? There's nothing
> wrong with using it, of course, but if you found a build problem that needs
> it as a workaround then I'd like to fix it.
My old box doesn't have USB support. I conjectured that using that flag
might make my compiles faster and/or my binary smaller.
BTW, for you Debian types out there, I had to make one little hack to
make hpoj recognize the QT stuff. The deb for QT puts the includes
in /usr/include/qt (not a bad idea, since there are dozens of them),
but the libs & binaries in /usr/lib & /usr/bin. The hpoj configure
script expects all three subdirs to be under the same parent dir. I
had to create a new directory named /usr/qt and inside that create
symlinks to /usr/bin, /usr/lib, and /usr/include/qt for the bin, lib,
and include subdirs, respectively. The stock hpoj configure script
now finds /usr/qt all on its own, and compiles in support for it.
# mkdir /usr/qt
# cd /usr/qt
# ln -s /usr/bin
# ln -s /usr/lib
# ln -s /usr/include/qt include
>> So much so that it overflowed my scrollback buffer. Before I send
>> thousands of lines of useless stuff to the list, is there anything
>> in particular that you'd like to see?
>
> Well, not knowing what's on the menu, it's hard to know what to order. :-)
> For starters, you could run the "script" command and invoke ptal-mlcd and
> ptal-printd (after making sure any old instances are killed off). Then try
> printing something that causes the error messages to spew. Once it has
> quieted down, you can exit the shell spawned by script and send the
> resulting "typescript" file. If it's really big you can send it just to me
> (both to dav...@hp... and pa...@rc...), but other than that we
> can keep this discussion on the mailing list.
I had the foresight to leave my PSC 500 on when I came to work today,
so I tried to scan something just now. I was fiddling with rc scripts,
so I killed & restarted ptal-mlcd & ptal-printd numerous times this
morning. Here's what's currently running:
> psg ptal
root 12720 0.0 2.4 1768 740 pts/15 S 11:18 0:00 /usr/local/sbin/ptal-mlcd par:psc500 -alias mlcpp0
root 12722 0.0 1.2 1244 392 pts/15 S 11:18 0:00 /usr/local/sbin/ptal-printd mlc:par:psc500 -like /dev/lp0
I redirected output to a log file when I launched them. When I run
scanimage -d hp:mlc:par:psc500 --test
I get this to stdout from scanimage:
> scanimage -d hp:mlc:par:psc500 --test
ptalChannelOpen(chan=0x08054678): provider failed open!
ptalChannelOpen(chan=0x08054678): provider failed open!
scanimage: open of device hp:mlc:par:psc500 failed: Error during device I/O
and this in the ptal-mlcd log file:
---------
ptal-mlcd: ERROR at transport/ExMlcCommandChannel.cpp:186, dev=<par:psc500>, pid=12720, errno=11
Reply timer popped on port=0, count=1!
ptal-mlcd: ERROR at ExMgr.cpp:872, dev=<par:psc500>, pid=12720, errno=11
exClose(reason=0x3002)
---------
Curiously, ptal-devid also fails now. It worked last night:
> ptal-devid mlc:par:psc500
ptalMlcDeviceGetDeviceIDString(dev=par:psc500): unsuccessful status=13!
ptalDeviceGetDeviceIDString(dev=mlc:par:psc500) failed!
The same errors are dumped to the ptal-mlcd log file.
I can't power cycle my PSC or restart my computer remotely (won't boot
automatically at the moment), so who knows what state either of them
is really in right now. I'll try more from home some evening soon.
--
Ben "Obi-Wan" Hollingsworth ob...@je...
The stuff of earth competes for the allegiance I owe only to the
Giver of all good things, so if I stand, let me stand on the
promise that You will pull me through. -- Rich Mullins
|
|
From: PASCHAL,DAVID (HP-Roseville,ex1) <dav...@hp...> - 2001-06-01 00:04:39
|
Ben "Obi-Wan" Hollingsworth wrote:
> My old box doesn't have USB support. I conjectured that
> using that flag
> might make my compiles faster and/or my binary smaller.
It prevents a very small amount of code from being compiled, but I don't
think that the time/space savings is enough to be worth the trouble of
typing an extra parameter on the ./configure command line. But do as you
wish. :-)
> BTW, for you Debian types out there, I had to make one little hack to
> make hpoj recognize the QT stuff. The deb for QT puts the includes
> in /usr/include/qt (not a bad idea, since there are dozens of them),
> but the libs & binaries in /usr/lib & /usr/bin. The hpoj configure
> script expects all three subdirs to be under the same parent dir.
Thanks for pointing that out. I added this to my TODO list.
> I had the foresight to leave my PSC 500 on when I came to work today,
> so I tried to scan something just now. I was fiddling with
> rc scripts,
> so I killed & restarted ptal-mlcd & ptal-printd numerous times this
> morning. Here's what's currently running:
>
> > psg ptal
> root 12720 0.0 2.4 1768 740 pts/15 S 11:18
> 0:00 /usr/local/sbin/ptal-mlcd par:psc500 -alias mlcpp0
> root 12722 0.0 1.2 1244 392 pts/15 S 11:18
> 0:00 /usr/local/sbin/ptal-printd mlc:par:psc500 -like /dev/lp0
That looks fine, although the "-alias mlcpp0" isn't really necessary unless
you're upgrading from a previous version of hpoj and don't want to
reconfigure SANE or whatever for the new device name format.
...
> and this in the ptal-mlcd log file:
>
> ---------
> ptal-mlcd: ERROR at transport/ExMlcCommandChannel.cpp:186,
> dev=<par:psc500>, pid=12720, errno=11
> Reply timer popped on port=0, count=1!
>
> ptal-mlcd: ERROR at ExMgr.cpp:872, dev=<par:psc500>,
> pid=12720, errno=11
> exClose(reason=0x3002)
That's not good. :-) Occasionally I've managed to get the R series and PSC
500 into a bad state, where the LCD scrolls the message "turn the power off
and back on again". I wonder if that's what happened here? But in that
case I would have expected a different error. Anyway, I'm just thinking
aloud here.
Another thing that comes to mind is to make sure that your parallel port is
configured in your BIOS setup for preferably ECP, or PS/2 (aka BPP)
otherwise, but not EPP. Also, make sure you're using a good parallel cable
and that the device is connected directly to your computer without any
switchboxes or other pass-through devices, such as Zip drives.
Here's another thing you can try, but probably not until you get home and
make sure the device is in a good state. Add the "-nofork" switch to
ptal-mlcd, and it will give you a debug console. Use the "log" command to
enable debug logging ("nolog" turns off the debug messages). Then use the
"activate" command to make it start trying to talk to the peripheral. When
the messages stop spewing, use the "dump" command, which displays the state
of the internal data structures. Wait about 20 seconds to see if you get
the "reply timer popped" message. If that doesn't happen, then in another
window try ptal-devid (this should work if you've gotten this far). After
this point try printing and scanning (separately) and see what happens. You
can press control-C to kill ptal-mlcd.
David
|
|
From: Obi-Wan <bv...@in...> - 2001-06-01 07:39:14
|
>> and this in the ptal-mlcd log file:
>>
>> ---------
>> ptal-mlcd: ERROR at transport/ExMlcCommandChannel.cpp:186,
>> dev=<par:psc500> , pid=12720, errno=11
>> Reply timer popped on port=0, count=1!
>>
>> ptal-mlcd: ERROR at ExMgr.cpp:872, dev=<par:psc500> ,
>> pid=12720, errno=11
>> exClose(reason=0x3002)
>
> That's not good. :-) Occasionally I've managed to get the R series and PSC
> 500 into a bad state, where the LCD scrolls the message "turn the power off
> and back on again". I wonder if that's what happened here? But in that
> case I would have expected a different error. Anyway, I'm just thinking
> aloud here.
LCD looked fine when I got home.
> Another thing that comes to mind is to make sure that your parallel port is
> configured in your BIOS setup for preferably ECP, or PS/2 (aka BPP)
> otherwise, but not EPP. Also, make sure you're using a good parallel cable
> and that the device is connected directly to your computer without any
> switchboxes or other pass-through devices, such as Zip drives.
Good cable. No pass-through devices. I'll check the BIOS next time
the system is down.
> Here's another thing you can try, but probably not until you get home and
> make sure the device is in a good state. Add the "-nofork" switch to
> ptal-mlcd, and it will give you a debug console. Use the "log" command to
> enable debug logging ("nolog" turns off the debug messages). Then use the
> "activate" command to make it start trying to talk to the peripheral. When
> the messages stop spewing, use the "dump" command, which displays the state
> of the internal data structures. Wait about 20 seconds to see if you get
> the "reply timer popped" message. If that doesn't happen, then in another
> window try ptal-devid (this should work if you've gotten this far). After
> this point try printing and scanning (separately) and see what happens. You
> can press control-C to kill ptal-mlcd.
On my list...
I did make a fresh reboot of my system & the PSC500 earlier this evening
(before I read your message about checking the BIOS). Without checking
anything, I printed a few pages & it worked fine. No errors in my stdout
logs. I brought up xsane to test that. Grabbing a preview worked, but
was dreadfully slow. Note that I'm on a P90 & at the same time I was
listening to a RealAudio station & actively web browsing. Still, it
seemed slower than it should have been. Attempting to scan a color image
to disk at 150 dpi cranked away for a good long while, then flagged an
xsane error window (something related to opening the output file), and
the shell said this:
> xsane
ptalChannelOpen(chan=0x080E6500): provider failed open!
ptalMlcChannelOpen(chan=0x080E6500): read(openReply) returns 0!
ptalChannelOpen(chan=0x080E6500): provider failed open!
The stdout log then got gobs of output, which I've included below.
--
Ben "Obi-Wan" Hollingsworth ob...@je...
The stuff of earth competes for the allegiance I owe only to the
Giver of all good things, so if I stand, let me stand on the
promise that You will pull me through. -- Rich Mullins
------------------------- Achilles tendon - cut here -------------------------
ptal-mlcd: ERROR at ParPort.cpp:163, dev=<par:psc500>, pid=139, errno=11
statusWaitSetClear(event=23) timed out!
ptal-mlcd: ERROR at ExMgr.cpp:2131, dev=<par:psc500>, pid=139, errno=11
llioService: llioForwardToReverse failed!
ptal-mlcd: ERROR at ExMgr.cpp:872, dev=<par:psc500>, pid=139, errno=11
exClose(reason=0x0010)
ptal-mlcd: ERROR at ParPort.cpp:163, dev=<par:psc500>, pid=139, errno=11
statusWaitSetClear(event=23) timed out!
ptal-mlcd: ERROR at ExMgr.cpp:2131, dev=<par:psc500>, pid=139, errno=11
llioService: llioReverseToForward failed!
ptal-mlcd: ERROR at ExMgr.cpp:872, dev=<par:psc500>, pid=139, errno=11
exClose(reason=0x0010)
ptal-mlcd: ERROR at transport/ExMlcTransport.cpp:1059, dev=<par:psc500>, pid=139, errno=11
reverseDataReceived_ts(port=0,channel=2): not open!
ptal-mlcd: ERROR at transport/ExMlcCommandChannel.cpp:1632, dev=<par:psc500>, pid=139, errno=11
sendError(port=0,MLC): error=0x07.
ptal-mlcd: ERROR at ExMgr.cpp:872, dev=<par:psc500>, pid=139, errno=11
exClose(reason=0x3007)
ptal-mlcd: ERROR at transport/ExMlcTransport.cpp:1059, dev=<par:psc500>, pid=139, errno=11
reverseDataReceived_ts(port=0,channel=2): not open!
ptal-mlcd: ERROR at transport/ExMlcCommandChannel.cpp:1632, dev=<par:psc500>, pid=139, errno=11
sendError(port=0,MLC): error=0x07.
ptal-mlcd: ERROR at ExMgr.cpp:872, dev=<par:psc500>, pid=139, errno=11
exClose(reason=0x3007)
ptal-mlcd: ERROR at transport/ExMlcTransport.cpp:1059, dev=<par:psc500>, pid=139, errno=11
reverseDataReceived_ts(port=0,channel=2): not open!
ptal-mlcd: ERROR at transport/ExMlcCommandChannel.cpp:1632, dev=<par:psc500>, pid=139, errno=11
sendError(port=0,MLC): error=0x07.
ptal-mlcd: ERROR at ExMgr.cpp:872, dev=<par:psc500>, pid=139, errno=11
exClose(reason=0x3007)
ptal-mlcd: ERROR at transport/ExMlcTransport.cpp:1621, dev=<par:psc500>, pid=139, errno=11
handleInitReply(port=0): ignoring extra InitReply!
ptal-mlcd: ERROR at transport/ExMlcTransport.cpp:1621, dev=<par:psc500>, pid=139, errno=11
handleInitReply(port=0): ignoring extra InitReply!
ptal-mlcd: ERROR at transport/ExMlcTransport.cpp:1621, dev=<par:psc500>, pid=139, errno=11
handleInitReply(port=0): ignoring extra InitReply!
************************************************
************************************************
************************************************
ExMgr:
gDebugFlag=0
pBufferPool: available#=10, size=4102, requested#=230, allocated#=12
initialized=1
nofork=0
activateAtStartup=0
argc=0
fd=3: r=1, w=0, x=0
fd=6: r=1, w=0, x=0
fdCount=7
exState=2
exActivateCount=6
exCloseCount=5
exCloseReason=0x3007
exReactivateFlag=0
noDot4=0
enablePmlMultiplexing=1
sleepBeforeOpen=0
tryDot4=0
tryMlc=1
miser=0
pFreeMsgPool: depth=2
pPendingMsgQueue: depth=0
pActiveTimerQueue: depth=1
pPeriodicTimerQueue: depth=1
select timeout: sec=0, usec=50000, infinite=0
consoleAllowRemote=0
consoleOldStdin=4
consoleOldStdout=5
consoleIsRemote=0
socketSuffix=<par:psc500>
socketAliasSuffix=<mlcpp0>
socketName=</dev/ptal-mlcd/par:psc500>
socketAliasName=</dev/ptal-mlcd/mlcpp0>
socketFd=3
pmlTransportSession=8
pmlCurrentSession=-1
pmlLastSession=31
sessionInWrite=0
llioName=<>
llioOverrideDeviceID=<>
llioFd=-1
llioDummyFd=-1
llioPollState=0
llioLastHitTime=991380275
llioForwardBdrQueue: depth=0
llioDeviceID=<MFG:HEWLETT-PACKARD;MDL:PSC 500;CMD:MLC,PCL,PML,SCL;CLS:PRINTER;DES:Hewlett-Packard PSC 500;CMT:OFFICEJET PRO;SERN:SGH02EGRMLWZ;VSTATUS:$HB0$FC0,ff,DN,IDLE,CUT;LSS:01;LDF:1;LDE:1;>
baseLow=0x378
baseHigh=0x778
portType=0x000
ParPort:
portType=1
debug=0
setupDelay(0)={tv_sec=0,tv_usec=100}
strobeDelay(1)={tv_sec=0,tv_usec=0}
holdDelay(2)={tv_sec=0,tv_usec=100}
ecpSetupDelay(3)={tv_sec=0,tv_usec=0}
ecpPostHtrDelay(4)={tv_sec=0,tv_usec=10000}
signalTimeout(5)={tv_sec=0,tv_usec=100000}
busyTimeout(6)={tv_sec=1,tv_usec=0}
reversePollRate(7)={tv_sec=0,tv_usec=10000}
dead=0
currentMode=0x10
currentChannel=0
htrCount=4
forwardMode=0x10
reverseMode=0x00
channel=77
status =0x7F
control =0xED
ECP config A =0x00
ECP config B =0x00
ECP control =0xE6
Transport:
this=0x08067838
port=0
pMgr=0x08066CB8
pPhysicalPort=0x08066CB8
forwardTransactionCounter: current=16, initial=16, low=15, high=16, max=16
channelCount=17
channelArray=0x08067A28
channelArray[0]=0x08067A70
channelArray[1]=0x08067D68
channelArray[2]=0x08067F68
channelArray[3]=0x08068168
channelArray[4]=0x08068368
channelArray[5]=0x08068568
channelArray[6]=0x08068768
channelArray[7]=0x08068968
channelArray[8]=0x08068B68
channelArray[9]=0x08068D68
channelArray[10]=0x08068F68
channelArray[11]=0x08069168
channelArray[12]=0x08069368
channelArray[13]=0x08069568
channelArray[14]=0x08069768
channelArray[15]=0x08069968
channelArray[16]=0x08069B68
overheadBufferCount=0
pNextTransport=0x00000000
pForwardDataTimer=0x08067900 (count=0)
pForwardDataTimeoutMsg=0x080678D0
reverseDataBufferCount=180
reverseDataBufferSize=4102
maxForwardBdrsPerTransaction=4
nextChannelToAllocate=17
nextBlockedChannel=-1
lookupQueue: depth=0, peek=0x00000000
----------------
pForwardHeaderPool=0x08067940
mlcChannelArray=0x08067A28
pCommandChannel=0x08067A70
grcState=0
reverseDataStopped=0
tryDot4=0
tryPreDot4=0
tryMlc=1
requestedRevision=0x03
revision=0x03
maxRemoteSockets=32
remsock[0]: state=2, socketID=1, fwdPS=134, revPS=134
Command channel:
this=0x08067A70
port=0
channel=0
localSocket=0
pTransport=0x08067838
pMgr=0x08066CB8
pPhysicalPort=0x08066CB8
openingAnySetFlags=0x0010
closingAnySetFlags=0x0124
flags=0x0003
countOpen=0
countOpenFailure=0
pService=0x00000000
scd=0x00000000
forwardDataPriority=0
minBuffersRequired=0
benefitOfMoreBuffers=0
reverseDataBufferSize=4102
bufferCount=3
remoteSocket=0
maxForwardDatalen=58
maxReverseDatalen=58
countForwardData=4
countReverseData=7
countReverseBuffers=7
countReverseBufferReturns=2
lastReverseBuffer=0x00000000
currentForwardBuffer=0x00000000
currentGrabbedCredit=-1
currentGrabbedTransaction=-1
----------------
pMlcTransport=0x08067838
pCommandChannel=0x08067A70
disableCreditCommands=1
pForwardCreditRequestTimer=0x08067C08
pForwardCreditRequestMsg=0x08067BD8
pReverseCreditHeartbeatTimer=0x08067C70
pReverseCreditHeartbeatMsg=0x08067C40
musherFirstCreditRequestDelay=2
musherNextCreditRequestDelay=5
gusherFirstCreditRequestDelay=5
gusherNextCreditRequestDelay=10
miserFirstCreditRequestDelay=0
miserNextCreditRequestDelay=2
gusherPiggybackCreditCount=1
gusherCreditCount=2
miserCreditRequestCount=2
workaroundReverseCreditLoss=0
maxForwardPacketSize=64
maxReversePacketSize=64
forwardCreditRequest=16
forwardMaxOutstandingCredit=1
forwardCredit: current=1, initial=1, low=0, high=1, max=65535
lastCreditRequestGotUsNowhere=0
reverseMaxOutstandingCredit=1
reverseBuffersPerPacket=1
uncreditedBuffers=0
reverseCreditToGrant=1
reverseCredit: current=1, initial=1, low=1, high=2, max=65535
countSendPiggybackCredit=4
countHandlePiggybackCredit=7
countSendCredit=0
countHandleCredit=0
countHandleCreditAfterCreditRequest=0
countSendCreditRequest=0
countHandleCreditRequest=0
countSendEmptyCreditRequestReply=0
countHandleEmptyCreditRequestReply=0
isGusher=1
----------------
pForwardCommandPool=0x08067CA8
pForwardNonconsumingQueue=0x08067CC8
pForwardReplyQueue=0x08067CD8
pForwardRequestQueue=0x08067CE8
forwardRequestCredit: current=1, initial=1, low=0, high=1, max=65535
pCommandReplyTimer=0x08067D28 (count=1)
pCommandReplyTimeoutMsg=0x08067CF8
allowErrorPackets=1
lastPsid=0
lastSsid=0
Session 0: type=command
state=4
fd=6
scdlink=9
pLookup=0x08067368
outstandingForwardBdrCount=2
pReverseBdrQueue: depth=0
tcd=0x00000000
pCommandBdr=0x080732A8
pmlTrapsRegistered=0
Session 8: type=transport
state=6
fd=-1
scdlink=-1
pLookup=0x08067668
outstandingForwardBdrCount=0
pReverseBdrQueue: depth=0
tcd=0x08067D68
pCommandBdr=0x00000000
pmlTrapsRegistered=0
Transport channel for session 8:
this=0x08067D68
port=0
channel=1
localSocket=128
pTransport=0x08067838
pMgr=0x08066CB8
pPhysicalPort=0x08066CB8
openingAnySetFlags=0x0010
closingAnySetFlags=0x0124
flags=0x0003
countOpen=1
countOpenFailure=0
pService=0x08066CB8
scd=0x00000008
forwardDataPriority=0
minBuffersRequired=10
benefitOfMoreBuffers=1
reverseDataBufferSize=4102
bufferCount=12
remoteSocket=1
maxForwardDatalen=128
maxReverseDatalen=128
countForwardData=0
countReverseData=0
countReverseBuffers=0
countReverseBufferReturns=0
lastReverseBuffer=0x00000000
currentForwardBuffer=0x00000000
currentGrabbedCredit=-1
currentGrabbedTransaction=-1
----------------
pMlcTransport=0x08067838
pCommandChannel=0x08067A70
disableCreditCommands=0
pForwardCreditRequestTimer=0x08067EC8
pForwardCreditRequestMsg=0x08067E98
pReverseCreditHeartbeatTimer=0x08067F30
pReverseCreditHeartbeatMsg=0x08067F00
musherFirstCreditRequestDelay=2
musherNextCreditRequestDelay=5
gusherFirstCreditRequestDelay=5
gusherNextCreditRequestDelay=10
miserFirstCreditRequestDelay=0
miserNextCreditRequestDelay=2
gusherPiggybackCreditCount=1
gusherCreditCount=2
miserCreditRequestCount=2
workaroundReverseCreditLoss=0
maxForwardPacketSize=134
maxReversePacketSize=134
forwardCreditRequest=16
forwardMaxOutstandingCredit=65535
forwardCredit: current=4, initial=4, low=4, high=4, max=65535
lastCreditRequestGotUsNowhere=0
reverseMaxOutstandingCredit=0
reverseBuffersPerPacket=1
uncreditedBuffers=0
reverseCreditToGrant=0
reverseCredit: current=12, initial=12, low=12, high=12, max=65535
countSendPiggybackCredit=0
countHandlePiggybackCredit=0
countSendCredit=0
countHandleCredit=0
countHandleCreditAfterCreditRequest=0
countSendCreditRequest=0
countHandleCreditRequest=0
countSendEmptyCreditRequestReply=0
countHandleEmptyCreditRequestReply=0
isGusher=-1
Session 9: type=transport
state=4
fd=-1
scdlink=0
pLookup=0x00000000
outstandingForwardBdrCount=0
pReverseBdrQueue: depth=0
tcd=0x08067F68
pCommandBdr=0x00000000
pmlTrapsRegistered=0
Transport channel for session 9:
this=0x08067F68
port=0
channel=2
localSocket=129
pTransport=0x08067838
pMgr=0x08066CB8
pPhysicalPort=0x08066CB8
openingAnySetFlags=0x0010
closingAnySetFlags=0x0124
flags=0x0001
countOpen=0
countOpenFailure=0
pService=0x08066CB8
scd=0x00000009
forwardDataPriority=0
minBuffersRequired=10
benefitOfMoreBuffers=1
reverseDataBufferSize=4102
bufferCount=11
remoteSocket=0
maxForwardDatalen=0
maxReverseDatalen=0
countForwardData=0
countReverseData=0
countReverseBuffers=0
countReverseBufferReturns=0
lastReverseBuffer=0x00000000
currentForwardBuffer=0x00000000
currentGrabbedCredit=-1
currentGrabbedTransaction=-1
----------------
pMlcTransport=0x08067838
pCommandChannel=0x08067A70
disableCreditCommands=0
pForwardCreditRequestTimer=0x080680C8
pForwardCreditRequestMsg=0x08068098
pReverseCreditHeartbeatTimer=0x08068130
pReverseCreditHeartbeatMsg=0x08068100
musherFirstCreditRequestDelay=2
musherNextCreditRequestDelay=5
gusherFirstCreditRequestDelay=5
gusherNextCreditRequestDelay=10
miserFirstCreditRequestDelay=0
miserNextCreditRequestDelay=2
gusherPiggybackCreditCount=1
gusherCreditCount=2
miserCreditRequestCount=2
workaroundReverseCreditLoss=0
maxForwardPacketSize=0
maxReversePacketSize=0
forwardCreditRequest=16
forwardMaxOutstandingCredit=65535
forwardCredit: current=0, initial=0, low=0, high=0, max=65535
lastCreditRequestGotUsNowhere=0
reverseMaxOutstandingCredit=65535
reverseBuffersPerPacket=0
uncreditedBuffers=11
reverseCreditToGrant=0
reverseCredit: current=0, initial=0, low=0, high=0, max=65535
countSendPiggybackCredit=0
countHandlePiggybackCredit=0
countSendCredit=0
countHandleCredit=0
countHandleCreditAfterCreditRequest=0
countSendCreditRequest=0
countHandleCreditRequest=0
countSendEmptyCreditRequestReply=0
countHandleEmptyCreditRequestReply=0
isGusher=-1
************************************************
ptal-mlcd: FATAL ERROR at transport/ExTransport.cpp:428, dev=<par:psc500>, pid=139, errno=11
|
|
From: <pa...@rc...> - 2001-06-01 09:18:26
|
Ben "Obi-Wan" Hollingsworth wrote:
> I did make a fresh reboot of my system & the PSC500 earlier this evening
> (before I read your message about checking the BIOS). Without checking
> anything, I printed a few pages & it worked fine. No errors in my stdout
> logs. I brought up xsane to test that. Grabbing a preview worked, but
> was dreadfully slow. Note that I'm on a P90 & at the same time I was
> listening to a RealAudio station & actively web browsing. Still, it
> seemed slower than it should have been. Attempting to scan a color image
> to disk at 150 dpi cranked away for a good long while, then flagged an
> xsane error window (something related to opening the output file)
...
> The stdout log then got gobs of output, which I've included below.
...
> ptal-mlcd: ERROR at ParPort.cpp:163, dev=<par:psc500>, pid=139, errno=11
> statusWaitSetClear(event=23) timed out!
>
> ptal-mlcd: ERROR at ExMgr.cpp:2131, dev=<par:psc500>, pid=139, errno=11
> llioService: llioForwardToReverse failed!
...
> ParPort:
> portType=1
...
> forwardMode=0x10
> reverseMode=0x00
Hi, Ben. Based on the above excerpts of your error log, I can tell that
your parallel port is not set to ECP or bidirectional ("BPP" or "PS/2").
Try it again once you get a chance to reboot and change the BIOS setting.
For now I don't think it will be necessary to mess with the debug console.
This exact same failure on the PSC 500 has been reported to me before, and
it was fixed by enabing bidirectional ECP signaling, which requires a
parallel port setting of ECP or BPP. This should also improve the speed
somewhat, with further speed improvements on my long-term TODO list.
David
|
|
From: Obi-Wan <bv...@in...> - 2002-12-22 18:39:50
|
> Hi, "Obi-Wan". I'm forwarding this to the mailing list in case anybody
> else has an idea of what's going wrong, because I'm afraid I don't.
Oops. I meant to send it there in the first place...
> It's
> strange that scanimage isn't reading dll.conf but is reading v4l.conf.
Yeah, that's what I thought.
> Is it possible that your copy of scanimage was statically linked with
> the "v4l" backend rather than the "dll" meta-backend? What is the output
> of "ldd </path/to/>scanimage"?
% ldd /usr/local/bin/scanimage
libptal.so.0 => /usr/lib/libptal.so.0 (0x40027000)
libsane.so.1 => /usr/lib/sane/libsane.so.1 (0x40034000)
libnsl.so.1 => /lib/libnsl.so.1 (0x4003b000)
libm.so.6 => /lib/libm.so.6 (0x4004e000)
libjpeg.so.62 => /usr/lib/libjpeg.so.62 (0x4006f000)
libdl.so.2 => /lib/libdl.so.2 (0x4008d000)
libc.so.6 => /lib/libc.so.6 (0x40090000)
libsnmp-0.4.2.so => /usr/lib/libsnmp-0.4.2.so (0x401a4000)
libusb-0.1.so.4 => /usr/lib/libusb-0.1.so.4 (0x401fd000)
libieee1284.so.3 => /usr/lib/libieee1284.so.3 (0x40204000)
libgphoto2.so.2 => /usr/lib/libgphoto2.so.2 (0x4020e000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
libcrypto.so.0.9.6 => /usr/lib/i686/libcrypto.so.0.9.6 (0x40286000)
libgphoto2_port.so.0 => /usr/lib/libgphoto2_port.so.0 (0x4033e000)
libltdl.so.3 => /usr/lib/libltdl.so.3 (0x40345000)
No libv4l in either scanimage or xsane.
> To answer your other question: There is no "hpoj.conf" file. libsane-hpoj
> asks libptal for a list of known PTAL devices, which is determined by the
> presence of correctly-named files in /etc/ptal which "ptal-init setup"
> creates.
In case it matters, here's what ptal-devid reports:
% ptal-devid
MFG:HEWLETT-PACKARD;MDL:PSC 500;CMD:MLC,PCL,PML,SCL;CLS:PRINTER;DES:Hewlett-Packard PSC 500;CMT:OFFICEJET PRO;SERN:SGH02EGRMLWZ;VSTATUS:$HB0$FC0,ff,DN,IDLE,CUT;LSS:01;LDF:1;LDE:1;
OK, here's something. It looks like the v4l stuff, but nothing else,
is compiled directly into libsane (dated 9 Dec 2002) in the Debian
unstable distribution:
% strings /usr/lib/sane/libsane.so.1 | grep sane
sanei_debug_v4l
sanei_debug_msg
sane_v4l_init
sanei_init_debug
sanei_config_open
sanei_config_read
sane_v4l_exit
sane_v4l_get_devices
sane_v4l_open
sane_v4l_close
sane_v4l_cancel
sane_v4l_get_option_descriptor
sane_v4l_control_option
sanei_constrain_value
sane_strstatus
sane_v4l_get_parameters
sane_v4l_start
sane_v4l_read
sane_v4l_set_io_mode
sane_v4l_get_select_fd
sane_init
sane_get_devices
sane_open
sane_get_option_descriptor
sane_control_option
sane_get_parameters
sane_start
sane_read
sane_set_io_mode
sane_get_select_fd
sane_cancel
sane_close
sane_exit
sanei_debug_sanei_debug
sanei_debug_sanei_config
sanei_config_skip_whitespace
sanei_config_get_string
libsane.so.1
sane-backends-1.0.9
sane_init: file `%s' not accessible (%s), trying /dev/video0
sane_exit: all devices freed
sane_get_devices
sane_open: devname == 0
sane_open: device %s found in devlist
sane_open: device %s doesn't seem to be a v4l device
sane_open: can't open %s (%s)
sane_open: ioctl (%d, VIDIOCGCAP,..) failed on `%s': %s
sane_open: %d channels, %d audio devices
sane_open: minwidth=%d, minheight=%d, maxwidth=%d, maxheight=%d
sane_open: V4L device can capture to memory
sane_open: V4L device has a tuner of some form
sane_open: V4L device supports teletext
sane_open: V4L device can overlay its image onto the frame buffer
sane_open: V4L device uses chromakey on overlay
sane_open: V4L device supports overlay clipping
sane_open: V4L device overwrites frame buffer memory
sane_open: V4L device supports hardware scaling
sane_open: V4L device is grey scale only
sane_open: V4L device can capture parts of the image
sane_open: can't ioctl VIDIOCGCHAN %s: %s
sane_open: channel %d (%s), tuners=%d, flags=0x%x, type=%d, norm=%d
sane_open: channel has tuner(s)
sane_open: channel has audio
sane_open: input is TV input
sane_open: input is camera input
sane_open: can't ioctl VIDIOCGPICT %s: %s
sane_open: brightness=%d, hue=%d, colour=%d, contrast=%d
sane_open: whiteness=%d, depth=%d, palette=%d
sane_open: ioctl VIDIOCSPICT failed (%s)
sane_open: can't ioctl VIDIOCGWIN %s: %s
sane_open: x=%d, y=%d, width=%d, height=%d
sane_close: trying to close handle %p
sane_close: bad handle %p
sane_get_option_descriptor: option %d (%s)
sane_control_option: %s option %d (%s)
sane_control option: option is inactive
sane_control_option: option %d unknown
sane_control_option: option is not settable
sane_control_option: sanei_constarin_value failed: %s
sane_control_option: ioctl VIDIOCGWIN failed (can not get window geometry)
sane_open: can't ioctl VIDIOCSCHAN %s: %s
sane_control_option: ioctl VIDIOCSWIN failed (%s)
sane_control_option: ioctl VIDIOCGWIN failed (%s)
sane_control_option: ioctl VIDIOCSPICT failed (%s)
sane_control_option: option can't be set automatically
sane_get_parameters
sane_get_parameters: params == 0
sane_start
sane_start: bad handle %p
sane_start: can not get capabilities
sane_start: V4L trying to read frame
sane_start: %d bytes read
sane_start: mmap frame, buffersize: %d bytes, buffers: %d, offset 0 %d
sane_start: mmap failed: %s
sane_start: mmapped frame, capture 1 pict into %p
sane_start: mmappeded frame %d x %d with palette %d
sane_start: ioctl VIDIOCMCAPTURE failed: %s
sane_start: waiting for frame %x
sane_start: call to ioctl(%d, VIDIOCSYNC, ..) failed
sane_start: frame %x done
sane_start: done
sane_read: max_len = %d
sane_read: lenp == 0
sane_read: tranfered %d bytes (from %d to %d)
sane_cancel
sanei_debug
[sanei_debug] malloc() failed
sanei_config
.:/etc/sane.d
sanei_config_open: attempting to open `%s'
sanei_config_open: using file `%s'
sanei_config_open: could not find config file `%s'
Ideas?
--
Ben "Obi-Wan" Hollingsworth ob...@je...
The stuff of earth competes for the allegiance I owe only to the
Giver of all good things, so if I stand, let me stand on the
promise that You will pull me through. -- Rich Mullins
|
|
From: Mark P. <ms...@de...> - 2002-12-29 09:53:29
|
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Ben,
On Mon, 23 Dec 2002 05:39, Obi-Wan wrote:
> > Is it possible that your copy of scanimage was statically linked with
> > the "v4l" backend rather than the "dll" meta-backend? What is the output
> > of "ldd </path/to/>scanimage"?
>
> % ldd /usr/local/bin/scanimage
> libptal.so.0 => /usr/lib/libptal.so.0 (0x40027000)
> libcrypto.so.0.9.6 => /usr/lib/i686/libcrypto.so.0.9.6 (0x40286000)
> libsnmp-0.4.2.so => /usr/lib/libsnmp-0.4.2.so (0x401a4000)
Debian scanimage isn't linked to libptal, libcrypto, libsnmp (see below)
- From the looks of above you aren't using the Debian GNU/Linux packaged version
of scanimage. But rather a locally installed version of scanimage.
(/usr/local/bin)
/usr/bin/scanimage is provided in the Debian sane-utils package which you said
you had installed.
Perhaps you could delete the extra sane files from /usr/local and try again
with the default Debian packaged versions.
I run an almost identical setup here and get good results scanning locally and
over the network.
Mark
msp@htpc:~$ scanimage -L
device `net:192.168.1.128:hpoj:mlc:par:OfficeJet' is a Hewlett-Packard
OfficeJet multi-function peripheral
msp@htpc:~/src/debian$ ssh lc
msp@bravo-lc:~$ scanimage -L
device `hpoj:mlc:par:OfficeJet' is a Hewlett-Packard OfficeJet multi-function
peripheral
msp@htpc:~$ ldd /usr/bin/scanimage
libsane.so.1 => /usr/lib/libsane.so.1 (0x4001f000)
libm.so.6 => /lib/libm.so.6 (0x40026000)
libnsl.so.1 => /lib/libnsl.so.1 (0x40047000)
libusb-0.1.so.4 => /usr/lib/libusb-0.1.so.4 (0x4005a000)
libjpeg.so.62 => /usr/lib/libjpeg.so.62 (0x40061000)
libieee1284.so.3 => /usr/lib/libieee1284.so.3 (0x4007f000)
libgphoto2.so.2 => /usr/lib/libgphoto2.so.2 (0x40089000)
libgphoto2_port.so.0 => /usr/lib/libgphoto2_port.so.0 (0x40103000)
libltdl.so.3 => /usr/lib/libltdl.so.3 (0x40109000)
libdl.so.2 => /lib/libdl.so.2 (0x4010f000)
libc.so.6 => /lib/libc.so.6 (0x40112000)
libexif.so.7 => /usr/lib/libexif.so.7 (0x40222000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+DsXQoCzanz0IthIRAo8OAJ44auFfrAZHQvkEQgEjMekl7FDWbwCfZN/I
a+t4pgkqJu6ExV/ojDsGXJ0=
=hhBz
-----END PGP SIGNATURE-----
|
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X