Re: printer problem (the saga continues)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Fuck you spam motherfucker!!
----- Original Message ----- 
From: "major" <major@xxxxxxxxxxx>
To: <shrike-list@xxxxxxxxxx>
Cc: "Anthony Baldwin" <mrbaldwin@xxxxxxxxxxxxxxxxxx>
Sent: Monday, June 23, 2003 6:54 AM
Subject: Re: printer problem (the saga continues)


> 
> On 2003.06.19 18:12, anthony baldwin wrote:
> > Here is a list of items that I have updated recently with apt-get:
> > 
> > aalib_1.4rc5-fr1_i386.rpm               kdesdk-gimp_3.0.5a-3_i386.rpm
> > cabextract_0.6-fr1_i386.rpm             lock
> > celestia_1.2.5-fr1_i386.rpm             lokkit_0.50-21.8.0_i386.rpm
> > cups_1%3a1.1.17-0.2_i386.rpm            mysql_3.23.56-1.80_i386.rpm
> > cups-devel_1%3a1.1.17-0.2_i386.rpm
> > mysql-devel_3.23.56-1.80_i386.rpm
> > cups-libs_1%3a1.1.17-0.2_i386.rpm
> > mysql-server_3.23.56-1.80_i386.rpm
> > evolution_1.0.8-11_i386.rpm             nmap_2%3a3.20-fr1_i386.rpm
> > gkrellm_1%3a2.1.8-fr1a_i386.rpm
> > nmap-frontend_2%3a3.20-fr1_i386.rpm
> > glibc_2.3.2-4.80_i686.rpm               nscd_2.3.2-4.80_i386.rpm
> > glibc-common_2.3.2-4.80_i386.rpm        partial
> > glibc-debug_2.3.2-4.80_i686.rpm         samba_2.2.7-4.8.0_i386.rpm
> > glibc-debug-static_2.3.2-4.80_i386.rpm
> > samba-client_2.2.7-4.8.0_i386.rpm
> > glibc-devel_2.3.2-4.80_i386.rpm
> > samba-common_2.2.7-4.8.0_i386.rpm
> > glibc-profile_2.3.2-4.80_i386.rpm
> > samba-swat_2.2.7-4.8.0_i386.rpm
> > glibc-utils_2.3.2-4.80_i386.rpm         zlib_1.1.4-8.8x_i386.rpm
> > gnome-lokkit_0.50-21.8.0_i386.rpm       zlib-devel_1.1.4-8.8x_i386.
> > rpm
> > 
> > It was after these updates that I became unable to print.
> > Does anyone know what here may have caused the problem?
> > 
> > If you recall, I have a Lexmark z33 and had been using the driver they
> > provide
> > from their website with LPD.  After running apt-get update and upgrade
> > last weekend
> > my printer stopped functioning with any app but KWord.  Now, for some
> > reason, it is
> > not even printing with KWord, likely because I have tried every other
> > possible configuration of CUPS+foomatic, LPR, and goat sacrifice and
> > have confused the system.
> > I have reinstalled the printer driver about a dozen times.
> > This driver had worked fine with RH 7.2, 6.3 and 8.0 and WAS working
> > with 9 until
> > last weekend when I ran these updates.  I can still drive the printer
> > from my OS X
> > iBook, so the printer itself is fine.
> > If I can identify a specific package that has disable the driver, I
> > will remove
> > and reinstall the older version, hopefully to regain printing
> > capabilities.
> > I would gladly provide and further information that would assist a
> > diagnosis
> > of this problem for me, and deeply appreciate any offered assistance.
> > 
> > I'm crossposting to my local LUG.  (sorry)
> > 
> > tony
> 
> Anthony, you may have installed incorrect packages of software. I 
> suggest that you download and install the Red Hat version 9 update 
> packages. Red Hat allows web access to their file transfer site. Point 
> your web browser to "http://updates.redhat.com";. The site is organized 
> by version ("9"), language ("en" for English), media format ("os" for 
> operating systems), and architecture ("SRPMS" for source rpms, "athlon" 
> for AMD Athlon, "i386" for Intel 80386, "i586" for Intel Pentium, 
> "i686" for Intel Pentium II, "noarch" for no particular architecture). 
> The "i386" architecture directory contains the bulk of the binary 
> packages, while "athlon", "i586", and "i686" contain kernels and 
> libraries that are compiled for the speed and features of those 
> architectures. Red Hat compiles the common packages for the Intel 80386 
> since those other architectures are backward compatible. The printing 
> packages that might help you are at 
> "http://updates.redhat.com/9/en/os/i386";.
> 
> The following printing and document packages may be of interest.
> LPRng-3.8.19-3.1.i386.rpm
> cups-1.1.17-13.3.i386.rpm
> cups-devel-1.1.17-13.3.i386.rpm
> cups-libs-1.1.17-13.3.i386.rpm
> foomatic-2.0.2-15.1.i386.rpm
> ghostscript-7.05-32.1.i386.rpm
> ghostscript-devel-7.05-32.1.i386.rpm
> hpijs-1.3-32.1.i386.rpm
> xpdf-2.01-9.i386.rpm
> xpdf-chinese-simplified-2.01-9.i386.rpm
> xpdf-chinese-traditional-2.01-9.i386.rpm
> xpdf-japanese-2.01-9.i386.rpm
> xpdf-korean-2.01-9.i386.rpm
> 
> "LPRng" is the "LPR Next Generation", which is the default print server 
> for some Red Hat versions before 9. "cups" is the "Common UNIX Printing 
> System", which is the default print server for Red Hat 9. "foomatic" is 
> a printer driver database system that works with both LPRng and CUPS. 
> "ghostscript" is a translator which converts Postscript (the common 
> printing output format of most Linux programs) to many other printer 
> formats, so that a printer that does not understand Postscript natively 
> (like a Lexmark Z33 apparently) can still be used. "hpijs" has 
> optimized drivers for some Hewlett Packard printers. "xpdf" is a 
> Portable Document Format (PDF) viewer.
> 
> If you need help understanding the Red Hat Package Manager, then look 
> at the manual pages for "rpm" and "rpmbuild". You should take care if 
> you decide to update the "kernel" and "glibc" related packages to know 
> exactly what you are doing because incorrectly doing so may make your 
> Linux system unbootable, unrunnable, or both. If you are interested in 
> further understanding this, then start another thread of discussion on 
> the Red Hat 9 mailing list.
> 
> The web page at 
> "http://www.linuxprinting.org/show_printer.cgi?recnum=Lexmark-Z33"; 
> describes the Lexmark Z33 printer and says that the manufacturer's 
> driver does not support CUPS, but the Lexmark driver, date 2001-10-25, 
> version 1.04, file "CJLZ33LE.TAR.GZ", available from
> "http://drivers.lexmark.com/drivers.nsf/SelectPrinter
> ?OpenForm&Lexmark+Z33+Color+Jetprinter" does have a script for setting 
> up CUPS support. Since you describe your previous successful use of the 
> Lexmark Z33 printer with Red Hat, one may presume that it worked with 
> LPRng but could work with CUPS as well.
> 
> "CJLZ33LE.TAR.GZ" is a gzipped tape archive that contains an 
> instruction file "README", and an installer "lexmarkz33-1.0-4.sh" that 
> is a hybrid text and binary file that contains another gzipped tape 
> archive which itself contains a Red Hat Package Manager (rpm) file and 
> various scripts. To obtain the contents of "CJLZ33LE.TAR.GZ" perform 
> the following directions. I use "/DOWNLOAD" as the directory containing 
> the driver archive. Please substitute your personal download directory.
> 
> ########################################################
> cd /tmp/
> cp /DOWNLOAD/CJLZ33LE.TAR.GZ .
> mkdir CJLZ33LE
> cd CJLZ33LE
> gzip -cd ../CJLZ33LE.TAR.GZ | tar xvf -
> mkdir lexmarkz33-1.0-4
> cd lexmarkz33-1.0-4
> tail +156 ../lexmarkz33-1.0-4.sh | gzip -cd | tar xvf -
> ########################################################
> 
> Schematically, the preceding script does the following:
> (1) change your current directory to "/tmp",
> (2) copy the driver file "CJLZ33LE.TAR.GZ" there,
> (3) make a new directory called "CJLZ33LE",
> (4) change your current directory to "/tmp/CJLZ33LE",
> (5) decompress the driver from the parent directory using "gzip" and 
> pipe its output to the tape archive program "tar" to extract its 
> content, producing "README" and "lexmarkz33-1.0-4.sh",
> (6) make a new directory called "lexmarkz33-1.0-4",
> (7) change your current directory to "/tmp/CJLZ33LE/lexmarkz33-1.0-4", 
> and
> (8) use "tail" to output the binary portion of "lexmarkz33-1.0-4.sh" 
> located in the parent directory starting from line 156, piping its 
> output to "gzip" to decompress it, and piping that output to "tar" to 
> extract the archive.
> 
> Use the following command to list the contents of the packaged file.
> ####################################
> rpm -qilp lexmarkz33-1.0-4.i386.rpm
> ####################################
> 
> You may be able to understand the Lexmark driver better and use its 
> scripts once you can read them by following the previous procedures. If 
> you are still having problems in the future, it may concern the USB 
> nature of your printer or some corruption of other configuration files. 
> There are many possibilities.
> 
> -----------------
> major@xxxxxxxxxxx
> 
> 
> -- 
> Shrike-list mailing list
> Shrike-list@xxxxxxxxxx
> https://www.redhat.com/mailman/listinfo/shrike-list





[Index of Archives]     [Fedora Users]     [Centos Users]     [Kernel Development]     [Red Hat Install]     [Red Hat Watch]     [Red Hat Development]     [Red Hat Phoebe Beta]     [Yosemite Forum]     [Fedora Discussion]     [Gimp]     [Stuff]     [Yosemite News]

  Powered by Linux