So, I contacted Creative and sent them back the headset, I figured I had gotten a faulty one, and they sent me back a refurbished one - with scratches galore everywhere on the headset.īut, I digress, it worked perfectly like new - until a month passed. I was having to redo this firmware business every single day just to get the thing to turn on and work, this went on for a good few months. Until the next day, and the next, and the next, etc. I downloaded an older firmware, installed it, downloaded the newest one, installed it, restarting the pc - and it worked fine after that. I looked online, found a solution that worked for me on this website. After about 2 months of normal use, the actual sound card/sound blaster just stopped powering on whenever the PC was turned on. If there's any more information and details you need, then please let me know.I've had issues pretty consistently with this device since purchasing it in December last year. snd_hda_codec_ca0132 hdaudioC0D1: ca0132 DSP downloaded and running snd_hda_codec_ca0132 hdaudioC0D1: dig-in=0xe snd_hda_codec_ca0132 hdaudioC0D1: Line=0x13 snd_hda_codec_ca0132 hdaudioC0D1: inputs: snd_hda_codec_ca0132 hdaudioC0D1: dig-out=0xc/0xd snd_hda_codec_ca0132 hdaudioC0D1: mono: mono_out=0x0 snd_hda_intel 0000:23:00.0: Force to non-snoop mode Some dmesg snippets regarding snd_hda_intel Memory at f7500000 (64-bit, non-prefetchable) Ĭapabilities: Power Management version 3Ĭapabilities: MSI: Enable- Count=1/1 Maskable+ 64bit+Ĭapabilities: Express Endpoint, MSI 00Ĭapabilities: Advanced Error ReportingĬapabilities: Device Serial Number 00-00-00-00-00-00-00-00 Memory at f7504000 (64-bit, non-prefetchable) Subsystem: Creative Labs Sound Core3D įlags: bus master, fast devsel, latency 0, IRQ 32 There's just basically no way to get the sound up and running, until another cold boot has been performed.Ģ3:00.0 Audio device: Creative Labs Sound Core3D (rev 01) Using rmmod -f snd-hda-intel or the like and running modprobe after does not resolve the issue. The dmesg output is the same in both instances The device always gets detected when booting and always loads the driver I'm loading the correct firmware from the tree I've used the alsa speaker-test utility to exclude potentional problems caused by pulseaudio Whenever I plug-in my AudioQuest DragonFly Red and plug in my headphone into it, sound starts playing immediately I've tried various kernel versions and the problem persists. I've tried both the speaker output and headphone jack (connected using a HDA connector) and both do not output any sound This soundcard was also in this system on Microsoft Windows 10 for over a year and always worked Testing the soundcard in Microsoft Windows 10 system for over a week (the issue didn't occur a single time to exclude some sort of hardware failure). Upgrading firmware of the motherboard (to exclude any possible related issues) Checked whether everything in alsamixer was unmuted This happens roughly 1 out of 4 to 1 out of 5 boots. Rebooting does not resolve the issue, only shutting down the system completely, waiting a few seconds and booting it up again resolves the issue. For some odd reason sometimes I don't have sound at all when performing a cold boot.
0 Comments
Leave a Reply. |