similar to: nouveau interrupts firewire ISO streaming

Hi..... I just bought a External HD with USB/FireWire interfaces. I was trying to connect it by firewire and nothing happened, but it's connected by USB, there is no problem. This is the "fdisk - l" output when i connect it by USB Disco /dev/sdc: 160.0 GB, 160041885696 bytes 255 cabezas, 63 sectores/pista, 19457 cilindros Unidades = cilindros de 16065 * 512 = 8225280 bytes

I am being given a digital camcorder. It uses Mini DV tapes and either connects via typical RCA cables (IE to a tv) or via FireWire. I don't have the brand on hand, but I was told it can be ripped to DV like any standard FireWire camcorder (I believe dvgrab will be sufficient). I just installed an older FireWire card I have that I used at one point in Fedora for my iPod. It was a PITA

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

Hi all! I'm trying to use my first-ever firewire device, and just OOB I'm not getting very far, so advice would be appreciated. When I plug in the device I see some entries in /var/log/messages: Jul 27 14:50:30 fcshome kernel: firewire_core: phy config: card 0, new root=ffc1, gap_count=5 Jul 27 14:50:31 fcshome kernel: firewire_core: created device fw1: GUID 0003f300118123f9, S100

Hi folks: Firewire was not supported in 4.0 due to the upstream provider not including it. Is it in 4.1? Or is it still out of the mainline upstream kernel provider? What about centosplus? Centosplus has been listed as unsupported. I presume this means that they are/were one-off builds with missing functionality (e.g. xfs, etc), and are not updated. Is this the case? I am looking

I got a WD 1TB My Book with eSATA/USB/Firewire400 connectivity to backup data on a client Centos 5.1 machine. USB 2.0 works fine out of the box but is rather slow, Nautilus predicts about 1+ hour to fully backup just one day's worth of data or about 100GB. So I was hoping Firewire would be faster, which is why we got the version with all 3 interfaces to experiment with first. Following the

Assuming I have a firewire card with a supported chipset, is there anything special I need to do in order for the kernel to recognize the card? Shouldn't kudzu "wake up" and configure the card when I boot up after installing it? This is a brand spanking new 4.4 system and a supported Agere chipset firewire card. I'm having trouble tickling devices connected to the card.

Hello, looking into the issue described in the advisory below I wonder how to tackle this issues. Primarily I ask myself * is there any reason not to filter all physical memory access by default * what would be the appropriate way to change the filter set? a sysctl? Regards Maximillian Dornseif FireWire/IEEE 1394 direct memory access - CAN-2004-1038 Advisory URL:

I just recently downloaded and installed the CentOS 3.3 release, and I'm having a bit of a problem... It appears that no support for firewire drives has been included. I am unable to find the ohci1394 or sbp2 modules anywhere. Are there other packages which must be installed from the distribution to get firewire devices to be recognized? Thanks. --Steve

Hello, Having a problem getting Centos to see my firewire connected camcorder. Here what I have thus far; Installed the kernek fron centos-plus and checked that libraw1394.x86_64 and libraw1394_8.x86_64 are installed Kernel i'm running is 2.6.9-34.106.unsupported here are some outputs from my machine; ~ $ lspci | grep -i firewire 00:07.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE

Message I recieved from a work colleage.... Wonder if anyone can help the guy? --------FORWARDED MESSAGE---------------------- I finally ditched my freebsd and put centos on my box. Trouble is I can''t figure out how to get it to automount my USB and firewire (ipod) bits. Any ideas? Googling has left me a bit frustrated. No one seems to be able to do it. I have a /etc/fstab that

Hi all, CentOS noob trying v5 for the first time -- What's the best way to get firewire modules onboard? Build a custom kernel? I'm not seeing any cent5 compatible module-rpms for this. Any general pointing in the right direction would be appreciated. Thanks

An interesting thing I just noticed here testing out some Firewire drives with OpenSolaris. Setup : OpenSolaris 2009.06 and a dev version (snv_129) 2 500Gb Firewire 400 drives with integrated hubs for daisy-chaining (net: 4 devices on the chain) - one SATA bridge - one PATA bridge Created a zpool with both drives as simple vdevs Started a zfs send/recv to backup a local filesystem Watching

I have set up an ocfs system using two linux nodes connected using firewire. Details: # uname -a Linux testrac2 2.4.21-9.0.1.ELorafw1 #1 Tue Mar 2 14:42:46 PST 2004 i686 i686 i386 GNU/Linux # cat /etc/issue Red Hat Enterprise Linux ES release 3 (Taroon Update 1) # rpm -qa |grep ocfs ocfs-tools-1.1.2-1 ocfs-2.4.21-EL-1.0.12-1 ocfs-support-1.1.2-1 <> Oracle version: 9.2.0.5 Cluster

I'm currently looking at how to deal with the lack of usable MACs in Infiniba(n)d and Firewire. Instead of presenting the MAC address when querying for the config file, these guys need either the Client Identifier, or the PC UUID. The Client Identifier is a fairly opaque object which tends to include various fixed portions; the PC UUID is far to often not at all or incorrectly programmed.

On Wednesday 15 September 2004 10:01 am, Neil wrote: > You would have been getting an exact copy on disc, but I suspect the > software you used was degrading playback. I think you're right. When I play video-a1v7x352y240.ogg, some of the artifacts I noticed in the firewire captured video.dv are no longer there. The *.dv video is sharper, but the *.ogg video, at 1/16th the size,

Helo, I'm trying to update a centos server with a kernel form the centos.plus repro because it contain Firewire/IEEE1394 support. But when y do a : # yum update The kernel from the base is more recent thant the centos plus repro I have tried with the http://wiki.centos.org/PackageManagement/Yum/Priorities plug-in and it didn't take the right kernel :

Hi, I am trying to get FreeBSD 4.7 to connect to a Maxtor 5000XT drive, but I get the following when connecting it -> Apr 26 09:19:43 chowder /kernel: fwohci0: node_id = 0xc000ffc1, CYCLEMASTER mode Apr 26 09:19:43 chowder /kernel: firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 (me) Apr 26 09:19:50 chowder /kernel: fwohci0: BUS reset Apr 26 09:19:50 chowder /kernel: fwohci0: node_id =

Hi I have a Firewire connected Micronet 1.5TB RAID with a single large ext3 filesystem on one partition on a dual Xeon system. I am checking out from an extremely large cvs repository (don't ask) to this drive over the course of many days, and intermittently I get bad blocks and the filesystem goes read-only. This is not related to any power failure or anything similar. The RAID is currently

A bit more info about my system; I edited /etc/modprobe.d/blacklist-firewire and commented out the blacklist like so it looks like so; #blacklist firewire-ohci Running lspci returns; 10:0b.0 Firewire (IEEE 1394): Texas Instruments TSB82AA2 IEEE-1394b Link Layer Controller (rev 02) lsmod | grep firewire returns; firewire_sbp2 50897 0 firewire_core 79305 1 firewire_sbp2 scsi_mod