Re: Asus SCB-1608-D problems

On Sun, 2003-09-21 at 23:32, Robert Reid wrote:
> Hi all,
>
> I'm new to the list, but couldn't find any archives to search, so
> figured I'd just ask away. I've just got a shiny new SCB-1608-D CD-R/RW
> DVD Combo Drive, and according to the linux1394 compatibility list it
> works fine. However, I've been unable to get it to go with my laptop.
> The syslog entries from insmod-ing ohci1394, ieee1394 and sbp2 are:
>
> Sep 20 22:47:47 triton kernel: ohci1394: $Rev: 1010 $ Ben Collins
> <bcollins@debi
> an.org>
> Sep 20 22:47:47 triton kernel: PCI: Found IRQ 11 for device 01:0e.0
> Sep 20 22:47:47 triton kernel: PCI: Sharing IRQ 11 with 00:1f.3
> Sep 20 22:47:47 triton kernel: PCI: Sharing IRQ 11 with 00:1f.5
> Sep 20 22:47:47 triton kernel: PCI: Sharing IRQ 11 with 00:1f.6
> Sep 20 22:47:47 triton kernel: PCI: Sharing IRQ 11 with 01:0a.1
> Sep 20 22:47:47 triton kernel: ohci1394_0: OHCI-1394 1.0 (PCI):
> IRQ=[11] MMIO=[
> e0200000-e02007ff] Max Packet=[1024]
> Sep 20 22:47:47 triton kernel: ieee1394: Current remote IRM is not
> 1394a-2000 co
> mpliant, resetting...
> Sep 20 22:47:47 triton kernel: ieee1394: unsolicited response packet
> received -
> np
> Sep 20 22:47:47 triton kernel: ieee1394: contents: ffc17160 ffc00000
> 00000000 01
> 0000d1
> Sep 20 22:47:48 triton kernel: ieee1394: NodeMgr: hotplug policy returned -2
> Sep 20 22:47:48 triton kernel: ieee1394: Node added: ID:BUS[0-00:1023]
> GUID[000
> 1a3a050001dad]
> Sep 20 22:47:48 triton kernel: ieee1394: Host added: ID:BUS[0-01:1023]
> GUID[000
> 00e100070b2f9]
> Sep 20 22:47:49 triton kernel: raw1394: /dev/raw1394 device initialized
> Sep 20 22:47:52 triton kernel: sbp2: $Rev: 1010 $ Ben Collins
> <bcollins@debian.o
> rg>
> Sep 20 22:47:52 triton kernel: scsi1 : SCSI emulation for IEEE-1394
> SBP-2 Device
> s
> Sep 20 22:48:12 triton kernel: ieee1394: sbp2: Error logging into SBP-2
> device -
> login timed-out
>
>
> I think this last error is the killer - basically it does not recognize
> the drive. I wonder whether the "unsolicited response ..." messages
> above are part of the problem too?
>
Correct, the login timeout is the problem. Not sure why though. Perhaps
the bus reset to reset the current IRM (isochronouse resource manager)
caused the sbp2 device to not be able to respond in time. Did you try
re-plugging the drive and/or reloading the sbp2 module?

-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
mailing list Linux1394-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux1394-user
Received on Mon Sep 22 16:06:04 2003