E-mu 0404 and getting nowhere...
Moderators: MattKingUSA, khz
-
- Established Member
- Posts: 38
- Joined: Wed Jan 15, 2014 8:20 pm
Re: E-mu 0404 and getting nowhere...
Hmm, lots to think about.
I do have a 2018.6.25 AV Linux boot disk that I can play around with... due to the connectivity issues, I don't think I ever got to the hardware testing phase.
Let me pull out AV Linux again in a live environment off the thumb drive and see what it thinks of the Emu card. At this point, it may be easier to troubleshoot the wireless/wired internet settings in AV Linux if I can get a working sound card. Plus, with having used it for 5+ years, it would be nice to stick with the home team
Were scheduled to have a blizzard tomorrow. Work might let out early, and if so...more time to mess around with stuff!
@GMaq @linuxmusician01 and @merlyn + all the others you all have been so patient. Thank you. One way or another I will have to get the system back up and running because we need to finish tracking our cd. More info to come!
I do have a 2018.6.25 AV Linux boot disk that I can play around with... due to the connectivity issues, I don't think I ever got to the hardware testing phase.
Let me pull out AV Linux again in a live environment off the thumb drive and see what it thinks of the Emu card. At this point, it may be easier to troubleshoot the wireless/wired internet settings in AV Linux if I can get a working sound card. Plus, with having used it for 5+ years, it would be nice to stick with the home team
Were scheduled to have a blizzard tomorrow. Work might let out early, and if so...more time to mess around with stuff!
@GMaq @linuxmusician01 and @merlyn + all the others you all have been so patient. Thank you. One way or another I will have to get the system back up and running because we need to finish tracking our cd. More info to come!
-
- Established Member
- Posts: 38
- Joined: Wed Jan 15, 2014 8:20 pm
Re: E-mu 0404 and getting nowhere...
Okay, so I am playing around with AV Linux live disk from USB, and:
1) I have all the EMU files
2) I try the aplay -l command, and I get card 0: PCH [HDA Intel PCH] and Subdevices: 0/1, Subdevice #0: subdevice #0
So, it looks like even under this, It is not 'seeing' the card? Is all this starting to point toward hardware failure?
I wish I could show the actual code, but I cannot connect to wireless from the live cd, so I'm posting this from a separate laptop.
Also, Ardour can be started with either ALSA or Jack from the options in the load menu. If I select ALSA, it fails. If I select Jack, it works, but I get nothing, no signal at all.
Here is my signal chain:
mic --> preamp --> converter --> via SPDIF --> EMU 0404. I have tried both optical and SPDIF and nothing works.
I'm currently downloading the newest version of AV linux and will see if that makes a difference.
Don't know where else to go from here.
1) I have all the EMU files
2) I try the aplay -l command, and I get card 0: PCH [HDA Intel PCH] and Subdevices: 0/1, Subdevice #0: subdevice #0
So, it looks like even under this, It is not 'seeing' the card? Is all this starting to point toward hardware failure?
I wish I could show the actual code, but I cannot connect to wireless from the live cd, so I'm posting this from a separate laptop.
Also, Ardour can be started with either ALSA or Jack from the options in the load menu. If I select ALSA, it fails. If I select Jack, it works, but I get nothing, no signal at all.
Here is my signal chain:
mic --> preamp --> converter --> via SPDIF --> EMU 0404. I have tried both optical and SPDIF and nothing works.
I'm currently downloading the newest version of AV linux and will see if that makes a difference.
Don't know where else to go from here.
-
- Established Member
- Posts: 38
- Joined: Wed Jan 15, 2014 8:20 pm
Re: E-mu 0404 and getting nowhere...
Also, one other thing - in the Jack Audio Connection Kit, I am given the option of 2 interfaces:
1) hw: PCH HDA Intel
2) hw: PCH, 0 ALC887-VD Analog
I'm guessing that none of these is the Emu.
Ebay has an AF4 for about $45 with shipping, I'm wondering if I should just get that like I had before mine died and finish the recording project and then when I have a bit more $$, save up for something that is a card and plays nicer with Linux. Still not sure why even with the firmware files it is not showing up as an option.
1) hw: PCH HDA Intel
2) hw: PCH, 0 ALC887-VD Analog
I'm guessing that none of these is the Emu.
Ebay has an AF4 for about $45 with shipping, I'm wondering if I should just get that like I had before mine died and finish the recording project and then when I have a bit more $$, save up for something that is a card and plays nicer with Linux. Still not sure why even with the firmware files it is not showing up as an option.
- Linuxmusician01
- Established Member
- Posts: 1542
- Joined: Mon Feb 23, 2015 2:38 pm
- Location: Holland
- Has thanked: 772 times
- Been thanked: 142 times
Re: E-mu 0404 and getting nowhere...
You still need to load the firmware into the card. That Fw is probably proprietary so it cannot be included in Linux. If I'm not mistaken that Fw needs to be compiled from source. If I remember correctly you were almost there.
-
- Established Member
- Posts: 1392
- Joined: Thu Oct 11, 2018 4:13 pm
- Has thanked: 168 times
- Been thanked: 247 times
Re: E-mu 0404 and getting nowhere...
@ Linuxmusician01 As far as I can tell you're mistaken. alsa-firmware is a package, and like any other package it could be installed from a repo or built from source.
AV Linux comes with alsa-firmware pre-installed.
@ Red Leader The fact that lspci showed the Emu card means it isn't completely fried, although it maybe isn't working 100% either. If you have another PCI slot available you could try changing the slot. Other than that this does look like there's something wrong with the card.
AV Linux comes with alsa-firmware pre-installed.
@ Red Leader The fact that lspci showed the Emu card means it isn't completely fried, although it maybe isn't working 100% either. If you have another PCI slot available you could try changing the slot. Other than that this does look like there's something wrong with the card.
- Linuxmusician01
- Established Member
- Posts: 1542
- Joined: Mon Feb 23, 2015 2:38 pm
- Location: Holland
- Has thanked: 772 times
- Been thanked: 142 times
Re: E-mu 0404 and getting nowhere...
I stand corrected. Thank you for pointing that out. So much has been discussed in this topic that I've lost the way. Are you sure the Fw will be loaded automatically w/ that package installed?merlyn wrote:@ Linuxmusician01 As far as I can tell you're mistaken. alsa-firmware is a package, and like any other package it could be installed from a repo or built from source.
AV Linux comes with alsa-firmware pre-installed.
@ Red Leader The fact that lspci showed the Emu card means it isn't completely fried, although it maybe isn't working 100% either. If you have another PCI slot available you could try changing the slot. Other than that this does look like there's something wrong with the card.
-
- Established Member
- Posts: 1392
- Joined: Thu Oct 11, 2018 4:13 pm
- Has thanked: 168 times
- Been thanked: 247 times
Re: E-mu 0404 and getting nowhere...
I don't know the exact details, but yes, it should work.Linuxmusician01 wrote:Are you sure the Fw will be loaded automatically w/ that package installed?
@Red Leader OK, so Linux audio is complicated, but it isn't this complicated.
I was looking through the whole thread and you've had three problems (1) Your Echo Audiofire stopped working (2) your networking stopped working (3) your Emu card won't work. It seems too much. Is the problem elsewhere? Like the motherboard? It could be BIOS settings, if you know how to have a look at that.
Do you know that the Echo Audiofire is definitely dead? If you could try the Echo on a friends computer it would rule out a motherboard problem as the cause of the Echo failing.
-
- Established Member
- Posts: 38
- Joined: Wed Jan 15, 2014 8:20 pm
Re: E-mu 0404 and getting nowhere...
Well, what is weird is everything worked perfect, out of the box in Ubuntu. Wireless was fine, wired was fine, etc.
I thought that maybe with AV Linux being Debian based (I think?) there were some proprietary packages for firmware for the wireless card or ethernet adapter that were technically not 'free' so they were not included in the package? I don't know how AV Linux handles it, but I gave Debian a try and had the same problem with wireless and it said as much.
Regarding the AF4 unit. It doesn't have to be connected up to fritz out. When I turn it on, all the levels jump to max, with a loud, throbbing clicking hum and no sound can pass through it. I took out the guts to inspect and didn't immediately see anything fried, so I'm not sure.
I'm going to give the 2019 AV Linux a go tonight on the thumb drive and see what happens. It might be entertaining.
If in the long run I cannot get the Emu to work, I will move on to greener pastures. The thing IS from 2004, so several centuries old as far as tech goes!
I thought that maybe with AV Linux being Debian based (I think?) there were some proprietary packages for firmware for the wireless card or ethernet adapter that were technically not 'free' so they were not included in the package? I don't know how AV Linux handles it, but I gave Debian a try and had the same problem with wireless and it said as much.
Regarding the AF4 unit. It doesn't have to be connected up to fritz out. When I turn it on, all the levels jump to max, with a loud, throbbing clicking hum and no sound can pass through it. I took out the guts to inspect and didn't immediately see anything fried, so I'm not sure.
I'm going to give the 2019 AV Linux a go tonight on the thumb drive and see what happens. It might be entertaining.
If in the long run I cannot get the Emu to work, I will move on to greener pastures. The thing IS from 2004, so several centuries old as far as tech goes!
- Linuxmusician01
- Established Member
- Posts: 1542
- Joined: Mon Feb 23, 2015 2:38 pm
- Location: Holland
- Has thanked: 772 times
- Been thanked: 142 times
Re: E-mu 0404 and getting nowhere...
@Red Leader: how old is you computer? Like @Merlyn said: it might be your computer.
-
- Established Member
- Posts: 1392
- Joined: Thu Oct 11, 2018 4:13 pm
- Has thanked: 168 times
- Been thanked: 247 times
Re: E-mu 0404 and getting nowhere...
That means the motherboard is good.Red Leader wrote:Well, what is weird is everything worked perfect, out of the box in Ubuntu.
What I can't understand is that lspci shows the card and lsmod shows that the 10k1 module is loaded. I would have thought that means the card is working.
If you treat this as a hardware problem then changing the slot might work. You could try taking the card out then booting without the card. Shutdown and put the card back in, making sure it is fully pushed down in its slot. Then reboot.
It would be good if you knew that the Emu is definitely broken before you buy another card.
-
- Established Member
- Posts: 38
- Joined: Wed Jan 15, 2014 8:20 pm
Re: E-mu 0404 and getting nowhere...
Computer is about 4 years-ish old. Intel Core i5-3570k cpu, Gigabyte motherboard, 8gig RAM, etc all other components around that same vintage.Linuxmusician01 wrote:@Red Leader: how old is you computer? Like @Merlyn said: it might be your computer.
It might only have 1 PCI slot. I'd have to verify when I get home.
I'll load up the 2019 AV Linux and throw some lspci and lsmod commands it's way
We'll see what happens!
-
- Established Member
- Posts: 38
- Joined: Wed Jan 15, 2014 8:20 pm
Re: E-mu 0404 and getting nowhere...
Okay, I'm testing AV Linux 2019 now. Same internet connection prob. Anyway, here were the results from what it is seeing:
When I checked the 'setup' for QjackCtl, it still only gives me those two generic options that don't work.
How do I get it to see this card in QjackCtl, even with all the right firmware installed? Are we at the end of the road here?
Code: Select all
isotester@avl64box:~$ lspci
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09)
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
00:16.0 Communication controller: Intel Corporation 7 Series/C216 Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 7 Series/C216 Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 7 Series/C216 Chipset Family PCI Express Root Port 1 (rev c4)
00:1c.4 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 5 (rev c4)
00:1c.5 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 6 (rev c4)
00:1d.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a4)
00:1f.0 ISA bridge: Intel Corporation B75 Express Chipset LPC Controller (rev 04)
00:1f.2 IDE interface: Intel Corporation 7 Series/C210 Series Chipset Family 4-port SATA Controller [IDE mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 7 Series/C216 Chipset Family SMBus Controller (rev 04)
00:1f.5 IDE interface: Intel Corporation 7 Series/C210 Series Chipset Family 2-port SATA Controller [IDE mode] (rev 04)
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)
03:00.0 PCI bridge: Texas Instruments XIO2213A/B/XIO2221 PCI Express to PCI Bridge [Cheetah Express] (rev 01)
04:00.0 FireWire (IEEE 1394): Texas Instruments XIO2213A/B/XIO2221 IEEE-1394b OHCI Controller [Cheetah Express] (rev 01)
05:01.0 Multimedia audio controller: Creative Labs EMU10k2/CA0100/CA0102/CA10200 [Sound Blaster Audigy Series] (rev 03)
Code: Select all
isotester@avl64box:~$ lsmod
Module Size Used by
fuse 118784 3
arc4 16384 2
intel_rapl 24576 0
intel_powerclamp 16384 0
coretemp 16384 0
kvm_intel 180224 0
kvm 479232 1 kvm_intel
snd_hda_codec_realtek 106496 1
irqbypass 16384 1 kvm
snd_hda_codec_generic 81920 1 snd_hda_codec_realtek
crct10dif_pclmul 16384 0
crc32_pclmul 16384 0
ghash_clmulni_intel 16384 0
i915 1507328 7
pcbc 16384 0
snd_emu10k1 180224 0
aesni_intel 188416 1
snd_hda_intel 40960 3
snd_util_mem 16384 1 snd_emu10k1
snd_hda_codec 135168 3 snd_hda_intel,snd_hda_codec_generic,snd_hda_codec_realtek
snd_ac97_codec 139264 1 snd_emu10k1
aes_x86_64 20480 1 aesni_intel
cpufreq_userspace 16384 0
crypto_simd 16384 1 aesni_intel
ac97_bus 16384 1 snd_ac97_codec
glue_helper 16384 1 aesni_intel
snd_hda_core 81920 4 snd_hda_intel,snd_hda_codec,snd_hda_codec_generic,snd_hda_codec_realtek
cpufreq_powersave 16384 0
cryptd 28672 3 crypto_simd,ghash_clmulni_intel,aesni_intel
snd_rawmidi 36864 1 snd_emu10k1
cpufreq_conservative 16384 0
snd_hwdep 16384 2 snd_emu10k1,snd_hda_codec
snd_seq_device 16384 2 snd_emu10k1,snd_rawmidi
snd_pcm 114688 5 snd_hda_intel,snd_emu10k1,snd_hda_codec,snd_hda_core,snd_ac97_codec
iTCO_wdt 16384 0
ath9k_htc 81920 0
ath9k_common 20480 1 ath9k_htc
drm_kms_helper 196608 1 i915
iTCO_vendor_support 16384 1 iTCO_wdt
intel_cstate 16384 0
ath9k_hw 475136 2 ath9k_htc,ath9k_common
evdev 24576 18
serio_raw 16384 0
ath 32768 3 ath9k_htc,ath9k_hw,ath9k_common
intel_uncore 131072 0
mac80211 528384 1 ath9k_htc
snd_timer 36864 2 snd_emu10k1,snd_pcm
drm 442368 8 i915,drm_kms_helper
intel_rapl_perf 16384 0
pcspkr 16384 0
cfg80211 360448 4 ath9k_htc,mac80211,ath,ath9k_common
snd 90112 17 snd_hda_intel,snd_emu10k1,snd_hwdep,snd_hda_codec,snd_ac97_codec,snd_timer,snd_rawmidi,snd_hda_codec_generic,snd_seq_device,snd_hda_codec_realtek,snd_pcm
button 16384 1 i915
video 45056 1 i915
mei_me 32768 0
sg 36864 0
mei 102400 1 mei_me
rfkill 28672 3 cfg80211
ie31200_edac 16384 0
shpchp 40960 0
lpc_ich 28672 0
soundcore 16384 1 snd
i2c_algo_bit 16384 1 i915
binfmt_misc 20480 1
sunrpc 335872 1
parport_pc 32768 1
ppdev 20480 0
lp 20480 0
parport 57344 3 lp,parport_pc,ppdev
ip_tables 24576 0
x_tables 40960 1 ip_tables
autofs4 49152 2
squashfs 61440 1
zstd_decompress 90112 1 squashfs
xxhash 16384 1 zstd_decompress
loop 32768 2
overlay 102400 1
nls_cp437 20480 1
vfat 24576 1
fat 73728 1 vfat
ext4 483328 1
crc32c_generic 16384 0
crc16 16384 1 ext4
mbcache 16384 1 ext4
jbd2 86016 1 ext4
fscrypto 32768 1 ext4
nls_ascii 16384 1
hid_generic 16384 0
usbhid 57344 0
hid 135168 2 hid_generic,usbhid
sr_mod 28672 0
cdrom 69632 1 sr_mod
sd_mod 53248 4
uas 24576 0
usb_storage 65536 2 uas
ata_generic 16384 0
ata_piix 36864 1
xhci_pci 16384 0
ehci_pci 16384 0
libata 245760 2 ata_piix,ata_generic
xhci_hcd 188416 1 xhci_pci
ehci_hcd 90112 1 ehci_pci
firewire_ohci 45056 0
crc32c_intel 24576 2
psmouse 167936 0
scsi_mod 212992 6 sd_mod,usb_storage,libata,uas,sr_mod,sg
i2c_i801 28672 0
firewire_core 77824 1 firewire_ohci
r8169 90112 0
crc_itu_t 16384 1 firewire_core
mii 16384 1 r8169
usbcore 282624 8 ath9k_htc,usbhid,usb_storage,ehci_hcd,xhci_pci,uas,xhci_hcd,ehci_pci
fan 16384 0
thermal 20480 0
When I checked the 'setup' for QjackCtl, it still only gives me those two generic options that don't work.
How do I get it to see this card in QjackCtl, even with all the right firmware installed? Are we at the end of the road here?
- Linuxmusician01
- Established Member
- Posts: 1542
- Joined: Mon Feb 23, 2015 2:38 pm
- Location: Holland
- Has thanked: 772 times
- Been thanked: 142 times
Re: E-mu 0404 and getting nowhere...
Could you post (yes, yet another time, sorry) the output of:Red Leader wrote: How do I get it to see this card in QjackCtl, even with all the right firmware installed? Are we at the end of the road here?
Code: Select all
cat /proc/asound/cards
-
- Established Member
- Posts: 38
- Joined: Wed Jan 15, 2014 8:20 pm
Re: E-mu 0404 and getting nowhere...
You of all people should not apologize! No worries, I will check it out today and post up code!Linuxmusician01 wrote:Could you post (yes, yet another time, sorry) the output of:Red Leader wrote: How do I get it to see this card in QjackCtl, even with all the right firmware installed? Are we at the end of the road here?If your Emu card is not in there then it is not (yet) recognized.Code: Select all
cat /proc/asound/cards