You are not logged in.
This applies to all sound on the entire system. No matter what is playing, this happens. I've searched quite a bit on this issue, and haven't found anything on it at all. I've even asked fellow arch users about this, and I still couldn't figure it out. Now to get to the meat of it.
First I'd like to go over everything I've tried. I've checked alsamixer, and master has been moved to 100%. I've downloaded pavucontrol, and sound is at 100%. I've killed and started pulseaudio, still no luck. I installed Antergos to see if maybe I just missed a config somewhere, nope. However... I have found one lead. When I hibernate and start back up... the sound returns to normal. Then and only then does it work. My guess is something isn't starting correctly. Once I return from hibernate, that something is reset. I tried to use Linux-LTS kernel just to see if this problem is maybe kernel related just to be sure. Sadly every time it kernel panicked. No idea why. My guess it has something to do with usbcore. I don't know for sure, but I did notice in dmesg, my usb devices were reset once I returned from hibernation.
This is the dmesg containing everything from startup, a hibernation, and sound working after hibernation: https://pastee.org/dgf8r
Yes I could just hibernate every time I start up, but that is unbelievably annoying. Hopefully I can figure this out ![]()
Last edited by fisch246 (2014-08-03 22:39:22)
Offline
Looks like it might be an issue directly related to the Plantronics Gamecom 780 headset. It's very possible it could be even kernel related. Since trying to switch to linux-lts gave me a kernel panic... no idea what to do ![]()
Offline
Offline
Yes I'm aware of this thread. However he ended up just returning it. From researching this issue, I found it was a kernel level problem. People using debian with the 3.14, and 3.15 kernel reported the gamecom "not working". So my assumption is the solution is to downgrade the kernel. However I had nothing but kernel panics no matter what kernel I changed to. Before I knew it was the 3.14 kernel, I switched to linux-lts, and it panicked. My assumption is I have too much stuff relying on the new kernel, so the only direction I can switch to, is future kernels. I'll try and get ahold of someone working on the kernel to see if I can get them to fix this.
Offline
As mentioned in the quoted conversation, Plantronics knows, but apparently they need reminding, so I would contact them. Since this is alsa/audio related, I would rather seek help from alsa developer or user mailing list.
Offline
Looks like the fix is somewhere in here: https://bugzilla.kernel.org/show_bug.cgi?id=65251
I'll look through it, and if I figure it out... I'll post a complete step by step fix for this.
Offline
https://bugzilla.kernel.org/attachment. … ction=diff
This is already in the kernel, at least I have it in linux-rt sources.
https://bugzilla.kernel.org/attachment. … ction=diff
This one is absent however. Look here for some guidance.
https://bbs.archlinux.org/viewtopic.php?id=185091
Offline
Patch submitted to Maintainer:Sound. To fix in the meantime just use abs to patch u8 buf[2] = { 0x74, 0xdc }; to make it look like this: u8 buf[2] = { 0x74, 0xe3 };
This will make the volume levels act more naturally. Also make sure you edit pacman.conf with IgnorePkg: linux
Then finally, make sure you pay attention to patch notes of future Linux kernels, and comment out that line once this is fixed. Then run pacman -Syu to upgrade the kernel.
Offline
Has it been taken into consideration that there are two models with the same id? Making one work instead of the other will not be a solution, so I hope this particular issue got enough attention.
Offline