Re: [hpoj-devel] Problem with hpoj /w SMP and USB?

[Dr. A. S. <And...@Dr...>]

Hi,

thanks for your help! To close this matter:=20

I didn't pay enough attention to the release: SuSE 9.0 ships with hpoj 0.90=
,=20
which leads to the problems described. After installing 0.91 everything wor=
ks=20
pretty fine (printing and scanning; I haven't tried to send a fax yet).

Yours sincerely

Andreas Schenk

Am Mittwoch, 3. M=E4rz 2004 20:45 schrieb Crosland, Jerel:
> I had the same problem, only my printer is the multi-function GX85, also =
on
> the USB port. I have a dual-CPU box where I installed SuSE 9.0 and have
> been (so-far) unable to get printing to work. In reading the support pages
> for hpoj I found that I needed to install the 0.91 version of the package.
> I did that (manually, from source, because binaries for SuSE 9.0 were not
> yet available) and the ptal setup ran fine this time. It noticed that I h=
ad
> the printer module activated in the kernel, with a USB printer and SMP and
> it offered to turn it off for me, which I told it to do. All tests from t=
he
> command line worked fine then. My problem came when I tried to go into Ya=
st
> to configure the printer queue etc. and Yast could not find things. I
> posted a message here, and recieved the following responses, which I have
> not yet had a chance to test out:
>
> From Laurence Keefe:
>
> 	When you installed version .91 of hpoj, where did things end up?  Are
> ptal-init, ptal-mlcd, and ptal-printd all in /usr/sbin?  That is where Su=
SE
> expects to find them, along with ptal-cups and ptal-photod.
>
> 	Does SuSE say that CUPS will not run with an SMP kernel?  If it does run
> then you don't want to use YAST anyway to set up the printing, or so the
> hpoj documentation says.  I successfully set up my OfficeJet V40 to print
> and scan using the CUPS web interface.
>
> And from Cory Meisch:
>
> Using YaST be sure that CUPS and HPOJ are setup up to start on runlevels
> 3 and 5. Then, use the web interface http://localhost:631 to setup your
> device.
>
> Cory
> hp linux printing team
>
> Jerel Crosland
> Technical Specialist
>  818/704-3187
>
> Bug: Small living things that small living boys throw on small living
> girls.
>
>
> -----Original Message-----
> From: hpo...@li...
> [mailto:hpo...@li...]On Behalf Of James B.
> Hiller
> Sent: Tuesday, March 02, 2004 3:07 PM
> To: Dr. Andreas Schenk
> Cc: hpo...@li...
> Subject: Re: [hpoj-devel] Problem with hpoj /w SMP and USB?
>
>
> Hi.
>
> Thanks for all the detail.  I hope others will jump in, because I'm not
> real familiar with a lot of the things that you have, and I'm not at
> all familiar with the track record of hpoj with the types of printers
> you're using.  (Implied:  maybe there could be some problems with
> those types of printers - is hpoj known to and intended to work ok
> with LaserJets?)
>
> > My software: SuSE Linux 9.0 installed on the workstation. No other
> > operating system besides that. Kernel: 2.4.21-99-smp4G. I guess the smp
> > stands for > symmetric multi-processor. I don't know exactely what it
> > means, but I guess, it should work with a hyperthreading CPU.
>
> Right.  SMP is Symmetric Multi Processing.  There's a very good, just a
> little old, SMP-HOWTO for linux that is well worth the read.  It explains=
 a
> lot about the capability in its different flavors, ways to make use of it,
> and a lot more.  It also has links to the Linux Parallel Processing HOWTO
> and a few other very good docs, all of which you would likely enjoy.
>
> The canonical URL for the SMP HOWTO is:
>
> http://www.tldp.org/HOWTO/SMP-HOWTO.html
>
> Note that there is a link to the maintainer's site, and in fact there is
> a slightly newer, better version there.
>
> The SMP HOWTO briefly mentions hyperthreading, as well as general hardware
> issues across a number of platforms, so you may gain some insight as to
> whether you have other latent issues to contend with.  But again, the
> document is 18 months old, so you'll probably get better general info on
> hyperthreading from other sources.
>
> > So I read the troubleshooting guide and found the problem "I have
> > an SMP system, and I experience kernel OOPSes or complete system lockups
> > when using USB".
>
> According to the original hpoj maintainer, David Paschal, the linux SMP/U=
SB
> bug was in principle fixed with the linux 2.6 series (which implies
> somewhere in the 2.5 development series as well).  However, he didn't have
> the opportunity to do comprehensive hpoj-related testing, so he couldn't
> attest to the veracity of the fix or 2nd/3rd order regression.  Worth
> keeping in mind.
>
> He has also previously told me that there was never an issue with SMP and
> parallel port hpoj, though on occasion someone would say, or imply, on
> the list that they were having such troubles.  I know this myself to be
> true, as I've been running hpoj/parallel port and an SMP box for a Very
> Long Time (since before hpoj actually did anything) (both Intel and AMD
> flavors). And also, though you didn't ask - the issue does not come up
> simply because one has USB configured and running in an SMP kernel.  It's
> only when you're attempting to use hpoj with USB that the problem
> manifests.  (I say this because there has been traffic on the list from
> time to time asserting otherwise, but those folks were misunderstanding t=
he
> issue at the time).
>
> Aside from all that - you'd probably benefit from upgrading the kernel if
> you don't have other major dependencies on 2.4.21.  There might even be
> some "improvement" in the SMP bug in the later 2.4-series kernels; I seem
> to recall some assertions of that on this mailing list.  If I remember
> right, it would be at least 2.4.23 to get to.  But I'll stress that I'm
> not certain of the accuracy of this conjecture, so even better would be
> to just go with latest (2.6.3, almost .4 now).
>
> > I tried to reboot with the nosmp kermel option. This didn't work, the
> > system didn't boot with this option. (I wonder why). Then I disabled
> > hyperthreading in the BIOS setup. As a result, hpoj worked pretty fine.
> > After I enabled > hyperthreading again in the BIOS setup, the system
> > locked up again. So I > guess, I have the cited problem.
>
> Seems like it.
>
> > What can I do now (besides throwing away something)?
>
> Rather than throwing anything away, you might consider just going with
> parallel-port-only for the moment, either with the one parallel port
> printer that you have, or even better, with that one and one borrowed
> from a friend (and a $10 PCI parallel port card if you need one).
> This way you could remove the USB issue from the mix and make sure you're
> not having other problems not at all related to it (seems like you could
> be).  Then you might be able to roll in hpoj with USB in a controlled
> way and see what happens.
>
> Hope some of this helps.
>
> jbh
>
>
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> Build and deploy apps & Web services for Linux with
> a free DVD software kit from IBM. Click Now!
> http://ads.osdn.com/?ad_id=3D1356&alloc_id=3D3438&op=3Dclick
>
> _______________________________________________
> hpoj-devel mailing list
> hpo...@li...
> https://lists.sourceforge.net/lists/listinfo/hpoj-devel
>
>
> ***********************************************************************
> This e-mail and any files transmitted with it are intended
> solely for the use of the addressee.  This e-mail may
> contain confidential and/or legally privileged information.
> Any review, transmission, disclosure, copying, or any action
> taken or not taken, by other than the intended recipient, in
> reliance on the information, is prohibited.  If you received
> this e-mail in error, notify the sender and delete this e-mail
> (and any accompanying material) from your computer and
> network. In addition, please be advised that 21st Century
> Insurance Group reserves the right to monitor, access and
> review all messages, data and images transmitted through
> our electronic mail system. By using our e-mail system, you
> consent to this monitoring.
> ***********************************************************************