WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: Cups Print Server  (Read 22225 times)

Offline SamK

  • Hero Member
  • *****
  • Posts: 713
Re: Cups Print Server
« Reply #30 on: April 07, 2011, 05:59:32 AM »
...I did not see any auto detect setting...
If it exists, it is quite likely that the IRQ fixed/auto-handling (not auto detect) toggle switch may be on a different BIOS configuration page as it refers to the entire machine, not just the parallel port.

...i'll boot the old pc up with just the tinycore linux boot cd and check with:
Code: [Select]
lsmod | grep lp
This should not appear unless you have previously manually loaded the module with
Code: [Select]
sudo modprobe lp

As an aside...
Both EPP and ECP were improvements in data transfer rates beyond those of a standard parallel port.  ECP is just fine if it's working with your kit.  I mentioned EPP as it appears to work most often with the equipment here.
 
« Last Edit: April 07, 2011, 08:33:25 AM by SamK »

Offline remus

  • Sr. Member
  • ****
  • Posts: 371
Re: Cups Print Server
« Reply #31 on: April 07, 2011, 08:31:41 PM »
Clean boot of tcl3.5.1 on pc with p4 cpu gives the following lsmod output
Code: [Select]
Module                  Size  Used by    Not tainted
vfat                    5596  1
fat                    30220  1 vfat
squashfs               14728  0
ppdev                   3732  0
scsi_wait_scan           276  0
parport_pc             18656  0
tg3                    84024  0
ramzswap               10240  1
parport                18560  2 ppdev,parport_pc
libphy                  8596  1 tg3
loop                    8068  0

I did not find anything in the BIOS regarding Auto handling of irq's its very ancient isn't it ;) I've set the Parallel port settings to EPP - 378/IRQ7 and I've tried ECP and the lsmod is always the same, see bellow.

Clean boot of tcl3.5.1 on pc with p2 cpu gives the following lsmod output
Code: [Select]
Module                  Size  Used by    Not tainted
squashfs               14728  0
scsi_wait_scan           276  0
ramzswap               10240  1
loop                    8068  0
e100                   19332  0

This is no big deal. I now have the info to use lsmod, and know to look for
Code: [Select]
parport                18560  2 ppdev,parport_pc
when trying to setup a parallel port printer with cups, and I know how to fix it by adding sudo modprobe parport_pc to my /opt/bootlocal.sh file :)

Regarding extra driver extensions.
I've removed both poppler-bin.tcz , ghostscript.tcz from OnBoot and everything works fine. I will keep some documentation that those extensions might be needed in the future to make things easier.

I can connect to the printer server via a windows xp computer and can print fine :)

Everything is working fine here now.

All thats left to do is write up a howto for next time.

Thanks to everyone for their input and advice.

I even learnt some new stuff.
Live long and prosper.

Offline remus

  • Sr. Member
  • ****
  • Posts: 371
Re: Cups Print Server
« Reply #32 on: April 10, 2011, 10:39:30 PM »
Hey Juanito,

Quote
I'm guessing that was the problem, i.e. that pstoraster needs gs, which in turn needs gs_init.ps in this context, which is in ghostscript_common

I'm wondering how you know about the dependencies, did you do a particular type of google search or did you know from experience ?
Live long and prosper.