Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No sound - Creative Labs Sound Blaster Recon 3D / Z (ca0132) #221

Closed
ThEMarD opened this issue Aug 17, 2014 · 146 comments

Comments

Projects
None yet
@ThEMarD
Copy link

commented Aug 17, 2014

Heyyo,

My Creative Labs Sound Blaster Recon 3D (ca0132, same DSP as the Sound Blaster Z) can't output sound or record from my microphone.

I'm running SteamOS with Alchemist_beta fully updated.

I tried the fixes that worked when using Arch Linux or Ubuntu of editing the /etc/rc.local and adding in...

rmmod snd_hda_intel
modprobe snd_hda_intel position_fix=1

or...

sudo kill ps uax |grep pulseaudio | grep -v grep | awk '{print $2}' ; sudo rmmod snd-hda-intel; sleep 3; sudo modprobe snd-hda-intel

and neither worked... all I get is static. I'm unsure if this is kernel related (since ca0132 workaround has worked in kernel 3.10+ when I've tested it) or something that SteamOS changes compared to other Linux distros.

Currently, Creative Labs have not put out a proper Linux driver for any ca0132... the current support for ca0132 sound cards comes from porting their official Google Chromebook Pixle drivers to ALSA & the Linux Kernel.

here's my alsa-info:
http://www.alsa-project.org/db/?f=8aefb0663de38f0e3e2f1df4facd257aaebbb3bc

I hope this helps. Please let me know if there's anything further I can try to help resolve this issue and hopefully get SteamOS working with the ca0132 based sound cards for all users. :)

@paulonarciso

This comment has been minimized.

Copy link

commented Sep 20, 2014

SteamOS lacks the proper firmware files for ca0132. But even if those files were present it will not matter.

Soundblaster Z doesn't work on linux no matter what.

Valve could try talking with Creative. If there's a driver for Google Chromebook they could do a driver to support SteamOS.

@ThEMarD

This comment has been minimized.

Copy link
Author

commented Sep 20, 2014

Heyyo,

Err... it works perfectly in 32bit dude... just currently the firmware loader is broken in 64bit.. plus look at the commands I said above that work fine in debian but doesn't work in SteamOS....

I'd just be nice if SteamOS had the fixes built in when it detects a ca0132 sound card or maybe checked into how to fix the firwmare loader in 64bit SteamOS.

Speaking of 32bit... how come SteamOS isn't offered in 32bit?

@PyGuy95

This comment has been minimized.

Copy link

commented Nov 10, 2014

Yes, I have this card and I'd love to see it get supported under SteamOS. It's currently the only thing that's broken on my end

@jadbox

This comment has been minimized.

Copy link

commented Feb 2, 2015

Same here, I really wish I had my SBZ working under SteamOS...

@martinmolin

This comment has been minimized.

Copy link

commented Mar 5, 2015

ZxR here, also broken in 64bit Linux (ca0132).. currently the only thing stopping me from dropping Windows. I haven't seen any positive response from Creative themselves when "regular" people pokes them for Linux drivers but I'd guess if they see that it's worth implementing it, they'll do it.. So lets hope SteamOS is a success, even more so than what it already is.

@r1sim

This comment has been minimized.

Copy link

commented Mar 22, 2015

I have the same problem. This is the only reason I use windows.

@MaxKotlan

This comment has been minimized.

Copy link

commented Apr 2, 2015

Yep. Same Problem. This is a real bottleneck for me....

@Tele42

This comment has been minimized.

Copy link

commented Oct 6, 2015

Creative have expressed their stance by their actions, once upon a time they supported linux, but have not in many years. Get this sound card working on linux in general, and it will trickle down to SteamOS.

@mdeguzis

This comment has been minimized.

Copy link
Collaborator

commented Oct 6, 2015

Is there source code released for the Chrombook variant of this firmware? Is it x86 or ARM? Can the module be rebuild under a test chroot or test machine? If I had the hardware, I'd be more interested in trying to help out. What steps do you use to make this work in Debian 7/8? Is there any particular reason you are running Alchemist over Brewmaster? You will have much newer packages, and systemd if you upgrade. It is worth updating if you are adamant about getting this working.

@ThEMarD

This comment has been minimized.

Copy link
Author

commented Oct 6, 2015

Heyyo, @ProfessorKaos64 , I don't think Brewmaster was out in Aug 17, 2014 when I made this topic. I can try installing it sure, but the latest 64bit kernel v4.2.0 has been giving me the same grief as whatever 64bit kernel v3.x that alchemist_beta used. Tested with Linux Mint, Manjaro and Ubuntu Mate.

The issue seems to be the 64bit kernel firmware loader or the firmware files themselves aren't 64bit compatible... ctefx.bin ctspeq.bin. It's included in many Linux distributions and can even be found I think with a quick Google search but no matter where I put the files they never load in 64bit and require that rmmod and modprobe terminal command to try and get working. I'm not sure how that circumvents the 64bit kernel firmware loading issue but it does... I kinda wish I picked up coding but I never found the time I guess... if you think you can do something with the ctefx.bin and ctspeq.bin files to make them load under a 64bit kernel that would be GREATLY appreciated.

I made this comment thread to hopefully get Valve to tell Creative to do something about their lack of Linux/SteamOS support and hopefully fix it but haven't had much luck yet sadly.

You can see the original Linux kernel bug report here from over two years ago:
https://bugzilla.kernel.org/show_bug.cgi?id=55541

@jadbox

This comment has been minimized.

Copy link

commented Oct 8, 2015

Sound Blaster Z support is one of my last remaining wishes for Debian/Linux. Anyone want to start a bug bounty pool on this?

@ThEMarD

This comment has been minimized.

Copy link
Author

commented Nov 2, 2015

Heyyo, someone's been working on it! Takashi Iwai!!! There is hope! https://bugzilla.kernel.org/show_bug.cgi?id=55541

@jadbox

This comment has been minimized.

Copy link

commented Nov 3, 2015

Sweet mother of God... I nearly gave up watching this issue. As a linux gamer, my excitement is unbounded!

@ThEMarD

This comment has been minimized.

Copy link
Author

commented Nov 18, 2015

Heyyo, The fix is now part of Kernel 4.4-RC1 for testing! Hopefully it gets approved and passed down to a stable kernel. Takashi Iwai is a very big hearted and humble gentlemen. He declined my PayPal donation too saying he's just happy to help so be sure to test out that kernel and report back to that bugzilla link in my previous post if it doesn't work for you.

@voron00

This comment has been minimized.

Copy link

commented Dec 19, 2015

Yeah the DSP load were fixed but that changed nothing for SB Z-Series.
But we are trying to get it fixed. See here https://bugzilla.kernel.org/show_bug.cgi?id=109191
Basically, the DSP firmware is incomptabile with SB Z-Series. Jaroslav Kysela is still trying to do something with it but i feel somewhat sceptic about that. Anyway, there is a way to make it work thanks to Takashi Iwai and his patch to use generic hda driver for SBZ. I've updated this patch to use proper pins for SBZ (still needs testing on Zx | ZxR) for Line in (rear mic) and Line out (3rd jack) (Yeah, only line out is working at the moment and mic). I've commited it for now: https://github.com/voron00/linux/commit/fcbf5ba088c9bc8104f32738e356600ecfb85689
You may try it yourself, just compile the kernel from my repo or cherrypick the patch and compile with your own kernel. I would really like to know if it actually works on Zx and ZxR since i only got the Z board.

@Millnert

This comment has been minimized.

Copy link

commented Jun 21, 2016

I had sound for a while but since debian 4.6.1 on debian stretch and recent package upgrade (2016-06-20) , it stopped working again. Now trying the patch at https://bugzilla.kernel.org/show_bug.cgi?id=109191#c14 , which applied cleanly to debian 4.6.1 source. I had one change in my PCI ID which is 1102:0011 rather than the 1102:0010 the patch was written for first. The motherboard is a Gigabyte Z170X-Gaming 7.

@NukeMania

This comment has been minimized.

Copy link

commented Jul 2, 2016

@sweca

This comment has been minimized.

Copy link

commented Jan 1, 2018

2018 and still not working. Creative don't care.

@Conmanx360

This comment has been minimized.

Copy link

commented May 3, 2018

Hi!
I've been working on my own patch, and am currently in the process of submitting it to the Linux Kernel. In the meantime, if anyone wants to compile their own kernel and test the early version, you're welcome to.
Here's the thread I posted on the Creative forums:
http://forums.creative.com/showthread.php?t=742256

If you don't want to read that stuff, you can just download it straight from my Google drive:
https://drive.google.com/drive/folders/1r-X8g6It5AO7SwgJc1JQfJ8KCOyqrr_d

Put the patch_ca0132.c in your kernel source's sound/pci/hda folder, and put the firmware ctefx-sbz.bin in your /lib/firmware folder. Let me know if it works for you. I'm still trying to find people with the variants of 0x0024 and 0x0025 to test it.

Thanks.

@medzernik

This comment has been minimized.

Copy link

commented Jun 9, 2018

I've been working on my own patch, and am currently in the process of submitting it to the Linux Kernel.

What does that patch do? Does it enable new features?

@mirh

This comment has been minimized.

Copy link

commented Jun 9, 2018

It enables the card to work properly, so.. yes I guess?

It has been already merged in linux-git (and for who's bound not to be able to compile a kernel itself it'll be official in 4.18)

@medzernik

This comment has been minimized.

Copy link

commented Jun 9, 2018

That is a great thing.

The question is though, can we control the card in any way? I remember that when I booted windows with the Recon3D Fatality card, and then linux it was fine, but if i turned off the PC and the capacitors discharged, the next time I booted Linux first, it all went to hell.

@Conmanx360

This comment has been minimized.

Copy link

commented Jun 9, 2018

Yes, it loads the firmware, so you don't have to boot into Windows first. It also allows you to mess with the effect levels. Here's what the new alsamixer looks like:
https://drive.google.com/drive/folders/1FGaLli4rKrVmBxpx0ulGF3k4ISJ3JCYj

Edit: If you have a recon3D, I haven't tested anything for it, I've only messed with Sound Blaster Z's and Recon3Di, which is an integrated motherboard version. I don't have the data on Recon3D, if someone wanted to get a dump of it though, I'd be willing to see what I could do. Same goes for the ZxR.

@medzernik

This comment has been minimized.

Copy link

commented Jun 9, 2018

That looks phenomenal! Absolutely phenomenal!! so I can finally put my recon3D card back in!!

also one question, will it work with the new Creative Sound BlasterX AE-5? it should have the same chipset but I don't know... I wanted to buy it if it works in Linux

@Conmanx360

This comment has been minimized.

Copy link

commented Jun 9, 2018

I believe I could get it to work on the new AE-5, which has the same Core3D onboard. The only thing is, I need the data, which someone could get by running my program QemuHDADump. It dumps all of the commands from Windows, which is how I've gotten the Sound Blaster Z and Recon3Di to work. So, basically, I'm pretty positive I could get any Core3D based card to work, I just need someone who owns the card to get me the data. That's the only thing keeping me from supporting them.

@medzernik

This comment has been minimized.

Copy link

commented Jun 9, 2018

I will purchase the card and do as you say. Feel free to contact me further here or on my email: medzernik1@gmail.com

@snegrini

This comment has been minimized.

Copy link

commented Jun 12, 2018

This is really great, thank you for your firmware. It works perfectly with my card SB-Z (0x0023 variant), though I have two questions:

  1. After kernel 4.18 installation will still be necessary to put the firmware ctefx-sbz.bin in /lib/firmware folder?
  2. Since Creative shut their forum down, @Conmanx360 could you please repost the topic anywhere else? (maybe here on github, your wiki?).

Thanks.

@Conmanx360

This comment has been minimized.

Copy link

commented Jun 12, 2018

I recently got an email from Creative saying that I had permission to submit the firmware in the same way the Chromebook's current ctefx.bin firmware is included, I haven't gotten around to getting that done, as I suspect it'll require some correspondence with Creative again to iron out the details. I do intend on putting it in a Wiki article, and including a guide on what I need in a dump for people who want support for their cards.

The Wiki part shouldn't take me too long, as I've already written a lot of the stuff previously. The firmware stuff, I have no clue yet. Need to do more research. But, the firmware for the Chromebook works, I just don't know if it makes any changes.

@mirh

This comment has been minimized.

Copy link

commented Jun 12, 2018

Couldn't that be sent to linux-firmware@kernel.org ?

@Conmanx360

This comment has been minimized.

Copy link

commented Jun 12, 2018

It's been awhile, but I recall reading that you need some sort of licensing to be sorted out before sending anything to that address. I almost think Creative would have to send it themselves, I don't work for them and have no involvement with them so I don't believe I could send something under a license on their behalf with just an e-mail as proof they gave me permission.

They're not exactly super responsive, so getting all of this out of them may take some time. Sometimes they just won't respond for weeks. It seems like the best way to get a response is to say bad things about them on Reddit, which happened coincidentally the same day they sent me an email saying I had permission to do it. I used to be able to bug the moderator on their forums to get them to respond, but that is no longer an option.

@Conmanx360

This comment has been minimized.

Copy link

commented Sep 11, 2018

Thank you for the replies. Okay, it's good to hear people are fine with submitting in it's current form, then moving onto the mic and ZxR stuff after that. I don't mind bug reports, and it's good to get them. What kind of got me frantic about the mic stuff was a guy on Reddit who private messaged me about the AE-5 and wasn't too happy when I told him the mic didn't work. This is my first time really programming anything, so I'm still learning how to deal better with feedback, and should probably learn how to not let more negative comments bother me.

I'm kind of scattered all over the place now, from rushing to get sound out of the ZxR and AE-5. Then, the mic detour. So, I guess I should regroup and plan this out. First thing to do is separate the AE-5 stuff into patches. Then, I think I'll take @dsteidley 's suggestion and make a repository of my ca0132 tools, and the documentation on the 8051 that @abridgewater has written along with the stuff I've added. That way, more people can help out with the disassembly if they'd like to. Then, doing ZxR stuff, and after that I guess I will get back into the mic issue. If Creative is willing to help out, it may not end up being necessary to do all the 8051 disassembly stuff, but, it's probably good to get the information we've gathered so far out there even if it isn't needed for anything immediately.

Alrighty, with that out of the way, getting to work on it.

@medzernik

This comment has been minimized.

Copy link

commented Sep 12, 2018

@medzernik - Full audio output support, inconsistent microphone input support. So, in my mind, pretty much fully functional minus the mic.

@AvdWerfhorst - I've kind of gotten side tracked on the whole microphone issue, as I kept getting complaints about it and it was really starting to bother me that I had everything BUT that working. But, I guess I should probably go about doing the driver cleanup, getting it into patches, and then go back to the microphone stuff.

The main thing is, after getting a few complaints about the mic issue, I wasn't sure if people were even happy at all to get sound... The kind of feedback I was getting was "Oh. I have sound output. But my mic doesn't work." So, I got kind of sidetracked trying to fix that in hopes of avoiding those kind of comments in the future, but I guess most people will probably be happy to get sound out of their card at all like I was. I kind of feel bad releasing a set of patches when it doesn't consistently fully work, but I guess if the Sound Blaster Z is already like that, it won't cause any harm.

Hopefully that doesn't come across as whining or anything. I just want to release it and not have to get a ton of emails telling me that it doesn't work. I've thought about maybe setting up some sort of FAQ where I explain common issues and how to fix them, and detail things that are still not working. But, if you guys think it's a good idea to patch it up as is, and then submit the patches and do the microphone stuff later (which, is what I'm leaning towards, because mic stuff is really hard to put a time-table on) then that is what I will do. I think the AE-5 is definitely in a state that it could be submitted with minimal fixes. The ZxR will need some discussion with the alsa mailing list due to the weird nature of how I'm handling it.

Anyways, let me know what you guys think. Like I said, I'm already leaning towards splitting the AE-5 stuff into patches as is, and then there might be some delay between mic/ZxR patches.

The full audio support is phenomenal. The mic not working is something that personally annoys me - but I think that is more because of the nature of soundcards - many people just need all the features of the soundcard, not just partial ones, so that's why everyone is pointing out something.

The fact that the card outputs sound now (and I presume it's configurable) is just amazing. I am so looking forward once the mic works to get a proper EQ/nice sound working in Linux. I am a bit tight on money right now, but when it's all done, expect a donation :D

@Conmanx360

This comment has been minimized.

Copy link

commented Sep 14, 2018

Okay, got today and tomorrow off, gonna try to get some more work done on it. I've been working a little slow due to working quite a bit. I'm off Monday-Thursday next week, so hopefully I get it split into patches by then.

Also, Creative gave me the stuff needed to submit the firmware, so I've got to get that done, too.

@ThomasAH

This comment has been minimized.

Copy link

commented Sep 17, 2018

linux-image-4.18.0-0.bpo.1-amd64 (4.18.6-1~bpo9+1) is now available in Debian stretch-backports, so installing it in stretch became really easy.

Thank you for your work!

@Conmanx360

This comment has been minimized.

Copy link

commented Sep 17, 2018

Okay, about halfway through getting the AE-5 stuff into patches. Hoping to get it done by tonight. If not, it should be done by tomorrow.

This is significantly more code than the Recon3D stuff, so it may require some back and forth. Then, I'll be onto getting the firmware sent off.

Edit: Ah. Just realized I must have forgotten to put in the AE-5 specific microphone stuff. It should still work, but front-mic probably doesn't work as it is now, and I'll add it in with the patches I submit. Also, seems like it might end up being tomorrow when it's finished. I'm pretty bad with time predictions. I'm at the point of adding in output selection stuff, which made me realize I forgot input selection stuff. I'd say I'm 75% done. All that's left is putting in mic stuff, adding the extra controls, and then the exit function. So, three patches.

@Conmanx360

This comment has been minimized.

Copy link

commented Sep 18, 2018

Okay, got the AE-5 patches sent. Now, time to see about the firmware stuff.

I changed the file ctefx-sbz.bin to ctefx-desktop.bin because all the desktop cards seem to use it, so it was no longer Sound Blaster Z specific. So, if you use the patch from the email, be sure to change ctefx-sbz.bin to the new name.

Edit: Actually, since I changed the firmware name, I should probably wait for the patch to be merged before submission. Or, just keep the old name, even if it is inaccurate. I'll wait on Takashi's reply.

@Conmanx360

This comment has been minimized.

Copy link

commented Sep 20, 2018

Okay, looks like the patches were accepted. Now, time to handle the firmware stuff and figure out how to get the ZxR into a cleaner state.

@Conmanx360

This comment has been minimized.

Copy link

commented Sep 24, 2018

Sorry for the lack of updates, been busy over the past few days. Anyways, I've now got the ZxR's digital input working, which is nice. I'm close to having it in a state where I believe it can be submitted to the kernel.

I'm treating the DBPRO daughterboard as basically a separate, generic card that only has digital in/out for now. I will see if I can't get it's line-in working without it being too much of a hassle, it kind of gets confusing when both cards are treated as one in alsa-mixer...

Anyways, like I said, making progress. :)

@dsteidley

This comment has been minimized.

Copy link

commented Sep 26, 2018

@Conmanx360

This comment has been minimized.

Copy link

commented Sep 27, 2018

@dsteidley - No problem. I plan on setting up that repository once I've got all this stuff sorted, although I guess I could set it up earlier, depending on how long this takes.

I've got the analog aux-in on the daughterboard of the ZxR working, so that means all of it's features (Digital In/Out, Aux-in) are working. I'm in the process of splitting it into patches right now, but since I work this weekend, it may not get done until Sunday or Monday. I've also added patches to fix the surround sound with output effects enabled having improper channel mixing.

On a recent bootup with the ZxR, the microphone and the input effects were all working. This leads me to believe that my commands aren't wrong, but the timing is. I may have already mentioned this earlier. Anyways, Once these ZxR patches are submitted, the plan is to add the ability to see the timing information from qemu to QemuHDADump, so that I can see if there are any obvious delays between commands in the microphone setup process. Fingers crossed that this is the issue, and that further 8051 disassembly isn't required, because that's pretty time consuming.

Anyways, like always, will update with progress here.

@Conmanx360

This comment has been minimized.

Copy link

commented Sep 29, 2018

Okay, just finished the ZxR patches. Gotta go to work now, but I'll do another look over them and then hopefully get them sent out tonight. That should wrap up getting audio output on the PCI-E Creative cards, next goal is the microphone.

@Conmanx360

This comment has been minimized.

Copy link

commented Oct 1, 2018

Got the ZxR patches sent out on Saturday night, looks like they should be good. Turning focus back on microphone now, already got timing info from QemuHDADump, so hopefully that should give me enough info to figure it out.

@Lolzen

This comment has been minimized.

Copy link

commented Oct 3, 2018

This might be somewhat related:
As i'm dual booting with Win7 currently, i noticed when i didn't fully power down the PC after being in Linux the mic loudness is affected in Win.
More precise: with a patched kernel the mic is significant more down in input volume, despite no settings changed until shutdown, boot. With an unpatched kernel (i.e. no sound) the mic is not picking up anything without proper shutdown. Reeboots don't "reset" the card.

Might have nothing to do with it at all, just though i'll throw it in here so it could be somewhat helpful(?)

@Conmanx360

This comment has been minimized.

Copy link

commented Oct 3, 2018

Yeah, the original ca0132 driver (unpatched one) sets some stuff up that is unfixable without a full shutdown and clearing of the onboard memory. If I had documentation, I could probably figure out what is being set and un-set it to fix it... might even be related to the fact that the original ca0132 driver tries setting up a digital mic, which the desktop cards don't have.

I'm kind of at the end of my wits with the microphone. Not many more ideas for fixing it. I still have a few, but I feel like they're not very likely to work. Once again, it's another case of lacking the proper documentation to actually debug what's going wrong. I believe that all of the info could be found through disassembly of the 8051's program, but like I've said before, that could take quite a bit of time.

I know I'm sending the exact same commands that Windows is, which to me seems to say that something else is wrong, either with the way Linux sets up streams, or maybe setting up controls causes it to run commands more than once, I really don't know. I know that my earlier drivers had the Sound Blaster Z microphone working all the time, and input effects worked fine as well. Maybe I should roll back to those and get some dumps of what verbs are sent from a virtual machine, because doing diffs between that driver and the ones where it began to break gave no indication on what went wrong.

I'm sure I'll figure it out. It's just going to take some time.

@Lolzen

This comment has been minimized.

Copy link

commented Oct 3, 2018

Thanks for the insight!
It's not a very urgent problem at all imo, like i said i just wanted to be sure you're aware of it, which you just confirmed :)
EDIT: any news on Creative's involvement? You mentioned earlier they'd be willing to help.

@Conmanx360

This comment has been minimized.

Copy link

commented Oct 3, 2018

@Lolzen - No updates on that. Not sure what to expect. I was told that they were looking into ways that they could help, but nothing more than that. So, I think it's best to expect that they most likely won't be helping out much on the technical side.

I never really got my hopes up on it, although it did sound good. I'll continue to bug them and see what I get out of it.

@Conmanx360

This comment has been minimized.

Copy link

commented Oct 5, 2018

Ahhh, this microphone issue is exhausting. Not even sure I'm making progress. Not sure if I mentioned it before, but it used to work perfectly fine in an older version of the driver I had written which only had stuff for the Sound Blaster Z. I've moved back to that version, and I'll be trying to debug the execution of it vs. the new, non-working one. So, hopefully now I'm not just trying things without any idea of what I'm doing.

Creative Labs now has a subreddit. I asked the moderator if I could make a post there on this, and he said that it'd be fine. So, I may make a post over there. It'd probably include a FAQ of some sort, and the stuff to figure out DKMS, instead of having it on some Github project that may end up being hard to find... I'll update here if/when I end up making a post there.

@Conmanx360

This comment has been minimized.

Copy link

commented Oct 6, 2018

Soooooooooooooo, seems like I solved the mic issue. Funny enough, a bug in the earlier versions of the code was actually what made it work. I don't know why it did, but it did, and now the microphone seems to be working fine as well as the input effects.

I'll try to mess with it a bit and see if I can't make it look better. If you are compiling your own patch and want to fix it, for Sound Blaster Z/ZxR, in sbz_setup_defaults, before the dsp download check, add:

        if (spec->quirk == QUIRK_SBZ || spec->quirk == QUIRK_ZXR)
		ca0132_alt_dsp_scp_startup(codec);

Similarly, for the AE-5, in ae5_setup_defaults, add:

        if (spec->quirk == QUIRK_AE5)
		ca0132_alt_dsp_scp_startup(codec);

Like I said, this is kind of silly. The checks for the quirks might not be necessary, but I haven't tested it out without them yet, and it works like that as for now.

If anyone else tests it, let me know if it works for you. After so many attempts at fixing it, I have my doubts, but so far it's been working. Now that that issue is (seemingly) out of the way, I feel a lot better.

@Conmanx360

This comment has been minimized.

Copy link

commented Oct 7, 2018

Okay, looks like an

msleep(100);

at the start of the setup_defaults function is sufficient enough to make the microphone work, and that the commands only served as a delay. Should be a pretty simple patch. Will test it out for a little bit before sending it out.

@Conmanx360

This comment has been minimized.

Copy link

commented Oct 8, 2018

Sent the microphone patches out, so, that should be it. Sending the firmware is the next on my list of things to do, then I'm pretty sure that wraps up getting the cards working for the most part.

Anyone know of anything else that still needs done? I can't really think of anything, I guess the AE-5 LED stuff, but that's not really necessary to get the card working or anything.

Edit: Also, I'll include links here, since this should be my final major post on status.

Most recent version of the patch is here: patch_ca0132.c

Most recent version of the desktop firmware (Sound Blaster Z, ZxR, AE-5, and Recon3D): ctefx-desktop.bin

Most recent version of the Recon3Di firmware: ctefx-r3di.bin

If you wish to donate, link is here: Donate

Like I said, that should end the majority of my work. I plan to make a post over on the SoundBlaster subreddit once the mod responds, currently only mods can post threads there. When I can do that, I'll post a more in depth writeup with a FAQ and stuff.

@nikosmar

This comment has been minimized.

Copy link

commented Oct 8, 2018

Since this is my first post here, I have to thank you for your work.

Anyone know of anything else that still needs done? I can't really think of anything, I guess the AE-5 LED stuff, but that's not really necessary to get the card working or anything.

I have SBZ on (K)Ubuntu 18.04.1 kernel 4.18.10 and sometimes (I can't remember exactly when) I have no sound after rebooting. This is fixed by toggling line out/headphones on alsamixer, not a serious bug of course.
I think I have read it already, but I am not sure if it's fixed.

@Conmanx360

This comment has been minimized.

Copy link

commented Oct 9, 2018

@nikosmar - Hmm, that's a weird bug I've never had / heard anyone mention. Maybe it has something to do with your alsamixer controls not being saved or something? What all do you have plugged in? Headphones and line-out, or just headphones?

@Conmanx360

This comment has been minimized.

Copy link

commented Oct 9, 2018

Okay, I created a thread over on the SoundBlasterOfficial subreddit, so migrating over there would probably be a good idea. I'll still try to respond to issues here, but it'd probably be easier to do any discussion over there.

@nikosmar

This comment has been minimized.

Copy link

commented Oct 9, 2018

@Conmanx360 I have plugged in my headphones, the card's mic and a set of logitech z506. I will write down when does this happen, and try to reproduce it, then I'll post my results on the reddit thread.

Lolzen added a commit to Lolzen/void_packages that referenced this issue Oct 9, 2018

add ca0132 patched kernel
This is the standard Linux kernel with patches for Sound Blaster R3D/R3Di/Z/ZxR/AE-5 which will be upstream
partially in 4.19 or later
ValveSoftware/SteamOS#221
https://www.reddit.com/r/SoundBlasterOfficial/comments/9mm5ad/sound_blaster_r3dr3dizzxrae5_linux_driver/
@lss4

This comment has been minimized.

Copy link

commented Mar 5, 2019

I've been thinking about posting this minor issue for a while... just not sure if the issue is with the driver or with PulseAudio. I'm using Sound Blaster ZxR with latest Manjaro Cinnamon on 4.20 kernel.

It seems for some reasons, with the desktop environment's Sound Settings (it uses PulseAudio), both Headphones and Line Out outputs to speakers. Actually, the underlying alsamixer settings set output to Line Out on both output options. I can manually set the output to Headphones using alsamixer, but it won't survive across reboots which means I need to manually change this every startup. While this can be a little inconvenient, everything essential works, including mic and speaker/headphone output.

Manjaro Cinnamon is the only OS installed on this system, so issues related with dual-booting is not involved.

@JacekJagosz

This comment has been minimized.

Copy link

commented Mar 5, 2019

@lss4 Destktop sound settings don't work for me either, no matter the OS.
I just use alsamixer instead and run it with sudo (sudo alsamixer) to make the settings stick after reboot. I also read that when even that doesn't work, you should use sudo alsactl store.
I use Sound Blaster Recon 3Di (Sound Core 3D - integrated into the mobo) for future refference.
Good luck!

@lss4

This comment has been minimized.

Copy link

commented Mar 29, 2019

The issue with desktop sound settings (PulseAudio) is still here.

While we can work around by using alsamixer (bypassing PulseAudio), it's still kinda inconvenient when we can't just use our desktop environment's sound settings...

@TTimo

This comment has been minimized.

Copy link
Collaborator

commented Apr 1, 2019

Since there is no clear problem with SteamOS here, but rather a problem with Linux support in general for some of Creative Labs's products, I'm going to be closing this report. Please open a different report if you have compatibility problem specifically with SteamOS. See the links in the history to SoundBlasterOfficial's subreddit, etc.

@TTimo TTimo closed this Apr 1, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.