I read in another forum that CentOS has problems with Firewire drives, something along the lines of whenever a new kernel is booted, the drives are gone.
Can anyone elaborate on that? I don't use Firewire drives (at all, yet), but information about this would be nice to have....
Thanks.
mhr
I haven't seen this problem from my drive. I am using Centos 5.4 and the configuration change that i found necessary was to uncomment the blacklist file /etc/modprobe.d/blacklist-firewire
regards- Rick
On Mon, Jan 25, 2010 at 11:52 AM, MHR mhullrich@gmail.com wrote:
I read in another forum that CentOS has problems with Firewire drives, something along the lines of whenever a new kernel is booted, the drives are gone.
Can anyone elaborate on that? I don't use Firewire drives (at all, yet), but information about this would be nice to have....
Thanks.
mhr _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
MHR wrote:
I read in another forum that CentOS has problems with Firewire drives, something along the lines of whenever a new kernel is booted, the drives are gone.
Can anyone elaborate on that? I don't use Firewire drives (at all, yet), but information about this would be nice to have....
Not personally experienced that issue, but when using kino to import from my dv camera, it almost always crashed in CentOS whenever doing anything that needed talking to the camera, but works *almost* flawlessly in Ubuntu. Same version of kino, some of libs built against may be different, but the biggest difference was firewire subsystem and firewire is where the crashes happened.
My firewire ipod however worked well in CentOS (until the ipod broke), so the issue may have been kino just working better with modern firewire subsystem than what CentOS has.
-
MHR -
Michael A. Peters -
Rick Philbrick