ASUS VC66-C sound stopped
I bought a VC66-C. Nice little box. All I did was move my disk to it and everything worked, except for the wifi. OK, I'll deal with that later and just plug a USB dongle in. So, I did an upgrade and a reboot, and then the sound died. We're 19 years into the 21st century and sound still dies? le sigh
So, does anyone have a recommended path to take for this to get the sound back? Sound Preferences says that the Built-In Audio Is Disabled. I don't have a clue how to proceed from here. It's certainly not disabled in the BIOS. Everything I find online is related to ALSA and none of it works. Please help. UPDATE: I have it working now. The quick solution is below. No .asoundrc is needed, and no files are needed in /etc/modprobe.d. Just make the change below and it works. Code:
1. Open /etc/default/grub |
Some more info. Note where I've highlighted in red "Active Profile: off". That has to be related to the problem. What do I actually do about it to enable the profile? Or is that just a symptom and not the problem?
ADDED: OK, I just noticed what that means. All the devices are set to "available: no". So, is that a hardware problem, a software setting, or something else/somewhere else. Output of pactl list Code:
Module #0 |
More info: I've just hooked my laptop up to the TV with the same HDMI cable. The sound from the laptop to the TV is fine. So, the problem is somewhere in the sound setup in the Linux box.
|
The sound card is an ALC255
|
If you run pulse operations as root (sudo or otherwise) it might have changed the "users" permissions. You can chown to get the permissions back. Which used to be /run/user/$UID/pulse*. And some of that might be the version of pulse in question. In days of old it would create /.pulse* things and those would trump any $HOME/.pulse* things and block audio. Although things moved to $HOME/.config/* and such. A reinstallation should fix it... oi... Still kind of sad that twenty years later, most of our audio things are command line based. Even jackdbus (jack2) requires some CLI parameters before it awakes from the dead.
And then there's hardware quirks, like a 3.5mm plug being partially out. Or HDMI to a DVI adapter that lacks audio signal. It's not common for the soundcard to fail, unless other things failed too (lightning / PSU / ...). They can be disabled in the bios/uefi to "force" use of another device (cause windows is stupid). But computers are pretty stupid, they only do what you (or others) tell them to do. And they come with soo many audio devices now, modems, webcams, motherboards, video cards, bluetooth, ... It's probably just trying to use the default sound output, which is obviously your webcam (it has no output, well, most of them anyway). |
Your pulse output is interesting:
Sink #1 State: SUSPENDED Name: auto_null Description: Dummy Output Driver: module-null-sink.c ... Source #2 State: SUSPENDED Name: auto_null.monitor Description: Monitor of Dummy Output Driver: module-null-sink.c ... Send any suspend commands to the device(s)? Not sure if it's NOT suspended when you try to use them. Also interesting that the actual hardware is NOT the SINK (output/speakers). But the SOURCE (input/microphone). |
Quote:
I'm a bit confused about your comment that my default sound output is my webcam. Was this a funny, or did you see something in the data I listed that points to a webcam that I don't have? |
It was a funny. We used to only have one soundcard (most of us anyway). Now we have at least 3 on most systems. Motherboard, Videocard, Webcam, ... Whatever one powers up first gets index 0 (default), and the webcam being the simpler one, tends to win a few times. Various ways to force indexing, even have a dummy soundcard (snd-aloop) to route audio to taste regardless of what hardware / sound daemon is in play.
|
OK, I've made some progress: I've gotten the headphones to work. So, I wonder if the HDMI cable just happened to go bad at a bad time?
I created /etc/modprobe.d/intel_snd.conf: Code:
options snd-hda-intel single_cmd=1 I also created /etc/modprobe.d/modesetting.conf: Code:
options i915 modeset=1 So, I guess the next step is getting a new HDMI cable and trying that. Also, I wonder if "model=basic" might be shutting off the HDMI now that the rest of it is working? So, I guess I'll try *that* next. :) |
Sorry, this was a dupe post.
|
I've had an HDMI cable fail. Radio Shack brand and a while ago. Things were "much" better with a new cable. Although I haven't done much HDMI audio to date. I just know that it's not a default by default. Even though that might be a modern expectation.
|
Well, it was working. And then it didn't. I've looked through the BIOS and I can make it stop working altogether, but I can't make it work any better than it is right now, which is halfway. I've got the headphones enabled, more or less by accident, following instructions for fields I don't understand and can't find a current list of setting for. Maybe I'll run into something.
And I just put a new HDMI cable on and that didn't change anything. I can't even figure out how to boot with the old kernel. I thought it was just holding shift down during boot, but that doesn't get me to the grub screen. |
$ amixer controls
$ amixer contents Do you remember the fields names? ADC (analog to digital converter, normally for audio input / microphones). DAC (digital to analog converter, for speakers / output). MIC for microphone. PCM (pulse code modulation) for output / speakers. And a few for codecs / protocols for things like optical or digital audio like S/PDIF (sony/philips digital interface), or TOSLINK. |
I've made some progress today. I have headphone sound. Plugging it in switches the sound sink. Unplugging it changes the sink back to the HDMI, which still has no sound. (grrrr)
My current /etc/modprobe.d/snd_hda_intel.conf (renamed from whatever I had it as for clarity). I commented everything except for "model=generic". That's what made the biggest improvement, as in the HDMI and headphones are now available and headphones switches the sink. Code:
#options snd-hda-intel model=basic Code:
[ 2.562056] snd_hda_codec_generic hdaudioC0D0: autoconfig for Generic: line_outs=1 (0x21/0x0/0x0/0x0/0x0) type:hp Is there a way to restart pulse to reload the modprobe values, or do I have to continue to reboot? Sorry, me<-clueless. |
Put "autospawn = no" in /etc/pulse/client.conf and you can stop/start pulseaudio.
$ pulseaudio --kill $ pulseaudio --start $ sudo modinfo snd-hda-intel Code:
filename: /lib/modules/4.9.0-9-amd64/kernel/sound/pci/hda/snd-hda-intel.ko |
Quote:
I'm down to just "options snd-hda-intel model=generic" in my snd_hda_intel.conf file, now that I know that probe_mask is -1 (all ones) by default. I have headphones working. They switch the sink back and forth to HDMI like they should, but no output sound on the TV. I tried both HDMI input ports on the TV, as well as a new HDMI cable. This is Big progress. But it seems that I just can't finish the last mile. I guess about the last thing to do is to put the Win 10 disk back in the computer and see if it works for sound once everything is configured. Maybe I somehow broke the sound on the connector? I dunno. |
So, after booting from power off, it became clear that something was retaining the last single_cmd, so I had to add that back to the conf file. But, that's where I'm stuck. I've got headphones, and it switches when the phones go in or out. I've just got no HDMI sound. Also, I did put the Win 10 disk in without changing anything else. The HDMI sound works with it in.
Code:
options snd-hda-intel single_cmd=1 |
You might need a fancy .asoundrc if your HDMI audio only takes certain protocols like AAC, MP3, or other "formatted" audio, not PCM. I'm not quite sure though. My HDMI monitor lets you change from "digital" to "Line-In", and has a DDC/CI option to toggle ON/OFF in the monitors menu. None of which makes my HDMI audio work. Where outputing just to the hw:#,3 on my HDTV would work almost brain dead. So I might need a fancy .asoundrc file myself. I know my pocketchip doesn't output audio without it's fancy .asoundrc. But it's hardly a standard piece of kit and doesn't do HDMI.
|
Hi Shadow 7,
I'm using Debian Stretch. Just for grins, I did a clean install of Stretch on an old disk I had laying around. No sound, codec doesn't load, wakeup waits. Grrrrrrrrrrrr. So, sometime in the past, possibly even in a previous release of Debian, I fixed something in the sound on the machine this OS was originally installed on. That was either an ASUS mobo with an AMD FX-8350 or something like that, or my little eeebox which is where I lifted the mostly running OS from. Oh, and to make matters worse, I've upgraded to all SSD drives, and the old drive I installed to was a hardware drive. ZZZZZZZZZZZZZZz LOL Yeah, getting frustrated at all this time lost. So, I think that next I'm going to download a live CD and see what that does with this computer. I'll post the results when they happen. |
Quote:
Code:
[ 2.535654] snd_hda_codec_generic hdaudioC0D2: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) I'm wondering if it would be easier to get a set of cheap powered speakers, or maybe even bluetooth speakers. Except bluetooth would probably be the same nightmare as this, which I don't need. |
bluetooth nightmares are just having a driver that works and getting the device to connect. Which might not be an issue worth noting with "blessed" hardware and a DE with an easy button.
Running debian stretch here as well. With a flatpak of the game I tends towards, I don't need buster (yet) for the more recent video driver(amdgpu) (although I tend to recall HDMI audio working in buster/testing, since pulseaudio would switch to it everytime the screen blanked). |
I just installed the backport package and I'm running the higher kernel. No improvement on the sound, but at least the onboard wifi is working, so I can pack away the wifi dongle. I've pretty much run out of ideas with the sound. I tried a lot of stuff from looking at the code. Most things I tried it returned "unplugged" for all the HDMI stuff. Generic seems to want to work, but it doesn't. At least it's not marked "unplugged", it simply doesn't work. So, I don't know whether that means I don't have something set right, or it's just so lost it doesn't know what to do. I did download the firmware package for Buster, so I may give that a try.
|
W00h00!!!!! I got it working. As it turns out, I don't need any files in /etc/modprobe.d, nor do I need a .asoundrc file. I found the solution here:
https://askubuntu.com/questions/1015...eadphones-work [code] 1. Open /etc/default/grub 2. Add: GRUB_CMDLINE_LINUX="i915.alpha_support=1" 3. Run sudo update-grub to make the change effective 4. Reboot After that, it just works. The key thing about this is that this computer has a Coffee lake processor. The article links here for the explanation. https://www.phoronix.com/scan.php?page=article&item=coffee-uhd-graphics&num=1 |
i915 is the intel video driver. With coffee lake coming out Oct 2018, so the newest of the CPUs. Not surprised that you needed to add a module parameter. You could also add that parameter in /etc/modprobe.d/
# echo "options i915 alpha_support=1" > /etc/modprobe.d/custom_intel.conf Why not, you might want to boot with LiLo or some other craziness. # modinfo i915 Code:
filename: /lib/modules/4.9.0-9-amd64/kernel/drivers/gpu/drm/i915/i915.ko BTW, Buster will become the new stable next month (July 2019) by the looks of things. Release parties and all that jazz. |
Yeah, I did have an i915 setting in modprobe.d, but it was the wrong one. LOL I've got my sources.list setup for stretch, so I won't change dists without doing something affirmative. I've tried dist upgrades in the past, and except for one, they were all disasters. So, I'll have to give long thought to upgrading to Buster. Maybe next year or the year after. Usually it's when there's something I want to do that I can't that causes me to upgrade. But, now that I'm living on this sailboat, my needs are pretty straightforward.
Thanks for all the help, even if you didn't come up with the final solution. Frustrating problems like this can make for a lonely job. Bob |
Was a resolution ever found for this? ALC298 seems to be quite a mystery. I have a laptop that is all but perfect, if only it had audio.
|
All times are GMT -5. The time now is 02:57 PM. |