>>>>> Gunther Mayer <gunther.mayer@braunschweig.okersurf.de>:
> Probably your parallel port is not at 0x378.
> If you provide io=0x378 in /etc/conf.modules (or /etc/modules.conf or elsewhere)
> the autodetection is disabled and parport trusts you blindly !
> Non-existant ISA ports read back as 0xff (see CTR and DATA above).
OK. This is the entry in /etc/conf.modules:
alias parport_lowlevel parport_pc
options parport_pc io=0x378 irq=none,none
I commented out the second line, rmmod'ed all parport modules, did a
"depmod -a", and tried cat'ing files to the /dev/lp0 device:
doohan:~ # cat .kderc >/dev/lp0
bash: /dev/lp0: No such device
Jun 19 00:03:10 doohan insmod: /lib/modules/2.2.10/misc/parport_pc.o: init_modu\
le: Device or resource busy
Jun 19 00:03:10 doohan insmod: /lib/modules/2.2.10/misc/parport_pc.o: insmod pa\
rport_lowlevel failed
Jun 19 00:03:10 doohan insmod: /lib/modules/2.2.10/misc/parport_pc.o: init_modu\
le: Device or resource busy
Jun 19 00:03:10 doohan insmod: /lib/modules/2.2.10/misc/parport_pc.o: insmod pa\
rport_lowlevel failed
Jun 19 00:03:10 doohan kernel: lp: driver loaded but no devices found
The results were the same for /dev/lp1 and /dev/lp2.
Is the reason that no devices were found that the parport_probe can't
find any? Or are the "Device or resource" busy messages above to
blame?
-- To unsubscribe, send mail to: linux-parport-request@torque.net --
-- with the single word "unsubscribe" in the body of the message. --
This archive was generated by hypermail 2b29 : Sun Jun 18 2000 - 16:18:07 EDT