Page 1 of 4 123 ... LastLast
Results 1 to 10 of 32

Thread: Getting Firewire (IEEE-1394) to work with 11.1

  1. #1
    Join Date
    Aug 2009
    Location
    Wales
    Posts
    49

    Unhappy Getting Firewire (IEEE-1394) to work with 11.1

    After I installed openSUSE 11.1 / KDE on a 64-bit HP laptop, I connected an external WD hard-drive via Firewire, but it didn't appear in the Device Notifier, and it's not in the Dolphin display either. (The controller does show up in Hardware Information, as "Texas Instruments OHCI Compliant IEEE 1394 Host Controller".)

    So I installed libraw1394 and -8 with Yast, but it makes no difference.

    Anyone know how to proceed?

  2. #2
    Join Date
    Mar 2008
    Location
    Phuket, Thailand
    Posts
    27,109
    Blog Entries
    40

    Default Re: Getting Firewire (IEEE-1394) to work with 11.1

    Quote Originally Posted by Weyland-Yutani View Post
    After I installed openSUSE 11.1 / KDE on a 64-bit HP laptop, I connected an external WD hard-drive via Firewire, but it didn't appear in the Device Notifier, and it's not in the Dolphin display either. (The controller does show up in Hardware Information, as "Texas Instruments OHCI Compliant IEEE 1394 Host Controller".)

    So I installed libraw1394 and -8 with Yast, but it makes no difference.

    Anyone know how to proceed?
    My external firewire drives "just work" with both a 32-bit and 64-bit openSUSE-11.1, both running KDE-3.5.10.

    Some suggestions:
    1. is this a dual USB/firewire external drive? If so, does the USB work?
    2. assuming the external drive is formatted as NTFS, then take the external drive to a running Windows PC, and plug the drive in the Windows PC. Then unmount the drive properly (using the lower right icon method on your windows desktop for removing hardware) ...
    3. consider running an MS-Windows " chkdsk /f " on your external firewire drive, to fix any errors.
    4. ensure the external firewire drive is NOT mentioned as a separate line in your openSUSE-11.1's /etc/fstab file. If so, back up the file, and then remove the firewire drive's entry from the nominal /etc/fstab file.
    5. boot your PC to openSUSE-11.1 without the external firewire drive plugged in and then type: su -c 'fdisk -l' #enter root password when prompted and keep a record of that, and then ...
    6. plug your external firewire drive in to your openSUSE PC, and then type: su -c 'fdisk -l' #enter root password when promted and then compare that to step-5. Is there a difference? What is the difference (ie is your external drive recognized via fdisk);

  3. #3
    Join Date
    Aug 2009
    Location
    Wales
    Posts
    49

    Default Re: Getting Firewire (IEEE-1394) to work with 11.1

    Quote Originally Posted by oldcpu View Post
    My external firewire drives "just work" with both a 32-bit and 64-bit openSUSE-11.1, both running KDE-3.5.10.

    Some suggestions:
    1. is this a dual USB/firewire external drive? If so, does the USB work? [Yes. Yes.]

    2. assuming the external drive is formatted as NTFS, then take the external drive to a running Windows PC, and plug the drive in the Windows PC. Then unmount the drive properly (using the lower right icon method on your windows desktop for removing hardware) ... [I'd already done this, but did it again.]

    3. consider running an MS-Windows " chkdsk /f " on your external firewire drive, to fix any errors. [Haven't done this yet.]

    4. ensure the external firewire drive is NOT mentioned as a separate line in your openSUSE-11.1's /etc/fstab file. If so, back up the file, and then remove the firewire drive's entry from the nominal /etc/fstab file. [Can't see it in there.]

    5. boot your PC to openSUSE-11.1 without the external firewire drive plugged in and then type: su -c 'fdisk -l' #enter root password when prompted and keep a record of that, and then ... [See 6.]

    6. plug your external firewire drive in to your openSUSE PC, and then type: su -c 'fdisk -l' #enter root password when promted and then compare that to step-5. Is there a difference? What is the difference (ie is your external drive recognized via fdisk); [6. results are the same as 5. Still doesn't appear in Dolphin.]
    Thanks, Oldcpu. [The oldest one I'm familiar with was in an IBM System 360/50 mainframe. Happy days.]

    Actually there are two identical dual-interface WD external drives, one all NTFS and the other all FAT32. Behaviour is the same for both. I've only tried connecting them one-at-a-time via Firewire so far. (There's only one socket on the laptop, and no daisy-chain attempted.)

  4. #4
    Join Date
    Jun 2008
    Location
    Groningen, Netherlands
    Posts
    20,925
    Blog Entries
    14

    Default Re: Getting Firewire (IEEE-1394) to work with 11.1

    Can you post output of:

    lsmod | grep 1394

    This would show us if at least something is loaded for the firewire protocol.
    ° Appreciate my reply? Click the star and let me know why.

    ° Perfection is not gonna happen. No way.

    http://en.opensuse.org/User:Knurpht
    http://nl.opensuse.org/Gebruiker:Knurpht

  5. #5
    Join Date
    Aug 2009
    Location
    Wales
    Posts
    49

    Default Re: Getting Firewire (IEEE-1394) to work with 11.1

    Quote Originally Posted by Knurpht View Post
    Can you post output of:

    lsmod | grep 1394

    This would show us if at least something is loaded for the firewire protocol.
    My pleasure . . .

    Code:
    [18:54:25 /etc]> lsmod|grep 1394
    ohci1394                  31364   0
    ieee1394                  98464   2 sbp2,ohci1394
    [18:56:28 /etc]>
    

  6. #6
    Join Date
    Mar 2008
    Location
    Phuket, Thailand
    Posts
    27,109
    Blog Entries
    40

    Default Re: Getting Firewire (IEEE-1394) to work with 11.1

    Quote Originally Posted by Weyland-Yutani View Post
    6. plug your external firewire drive in to your openSUSE PC, and then type: su -c 'fdisk -l' #enter root password when promted and then compare that to step-5. Is there a difference? What is the difference (ie is your external drive recognized via fdisk);
    [6. results are the same as 5. Still doesn't appear in Dolphin.]
    I was not so much interested in it appearing in dolphin, to see if " fdisk -l " detects it.

    its good that the USB detects it (and presumeably it shows up with " fdisk -l " when you plug in via USB).

    Have you tested the drive's Firewire with MS-windows? It works? I'm somewhat surprised it does not show up with "fdisk". Your dolphin statement makes me think you did not understand what I asked, ... you did run "fdisk" twice, right? And compare the outputs with drive plugged and not plugged in? Note you may have to give the drive a minute or so after plugging in (dependant on the drive).

    I'm wondering if UDEV/HAL have a problem with Firewire on your drive.

    The: lsmod | grep 1394 #command without the drive plugged in gives me this:
    Code:
    oldcpu@hal1000:~> lsmod | grep 1394
    ohci1394               31364  0
    ieee1394               98464  1 ohci1394
    oldcpu@hal1000:~>
    where my system works.

    with the drive plugged in gives me this (where again, my drive works):
    Code:
    oldcpu@hal1000:~> lsmod | grep 1394
    ohci1394               31364  1
    ieee1394               98464  2 sbp2,ohci1394
    Also for comparison, the "fdisk -l" gives me this with my drive plugged (where sdb is the firewire external drive on my PC):
    Code:
    hal1000:/home/oldcpu # fdisk -l
    
    Disk /dev/sda: 1500.3 GB, 1500301910016 bytes
    255 heads, 63 sectors/track, 182401 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0x00094fab
    
       Device Boot      Start         End      Blocks   Id  System
    /dev/sda1               1       12748   102398278+   7  HPFS/NTFS
    /dev/sda2   *       12749       16572    30716280   83  Linux
    /dev/sda3           16573       16827     2048287+  82  Linux swap / Solaris
    /dev/sda4           16828      182401  1329973155    5  Extended
    /dev/sda5           16828      176027  1278773968+  83  Linux
    /dev/sda6          176028      177939    15358108+  83  Linux
    /dev/sda7          177940      182401    35840983+  83  Linux
    
    Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
    255 heads, 63 sectors/track, 121601 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0x844f0716
    
       Device Boot      Start         End      Blocks   Id  System
    /dev/sdb1               1      121601   976760001    7  HPFS/NTFS

  7. #7
    Join Date
    Aug 2009
    Location
    Wales
    Posts
    49

    Default Re: Getting Firewire (IEEE-1394) to work with 11.1

    Yes, I did fdisk twice, before and after connecting the drive, and gave it plenty of time to ready itself. Identical results. No trace of the external drive. (I meant AND doesn't appear in Dolphin. Also not in the Device Notifier.)

    It's the same with the lsmod display. Doesn't change whether or not the Firewire cable is connected (sbp2 always appears).

    The drives work fine on the same machine in XP with Firewire. In fact that's how I wrote most of their contents in the first place.

  8. #8
    Join Date
    Mar 2008
    Location
    Phuket, Thailand
    Posts
    27,109
    Blog Entries
    40

    Default Re: Getting Firewire (IEEE-1394) to work with 11.1

    Quote Originally Posted by Weyland-Yutani View Post
    It's the same with the lsmod display. Doesn't change whether or not the Firewire cable is connected (sbp2 always appears).
    Do you have any other USB or firewire devices plugged in at the same time?

    I'm still suspicious this could be hal or udev related (which is well beyond my expertise to address)

  9. #9
    Join Date
    Aug 2009
    Location
    Wales
    Posts
    49

    Smile Re: Getting Firewire (IEEE-1394) to work with 11.1

    Quote Originally Posted by oldcpu View Post
    Do you have any other USB or firewire devices plugged in at the same time?

    I'm still suspicious this could be hal or udev related (which is well beyond my expertise to address)
    No other Firewire devices (there's only one socket), and only a USB mouse. No other connections to anything except an ADSL router via Ethernet.

    I've seen HAL mentioned in a Dolphin message, but I can't remember the context.

    . . . I had switched the laptop off, but I just booted it up again to check out the HAL message. This time the drive was powered on and connected during boot, and it came up with no problem. Strangely reminiscent of how Windoze often behaves.

    Looks like my problem has solved itself. Thanks for your time, Oldcpu, and my apologies for wasting it.

  10. #10
    Join Date
    Jun 2008
    Location
    The English Lake District. UK - GMT/BST
    Posts
    36,857
    Blog Entries
    20

    Default Re: Getting Firewire (IEEE-1394) to work with 11.1

    This time the drive was powered on and connected during boot, and it came up with no problem.
    It looks like that was all you needed to do then?
    Tumbleweed_KDE
    My Articles Was I any help? If yes: Click the star below

Page 1 of 4 123 ... LastLast

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •