similar to: Firewire, USB + CentOS

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 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

Tripwire is probably one of must-have utilities for many system administrators. However, it is missing from almost all recent Red Hattish distributions. IMO, probably due to the fact that source compiles only on i386, and needs patches to compile almost every time new major version of gcc is released. However, in absence of good replacement, this is all we have. (IMO, other tools such as AIDE

I have 2 servers: On both, I did yum update. One upgraded the kernel, the other didn't. Why? TIA, Dave Augustus

Any chance we can set up a low-volume "centos-announce" list so that we all don't have to read all of these non-Centos-specific E-mail threads about people figuring out how to admin a Linux box when all we need to know is when major releases/milestones/news items are available? Regards, -Tom

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:

The following errata for CentOS-2 have been built and uploaded the the centos mirror: RHSA-2004:634-01 Updated zip package fixes security issue Files available: zip-2.3-10.1.i386.rpm More details are available from the RedHat web site at https://rhn.redhat.com/errata/rh21as-errata.html The easy way to make sure you are up to date with all the latest patches is to run: # yum update -- John

A friend sent me an ipod to office to transfer music to it. It had a firewire cable and I have an Audigy soundcard with a firewire port. But when I connected the ipod to the firewire port, I got a lot of weird numbers and interrupt errors and the system crashed badly. Is there some problem with firewire support in the kernel? -- Roger D. Vargas http://dsgp.blogspot.com | Linux, programaci?n,

i have an ati radeon 7000. what i have to do for 3d aceleration? remember: my english is no good.... :)

I just installed a fresh 3.3 system (because those are the ISO's I had on hand). Upon running yum update, it starts to download headers and then stalls. I hit Ctl-C and it continues to download about 4-5 more headers and stalls. I hit Ctl-C again and it pulls a few more headers. Anyone seen this and/or know how to fix it? TIA Mike

I''ve just started using CentOS as an alternative OS for some servers for a project. At the time 3.4 was the release of choice. I''m curious how long the CentOS project will release fixes and patched rpms for 3.4 before it would be necessary to migrate these machines to 4.x. I rather know in advance so I can plan accordingly and slowly migrate these over time. I do realize that 4.x

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

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

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

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

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

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.

Hi! After switching from UMS (dated 20090701+c0bf670) to KMS (as of 2010-02-01), almost any X activity causes buffer underruns on my firewire soundcard. When the X pointer changes from arrow to the vertical text selection bar, firewire streaming is interrupted. Same with scrolling in firefox or hovering over a link, thus changing the pointer to "hand". Looks like nouveau is disabling

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