Re: firewire 800 trouble

Alexis Zubrow wrote:
> First, do I need to upgrade to kernel 2.6.* to possibly get this
> working? I'm hesitant to do this b/c this is a computational node that
> needs to be quite stable. Is there any advantage of upgrading to a
> later 2.4.27 kernel? Presently, I'm using 2.4.24.

Strictly spoken, IEEE 1394 support should not be enabled on a critical
machine. That said, I suggest you try either the latest kernel 2.4 or
the latest 1394 drivers from linux1394.org's linux-2.4 branch in your
current kernel. I have not kept up though which driver revisions
addressed IEEE 1394b issues though, i.e. I do not know if there are any
benefits from newer drivers than those in 2.4.24.

Here is how you update:
- Check out the "branches/linux-2.4/" directory from the repo, either
   using the svn client or as a tarball. If the repo is down again,
   look at http://me.in-berlin.de/~s5r6/linux1394/.
- cd linux-2.4.24/drivers/
- mv ieee1394 ieee1394.orig
- mv ~/linux-2.4 ieee1394 # the checked-out sorce directory
- cd ..
- make menuconfig # or xconfig
- make dep modules modules_install
Also build, install, and boot a new kernel if you changed something
that affects the kernel image instead of just kernel modules.

> Second, if the rescan script doesn't pick up the new sd device, what
> would you recommend for finding and testing it?

The syslog and /proc/bus/ieee1394/devices (under Linux 2.6 replaced by a
sysfs interface which is not really intended to serve dignostic purposes).

> I've tried gscanbus and it seems to do nothing. When I try killing it,
> the computer hangs and needs to be hard rebooted.

Gscanbus is not prepared for IEEE 1394b. However it should still show
basic information about a working 1394b setup. The fact that it hangs
the whole system means there is something seriously wrong with the
drivers, not so much with gscanbus. (Sorry for pointig out the obvious.)

> I've even tried using fdisk and hdparm on an assortment of devices to
> see if it is there:
> $ fdisk -l /dev/sd?
> I haven't found anything this way.

If there are not even syslog messages of sbp2 attempting to acces the
device then neither the rescan script nor fdisk and so on will find
anything.

> Again, I don't get any message when I plug and unplug the firewire,
> so I assume this means that it is not recognizing the disk.

You could enable "excessive" logging in the 1394 section of the kernel
configuration. But try updated drivers first.

-- 
Stefan Richter
-=====-=-=-- ==-- ---==
http://arcgraph.de/sr/
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
mailing list Linux1394-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux1394-user