Re: [PARPORT] Another 'device busy' incident

From: Greg Peters (
Date: Thu Nov 16 2000 - 15:58:14 EST

  • Next message: daniel sheltraw: "[PARPORT] parallel port grounding"

    Silly boy...

    My Epson Stylus Photo was out of ink!!! Gasp! How embarassing...

    I rebooted under Windows and still couldn't print. But the Zip drive worked.
    This was looking suspicious. So I plugged the printer into the other linux
    box and got the same error message.

    Two wrong assumptions were made:
    1) Because the printer stopped working just when I was doing unorthodox (and
    maybe dangerous) things with root privilege, I assumed that these activities
    were responsible for the failure.
    2) I assumed that something like a printer error would not produce the
    symptoms I was getting.

    So remember, before you call the garage, look at the gas guage.



    >From: "Greg Peters" <>
    >Subject: [PARPORT] Another 'device busy' incident
    >Date: Wed, 15 Nov 2000 21:20:59 -0000
    >I have a Zip drive and an Epson computer on the parallel port.
    >- RH6.2
    >- Dell Inspiron 7500
    >- Zip unused for the moment (I use it under Windows)
    >Printing worked just fine until a few days ago. I wanted to automate a task
    >by streaming some stuff directly to the printer, so I needed to learn to
    >print from a shell script. I executed some command line instructions in the
    >Printing Usage Howto. This only produced errors, or created files called
    >/root/lp or |lp or whatever.
    >When I finished, printing would not work any more. I may have broken
    >I apologise if the answer is in Documentation/parport.txt. I don't have
    >file and I don't know where to find it. All the refrences to it just call
    >I have read just about every message in the current archives on the subject
    >of busy device. I have tried to follow the instructions but nothing has
    >improved the situation.
    >Here is some information:
    >- bios setup: parallel port Auto/EPP (I also tried EPP/IRQ7 and
    >ECP/378/IRQ7/DMA3) - nothing works
    ># insmod imm
    >Using /lib/modules/2.2.14-5.0/scsi/imm.o
    >/lib/modules/2.2.14-5.0/scsi/imm.o: init_module: Device or resource busy
    ># modprobe imm
    >/lib/modules/2.2.14-5.0/scsi/imm.o: init_module: Device or resource busy
    >/lib/modules/2.2.14-5.0/scsi/imm.o: insmod
    >/lib/modules/2.2.14-5.0/scsi/imm.o failed
    >/lib/modules/2.2.14-5.0/scsi/imm.o: insmod imm failed
    ># modprobe parport_lowlevel (returns nothing)
    ># modprobe -c|grep parport
    >alias parport_lowlevel parport_pc
    >options parport_pc io=0x378 irq=none
    ># lpq
    >lp is ready and printing
    >Rank Owner Job Files Total Size
    >1st root 19 (standard input) 42973 bytes
    ># lpc status all
    > queuing is enabled
    > printing is enabled
    > 1 entry in spool area
    > lp is ready and printing
    ># dmesg produces an endless spew of VFS: Disk change bla bla bla
    >parport0: PC-style at 0x378 [SPP,PS2,EPP]
    >parport0: no IEEE-1284 device present.
    >lp0: using parport0 (polling).
    >lp0 on fire
    >(I couldn't smell any smoke)
    >When I try to send text directly to the port from printtool, sometimes I
    >lp0: file busy.
    >When I print from Netscape sometimes I get the message can't restart lpd
    >One more thing:
    >I have a desktop machine running exactly the same version of RH, and it
    >prints ok (like the laptop did up until 2 days ago). Are there any other
    >files than conf.modules that I could compare between the two machines?
    >Get more from the Web. FREE MSN Explorer download :
    >-- To unsubscribe, send mail to: --
    >-- with the single word "unsubscribe" in the body of the message. --

    Get Your Private, Free E-mail from MSN Hotmail at

    Share information about yourself, create your own public profile at

    -- To unsubscribe, send mail to: --
    -- with the single word "unsubscribe" in the body of the message. --

    This archive was generated by hypermail 2b29 : Thu Nov 16 2000 - 16:15:04 EST