Anyone successfully using a Samsung ML6060 printer with Suse ?
I'm on the verge of buying a Samsung ML6060 laser printer. I can't see any reason why it won't work with Linux but I thought I'd better check it out for any gotchas before parting with my cash. So is anyone using one of these and if so, how are you getting on with it ? I have Suse 7.0 and 7.2 running on my systems. Cheers, Sean.
Don't. It won't work. It is a GDI printer. It won't work under lpdold, and with CUPS it won't work unless it is listed when you do "gs -h", which list the supported printers in the GhostScript gs_lib file,. I recently returned a Samsung ML4500 for that very reason. JLK On Sunday 28 October 2001 11:39, Sean Akers wrote:
I'm on the verge of buying a Samsung ML6060 laser printer. I can't see any reason why it won't work with Linux but I thought I'd better check it out for any gotchas before parting with my cash. So is anyone using one of these and if so, how are you getting on with it ? I have Suse 7.0 and 7.2 running on my systems.
Cheers,
Sean.
On Sunday 28 Oct 2001 7:01 pm, jk05308 wrote:
Don't. It won't work. I am not sure about that, read on.
It is a GDI printer. It won't work under lpdold, and with CUPS it won't work unless it is listed when you do "gs -h", which list the supported printers in the GhostScript gs_lib file,. I recently returned a Samsung ML4500 for that very reason. I have a Samsung ML4600 and have it working under Linux fine. YaST CUPS Configuration utility provided with SuSE 7.2 has the Samsung ML4500 listed despite it being GDI.
I'm on the verge of buying a Samsung ML6060 laser printer. I can't see any reason why it won't work with Linux but I thought I'd better check it out for any gotchas before parting with my cash. So is anyone using one of these and if so, how are you getting on with it ? I have Suse 7.0 and 7.2 running on my systems. If you use YaST CUPS Configuration utility you will notice that it supports
On Sunday 28 October 2001 11:39, Sean Akers wrote: the ML6000/ML6100, assuming the ML6060 is a member of the ML6000 series I would think it is supported. According to the Simply Computers catalog the ML6060 is a ML6000 series printer.
TTFN Roger -- Roger L.S. Griffiths, BSc (Hons) Gott würfelt nicht (God does not play dice) - Albert Einstein
On Monday 29 October 2001 01:24, Roger L.S. Griffiths BSc (Hons) wrote:
On Sunday 28 Oct 2001 7:01 pm, jk05308 wrote:
Don't. It won't work.
I am not sure about that, read on.
It is a GDI printer. It won't work under lpdold, and with CUPS it won't work unless it is listed when you do "gs -h", which list the supported printers in the GhostScript gs_lib file,. I recently returned a Samsung ML4500 for that very reason.
I have a Samsung ML4600 and have it working under Linux fine. YaST CUPS Configuration utility provided with SuSE 7.2 has the Samsung ML4500 listed despite it being GDI.
YaST2 pulls the mfgr name and model number from the printer bios, but it fails to recognize the printer regardless. I, too, am running a fully installed SuSE 7.2 and when I do a 'gs -h' on GhostScript (where the driver actually is) the ML4500 is NOT listed. http://sdb.suse.de/en/sdb/html/ke_printer-gdi.html
On Sunday 28 October 2001 11:39, Sean Akers wrote:
I'm on the verge of buying a Samsung ML6060 laser printer. I can't see any reason why it won't work with Linux but I thought I'd better check it out for any gotchas before parting with my cash. So is anyone using one of these and if so, how are you getting on with it ? I have Suse 7.0 and 7.2 running on my systems.
If you use YaST CUPS Configuration utility you will notice that it supports the ML6000/ML6100, assuming the ML6060 is a member of the ML6000 series I would think it is supported. According to the Simply Computers catalog the ML6060 is a ML6000 series printer.
TTFN
Roger
On Monday 29 Oct 2001 3:37 pm, jk05308 wrote:
It is a GDI printer. It won't work under lpdold, and with CUPS it won't work unless it is listed when you do "gs -h", which list the supported printers in the GhostScript gs_lib file,. I recently returned a Samsung ML4500 for that very reason.
I have a Samsung ML4600 and have it working under Linux fine. YaST CUPS Configuration utility provided with SuSE 7.2 has the Samsung ML4500 listed despite it being GDI.
YaST2 pulls the mfgr name and model number from the printer bios, but it fails to recognize the printer regardless. I, too, am running a fully installed SuSE 7.2 and when I do a 'gs -h' on GhostScript (where the driver actually is) the ML4500 is NOT listed. ghostscript (ie gs) does not list my ML4600 either, but my printer is supported according to YaST CUPS Config via three different mechanisms:- Foomatic + lj5gray Foomatic + ljet4 Foomatic + pxlmono
The ML4500 is listed as being supported by ONE mechanism Foomatic + gdi The ML6000/ML6100 printers are supported by ONE mechanism Foomatic + ljet4 I got this information from YaST2 without any printer connected, just try adding a printer manually with the CUPS printer configuration utility.
That document has not been updated since August 2000 (over 1 year old)! I think it might be somewhat out of date. Anyway, maybe someone could shed some light on the Foomatic business? TTFN Roger -- Roger L.S. Griffiths, BSc (Hons) Gott würfelt nicht (God does not play dice) - Albert Einstein
On Monday 29 October 2001 17:32, Roger L.S. Griffiths BSc (Hons) wrote:
On Monday 29 Oct 2001 3:37 pm, jk05308 wrote:
It is a GDI printer. It won't work under lpdold, and with CUPS it won't work unless it is listed when you do "gs -h", which list the supported printers in the GhostScript gs_lib file,. I recently returned a Samsung ML4500 for that very reason.
I have a Samsung ML4600 and have it working under Linux fine. YaST CUPS Configuration utility provided with SuSE 7.2 has the Samsung ML4500 listed despite it being GDI.
YaST2 pulls the mfgr name and model number from the printer bios, but it fails to recognize the printer regardless. I, too, am running a fully installed SuSE 7.2 and when I do a 'gs -h' on GhostScript (where the driver actually is) the ML4500 is NOT listed.
ghostscript (ie gs) does not list my ML4600 either, but my printer is supported according to YaST CUPS Config via three different mechanisms:- Foomatic + lj5gray Foomatic + ljet4 Foomatic + pxlmono
The ML4500 is listed as being supported by ONE mechanism Foomatic + gdi
The ML6000/ML6100 printers are supported by ONE mechanism Foomatic + ljet4
I had tried all of these configs to no avail.
I got this information from YaST2 without any printer connected, just try adding a printer manually with the CUPS printer configuration utility.
That document has not been updated since August 2000 (over 1 year old)! I think it might be somewhat out of date.
I suspect that the drivers may be susecptible to printer changes within the model designation. The GDI is, after all, a WIndows propriatary protocol, and I have no doubts that MS can make tweeks GDI formats that render formerly good Linux drivers worthless on later version of the same model.
Anyway, maybe someone could shed some light on the Foomatic business?
TTFN
Roger
Hello all, when Suseconfig runs, i get the following error message: ldconfig: /usr/lib/libexpat.so.1 is not a symbolic link how can i avoid this ? -- Best regards, SAE's System Administrator noc@sae.gr World Council of Hellenes Abroad 2 Komotinis str. 54655 - Thessaloniki GREECE ----------__________----------__________----------__________---------- This message was passed through SAE's Mailgate Server. Our MailGate Server employs the latest antivirus & antispam technology. Please report any errors to noc@sae.gr
On 30 Oct 2001, SAE's System Administrator wrote:
Hello all,
when Suseconfig runs, i get the following error message: ldconfig: /usr/lib/libexpat.so.1 is not a symbolic link
how can i avoid this ?
What does 'file /usr/lib/libexpat*' tell you? -- noodlez: Karol Pietrzak PGP KeyID: 0x3A1446A0
Hello Karol, Tuesday, October 30, 2001, 5:08:40 AM, you wrote:
when Suseconfig runs, i get the following error message: ldconfig: /usr/lib/libexpat.so.1 is not a symbolic link
how can i avoid this ?
KP> What does 'file /usr/lib/libexpat*' tell you? cleopatra:~ # file /usr/lib/libexpat* /usr/lib/libexpat.a: current ar archive /usr/lib/libexpat.so: ELF 32-bit LSB shared object, Intel 80386, version 1, not stripped /usr/lib/libexpat.so.1: ELF 32-bit LSB shared object, Intel 80386, version 1, not stripped /usr/lib/libexpat.so.1.2: ELF 32-bit LSB shared object, Intel 80386, version 1, not stripped -- Best regards, SAE's System Administrator noc@sae.gr World Council of Hellenes Abroad 2 Komotinis str. 54655 - Thessaloniki GREECE ----------__________----------__________----------__________---------- This message was passed through SAE's Mailgate Server. Our MailGate Server employs the latest antivirus & antispam technology. Please report any errors to noc@sae.gr
On 30 Oct 2001, SAE's System Administrator wrote:
cleopatra:~ # file /usr/lib/libexpat* /usr/lib/libexpat.a: current ar archive /usr/lib/libexpat.so: ELF 32-bit LSB shared object, Intel 80386, version 1, not stripped /usr/lib/libexpat.so.1: ELF 32-bit LSB shared object, Intel 80386, version 1, not stripped /usr/lib/libexpat.so.1.2: ELF 32-bit LSB shared object, Intel 80386, version 1, not stripped
Are /usr/lib/libexpat.so.1.2 , /usr/lib/libexpat.so.1, and /usr/lib/libexpat.so all the same files? To check, do this: diff /usr/lib/libexpat.so.1.2 /usr/lib/libexpat.so.1 diff /usr/lib/libexpat.so /usr/lib/libexpat.so.1 diff /usr/lib/libexpat.so /usr/lib/libexpat.so.1.2 -- Karol Pietrzak PGP KeyID: 3A1446A0
Hello Karol, Wednesday, October 31, 2001, 5:35:02 AM, you wrote: KP> Are /usr/lib/libexpat.so.1.2 , /usr/lib/libexpat.so.1, and KP> /usr/lib/libexpat.so all the same files? To check, do this: KP> diff /usr/lib/libexpat.so.1.2 /usr/lib/libexpat.so.1 KP> diff /usr/lib/libexpat.so /usr/lib/libexpat.so.1 KP> diff /usr/lib/libexpat.so /usr/lib/libexpat.so.1.2 cleopatra:~ # diff /usr/lib/libexpat.so.1.2 /usr/lib/libexpat.so.1 cleopatra:~ # diff /usr/lib/libexpat.so /usr/lib/libexpat.so.1 cleopatra:~ # diff /usr/lib/libexpat.so /usr/lib/libexpat.so.1.2 cleopatra:~ # <blinking cursor> ;)) -- Best regards, George george@michalopoulos.gr Tel: +30 31 0888448 Fax: +30 31 0848770 VideoPhone:+30 31 0888447 I've set up my Wish Lists at Amazon.com and Amazon.co.uk. If you're ever feeling generous and fancy splashing out on a present for me, here's where to go to find something you know I'll love. PS. Have I told you lately how much I admire and respect you? Seems like a good time to do that. ;-) To view my Wish Lists, click on the links below. http://www.amazon.com/exec/obidos/wishlist/257PYFNXCHPVH/ref=wl_em_to?add-fa...
On 31 Oct 2001, George A. Michalopoulos wrote:
cleopatra:~ # diff /usr/lib/libexpat.so.1.2 /usr/lib/libexpat.so.1 cleopatra:~ # diff /usr/lib/libexpat.so /usr/lib/libexpat.so.1 cleopatra:~ # diff /usr/lib/libexpat.so /usr/lib/libexpat.so.1.2 cleopatra:~ # <blinking cursor>
Try this: rpm -qf /usr/lib/libexpat* If that fails, check each individually. Delete the files that do not belong to any package. Have you tried uninstalling libexpat and installing it again?? -- Karol Pietrzak PGP KeyID: 3A1446A0
Hello Karol, Wednesday, October 31, 2001, 5:35:02 AM, you wrote: it is reporting this error, after some checks for /etc/XF86Config.. I do not have X installed... cleopatra:~ # /sbin/SuSEconfig Starting SuSEconfig, the SuSE Configuration Tool... Running in full featured mode. Reading /etc/rc.config and updating the system... XFree86 not configured yet! No graphical login. Check /etc/X11/XF86Config or /etc/XF86Config. /sbin/ldconfig: /usr/lib/libexpat.so.1 is not a symbolic link Executing /sbin/conf.d/SuSEconfig.alljava... Executing /sbin/conf.d/SuSEconfig.apache... Executing /sbin/conf.d/SuSEconfig.fonts... Executing /sbin/conf.d/SuSEconfig.groff... Executing /sbin/conf.d/SuSEconfig.hostname... Executing /sbin/conf.d/SuSEconfig.pam... Executing /sbin/conf.d/SuSEconfig.perl... No kernel includes installed Executing /sbin/conf.d/SuSEconfig.profiles... Executing /sbin/conf.d/SuSEconfig.sendmail... Processing index files of all manpages... Finished. -- Best regards, George george@michalopoulos.gr Tel: +30 31 0888448 Fax: +30 31 0848770 VideoPhone:+30 31 0888447 I've set up my Wish Lists at Amazon.com and Amazon.co.uk. If you're ever feeling generous and fancy splashing out on a present for me, here's where to go to find something you know I'll love. PS. Have I told you lately how much I admire and respect you? Seems like a good time to do that. ;-) To view my Wish Lists, click on the links below. http://www.amazon.com/exec/obidos/wishlist/257PYFNXCHPVH/ref=wl_em_to?add-fa...
On Tuesday 30 October 2001 03:08, Karol Pietrzak wrote:
when Suseconfig runs, i get the following error message: ldconfig: /usr/lib/libexpat.so.1 is not a symbolic link how can i avoid this ?
What does 'file /usr/lib/libexpat*' tell you?
I get this message too. The output from the above is: /usr/lib/libexpat.a: current ar archive /usr/lib/libexpat.so: ELF 32-bit LSB shared object, Intel 80386, version 1, not stripped /usr/lib/libexpat.so.1: ELF 32-bit LSB shared object, Intel 80386, version 1, not stripped /usr/lib/libexpat.so.1.2: ELF 32-bit LSB shared object, Intel 80386, version 1, not stripped None of these is a symlink, so the message is correct. But what is causing the message? Kevin -- 11:22am up 1 day, 21:12, 1 user, load average: 0.12, 0.09, 0.02
I have this on all the 7.2 boxes here. I've never seen a fix on this list. file /usr/lib/libexpat* /usr/lib/libexpat.a: current ar archive /usr/lib/libexpat.so: ELF 32-bit LSB shared object, Intel 80386, version 1, not stripped /usr/lib/libexpat.so.1: ELF 32-bit LSB shared object, Intel 80386, version 1, not stripped /usr/lib/libexpat.so.1.2: ELF 32-bit LSB shared object, Intel 80386, version 1, not stripped -----Original Message----- From: Kevin Donnelly [mailto:kevin@dotmon.com] Sent: Tuesday, October 30, 2001 6:40 AM To: suse-linux-e@suse.com Subject: Re: [SLE] Suse 7.2 - Ldconfig On Tuesday 30 October 2001 03:08, Karol Pietrzak wrote:
when Suseconfig runs, i get the following error message: ldconfig: /usr/lib/libexpat.so.1 is not a symbolic link how can i avoid this ?
What does 'file /usr/lib/libexpat*' tell you?
I get this message too. The output from the above is: /usr/lib/libexpat.a: current ar archive /usr/lib/libexpat.so: ELF 32-bit LSB shared object, Intel 80386, version 1, not stripped /usr/lib/libexpat.so.1: ELF 32-bit LSB shared object, Intel 80386, version 1, not stripped /usr/lib/libexpat.so.1.2: ELF 32-bit LSB shared object, Intel 80386, version 1, not stripped None of these is a symlink, so the message is correct. But what is causing the message? Kevin
I've sent a 'fix' for this a while back. rm /usr/lib/libexpat.so rm /usr/lib/libexpat.so.1 ln -s /usr/lib/libexpat.so.1.2 /usr/lib/libexpat.so.1 ln -s /usr/lib/libexpat.so.1 /usr/lib/libexpat.so The problem is that someone at suse did a cp with full copy of symlinks when they created the iso image. Easily fixed, but even if you don't it's not harmful. It just takes up a few unnecessary bytes regards Anders On Tuesday 30 October 2001 18.51, W.D.McKinney wrote:
I have this on all the 7.2 boxes here. I've never seen a fix on this list.
file /usr/lib/libexpat* /usr/lib/libexpat.a: current ar archive /usr/lib/libexpat.so: ELF 32-bit LSB shared object, Intel 80386, version 1, not stripped /usr/lib/libexpat.so.1: ELF 32-bit LSB shared object, Intel 80386, version 1, not stripped /usr/lib/libexpat.so.1.2: ELF 32-bit LSB shared object, Intel 80386, version 1, not stripped
-----Original Message----- From: Kevin Donnelly [mailto:kevin@dotmon.com] Sent: Tuesday, October 30, 2001 6:40 AM To: suse-linux-e@suse.com Subject: Re: [SLE] Suse 7.2 - Ldconfig
On Tuesday 30 October 2001 03:08, Karol Pietrzak wrote:
when Suseconfig runs, i get the following error message: ldconfig: /usr/lib/libexpat.so.1 is not a symbolic link how can i avoid this ?
What does 'file /usr/lib/libexpat*' tell you?
I get this message too. The output from the above is: /usr/lib/libexpat.a: current ar archive /usr/lib/libexpat.so: ELF 32-bit LSB shared object, Intel 80386, version 1, not stripped /usr/lib/libexpat.so.1: ELF 32-bit LSB shared object, Intel 80386, version 1, not stripped /usr/lib/libexpat.so.1.2: ELF 32-bit LSB shared object, Intel 80386, version 1, not stripped
None of these is a symlink, so the message is correct. But what is causing the message?
Kevin
-- ICQ: 132715168 YM: cicerose
participants (9)
-
Anders Johansson -
George A. Michalopoulos -
jk05308 -
Karol Pietrzak -
Kevin Donnelly -
Roger L.S.Griffiths BSc -
SAE's System Administrator -
Sean Akers -
W.D.McKinney