Audio Card in Linux

Jump to Latest
K

kraka

Member
Joined 2024
#1
Hello.
I register here, because i have a problem with an Audio Card.

Is there a Linux distro in which the APS (Audio Production Studio audio card, by EMU) is working "out of the box" ?
I have test it in AVLinux MX 19.4 (for 32 bit) and it is not working.
Or if there is not, then does somebody know a patch or a setting or something.., that will make it give sound ?
I have tested, in the same distro, two other cards with the same processor (EMU10K1) and they work "out of the box".
Thanks
 
#3
Thanks for reply !
I am not, right now, in the machine "in question", but i can reproduce the results. When "SBLive1024" or "Audigy4" (these are the two cards that have exactly the same processor with the card "APS" [which is not worked], are attached in the main-board (in a PCI slot), then lsmode list all the appropriate modules ie : "snd-emu10k1.ko" , "snd-emu10k1x.ko" , "snd-emu10k1-synth.ko". Then the cards work fine. But when the "APS" card is attached, then the
lsmod do not give the above three modules. I have not run lspci
Something else that may help is this : In the distro i used (AVLinux MX 19.4 for 32bit) there is an application that control Audio processes called "Jack". Inside this app, i can choose ALSA. If the attached card is a working one, then it is shown in a window and can choose it. Once, i did some settings-modifications in the modules (snd-emu10k1.ko" , "snd-emu10k1x.ko" , "snd-emu10k1-synth.ko"), i cannot remember what exactly because i was on it for days and maybe i did it by chance, and i "trick" system so the problematic card EMU, have shown in the "Jack's" window i mentioned above. Then i open a drum machine app, write some lines, playback, and showing all sound fenders moving up down, but not sound. (i previously had turned up all volumes controls).
 
#4
I am in the problematic machine. Here are outputs from lspci and lsmod :

$ lspci
00:00.0 Host bridge: Intel Corporation 82865G/PE/P DRAM Controller/Host-Hub Interface (rev 02)
00:01.0 PCI bridge: Intel Corporation 82865G/PE/P AGP Bridge (rev 02)
00:06.0 System peripheral: Intel Corporation 82865G/PE/P Processor to I/O Memory Interface (rev 02)
00:1d.0 USB controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #1 (rev 02)
00:1d.1 USB controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #2 (rev 02)
00:1d.2 USB controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #3 (rev 02)
00:1d.3 USB controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #4 (rev 02)
00:1d.7 USB controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev c2)
00:1f.0 ISA bridge: Intel Corporation 82801EB/ER (ICH5/ICH5R) LPC Interface Bridge (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801EB/ER (ICH5/ICH5R) IDE Controller (rev 02)
00:1f.3 SMBus: Intel Corporation 82801EB/ER (ICH5/ICH5R) SMBus Controller (rev 02)
01:00.0 VGA compatible controller: NVIDIA Corporation NV34 [GeForce FX 5200] (rev a1)
02:05.0 Multimedia audio controller: Creative Labs EMU10k1 [Sound Blaster Live! Series] (rev 04)
02:05.1 Input device controller: Creative Labs SB Live! Game Port (rev 01)
02:06.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8169 PCI Gigabit Ethernet Controller (rev 10)

$ lsmod
Module Size Used by
cpufreq_powersave 16384 0
cpufreq_conservative 16384 0
cpufreq_userspace 16384 0
bnep 20480 2
bluetooth 516096 7 bnep
jitterentropy_rng 16384 1
drbg 28672 1
ansi_cprng 16384 0
ecdh_generic 16384 1 bluetooth
ecc 40960 1 ecdh_generic
rfkill 24576 2 bluetooth
uinput 20480 1
nfsd 331776 2
auth_rpcgss 53248 1 nfsd
nfs_acl 16384 1 nfsd
nfs 184320 0
lockd 81920 2 nfsd,nfs
grace 16384 2 nfsd,lockd
fscache 192512 1 nfs
sunrpc 262144 6 auth_rpcgss,nfsd,nfs_acl,lockd,nfs
vmwgfx 258048 0
fuse 102400 2
loop 28672 0
lp 20480 0
nouveau 1712128 4
snd_emu10k1 139264 2
mxm_wmi 16384 1 nouveau
wmi 24576 2 mxm_wmi,nouveau
video 45056 1 nouveau
ttm 86016 2 nouveau,vmwgfx
snd_util_mem 16384 1 snd_emu10k1
snd_ac97_codec 110592 1 snd_emu10k1
pktcdvd 28672 1
drm_kms_helper 192512 2 nouveau,vmwgfx
ac97_bus 16384 1 snd_ac97_codec
drm 446464 8 nouveau,vmwgfx,ttm,drm_kms_helper
snd_hwdep 16384 1 snd_emu10k1
snd_rawmidi 28672 1 snd_emu10k1
i2c_algo_bit 16384 1 nouveau
snd_seq_device 16384 2 snd_emu10k1,snd_rawmidi
fb_sys_fops 16384 1 drm_kms_helper
syscopyarea 16384 1 drm_kms_helper
sysfillrect 16384 1 drm_kms_helper
snd_pcm 98304 2 snd_emu10k1,snd_ac97_codec
sysimgblt 16384 1 drm_kms_helper
snd_timer 32768 2 snd_emu10k1,snd_pcm
iTCO_wdt 16384 0
iTCO_vendor_support 16384 1 iTCO_wdt
snd 69632 11 snd_emu10k1,snd_hwdep,snd_ac97_codec,snd_timer,snd_rawmidi,snd_seq_device,snd_pcm
soundcore 16384 1 snd
ppdev 20480 0
rng_core 16384 0
evdev 20480 13
emu10k1_gp 16384 0
intel_powerclamp 16384 0
sg 28672 0
serio_raw 16384 0
gameport 16384 2 emu10k1_gp
parport_pc 28672 1
parport 53248 3 lp,parport_pc,ppdev
button 16384 1 nouveau
ext4 417792 2
crc16 16384 2 bluetooth,ext4
mbcache 16384 1 ext4
jbd2 73728 1 ext4
btrfs 1040384 0
blake2b_generic 40960 0
zstd_compress 151552 1 btrfs
raid10 53248 0
raid456 143360 0
async_raid6_recov 16384 1 raid456
async_memcpy 16384 2 raid456,async_raid6_recov
async_pq 16384 2 raid456,async_raid6_recov
async_xor 16384 3 async_pq,raid456,async_raid6_recov
async_tx 16384 5 async_xor,async_pq,raid456,async_memcpy,async_raid6_recov
xor 28672 2 async_xor,btrfs
raid6_pq 110592 4 async_pq,btrfs,raid456,async_raid6_recov
libcrc32c 16384 2 btrfs,raid456
crc32c_generic 16384 5
raid1 40960 0
raid0 20480 0
multipath 16384 0
linear 16384 0
md_mod 147456 6 raid1,raid10,multipath,linear,raid0,raid456
uas 20480 0
usb_storage 57344 1 uas
sr_mod 24576 1
sd_mod 40960 4
cdrom 57344 2 pktcdvd,sr_mod
t10_pi 16384 1 sd_mod
ata_generic 16384 0
ata_piix 32768 4
r8169 69632 0
ehci_pci 16384 0
uhci_hcd 40960 0
libata 196608 2 ata_piix,ata_generic
lpc_ich 24576 0
realtek 16384 1
mdio_devres 16384 1 r8169
psmouse 139264 0
i2c_i801 24576 0
i2c_smbus 16384 1 i2c_i801
libphy 110592 3 r8169,realtek,mdio_devres
scsi_mod 167936 6 sd_mod,usb_storage,libata,uas,sr_mod,sg
ehci_hcd 69632 1 ehci_pci
usbcore 233472 5 usb_storage,ehci_hcd,uhci_hcd,uas,ehci_pci
floppy 65536 0
 
#6
Thanks for posting lspci & lsmod. It is not always easy (or even possible to run newer software on older hardware). I do not have this card and have not run that distro so am speaking blindly. These kinds of things can be a lot of work/reading so be patient unless you find someone attempting the same exact thing. Your two other 10k1 cards may/not have the same revs of the same chipset--the specifics really matter.

My knee-jerk thought from your post is that you have firmware for the ones that work but not complete/missing firmware for the one you are trying. There seems (?) to be enough to identify it as a 10k1 device and load the modules, but not enough to work. If it's identified correctly (Blaster live etc), you might need a deeper dive into Alsa firmware to custom-build what's not included. (Inherent in that is the question of if it has ID'd correctly as whatever chipset that Blaster live family uses). I might also be 100% wrong, but that was my first reaction/thought.

Question zero is if the hardware works at all -- has it worked on (old) Windows recently or even on the same mainboard w/ Windows? If you know it works somewhere (other mainboard/other OS, etc, that's great but don't ask me how I know to check this).

First, suggest to ask the people that spun that respin:
https://forum.mxlinux.org/viewforum.php?f=127

Seeing MX 19.4 lists Debian 4.19 kernel (?) & "The AHS (Advanced Hardware Support) ISO features a Debian 5.10.24 kernel".
Code: 
uname -r
to look at yours--if it has dashes and some subversion other than just a number, it's not a vanilla kernel.org kernel (then do
Code: 
uname -a

Tell them what Exactly you mean by "doesn't work"--what exactly did you try and what exactly was the result, etc. In the end, it's Debian under all the layers, so if it works on some Debian release that yours is based-on, you'll have a great chance of success. That's the other shortest-path solution--get it going on that base release of Debian first.

For now, just some more loose ideas, FWIW, in case they provoke something. Please don't take offense, but have you checked the volume mixer to make sure it's not muted? (If it's Alsa with a lot of channels, you have to keep going to the right/off-screen to scroll it to get to all the entries). Is your user name in the audio group? Is there an onboard audio device that either needs to be blacklisted or perhaps disabled in the BIOS (not seeing any in the lspci but...)?

Your modules are loaded so the firmware knows what it is (is it right--does that chipset need the 10k1?) and there are drivers for it...or seems to. Might as well double-check that with

Code: 
aplay -l

Does that list any onboard device or the one you want or something else? That should give just playback devices (the big list you get with cap L: aplay -L)

Again, could still be missing firmware. Ask at the main distro forum where to find a list of their firmware if you can't find it on your machine or search it up in MX docs/sites somewhere. (Yes, a user shouldn't have to do any of this but it's been life in linux since ALSA bumped OSS and started all this "progress" and fixes for it like jackd and so on).

You've got soundcore
soundcore 16384 1 snd
so that's one showstopper down.

Next, it's been ID'd as a 10k1 device (of the 3 types--I'm still reading):

snd_emu10k1 139264 2
...
emu10k1_gp 16384 0 ( this is for game port is that midi ? )

If it's not using 10k1x, it doesn't think you need it, ditto the synth module. But, for kicks:
Code: 
sudo modprobe snd-emu10k1x
sudo modprobe snd-emu10k1-synth

if it tells you module <blah> not found in /lib/modules/<kernel version> you will have a different breadcrumb trail to follow.

Perhaps also (sanity check) look in the kernel config to see what options are listed for that manufacturer in whatever version of kernel you are running.

Code: 
cd /boot
grep SND_EMU10K /boot/config<-tab to auto-complete kernel version filename

Look at the dmesg and grep for every possible line that has udio or ound in it -- best to read it line by line to be sure.

If desperate and time-crunched & if it will stay off of the networks, you might end-up using an older linux audio distro for "just works" or loading older Win 32-bit.

Don't give up right away, though--custom low-latency kernels are built by somebody -- and bumps happen in 25 year old kernel drivers. If you're okay building kernels, you can use a frugal install of Antix or DSL or something to just have the 32-bit toolchain isolated on your faster machine so you don't have to worry about the 32-bit libs and so on.

It might be simple--again I don't have either piece of this stuff--just some ideas. Stay high level at first to be the most-efficient and not spin your wheels--does the card work at all in other distros or on an old windows box? Can a window (say XP) install disc detect it (see archive.org if you need to) right? Does an old Debian release work right, etc. Keep us posted if you feel like it.
 
Last edited:
  • Thank You
Reactions: kraka
#8
grindstone said:
Keep us posted if you feel like it.
Click to expand...

First of all, after your reply, i feel that somebody care for my problem. This is very important. I have very bad experience from people in other fora where they do not really care to help but, to show off their knowledge, and if they do not have this knowledge, they just attacking you.
Thank you for this.
Now for the real problem, it is much work for me, after you suggestions. I will try to follow.
This card is not the first but the second. (two exactly the same). First card worked without a problem in WinXP machine with this motherboard (the one on which i am trying now, to install the card in question). It worked with modified drivers, because its native OS was Win95 or Win98. Anyway it was working OK until one day stopped have sound. I tried every OS i had : Win95,98 with the native drivers, Vista,Me,2000 with modified drivers and many times XP. I am talking about complete install and reinstall of all these OS's i mentioned before. It took me weeks or months. Card was detected but no sound. Then i was thinking that maybe it was a hardware problem and after i ask help of professional technicians and they refused, i replaced, by my self, about 15-20 components on the board. I am not a professional and i have not the right equipment to check a card (to see if i indeed fixed a component), so i bought a "new" one. I tried again installed it, with Windows with not succeed. Card was detected but no sound. Then somebody told me to try Linux. I had little experience with Linux from the past (Umbudu or Lumbudu, Kali and maybe some other distros) so now i am trying with AV MX 19.4.
Lately i am thinking if it is a problem related to the Box of my machine. I mean the metal tower. I remember that before the initial problem occurred, i had install in my machine (it is a PC) a PSU that it proved to be problematic. Then i changed it with a good one. I am thinking if there is a short circuit problem in my tower that prevent the card for giving sound (playback ie to output sound from its jacks). I do not know... And i do not know how to check. Maybe if i will found another tower to check it. Anyway, as for your suggestions :
It will be very helpful if you explain to me what exactly is the difference between "modules" and "firmware". Are not the same ? If i will understand this i will start to searching with a different "base".

Now i will try to input your suggested commands and post the output.


$ uname -r
5.9.1-rt19avl1

$ uname -a
Linux mx 5.9.1-rt19avl1 #1 SMP PREEMPT_RT Fri Oct 30 16:03:33 EDT 2020 i686 GNU/Linux

Volume Feders have checked many times, they are all up. On Board audio card (AC97) has disabled on the BIOS.
About my user name in the audio group, i do not know where to check this. You mean in the alsamixer properties ?


$ aplay -l
** List of PLAYBACK Hardware Devices **
card 0: APS [E-mu APS [PC545]], device 0: emu10k1 [ADC Capture/Standard PCM Playback]
Subdevices: 31/32
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
Subdevice #4: subdevice #4
Subdevice #5: subdevice #5
Subdevice #6: subdevice #6
Subdevice #7: subdevice #7
Subdevice #8: subdevice #8
Subdevice #9: subdevice #9
Subdevice #10: subdevice #10
Subdevice #11: subdevice #11
Subdevice #12: subdevice #12
Subdevice #13: subdevice #13
Subdevice #14: subdevice #14
Subdevice #15: subdevice #15
Subdevice #16: subdevice #16
Subdevice #17: subdevice #17
Subdevice #18: subdevice #18
Subdevice #19: subdevice #19
Subdevice #20: subdevice #20
Subdevice #21: subdevice #21
Subdevice #22: subdevice #22
Subdevice #23: subdevice #23
Subdevice #24: subdevice #24
Subdevice #25: subdevice #25
Subdevice #26: subdevice #26
Subdevice #27: subdevice #27
Subdevice #28: subdevice #28
Subdevice #29: subdevice #29
Subdevice #30: subdevice #30
Subdevice #31: subdevice #31
card 0: APS [E-mu APS [PC545]], device 2: emu10k1 efx [Multichannel Capture/PT Playback]
Subdevices: 8/8
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
Subdevice #4: subdevice #4
Subdevice #5: subdevice #5
Subdevice #6: subdevice #6
Subdevice #7: subdevice #7
card 0: APS [E-mu APS [PC545]], device 3: emu10k1 [Multichannel Playback]
Subdevices: 1/1
Subdevice #0: subdevice #0

Again, could still be missing firmware. Ask at the main distro forum where to find a list of their firmware if you can't find it on your machine or search it up in MX docs/sites somewhere. (Yes, a user shouldn't have to do any of this but it's been life in linux since ALSA bumped OSS and started all this "progress" and fixes for it like jackd and so on)
Click to expand...

As i told before, i do not know what is "firmware", so i can not search for it in my OS, or ask somebody else if it have it. I only know about "modules" and that the modules that required for the Audio Cards with the EMU10K1 processor are "snd-emu10k1.ko" , "snd-emu10k1-synth.ko" , snd-emu10k1x.ko" and they are all exists in folder : /lib/modules/5.9.1-rt19avl1/kernel/sound/pci/emu10k1/
But, please wait a moment. As i was searching in the above address, somewhere i saw a folder named "firmware". Wait for me to see what is inside there....

I found a folder named "firmware" in address : /lib/firmware/emu/ and inside the "firmware" folder there is a folder named "EMU" and inside the "EMU" folder there are six files with extension .fw. These are : 1)audio_dock 2)emu0404 3)emu1010b 4)emu1010_notebook 5)hana 6)micro_dock

Something tell me that these files are specific for specific cards, and even if a card may have the same processor with an other, if its .fw file is not listed here, then may not be able to give sound. Am i correct ?

Wait for me to see in the file you have attached....

I do not understand many things. I can see my card with these numbers next to it :

"1102 4001 E-mu APS" . This "4001" is also next to this line i read somewhere down the list : "1102 4001 E-MU 1010 [MAEM8810]" Here i can see the 1010 which is the same with the 3)emu1010b and 4)emu1010_notebook

I am confused. What file i must look for ? The "1102 4001 E-MU 1010 [MAEM8810]" ?


Next commands :
$ grep SND_EMU10K /boot/config-5.9.1-rt19avl1
CONFIG_SND_EMU10K1=m
CONFIG_SND_EMU10K1_SEQ=m
CONFIG_SND_EMU10K1X=m

Output from dmsg refered to "audio" "sound" or "EMU" ARE ONLY THESE TWO :
[ 2.836353] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
[ 40.104954] gameport gameport0: EMU10K1 is pci0000:02:05.1/gameport0, io 0xcc00, speed 1037kHz

I did not understand your penultimate paragraph. Antix and DSL, are Linux distributions? I have no problem installing any distrοs on which, my card would work. But it is impossible, to try all distροs. There are too many.

Again, THANKS and, any help is valuable.
 
  • Like
Reactions: grindstone
#10
Seems that my theory was wrong--you have all the E-mu firmware that you should have--you don't need to look for any more (I looked in the source code last night). If you care to note the details,

Code: 
dmesg | grep emu10k1

should show the firmware being loaded at boot. (Oh--and generally, firmware operates at a lower level (closer to hardware control) than modules, but is sometimes distributed (packaged) separately in linux distributions for space-saving reasons.)

In short, my sense is that it is the same as with Windows--detection but not operation. Sad to report, but I think hardware problem, too--unless you can prove it runs on Something. Surely a great card worth some effort to use, but...much grief already.

I have not installed (3.6G) AVL because I have a data limit and now is not a good time. I do, however, know a bit about the MX/AntiX family AVL is built-upon.

Too many things don't make sense.
1) Unknown yet is why the card that worked (first card) stopped working. If the hardware works, all I can think of is that something else was added/configured that made an IRQ conflict (???) Can you figure out how to add a boot parameter to the grub line that boots your system? It's either hitting "e" to edit or hit escape right when the boot menu is displayed (then you get the option to hit "e" to edit). Arrow-down until you find a line that has something like /boot/vmlinuz... in it--it might be a long (wrap-around) line but go to the end of that line, add one space, and then add the word "irqpoll" (without the quotes) as the last item. Hit Ctl-x or F10 to boot that. If you made an editing mistake, just hit ESC and back out and you can try again. Alternatively, maybe you could just manually reassing things in CMOS setup, etc. as blind shots.
2) If it (APS) ever worked right in linux, it should "just work" since the early 2000's in linux (10K1). Long shot but it's another test (like all the Windows revs you tried)--you could try old/smaller 32-bit distros from those times that still run as live CD's--something simply as a test like (2006):
https://old-releases.ubuntu.com/releases/dapper/ubuntu-6.06.1-desktop-i386.iso (~698MB) Maybe better yet (because it has a low-latency kernel and jackd), an old (2008) rev of Ubuntu studio: https://download.linuxaudio.org/ubuntustudio/8.04.1/release/ubuntustudio-8.04.1-alternate-i386.iso (1.1GB). If your machine will boot from usb, you could use a thumb drive and Ventoy so you don't have to wipe the AVL w/o seeing if it works differently. If you want 64-bit, the same directory contains an amd64 image. If you can't boot from usb, there is always the PloP which you can put on other media that you can boot from so that the USB drive may become bootable. Note that those old distros are sort of like running W9X in 2024--you don't want them front-facing on any network and the repositories/updates are no longer available, but if it makes sense to you, they might aid diagnosing things.

In the absence of any help from those, I'm out of ideas. Conclusion here is that it must be shown to work on other hardware before it can be trusted to be operational; my sense is the card doesn't work (but I know you are too far in to hear that). If you go to the Alsa project Creative (E-mu) page itself, the APS isn't in the list. https://www.alsa-project.org/wiki/Matrix:Vendor-Creative_Labs That is literally the place to go to answer the question of "is my soundcard supported?". Now, in other places (https://alsa.opensrc.org/Emu10k1#Options_of_the_kernel_module), one can see "partially supported". The only specific answers would require diving into old Alsa mailing lists and searching or reading code (and old code).

The 10k1x hardware is different than yours so you don't need that module, IMO. https://alsa.opensrc.org/Emu10k1x

I do not know what you have tried to test / configure alsamixer. It may be worthwhile to read mixer comments under 10k1 module options Probably should've asked for this first, but an easy way to look at to see the levels is to just type
Code: 
alsa-info
and save that to a file so you can inspect each playback element that shows a % symbol to see the level settings--as well as to know what you really have for the alsa configuration. It may be that it's actually working but certain levels remain at 0%. If you feel like attaching the output file to a post, perhaps others can review it as well.

To change the levels, of course you enter
Code: 
alsamixer
and then arrow through everything and use the F-keys, etc. (ESC to get exit).

Alternatively, you could just see what it does on one channel if you type
Code: 
alsabat

Maybe better yet, just skim this page and see if anything looks inviting:
https://www.alsa-project.org/wiki/SoundcardTesting

In linux distros, groups are a way to make system administration of access to hardware more convenient--so there is (or used to be), for example, "audio" for the soundcard access, etc. My comments about being a member of the audio group reflect old thinking--at least in Debian-based things. I'd leave that alone--AVL surely knows what they need to use a soundcard.

As a point of information, I'm sure there is some pretty GUI application in AVL for this but I don't know it so you can do this to see which groups you are already in:
Code: 
grep <your_username> /etc/group

My sense is that it all has to do with jackd and real-time privileges so that a anyone with audio access can't lock-up a machine but perhaps that's off, too. At any rate, I'd leave that alone.

Sooooo, no help, but maybe you can learn more from some of this all.

( Aside/academic APS detail perhaps for others searching:
While a 10K1 device, APS has A-D Crystal CS5335 20‑bit and D‑A Crystal CS4329 -- is NOT same as Blaster Live. Records at different speed than it plays back. Runs 48kHz all the time (so must work at 48kHz recording & downsample after all work to get to 44k and not have sync prob). )
 
#11
I'm not currently on my PC, but I'm just log in to say hello. I liked very much your approach to (my) problem. You pay attention to details and that's pretty good (and not something many can do). I'm happy because after your new post i have a lot of work to do and a lot of new things to learn (I love learning and working on a solution).

Until I get to my PC, I would like to say a few things: Thanks for explaining (in simple and understandable words) the difference between "module" and "firmware". That was very important to me. I will give the command

dmesg | grep emu10k

and maybe i will upload the results here.

I had exactly the same feeling as you about IRQ. Even though I didn't know what that was, I read and learned. While I was in Windows I tried to make as many settings as I could. The card had a preference to IRQ 17. IRQ 17 was shared with another device (USB) which I uninstalled, but the problem was not solved.
Then I tried at the CMOS level settings, changing the IRQs that each PCI-slot (my motherboard has 5 slots) prefers. And some other settings that I don't remember now. I had no success. However, the last attempts I made when I was on Windows, if I remember correctly, were IRQ-related.

I can't boot from USB, but I can from CD. I have a few CDs with linux diagnostics that have a "window" interface and I will try with them. I will also try distros you suggested. I'm very curious to see if it works on any of them.

I've also noticed "partial support", but what, exactly, does that mean ?

I will also try all the ones you suggested for alsa mixers. Sometimes, the solution is where you least expect.

Until I will have access to my computer and try all of the above, I would like to raise something for reflection. Is there a possibility that there is a problem with the power wiring? I had heard of some problems known as "loops" or something.
The path followed by the current is as follows: I use two sockets (built into the wall). First socket is directly connected to a voltage stabilization device. A UPS is connected to the stabilizer. A power strip is connected to the UPS, to which the computer and all peripherals, including one of the two speakers, are connected. The second speaker is connected directly to another separate socket (the second socket) built into the wall. I understand that if there was a problem, no other card would work, but I mention it simply because no one ever knows...
 
  • Like
Reactions: grindstone
#12
There are plenty of people on this forum capable to answer your power questions, but unfortunately I am not one of them 🙂 In fact, I have no business even attempting to help here but empathize because I can recall working like an animal for days/weeks in early years to measure signal on serial pins for dial and button boxes, etc. Major subsystems in linux change a lot over time. This is how it is with old hardware (and it's going the wrong direction and accelerating).
 
#13
Hello...again

I have tried Ubuntu 6.06.1 and Ubuntu-studio 8.04.1.

6.06 detected the audio card but no sound.
Studio 8 could not been tested from a live DVD, because the ISO file had not an option for this. Instead, it had an option for installation. So i installed it in a new partition i have made, but after installation there was not a "window" interface. Only a command prompt style environment.
I tried to install it 2 times. Also i tried Ubuntu-studio 7, with the exact results.

I have also noticed the "partially supported". But what exactly this means ? Certainly does not mean that works on Sunday, Monday, Tuesday, stop working on Wednesday, Friday, Saturday and in Sunday it depends on the Weather 🙂 . If this is related to a specific software or hardware, i must find what they are.
 
  • Like
Reactions: grindstone
#14
We still don't know if the hardware works at all in that same tower, right? In addition to previously-mentioned ideas, maybe try gathering more detailed info on some distro which correctly detects it. Work the list. Once you have solid details, you can inquire with the developers on a mailing list and get better help.

Edit: This is older than the 6.06.1 you tried, but may be informational
This thread--look at the "amixer contents" and discussion--should very much help detailing what works/does not.
 
Last edited:
#15
Hello. This Thread is mine.
Just kidding....😉
My friend, you impressed me! Where did you find this Post? It's like I've written it, because it describes exactly my problem. I have already read it 1-2 months ago (I don't remember exactly), but in order to find it I searched many, many hours maybe days. I'm surprised that you found it in your attempt to help someone else (me). I'm not currently on my PC. When I go there I will re-read this post in detail and pay more attention to it because there is also the following case: In my effort to solve my problem, I have read over a hundred posts or articles and maybe some of them I just took a look at, without delving into them. Once again: Thank you.
 
  • Like
Reactions: grindstone
You must log in or register to reply here.
Top Bottom