similar to: FireWire Security issues

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

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

No need to store that, struct drm_framebuffer has all we need. Also update VBE_DISPI_INDEX_VIRT_WIDTH register, otherwise we'll have a fixes broken display in case pitch != width * cpp. Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> --- drivers/gpu/drm/bochs/bochs.h | 2 -- drivers/gpu/drm/bochs/bochs_hw.c | 18 +++++++++--------- drivers/gpu/drm/bochs/bochs_kms.c | 2 +-

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

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

Not needed, writing to VBE_DISPI_INDEX_VIRT_HEIGHT has no effect anyway. Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> --- drivers/gpu/drm/bochs/bochs.h | 1 - drivers/gpu/drm/bochs/bochs_hw.c | 8 ++------ 2 files changed, 2 insertions(+), 7 deletions(-) diff --git a/drivers/gpu/drm/bochs/bochs.h b/drivers/gpu/drm/bochs/bochs.h index 246f05f4a711..5c90b76708ef 100644 ---

Call drm_dev_unregister() first in bochs_pci_remove(). Hook bochs_unload() into the new .release callback, to make sure cleanup is done when all users are gone. Add ready bool to state struct and move bochs_hw_fini() call from bochs_unload() to bochs_pci_remove() to make sure hardware is not touched after bochs_pci_remove returns. Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> ---

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

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

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

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

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.

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

Create a separate bochs_hw_setformat function to configure the framebuffer format (actually just the byteorder). Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> --- drivers/gpu/drm/bochs/bochs.h | 5 +++-- drivers/gpu/drm/bochs/bochs_hw.c | 19 ++++++++++++------- drivers/gpu/drm/bochs/bochs_kms.c | 3 ++- 3 files changed, 17 insertions(+), 10 deletions(-) diff --git

Call bochs_unload via drm_driver.release to make sure we release stuff when it is safe to do so. Use drm_dev_{enter,exit,unplug} to avoid touching hardware after device removal. Tidy up here and there. Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> --- drivers/gpu/drm/bochs/bochs_drv.c | 6 +++--- drivers/gpu/drm/bochs/bochs_hw.c | 24 +++++++++++++++++++++++- 2 files changed, 26

Add bochs_hw_set_*_endian() helper functions, to set the framebuffer byteorder at mode set time. Support both DRM_FORMAT_XRGB8888 and DRM_FORMAT_BGRX8888 framebuffer formats, no matter what the native machine byte order is. Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> --- drivers/gpu/drm/bochs/bochs.h | 4 ++- drivers/gpu/drm/bochs/bochs_fbdev.c | 3 +-

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