You can subscribe to this list here.
2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(6) |
Sep
(111) |
Oct
(63) |
Nov
(64) |
Dec
(116) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
(49) |
Feb
(27) |
Mar
(136) |
Apr
(59) |
May
(122) |
Jun
(72) |
Jul
(167) |
Aug
(77) |
Sep
(103) |
Oct
(128) |
Nov
(86) |
Dec
(87) |
2002 |
Jan
(150) |
Feb
(111) |
Mar
(112) |
Apr
(139) |
May
(204) |
Jun
(228) |
Jul
(202) |
Aug
(244) |
Sep
(215) |
Oct
(311) |
Nov
(127) |
Dec
(229) |
2003 |
Jan
(252) |
Feb
(119) |
Mar
(163) |
Apr
(166) |
May
(91) |
Jun
(84) |
Jul
(106) |
Aug
(98) |
Sep
(93) |
Oct
(161) |
Nov
(82) |
Dec
(62) |
2004 |
Jan
(58) |
Feb
(44) |
Mar
(56) |
Apr
(67) |
May
(50) |
Jun
(57) |
Jul
(20) |
Aug
(25) |
Sep
(33) |
Oct
(35) |
Nov
(61) |
Dec
(95) |
2005 |
Jan
(61) |
Feb
(31) |
Mar
(17) |
Apr
(10) |
May
(2) |
Jun
(13) |
Jul
(4) |
Aug
(10) |
Sep
(9) |
Oct
(33) |
Nov
(2) |
Dec
(7) |
2006 |
Jan
(11) |
Feb
(3) |
Mar
(3) |
Apr
(8) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2007 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
From: Cory M. <cor...@hp...> - 2004-04-20 17:26:36
|
How slow is slow? 1 page per minute? 3 pages? Please also check your CUPS queue using http://localhost:631 and tell me what the settings are... Cory hp linux printing team On Tue, 2004-04-20 at 08:05, Alexandre Thieme Reis wrote: > Greeting from Brasil, > > my HPPSC1210 work ok (print and scan), but in Linux print slow (very > slow). In windows print fast (very fast). > The configuration for Linux and Windows is the same: Draft. > > My software : > Fedora Core 1.0 with all updates > hpoj 0.91 > hpijs 1.5 > > Hardware: > Athlon 1.4 MHz. > HPPSC1210 connected via usb > > Somebody can help me? > > Alexandre. > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > > _______________________________________________ > hpoj-devel mailing list > hpo...@li... > https://lists.sourceforge.net/lists/listinfo/hpoj-devel -- Cory Meisch <cor...@hp...> HP Vancouver Linux Printing Team (360) 212-7009 |
From: Cory M. <cor...@hp...> - 2004-04-20 17:21:38
|
Please check out the documentaion at http://hpoj.sourceforge.net/hpoj-0.91/doc/index.html If you notice, there is only partial support for FreeBSD. Please follow the troubleshooting steps outlined there for your particular distribution. Cory hp linux printing team On Tue, 2004-04-20 at 09:43, Raphael Langerhorst wrote: > > hpoj.sf.net has no news since november. hpijs (which was said > > to take the development) does not either speak of hpoj. > > > > Shoul I consider that hpoj is dead and that I should try replacing my > > PSC 750 by another brand than HP ? Or could I hope to see some *BSD > > support in a near future (especially with the new USB drivers in > > FreeBSD) ? > > I would also like to see _just_ this happen. > > As I posted a week ago I have a PSC 1210 (with USB) which worked fine > (printing AND scanning) in Linux and now on FreeBSD (5.2.1) hpoj simply > doesn't recognise the device anymore (ptal-init setup). I tried it with > latest CVS, 4 days ago or so. > > Regards, > Raphael > > PS: and latest cups, latest foomatic*, latest hpijs (1.6) > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > > _______________________________________________ > hpoj-devel mailing list > hpo...@li... > https://lists.sourceforge.net/lists/listinfo/hpoj-devel -- Cory Meisch <cor...@hp...> HP Vancouver Linux Printing Team (360) 212-7009 |
From: Raphael L. <rap...@gm...> - 2004-04-20 16:44:48
|
> hpoj.sf.net has no news since november. hpijs (which was said > to take the development) does not either speak of hpoj. > > Shoul I consider that hpoj is dead and that I should try replacing my > PSC 750 by another brand than HP ? Or could I hope to see some *BSD > support in a near future (especially with the new USB drivers in > FreeBSD) ? I would also like to see _just_ this happen. As I posted a week ago I have a PSC 1210 (with USB) which worked fine (printing AND scanning) in Linux and now on FreeBSD (5.2.1) hpoj simply doesn't recognise the device anymore (ptal-init setup). I tried it with latest CVS, 4 days ago or so. Regards, Raphael PS: and latest cups, latest foomatic*, latest hpijs (1.6) |
From: Alexandre T. R. <th...@pp...> - 2004-04-20 15:05:50
|
Greeting from Brasil, my HPPSC1210 work ok (print and scan), but in Linux print slow (very slow). In windows print fast (very fast). The configuration for Linux and Windows is the same: Draft. My software : Fedora Core 1.0 with all updates hpoj 0.91 hpijs 1.5 Hardware: Athlon 1.4 MHz. HPPSC1210 connected via usb Somebody can help me? Alexandre. |
From: Erwan D. <er...@ra...> - 2004-04-19 14:04:08
|
hpoj.sf.net has no news since november. hpijs (which was said to take the development) does not either speak of hpoj. Shoul I consider that hpoj is dead and that I should try replacing my PSC 750 by another brand than HP ? Or could I hope to see some *BSD support in a near future (especially with the new USB drivers in FreeBSD) ? -- Erwan |
From: Laurence O. <lau...@or...> - 2004-04-18 22:30:16
|
Hi All I am trying to get a copy of the PML Objects Specification. I have got the PML Protocol Spec from the HP site, but it doesn't give the oids for different functions/commands. I realise that most printers only use a subset of the oids, but I would like a list so I can check out my printers. Ultimately I want to extend the pml-hp command to be able to get more info from the printer, such as inkjet cartridge levels, color saturations etc and also to be able to issue various commands such as align cartridge, clean heads, change ink saturation etc. I have the source of XOJpanel and pml-hp. I think xojpanel is too complecated using QT and having all the commands enbedded. If the pml-hp command could be extended there should bee no reason not to use it to handle the communication to the printer and QT or even HTML to display the data / accept input. Laurence orchard |
From: Phil C. <pb...@in...> - 2004-04-18 16:16:31
|
By following a suggestion from Joshua Pinter, I fixed this problem by installing libusb 0.1.7 instead of libusb 0.1.8. Everything compiled and linked fine with 0.1.7. > -----Original Message----- > From: hpo...@li... > [mailto:hpo...@li...] On Behalf Of > Joe Piolunek > Sent: Wednesday, April 14, 2004 4:18 PM > To: hpo...@li... > Subject: Re: [hpoj-devel] Make install - undefined reference > to `usb_init' > > On Wednesday 14 April 2004 11:36, Phil Clay wrote: > > > From the output you posted, it looks like ExMgr.cpp compiled > > > without errors, > > > but can not be linked. In case 'ldconfig' was not rerun after > > > installing > > > libusb, try running it again. If you installed libusb into > > > /usr/local/lib or > > > some directory tree other than /usr, try adding the > library location > > > to /etc/ld.so.conf, then run ldconfig afterward. > > > > > > > > > -- > > > Joe > > > > Thanks for helping me on this. Unfortunately, after > running ldconfig, it > > still does not link. I even rebooted just for fun. I > installed libusb > > into /usr/local/lib, and that is definitely in > /etc/ld.so.conf, so I'm not > > sure what's going on. > > > > What files specifically is it looking for when it links? I > should verify > > that they are available. > > I'm not sure, but I think ld will be looking for libusb.so, > which should be a > symlink to the actual shared library file you have. > > On my system (FC1): > > ls -l /usr/lib/libusb* > <...> > /usr/lib/libusb.so -> libusb-0.1.so.4.3.0 > > > > > Any other ideas? > > In the hpoj-0.91 directory, try running the ./configure > script again after > running "make distclean". Rerun ./configure with the option > "--with-libusb=/usr/local" (without the quotes). Adding that > configure > option should result in a g++ linking command that looks > something like this: > > g++ -L/usr/local/lib -lusb -o ptal-mlcd ExMgr.o ParPort.o > transport/ExTransport.o transport/ExMlcTransport.o > transport/ExMlcCommandChannel.o > > As a last resort, you could try adding symlinks in /usr/lib > and /usr/include > that point to your libusb and usb.h respectively. > > -- > Joe > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > > _______________________________________________ > hpoj-devel mailing list > hpo...@li... > https://lists.sourceforge.net/lists/listinfo/hpoj-devel > |
From: Cory M. <cor...@hp...> - 2004-04-16 19:40:33
|
Hi, This could be a couple of issues... One is, any printmode other than grayscale will give you mixed color printing. hpijs-1.6 partially addresses this issue. Cleaning the heads will help. Also, you might want to use the GPL'd ghostscript... cory hp linux printing team On Thu, 2004-04-15 at 12:35, James H. Cloos Jr. wrote: > I am printing to a oj d using cups-1.1.20, hpijs-1.5, hpoj-0.91 via > tcp/9100 to the printer's jd card. gs is afpl 8.13. > > I tmay not be relevant, but the printer was off for a month or so > waiting for new ink. > > Now, all black text has a cyan underprint about 0.2 mm below and > either to the rt or lt depending, I think, on which direction the > printhead was moving at the time. > > THe kludge around it is to specify grayscale rather than colour > in xpp (or similar), but black used to be just black. > > Or is this related to the new Krgb mode for the ijs driver? > > -JimC > > > -- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > > _______________________________________________ > hpoj-devel mailing list > hpo...@li... > https://lists.sourceforge.net/lists/listinfo/hpoj-devel -- Cory Meisch <cor...@hp...> HP Vancouver Linux Printing Team (360) 212-7009 |
From: Troy Leveille-dit-T. <cap...@co...> - 2004-04-16 07:48:25
|
I just noticed that konqueror on kde uses mtools in the floppy kio-slave, could this be adapted into a hpoj kio-slave since it uses mtools to access flash cards? -- -Troy Joseph Leveille-dit-Truchon |
From: James H. C. Jr. <cl...@jh...> - 2004-04-15 19:35:42
|
I am printing to a oj d using cups-1.1.20, hpijs-1.5, hpoj-0.91 via tcp/9100 to the printer's jd card. gs is afpl 8.13. I tmay not be relevant, but the printer was off for a month or so waiting for new ink. Now, all black text has a cyan underprint about 0.2 mm below and either to the rt or lt depending, I think, on which direction the printhead was moving at the time. THe kludge around it is to specify grayscale rather than colour in xpp (or similar), but black used to be just black. Or is this related to the new Krgb mode for the ijs driver? -JimC |
From: Joe P. <joe...@sn...> - 2004-04-14 20:18:10
|
On Wednesday 14 April 2004 11:36, Phil Clay wrote: > > From the output you posted, it looks like ExMgr.cpp compiled > > without errors, > > but can not be linked. In case 'ldconfig' was not rerun after > > installing > > libusb, try running it again. If you installed libusb into > > /usr/local/lib or > > some directory tree other than /usr, try adding the library location > > to /etc/ld.so.conf, then run ldconfig afterward. > > > > > > -- > > Joe > > Thanks for helping me on this. Unfortunately, after running ldconfig, it > still does not link. I even rebooted just for fun. I installed libusb > into /usr/local/lib, and that is definitely in /etc/ld.so.conf, so I'm not > sure what's going on. > > What files specifically is it looking for when it links? I should verify > that they are available. I'm not sure, but I think ld will be looking for libusb.so, which should be a symlink to the actual shared library file you have. On my system (FC1): ls -l /usr/lib/libusb* <...> /usr/lib/libusb.so -> libusb-0.1.so.4.3.0 > Any other ideas? In the hpoj-0.91 directory, try running the ./configure script again after running "make distclean". Rerun ./configure with the option "--with-libusb=/usr/local" (without the quotes). Adding that configure option should result in a g++ linking command that looks something like this: g++ -L/usr/local/lib -lusb -o ptal-mlcd ExMgr.o ParPort.o transport/ExTransport.o transport/ExMlcTransport.o transport/ExMlcCommandChannel.o As a last resort, you could try adding symlinks in /usr/lib and /usr/include that point to your libusb and usb.h respectively. -- Joe |
From: upscope <rus...@ce...> - 2004-04-14 17:09:39
|
I welcome your link to the usb printer issue. I have an HP G55 which the article covers. I have not be able to get it to print even thought the print manager says it printed successfully. I will go thru the referenced document and see if that covers my problem I'm using SuSE 9.0 personal edition. The atricle does mention the G55. Thanks for your info which may solve my problem. My parellel printer works fine. "Johannes Meixner" <js...@su...> wrote in message news:Pin...@wo...... > > Hello, > > On Apr 13 20:44 Bayard R. Coolidge wrote (shortened): > > > > #!/bin/bash > > /etc/init.d/cups stop > > /etc/init.d/ptal-init stop > > /etc/init.d/ptal-init start > > /etc/init.d/cups start > > > > Yes, it's ugly, but it does the trick. I suspect that the problem is > > that the initialization needs to be done in a specific order, and that > > the hotplug scripts need to be run before the ptal-init and cups startup > > scripts during initialization. > > See > http://portal.suse.com/sdb/en/2002/05/ke_hp-officejet.html > -------------------------------------------------------------------------- > The PTAL service must be started after the USB system and before the > print service (cupsd or lpd), since the PTAL service requires the > USB device files /dev/usb/lp* and the printing system requires the > PTAL device files. > -------------------------------------------------------------------------- > > Therefore you may enlarge your script to something like > > #!/bin/bash > /etc/init.d/cups stop > /etc/init.d/ptal-init stop > /etc/init.d/hotplug stop > /etc/init.d/hotplug start > /etc/init.d/ptal-init start > /etc/init.d/cups start > > but only if you don't have an imoprtant USB device e.g. an USB keyboard > because "/etc/init.d/hotplug stop" may disable the USB keyboard. > > > > BTW, if you don't restart cups and ptal as I do in the script and you > > queue a document for printing first, you'll not only have to run this > > script, but also go into http://localhost:631/ and Manage Printers to > > restart your printer. > > See > http://portal.suse.com/sdb/en/2002/05/ke_hp-officejet.html > > > > I'm also finding that I have to restart the print queue using localhost:631 > > after every document that I print anyway. So, there is clearly a problem > > with what CUPS is being told or is trying to cope with. > > Of course it is clearly not a problem in CUPS but > - either a problem with the ptal backend > - or a problem with the ptal backend and the particular printer > - or a general USB problem (perhaps only on the particular computer > or only with the particular printer and the particular computer). > > It depends on the particular backend whether or not it gives up or retries. > If a backend finishes with non-zero exit code then the cupsd must disable > the queue. > > This is perfectly o.k. because it is the backend (and only the backend) > which can and must decide whether or not to retry or to tell the cupsd > that it had finally failed. > > It doesn't make sense when a backend gives up with zero exit code > because this indicates that the job was successfully sent to the > printer (i.e. the cupsd would remove the job from the spool). > > It doesn't make sense when the cupsd doesn't disable the queue > when a backend results a non-zero exit code because why should > it work to start with a new job or the same job again. > > The only way which makes sense is that > 1. cupsd disables the queue, > 2. the user will see (via lpstst or CUPS web interface) that > there is a severe problem with the queue, > 3. the user will inform the administrator, > 4. the administrator will see (e.g. /var/log/cups/error_log) > that it is impossible to send data to the printer, > 5. the administrator will fix what has caused the problem, > 6. the administrator will re-enable the queue. > 7. cupsd will re-send the job > > I think that it may be a nice feature to have additional parameters > for all backends regarding timeout and retries. > > For example something like > lpd://server/name?timeout=30+retries=0 > to do endless retries. > > For example it may make sense to be able to specify something like > socket://host:port?timeout=60+retries=1440 > to disable the queue when there is no connection possible within 24 hours. > > At the moment the lpd backend has a timeout parameter > (see for example http://www.cups.org/sam.html#LPD_OPTIONS) > but no parameter regarding the number of retries. > > > Regards > Johannes Meixner > -- > SUSE LINUX AG, Maxfeldstrasse 5 Mail: js...@su... > 90409 Nuernberg, Germany WWW: http://www.suse.de/ > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click |
From: Martin S. <ma...@m-...> - 2004-04-14 16:26:31
|
> The PTAL service must be started after the USB system and before the I'm not using any USB device, so no USB system is started |
From: Phil C. <pb...@in...> - 2004-04-14 15:36:50
|
> > From the output you posted, it looks like ExMgr.cpp compiled > without errors, > but can not be linked. In case 'ldconfig' was not rerun after > installing > libusb, try running it again. If you installed libusb into > /usr/local/lib or > some directory tree other than /usr, try adding the library location > to /etc/ld.so.conf, then run ldconfig afterward. > > > -- > Joe > Thanks for helping me on this. Unfortunately, after running ldconfig, it still does not link. I even rebooted just for fun. I installed libusb into /usr/local/lib, and that is definitely in /etc/ld.so.conf, so I'm not sure what's going on. What files specifically is it looking for when it links? I should verify that they are available. Any other ideas? Phil |
From: Joe P. <joe...@sn...> - 2004-04-14 12:53:50
|
On Tuesday 13 April 2004 10:56, Phil Clay wrote: > Sorry, should have given more info... > > Redhat 7.1 > > Kernel 2.4.7-10 > > I installed libusb 0.1.8 from source (not rpms). =A0I used the default > configuration and everything worked fine. =46rom the output you posted, it looks like ExMgr.cpp compiled without erro= rs,=20 but can not be linked. In case 'ldconfig' was not rerun after installing=20 libusb, try running it again. If you installed libusb into /usr/local/lib o= r=20 some directory tree other than /usr, try adding the library location=20 to /etc/ld.so.conf, then run ldconfig afterward. =2D-=20 Joe |
From: Matteo <qua...@ya...> - 2004-04-14 10:00:56
|
Hi everyone, I'm trying to get my OJ5510 working on my Asus L3s laptop, now I'm running Slackware 9.1 with 2.4.25+ck patch kernel (pci=assign-busses passed to the kernel via LILO to get pcmcia working), I used your sw and everything seems ok, but when I try to print a test page with CUPS web interface (localhost:631) I get no print and CUPS tells me that everyting is ok :-( Can you help me? Thanks Matteo |
From: Johannes M. <js...@su...> - 2004-04-14 08:17:13
|
Hello, On Apr 13 20:44 Bayard R. Coolidge wrote (shortened): > > #!/bin/bash > /etc/init.d/cups stop > /etc/init.d/ptal-init stop > /etc/init.d/ptal-init start > /etc/init.d/cups start > > Yes, it's ugly, but it does the trick. I suspect that the problem is > that the initialization needs to be done in a specific order, and that > the hotplug scripts need to be run before the ptal-init and cups startup > scripts during initialization. See http://portal.suse.com/sdb/en/2002/05/ke_hp-officejet.html -------------------------------------------------------------------------- The PTAL service must be started after the USB system and before the print service (cupsd or lpd), since the PTAL service requires the USB device files /dev/usb/lp* and the printing system requires the PTAL device files. -------------------------------------------------------------------------- Therefore you may enlarge your script to something like #!/bin/bash /etc/init.d/cups stop /etc/init.d/ptal-init stop /etc/init.d/hotplug stop /etc/init.d/hotplug start /etc/init.d/ptal-init start /etc/init.d/cups start but only if you don't have an imoprtant USB device e.g. an USB keyboard because "/etc/init.d/hotplug stop" may disable the USB keyboard. > BTW, if you don't restart cups and ptal as I do in the script and you > queue a document for printing first, you'll not only have to run this > script, but also go into http://localhost:631/ and Manage Printers to > restart your printer. See http://portal.suse.com/sdb/en/2002/05/ke_hp-officejet.html > I'm also finding that I have to restart the print queue using localhost:631 > after every document that I print anyway. So, there is clearly a problem > with what CUPS is being told or is trying to cope with. Of course it is clearly not a problem in CUPS but - either a problem with the ptal backend - or a problem with the ptal backend and the particular printer - or a general USB problem (perhaps only on the particular computer or only with the particular printer and the particular computer). It depends on the particular backend whether or not it gives up or retries. If a backend finishes with non-zero exit code then the cupsd must disable the queue. This is perfectly o.k. because it is the backend (and only the backend) which can and must decide whether or not to retry or to tell the cupsd that it had finally failed. It doesn't make sense when a backend gives up with zero exit code because this indicates that the job was successfully sent to the printer (i.e. the cupsd would remove the job from the spool). It doesn't make sense when the cupsd doesn't disable the queue when a backend results a non-zero exit code because why should it work to start with a new job or the same job again. The only way which makes sense is that 1. cupsd disables the queue, 2. the user will see (via lpstst or CUPS web interface) that there is a severe problem with the queue, 3. the user will inform the administrator, 4. the administrator will see (e.g. /var/log/cups/error_log) that it is impossible to send data to the printer, 5. the administrator will fix what has caused the problem, 6. the administrator will re-enable the queue. 7. cupsd will re-send the job I think that it may be a nice feature to have additional parameters for all backends regarding timeout and retries. For example something like lpd://server/name?timeout=30+retries=0 to do endless retries. For example it may make sense to be able to specify something like socket://host:port?timeout=60+retries=1440 to disable the queue when there is no connection possible within 24 hours. At the moment the lpd backend has a timeout parameter (see for example http://www.cups.org/sam.html#LPD_OPTIONS) but no parameter regarding the number of retries. Regards Johannes Meixner -- SUSE LINUX AG, Maxfeldstrasse 5 Mail: js...@su... 90409 Nuernberg, Germany WWW: http://www.suse.de/ |
From: Martin S. <ma...@m-...> - 2004-04-14 08:12:40
|
Thanks for your help, but even with your script I don't get ptal-init started. I even don't get any error messages and their is nothing in /var/log/messages. |
From: Raphael L. <rap...@gm...> - 2004-04-14 04:59:59
|
Hi all, first: I'm sorry if this problem was already discussed on the list. second: greetings to all, this is my first post. third: thanks for all your work problem description: About two months ago I got a PSC 1210 and installed this thing on Linux, all worked fine without any problems, I was really happy about that :) because I didn't have time to find out if the device would work with Linux before I bought it. Recently I installed FreeBSD 5.2.1, hpoj didn't compile out of the box (CVS version after 0.91, some weeks/months ago probably). I tweaked some system(!!) headers to get it compile and when I run ptal-setup with the device attached (syslog tells me that the device IS attached) it doesn't autodetect the device. A manual entry in the ptal config directory doesn't do the trick either - I get a device not found error by mlcd. Neither printing (?) nor scanning works. I wonder why even printing doesn't work but this might be due to older hpijs drivers than I had in Linux, I'll probably soon update those. (I use CUPS - or "try" to *g*). I am not sitting at this machine right now so I can't give you details now. Also it might be that the combination (FreeBSD, PSC 1210 and USB) is a known issue and you don't need all the details. If there is no known solution and you would like to have more details I'll be happy to provide these. As much as time allows I would like to help solve it, as I have programming skills - but not much knowledge about FreeBSD internals yet. Thanks, Raphael |
From: Phil C. <pb...@in...> - 2004-04-14 02:56:40
|
Sorry, should have given more info... Redhat 7.1 Kernel 2.4.7-10 I installed libusb 0.1.8 from source (not rpms). I used the default configuration and everything worked fine. I am installing hpoj 0.91 from source (not rpms). I used the --with-usb=libusb configuration param. I did not have an older version of libusb or hpoj installed. I am trying to print to a hp 3380 (which is the replacement for the 3330 which is listed on the compatible printers). I tried to not use libusb, but it did not find the printer when running ptal-init setup, so I am now trying to get it to work with libusb. Thanks for your help! Phil > > > You haven't given any information about your distribution. > Assuming it is > RPM-based and your libusb is installed as an RPM instead of > source, you may > be missing the development package for libusb. Depending on > your distro, the > package may be named something like "libusb-devel" . > > Also make sure you don't have any part of an older version of > hpoj installed. > > -- > Joe > > |
From: Bayard R. C. <n1...@co...> - 2004-04-14 00:39:19
|
"Martin Schaller" <ma...@m-...> wrote: >>> I'm running Redhat 9 and hpoj 0.91. My HP OfficeJet 1150C was detected and >>> configured with "ptal-init setup". But ptal-init doesn't start with the >>> command "ptal-init start" (under root). Even if I stop CUPS or start >>> ptal-init at boot. I'm running SuSE 9.0 and hpoj 0.91 with a USB HP PSC 2410xi, and have similar symptoms. As a temporary measure, I run the following horrific script as root (using the 'su' command) in an xterm window when logged in as an ordinary user: #!/bin/bash /etc/init.d/cups stop /etc/init.d/ptal-init stop /etc/init.d/ptal-init start /etc/init.d/cups start Yes, it's ugly, but it does the trick. I suspect that the problem is that the initialization needs to be done in a specific order, and that the hotplug scripts need to be run before the ptal-init and cups startup scripts during initialization. However, I haven't had the time to tinker with it yet. BTW, if you don't restart cups and ptal as I do in the script and you queue a document for printing first, you'll not only have to run this script, but also go into http://localhost:631/ and Manage Printers to restart your printer. I'm also finding that I have to restart the print queue using localhost:631 after every document that I print anyway. So, there is clearly a problem with what CUPS is being told or is trying to cope with. I have a duplexer on my printer, but I don't believe that that affects my problem. HTH, Bayard, N1HO |
From: Joe P. <joe...@sn...> - 2004-04-13 23:37:22
|
On Monday 12 April 2004 11:09, Phil Clay wrote: > I'm having a problem installing hpoj 0.91 on Linux. > > I have installed libusb 0.1.8. > > When running ./configure for hpoj, it finds libusb correctly. > > Then while running make install for hpoj, I get the errors listed at the > end of this message. > > Does anybody have any insight into how to fix this? <...> > g++ -lusb -o ptal-mlcd ExMgr.o ParPort.o transport/ExTransport.o > transport/ExMlcTransport.o transport/ExMlcCommandChannel.o > ExMgr.o: In function `UsbMgr::llioInit(void)': > /home/phil/hpoj-0.91/mlcd/ExMgr.cpp:3945: undefined reference to `usb_init' > ExMgr.o: In function `UsbMgr::llioGlob(void)': > /home/phil/hpoj-0.91/mlcd/ExMgr.cpp:3959: undefined reference to > `usb_find_busses' You haven't given any information about your distribution. Assuming it is RPM-based and your libusb is installed as an RPM instead of source, you may be missing the development package for libusb. Depending on your distro, the package may be named something like "libusb-devel" . Also make sure you don't have any part of an older version of hpoj installed. -- Joe |
From: Jarl F. <ja...@so...> - 2004-04-13 19:04:55
|
Michal Kosmulski <M.K...@el...> writes: > hello, > I have a PSC2210 multifunction device and use it with hpoj 0.90. I also > have linux kernel 2.4.23, and the device is connected to the usb port. > Generally, everything works quite well (printing via cups works without > problems), but there are two issues with scanning that I have not been > able to solve despite reading the docs and doing extensive web searches. > a) When I scan (sane with hpoj backend, xsane or kooka as frontend), the > size of the whole scan area is always Letter-size, even though the > booklets claim that the device can do either Letter or A4. For me (and > probably most people in Europe), A4 scanning is necessary since many > documents are on A4 sized paper. Being unable to scan an A4 piece of paper > in a single scan is a rather annoying problem. > b) When I select an area to be scanned in the preview window (whether in > xsane or kooka), the area that actually gets scanned is not what I > selected but both vertical edges are shifted to the right: the left edge > is shifted only a little, but the right edge is shifted quite a lot (ca 2 > centimeters on the original document). This is annoying since it makes > precise scanning of e.g. photos or any documents smaller than the whole > scan area problematic. Selecting the right area to be scanned is not > possible, so I always have to select much more than is really needed and > then use GIMP to leave only the important part. This sound like the well known problem described on=20 http://hpoj.sourceforge.net/_todo-0.90.shtml=20 as=20 ------------------------------ When scanning on some models (especially the PSC 2xxx and OfficeJet 61xx series), the bottom and/or right margin may be cut off, and/or selected scan areas may be offset to the right. Fixed as much as possible in CVS; any remaining cutoffs are probably the fault of either the device or frontend application. ------------------------------ The page states that this has been fixed in CVS (but with no date). However I can verify that this has been solved in 0.91, so I suggest that you use 0.91 instead. If you use SuSE 9.0 I have made packages for that, which is available on http://www.softace.dk/personal/jarl/hpoj/SuSE-9.0/ > Please let me know if there are any known solutions to these two issues. > Please also reply to my e-mail, as I am not subscribed to the mailing > list. Please post positive or negative results back here on the list. Jarl --=20 Jarl Friis Softace Om=F8gade 8, 2.sal 2100 K=F8benhavn =D8. Denmark Phone: +45 26 13 20 90 E-mail: ja...@so... |
From: Michal K. <M.K...@el...> - 2004-04-13 17:41:15
|
hello, I have a PSC2210 multifunction device and use it with hpoj 0.90. I also have linux kernel 2.4.23, and the device is connected to the usb port. Generally, everything works quite well (printing via cups works without problems), but there are two issues with scanning that I have not been able to solve despite reading the docs and doing extensive web searches. a) When I scan (sane with hpoj backend, xsane or kooka as frontend), the size of the whole scan area is always Letter-size, even though the booklets claim that the device can do either Letter or A4. For me (and probably most people in Europe), A4 scanning is necessary since many documents are on A4 sized paper. Being unable to scan an A4 piece of paper in a single scan is a rather annoying problem. b) When I select an area to be scanned in the preview window (whether in xsane or kooka), the area that actually gets scanned is not what I selected but both vertical edges are shifted to the right: the left edge is shifted only a little, but the right edge is shifted quite a lot (ca 2 centimeters on the original document). This is annoying since it makes precise scanning of e.g. photos or any documents smaller than the whole scan area problematic. Selecting the right area to be scanned is not possible, so I always have to select much more than is really needed and then use GIMP to leave only the important part. Please let me know if there are any known solutions to these two issues. Please also reply to my e-mail, as I am not subscribed to the mailing list. Michal Kosmulski |
From: Joe P. <joe...@sn...> - 2004-04-13 14:57:56
|
On Monday 12 April 2004 02:16, Dmitry Vukolov wrote: > Hi Joe, <...> > I'm reposting the patch to the mailing list for anyone else who may be > interested in it. I works without a hitch for iso8859-1 and iso8859-5 > showing all special characters correctly. OK. I didn't understand that before. You didn't make it clear. If your patch fixes all of the problems you were seeing, then the changes I was suggesting would not be useful. I would like to see others try your patch and report their results. I've put up a web page containing your patch for download at http://pages.cthome.net/jsp/prj/xojpanel/xojpanel.html I've been away from coding (and from xojpanel) for a while, so it will take me some time to relearn a bit and to try to understand what your patch will do, since I can not see its results on my hardware. > What bothers me is that the current convertion procedure will probably not > work for multibyte encodings if HP devices ever make use of them. I would > appreciate any information and ideas about that. It seems likely that xojpanel would need some changes. Using QChar for the character maps would probably be one of them. I don't know if libptal, which xojpanel uses to retrieve the peripherals' LCD display strings, can handle multibyte characters. If it cannot, it would need to be hacked. Doing that might be beyond my capability. HP is showing little evidence of intention to continue hpoj development. I can think of a couple of ways that HP could use unicode in future LCD displays: 1. Unicode sent to the PC, with software doing character (or even string) translations based on a locale setting, then feeding back the translations to the LCD display unit. I think this would only be used when the device is not expected to be used in "stand-alone" fashion. 2. Unicode used (or just stored) internally, but making only a subset visible to the user, with some way to configure the charset before or (maybe through software) after delivery. This would be more suitable for use in stand-alone devices. If HP wants to be generous, it could allow the user to configure the locale directly on the peripheral. These are just guesses, though. It would really be helpful if HP provides answers. > The original idea was that -devenc could be useful not only with cyrillic > but other non-latin charsets as well. We might make -cyrillic (or -charset > cyrillic) an alias for -devenc ISO8859-5 for convenience reasons assuming > that it's the only encoding used by HP for that purpose. To keep things simple, it might be better to use only '-devenc', as you suggested at first. -- Joe |