Firewire HD problem connecting [HELP]

maginotjr · 07-07-2005, 09:02 PM

Im having problem to connect my Firewire external HD... when I connect it I cant mount sda (there is no sd* in dev) in dmesg I rereive the follow line :

Code:

ieee1394: Error parsing configrom for node 0-00:1023
ieee1394: Node changed: 0-00:1023 -> 0-01:1023

#lsmod

Code:

Module                  Size  Used by
snd_pcm_oss            48416  1
snd_mixer_oss          17408  1 snd_pcm_oss
parport_pc             22724  0
parport                20928  1 parport_pc
ati_agp                 6796  1
usbhid                 32608  0
uhci_hcd               30352  0
ehci_hcd               29704  0
usbcore               108796  4 usbhid,uhci_hcd,ehci_hcd
ohci1394               32436  0
evdev                   7552  0
ide_scsi               14468  0
ppp_generic            24724  0
slhc                    6144  1 ppp_generic
agpgart                29896  1 ati_agp

any ideia? I just want to mount my HD ... ;///

maginotjr · 07-08-2005, 12:35 AM

Well, since NOBODY could help-me I have to help myself. I did it and find the answer and now the firewire HD is working perfectly... And Im thinking about buy it realy serious.

The secret was: www.linux1394.org
and have the follow modules: sbp2, ieee1394, ohci1394, raw1394
And I downloaed some pkgs from the site above...

2 hours later some reboots and command line, now its connected at 400mb/s

lionslair · 10-25-2005, 06:04 AM

That site does not appear to load anymore does anyone know what happened to it?

maginotjr · 10-25-2005, 09:44 AM

Are you having trouble with you Firewire device??

What kind of problem?

lionslair · 10-26-2005, 09:36 AM

Quote:

Originally posted by maginotjr
Are you having trouble with you Firewire device??

What kind of problem?

Yes I am. Please see this thread
http://www.linuxquestions.org/questi...hreadid=368054

I have read everything on here and other resources butI have found no solution yet. I keep plugging away at it. Thing is my device and setup all worked fine until I had a power outage. I have bought new cables and everything however.

I can mount the device still if I plug it into the onboard usb ports which are only usb1

I did get this error last night when trying to run the backup using this slow transfer method.

See below error message?

Oct 25 22:40:06 rzepecki-04 kernel: usb 1-1: new full speed USB device using address 5
Oct 25 22:40:14 rzepecki-04 kernel: usb 1-1: new full speed USB device using address 7
Oct 25 22:40:14 rzepecki-04 kernel: usb 1-1: not running at top speed; connect to a high speed hub
Oct 25 22:40:14 rzepecki-04 kernel: scsi36 : SCSI emulation for USB Mass Storage devices
Oct 25 22:40:14 rzepecki-04 kernel: Vendor: ST316002 Model: 1A Rev: 8.01
Oct 25 22:40:14 rzepecki-04 kernel: Type: Direct-Access ANSI SCSI revision: 02
Oct 25 22:40:14 rzepecki-04 kernel: SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
Oct 25 22:40:14 rzepecki-04 kernel: /dev/scsi/host36/bus0/target0/lun0: p1
Oct 25 22:40:14 rzepecki-04 kernel: Attached scsi disk sda at scsi36, channel 0, id 0, lun 0
Oct 25 22:40:14 rzepecki-04 kernel: Attached scsi generic sg0 at scsi36, channel 0, id 0, lun 0, type 0
Oct 25 22:40:15 rzepecki-04 scsi.agent[1658]: sd_mod: loaded sucessfully (for disk)
Oct 25 22:40:15 rzepecki-04 usb.agent[1655]: usb-storage: already loaded
Oct 25 22:42:13 rzepecki-04 kernel: kjournald starting. Commit interval 5 seconds
Oct 25 22:42:13 rzepecki-04 kernel: EXT3 FS on sda1, internal journal
Oct 25 22:42:13 rzepecki-04 kernel: EXT3-fs: mounted filesystem with ordered data mode.
Oct 25 22:42:57 rzepecki-04 kernel: Current sda: sense key No Sense
Oct 25 22:43:33 rzepecki-04 kernel: __journal_remove_journal_head: freeing b_committed_data

Does this maybe mean that th3e disk is in someway corrupted?
Oct 25 22:43:39 rzepecki-04 last message repeated 16 times

Does this mean maybe the disk is corrupted and need re-formatting.

Please see thread metioned above for the full description of the problem and thank you for any help or suggestions you can give me.

maginotjr · 10-27-2005, 05:11 AM

Im not seeing no error message... for what Im seeing is:

Oct 25 22:40:06 rzepecki-04 kernel: usb 1-1: new full speed USB device using address 5
Oct 25 22:40:14 rzepecki-04 kernel: usb 1-1: new full speed USB device using address 7
Oct 25 22:40:14 rzepecki-04 kernel: usb 1-1: not running at top speed; connect to a high speed hub

The system setted an address to the device and recognized that it isnt 2.0 usb connection (not running at top speed).

Oct 25 22:40:14 rzepecki-04 kernel: scsi36 : SCSI emulation for USB Mass Storage devices
Oct 25 22:40:14 rzepecki-04 kernel: Vendor: ST316002 Model: 1A Rev: 8.01
Oct 25 22:40:14 rzepecki-04 kernel: Type: Direct-Access ANSI SCSI revision: 02
Oct 25 22:40:14 rzepecki-04 kernel: SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
Oct 25 22:40:14 rzepecki-04 kernel: /dev/scsi/host36/bus0/target0/lun0: p1
Oct 25 22:40:14 rzepecki-04 kernel: Attached scsi disk sda at scsi36, channel 0, id 0, lun 0
Oct 25 22:40:14 rzepecki-04 kernel: Attached scsi generic sg0 at scsi36, channel 0, id 0, lun 0, type 0
Oct 25 22:40:15 rzepecki-04 scsi.agent[1658]: sd_mod: loaded sucessfully (for disk)
Oct 25 22:40:15 rzepecki-04 usb.agent[1655]: usb-storage: already loaded

Recognized and setted the SCSI ID to the device, mounted the SCSI emulation with sg and the device in the /dev/sda1 block device.

Oct 25 22:42:13 rzepecki-04 kernel: kjournald starting. Commit interval 5 seconds
Oct 25 22:42:13 rzepecki-04 kernel: EXT3 FS on sda1, internal journal
Oct 25 22:42:13 rzepecki-04 kernel: EXT3-fs: mounted filesystem with ordered data mode.
Oct 25 22:42:57 rzepecki-04 kernel: Current sda: sense key No Sense
Oct 25 22:43:33 rzepecki-04 kernel: __journal_remove_journal_head: freeing b_committed_data

Started the journalling mode after found the EXT3 Filesystem type. Some config didnt match and it is freeing the information (maybe the repeat of the message if because it tries again and again)

---

For what I saw your device is perfectly connecting in USB mode.
To connect with the firewire (if nothing blowed off when the power went off) you have to be somekind persistent because the support for linux is still _very_ poor. To connect my device I recompiled the kernel to ensure I had the right drivers support for the firewire. I compiled with the IEEE1394 main module and RAW1394 (for firewire videocam, but who knows...), SBP2, OHCI1394, IDE-SCSI modules. Probably you already have ieee1394, sbp2, ohci1394 and ide-scsi. But is always good to confirm with:

Code:

# lsmod

if not listed load the modules

Code:

# modprobe ieee1394; modprobe ohci1394; modprobe sbp2; modprobe raw1394 (if you have it)

Now you can try what I do for making my linux box see my device. Load all modules with the device unplugged. Turn it on unplugged and plug in the machine. You can stay with a console window open and keep watching the log with #tail -f /var/log/messages waiting for a message close to what you posted here. With me is very normal that my box doesnt find my device in the first try so, I keep unplugging and plugging it sometimes (this is enought to my system find the device after some tries).

Try it, you may also put here the log of when you connect you firewire dev.

SBP2 have some option too, you can load the modules with serialize_io=1 (1=on 0=off), max_speed=2 (0=default, 1=100mb, 2=200mb, 3=300mb, 4=400mb).

Code:

#modinfo sbp2

will give you more information.

keep update.

[ ]'s

yoron · 12-16-2005, 08:31 AM

Interesting, i have a somewhat similar problem with slackware 10.2.
I'm using a firewire cd/dvd which i had no trouble installing Slackware from, but when i tried to mount it as:
root@xzonk:~# mount -t iso9660 /dev/sr0 /mnt/cdrom

i get this back
mount: /dev/sr0 is not a valid block device

In my fstab it's connected as follows:
----------------------------------
/dev/cdrom /mnt/cdrom auto noauto,owner,ro 0 0
-.-.-.-.-.-.-.---.-.-.-.-.-.-.--.-

So i tried to mount it like that:
root@xzonk:~# mount -t iso9660 /dev/cdrom /mnt/cdrom
-with this result-
mount: /dev/cdrom is not a valid block device

So i changed my fstab to /dev/sr0 and 'iso9660' instead of /dev/cdrom and 'auto'
Without success .. sooo?

And Vectorlinux f ex can boot on it, but when it's supposed to start reading from the same cd (?) it can't find it...
The ones that work are Mandrake/Mandriva 2005 and (almost

) Slackware, which btw i find to be the most undrstandable distro for now..
Any suggestions/solutions

maginotjr · 12-18-2005, 08:34 PM

for what I have noticed... sg0 is not a scsi driver to mount, you need to mount the sda, sdb, sdc, etc... so if you have a sg0 device you have to look for the partitions that are those I have just mentioned...

[ ]`s

yoron · 12-20-2005, 02:40 AM

ok & thanks