Re: Momobay CX-1 with 40 GB IBM Hardisk
Brought to you by:
aeb,
bencollins
From: Grahame J. <gb...@th...> - 2002-08-26 14:10:59
|
Stefan, My one works on both USB and ieee1394, but I had to do some playing first. To get ieee1394 working I had to compile the 2.4.19 kernel which has the=20 compatable version of ieee1394 for your drive. Once you have installed=20 the new kernel put the line alias char-major-117 ohci1394 into /etc/modules.conf and then do a modprobe ohci1394 you should now see your drive in cat /proc/scsi/scsi or cat/proc/scsi/sbp2/0 If so you can mount /dev/sda1 in your favourite place. I have problems unloading the ohci1394 module and have to reboot to get=20 it to reset (as it will when you reboot) Good luck Grahame Jordan Stefan Eilers wrote: >-----BEGIN PGP SIGNED MESSAGE----- >Hash: SHA1 > >Hi ! > >I was unable to mount the device, but it was shown as "works" in the=20 >compatibility list.=20 > >Can somebody pleas help me !? > >First some system information: >I am using Kernel 2.4.18, libraw1394-0.9.0, OHCI-Driver > >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D >lspci: > >00:00.0 Host bridge: VIA Technologies, Inc. VT82C693A/694x [Apollo PRO13= 3x]=20 >(rev c4) >00:01.0 PCI bridge: VIA Technologies, Inc. VT82C598/694x [Apollo MVP3/Pr= o133x=20 >AGP] >00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South]= (rev=20 >22) >00:07.1 IDE interface: VIA Technologies, Inc. Bus Master IDE (rev 10) >00:07.2 USB Controller: VIA Technologies, Inc. UHCI USB (rev 10) >00:07.3 USB Controller: VIA Technologies, Inc. UHCI USB (rev 10) >00:07.4 Host bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI]= (rev=20 >30) >00:07.5 Multimedia audio controller: VIA Technologies, Inc. AC97 Audio=20 >Controller (rev 20) >00:0c.0 Unknown mass storage controller: Promise Technology, Inc. 20265 = (rev=20 >02) >00:0d.0 FireWire (IEEE 1394): Texas Instruments: Unknown device 8020 >00:0e.0 Ethernet controller: 3Com Corporation 3c905C-TX [Fast Etherlink]= (rev=20 >74) >00:10.0 SCSI storage controller: Adaptec 7892A (rev 02) >01:00.0 VGA compatible controller: nVidia Corporation NV11 (rev a1) >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D > >I have a strange problem with my Firewire device: > >Loading the drivers may work perfectly: > >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D >ieee1394: sbp2: Node 0:1023: Max speed [S400] - Max payload [2048] >ieee1394: sbp2: Driver forced to serialize I/O (serialize_io =3D 1) >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D > >The Application gscanbus shows the following information: > >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D >SelfID Info >- ----------- >Physical ID: 0 >Link active: Yes >Gap Count: 63 >PHY Speed: S400 >PHY Delay: <=3D144ns >IRM Capable: No >Power Class: -1W >Port 0: Not connected >Port 1: Connected to parent node >Init. reset: No > >CSR ROM Info >- ------------ >GUID: 0x0001041010003DAB >Node Capabilities: 0x000083C0 >Vendor ID: 0x00000104 >Unit Spec ID: 0x0000609E >Unit SW Version: 0x00010483 >Model ID: 0x00001010 >Nr. Textual Leafes: 2 > >Vendor: DVICO Co., Ltd. >Textual Leafes:=20 >"DViCO"=20 >REV2 > >AV/C Subunits >- ------------- >N/A >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D > > >But if I start "rescan_scsi_bus.sh": > >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D >Scanning for device 1 0 0 0 ... >OLD: Host: scsi1 Channel: 00 Id: 00 Lun: 00 > Vendor: 01234567 Model: 89ABCDEFGHIJKLMN Rev: OPQR > Type: Unknown ANSI SCSI revision: 07 >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D > > > >I don't think that this looks quit good !? > >"dmesg" shows this: >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D >ieee1394: sbp2: Node 0:1023: Max speed [S400] - Max payload [2048] >ieee1394: sbp2: Driver forced to serialize I/O (serialize_io =3D 1) >ieee1394: sbp2: Node 0:1023: Max speed [S400] - Max payload [2048] >scsi1 : IEEE-1394 SBP-2 protocol driver >scsi: unknown type 20 > Vendor: 01234567 Model: 89ABCDEFGHIJKLMN Rev: OPQR > Type: Unknown ANSI SCSI revision: 07 >Attached scsi generic sg3 at scsi1, channel 0, id 0, lun 0, type 20 >resize_dma_pool: unknown device type 20 >smb_trans2_request: result=3D-104, setting invalid >smb_retry: successful, new pid=3D21459, generation=3D52 >scsi singledevice 0 0 1 0 >scsi singledevice 0 0 2 0 >scsi singledevice 0 0 3 0 >scsi singledevice 0 0 4 0 >scsi singledevice 0 0 6 0 >scsi singledevice 0 0 7 0 >scsi singledevice 1 0 1 0 >scsi singledevice 1 0 2 0 >scsi singledevice 1 0 3 0 >scsi singledevice 1 0 4 0 >scsi singledevice 1 0 5 0 >scsi singledevice 1 0 6 0 >scsi singledevice 1 0 7 0 >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D > > > > >- --=20 >Dipl.-Ing. Stefan Eilers | Institut f=FCr Systems Engineering >Tel. +49 511 762 19737 | System- und >Fax +49 511 762 19733 | Rechnerarchitektur >EMail: ei...@sr... | Universit=E4t Hannover > | Appelstra=DFe 4 (Raum 118) > | D-30167 Hannover >-----BEGIN PGP SIGNATURE----- >Version: GnuPG v1.0.4 (GNU/Linux) >Comment: For info see http://www.gnupg.org > >iD8DBQE9ajFpgHBfg4VrVxARAkqHAJ9D8ObiPYAAmnYNmiL9DSG9Rn0ShQCfeKiG >SfnQZ3laqDtvSjNMJZiyJYE=3D >=3Dz1Mq >-----END PGP SIGNATURE----- > > >------------------------------------------------------- >This sf.net email is sponsored by: OSDN - Tired of that same old >cell phone? Get a new here for FREE! >https://www.inphonic.com/r.asp?r________________________________________= _______ >mailing list Lin...@li... >https://lists.sourceforge.net/lists/listinfo/linux1394-user > |