October 2001 - openSUSE Users - openSUSE Mailing Lists

Printer trouble. Blocked at the end of printing job.
by José Luis Canales Salceda 05 Oct '01

05 Oct '01

I have a Lexmark Z53 printer. I use Ghostscript 6.51 from SuSE's ftp and a printer driver from Lexmark that was installed from a rpm downloaded from http://www.lexmark.com. It created an entry on /etc/printcap: ##PRINTTOOL3## LOCAL lexmarkz53:\ :sd=/var/spool/lpd/lexmarkz53:\ :mx#0:\ :sh:\ :lp=/dev/lp0:\ :if=/usr/local/lexmark/z53/z53.sh: When I print something the printer suffers a blockage when in the last line of the last page of the printing job. I have to open a lpq frontend and cancell printing job to make it eject the last page. I think I should add something to /etc/printcap to "send end of page" to printer when job is finished but I don't understand such a cryptic thing like /etc/printcap. Could anyone tell me how to modify it to avoid printer retaining the last page in every job?.

1 0

USB Zip Drive
by Mark Annandale 05 Oct '01

05 Oct '01

Hi Guys While 7.2 is loading it appears to enable the usbmngr (?) and places an icon on mydesktop for the zip drive. When I try and mount the zip drive I get the error ' /dev/sda4 is not a valid block device'. This is strange as it appears in /fstab and i think all the necessary drivers are there. Here's the line from fstab: /dev/sda4 /media/zip auto noauto,user 0 0 Where can I look for anpther clue, or what is the fix for this problem ? Thanks Mark A -- Mark R Annandale SuSE Linux 7.2 Pro KDE 2.2.1 KMail 1.3.1

2 2

RE: [SLE] New Lilo problems
by Jostein Berntsen 05 Oct '01

05 Oct '01

>===== Original Message From "Carley, Jason (Hong Kong)" <jason_carley(a)hk.ml.com> ===== >Well I haven't yet gotten around to fixing my network problems. I am now >trying to get my system to boot from either a disk or LILO on the hard >drive. > >It is an Abit KT-7 and the Drive is a slave (for historical reasons) behind >a CDROM drive on the 1st IDE controller (not the RAID controllers which have >a seperate windows installation on them). > >I get the famous LI response from the bootloader. Now after looking this up >in the docs and being told that it relates to disk geometry I am stumped. I >am booting to a /boot all within the 1024 limit. The drive is properly >detected and boots under other OSs. I get exactly the same problem whether I >am using LILO on a boot disk or the hard drive. I even tried a reinstall >using default partitioning in case something I did stuffed up the booting >ability from the hard drive. > >It boots fine from the Disk 1 CDROM. > >Any help greatly appreciated. > >Regards, > >Jason. > > >-- >To unsubscribe send e-mail to suse-linux-e-unsubscribe(a)suse.com >For additional commands send e-mail to suse-linux-e-help(a)suse.com >Also check the FAQ at http://www.suse.com/support/faq and the >archives at http://lists.suse.com

1 0

NIS on multiple NICs
by Dunphy Richard-rdunph01 05 Oct '01

05 Oct '01

I have an NIS Server running on a SuSE 7.1 server. The server has two nics, one serving 255.255.255.0/10.1.1.x and the other 255.255.255.0/175.3.56.x I have the following in my /var/yp/securenets 255.0.0.0 127.0.0.0 255.255.255.0 10.1.1.0 255.255.255.0 175.3.56.0 Those machines on the first network can access the NIS domain perfectly, but the other network can't! running ypserv with the -d (debug) option doesn't even show the 175.3.56.203 machine trying to connec to the NIS server. Have I missed something? Any help would be greatly appreciated. TIA RikD.

1 0

SUMMARY: [SLE] Failed re-install
by Fletcher, Joe 05 Oct '01

05 Oct '01

Hi, My guess is that the original upgrade from 7.0. to 7.2 hacked the MBR in some way not backwards compatible with 7.0. Re-installing from scratch, picking custom LILO options and choosing install LILO in MBR fixed the problem. Cheers Joe ---------------------------- originally ------------------------------------- I've got this Proliant 3000. I installed SuSE 7.0 on it. It worked. Then, because of some work with DB2 I "upgraded" to 7.2. Still worked. Now, for reasons connected with Oracle I'm attempting to re-install 7.0. I load the CD, format the disks, pick the options I want installed, these load and I reboot. On restart the box hangs with a balck screen reading LI. I'm assuming the boot files are corrupted. Anyone know why this might be and how I fix the problem. MetaPack The Lightwell 12/16 Laystall Street Clerkenwell London EC1R 4PF Tel: +44 (0) 20 7843 6720 Fax: +44 (0) 20 7843 6721 -------------------------------------------------------------------------- This email is confidential and proprietary; all information contained in it must be used only by the addressee in accordance with MetaPack's terms of business and non-disclosure agreement. Disclosure, copying, and distribution to, or use by, anyone other than the intended recipient is strictly prohibited and may be unlawful.

1 0

Backup (like in yast) but automatically at 2:35 am ??
by Ronald Wiplinger 05 Oct '01

05 Oct '01

How can I get used of the settings in yast for the backup and make it as a cron job at 2:35 am ??? thanks bye Ronald Ronald Wiplinger (ÃQ¤¯¯Ç), CEO, ELMIT - The Solution Provider Tel. +886 2 8809-7980, Fax. +886 2 2809-0183, Mobile: +886 915 653-452 Net2Phone:8869550066, ICQ: 111651169 http://www.elmit.com http://www.wiplinger.org

1 0

New Lilo problems
by Carley, Jason (Hong Kong) 05 Oct '01

05 Oct '01

Well I haven't yet gotten around to fixing my network problems. I am now trying to get my system to boot from either a disk or LILO on the hard drive. It is an Abit KT-7 and the Drive is a slave (for historical reasons) behind a CDROM drive on the 1st IDE controller (not the RAID controllers which have a seperate windows installation on them). I get the famous LI response from the bootloader. Now after looking this up in the docs and being told that it relates to disk geometry I am stumped. I am booting to a /boot all within the 1024 limit. The drive is properly detected and boots under other OSs. I get exactly the same problem whether I am using LILO on a boot disk or the hard drive. I even tried a reinstall using default partitioning in case something I did stuffed up the booting ability from the hard drive. It boots fine from the Disk 1 CDROM. Any help greatly appreciated. Regards, Jason.

3 2

strange ownerships
by S.Toms 05 Oct '01

05 Oct '01

I noticed something weird, I've installed and reinstalled a few times now (from scratch) and I noticed that alot of the objects in the /dev directory have me as the owner when I always thought they should be owned by root. Am I forgetting something? I know I didn't go in there and change anything, I've still been customizing and installing things, so I havn't had a chance to do anything in there. Here's an example of the drives (removable). skull@daydream:~ > l /dev/hdd /dev/hdc /dev/fd0 brw------- 1 skull users 22, 64 May 21 05:21 /dev/hdd brw------- 1 skull users 22, 0 May 21 05:21 /dev/hdc brw------- 1 skull users 2, 0 May 21 05:21 /dev/fd0 skull@daydream:~ > ssh -l nitz daydream nitz@daydream's password: Have a lot of fun... nitz@daydream:~ > l /dev/hdd /dev/hdc /dev/fd0 brw------- 1 skull users 22, 64 May 21 05:21 /dev/hdd brw------- 1 skull users 22, 0 May 21 05:21 /dev/hdc brw------- 1 skull users 2, 0 May 21 05:21 /dev/fd0 nitz@daydream:~ > I tried with a second user thinking maybe it changed per user but obviously that wasn't the case. -- S.Toms - smotrs(a)mindspring.com - www.mindspring.com/~smotrs SuSE Linux v7.2+ - Kernel 2.4.4 I brake for chezlogs!

2 2

Sensors
by Alain DIDIERJEAN 05 Oct '01

05 Oct '01

I just compiled SuSE-kernel 2.4.10. Everything went find and I have no problem with the kernel, except that I'd like to experiment with sensors, but when the "Hardware sensors support" was displayed by xconfig, it showed greyed out. I'm sure I missed something that should be enabled before displaying that page, but couldn't figure out what. Help welcome, thx -- ~adj~ Ces mystères nous dépassent Feignons d'en être l'organisateur...

2 1

RE: [SLE] New Lilo problems
by Carley, Jason (Hong Kong) 05 Oct '01

05 Oct '01

To be honest it was due to laziness. And not wanting to muck up windows drive allocations etc. Thinking it through, it may be easier to fix it first and see if it helps lilo out. Is there any chance that switching them could work? -----Original Message----- From: philippt(a)t-online.de [mailto:philippt@t-online.de] Sent: Friday, October 05, 2001 3:48 PM To: suse-linux-e Subject: Re: [SLE] New Lilo problems * Carley, Jason (Hong Kong) [Fri, 5 Oct 2001 09:47:11 +0800 ]: >It is an Abit KT-7 and the Drive is a slave (for historical reasons) behind >a CDROM drive on the 1st IDE controller Might I ask which reasons this were? For all means, removable drives should always follow fixed drives. >I get the famous LI response from the bootloader. Now after looking this up >in the docs and being told that it relates to disk geometry I am stumped. It might be as simple as lilo using the wrong BIOS identifier. If that's the reason, but this in the global section: disk=/dev/hdb bios=0x80 This tells lilo that your slave will be the first disk discovered by the BIOS (which enumerates the drives in the order it detects them). Philipp -- Penguins to save the dinosaurs -- Handelsblatt on Linux for S/390 -- To unsubscribe send e-mail to suse-linux-e-unsubscribe(a)suse.com For additional commands send e-mail to suse-linux-e-help(a)suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com

1 0