D&C Lug - Home Page
Devon & Cornwall Linux Users' Group

[ Date Index ][ Thread Index ]
[ <= Previous by date / thread ] [ Next by date / thread => ]

Re: [LUG] post message



On 22-May-01 at 20:01:45 Jody Dunstan wrote:
> parport0: irq7 detected
> parport0: found 1 dasisy chained device
> parport0: no more nibblre data
> parport0: device reported incorrect data field (61, should be 62)
> parport:0: (addr 0): SCSI adapter, IMG VP1
> parport0: Printer, canon BJC-1000.
> 
Okay, on my system I have:

 parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE,EPP]
 parport0: Found 1 daisy-chained devices
 parport0: No more nibble data (1 bytes)
 parport0: device reported incorrect length field (61, should be 62)
 parport0 (addr 0): SCSI adapter, IMG VP1
 parport_pc: Via 686A parallel port: io=0x378, irq=7                         

so it looks similar. I assume the mention of your printer is because it is
being detected through the zip drive. I also have in dmesg:

 Adding Swap: 136544k swap-space (priority 1)
 Adding Swap: 136544k swap-space (priority 1)
 imm: Version 2.05 (for Linux 2.4.0)
 imm: Found device at ID 6, Attempting to use EPP 16 bit
 imm: Communication established at 0x378 with ID 6 using EPP 16 bit
 scsi0 : Iomega VPI2 (imm) interface
   Vendor: IOMEGA    Model: ZIP 100           Rev: P.05
   Type:   Direct-Access                      ANSI SCSI revision: 02
 Attached scsi removable disk sda at scsi0, channel 0, id 6, lun 0
 sda : READ CAPACITY failed.
 sda : status = 0, message = 00, host = 0, driver = 08
 sda : extended sense code = 2
 sda : block size assumed to be 512 bytes, disk size 1GB.
  sda: I/O error: dev 08:00, sector 0
  unable to read partition table                                             

The first lines are simply to indicate where in dmesg this occurs. The 'read
capacity failed', 'i/o error' etc are simply because the drive was on but
had no disk in it. Look for this sort of thing in your dmesg output.

In /etc/modules.conf I have:
  alias parport_lowlevel parport_pc

and in /etc/rc.modules I have:
  /sbin/insmod imm >/dev/null 2>&1

This last one simply loads the module upon system booting. If it isn't used
then it gets automatically removed as far as I know (haven't really
checked). So you may still need to manually load the module during your
login session.


John.

------------------------------------------------------------------------
John Horne, University of Plymouth, UK           Tel: +44 (0)1752 233914
E-mail: jhorne@xxxxxxxxxxxxxx
PGP key available from public key servers
--
The Mailing List for the Devon & Cornwall LUG
Mail majordomo@xxxxxxxxxxxx with "unsubscribe list" in the
message body to unsubscribe.


Lynx friendly