Page 1 of 1

SOLVED: CUPS and 32 bit porteus 2.0

Posted: 09 Mar 2013, 20:30
by francois
Essentially the problem is the same as reported for the 64 bit version:
http://forum.porteus.org/viewtopic.php? ... &p=13644#p

As before, there was no problem using the gutenprint-postscipt solution to install printers with porteus 1.2. All you had to do was to install 1) gutenprint, 2) ghostscript and 3) ghostscript-fonts and you were able to install quite a number of manufactured brands on porteus.

With porteus v. 2.0, booting without changes from hdd, with those packages into optional folder, in addition to the 4) cups module from slax 7.05 (that I picked within the system-config-printer bundle), I activate 1, 2, and 3 and get an error at print test:
Unable to print test page:

Unsupported format "application/vnd.cups-banner".
After that if I activate 4 (slax cups module), the print test will work.

I have repeated the procedure many times. with a basic porteus 2.0 razor, with the same results.

Re: CUPS and 32 bit porteus 2.0

Posted: 09 Mar 2013, 21:47
by brokenman
I'll have to checkout Quax's module to see where the difference is. We use a stock standard slackware cups package (minus the documentation) so perhaps Quax has added some extra file.

Re: CUPS and 32 bit porteus 2.0

Posted: 10 Mar 2013, 01:52
by francois
Thanks to you brokenman. I would appreciate the details of the difference if there is. I am quite interested in the topic. :)

Re: CUPS and 32 bit porteus 2.0

Posted: 10 Mar 2013, 14:53
by brokenman
The mediafire link to Quax's module is dead. Any chance to re-upload?

EDIT: Ok i tracked down the .sb file and compared against stock slackware.

The only difference appears to be some files in /run that start/stop the cups service when the module is activated/deactivated.

Code: Select all

/etc/rc.d/rc.cups start

Re: CUPS and 32 bit porteus 2.0

Posted: 10 Mar 2013, 17:53
by francois
Sorry I thought you saw them (including 1720-cups.sb) in my other thread on system-config-printer:
http://forum.porteus.org/viewtopic.php?f=61&t=1994

I had to install slax 7.05 to download them.

Here is 1720-cups.sb or xzm:
http://www.mediafire.com/?uzg1bvc8zc1c9vt

Re: CUPS and 32 bit porteus 2.0

Posted: 19 Mar 2013, 08:10
by fanthom
@francois
any update on this?
maybe you could test 64bit edition as according to cttan printing works (so maybe only 32bit build is affected):
http://forum.porteus.org/viewtopic.php? ... =30#p13834
(wish i had a printer around so i could test it myself, never printed anything under Linux)

Re: CUPS and 32 bit porteus 2.0

Posted: 19 Mar 2013, 21:50
by francois
@fanthom:
Hello fanthom. The best estimate about what is going on seems to be given from one of my comments on the post you cite:
@Bjornar:
Thanks for reporting your experience. You give us food for thought. Maybe I was on the wrong path, but I am not that sure. It might be possible that gutenprint-ghjostscript is not compatible with the actual cups version. Some more testing will be needed. Unless we get testimonies from others, and this might be the case for cttan.

Bjornar observation would mean that the (HOW TO) CUPS: adding lpr and cupswrapper drivers is still the way to go for now with porteus 2.0:
viewtopic.php?f=39&t=843&p=7510&hilit=ADDING+LPR#p7510

Until the issue with gutenprint-ghostscript method with CUPS could be debugged. On my part, I will not be able to look at it before the weekend.

@cttan:
Have you been able to install some printer with the gutenprint and ghostscript packages using porteus version 2.0?
The answer from cttan was:
Hi francois,

Yes. I am still able to use gutenprint driver and ghostscript to print to my Canon MP145 USB printer.
As for my office printer, currently it is Konica Minolta C420 copier+printer which I use the driver from Konica Minolta website. The step to insert the printer is shown in above post.
And I imagine that cttan meant that he was working with porteus 2.0 though he did not mention it.

I cannot explain why blaze and EdP and tadatma are not able to get their printer to go for now:
http://forum.porteus.org/viewtopic.php?f=74&t=1989
http://forum.porteus.org/viewtopic.php?f=81&t=1873
http://forum.porteus.org/viewtopic.php?f=61&t=1983

I would need to work on the different solutions: installing single printer drivers, installing printer drivers thru gutenprint-ghostscript once more. I know that it bugs when I use the gutenprint-ghostscript solution for me since porteus 2.0. The problem is that I have b stuck in a period of overwork in the last few weeks.

Cttan is really good at it, he seems to know more than me or at least he has some knowledge I do not have.

Conclusion: maybe the problem is with gutenprint or ghostscript.

Re: CUPS and 32 bit porteus 2.0

Posted: 20 Mar 2013, 17:12
by francois
One way to help me, and save me a lot of time, would be to provide me with porteus 2.0 without cups in the base system. Is this easily feasable? I would need it for both 64 bit and 32 bit editons.

Thanks :)

Re: CUPS and 32 bit porteus 2.0

Posted: 20 Mar 2013, 18:33
by fanthom
you can do it yourself with a little trick:
please boot in 'always fresh' mode -> switch to root -> run 'removepkg cups' to delete this package from the system.

there is one disadvantage of this approach:
in case of adding new cups to the system you cant use 'activate cups.xzm' anymore. you must unpack cups.xzm and copy files to the system manually:

Code: Select all

unsquashfs cups.xzm && cd squashfs-root && cp -a * /
reason: writable aufs branch (tmpfs in this case) will "remember" that cups files were deleted from 002-xorg.xzm. injecting new cups module would place it under top branch (tmpfs) so files are still not visible.
copying files (instead of activation) resolves this problem.

btw: other modules (like gutenprint, ghostscript, etc) can be activated normally.

Re: CUPS and 32 bit porteus 2.0

Posted: 22 Mar 2013, 11:09
by francois
No evident results yet. :(

I will have to dwelve more systematically into it this weekend. cttan is seems to be using gutenprint version different than mine.

Re: CUPS and 32 bit porteus 2.0

Posted: 22 Mar 2013, 22:28
by francois
Finally, everything is ok. I was just induced on the wrong path by a few member's comments, in addition to using a old version of gutenprint that worked with previous porteus version 1.2. See printing:
viewtopic.php?f=81&t=1873&start=45

Sorry about that. :oops:

A good thing is to cite the distinguished and honorable fanthom:
http://forum.porteus.org/viewtopic.php?f=46&t=1996
fanthom wrote: taking this opportunity i'll remind about main rule when upgrading Porteus (i believe it applies to every other linux distros as well):

Code: Select all

- when you upgrade between major Porteus releases (1.x->2.x, 2.x -> 3.x) then you must upgrade your ALL existing modules. you should also start with fresh save.dat as settings may not be compatible anymore.
- when you upgrade between minor Porteus releases (2.x -> 2.x) then everything should work out of the box but still some incompatibility may happen.