Tiny Core Linux
Tiny Core Extensions => TCE Q&A Forum => Topic started by: Multitudes on October 06, 2009, 03:44:14 PM
-
After many searches here on the forum and (most of the rest of) internet I am unable to figure out my problem and need a little help.
I'm running TC 2.3.1 only with kmaps and Opera mounted during startup. After startup I mount Beaver, Emelfm, wireless-2.6.29.1-tinycore, wireless_tools and wl.
If I load cups.tcel (ver. 1.3.8) locally printing works fine on my network attached hp laserjet 1300n (socket connection).
I can print a test page from CUPS, a file from terminal and a file from beaver.
If I mount cups.tczl (ver. 1.4.1) it doesn't work:
If I try to print a test page from CUPS I get an error saying "Unsupported format 'application/vnd.cups-banner'!".
The job list is empty.
If I try to print a file from terminal lpd responds "lp: successful -ok" but the job list shows that the job was cancelled immediately after it was created.
If I try to print a file from Beaver it is also cancelled.
CUPS error_log:E [06/Oct/2009:21:03:37 +0000] Unable to open listen socket for address ::1:631 - Address family not supported by protocol.
E [06/Oct/2009:21:04:33 +0000] Request from "localhost" using invalid Host: field "box:631"
E [06/Oct/2009:21:04:33 +0000] Request from "localhost" using invalid Host: field "box:631"
E [06/Oct/2009:21:04:33 +0000] Request from "localhost" using invalid Host: field "box:631"
E [06/Oct/2009:21:04:50 +0000] [CGI] smbclient not found!
E [06/Oct/2009:21:04:50 +0000] [CGI] rpcclient not found!
E [06/Oct/2009:21:06:10 +0000] [cups-driverd] Unable to open driver directory "/usr/local/lib/cups/driver": No such file or directory
E [06/Oct/2009:21:06:22 +0000] [cups-driverd] Unable to open driver directory "/usr/local/lib/cups/driver": No such file or directory
E [06/Oct/2009:21:07:08 +0000] Returning IPP client-error-document-format-not-supported for Print-Job (ipp://localhost:631/printers/hplj1300) from localhost
E [06/Oct/2009:21:28:15 +0000] Returning IPP client-error-document-format-not-supported for Send-Document (ipp://localhost:631/printers/hplj1300) from localhost
I'll be more whan willing to supply additional information in case anyone of you have a clue.
Thanks in advance!
/Multitudes
-
You're right. CUPS 1.4 in the tczl package is broken several ways. You are best to stick with 1.3.8.
-
Too bad.
I read that tce(l) will be phased out in the upcoming TC 2.4.
/Multitudes
-
I converted the CUPS 1.3.8 tce package to a tcz and installed it in TC 2.4rc4. It works fine.
-
Quoting from http://www.linuxforums.org/forum/mandriva-linux-help/151962-solved-cups-printing-error-request-localhost-using-invalid-host-field.html
Request from "localhost" using invalid Host: field "::1"
.
A bit of searching led to a few such CUPS related errors, all posted after recent upgrades (mostly since April). The solutions varied... I did the following to get it to work:
Open /etc/cups/cupsd.conf
Add the line "ServerAlias *"
Add the line "Port 631"
Add the line "Listen /var/run/cups/cups.sock"
Save the file and restart cups ("/etc/init.d/cups restart").
If that works, maybe it should be added to the extension.
-
Quoting from http://www.linuxforums.org/forum/mandriva-linux-help/151962-solved-cups-printing-error-request-localhost-using-invalid-host-field.html
Request from "localhost" using invalid Host: field "::1"
.
A bit of searching led to a few such CUPS related errors, all posted after recent upgrades (mostly since April). The solutions varied... I did the following to get it to work:
Open /etc/cups/cupsd.conf
Add the line "ServerAlias *"
Add the line "Port 631"
Add the line "Listen /var/run/cups/cups.sock"
Save the file and restart cups ("/etc/init.d/cups restart").
If that works, maybe it should be added to the extension.
I tried it but got the same result as before.
/Multitudes
-
with cups 1.3.8 and tc 2.4rc5 i noticed that cups_start.sh has to be loaded as root, and that it points to /etc/init.d/cupsd which does not exist; i did the following:
tc@box:~$ sudo cups_start.sh
aterm: can't load color "dark", colorID = 1, (29)
sudo: /etc/init.d/cups: command not found
i did not understand this error message, but it points me to the solution; after it, i did:
tc@box:~$ cups_start.sh
4486 tc grep cupsd
sudo: /etc/init.d/cups: command not found
tc@box:~$ kill 4486
sh: cannot kill pid 4486: No such process
and then:
tc@box:~$ sudo /usr/local/sbin/cupsd
it made me able to log into cups and to print without issue; i have tried the new cups extension, but i can't print probably because the usb port of my printer won't be catched up (even if i can set the printer with the cups frontend).
-
..but where did you take the extension with cups-1.3.8 from?
The cups.tcz extension is cups-1.4.1, if you have a previous tcz extension using cups-1.3.8, it will contain a user.tar.gz file which will not be processed properly by tc-2.4.
-
yes, i use the old cup.tcz extension, and it seems to behave adequately with the hitches mentionned in my post; i tried the new one, but after spending 3 hours to configure and reconfigure the (usb) printer with cups and lp without success, i gave out; with the new extension, my problem was:
1. cupsd started as expected;
2. lsusb see the printer
3. i use a ppd file and have had no problem with the configuration of the printer with cups frontend;
but: i tried to print, cups stores the job, but didn't print anything; i think that it can't read the usb port, but didn't investigate further.
-
but: i tried to print, cups stores the job, but didn't print anything; i think that it can't read the usb port, but didn't investigate further.
..as per google, you probably need to "rmmod" the usblp kernel module and even then there may be a problem with cups expecting the usb device to be owned by "lp:lp" rather than "tc:staff" (even though it was compiled to expect tc:staff).
I believe Pethie is just finishing up a cups-1.3.11 extension for users that cannot use the cups (1.4.1) extension.
-
which version of cups 1.4.1 did you compile? i ask because it seems that only 1.4.1-4 unstable came out with the usb bug corrected (since it seems to be a bug); for the moment, i remain with cups 1.3.8 since it is not a big deal to set the path of cupsd right.
-
Thanks for the info - It was the official cups-1.4.1 - I think I'll wait until there is a finalised update before looking at this again.
-
i made a script for those who want to keep on using cups 1.3.8 (the older extension one) with tc/mc 2.4; the script replaces cups_start.sh default; the script set the right path for cupsd and prompt for root password; you can label it 'cups' and save it in your /home/tc, calling it with ./cups (for example):
#!/bin/sh
#
# Check if root password is set
# and prompt to set if not
#
if sudo grep "root:[$]1[$]EbR327ag[$]" /etc/shadow 2>&1 >/dev/null; then
xterm -title "Set Root Password" -e sudo passwd
fi
#
# Check if cups is started
# and start/restart
#
if ! ps | grep cupsd; then
sudo /usr/local/sbin/cupsd
fi
#
# Start cups browser interface
#
#exec /usr/local/bin/opera http://localhost:631 &
#
#EOF
-
I believe Perthie is just finishing up a cups-1.3.11 extension for users that cannot use the cups (1.4.1) extension.
Done and submitted!