Printing with Kernel 2.6.14.4

Printing with Kernel 2.6.14.4

[Peter]

Hi,

Slackware 10.2    kernel 2.6.14.4

Putting /sbin/modprobe parport_pc and ... lp in rc.local I can print, however, 
only when I am connected to the Internet since the print configuration tool 
has no provisions for parallel port when local printer is selected. Only 
Network Printer will show the setting for parallel port and Epson printers.

In my Fedora4 box with kernel 2.6.14-1... selecting local printer will show 
parallel port and Epson printers and I can print w/o being connected.

How could I correct to be able to print in slackware w/o being connected.

Should I just copy the files of /lib/modules/kernel/drivers from Fedora over 
the slackware?

Thanks & regards
-- 
Peter









-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Printing with Kernel 2.6.14.4

[Hal MacArgle]

On 03-21, Peter wrote:
> Hi,
> 
> Slackware 10.2    kernel 2.6.14.4
> 
> Putting /sbin/modprobe parport_pc and ... lp in rc.local I can print, however, 
> only when I am connected to the Internet since the print configuration tool 
> has no provisions for parallel port when local printer is selected. Only 
> Network Printer will show the setting for parallel port and Epson printers.
> 
> In my Fedora4 box with kernel 2.6.14-1... selecting local printer will show 
> parallel port and Epson printers and I can print w/o being connected.
> 
> How could I correct to be able to print in slackware w/o being connected.
> 
> Should I just copy the files of /lib/modules/kernel/drivers from Fedora over 
> the slackware?
> 
> Thanks & regards
> -- 
> Peter

	Doesn't 'cat filename.txt > /dev/lp0' /or/ /dev/lp1 work??
Depending on whether you're using 0x378 or 0x278??

	I don't have a printer connected to the one Slack 10.2, 2.6.X
machine, so could be all wet... My one 10.2 machine using 2.4.31...

-- 

    Hal - in Terra Alta, WV/US - Slackware GNU/Linux 10.1   (2.4.29)
.
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Printing with Kernel 2.6.14.4

[Peter]

Thanks Hal!

haltec@kvinet.com said:
> Doesn't 'cat filename.txt > /dev/lp0'

no since /dev/lp0 is not an executable file.

I just had for 36 hours no Internet connection and therefore no printing.

Regards

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Printing with Kernel 2.6.14.4

[heisspf]

thanks Hal!

altec@kvinet.com said:
> Doesn't 'cat filename.txt > /dev/lp0' work

no since /dev/lp0 is not an executable file.

I just had for 36 hours no Internet connection and therefore no printing
and this
late reply. When connection was restored I can't send mail any more with
exmh or sylpheed????????

Luckily there is mail2web.com

Regards

Peter

--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .


-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Printing with Kernel 2.6.14.4

[Ray Olszewski]

heisspf@skyinet.net wrote:
> thanks Hal!
> 
> altec@kvinet.com said:
> 
>>Doesn't 'cat filename.txt > /dev/lp0' work
> 
> 
> no since /dev/lp0 is not an executable file.
> 
> I just had for 36 hours no Internet connection and therefore no printing
> and this
> late reply. When connection was restored I can't send mail any more with
> exmh or sylpheed????????
> 
> Luckily there is mail2web.com
> 

Peter -- Your response reflects a misunderstanding of the relevant 
permissions. When you redirect output to a file (or a pseudofile like 
the device link /dev/lp0), that destination file need not be executable. 
It just needs to be writable by the uid doing the redirection.

For example, these are the permissions from my stock Debian-Sid setup here:

autovcr@new-flagg:~$ ls -l /dev/lp*
crw-rw----  1 root lp 6, 0 Feb 25  2005 /dev/lp0
crw-rw----  1 root lp 6, 1 Feb 25  2005 /dev/lp1
crw-rw----  1 root lp 6, 2 Feb 25  2005 /dev/lp2

So root and members of group lp can write to these files, but other 
users cannot (they will get "Permission denied" because they lack write 
access, NOT because the file is not executable).

Since I use neither parallel printers nor the particular X application 
your earlier messages referred to, I haven't tried to figure out what 
your problem is. But no one will be able to help you if you don't report 
  accurately the failures (specifically, the associated error messages) 
of the tests that people ask you to run.

Here, for example, where I have no printer attached to lp0, I get 
different failure messages as an ordinary user and as root:

autovcr@new-flagg:~$ cat mencoder_notes.txt > /dev/lp0
-bash: /dev/lp0: Permission denied
autovcr@new-flagg:~$ su
Password:
new-flagg:/home/autovcr# cat mencoder_notes.txt > /dev/lp0
bash: /dev/lp0: No such device

The response I get as autovcr means I don't have write (not execute) 
permission for the file (device). The response I get as root means there 
is no printer attached to the port.

You should be equally specific in your reporting to us. Oh and also try

	cat filename.txt > /dev/lp1

as I have a hazy recollection that some versions of Slackware associated 
lp1, not lp0, with the first parallel port.

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Printing with Kernel 2.6.14.4

[heisspf]

Thanks Ray,

>>Doesn't 'cat filename.txt > /dev/lp0' work
> 
> 
> no since /dev/lp0 is not an executable file.
> 

Ok my mistake. It does work under su, however, not as sudo which I had
tried only.

> as I have a hazy recollection that some versions of Slackware associated 
> lp1, not lp0, with the first parallel port.

It is lp0.

The reason I can't print not being connected with kernel 2.6.14 is, the way
I see it, that there is no provision for a parallel port on "local printer"
set-up, but only for "network printer".

May be I should try to fumble around the source, /usr/src/linux.

Regards

Peter



--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .


-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Printing with Kernel 2.6.14.4

[Hal MacArgle]

On 03-24, heisspf@skyinet.net wrote:
> Thanks Ray,
> 
> >>Doesn't 'cat filename.txt > /dev/lp0' work
> > 
> > 
> > no since /dev/lp0 is not an executable file.
> > 
> 
> Ok my mistake. It does work under su, however, not as sudo which I had
> tried only.
> 
> > as I have a hazy recollection that some versions of Slackware associated 
> > lp1, not lp0, with the first parallel port.
> 
> It is lp0.
> 
> The reason I can't print not being connected with kernel 2.6.14 is, the way
> I see it, that there is no provision for a parallel port on "local printer"
> set-up, but only for "network printer".
> 
> May be I should try to fumble around the source, /usr/src/linux.
> 
> Regards
> 
> Peter

	Greetings: You got my curiosity in gear: I installed
Slackware 10.2, (test26) and it's module library, full install except KDE,
Tex or Games and hooked a Panasonic KX-P2123, Epson mode, printer;
and booted...

	After logging in as root; lsmod reported that parport_pc and
parport were both installed automatically..

	Noting there was one txt file already in root I invoked 'cat
loadlin16c.txt > /dev/lp0' and it printed perfectly.. I created
another txt file of all 60 lines and tried it too; AOK...

	Since default Slack 10.2/26test is 2.6.13; something may have
happened when you bumped up from that?? I don't remember; maybe
you're not using Slackware10.2 here?? As an aside; I've been trying
to install SuSE 10.0 on the same machine, off and on for a week, to
no avail.. Forget which 2.6 patch it defaults to...

	At least I know Slack still works as expected.. I didn't go
any further than that...

-- 

    Hal - in Terra Alta, WV/US - Slackware GNU/Linux 10.1   (2.4.29)
.
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Printing with Kernel 2.6.14.4

[Peter]

Thanks Hal!

As I mentioned in another mail your suggestion of "cat file > /dev/lp0" works 
in root when there is no Internet connection. However, I cannot print when 
disconnected using "cat file | lpr". Giving lpq it will just sit doing nothing 
when not connected.

I installed kernel 2.6.13 and the above is the same. However, there is a 
provision for parallel port for local printer in gnome-cups-manager unlike in 
kernel 2.4.14.4 there is that provision only for Network printer. Beside the 
point with 2.6.13 I have no sound since module snd_via82xx can not be found. 
Beats me.

Regards
-- 
Peter

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Printing with Kernel 2.6.14.4

[Ray Olszewski]

Peter wrote:
> Thanks Hal!
> 
> As I mentioned in another mail your suggestion of "cat file > /dev/lp0" works 
> in root when there is no Internet connection. However, I cannot print when 
> disconnected using "cat file | lpr". Giving lpq it will just sit doing nothing 
> when not connected.

Right. This is pretty consistent with the rest of what you have 
reported. The kernel driver itself works just fine (that's the piece 
that connects the device pseudofile /dev/lp0 to the parallel port, hence 
to the printer). But cupsd (the printer daemon that listens on UDP port 
631 and/or a Unix port) is somehow misconfigured to require networking 
to be active.

One possibility is that your printer database (in /etc/printcap, the one 
lpr uses, or in /etc/cups/printers.conf, the one cupsd uses) is set to 
identify all printers, even local ones, as remote printers. This could 
cause them to become inaccessible if your network interface is not 
configured. You would fix this by fixing printcap &/or printers.conf ... 
I can't be more specific without seeing the actual contents of the files.

A more involved possibility is that for some reason you have cupsd set 
to listen only on the network interface's address and not also on 
localhost (I believe it defaults to listening on all interfaces, so this 
would be a local error; check /etc/cups/cupsd.conf). So if your 
networking is not active ... by which I mean eth0 (or perhaps ppp0) is 
not configured (which could happen if you get it configured via DHCP (or 
PPPoE) ... I don't know the details of your Internet connection, so I'm 
guessing pretty openly here) ... there is no place for cupsd to listen.

Check this with "netstat -ln |grep 631" to see what cupsd is listening 
on. Check this when you are not connected to the network (with the exact 
meaning of "not connected" being the state your host was in when it 
would not print). If cupsd is listening properly, you should see 
something about like this:

	udp        0      0 0.0.0.0:631             0.0.0.0:*

If you don't then your problem is a misconfiguration of CUPS and 
networking. I can't tell you how to fix this without seeing your system 
setup, but look at whatever init script starts cupsd, as well as 
cupsd.conf, to see if either is limiting the interfaces cupsd will 
listen on.

Depending on lpr expects about printers (from their printcap entries), 
it may also fail if there is nothing listening on port 515/tcp.

All of this really is just a bunch of guesses, though.

> I installed kernel 2.6.13 and the above is the same. However, there is a 
> provision for parallel port for local printer in gnome-cups-manager unlike in 
> kernel 2.4.14.4 there is that provision only for Network printer. 

I'm a bit confused here, Peter. CUPS is a service for managing access to 
printers (an alternative to lpd), not part of a kernel. I can well 
imagine that the versions of Slackware that install the two kernels are 
different enough that they also have different versions of CUPS. But 
once more, this is NOT a kernel problem, at least not from what you are 
reporting about your tests.

> Beside the 
> point with 2.6.13 I have no sound since module snd_via82xx can not be found. 
> Beats me.

Are you using OSS or ALSA sound? From kernel source (I actually checked 
2.6.11, not .13), the relevant OSS module appears to be SOUND_VIA82CXXX. 
But 2.6.x kernels are supposed to use ALSA sound, with the relevant name 
the one you list (snd-via82xx).

I'm not quite sure what your phrase "module snd_via82xx can not be 
found" means. Do you mean that the kernel fails to load it? Or that you 
yourself cannot find snd-via82xx.ko, by a manual search, in 
/lib/modules/2.6.13? Or that it is not listed in 
/lib/modules/2.6.13/modules.dep? Or something else?

You may need to check whether Slackware provides modules for precompiled 
kernels in multiple packages. I can't think of any other reason why a 
precompiled 2.6.x kernel should be missing this module. (Well, I suppose 
it could be compiled in directly, but then your sound should work ... 
and that's not a very usual practice except for embedded systems.

> 
> Regards

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Printing with Kernel 2.6.14.4

[Peter]

On Mon, 27 Mar 2006 21:20:07 -0800
Ray Olszewski <ray@comarre.com> wrote:

> Peter wrote:
> > Thanks Hal!
> > 
> > As I mentioned in another mail your suggestion of "cat file > /dev/lp0"
works 
> > in root when there is no Internet connection. However, I cannot print when
> > disconnected using "cat file | lpr". Giving lpq it will just sit doing
>> nothing  when not connected.
> 
> Right. This is pretty consistent with the rest of what you have 
> reported. The kernel driver itself works just fine (that's the piece 
> that connects the device pseudofile /dev/lp0 to the parallel port, hence 
> to the printer). But cupsd (the printer daemon that listens on UDP port 
> 631 and/or a Unix port) is somehow misconfigured to require networking 
> to be active.
> 
> One possibility is that your printer database (in /etc/printcap, the one 
> lpr uses, or in /etc/cups/printers.conf, the one cupsd uses) is set to 
> identify all printers, even local ones, as remote printers. This could 
> cause them to become inaccessible if your network interface is not 
> configured. You would fix this by fixing printcap &/or printers.conf ... 
> I can't be more specific without seeing the actual contents of the files.

# Printer configuration file for CUPS v1.1.23                                 
# Written by cupsd on Tue Mar 28 15:21:02 2006                              
<DefaultPrinter 24-Pin-Series>                                            
Info 24-Pin-Series                                                      
DeviceURI epson:/dev/lp0                                              
State Idle                                                          
Accepting Yes                                                     
JobSheets none none                                             
QuotaPeriod 0                                                 
PageLimit 0                                                 
KLimit 0                                                  
</Printer> 

> A more involved possibility is that for some reason you have cupsd set 
> to listen only on the network interface's address and not also on 
> localhost (I believe it defaults to listening on all interfaces, so this 
> would be a local error; check /etc/cups/cupsd.conf). So if your 
> networking is not active ... by which I mean eth0 (or perhaps ppp0) is 
> not configured (which could happen if you get it configured via DHCP (or 
> PPPoE) ... I don't know the details of your Internet connection, so I'm 
> guessing pretty openly here) ... there is no place for cupsd to listen.

I have a broadband connection via DHCP

> Check this with "netstat -ln |grep 631" to see what cupsd is listening 
> on. Check this when you are not connected to the network (with the exact 
> meaning of "not connected" being the state your host was in when it 
> would not print). If cupsd is listening properly, you should see 
> something about like this:

sudo /etc/rc.d/rc.inet1 stop
heisspf@~:$ netstat -ln |grep 631
tcp        0      0 0.0.0.0:631             0.0.0.0:*               LISTEN    
udp        0      0 0.0.0.0:631             0.0.0.0:*

sudo /etc/rc.d/rc.inet1 start
heisspf@~:$ netstat -ln |grep 631
tcp        0      0 0.0.0.0:631             0.0.0.0:*               LISTEN    
udp        0      0 0.0.0.0:631             0.0.0.0:*

There seems to be no difference


> 	udp        0      0 0.0.0.0:631             0.0.0.0:*
> 
> If you don't then your problem is a misconfiguration of CUPS and 
> networking. I can't tell you how to fix this without seeing your system 
> setup, but look at whatever init script starts cupsd, as well as 
> cupsd.conf, to see if either is limiting the interfaces cupsd will 
> listen on.

On separate mail I am sending to you /etc/rc.d/rc.cupsd as an attachment.

This is from cupsd.conf which I have never touched.

# Listen to (Port/Listen)                                                     
#                                                                           
# Ports/addresses that are listened to.  The default port 631 is reserved 
# for the Internet Printing Protocol (IPP) and is what is used here.    
#                                                                     
# You can have multiple Port/Listen lines to listen to more than one
# port or address, or to restrict access.                         
#                                                               
# Note: Unfortunately, most web browsers don't support TLS or HTTP Upgrades   
# for encryption.  If you want to support web-based encryption you will     
# probably need to listen on port 443 (the "HTTPS" port...).              
#                                                                       
# ex: 631, myhost:80, 1.2.3.4:631                                      
#                                                                     
#    Port 80                                                         
#    Port 631                                                       
#    Listen hostname                                               
#    Listen hostname:80                                           
#    Listen hostname:631                                         
#    Listen 1.2.3.4                                             
#    Listen 1.2.3.4:631                                        
#                                                            
#Port 631                                                   
                                                                              
Listen *:631    


> Depending on lpr expects about printers (from their printcap entries), 
> it may also fail if there is nothing listening on port 515/tcp.
> 
> All of this really is just a bunch of guesses, though.
> 
> > I installed kernel 2.6.13 and the above is the same. However, there is a 
> > provision for parallel port for local printer in gnome-cups-manager unlike
in 
> > kernel 2.4.14.4 there is that provision only for Network printer. 

This does not hold any longer after I enabled paraport_pc and lp modules in
rc.modules.

> I'm a bit confused here, Peter. CUPS is a service for managing access to 
> printers (an alternative to lpd), not part of a kernel. I can well 
> imagine that the versions of Slackware that install the two kernels are 
> different enough that they also have different versions of CUPS. But 
> once more, this is NOT a kernel problem, at least not from what you are 
> reporting about your tests.
> 
> > Beside the 
> > point with 2.6.13 I have no sound since module snd_via82xx can not be
found. 
> > Beats me.
> 
> Are you using OSS or ALSA sound? From kernel source (I actually checked 
> 2.6.11, not .13), the relevant OSS module appears to be SOUND_VIA82CXXX. 
> But 2.6.x kernels are supposed to use ALSA sound, with the relevant name 
> the one you list (snd-via82xx).

I am using ALSA

> I'm not quite sure what your phrase "module snd_via82xx can not be 
> found" means. Do you mean that the kernel fails to load it? Or that you 
> yourself cannot find snd-via82xx.ko, by a manual search, in 
> /lib/modules/2.6.13? Or that it is not listed in 
> /lib/modules/2.6.13/modules.dep? Or something else?

That is the message on booting. FATAL failed to load module snd_via82xx 
 
> You may need to check whether Slackware provides modules for precompiled 
> kernels in multiple packages. I can't think of any other reason why a 
> precompiled 2.6.x kernel should be missing this module. (Well, I suppose 
> it could be compiled in directly, but then your sound should work ... 
> and that's not a very usual practice except for embedded systems.
> 

I just went back to kernel 2.6.14.4 where all snd.... modules are loaded.
 
Regards
Peter

-- 
Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Printing with Kernel 2.6.14.4

[Peter]

On Tue, 28 Mar 2006 07:42:21 -0500
David Fierbaugh <david@fierbaugh.org> wrote:

> With cups apparently running, and root having the ability to print manually,

> try configuring your printer with cups web based tool.
> 
> Point your favorite web browser to 'http://localhost:631/'. This should open

> cups configuration. The login will probably be root and your root password, 
> this can be changed later, after you get printing working. From there you
can 
> add/change/delete printers and their settings. You can also print test pages

> from cups once you've got a printer setup correctly.
> 
Thanks!
I have done all this. Now I tried it again adding a new printer,  then w/o
being connected to print a test. It will just sit and wait and wait. So I
closed the page http://localhost:631/admin and tried to open it again w/o
being connected. The result was the machine froze, keyboard, second hand on
clock and I had to do a reset.

Regards

-- 
Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Printing with Kernel 2.6.14.4

[Peter]

Just want to inform, the problem that I could not print offline was solved 
with the help of a  certain Jorgeu from Venezuela, in Dropline-Gnome-Forum, 
Slackware Discussions under "Unable to Print Offline".

Jorgeu asked me what the output is of /sbin/route when offline. There was 
none. From which he concluded correctly that it is a loopback configuration 
issue.

He told me then to input the following command:

# route add 127.0.0.0 dev lo

and behold Jorgeu was right: And you should be printing offline without 
problems.

And it seems to hold. This morning when I bootet I was offline and could print.

Thank you Jorgeu!!
-- 
Peter

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs