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: Joe P. <joe...@sn...> - 2000-09-14 21:17:55
|
On Thu, 14 Sep 2000, Salkind, Lou wrote: > I haven't tried the new release yet, but at least under the 0.4 > distribution, the gamma correction didn't work for me. More precisely, on > an Officejet 720, I did get colors to print out, but the colors didn't > correspond to the colors in the original image. I used the same gamma > correction as Joe. > Lou- Sorry it didn't work. Did you take a look at the SuSe gamma page? There may be something there that you could use. It has some info relating to incorrect colors. I'm including it here again so you won't have to search. http://sdb.suse.de/sdb/en/html/jsmeix_print-gammakorrektur.html The advice there doesn't apply exactly if you're running redhat, but it still might be useful. Out of curiosity, which colors seem to be switched? Did it look like the gamma correction worked? Joe |
From: Salkind, L. <Lou...@de...> - 2000-09-14 14:48:08
|
I haven't tried the new release yet, but at least under the 0.4 distribution, the gamma correction didn't work for me. More precisely, on an Officejet 720, I did get colors to print out, but the colors didn't correspond to the colors in the original image. I used the same gamma correction as Joe. I'll play around a bit more with this in a few days when I install the 0.6 distribution, and if I make any progress, I will report it to you. Thanks again for all your work on this distribution. -----Original Message----- From: PASCHAL,DAVID (HP-Roseville,ex1) [mailto:dav...@hp...] Sent: Wednesday, September 13, 2000 8:30 PM To: hpo...@li... Subject: RE: [Hpoj-devel] Re: color printing in OfficeJets 300/500/600/700 > Though I didn't complain about print trouble here, I thought > I'd pass along > some info regarding my officejet 600 that I'm using with a > redhat 6.1 system. Hi, Joe. Thanks for the info. If you don't object I will include it in the documentation for a future release. I haven't yet gotten around to trying your advice out. Lou Salkind was the one who reported color printing problems on these models a while back. Lou, does Joe's advice fix the problems you were having? David _______________________________________________ hpoj-devel mailing list hpo...@li... http://lists.sourceforge.net/mailman/listinfo/hpoj-devel |
From: Alexander Z. <Ale...@fm...> - 2000-09-14 14:28:05
|
On 13 Sep, David Paschal wrote: > >> But now, how to track this error. Before chrashing there are a lot of >> messages displayed on the screen (virtual consule 1), but these are not >> in the log file after rebooting, and scrolling up the screen doesn't >> work any more, when the kernel crashed. Redirecting to file also does >> not work. Any idea? > Redirecting to a file wouldn't work because the messages are sent directly > to the console by the kernel, rather than through standard output or > standard error of any particular process. I added line numbers to the printk statements in ieee12844pp.c the last lines before the crash are (transcribed): 439: get_nibble(e00ba5c0): nibble=0x5 Aiee, killing interupt handle 444: e00ba5c0: event=11. Kernel panic: Attemped to kill the idle task! 448: e00ba5c0: event=6. In swapper task - not syncing 433: e00ba5c0: event=9. Does this help? > Is there any way you can run an SMP kernel but somehow force your computer > to only activate one CPU, either by a BIOS setup option, dip switch/jumper, > or physically removing one CPU (but be careful!)? If you can duplicate > this problem with an SMP kernel on a uniprocessor system then I might be > able to scrounge up an extra PC and set it up to work on this problem if > nobody else can. There is no way to deactivate the CPU without unscrewing the machine. I'll try that as soon as it is possible. -- Ale...@fm... / You look like a million http://www.fmi.uni-passau.de/~zimmerma/ dollars. All green and for PGP public key finger / wrinkled. zim...@yo... / |
From: <pa...@rc...> - 2000-09-14 06:31:10
|
> I don't have any objection to it being added to the docs, but I've only been > able to test it on this one machine. It really should be checked out by others > before including it, as I'm not an expert in this field. Hi, Joe. I'll try it out on my 570 at some point before I add it, and hopefully Lou or somebody else can try it out on a 700 series OfficeJet and let me know if it's good there. > I think I should clarify that I wasn't using the hpoj drivers then, only the > standard redhat-distributed printing system (with gamma correction). That shouldn't make a difference. The hpoj drivers only provide I/O functionality to access all of the services on an MFP, not just printing. Either way, the same ghostscript drivers are responsible for rendering the print job. David |
From: Joe P. <joe...@sn...> - 2000-09-14 02:40:18
|
On Wed, 13 Sep 2000, PASCHAL,DAVID (HP-Roseville,ex1) wrote: > > Though I didn't complain about print trouble here, I thought > > I'd pass along > > some info regarding my officejet 600 that I'm using with a > > redhat 6.1 system. > Hi, Joe. Thanks for the info. If you don't object I will include it in the > documentation for a future release. > > I haven't yet gotten around to trying your advice out. Lou Salkind was the > one who reported color printing problems on these models a while back. Lou, > does Joe's advice fix the problems you were having? > > David David - I don't have any objection to it being added to the docs, but I've only been able to test it on this one machine. It really should be checked out by others before including it, as I'm not an expert in this field. I think I should clarify that I wasn't using the hpoj drivers then, only the standard redhat-distributed printing system (with gamma correction). Joe |
From: PASCHAL,DAVID (HP-Roseville,ex1) <dav...@hp...> - 2000-09-14 00:29:51
|
> Though I didn't complain about print trouble here, I thought > I'd pass along > some info regarding my officejet 600 that I'm using with a > redhat 6.1 system. Hi, Joe. Thanks for the info. If you don't object I will include it in the documentation for a future release. I haven't yet gotten around to trying your advice out. Lou Salkind was the one who reported color printing problems on these models a while back. Lou, does Joe's advice fix the problems you were having? David |
From: PASCHAL,DAVID (HP-Roseville,ex1) <dav...@hp...> - 2000-09-14 00:26:08
|
> When I run "modprobe -k ieee12844pp", I get: > > /lib/modules/misc/ieee12844pp.o: init_module: Device or resource busy > Hint: insmod errors can be caused by incorrect module > parameters, including invalid IO or IRQ parameters > /lib/modules/misc/ieee12844pp.o: insmod ieee12844pp failed > > The problem is that modprobe does not know to load paraport_probe. If > I change the modules.dep file, by hand, to make ieee12844pp depend on > paraport_probe instead of paraport, it works as expected. Depmod -a > does not detect that ieee12844pp requires paraport_probe. Hi, John. Thanks for the info. I might be able to fix this by having a dummy call from ieee12844pp.c to some function in parport_probe. It wouldn't even have to be executed, as long as the external reference is enough to make modprobe realize that ieee1284pp.o requires parport_probe. Keep in mind that the peripheral needs to be connected and powered on before parport_probe is loaded, so one should be careful about forcing these modules to be loaded at boot time. David |
From: PASCHAL,DAVID (HP-Roseville,ex1) <dav...@hp...> - 2000-09-14 00:10:30
|
> I was able to scan some small images using sane. > Unfortunately, for large > images, the scanning went into 'D' (hardware block?) before > the scans were > finished. Resetting the PSC a number of times didn't help, > and the module > couldn't be unloaded or the scan processes killed (expected). > I didn't try > printing large files, but small files worked fine. > > What is the best way to debug this kind of stall? Hi, Daniel. I've occasionally seen this problem, where the process hangs and can't be killed, and ieee12844pp can't be unloaded, but I haven't been able to reproduce it reliably to try to track it down. What sequence of steps do you take to cause the problem (i.e. resolution and geometry settings, preview versus non-preview scans, number and frequency of scans, etc.)? > Also, does anyone have (or know how to get) a list of valid > OID codes for the > PSC 500? The LCD display codes didn't work. I've found trial and error to be the most reliable way to determine which OIDs are supported by which models. According to my testing very few are supported by the 1150, 117x, R series, and PSC500. That's why I put an "X" for xojpanel and these models on http://hpoj.sourceforge.net/suplist.shtml. > This last bit is off-topic, but xscanimage wasn't recognized by gimp. > According to the sane docs, all I have to do is put it in the > gimp plugin > directory. This didn't work, and gimp skipped it with an > "unrecognized > plugin" error. If anyone knows how to integrate this into gimp, I'd > appreciate an e-mail. Try looking around in the SANE mailing list archives (http://www.mostang.com/sane). I think there has been some discussion about this problem there in the past, but I don't remember the solution. Was gimp installed when you configured and built SANE? Was SANE's configure script able to find GIMP? Alternatively, you could try xsane, which is linked from there. xscanimage isn't really being maintained anymore. David |
From: <pa...@rc...> - 2000-09-13 21:51:30
|
> First of all it's not a problem of version 0.6, it's more general, since > 0.5 make the same problems. It's really a problem of the SMP kernel: > (Seems I've never tested 0.5 with a SMP kernel.) > > If I boot a non-SMP kernel and load the modules I build on this kernel, > it works (I've at least printed one page with ptal-connect). > If I boot the SMP kernel and load the SMP kernel modules it crashes at > "hpo devid". Hi, Alexander. I feel a little better knowing that I didn't break it in my changes for 0.6. :-) > If I try to load the modules build with the non-SMP kernel into the > running SMP kernel it gives unresolved kernel symbols (and also > vice-versa), although the module and kernel source where the same! Switching between SMP and non-SMP kernels may change version information attached to kernel symbols. This would cause unresolved kernel symbol errors as if you had switched kernel versions. > Don't you have any kernel expert at your hand, that may help us? Unfortunately, the people who originally developed this code are no longer maintaining it. There is one other person who indicated an interest in resolving another kernel problem. I forwarded your and my messages to the hpoj-devel mailing list in hopes that somebody might be able to assist. If you haven't already, please subscribe to this list and use that for further communications about this issue, so that others can follow along. > But now, how to track this error. Before chrashing there are a lot of > messages displayed on the screen (virtual consule 1), but these are not > in the log file after rebooting, and scrolling up the screen doesn't > work any more, when the kernel crashed. Redirecting to file also does > not work. Any idea? Redirecting to a file wouldn't work because the messages are sent directly to the console by the kernel, rather than through standard output or standard error of any particular process. Is there any way you can run an SMP kernel but somehow force your computer to only activate one CPU, either by a BIOS setup option, dip switch/jumper, or physically removing one CPU (but be careful!)? If you can duplicate this problem with an SMP kernel on a uniprocessor system then I might be able to scrounge up an extra PC and set it up to work on this problem if nobody else can. David |
From: David P. <pa...@rc...> - 2000-09-13 21:30:37
|
It looks like the ieee12844 and/or ieee12844pp drivers are broken on SMP kernels. Any ideas? David ------- Forwarded Messages Return-Path: zim...@fo... Delivery-Date: Mon Sep 11 12:52:21 2000 Return-Path: <zim...@fo...> Received: from localhost (localhost.localdomain [127.0.0.1]) by axel.local (8.9.3/8.9.3) with ESMTP id MAA00725 for <paschal@localhost>; Mon, 11 Sep 2000 12:52:21 -0700 Received: from mail.rcsis.com by localhost with POP3 (fetchmail-5.3.1) for paschal@localhost (single-drop); Mon, 11 Sep 2000 12:52:21 -0700 (PDT) Received: from sauron.forwiss.uni-passau.de (sauron.forwiss.uni-passau.de [132.231.20.100]) by mail.rcsis.com (Rockliffe SMTPRA 4.2.2) with ESMTP id <B00...@ma...> for <pa...@rc...>; Mon, 11 Sep 2000 06:31:50 -0700 Received: from forwiss.uni-passau.de (kepler.fmi.uni-passau.de [132.231.31.158]) by sauron.forwiss.uni-passau.de (8.9.3/8.9.3) with ESMTP id PAA15712 for <pa...@rc...>; Mon, 11 Sep 2000 15:34:30 +0200 (MET DST) Message-Id: <200...@sa...> Date: Mon, 11 Sep 2000 15:34:15 +0200 (MEST) From: Alexander Zimmermann <Ale...@fm...> Reply-To: Ale...@fm... Subject: Problems with hpoj-0.6 To: pa...@rc... In-Reply-To: <200009111115.EAA06535@axel.local> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Hi David, after your announcement I tried hpoj-0.6 and ran into major problems. My environment (RedHat 6.2): CPUs: Dual Pentium III 750 MHz Kernel: 2.2.14-5.0smp Printer: OfficeJet G85 I've compiled and installed hpoj succesfull. Also loading the kernel modules works and "hpo devid" yields: MFG:Hewlett-Packard;MDL:OfficeJet G85;CMD:MLC,PCL,PML,SCL;CLASS:PRINTER; DESCRIPTION:Hewlett-Packard OfficeJet G Series;1284.3M:f7f,f7f; 1284.4DL:4d,4e,1;SERN:SGD05E07X7VL; VSTATUS:$HB0$NC0,ff,DN,IDLE,CUT,K0,C0,SM,NR,KP074,CP072;AiO:0; But any call to ieee12844_print or ptal-connect or even multiple calls to hpo get OID_STATUS_MSG_LINE1_PART1 crashed the kernel with a message like this: Scheduling in interrupt Unable to handle kernel NULL pointer dereference at virtual adress 00000000 current->tss.cr3 = 00101000, %cr3 = 00101000 . . (not copied) . Kernel panic: Attempted to kill the idle task! In swapper task - not syncing And I had to press the hardware reset button :-(. With 0.5 this did not appear. I assume there's something wrong with a kernel module. Is there any way to debug these modules? - -- Ale...@fm... / Pick another fortune cookie. http://www.fmi.uni-passau.de/~zimmerma/ for PGP public key finger / zim...@yo... / ------- Message 2 Return-Path: pa...@rc... Delivery-Date: Mon Sep 11 16:18:37 2000 Return-Path: <pa...@rc...> Received: from localhost (localhost.localdomain [127.0.0.1]) by axel.local (8.9.3/8.9.3) with ESMTP id QAA01676 for <paschal@localhost>; Mon, 11 Sep 2000 16:18:36 -0700 Received: from mail.rcsis.com by localhost with POP3 (fetchmail-5.3.1) for paschal@localhost (single-drop); Mon, 11 Sep 2000 16:18:37 -0700 (PDT) Received: from axel.local (226.dsl9218.rcsis.com [63.92.18.226]) by mail.rcsis.com (Rockliffe SMTPRA 4.2.2) with ESMTP id <B00...@ma...> for <pa...@rc...>; Mon, 11 Sep 2000 16:12:25 -0700 Received: from rcsis.com (localhost.localdomain [127.0.0.1]) by axel.local (8.9.3/8.9.3) with ESMTP id QAA01669; Mon, 11 Sep 2000 16:17:51 -0700 Message-Id: <200009112317.QAA01669@axel.local> To: Ale...@fm... Cc: pa...@rc... Subject: Re: Problems with hpoj-0.6 In-reply-to: Your message of "Mon, 11 Sep 2000 15:34:15 +0200." <200...@sa...> From: pa...@rc... (David Paschal) Reply-To: pa...@rc... Date: Mon, 11 Sep 2000 16:17:51 -0700 Hi, Alexander. Unfortunately I don't have access to an SMP system and I'm not very familiar with kernel-mode development, so I don't have any easy answers. There are several things we can try, though. First of all, try the following variations on the insmod commands: insmod ieee12844.o debug=15 insmod ieee12844pp.o debug=1 If necessary, specify the path to the .o files. Try performing the smallest operation you can that makes it crash. Assuming it still crashes when debug messages are turned on (sometimes this changes the timing and makes the problem go away), I would like to see how far it gets when it dies. The debug messages may or may not make it into syslog by that time. You can also try including the "debug=" parameter on one or the other insmod command and not both. In 0.6 I made some very small changes to ieee12844.c and some larger changes to ieee12844pp.c, but nothing that obviously looks like the culprit. Try reverting back to the 0.5 versions of these files, while otherwise using the rest of 0.6. Verify that it works now. If you're willing to help me with this, then maybe I should next try to send you small patches against the 0.5 versions and gradually add back in the changes that went into 0.6. This would help narrow down exactly which change broke it on your system. I apologize for the inconvenience this causes you. Thanks in advance for helping me resolve this problem. David > Hi David, > > after your announcement I tried hpoj-0.6 and ran into major problems. > My environment (RedHat 6.2): > > CPUs: Dual Pentium III 750 MHz > Kernel: 2.2.14-5.0smp > Printer: OfficeJet G85 > > I've compiled and installed hpoj succesfull. Also loading the kernel > modules works and "hpo devid" yields: > > MFG:Hewlett-Packard;MDL:OfficeJet G85;CMD:MLC,PCL,PML,SCL;CLASS:PRINTER; > DESCRIPTION:Hewlett-Packard OfficeJet G Series;1284.3M:f7f,f7f; > 1284.4DL:4d,4e,1;SERN:SGD05E07X7VL; > VSTATUS:$HB0$NC0,ff,DN,IDLE,CUT,K0,C0,SM,NR,KP074,CP072;AiO:0; > > > But any call to ieee12844_print or ptal-connect or even multiple > calls to > hpo get OID_STATUS_MSG_LINE1_PART1 > crashed the kernel with a message like this: > > Scheduling in interrupt > Unable to handle kernel NULL pointer dereference at virtual adress 00000000 > current->tss.cr3 = 00101000, %cr3 = 00101000 > . > . (not copied) > . > Kernel panic: Attempted to kill the idle task! > In swapper task - not syncing > > > And I had to press the hardware reset button :-(. > > With 0.5 this did not appear. > > I assume there's something wrong with a kernel module. Is there any way > to debug these modules? > -- > Ale...@fm... / Pick another fortune cookie. > http://www.fmi.uni-passau.de/~zimmerma/ > for PGP public key finger / > zim...@yo... / ------- Message 3 Return-Path: zim...@fo... Delivery-Date: Wed Sep 13 12:39:57 2000 Return-Path: <zim...@fo...> Received: from localhost (localhost.localdomain [127.0.0.1]) by axel.local (8.9.3/8.9.3) with ESMTP id MAA00719 for <paschal@localhost>; Wed, 13 Sep 2000 12:39:56 -0700 Received: from mail.rcsis.com by localhost with POP3 (fetchmail-5.3.1) for paschal@localhost (single-drop); Wed, 13 Sep 2000 12:39:56 -0700 (PDT) Received: from sauron.forwiss.uni-passau.de (sauron.forwiss.uni-passau.de [132.231.20.100]) by mail.rcsis.com (Rockliffe SMTPRA 4.2.2) with ESMTP id <B00...@ma...> for <pa...@rc...>; Wed, 13 Sep 2000 05:38:30 -0700 Received: from forwiss.uni-passau.de (kepler.fmi.uni-passau.de [132.231.31.158]) by sauron.forwiss.uni-passau.de (8.9.3/8.9.3) with ESMTP id OAA12116 for <pa...@rc...>; Wed, 13 Sep 2000 14:41:11 +0200 (MET DST) Message-Id: <200...@sa...> Date: Wed, 13 Sep 2000 14:40:54 +0200 (MEST) From: Alexander Zimmermann <Ale...@fm...> Reply-To: Ale...@fm... Subject: SMP Problems with hpoj-0.6 To: pa...@rc... In-Reply-To: <200009112317.QAA01669@axel.local> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Hello David, On 11 Sep, David Paschal wrote: > Hi, Alexander. Unfortunately I don't have access to an SMP system and I'm > not very familiar with kernel-mode development, so I don't have any easy > answers. There are several things we can try, though. Fortunately I have access to an SMP system (;-)), but unfortunately I'm also not familiar with kernel module development. But I made some tests. First of all it's not a problem of version 0.6, it's more general, since 0.5 make the same problems. It's really a problem of the SMP kernel: (Seems I've never tested 0.5 with a SMP kernel.) If I boot a non-SMP kernel and load the modules I build on this kernel, it works (I've at least printed one page with ptal-connect). If I boot the SMP kernel and load the SMP kernel modules it crashes at "hpo devid". If I try to load the modules build with the non-SMP kernel into the running SMP kernel it gives unresolved kernel symbols (and also vice-versa), although the module and kernel source where the same! Don't you have any kernel expert at your hand, that may help us? There are some compiler warning when bulding the modules like this: /usr/src/linux-2.2.14/include/linux/smp.h:77: warning: `smp_num_cpus' redefined /usr/src/linux-2.2.14/include/linux/modules-smp/i386_ksyms.ver:72: warning: this is the location of the previous definition But now, how to track this error. Before chrashing there are a lot of messages displayed on the screen (virtual consule 1), but these are not in the log file after rebooting, and scrolling up the screen doesn't work any more, when the kernel crashed. Redirecting to file also does not work. Any idea? > I apologize for the inconvenience this causes you. Thanks in advance for > helping me resolve this problem. You don't have to apologize for anything. It's great to have one person who is developing a device driver, that I can use. To me it's self-evident to give help in this development, as far as I can. And I hope we can solve this problem. - -- Ale...@fm... / Who is John Galt? http://www.fmi.uni-passau.de/~zimmerma/ for PGP public key finger / zim...@yo... / ------- End of Forwarded Messages |
From: PASCHAL,DAVID (HP-Roseville,ex1) <dav...@hp...> - 2000-09-13 21:22:56
|
> You're right David, I've hacked for a few hours since my last > messages, > and I've found that (apparently) the function start_bh_atomic and > end_bh_atomic don't exist any more since 2.3.43. > So I just commented out these functions, and it compiled. > I can insmod the modules, and run hpo devid without errors. Hi, Damcha. I'm glad you got it working, but I would be a little concerned about just removing these calls altogether as opposed to trying to find out if there's a proper replacement in the newer kernels. > But hpo get OID_STATUS_MSG_LINE1_PART1 replies: > Error 11 (system error 22) in file pml.c, line 283: > I got the same error for trap but in line 381, This OID isn't supported on the PSC500. I don't remember if this is the right error or if it's failing for some other reason. Try some of the others, like OID_DEV_MODEL_NAME. > and for scan at line 246... Please try downloading version 0.6. It contains a patch to SANE 1.0.3 to allow scanning on some of the OfficeJets (including the PSC500). > If you want, I think I can go more indepth into this, and try to make > hpoj 2.4-kernel compatible, or is there already someone > working on this > ? If you're willing and able to do some kernel-level hacking like this, I would certainly appreciate it. I'm familiar with the communication protocols but rather ignorant when it comes to kernel issues. :-) It also seems that the kernel-mode drivers are broken for SMP. I'll forward the e-mails I've been exchanging about that, in hopes that you or somebody else might be able to figure it out. David |
From: Damcha <da...@cy...> - 2000-09-13 18:47:45
|
Hello all, > Hi, Damcha. It appears that something changed in kernel 2.3/2.4 that broke > the ieee12844 and ieee12844pp drivers. You're right David, I've hacked for a few hours since my last messages, and I've found that (apparently) the function start_bh_atomic and end_bh_atomic don't exist any more since 2.3.43. So I just commented out these functions, and it compiled. I can insmod the modules, and run hpo devid without errors. But hpo get OID_STATUS_MSG_LINE1_PART1 replies: Error 11 (system error 22) in file pml.c, line 283: I got the same error for trap but in line 381, and for scan at line 246... If you want, I think I can go more indepth into this, and try to make hpoj 2.4-kernel compatible, or is there already someone working on this ? Damcha -----BEGIN GEEK CODE BLOCK----- Version: 3.12 GCS d--(+) s: a-- C++ UL+++ P+>++ L+++ E(+) W++ N+ o? K- w-- O? M V? PS++ PE- Y+ PGP t+ 5 X++ R(+) tv-(+) b+ DI D++ G e+++ h--- r++ y+++* ------END GEEK CODE BLOCK------ See http://www.geekcode.com |
From: John L. C. <jl...@cf...> - 2000-09-13 17:37:36
|
Tried the hpoj-0.6 package, and it is a great improvement over the earlier ones. However, I have detected a problem with the kernel modules using modprobe. Since I wanted to start playing with Sane on my officejet 1170, I wrote a RedHat hpoj.spec to install the package as it seems fairly stable. I decided to install the modules under /lib/modules/misc so that depmod -a would find it and I could probably change 2.2.x kernel versions without a recompile. After running depmod -a, the modules.dep file, in /lib/modules/`uname -r`, shows the following: /lib/modules/misc/ieee12844.o: /lib/modules/misc/ieee12844pp.o: /lib/modules/misc/ieee12844.o \ /lib/modules/2.2.15/misc/parport.o When I run "modprobe -k ieee12844pp", I get: /lib/modules/misc/ieee12844pp.o: init_module: Device or resource busy Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters /lib/modules/misc/ieee12844pp.o: insmod ieee12844pp failed The problem is that modprobe does not know to load paraport_probe. If I change the modules.dep file, by hand, to make ieee12844pp depend on paraport_probe instead of paraport, it works as expected. Depmod -a does not detect that ieee12844pp requires paraport_probe. Attached is a simple hpoj-spec file. If it is included in the source, people with redhat can build a package by executing, for example, "rpm -tb hpoj-0.6.tgz", but it would need to be modified for each distribution. John Chmielewski |
From: <br...@pe...> - 2000-09-11 22:12:25
|
Nice work, people! Thanks Bruce Perens |
From: Joe P. <joe...@sn...> - 2000-09-11 17:00:19
|
On Sun, 10 Sep 2000, David Paschal wrote: > Hi. For those of you who reported problems with color printing on the > OfficeJet 300/500/600/700 series when using the DeskJet 550C ghostscript > driver, has anybody tried using the "DeskJet 670/680/690 series" driver > instead? Does it work any better? > > David Though I didn't complain about print trouble here, I thought I'd pass along some info regarding my officejet 600 that I'm using with a redhat 6.1 system. I tried both drivers you mentioned above, but I seem to get the best print quality with the "550C/560C/6xxC series" driver. Using only that driver, though, the printing is too dark. To overcome that, I use an extra gs command to change the gamma. The print quality still is not great compared to what this printer can do under windoze, but it's acceptable for now. For those who have redhat's "printtool" and are still having trouble setting up their Officejet, I've listed my settings below. I can't guarantee that these settings are the best, or that they will work correctly for anyone else. They do work for me, though. ]$ su printtool Names: HPOfficejet|officejet|ojet|oj ( You can specify several alternate names here. It lets the user choose the one they like best.) Spool Directory : /var/spool/lpd/HPofficejet (The printer-specific spool directory needs to be created inside your system's default lpd spool dir. With redhat it's /var/spool/lpd. ) File Limit in Kb: 0 Printer device: /dev/lp0 ( /dev/lp0 corresponds to the parallel port the printer is connected to. Some systems call the first port /dev/lp1. I actually have two printers on this box. The second is on device /dev/lp1.) Suppress Headers: yes Input Filter: click "select", choose this driver - "HP Deskjet 550C/560C/6xxC series" Resolution: 300x300 (probably no choice here) Paper Size: your choice. I use "letter". Color Depth: "32, sometimes better than 24" "send EOF after job... " - yes "Fix stair-stepping" - yes "Fast-text printing" - yes Pages per Output Page: 1 (your choice) Margins: 18, 18 extra gs options - "gs /usr/local/etc/gamma.ps %s" (without the quotes) You will probably have to create the file /usr/local/etc/gamma.ps. The file can be placed elsewhere, but that's where I have it. Wherever you do put it, you need to specify its location on the "Extra gs Options" line in printtool. Using this file is only necessary if you need to modify the brightness of the output. My gamma.ps contains the following text (between the lines). In case the lines wrap, the '%1' is on the first line. The rest all on the second. I don't really understand all of these commands, but they work on this system. ------------------------------------------------ %! {0.333 exp} {0.333 exp} {0.333 exp} currenttransfer setcolortransfer ------------------------------------------------ Setting ownership and permissions for gamma.ps: ]$ su cd /usr/local/etc chown root:root gamma.ps chmod 644 gamma.ps After all this, restart lpd. You don't need to restart lpd if you are only modifying 'gamma.ps'. The suSe linux site has information on printer gamma here: http://sdb.suse.de/sdb/en/html/jsmeix_print-gammakorrektur.html A google.com search for "gamma.ps" will turn up more information. I hope this is useful to someone. My thanks to David for working on a driver for the officejets. Joe Piolunek |
From: Salkind, L. <Lou...@de...> - 2000-09-11 14:07:26
|
I tried this a while back (about 8 months ago on Redhat 6.1) and the colors came out worse than the 550C. I haven't tried it with the most recent ghostscript release, though. -----Original Message----- From: pa...@rc... [mailto:pa...@rc...] Sent: Sunday, September 10, 2000 10:03 PM To: hpo...@li... Cc: pa...@rc... Subject: [Hpoj-devel] color printing in OfficeJets 300/500/600/700 Hi. For those of you who reported problems with color printing on the OfficeJet 300/500/600/700 series when using the DeskJet 550C ghostscript driver, has anybody tried using the "DeskJet 670/680/690 series" driver instead? Does it work any better? David _______________________________________________ Hpoj-devel mailing list Hpo...@li... http://lists.sourceforge.net/mailman/listinfo/hpoj-devel |
From: <pa...@rc...> - 2000-09-11 02:00:12
|
Hi. For those of you who reported problems with color printing on the OfficeJet 300/500/600/700 series when using the DeskJet 550C ghostscript driver, has anybody tried using the "DeskJet 670/680/690 series" driver instead? Does it work any better? David |
From: David P. <pa...@rc...> - 2000-09-10 23:38:49
|
> ieee12844.c:1541: warning: initialization from incompatible pointer type > ieee12844.c:1542: warning: initialization from incompatible pointer type > ieee12844.c:1545: warning: initialization from incompatible pointer type > ieee12844.c:1547: warning: excess elements in struct initializer > ieee12844.c:1547: warning: (near initialization for `mlc_proto_ops') <snip> > When I try to insmod ieee12844.o I obtain: ieee12844 unresolved symbol > end_bh_atomic, ieee12844.o: unresolved symbol start_bh_atomic. <snip> > uname -a > Linux guizmo 2.4.0-test1 #10 SMP Sat Sep 9 16:51:13 CEST 2000 i686 > unknown Hi, Damcha. It appears that something changed in kernel 2.3/2.4 that broke the ieee12844 and ieee12844pp drivers. Since I'm not a kernel expert and don't have a 2.4 machine, I'm not sure how to fix this right now, but I'll look into it at some point. Does anyone else have any ideas here? > The apps compile without errors (except xojpanel -- I don't have QT > installed), ojlib also, ptal gives me some warnings (end of non void > functions and unused variables (cbd,dev,chan)) but compiles. The warnings in the ptal directory result from currently unused functions I started but haven't finished writing yet. David |
From: David P. <pa...@rc...> - 2000-09-10 23:38:49
|
> Does anyone know if the comment below applies to enabling scanning for > the OfficeJet 1150C? I know that David said before there is a danger > of carriage damage with that model, and I wouldn't want to try it > unless I know for sure. Thanks. Hi, Gregory. I fixed that problem. It turned out that when scanning at resolutions less than 42 dpi, the carriage moved so fast that it crashed into the wall on both sides. My fix was to check for this model and set a minimum resolution of 50 dpi. That should give enough of a safety margin. Of course, if you still experience problems of this nature, stop using it and let me know. Fortunately, I don't think I killed the 1150C I was testing with; it still seems to scan fine despite the abuse I subjected it to. :-) David |
From: Gregory A. <ga...@ne...> - 2000-09-10 15:06:26
|
Does anyone know if the comment below applies to enabling scanning for the OfficeJet 1150C? I know that David said before there is a danger of carriage damage with that model, and I wouldn't want to try it unless I know for sure. Thanks. > > Last night I finally finished my SANE changes to support scanning on the > > flatbed OfficeJets, and I submitted them to one of the official SANE > > developers for review and checkin to their codebase. Once that's done > > (hopefully this weekend) I'll put out hpoj-0.6 to enable it. > > > > Scanning support for the scrollfed OfficeJets (such as the 635) will not be > > included in this release, but it's next on my to-do list. Hang in there. -- ************************************** Gregory Allan <ga...@ne...> Great American Land Exchange http://land.netonecom.net ************************************** |
From: Damcha <da...@cy...> - 2000-09-09 16:31:52
|
Hello all, First a big thanx for the work you've done... But I'd really like to test it myself !! ;-) Sorry for this verbose mail, but I couldn't decide what I should erase... So, when I try to compile it, I got this message: guizmo:/home/damcha/hpoj-0.5/ieee12844# make -j3 >ieee12844.ver gcc -E -O -I/home/damcha/hpoj-0.5/include -I/home/damcha/hpoj-0.5/ptal -I/usr/src/linux/include -Wall -Wstrict-prototypes -D__KERNEL__ -DMODULE -DEXPORT_SYMTAB -D__GENKSYMS__ ieee12844.c | \ /sbin/genksyms -k 2.4.0 >ieee12844.ver gcc -O -I/home/damcha/hpoj-0.5/include -I/home/damcha/hpoj-0.5/ptal -I/usr/src/linux/include -Wall -Wstrict-prototypes -D__KERNEL__ -DMODULE -DEXPORT_SYMTAB -c ieee12844pp.c gcc -O -I/home/damcha/hpoj-0.5/include -I/home/damcha/hpoj-0.5/ptal -I/usr/src/linux/include -Wall -Wstrict-prototypes -D__KERNEL__ -DMODULE -DEXPORT_SYMTAB -c ieee12844.c ieee12844.c: In function `link_open': ieee12844.c:1056: warning: implicit declaration of function `start_bh_atomic' ieee12844.c:1060: warning: implicit declaration of function `end_bh_atomic' ieee12844pp.c: In function `mlcpp_intr': ieee12844pp.c:844: warning: implicit declaration of function `start_bh_atomic' ieee12844pp.c:903: warning: implicit declaration of function `end_bh_atomic' ieee12844.c: At top level: ieee12844.c:1541: warning: initialization from incompatible pointer type ieee12844.c:1542: warning: initialization from incompatible pointer type ieee12844.c:1545: warning: initialization from incompatible pointer type ieee12844.c:1547: warning: excess elements in struct initializer ieee12844.c:1547: warning: (near initialization for `mlc_proto_ops') /tmp/ccj5jNyW.s: /tmp/ccYk49pS.s: Assembler messages: /tmp/ccYk49pS.s:8: Warning: Ignoring changed section attributes for .modinfo Assembler messages: /tmp/ccj5jNyW.s:8: Warning: Ignoring changed section attributes for .modinfo The apps compile without errors (except xojpanel -- I don't have QT installed), ojlib also, ptal gives me some warnings (end of non void functions and unused variables (cbd,dev,chan)) but compiles. When I try to insmod ieee12844.o I obtain: ieee12844 unresolved symbol end_bh_atomic, ieee12844.o: unresolved symbol start_bh_atomic. Here's my configuration: cat /proc/sys/dev/parport/parport1/autoprobe CLASS:PRINTER; MODEL:PSC 500; MANUFACTURER:HEWLETT-PACKARD; DESCRIPTION:Hewlett-Packard PSC 500; COMMAND SET:MLC,PCL,PML,SCL; uname -a Linux guizmo 2.4.0-test1 #10 SMP Sat Sep 9 16:51:13 CEST 2000 i686 unknown Could someone help me ? It would be really nice if you could... Again I'm sorry about the amount of crap I paste but if it can help... Thanx, Damcha -----BEGIN GEEK CODE BLOCK----- Version: 3.12 GCS d--(+) s: a-- C++ UL+++ P+>++ L+++ E(+) W++ N+ o? K- w-- O? M V? PS++ PE- Y+ PGP t+ 5 X++ R(+) tv-(+) b+ DI D++ G e+++ h--- r++ y+++* ------END GEEK CODE BLOCK------ See http://www.geekcode.com |
From: PASCHAL,DAVID (HP-Roseville,ex1) <dav...@hp...> - 2000-09-07 23:54:27
|
Hi, Ranier. > Well, the point is, that it is not sufficient that you change > your LD_LIBRARY_PATH, but the LD_LIBRARY_PATH of the printer > daemon. As soon as the distributions pick up hpoj, the > problem is gone, because then the ptal library will be in > /usr/lib. But before, at least I personally prefer the > wrapper script, because it is a local change and > deinstalling/upgrading hpoj means simply removing the old directory. Couldn't you just add /opt/hpoj-XXXX/lib to ld.so.conf and re-run ldconfig? I've been considering adding an uninstall script that would get installed with the other binaries. That would make it easier to uninstall the package when it's installed to /usr/local or /usr. Would you be interested in this? David |
From: Rainer D. <rd...@we...> - 2000-09-07 08:47:46
|
"PASCHAL,DAVID (HP-Roseville,ex1)" <dav...@hp...> schrieb am 06.09.00: > > 3) Dynamic library issue: > > > > Since ptal-connect is linked against a non-system library I created a > > wrapper script ptal-print (this is not necessary any more as soon > > as hpoj is converted into a standard Debian/RedHat or whatever > > package or the dynamic library is install in /usr/lib. > The next version (0.6) will have a "make install" feature that installs > everything under /usr/local, which can be overridden by passing > "--prefix=DIR" to the configure script. You will still have to make sure > /usr/local/lib is specified in ld.so.conf and re-run ldconfig, or add the > directory to LD_LIBRARY_PATH. Will this installation method be acceptable? Well, the point is, that it is not sufficient that you change your LD_LIBRARY_PATH, but the LD_LIBRARY_PATH of the printer daemon. As soon as the distributions pick up hpoj, the problem is gone, because then the ptal library will be in /usr/lib. But before, at least I personally prefer the wrapper script, because it is a local change and deinstalling/upgrading hpoj means simply removing the old directory. > > > 4) Color printing > > > > So far color printing was not successful. But I have to check first if > > this is a printer hardware problem (ink empty...). But anyways, if > > somebody has an already written description how to do this, it would > > be welcome (basically I expect that I have to specify another > > OutputDevice in gs). > I have heard (but not yet verified) that ghostscript has problems with color > printing on the 500/600/700 series OfficeJets. Embarassing... I wanted to install the windows driver to check if it works under windows, but I can't find the driver disks any more. And the driver I downloaded from HP's web site does not install (although I am not a windows expert). So at least on my machine, hpoj support under linux was much easier and is currently much better! > > > 5) Scanning > > > > No success either: > Last night I finally finished my SANE changes to support scanning on the > flatbed OfficeJets, and I submitted them to one of the official SANE > developers for review and checkin to their codebase. Once that's done > (hopefully this weekend) I'll put out hpoj-0.6 to enable it. > > Scanning support for the scrollfed OfficeJets (such as the 635) will not be > included in this release, but it's next on my to-do list. Hang in there. > :-) > > > # /opt/hpoj-0.5/ptal/ptal-connect mlc:mlcpp0 -scan > > ptalMlcChannelOpen(chan=0x0804A668): error connecting socket! > > ptalChannelOpen(chan=0x0804A668): provider failed open! > "ptal-connect -scan" doesn't actually initiate a scan. It just connects to > the scan data channel on the peripheral. However, some OfficeJet models > don't allow you to do this unless you've already issued the right PML > commands to initiate the scan, so that's probably why you got this error > message. Good to know. So I postphone scaning until hpoj 0.7. > > > 6) Other vendors > > > > I want to purchase a all-in-one-device. The only real > > requirement is cost less than 500 Euro and good linux support > > (print, scan, copy). Does anybody know, if other vendors > > provide better linux support than HP does? > Not that I know of. > > Since you mentioned you were looking for good Linux support for copying, > could you clarify what exactly you're looking for here? The 500/600/700 > series OfficeJets sometimes need help from the PC to copy a page > (particularly when copying in color), in which case "copy" really means > "scan and then print". The more recent models have pretty good standalone > copy capabilities. > I was looking for color copies, which currently requires a windows machine (with a working driver) for a 635. Thanks a lot. Rainer. _______________________________________________________________________ 1.000.000 DM gewinnen - kostenlos tippen - http://millionenklick.web.de Ih...@we..., 8MB Speicher, Verschluesselung - http://freemail.web.de |
From: Tim W. <tw...@re...> - 2000-09-06 16:27:04
|
On Wed, Sep 06, 2000 at 09:13:56AM -0700, Erick Calder wrote: > I'm starting to get the feeling printing is not simple in Linux<g>. > Perhaps I could ask you this: my aim is to be able to print from my > NT laptop via the Linux box. is this even doable? Of course! Use samba to make a printer share for your print queue. Tim. */ |
From: Erick C. <ec...@ar...> - 2000-09-06 16:08:24
|
ok. so I did need apsfilter. I installed it (and a2ps which it needs, and GhostScript 6.01 which I read somewhere I had to have) but the installation requires that I configure a printer from their list, of course my OJ700 isn't there. I tried several of the HP printers but it kept complaining that GhostScript was not compiled with support for that printer (I installed from RPM), so in the end I picked one of the Epsons, figuring I would reconfigure manually later when I figure out what to do. when the installation was complete, it did not create the /var/spool/lpd/lp0/filter to which Colin Dean's wrapfilter refers. I'm starting to get the feeling printing is not simple in Linux<g>. Perhaps I could ask you this: my aim is to be able to print from my NT laptop via the Linux box. is this even doable? here's the contents of my /etc/printcap now: # /etc/printcap # # Please don't edit this file directly unless you know what you are doing! # Be warned that the control-panel printtool requires a very strict format! # Look at the printcap(5) man page for more info. # # This file can be edited with the printtool in the control-panel. ##PRINTTOOL3## LOCAL lp:\ :sd=/var/spool/lpd/lp:\ :mx#0:\ :sh:\ :lp=/dev/null:\ :if=/usr/local/bin/ieee12844_print: # LABEL apsfilter # apsfilter setup Mon Sep 4 05:46:42 EDT 2000 # # DON'T DELETE THIS: # APS_BASEDIR:/usr/local/lib/apsfilter # # APS1_BEGIN:printer1:lp8000:letter:default # - don't delete start label for apsfilter printer1 # - no other printer defines between BEGIN and END LABEL # lp|aps1-lp8000-letter-auto-default|Printer1 lp8000 letter auto default:\ :lp=/dev/lp0:\ :sd=/var/spool/lpd/printer1-lp8000-letter-auto-default:\ :lf=/var/spool/lpd/printer1-lp8000-letter-auto-default/log:\ :af=/var/spool/lpd/printer1-lp8000-letter-auto-default/acct:\ :if=/usr/local/lib/apsfilter/filter/aps1-lp8000-letter-auto-default:\ :mx#0:\ :sh: raw|aps2-lp8000-letter-raw|Printer1 lp8000 letter raw:\ :lp=/dev/lp0:\ :sd=/var/spool/lpd/printer1-lp8000-letter-raw:\ :lf=/var/spool/lpd/printer1-lp8000-letter-raw/log:\ :af=/var/spool/lpd/printer1-lp8000-letter-raw/acct:\ :if=/usr/local/lib/apsfilter/filter/aps2-lp8000-letter-raw:\ :mx#0:\ :sh: # APS1_END - don't delete this END LABEL for printer1 any help you can provide will be tremendously appreciated. - e -----Original Message----- From: hpo...@li... [mailto:hpo...@li...]On Behalf Of PASCHAL,DAVID (HP-Roseville,ex1) Sent: Tuesday, September 05, 2000 7:27 PM To: hpo...@li... Subject: RE: [Hpoj-devel] filters & "no daemon present" Hi, Erick. I've had my head in the sand for a while working on I/O and scanning issues, so I guess it's time to look into printing. > as I don't have apsfilter installed (do I need to install it?, can I not > just print with ieee12844_print?) There are actually two sets of instructions from at least two different people in PRINT-HOWTO: Andreas Fester (presumably) for SuSE (which is the part using apsfilter), and Colin Dean for RedHat. I'll try to clean this up some. > my /etc/printcap looks like this: > > lp:\ > :sd=/var/spool/lpd/lp:\ > :mx#0:\ > :sh:\ > :lp=/dev/null:\ > :if=/usr/local/bin/ieee12844_print: You can't just set "if=" to ieee12844_print, because it needs to go through a print filter script to convert the PostScript print job to the right language for the printer. Also, ieee12844_print doesn't handle the arguments that lpd automatically passes to the filter. The solution for now according to the second half of PRINT-HOWTO is to create a wrapper script that passes its command-line arguments to the standard print filter and pipes the resulting output to ieee12844_print. David _______________________________________________ Hpoj-devel mailing list Hpo...@li... http://lists.sourceforge.net/mailman/listinfo/hpoj-devel |