From: Stefan R. <st...@s5...> - 2012-01-27 09:25:08
|
On Jan 27 Stefan Thomas wrote: > By the way: the fa-66 works well with windows, it can't be a hardware > problem. Good, then the issue is most likely with how firewire-ohci drives this Ricoh controller. Perhaps the "disable MSI" workaround needs to be given right at the beginning when the driver is attached to the controller after power-up, i.e. cold boot? One way to do that is to boot Linux with the module parameter added to the kernel command line which can be entered when the boot loader comes up (grub or lilo or whatever). I think the syntax of the parameter to be appended to the kernel command line is firewire_ohci.quirks=17 (The command line starts with the name of the kernel image which is to be booted, and other kernel parameters, if any.) Another way would be to add the line options firewire-ohci quirks=17 to one of the configuration files in /etc/modprobe.d (can be a newly created file just for that purpose). But if your distribution loads the firewire-ohci kernel module already from an initrd (initial RAM disk), then you need to copy this modprobe configuration into the initrd and rebuild the initrd image. [Side note, also for the list archives: Those firewire-ohci module parameters are not meant to be configured by users. This is all just for testing the behavior of this particular controller here. If it turns out this way that firewire-ohci's built-in quirk flags need to be amended, then we update the driver so that it behaves as intended without needing extra configuration.] > Dear Clemens, > what do You mean by: > > Please make a new log, but with 7 instead of 3 as debug parameter. > > I just had typed in dmesg and pasted this output. This refers to the echo command which I posted earlier, i.e. echo 7 > /sys/module/firewire_ohci/parameters/debug (connect the FA-66, wait about 20 seconds) echo 0 > /sys/module/firewire_ohci/parameters/debug dmesg -- Stefan Richter -=====-===-- ---= ==-== http://arcgraph.de/sr/ |