You are not logged in.
Years ago I was given an M-Audio Firewire Solo audio interface. It's not one I would've chosen - simply because of firewire, but beggars can't be choosers eh?
I've had it working via a PCMCIA firewire adapter in my laptop, but I recently put together a new Desktop and cannot, for the life of me, get it working.
The firewire card in question is this one. lspci shares the following information:
09:00.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller (rev 80)I must admit that I simply assumed it would work under Linux and didn't do any research - possibly a fatal mistake... That said, I've googled now and I still can't find anything that lists it as either compatible or incompatible.
I do have libffado installed. lsmod | grep firewire returns:
snd_firewire_lib 28672 1 snd_bebob
snd_rawmidi 28672 2 snd_firewire_lib,snd_bebob
snd_pcm 90112 7 snd_pcm_oss,snd_hda_intel,snd_hda_codec,snd_firewire_lib,snd_hda_core,snd_bebob
firewire_ohci 40960 0
firewire_core 57344 3 snd_firewire_lib,snd_bebob,firewire_ohci
crc_itu_t 16384 1 firewire_coreInitially, whenever I plugged the device in dmesg would contain errors like "AMD-Vi event logged io_page_fault device", but googling suggested that I needed to add iommu=pt to the kernel line in grub, which I've done. There seems to be some debate as to whether I should've gone with pt, soft or auto...
If I try and run jack using "firewire" as the driver, the computer either instantly reboots, or, very occasionally, simply powers off. This is very disconcerting and I hope I'm not damaging my system in any way. If I could get to the point where I could actually start jack then I could probably take it from there.
Edit: I've also noticed that alsamixer lists the audio interface as FW Solo, but claims that it doesn't have any controls...
Last edited by phunni (2017-05-23 20:08:44)
Offline
Bump - no thoughts on this one?
Offline
I just ran "dmesg" post plugging the device in and got the following error trace:
[ 3843.732630] WARNING: CPU: 7 PID: 7764 at kernel/workqueue.c:2423 check_flush_dependency+0xc3/0x120
[ 3843.732638] workqueue: WQ_MEM_RECLAIM firewire:fw_device_workfn [firewire_core] is flushing !WQ_MEM_RECLAIM events:do_registration [snd_bebob]
[ 3843.732638] Modules linked in: snd_bebob snd_firewire_lib snd_rawmidi nvidia_drm(PO) nvidia_modeset(PO) nvidia(PO) edac_mce_amd edac_core kvm_amd kvm irqbypass crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc drm_kms_helper aesni_intel snd_hda_codec_realtek input_leds aes_x86_64 joydev crypto_simd mousedev led_class glue_helper snd_hda_codec_generic evdev mac_hid cryptd drm snd_hda_intel r8169 pcspkr mii snd_hda_codec syscopyarea sysfillrect sysimgblt ccp snd_hda_core fb_sys_fops rng_core snd_hwdep shpchp i2c_piix4 wmi tpm_infineon 8250_dw acpi_cpufreq i2c_designware_platform tpm_tis i2c_designware_core tpm_tis_core button tpm sch_fq_codel snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_timer snd soundcore ip_tables x_tables
[ 3843.732667] ext4 crc16 jbd2 fscrypto mbcache sr_mod cdrom hid_generic sd_mod usbhid hid ahci libahci xhci_pci firewire_ohci xhci_hcd libata firewire_core crc_itu_t usbcore scsi_mod usb_common serio
[ 3843.732677] CPU: 7 PID: 7764 Comm: kworker/7:0 Tainted: P O 4.11.2-1-ARCH #1
[ 3843.732678] Hardware name: Gigabyte Technology Co., Ltd. AB350-Gaming 3/AB350-Gaming 3-CF, BIOS F6 04/07/2017
[ 3843.732681] Workqueue: firewire fw_device_workfn [firewire_core]
[ 3843.732683] Call Trace:
[ 3843.732687] dump_stack+0x63/0x81
[ 3843.732689] __warn+0xcb/0xf0
[ 3843.732691] ? bebob_card_free+0x50/0x50 [snd_bebob]
[ 3843.732692] warn_slowpath_fmt+0x5a/0x80
[ 3843.732694] ? radix_tree_iter_tag_set+0x1c/0x20
[ 3843.732695] ? ida_remove+0xe0/0x130
[ 3843.732697] ? init_fw_attribute_group+0xc0/0xc0 [firewire_core]
[ 3843.732698] check_flush_dependency+0xc3/0x120
[ 3843.732699] ? bebob_card_free+0x50/0x50 [snd_bebob]
[ 3843.732701] flush_work+0xb2/0x1c0
[ 3843.732703] ? kmem_cache_free+0x1e8/0x210
[ 3843.732704] ? kmem_cache_free+0x1e8/0x210
[ 3843.732706] __cancel_work_timer+0x155/0x1f0
[ 3843.732708] ? kernfs_name_hash+0x17/0x80
[ 3843.732710] cancel_delayed_work_sync+0x13/0x20
[ 3843.732711] bebob_remove+0x1f/0x40 [snd_bebob]
[ 3843.732713] fw_unit_remove+0x16/0x20 [firewire_core]
[ 3843.732716] device_release_driver_internal+0x158/0x200
[ 3843.732717] device_release_driver+0x12/0x20
[ 3843.732718] bus_remove_device+0x104/0x180
[ 3843.732720] device_del+0x1e8/0x390
[ 3843.732722] ? put_prev_entity+0x40/0xc10
[ 3843.732724] ? sched_clock+0x9/0x10
[ 3843.732725] ? set_broadcast_channel+0x130/0x130 [firewire_core]
[ 3843.732726] device_unregister+0x1a/0x60
[ 3843.732728] shutdown_unit+0xe/0x20 [firewire_core]
[ 3843.732729] device_for_each_child+0x50/0x90
[ 3843.732731] fw_device_shutdown+0x9e/0xf0 [firewire_core]
[ 3843.732733] fw_device_workfn+0xc/0x10 [firewire_core]
[ 3843.732734] process_one_work+0x1e0/0x490
[ 3843.732736] worker_thread+0x48/0x4e0
[ 3843.732737] kthread+0x125/0x140
[ 3843.732738] ? process_one_work+0x490/0x490
[ 3843.732739] ? kthread_create_on_node+0x70/0x70
[ 3843.732741] ret_from_fork+0x2c/0x40Does this provide any (helpful) information?
Offline