Re: FreeBSD 5.1, Cups problem
Indeed, we have a big problem getting CUPS to work with FreeBSD 5.1. The root of the problem is in the fact that it does not install properly! (I think this is completely the responsibility of the folks at FreeBSDMall, who clearly didn't test the system they sell in the box!) I suppose I should have (and still should) written all the steps I had to do to get it working. So, here's a list of what I remember having to do, and why: 1) The software expects to be installed in /usr/sbin, but FreeBSD's version puts it in /usr/local/sbin. If that isn't in your path, none of the command line stuff will work, and this includes even starting cupsd or using lpadmin. 2) CUPS expects its config files and other stuff to be in /etc/cups, but FreeBSD puts that stuff in /usr/local/etc/cups. This means that even if you make the path correct for finding the program, it won't find any of its control or configuration files and will die almost instantly if you start it from a shell. 3)CUPS expects its spool file directory to be in /var/spool/cups, but FreeBSD5.1 puts similar stuff below /var/spool/output, so you might want to continue this philosophy by creating /var/spool/output/cups. Neither of these dirs exist or are created when you install cups. You can decide which one of them you want to use and create it... but don't forget to give it and its sub parts (I'll talk about them shortly) the proper owner:group (either root:daemon or daemon:daemon, your choice). You'll need a sub-dir called tmp with the same owner attribs below where ever you create the cups dir. 4) Cups requires (even if you aren't using certificates) a sub-dir to the /usr/local/etc/cups dir called certs, and the ownership requirements are the same as in 3, above. If the dir isn't there, cupsd won't get far before dying somewhat ungracefully, and it isn't created by default... you have to do it. 5) The cupsd.conf that comes with the installation isn't aware of any of the above misplacements or that any of this might be missing. Thus, it has to be edited. I've attached the version I am successfully using now to this message. You'll almost certainly have to change it to fit where you decide to put things, but it's a good start. Be aware of the error reporting level parts of this file, as they can help you a lot when you've finally got to the point where you can start the program. You'll want to tone it down later, after things are up and running smoothly, but having it fairly verbose can really help a lot at first. 6) The printers.conf, mime.types, .convs and other .conf files all go in the /usr/local/etc/cups dir. You'll also probably have to create a ppd directory under /usr/local/etc/cups, as well, as I don't believe it got created automagically. 7) If you're using any of the more recent printers (one of mine is an HP deskjet 960c) that isn't in the hpijs add-on to gs, you'll have to go get them and put them into the ppd dir mentioned in step 6. If you get this far and are having trouble figuring out what needs to go where to do this part, let me know and I'll send another message with the specifics of what I did to get it to work. 8) Finally, cups expects its control script file to be in /etc/rc.d, and that it will be named cups.sh If you look hard enough through the documentation, you can find that there is supposed to be a file there called cups.sh.sample that you can edit and rename or copy for your installation to make it work. This is a really idiotic chicken and egg situation, as you can normally only see the documentation to find this out if you can run the cups daemon and get to the web pages at port 631, but you really should start and control the daemon with the shell script. It's almost funny, in a really sadistic way. In any event, you can either search around and find the sample file, edit it and move it to /usr/local/etc/rc.d, or use the one attached here and put it in that dir. Don't forget where you put it... you may want to either edit it or use it later! 9) With all this done, I believe you will be able to do /usr/local/etc/rc.d/cups.sh start and the beast should come alive. You can then point your favorite browser at http://localhost:631 and you should see the nice cups web control interface. If you don't, have a look at /var/log/messages, or where ever you told cups to put its error messages in the cupsd.conf file, and you will probably get something meaningful in the way of an error message that will lead you to fix something. (This is especially true if I left anything out here, but I hope I didn't.) Then you can try again. I hope this helps you (and anyone else struggling with this problem). I got wonderful advice (and patience) from Peter Ulrich Kruppa in Germany. Without his pointers, I'd still be fighting with this thing! Certainly, if you have further questions about the cups installation on FreeBSD5.1, let me know and I'll
New name for Floppy disk devices?
OK, so sometimes serial devices that one would expect to have names in /dev like sio0 or sio1 are now called cuaa0 or cuaa1 (for reasons beyond my understanding). Now I can see my floppy disk in the dmesg output, but there doesn't appear to be an fdc0 in /dev. Did floppy disk devices get renamed, too, or is it hiding somewhere else, or did it, for some unknown reason, just vanish? I'm trying to create a floppy disk boot pair, and can't write to a device I can't find. Help? -Lyman ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Adding SCSI Scanner
I didn't have my SCSI scanner (UMAX Astra 1200S) powered up when I loaded FreeBSD 5.1. I turned it on and re-booted the system, and it certainly sees it (as seen in the dmesg report), but it simply says it's part of pass4:... in other words, no driver associated with it. Is there some nice way of getting the system to use it, other than reloading the entire system from scratch? The system has been up a few days and I've loaded a lot of other good stuff and got it running just the way I want it to, so reloading and reconfiguring all of it would be a lotta work. -Lyman ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
ScreenSavers in KDE 3.0 under FreeBSD 5.1
kcontrol (the Control Center) doesn't seem to know where the xscreesavers are, and only gives me the choice to use BlankScreen. How does one inform KDE of where the screensavers reside? I know where they are... but don't know how to tell this to KDE. This has to be a common problem, but I'm not at all sure where to search for the answer. If there's a FAQ that has this in it, please point me in its direction. Thanks! -Lyman ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Nasty hardware problem...
I trying to bring up a file server a system with a 1.5GHz AMD Athlon, 256MB RAM, an older AHA2940 SCSI card with an IBM DDYS-T18350N hard drive. The hard drive is connected to the second channel (the Ultra-wide channel) on the 2940. During the boot process (from the dmesg) the machine stops with a SCSI Status Error (Check Condition) saying it refuses Tagged commands. The boot system appears to then go into untagged mode and finds that the SCSI card has been RESET. There follows a dump of the card, which I have attached here. Could this be because the data rate frequency is set too high? I lowered it from 20MB/s to 16MB/s, but I could go as low as 10MB/s. On the other hand, that may have nothing to do with the problem. This is kind of a shot in the dark, I know... but someone out there in FreeBSD land might have seen something like this before. Please forgive the long message. -Lyman Dec 2 21:10:55 Cogitek-UX2 kernel: Dump Card State Begins Dec 2 21:10:55 Cogitek-UX2 kernel: ahc0: Dumping Card State in Message-in phase, at SEQADDR 0x1bf Dec 2 21:10:55 Cogitek-UX2 kernel: Card was paused Dec 2 21:10:55 Cogitek-UX2 kernel: ACCUM = 0x0, SINDEX = 0x31, DINDEX = 0xc0, ARG_2 = 0x8 Dec 2 21:10:55 Cogitek-UX2 kernel: HCNT = 0x0 SCBPTR = 0x7 Dec 2 21:10:55 Cogitek-UX2 kernel: SCSISIGI[0xe6]:(REQI|BSYI|MSGI|IOI|CDI) ERROR[0x0] Dec 2 21:10:55 Cogitek-UX2 kernel: SCSIBUSL[0x80] LASTPHASE[0xe0]:(MSGI|IOI|CDI) SCSISEQ[0x12]:(ENAUTOATNP|ENRSELI) Dec 2 21:10:55 Cogitek-UX2 kernel: SBLKCTL[0x2]:(SELWIDE) SCSIRATE[0x0] SEQCTL[0x10]:(FASTMODE) Dec 2 21:10:55 Cogitek-UX2 kernel: SEQ_FLAGS[0xc0]:(NO_CDB_SENT|NOT_IDENTIFIED) SSTAT0[0x7]:(DMADONE|SPIORDY|SDONE) Dec 2 21:10:55 Cogitek-UX2 kernel: SSTAT1[0x3]:(REQINIT|PHASECHG) SSTAT2[0x0] SSTAT3[0x0] Dec 2 21:10:55 Cogitek-UX2 kernel: SIMODE0[0x0] SIMODE1[0xac]:(ENSCSIPERR|ENBUSFREE|ENSCSIRST|ENSELTIMO) Dec 2 21:10:55 Cogitek-UX2 kernel: SXFRCTL0[0x88]:(SPIOEN|DFON) DFCNTRL[0x4]:(DIRECTION) Dec 2 21:10:55 Cogitek-UX2 kernel: DFSTATUS[0x6d]:(FIFOEMP|DFTHRESH|HDONE|FIFOQWDEMP|DFCACHETH) Dec 2 21:10:55 Cogitek-UX2 kernel: STACK: 0x144 0x0 0x191 0x199 Dec 2 21:10:55 Cogitek-UX2 kernel: SCB count = 70 Dec 2 21:10:55 Cogitek-UX2 kernel: Kernel NEXTQSCB = 69 Dec 2 21:10:55 Cogitek-UX2 kernel: Card NEXTQSCB = 69 Dec 2 21:10:55 Cogitek-UX2 kernel: QINFIFO entries: Dec 2 21:10:55 Cogitek-UX2 kernel: Waiting Queue entries: 15:32 Dec 2 21:10:55 Cogitek-UX2 kernel: Disconnected Queue entries: 8:34 11:36 5:2 3:59 13:53 6:41 0:15 10:8 1:38 12:35 9:9 2:1 4:40 14:33 Dec 2 21:10:55 Cogitek-UX2 kernel: QOUTFIFO entries: Dec 2 21:10:55 Cogitek-UX2 kernel: Sequencer Free SCB List: 7 Dec 2 21:10:55 Cogitek-UX2 kernel: Sequencer SCB Info: Dec 2 21:10:55 Cogitek-UX2 kernel: 0 SCB_CONTROL[0x64]:(DISCONNECTED|TAG_ENB|DISCENB) SCB_SCSIID[0x87]:(TWIN_CHNLB) Dec 2 21:10:55 Cogitek-UX2 kernel: SCB_LUN[0x0] SCB_TAG[0xf] Dec 2 21:10:55 Cogitek-UX2 kernel: 1 SCB_CONTROL[0x64]:(DISCONNECTED|TAG_ENB|DISCENB) SCB_SCSIID[0x87]:(TWIN_CHNLB) Dec 2 21:10:55 Cogitek-UX2 kernel: SCB_LUN[0x0] SCB_TAG[0x26] Dec 2 21:10:55 Cogitek-UX2 kernel: 2 SCB_CONTROL[0x64]:(DISCONNECTED|TAG_ENB|DISCENB) SCB_SCSIID[0x87]:(TWIN_CHNLB) Dec 2 21:10:55 Cogitek-UX2 kernel: SCB_LUN[0x0] SCB_TAG[0x1] Dec 2 21:10:55 Cogitek-UX2 kernel: 3 SCB_CONTROL[0x64]:(DISCONNECTED|TAG_ENB|DISCENB) SCB_SCSIID[0x87]:(TWIN_CHNLB) Dec 2 21:10:55 Cogitek-UX2 kernel: SCB_LUN[0x0] SCB_TAG[0x3b] Dec 2 21:10:55 Cogitek-UX2 kernel: 4 SCB_CONTROL[0x64]:(DISCONNECTED|TAG_ENB|DISCENB) SCB_SCSIID[0x87]:(TWIN_CHNLB) Dec 2 21:10:55 Cogitek-UX2 kernel: SCB_LUN[0x0] SCB_TAG[0x28] Dec 2 21:10:55 Cogitek-UX2 kernel: 5 SCB_CONTROL[0x64]:(DISCONNECTED|TAG_ENB|DISCENB) SCB_SCSIID[0x87]:(TWIN_CHNLB) Dec 2 21:10:56 Cogitek-UX2 kernel: SCB_LUN[0x0] SCB_TAG[0x2] Dec 2 21:10:56 Cogitek-UX2 kernel: 6 SCB_CONTROL[0x64]:(DISCONNECTED|TAG_ENB|DISCENB) SCB_SCSIID[0x87]:(TWIN_CHNLB) Dec 2 21:10:56 Cogitek-UX2 kernel: SCB_LUN[0x0] SCB_TAG[0x29] Dec 2 21:10:56 Cogitek-UX2 kernel: 7 SCB_CONTROL[0x10]:(MK_MESSAGE) SCB_SCSIID[0x87]:(TWIN_CHNLB) Dec 2 21:10:56 Cogitek-UX2 kernel: SCB_LUN[0x0] SCB_TAG[0xff] Dec 2 21:10:56 Cogitek-UX2 kernel: 8 SCB_CONTROL[0x64]:(DISCONNECTED|TAG_ENB|DISCENB) SCB_SCSIID[0x87]:(TWIN_CHNLB) Dec 2 21:10:56 Cogitek-UX2 kernel: SCB_LUN[0x0] SCB_TAG[0x22] Dec 2 21:10:56 Cogitek-UX2 kernel: 9 SCB_CONTROL[0x64]:(DISCONNECTED|TAG_ENB|DISCENB) SCB_SCSIID[0x87]:(TWIN_CHNLB) Dec 2 21:10:56 Cogitek-UX2 kernel: SCB_LUN[0x0] SCB_TAG[0x9] Dec 2 21:10:56 Cogitek-UX2 kernel: 10 SCB_CONTROL[0x64]:(DISCONNECTED|TAG_ENB|DISCENB) SCB_SCSIID[0x87]:(TWIN_CHNLB) Dec 2 21:10:56 Cogitek-UX2 kernel: SCB_LUN[0x0] SCB_TAG[0x8] Dec 2 21:10:56 Cogitek-UX2 kernel: 11 SCB_CONTROL[0x64]:(DISCONNECTED|TAG_ENB|DISCENB) SCB_SCSIID[0x87]:(TWIN_CHNLB) Dec 2 21:10:56 Cogitek-UX2 kernel: SCB_LUN[0x0] SCB_TAG[0x24] Dec 2 21:10:56 Cogitek-UX2 kernel: 12
Nasty hardware problem...
Oops! Major irq head-butting is the problem. I'm amazed the system even came up far enough to complain about it. Sorry I bothered the list with this. -Lyman ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
HP Color DeskJet 960c
Has anyone gotten one of these to work? If so, would you mind letting me know how to configure the ghostscript fliter for it? Thanks! -Lyman ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Piping from one printer queue to another?
I am trying to get a networked old HP printer to work. I have the following printcap entries for it, using gs filtering: # Entry for device ljet3 (output to ljet3.raw, I hope) lp|ljet3|Ghostscript device ljet3:\ :lp=ljet3.raw:\ :sd=/var/spool/output/ljet3:\ :lf=/var/spool/output/ljet3/logfile:\ :af=/var/spool/output/ljet3/acct:\ :if=/usr/local/share/ghostscript/filt/indirect/ljet3/gsif:\ :mx#0:sf:sh:rs: and # Entry for raw device ljet3.raw ljet3.raw|Raw output device ljet3:\ :lp=:\ :rm=192.168.2.1:\ :rp=LPT1:\ :sd=/var/spool/output/ljet3/raw:\ :mx#0:sf:sh:rs: The ljet3.raw queue works perfectly! Of course, I have to send it either ascii with CRLFs or PCL, but it does print what I send to it. However, the lp|ljet3 filter does not send its output on to ljet3.raw. I am sure that I am doing something (subtle?) wrong in this entry, but I don't know enough to find it. Can someone either tell me what's wrong or (better yet) point me to documentation that explains how to do this correctly? Thanks! -Lyman ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Piping from one printer queue to another?
Problem solved! -Lyman ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
SMC Networks Router with HP Printer?
I have an SMC Networks model SMC7004ABR router which forms the hub of my network. It has a parallel printer port and a queueing system with a fair amount of RAM, so it acts somewhat like an LPR printer queue, though it does not have any smarts for doing filtering. I would like to (1) assign a name to the router in the /etc/hosts file so I can refer to it by name rather than by its IP address, and (2) set up my FreeBSD systems so that my old, but reliable, HP-IIIP laser printer hanging on the router's parallel port is the default (lp) printer for all of them. The router's technical manual says the local name of the printer port on it is lpt1. I made an entry in the /etc/hosts file for it that looks like 192.168.2.1 Baricade but while I can successfully ping it by IP address, I can't do ping Baricade I can even connect to its web-based configuration manager in Konqueror with http://192.168.2.1:88/index.htm How do I inform FreeBSD that there is a local host out there that I want to refer to by the name Baricade rather than the IP address? I am clear that I have to do the input and/or output filtering on each of the FreeBSD systems. But how do I setup the /etc/printcap file so it will find and recognize the printer out there. Should I put the IP address in the rm= field? Thanks for any help. Several of you have been extremely helpful as I have gone through setting up these systems. I hope I shall become knowledgeable enough at some point to help others. -Lyman ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Is there something special about mount points in / ?
I have set vfs.usermount=1, and now I can create a local directory (call it xxx) in my home dir and use it successfully to do mount -t cd9660 /dev/cd0 xxx or mount -t msdos /dev/fd0 xxx However, if I attempt to use the standard mount points, /cdrom or /floppy, to do the same thing, like mount -t cd9660 /dev/cd0 /cdrom I get the message: cd9660: /dev/cd0: Operation not permitted. I have set the permissions on /cdrom to 555 and the file is owned by root:operators, and my non-root user-id is a member of operators. Is there something special I have to do to /cdrom to make it usable to non-root users? What ever it is, it must be the same problem I am having with /floppy and my sound system, so solving this will solve a lot of related problems. Thanks for any and all assistance. -Lyman ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Non-root access to peripheral file devices
Perhaps this is discussed somewhere, but so far I haven't found anything that helps. I have two SCSI CDROM drives (/dev/cd0 and /dev/cd1) and an IDE floppy drive. All of these drives are mountable and work flawlessly if I am logged in as root. Trying to mount any of them as any other login-id results in an operation not permitted message and failure. I have a /cdrom mount point that is matched with /dev/cd0 in /etc/fstab and says its file type is cd9660. The permissions on /dev/cd0 are 0555. Same for /cdrom. The owner of both is root:wheel. I already tried setting the permissions to ... no help. The odd thing is that I can successfully run KsCD using either drive as a non-root user and play music through my sound card. (Can't seem to make any other sound work, but that is a separate issue.) I even tried creating a file in /usr/local/bin called mountcd that has just the line mount /cdrom in it, and setting the super user bit on the file. That works fine for root, but fails the same way for non-root users. Does anyone have a hint that will allow me to fix this problem? -Lyman ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Strange problem with Floppy Drive
I have an AMD K6 based system with almost everything on ultra-wide, ultra-fast SCSI. The exceptions are video, sound and floppy disk. The IDE floppy disk works fine if, for example, I boot from it on this machine. Further, I have removed it and tested it on a Windows 2K system, where it works just fine. However, when I boot FreeBSD (version 5.1), I get the following messages in dmseg: fdc0: cannot reserve I/O port range (1 ports) fdc0: cannot reserve I/O port range (1 ports) fdc0: cannot reserve I/O port range (6 ports) and, of course, the floppy isn't available. Any suggestions about what may be wrong here and how to go about making it work? Floppy drives are inexpensive, and I don't mind getting a new one if there's something wrong with the hardware, but I don't understand why it works on other systems and why the same system can boot from it. This just seems very bizarre, and I'm stumped. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
