Take a look at your /etc/modules.conf file and see if you have anything uncommented in that file that looks like this: alias parport_lowlevel parport_pc options parport_pc io=0x378 irq=none,none I am running a 2.2.18 kernel, and this is part of what I have. Since I have this, the proper modules get installed when I boot the machine. Check and see what you have. You might be able to get stuff working this way. I am going to guess that the "device or resource busy" is coming from your lpd daemon. Check to see if lpd is running with something like this: ps ax | grep lpd Good luck! Andy -- Andy Stewart, Founder Worcester Linux Users' Group Worcester, MA USA http://www.wlug.org On Friday 04 May 2001 14:34, gwlt@ma.ultranet.com wrote:
Andy, Mike, Wesley, Jeff, et. al, thanks for helping me out on this. So here is where I stand, I have discovered a backlog of queued docs and deleted them, but I am getting Device or resource busy when I try to insmod the two missing pieces from lsmod. Here is what I tried:
parport_probe and parport are present in lsmod; lp and parport_pc are missing /lib/modules/2.2.15-4mdk/misc/ lp.o and parport_pc.o are present when I go to... [root@localhost misc]# insmod parport_pc I get Using parport_pc.o /lib/modules/2.2.15-4mdk/misc/parport_pc.o: init_module: Device or resource busy and the same for lp.o Using lp.o /lib/modules/2.2.15-4mdk/misc/lp.o: init_module: Device or resource busy So I am missing elements in lsmod, and there is something holding me back from using insmod. Then I: lpq -P lp0 (and get) Waiting for lp0 to become ready (offline ?) Rank Owner Job Files 1st root 9 ... I try to clear this with lprm - -Plp0 dfA009localhost.localdomain dequeued cfA009localhost.localdomain dequeued The when I: lpq -P lp0 no entries I return to try to insmod lp and still get Using /lin/modules/2.2.15-4mdk/misc/lp.o /lib/modules/2.2.15-4mdk/misc/lp.o: init_module: Device or resource busy
So what now? Thanks a lot for keeping me going on this. Colin
---------------------------------------- Content-Type: application/rtf; charset="iso-8859-1"; name="Attachment: 1" Content-Transfer-Encoding: base64 Content-Description: filename="text1.rtf" ---------------------------------------- -- Andy Stewart, Founder Worcester Linux Users' Group Worcester, MA USA http://www.wlug.org