>>>>> Tim Waugh <twaugh@redhat.com>:
> On Sun, Jun 18, 2000 at 10:08:38PM +0200, Steinar Bang wrote:
>> Jun 19 00:03:10 doohan insmod: /lib/modules/2.2.10/misc/parport_pc.o: init_modu\
>> le: Device or resource busy
> [...]
>> 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?
> Device or resource busy means the driver didn't want to load. For
> parport_pc it probably means it didn't find any ports.
OK, thanx! Is there a way of finding the builtin parport manually?
Or will I need to dig up the specs on the PC and finding them there?
Is the BIOS a place to look?
> You can see what messages it logged (if any) by using the 'dmesg'
> command.
Here's the relevant bits of output from the dmesg command (everything
related to parport):
0x378: CTR: wrote 0x0c, read 0xff
0x378: DATA: wrote 0xaa, read 0xff
parport0: PC-style at 0x378 [SPP,PS2]
parport0: no IEEE-1284 device present.
lp0: using parport0 (polling).
0x378: CTR: wrote 0x0c, read 0xff
0x378: DATA: wrote 0xaa, read 0xff
parport0: PC-style at 0x378 [SPP,PS2]
parport0: no IEEE-1284 device present.
lp0: using parport0 (polling).
0x378: CTR: wrote 0x0c, read 0xff
0x378: DATA: wrote 0xaa, read 0xff
parport0: PC-style at 0x378 [SPP,PS2]
parport0: no IEEE-1284 device present.
lp0: using parport0 (polling).
lp: driver loaded but no devices found
lp: driver loaded but no devices found
lp: driver loaded but no devices found
lp: driver loaded but no devices found
lp: driver loaded but no devices found
-- 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 : Mon Jun 19 2000 - 11:08:18 EDT