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

My printer used to work before I fooled with the imm and ppa modules



Hello-

	I had my printer working just fine. But then I tried to install ome 
modules, because I figured that would be the way to go since my Zip 
drive wasn't working.
	As you can see from my syslog, I had 

Jul 23 13:49:10 siddhi kernel: imm: Version 2.03 (for Linux 2.0.0)
Jul 23 13:49:10 siddhi kernel: scsi : 0 hosts.
Jul 23 13:49:35 siddhi kernel: imm: Version 2.03 (for Linux 2.0.0)
Jul 23 13:49:35 siddhi kernel: scsi : 0 hosts.
[cut some]
Jul 23 14:22:45 siddhi kernel: imm: Version 2.03 (for Linux 2.0.0)
Jul 23 14:22:45 siddhi kernel: scsi : 0 hosts.
Jul 23 11:33:33 siddhi modprobe: modprobe: Can't locate module 
block-major-8
Jul 23 11:36:29 siddhi nscd: 360: short write in cache_addhst: Broken 
pipe
Jul 23 11:36:28 siddhi nscd: 359: short write in cache_addhst: Broken 
pipe
Jul 23 11:36:29 siddhi nscd: 361: short write in cache_addhst: Broken 
pipe
Jul 23 14:38:01 siddhi /USR/SBIN/CRON[1404]: (mail) CMD (  if [ -x 
/usr/sbin/exim -a -f /etc/exim.conf ]; then /usr/sbin/exim -q >/dev/null 
2>&1; fi)
Jul 23 14:56:57 siddhi kernel: imm: Version 2.03 (for Linux 2.0.0)
Jul 23 14:56:57 siddhi kernel: scsi : 0 hosts.
Jul 23 14:58:37 siddhi kernel: ppa: Version 2.05 (for Linux 2.2.x)
Jul 23 14:58:37 siddhi kernel: WARNING - no ppa compatible devices 
found.
Jul 23 14:58:37 siddhi kernel:   As of 31/Aug/1998 Iomega started 
shipping parallel
Jul 23 14:58:37 siddhi kernel:   port ZIP drives with a different 
interface which is
Jul 23 14:58:37 siddhi kernel:   supported by the imm (ZIP Plus) driver. 
If the
Jul 23 14:58:37 siddhi kernel:   cable is marked with "AutoDetect", this 
is what has
Jul 23 14:58:37 siddhi kernel:   happened.
Jul 23 14:58:37 siddhi kernel: scsi : 0 hosts.

	Today, in my dmesg file I have:

parport0: PC-style at 0x378 (0x778) [SPP,EPP,ECP,ECPEPP,ECPPS2]
parport0: detected irq 7; use procfs to enable interrupt-driven 
operation.
parport_probe: failed
parport0: no IEEE-1284 device present.
lp0: using parport0 (polling).

	You can see there's no reference to imm, in the message above.

	Whenever I try to print anything with lpr, I get no sign of life.
	However, if I try to bypass lpr, (I'm using a free turboprint 
driver for HP840c), like this:

siddhi:/usr/local# turboprint -Ptp0 output.prn testfile.txt
siddhi:/usr/local# cat ouput.prn > /dev/lp0
bash: /dev/lp0: Device or resource busy

	Busy with what? How do I check that? 
	With lsmod|more, regarding the parport, I have that

parport_probe           3348   0  (autoclean)
parport                 6836   1  (autoclean) [parport_pc lp paride 
parport_probe]

	Do you think this is what making the /dev/lp0 busy? Should I remove 
these modules?
	And what happened to the imm module?

	Thank you for your help.
	Best regards,
	Henry










Reply to: