I am not able to get my HPLaserjet 2300 printer to working in suse 9.3. I set it up with yast for the tcp address 1.9.168.0.31, it says it is ready, but printing a test page results in nothing. http://localhost:631 show the print que as waiting. I can ping the address fine. I get the following from the /var/log/messages which appears to say the printer is trying on the parallel port. Jul 3 07:26:16 linux kernel: parport0: PC-style at 0x378 [PCSPP] Jul 3 07:26:16 linux kernel: lp0: using parport0 (polling). Jul 3 07:26:16 linux kernel: parport0: PC-style at 0x378 [PCSPP] Jul 3 07:26:42 linux syslog-ng[2801]: STATS: dropped 0 (This all worked in suse 9.2) Any suggestions on what the problem could be? Art
On Sunday 03 July 2005 10:51 am, Art Fore wrote:
I am not able to get my HPLaserjet 2300 printer to working in suse 9.3. I set it up with yast for the tcp address 1.9.168.0.31, it says it is ready, but printing a test page results in nothing. http://localhost:631 show the print que as waiting. I can ping the address fine. I get the following from the /var/log/messages which appears to say the printer is trying on the parallel port.
Jul 3 07:26:16 linux kernel: parport0: PC-style at 0x378 [PCSPP] Jul 3 07:26:16 linux kernel: lp0: using parport0 (polling). Jul 3 07:26:16 linux kernel: parport0: PC-style at 0x378 [PCSPP] Jul 3 07:26:42 linux syslog-ng[2801]: STATS: dropped 0
(This all worked in suse 9.2) Any suggestions on what the problem could be?
Art
1) The IP address you show isn't valid. (probably a typo) 2) It appears it is trying to print to a parallel printer. Something is wrong in your setup. Go back to Yast and try again.
I tried that, trying tcp, everything else. When I test remote socket access, it says cups cannot connect to server. (ip address should be 192.168.0.31) When I go to localhost:631, it show it running, but cannot get into admin or configure printer even with root password. Art On Sun, 2005-07-03 at 13:12 -0400, Bruce Marshall wrote:
On Sunday 03 July 2005 10:51 am, Art Fore wrote:
I am not able to get my HPLaserjet 2300 printer to working in suse 9.3. I set it up with yast for the tcp address 1.9.168.0.31, it says it is ready, but printing a test page results in nothing. http://localhost:631 show the print que as waiting. I can ping the address fine. I get the following from the /var/log/messages which appears to say the printer is trying on the parallel port.
Jul 3 07:26:16 linux kernel: parport0: PC-style at 0x378 [PCSPP] Jul 3 07:26:16 linux kernel: lp0: using parport0 (polling). Jul 3 07:26:16 linux kernel: parport0: PC-style at 0x378 [PCSPP] Jul 3 07:26:42 linux syslog-ng[2801]: STATS: dropped 0
(This all worked in suse 9.2) Any suggestions on what the problem could be?
Art
1) The IP address you show isn't valid. (probably a typo)
2) It appears it is trying to print to a parallel printer. Something is wrong in your setup. Go back to Yast and try again.
On Sunday 03 July 2005 11:58 am, Art Fore wrote:
I tried that, trying tcp, everything else. When I test remote socket access, it says cups cannot connect to server. (ip address should be 192.168.0.31) When I go to localhost:631, it show it running, but cannot get into admin or configure printer even with root password.
Art
On Sun, 2005-07-03 at 13:12 -0400, Bruce Marshall wrote:
On Sunday 03 July 2005 10:51 am, Art Fore wrote:
I am not able to get my HPLaserjet 2300 printer to working in suse 9.3. I set it up with yast for the tcp address 1.9.168.0.31, it says it is ready, but printing a test page results in nothing. http://localhost:631 show the print que as waiting. I can ping the address fine. I get the following from the /var/log/messages which appears to say the printer is trying on the parallel port.
Jul 3 07:26:16 linux kernel: parport0: PC-style at 0x378 [PCSPP] Jul 3 07:26:16 linux kernel: lp0: using parport0 (polling). Jul 3 07:26:16 linux kernel: parport0: PC-style at 0x378 [PCSPP] Jul 3 07:26:42 linux syslog-ng[2801]: STATS: dropped 0
But you haven't dealt with the problem that 9.3 is trying to print to a parallel port printer as shown above. Is this a network connected printer or a parallel port printer? If network, what port does it use?
On Sun, 2005-07-03 at 14:10 -0400, Bruce Marshall wrote:
On Sunday 03 July 2005 11:58 am, Art Fore wrote:
I tried that, trying tcp, everything else. When I test remote socket access, it says cups cannot connect to server. (ip address should be 192.168.0.31) When I go to localhost:631, it show it running, but cannot get into admin or configure printer even with root password.
Art
But you haven't dealt with the problem that 9.3 is trying to print to a parallel port printer as shown above. Is this a network connected printer or a parallel port printer?
If network, what port does it use?
Go to k-menu(bottom left green button)-->Utilities-->Printing-->Printing Manager At the bottom click on the Administrator Mode button and enter root's password. Highlight the printer by single clicking on it. Then click on the properties tab. Next click on the interface tab on the left. Report back as to what the interface is, the full text as shown. You either have it set as a paralell printer or have the IP/port set wrong. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
On Sun, 2005-07-03 at 15:27 -0400, Ken Schneider wrote:
On Sun, 2005-07-03 at 14:10 -0400, Bruce Marshall wrote:
On Sunday 03 July 2005 11:58 am, Art Fore wrote:
I tried that, trying tcp, everything else. When I test remote socket access, it says cups cannot connect to server. (ip address should be 192.168.0.31) When I go to localhost:631, it show it running, but cannot get into admin or configure printer even with root password.
Art
But you haven't dealt with the problem that 9.3 is trying to print to a parallel port printer as shown above. Is this a network connected printer or a parallel port printer?
If network, what port does it use?
Go to k-menu(bottom left green button)-->Utilities-->Printing-->Printing Manager
At the bottom click on the Administrator Mode button and enter root's password. Highlight the printer by single clicking on it. Then click on the properties tab. Next click on the interface tab on the left. Report back as to what the interface is, the full text as shown. You either have it set as a paralell printer or have the IP/port set wrong.
-- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
"The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
Printer type: Network Printer URI: socket:192.168.0.31:9100 This is the setting from YAST. I also enabled port 9100 on the firewall. Art
On Sun, 2005-07-03 at 12:05 -0700, Art Fore wrote:
On Sun, 2005-07-03 at 15:27 -0400, Ken Schneider wrote:
On Sun, 2005-07-03 at 14:10 -0400, Bruce Marshall wrote:
Go to k-menu(bottom left green button)-->Utilities-->Printing-->Printing Manager
At the bottom click on the Administrator Mode button and enter root's password. Highlight the printer by single clicking on it. Then click on the properties tab. Next click on the interface tab on the left. Report back as to what the interface is, the full text as shown. You either have it set as a paralell printer or have the IP/port set wrong.
Printer type: Network Printer URI: socket:192.168.0.31:9100
This is the setting from YAST. I also enabled port 9100 on the firewall.
That would be correct for a HP JetDirect. You might try deleting the printer and add it using the Printing Manager, it has always served me well. Also double check the driver and try a different one as a test. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
On Sun, 2005-07-03 at 18:48 -0400, Ken Schneider wrote:
On Sun, 2005-07-03 at 12:05 -0700, Art Fore wrote:
On Sun, 2005-07-03 at 15:27 -0400, Ken Schneider wrote:
On Sun, 2005-07-03 at 14:10 -0400, Bruce Marshall wrote:
Go to k-menu(bottom left green button)-->Utilities-->Printing-->Printing Manager
At the bottom click on the Administrator Mode button and enter root's password. Highlight the printer by single clicking on it. Then click on the properties tab. Next click on the interface tab on the left. Report back as to what the interface is, the full text as shown. You either have it set as a paralell printer or have the IP/port set wrong.
Printer type: Network Printer URI: socket:192.168.0.31:9100
This is the setting from YAST. I also enabled port 9100 on the firewall.
That would be correct for a HP JetDirect. You might try deleting the printer and add it using the Printing Manager, it has always served me well. Also double check the driver and try a different one as a test.
-- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
"The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
I am using a netgear print server that goes on the parallel port of a printer with the ethernet cable plugged into network switch. Art
On Sunday 03 July 2005 05:35 pm, Art Fore wrote:
On Sun, 2005-07-03 at 18:48 -0400, Ken Schneider wrote:
On Sun, 2005-07-03 at 12:05 -0700, Art Fore wrote:
On Sun, 2005-07-03 at 15:27 -0400, Ken Schneider wrote:
On Sun, 2005-07-03 at 14:10 -0400, Bruce Marshall wrote:
Go to k-menu(bottom left green button)-->Utilities-->Printing-->Printing Manager
At the bottom click on the Administrator Mode button and enter root's password. Highlight the printer by single clicking on it. Then click on the properties tab. Next click on the interface tab on the left. Report back as to what the interface is, the full text as shown. You either have it set as a paralell printer or have the IP/port set wrong.
Printer type: Network Printer URI: socket:192.168.0.31:9100
This is the setting from YAST. I also enabled port 9100 on the firewall.
That would be correct for a HP JetDirect. You might try deleting the printer and add it using the Printing Manager, it has always served me well. Also double check the driver and try a different one as a test.
-- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
"The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
I am using a netgear print server that goes on the parallel port of a printer with the ethernet cable plugged into network switch.
Art
Aha!! The netgear print server that I have here doing the same thing (to a parallel printer) uses ports of 4010 and 4020 for the two parallel ports that it has. I would guess your port is not specified correctly.
On Sun, 2005-07-03 at 19:29 -0400, Bruce Marshall wrote:
On Sunday 03 July 2005 05:35 pm, Art Fore wrote:
Printer type: Network Printer URI: socket:192.168.0.31:9100
That would be correct for a HP JetDirect. You might try deleting the printer and add it using the Printing Manager, it has always served me well. Also double check the driver and try a different one as a test.
I am using a netgear print server that goes on the parallel port of a printer with the ethernet cable plugged into network switch.
Art
Aha!! The netgear print server that I have here doing the same thing (to a parallel printer) uses ports of 4010 and 4020 for the two parallel ports that it has.
I would guess your port is not specified correctly.
Yep. He was trying to use port 9100 which is what HP uses for the JetDirect. No wonder it does not work. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
Ken Schneider wrote:
On Sun, 2005-07-03 at 19:29 -0400, Bruce Marshall wrote:
Printer type: Network Printer URI: socket:192.168.0.31:9100
That would be correct for a HP JetDirect. You might try deleting the printer and add it using the Printing Manager, it has always served me well. Also double check the driver and try a different one as a test.
I am using a netgear print server that goes on the parallel port of a printer with the ethernet cable plugged into network switch.
Art Aha!! The netgear print server that I have here doing the same thing (to a
On Sunday 03 July 2005 05:35 pm, Art Fore wrote: parallel printer) uses ports of 4010 and 4020 for the two parallel ports that it has.
I would guess your port is not specified correctly.
Yep. He was trying to use port 9100 which is what HP uses for the JetDirect. No wonder it does not work.
The small Netgear print server does use port 9100. I have one and have it working no problem. However, I also have the two port Netgear Print server which I can't scan and find on port 4010, 4020 OR on 9100. ???? -- 72 for now & Adios from Texas! Tom J Owens, WB5KHC ex-QRP ARCI Contest Manager #10645 FISTS #7865 CC #1026 SILVER #192 GOLD #200 PLATINUM #194 PLATINUM 250-#81 PLATINUM 500-#39 WAS FISTS #123 QRP 1X-#69 QRP 2X-#7 DIAMOND #118 FISTS USA CLUB STATION OPERATOR AWARD FISTS USA CLUB STATION ACHIEVEMENT AWARD AUTHOR OF ALL FISTS SUBMISSION FORMS FOR AWARDS http://2hams.net wb5khc@2hams.net
On Sunday 03 July 2005 07:47 pm, Tom-WB5KHC wrote:
Ken Schneider wrote:
On Sun, 2005-07-03 at 19:29 -0400, Bruce Marshall wrote:
On Sunday 03 July 2005 05:35 pm, Art Fore wrote:
Printer type: Network Printer URI: socket:192.168.0.31:9100
That would be correct for a HP JetDirect. You might try deleting the printer and add it using the Printing Manager, it has always served me well. Also double check the driver and try a different one as a test.
I am using a netgear print server that goes on the parallel port of a printer with the ethernet cable plugged into network switch.
Art
Aha!! The netgear print server that I have here doing the same thing (to a parallel printer) uses ports of 4010 and 4020 for the two parallel ports that it has.
I would guess your port is not specified correctly.
Yep. He was trying to use port 9100 which is what HP uses for the JetDirect. No wonder it does not work.
The small Netgear print server does use port 9100. I have one and have it working no problem. However, I also have the two port Netgear Print server which I can't scan and find on port 4010, 4020 OR on 9100. ????
--
72 for now & Adios from Texas!
Tom J Owens, WB5KHC ex-QRP ARCI Contest Manager #10645
FISTS #7865 CC #1026 SILVER #192 GOLD #200 PLATINUM #194 PLATINUM 250-#81 PLATINUM 500-#39 WAS FISTS #123 QRP 1X-#69 QRP 2X-#7 DIAMOND #118 FISTS USA CLUB STATION OPERATOR AWARD FISTS USA CLUB STATION ACHIEVEMENT AWARD AUTHOR OF ALL FISTS SUBMISSION FORMS FOR AWARDS
http://2hams.net wb5khc@2hams.net
And might you be reminded that standard netiquette calls for no more than 6 lines of 'signature' information. (you have TWENTY)
On Sun, 2005-07-03 at 19:38 -0400, Ken Schneider wrote:
On Sun, 2005-07-03 at 19:29 -0400, Bruce Marshall wrote:
On Sunday 03 July 2005 05:35 pm, Art Fore wrote:
Printer type: Network Printer URI: socket:192.168.0.31:9100
That would be correct for a HP JetDirect. You might try deleting the printer and add it using the Printing Manager, it has always served me well. Also double check the driver and try a different one as a test.
I am using a netgear print server that goes on the parallel port of a printer with the ethernet cable plugged into network switch.
Art
Aha!! The netgear print server that I have here doing the same thing (to a parallel printer) uses ports of 4010 and 4020 for the two parallel ports that it has.
I would guess your port is not specified correctly.
Yep. He was trying to use port 9100 which is what HP uses for the JetDirect. No wonder it does not work.
-- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
"The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
There has been no change on this print server for two years and was was working with suse 8.0, 8.1, 9.0, 9.1, & 9.2 always setting it up with yast other than changing the printer from laserjet III to laserjet 2300 about a year ago (suse 9.2) when the laserjet III finally died. So, how do I get it to not think it is the parallel port? Just change printer drivers until I find one that work? Art
On Sun, 2005-07-03 at 19:19 -0700, Art Fore wrote:
On Sun, 2005-07-03 at 19:38 -0400, Ken Schneider wrote:
On Sun, 2005-07-03 at 19:29 -0400, Bruce Marshall wrote:
On Sunday 03 July 2005 05:35 pm, Art Fore wrote:
Printer type: Network Printer URI: socket:192.168.0.31:9100
That would be correct for a HP JetDirect. You might try deleting the printer and add it using the Printing Manager, it has always served me well. Also double check the driver and try a different one as a test.
I am using a netgear print server that goes on the parallel port of a printer with the ethernet cable plugged into network switch.
Art
Aha!! The netgear print server that I have here doing the same thing (to a parallel printer) uses ports of 4010 and 4020 for the two parallel ports that it has.
I would guess your port is not specified correctly.
Yep. He was trying to use port 9100 which is what HP uses for the JetDirect. No wonder it does not work.
-- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
"The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
There has been no change on this print server for two years and was was working with suse 8.0, 8.1, 9.0, 9.1, & 9.2 always setting it up with yast other than changing the printer from laserjet III to laserjet 2300 about a year ago (suse 9.2) when the laserjet III finally died. So, how do I get it to not think it is the parallel port? Just change printer drivers until I find one that work?
Art
Just tried the hp2200 driver which is the one I was using in Suse 9.2. Same Identical results. What was the big change from 9.2 to 9.3 in this area? Art
On Sun, 2005-07-03 at 19:32 -0700, Art Fore wrote:
On Sun, 2005-07-03 at 19:19 -0700, Art Fore wrote:
Just tried the hp2200 driver which is the one I was using in Suse 9.2. Same Identical results. What was the big change from 9.2 to 9.3 in this area?
Art
What is the model of the print server? -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
On Mon, 2005-07-04 at 07:17 -0400, Ken Schneider wrote:
On Sun, 2005-07-03 at 19:32 -0700, Art Fore wrote:
On Sun, 2005-07-03 at 19:19 -0700, Art Fore wrote:
Just tried the hp2200 driver which is the one I was using in Suse 9.2. Same Identical results. What was the big change from 9.2 to 9.3 in this area?
Art
What is the model of the print server?
-- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
"The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
It is a PS101. Art
On Mon, 2005-07-04 at 06:23 -0700, Art Fore wrote:
On Mon, 2005-07-04 at 07:17 -0400, Ken Schneider wrote:
On Sun, 2005-07-03 at 19:32 -0700, Art Fore wrote:
On Sun, 2005-07-03 at 19:19 -0700, Art Fore wrote:
Just tried the hp2200 driver which is the one I was using in Suse 9.2. Same Identical results. What was the big change from 9.2 to 9.3 in this area?
Art
What is the model of the print server?
It is a PS101.
I looked at the docs for the PS101 and saw nothing that referred to port 9100. It looks like it can be used as a remote lpd printer port in which case you would use the logical port name as the printer name when it is configured. Try setting it up as a remote lpd printer, as though you were printing to another machine, and see how that works. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
On Mon, 2005-07-04 at 12:42 -0400, Ken Schneider wrote:
On Mon, 2005-07-04 at 06:23 -0700, Art Fore wrote:
On Mon, 2005-07-04 at 07:17 -0400, Ken Schneider wrote:
On Sun, 2005-07-03 at 19:32 -0700, Art Fore wrote:
On Sun, 2005-07-03 at 19:19 -0700, Art Fore wrote:
Just tried the hp2200 driver which is the one I was using in Suse 9.2. Same Identical results. What was the big change from 9.2 to 9.3 in this area?
Art
What is the model of the print server?
It is a PS101.
I looked at the docs for the PS101 and saw nothing that referred to port 9100. It looks like it can be used as a remote lpd printer port in which case you would use the logical port name as the printer name when it is configured. Try setting it up as a remote lpd printer, as though you were printing to another machine, and see how that works.
-- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
"The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
Still does not work. I give up for now. Connected printer directly to the parallel port and it works. Art
On Sunday 03 July 2005 10:32 pm, Art Fore wrote:
On Sun, 2005-07-03 at 19:19 -0700, Art Fore wrote:
On Sun, 2005-07-03 at 19:38 -0400, Ken Schneider wrote:
On Sun, 2005-07-03 at 19:29 -0400, Bruce Marshall wrote:
On Sunday 03 July 2005 05:35 pm, Art Fore wrote:
> Printer type: Network Printer > URI: socket:192.168.0.31:9100
That would be correct for a HP JetDirect. You might try deleting the printer and add it using the Printing Manager, it has always served me well. Also double check the driver and try a different one as a test.
I am using a netgear print server that goes on the parallel port of a printer with the ethernet cable plugged into network switch.
Art
Aha!! The netgear print server that I have here doing the same thing (to a parallel printer) uses ports of 4010 and 4020 for the two parallel ports that it has.
I would guess your port is not specified correctly.
Yep. He was trying to use port 9100 which is what HP uses for the JetDirect. No wonder it does not work.
-- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
"The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
There has been no change on this print server for two years and was was working with suse 8.0, 8.1, 9.0, 9.1, & 9.2 always setting it up with yast other than changing the printer from laserjet III to laserjet 2300 about a year ago (suse 9.2) when the laserjet III finally died. So, how do I get it to not think it is the parallel port? Just change printer drivers until I find one that work?
Art
Just tried the hp2200 driver which is the one I was using in Suse 9.2. Same Identical results. What was the big change from 9.2 to 9.3 in this area?
I don't think there was a major change.... I think you just haven't set it up properly. From what you say, that Netgear print server should look exactly like an HP LJ printer using port 9100. I have a network HP4000 printer here and it was set up during initial install to use port 9100. Worked fine and has with SUSE since I bought it 6 years ago. Could you send us the contents of: /etc/cups/printcap and /etc/cups/printers.conf This would help.
On Sun, 2005-07-03 at 14:35 -0700, Art Fore wrote:
On Sun, 2005-07-03 at 18:48 -0400, Ken Schneider wrote:
On Sun, 2005-07-03 at 12:05 -0700, Art Fore wrote:
On Sun, 2005-07-03 at 15:27 -0400, Ken Schneider wrote: Printer type: Network Printer URI: socket:192.168.0.31:9100
This is the setting from YAST. I also enabled port 9100 on the firewall.
That would be correct for a HP JetDirect. You might try deleting the printer and add it using the Printing Manager, it has always served me well. Also double check the driver and try a different one as a test.
I am using a netgear print server that goes on the parallel port of a printer with the ethernet cable plugged into network switch.
And which port does netgear use, what does their docs say. When setting up a network printer there is a scan function, use it to find the connection. If does not find it you are using the wrong network selection. It might be using "Network Printer w/IPP" or lpd on the port try both to see which one works. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
On Sunday 03 July 2005 17:58, Art Fore wrote:
I tried that, trying tcp, everything else. When I test remote socket access, it says cups cannot connect to server. (ip address should be 192.168.0.31) When I go to localhost:631, it show it running, but cannot get into admin or configure printer even with root password.
By default you can not access the configuration stuff for cups under localhost:631 with your root password. You will have to configure a password. When you have configured your printer have you set the port correctly? Can you telnet to that ip:port? Can you print from another station on that network to the printer? Ulf
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2005-07-03 at 07:51 -0700, Art Fore wrote:
I am not able to get my HPLaserjet 2300 printer to working in suse 9.3. I set it up with yast for the tcp address 1.9.168.0.31, it says it is ready, but printing a test page results in nothing. http://localhost:631 show the print que as waiting. I can ping the address fine. I get the following from the /var/log/messages which appears to say the printer is trying on the parallel port.
Jul 3 07:26:16 linux kernel: parport0: PC-style at 0x378 [PCSPP] Jul 3 07:26:16 linux kernel: lp0: using parport0 (polling). Jul 3 07:26:16 linux kernel: parport0: PC-style at 0x378 [PCSPP] Jul 3 07:26:42 linux syslog-ng[2801]: STATS: dropped 0
The above only says that the kernel is managing the local parallel port, it doesn't say that cups or any thing else is ready, nor even that there is a printer connected. And of course, it doesn't say anything about a network printer. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFCyH5ftTMYHG2NR9URAotyAJ9yg44SrlyVQbYZYQi+ZZYRfYmtlACZAfg1 17A4PC6zH6+rzxoG5/gHqUs= =oNWh -----END PGP SIGNATURE-----
participants (6)
-
Art Fore -
Bruce Marshall -
Carlos E. R. -
Ken Schneider -
Tom-WB5KHC -
Ulf Rasch