Re: [hpoj-devel] preparing for 0.7

[Joe P. <joe...@sn...>]

On Saturday 09 December 2000 21:31, David Paschal wrote:
> Hi,
>
> I've checked into CVS all of the code changes that I needed to make and
> that others have sent me, so I'm close to being ready to release 0.7.
>
> I would like to wait a few more days to see if we can resolve the problem
> Robert reported about printing on 2.2.16-SMP, since 0.7 is supposed to fix
> problems like this.  If it turns out that upgrading to 2.2.17 fixes the
> problem, then maybe I'll just document the issue and release if there isn't
> an easy fix.  My goal is to release this by next weekend if possible.
>
> In the meantime, it would be appreciated if some people could try out the
> latest CVS source and let me know if there are any problems, particularly
> with the new PRINT-HOWTO, xojpanel, or changes to the kernel-mode drivers.
> Those who have already downloaded from CVS and applied patches may need to
> delete the modified trees and download a fresh copy, because the "cvs
> update" command may get confused when it's trying to merge updates into
> locally modified files.  For convenience I added links to the CVS homepage
> (http://www.cvshome.org), where one can learn more about using CVS.
>
> I will also try to test with 2.4.0-test on a uniprocessor PC to see if I
> can reproduce the slow-scan problem that was previously reported.  If
> anybody else can confirm that that is or isn't a problem, that would be
> nice too.
>
> David

David:

I didn't have any problems with the build or install of the project from CVS. 

Printing still works ok.
The PRINT-HOWTO looks as I expected it to.

The xojpanel "start failures" still occur. I tried connecting the OfficeJet 
to the MB-based port instead of the IO card, but there was no improvement. 
Rebooting or reinserting the ieee12844 modules has no effect either.

The cause of the problem seems to have been introduced after hpoj-0.5. As a 
test, I inserted the ieee12844 modules from the 0.5 release. The no-start 
problem then disappeared. In /var/log/messages (using debug=1), lines 
containing "Got device ID string" are definitely related to the problem.  One 
such message occurs for each failure to execute.     

-- 
Joe