The only think I can think of is there's another program, more specifically a TSR that's running resident in the background causing modprobe to report with this error. Are you sure that you don't have lpd running in the background and that you have unloaded any other possibly conflicting modules that may take up your IRQ or use the parrallel port? Reboot your computer and check the bios settings for your parallel port's IRQ and memory address. Then modprobe lp and make sure it's displayed as shown in your /proc/interrupts and the other file that's in the /proc directory that shows memory address for devices connected to the system (sorry, I can't tell you exactly which one, I'm in school on a NT box). If everything isn't 'congruent', then you need to check to be sure that no other device is using those resources.
Debian Mail wrote: > > Just modprobe ppa and e-mail the output to this list. There should > > be an interrupt here for your parallel port, and yes, the parallel > > port can have conflicting irqs with other devices. Do that and let > > me see the output. > > #> modprobe ppa > /lib/modules/2.2.5/scsi/ppa.o: init_module: Device or resource busy > parport: Device or resource busy > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
