Linux Firewire disk
Results 1 to 9 of 9

Thread: Linux Firewire disk

  1. #1
    Leftie Linux Lover the_JinX's Avatar
    Join Date
    Nov 2001
    Location
    Beverwijk Netherlands
    Posts
    2,534

    Linux Firewire disk

    Heey all,

    I seem to have trouble gettinng my 250Gb firewire disk (Maxtor 5000XT) to work on linux (slackware 9) on my laptop..

    lspci tells me it's a:
    Code:
    02:07.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link)
    firewire ccontroller, but I can't seem to load the module..

    if I look at dmesg tells me:
    Code:
    PCI: Found IRQ 11 for device 02:07.0
    ohci1394_0: Remapped memory spaces reg 0xe4968800
    ohci1394_0: Soft reset finished
    ohci1394_0: Iso contexts reg: 000000a8 implemented: ffffffff
    ohci1394_0: 32 iso receive contexts available
    ohci1394_0: Iso contexts reg: 00000098 implemented: ffffffff
    ohci1394_0: 32 iso transmit contexts available
    ohci1394_0: No IR DMA context available
    ohci1394_0: Freeing dma_rcv_ctx 0
    ohci1394_0: Runaway loop while stopping context...
    ohci1394: Failed to allocate IR context
    ohci1394_0: Freeing dma_rcv_ctx 0
    ohci1394_0: Runaway loop while stopping context...
    ohci1394_0: Freeing dma_rcv_ctx 0
    ohci1394_0: Runaway loop while stopping context...
    ohci1394_0: Freeing dma_trm_ctx 0
    ohci1394_0: Runaway loop while stopping context...
    ohci1394_0: Freeing dma_trm_ctx 1
    ohci1394_0: Runaway loop while stopping context...
    ohci1394: $Rev: 578 $ Ben Collins <bcollins@debian.org>
    aboutt 10 times..

    and I can't seem to be gettting anything to work..

    Anybody with an idea ??
    ASCII stupid question, get a stupid ANSI.
    When in Russia, pet a PETSCII.

    Get your ass over to SLAYRadio the best station for C64 Remixes !

  2. #2
    Senior Member
    Join Date
    Aug 2002
    Posts
    508

    Re: Linux Firewire disk

    Originally posted here by the_JinX

    ohci1394_0: No IR DMA context available
    Heeya the_JinX,

    Look like you have problem with your DMA. Have you play around with hdparm to change your DMA?.

    What happen when you do :
    # hdparm /dev/hda

    And then you should see something like this:
    using_dma=0 (off)
    Try to turn it on to =1 using hdparm command.

    This is just my opinion..I could be wrong.

    Hope this helps


    Annya
    Not an image or image does not exist!
    Not an image or image does not exist!

  3. #3
    Senior Member
    Join Date
    Jan 2002
    Posts
    1,207
    sweet_angel:

    hdparm has nothing to do with firewire. hdparm is for setting up (mostly) IDE discs. The dma option does not have any effect and is not implemented on non-IDE discs.

    To the best of my knowledge, assuming the kernel can set the adapter up right (which I suspect in this case it can't), then a firewire HD should appear as if it were a SCSI one, hence be /dev/sda or whatever.

    Yes, the problem is related to DMAs, but hdparm cannot help. hdparm does not affect the DMA on any non-ATAPI device. Most devices like SCSI, firewire controllers should always use DMA.

  4. #4
    Senior Member
    Join Date
    Aug 2002
    Posts
    508
    Originally posted here by slarty
    sweet_angel:

    hdparm has nothing to do with firewire. hdparm is for setting up (mostly) IDE discs. The dma option does not have any effect and is not implemented on non-IDE discs.

    To the best of my knowledge, assuming the kernel can set the adapter up right (which I suspect in this case it can't), then a firewire HD should appear as if it were a SCSI one, hence be /dev/sda or whatever.

    Yes, the problem is related to DMAs, but hdparm cannot help. hdparm does not affect the DMA on any non-ATAPI device. Most devices like SCSI, firewire controllers should always use DMA.

    Thanks Slarty..I could be wrong for that..just my opinion though and actually I have second opinion:

    Try to rebuild kernel or try using different kernel and look at "firewire section" (you need to enable it) and should be look like this :
    "IEEE 1394 support -> IEEE 1394" - required by OHCI1394
    "IEEE 1394 support -> OHCI 1394" - required by SBP-2
    "IEEE 1394 support -> SBP-2 support" - driver for hard drives, CD-ROMs, DVDs, and so on.
    and BTW this in on my laptop

    Cheers
    Not an image or image does not exist!
    Not an image or image does not exist!

  5. #5
    Leftie Linux Lover the_JinX's Avatar
    Join Date
    Nov 2001
    Location
    Beverwijk Netherlands
    Posts
    2,534
    Yeah,, I have added all of them..

    but I found this..

    http://www.linux1394.org/cgi-bin/view_device.cgi?id=503

    it seems to be a toshiba 5100 (mine is a 5100-603) problem..

    they are working on it...
    ASCII stupid question, get a stupid ANSI.
    When in Russia, pet a PETSCII.

    Get your ass over to SLAYRadio the best station for C64 Remixes !

  6. #6
    Senior Member
    Join Date
    Aug 2002
    Posts
    508
    *
    Not working with kernels of recent distributions (redhat 9.0, mandrake 9.1). Not working after updating these kernels.
    more information:
    http://sourceforge.net/tracker/index...52&atid=202252
    So they have problem with latest kernel on RH 9,Mandrake 9.1. Have you try use old kernel or maybe try install slackware 8.1, let's see what happen..
    Not an image or image does not exist!
    Not an image or image does not exist!

  7. #7
    Leftie Linux Lover the_JinX's Avatar
    Join Date
    Nov 2001
    Location
    Beverwijk Netherlands
    Posts
    2,534
    Yeah.. I might just try a 2.4.18 kernel..
    or combining kernel sources (old firewire drivers, new kernel)..
    I'm gonna go and try some later tonight..

    Luckily it doesn't have to be operational before august 15th
    ASCII stupid question, get a stupid ANSI.
    When in Russia, pet a PETSCII.

    Get your ass over to SLAYRadio the best station for C64 Remixes !

  8. #8
    Junior Member
    Join Date
    Feb 2003
    Posts
    1

    Firewire device

    Hello:

    log on as root in your terminal window and type modprobe ohci1394, hit enter, then type modprobe sbp2 and hit enter. This should load the drivers for Firewire devices. If it is your only Firewire device it should be identified as /dev/sda1. Make sure to have user permissions to it and mount it to another directory name if possible. Also, make sure this device is listed in your /etc/fstab and etc/mtab as well. This helped me with my SuSE box.

    Good Luck

  9. #9
    Leftie Linux Lover the_JinX's Avatar
    Join Date
    Nov 2001
    Location
    Beverwijk Netherlands
    Posts
    2,534
    as I stated before the loading of the ohci1394 module is the problem..

    It is autodetected by my hotplug susbsystem when I use the usb connector and that works but is slow (1mb/s).

    It is also autodetected when I use the firewire, but then it gives the same as above

    ohci1394_0: Runaway loop while stopping context...

    but it does indeed seem to work on the 2.4.18 kernel, so I'll be doing some merging asap..
    ASCII stupid question, get a stupid ANSI.
    When in Russia, pet a PETSCII.

    Get your ass over to SLAYRadio the best station for C64 Remixes !

Posting Permissions

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