I just setup a FireWire audio interface. Everything works fine, except for I need rw-rw-rw- permissions on /dev/fw0. I can always sudo chmod 666 /dev/fw0 just before setting the thing up, but then it will be gone on the next rebooting.The solution to modify /etc/udev/rules.d/020-permissions.rules (which is for Ubuntu Breezy) doesn't go well for Ubuntu 10.10 Maverick because there is no /etc/udev/rules.d directory.
I have a FireWire camera LifeSize connected to my PC in the FireWire interface. My PC has miniPCI slot and with external converter its having a FireWire interface. Now its Ubuntu who is not showing me anything at all when i try:
$ uname -a Linux desktop 2.6.38-11-generic-pae #48-Ubuntu SMP Fri Jul 29 20:51:21 UTC 2011 i686 i686 i386 GNU/Linux
I'm using FFADO on JACK in order to use my firewire device (M-Audio Profire 610) and I seem to have the opposite issue as others who have similar problems. Everything starts up fine, and I can record audio into Ardour using my inputs, but I can't get any output from any of my 8 line outs.
I've checked the connections using QjackCtl, and I tried to route audio from another program (Audacious) but I can't seem to pull audio out of the device (or the computer won't send my device audio?).
I'm currently pursuing a CCNA certification. I need to use a so called "Eagle Server" to do my lab exercises. I have the Linux Live CD (FEDORA CORE 3 KERNEL 2.6.12) and I have installed it on a laptop that I have (TOSHIBA EQUIUM M50-164, PSM57E). This laptop had Windows XP installed, so I created a 4GB FAT partition and booted with the Live CD.I need the CD in the tray every time I want to run Linux. Without the CD, it boots to Windows XP. Also, according to Eagle Server documentation, any modification to the server is available even after reboot. Well, that is not happening to me. Does someone have a clue why the server doesn't save the modifications? Is it because I need the Live CD to boot, even after I have installed on a FAT partition?
Eagle server supports only 1 network interface card, eth0. When I first run the server it showed me that the hardware mapped to eth0 was my wireless adapter. There is no option to disable it in my BIOS, so I just removed the hardware myself. After rebooting it show eth1394 on eth0. I presume that is the FireWire Adapter.What can I do so that eth0 is mapped to my LAN adapter (Marvell Yukon 88E8036 PCI-E Fast Ethernet)?Is there a way do disable FireWire?Please remember that due to 1st problem above, any changes to the server are not available after reboot So the main problem is that I can't ping from Eagle Server to the router and vice-versa
Is there an application that allows one to 'export' a drive or virtual disk image to firewire so that the machine at the other end sees the computer as a regular firewire drive? Apple computers can do that via their target disk mode (hold down t on boot), but I am searching for an application that would work under Windows or Linux.The goal is to boot an older Apple iBook, which can not boot from USB, via this emulated firewire drive.
I want to import raw High Def video into my computer so I can edit it on Cinelerra. Ubuntu doesn't allow you to use the ieee 1394 cable by default and everything I've tried to make it work, hasn't!!I don't want to go back to windows, pay a ton of money for some video editing software when there is an excellent video editing program already on my computer.]
Amarok 2 can search through music collection using ID3v2 tag's 'bpm' field. That would be very nice to retag the entire music collection so I can find the 'mood' of the track I like.However I've not found any beat-detection software that could have helped me. Have you ever used one? CLI, preferably. Also I'm interested if there's anything alike for tagging FLACs with the same 'bpm' field.
When I downloaded the motion detection sw "Motion" I found in the following path: /etc/motion/ motion.conf and 4 thread files in case of using several cameras.
Q1: Which language is that configuration file written? Q2: I need to collect the source of Motion. Is that configuration file + the 4 thread files which in the /etc/motion directory only the source of the program neither there is some files in another paths I don't know?
I want to add a Lacie external drive to x64 box with SL55, but it has only Firewire interface. After searching a bit the net I could not find a working solution how to make the PCI card and the drive recogizable by the system, even if I removed Firewire from RHEL blacklist. The system does not see this piece of hardware. Does anyone has a positive experience with RHEL/SL with that issue? Similar trends search lists only quite old treads - ane recent experience?
In my college many proxy : port (like 220.127.116.11:8080)are using to get Internet connection, performance of each proxy changes, how can i decide which one is working well at particular time. is there any way to switch over them automatically?
When I boot it takes about 5 seconds for the firewire device (fw0) to load. I don't use firewire and I would like to disable it to help improve my boot time. My BIOS doesn't have an option to turn it off. Is there a way I can turn it off in Ubuntu?
I have several laptops that all have firewire ports. Here is what I want to do. connect two laptops together using firewire across the table don't care about any existing network connection either laptop might have in progress use firewire for an interconnecting ad-hoc, static network link establish file and folder sharing between the two laptops (NFS makes a lot of sense but there are other options) Here is a likely scenario.
Two folks meet at some hotspot with a lot of data to share and exchange. Each is likely already on the net through the hotspot. Connecting firewire point-to-point gets an ad-hoc net and subnet that is independent of whatever might be happening with the hotspot. When this ad-hoc net comes up, udev or deviceKit (or whatever) rules enable the automatic sharing.
I purchased a WD My Book with Firewire. What I have noticed is that whether I run Fedora or Ubuntu, the file transfers are slow compared to Windows Vista. The drive is formatted NTFS. For example, on the Fedora system I get about 30MB/s. Boot into Vista and I get about 36MB/s. On my laptop, using Ubuntu, I get about 36MB/s. In Vista on the same laptop I get about 48MB/s. It was around 35MB/s in Vista, but then I turned on the drive caching (a Vista setting for "performance"). So my guess is that Linux in general has the same issue.
I notice a similar story with wireless N on the laptop. Much slower in Ubuntu than in Vista, by almost 50%. Why would this be? I tried Fedora Live on the laptop as well, but got no better results for either wireless-N or firewire400. What I do notice is that I get the following when attaching the drive:
scsi 11:0:0:0: Direct-Access WD My Book 1028 PQ: 0 ANSI: 4 sd 11:0:0:0: Attached scsi generic sg9 type 0 sd 11:0:0:0: [sdi] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB) sd 11:0:0:0: [sdi] Write Protect is off sd 11:0:0:0: [sdi] Mode Sense: 10 00 00 00 sd 11:0:0:0: [sdi] Cache data unavailable sd 11:0:0:0: [sdi] Assuming drive cache: write through
I've searched using Google, but can't come up with anything.
I have successfully installed ubuntu on a seagate goflex hd and can get it to boot with using a usb cable and refit on my mac. But I cannot get it to boot with a firewire cable and I have not seen any instructions on how to do this with an intel imac, only a ppc.
The mac does recognize the external hard drive when I hold the option key when I turn on the mac, but I get a "no bootable device found" error once I select it...same thing happens with refit and firewire cable. Any ideas on how to get this to work? I am ok with running it via usb cable, but would like the firewire option.
I'm thinking of getting a forensic bridge to help with fixing machines and I was wondering if the support was good for Firewire and if so do they show up in /dev like hda and sda do so I can keep using my normal set of tools.
I just compiled my first own kernel (I'm using Arch Linux), following the tutorial on the german site. Now I tried to boot it, I ended up failing with this message: Code: Waiting 10 seconds for device /dev/sda1 ... Root device '/dev/sda1' doesn't exist, Attempting to create it. ERROR: Unable to determine major/minor number of root device '/dev/sda1' Here is the important part of my menu.lst:
I simply copy&pasted the Arch-entry, i.e. I also had the disk by uuid there. The failure message was the same, just the root device name was the different name Also, at first I did not have the initrd line in my menu.lst (as written in my tutorial that I may not need it). In this case I had this error message:
I recently switched to Linux. I got a Camcorder connected to my machine via firewire that under Win i used as a webcam. So I want the same to work in debian, but honestly i don't know how to do it. The thing i tried was to use a loopback device via v4l2loopback, so what i did exactly is:
1. install v4l2loopback 2. modprobe v4l2loopback 3. feed it via ffmpeg Code: Select allffmpeg -f iec61883 -i auto -f v4l2 /dev/video0this so far works like a charm, i can open the stream via vlc for example if i choose open device and point it to /dev/video0
My problem now is the device detection. For example "Cheese" and the adobe flash plugin doesn't recognize any webcam.
Funning fc13 64bit and trying to get an Edirol FA-66 running. I bought it on the fact that ffado said it was fully supported... Altho I can't for the life of me work out how to install it in fedora... everything seems to be set up for ubuntu and the derivatives... I'm not up on using the terminal as I've managed to find everything else as an RPM etc so am not 100% on compiling from source but if that's the only way that's the only way...
I have a different problem with Firewire drives than I've seen posted here before. All my Firewire drives work just fine - too fine in fact. I can't boot without all of them being attached. Without them attached Suse just boots into a command prompt in maitenance mode. With ALL of them attached Suse boots just fine. I have tried shutting down normally with dirves attached and shutting down normally with drives disconnected (both unmounting before shut down and just discounting when machine powered off). Nothing changes. I need to be able to boot without the drives attached - I am using Suse 11.1 64 bit wiht KDE 3.5 on a 4 core Athlon. All system files are on internal hard drives - external drives just for data storage (no external USB drives).
I have updated my computer to Kubuntu 10.10 (which has the new firewire stack enabled by default) and now my firewire application is giving permission related problems. I try to read CSR_CHANNELS_AVAILABLE_HI (defined in libraw1394 which is used by the application) to see which isochronous channels are available to use:
With the old stack (raw1394) there are not problems and it runs fine and I get the octlet back containing the information about the free channels. But with the new stack (firewire_core and friends) I get a 'permission denied' (errno = 1) error. I do have permission to read/write /dev/fw* and I even tried running the application as root without any luck. If I read the config rom of a node (located at CSR_CONFIG_ROM) there are no permission problems and I am able to get the information/ What am I doing wrong? Did something change with the new stack (even though libraw1394 should be compatible with both stacks)? Is it a bug?
I want to capture DV-video through IEE1394 (FireWire) with Kino and Ubuntu 10.10. Seems I can't capture... When I plug in the camera there is no hot plug message (if there should be one? I've read it should...). The DV-out on the camera is enabled There is no option to enable/disable the port in my BIOS.
Some information: Code: a~# lspci | grep 1394 07:09.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 05) Hope there are some command to check?
I bought a USB to firewire cable to use with a DV camera, but I don't know what to do now. Do I need to enable firewire drivers, or is there something else I should do? I know I should read the manual.