Advertisement
Guest User

Untitled

a guest
Aug 9th, 2014
29
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 7.80 KB | None | 0 0
  1. [15:37] <swenzel> Hey, guys... I have some problems with my sound. It works fine on win8 but on ubuntu 14.04 the mainboard's audiocard makes no sound at all :/
  2. [15:37] <swenzel> http://www.alsa-project.org/db/?f=8f57f0b72d65046469b8b6ce8a57ff6fe0371769
  3. [15:38] <Lukah> thanks gnarface, debianuser :) We'll look into those.
  4. [15:40] <gnarface> Lukah: eh, i didn't really help, but good luck
  5. [15:42] <debianuser> Lukah: In case of snd-aloop+route+multi duplication .asoundrc config can look like this: http://pastebin.com/B7iEKBwH Then you can listens to "hw:Loopback,1" to hear what's playing.
  6. [15:42] <swenzel> I tried some stuff from https://help.ubuntu.com/community/SoundTroubleshooting but could not find the problem... it seems to me as if everything works fine, but I can't hear anything oO
  7. [15:45] <gnarface> swenzel: is it snd_hda_intel?
  8. [15:46] <swenzel> gnarface: guess so... the other one should be the HDMI port of my graphics card
  9. [15:46] <swenzel> and the usb headset works fine
  10. [15:46] == azeam_afk has changed nick to azeam
  11. [15:46] <gnarface> swenzel: maybe the speakers aren't plugged into the right jack?
  12. [15:47] <swenzel> gnarface: as i said it works on windows8
  13. [15:47] <swenzel> parallel installation
  14. [15:47] <gnarface> ah, right
  15. [15:47] <debianuser> swenzel: Hm... Codec: Creative CA0132... I remember someone have already asked about some problems with this codec... Wait a little, I'm digging through my logs...
  16. [15:47] <swenzel> thx
  17. [15:47] <gnarface> i have had auto-detection problems with snd_hda_intel before but its been a long time
  18. [15:48] <gnarface> (where it would map the jacks wrong)
  19. [15:48] <swenzel> well i could try around a bit and see if one wokrs
  20. [15:49] <gnarface> swenzel: i assume you verified that volumes are up and unmuted in alsamixer too?
  21. [15:49] <swenzel> oh, indeed
  22. [15:49] <swenzel> the mapping is wrong
  23. [15:49] <swenzel> i found one jack that works
  24. [15:50] <gnarface> you can pass a parameter to the module at load time to override the auto detect
  25. [15:51] <gnarface> but if its multi-channel do verify alsamixer too (you might have the side speakers defaulting to 80% volume but the front speakers defaulting to muted or something like that)
  26. [15:52] <swenzel> i think alsa doesn't recognise that it is surround... at least i have not as many mixers as channels
  27. [15:52] <gnarface> well, that definitely sounds like the typical failure of auto-detect to me but it could be a red herring like i said
  28. [15:53] <gnarface> but getting stereo only sound, and out of the wrong jack... definitely has happened to me before
  29. [15:54] <swenzel> what do you want me to do?
  30. [15:54] <gnarface> just like i said, check alsamixer, and see if you have "front" "surround" "center" "lfe" and "side" sliders, and whether any are muted
  31. [15:55] <gnarface> or at 0%
  32. [15:55] <gnarface> if even alsamixer isn't reporting the right amount of channels, then you know for sure its failed to auto-detect
  33. [15:57] <swenzel> I have: Master, PCM, Surround, S/PDIF, S/PDIF D, Crustali, Dialog P, Equalize, HP/Speak, HP/Speak, PlayEnha, Smart Vo, X-Bass
  34. [15:57] <swenzel> only the S/PDIFs are muted
  35. [15:57] <swenzel> and only master and pcm have volume bars
  36. [15:57] <gnarface> interesting
  37. [15:58] <gnarface> well i'm not familiar with your hardware, so i can't tell you what to set it to
  38. [15:58] <gnarface> but the module parameter is "model="
  39. [15:59] <gnarface> and the only exhaustive list of available options for it is in the actual file in the kernel
  40. [15:59] <gnarface> in the comments in the source code
  41. [15:59] <gnarface> (brutal, i know)
  42. [16:00] <gnarface> i had to try a few until i got one that mapped them right by luck basically
  43. [16:00] <gnarface> (i think it was 6-stack-dig )
  44. [16:01] <debianuser> swenzel: Just to make sure that alsa-info collected it correctly - this is a builtin sound of the G1.Sniper Z87 motherboard, which has 5 jacks on the back, and, probably, 2 front jacks.
  45. [16:02] <debianuser> is that right?
  46. [16:02] <swenzel> debianuser: that's right... it also has two front jacks... the one that works is the upper left on the back, next to the optical port
  47. [16:04] <hegge> Most CA0132-based cards won't work with the snd-hda-intel driver, see comment 106 in https://bugzilla.kernel.org/show_bug.cgi?id=55541#c106
  48. [16:05] <gnarface> hegge: not even with a specific model= setting?
  49. [16:05] <debianuser> swenzel: That's actually a correct Line-Out jack. :) I mean that's where the sound is supposed to come from according to the motherboard manual. :)
  50. [16:06] <debianuser> swenzel: Are you using it with stereo speakers or 5.1?
  51. [16:06] <hegge> gnarface: Not as far as I know, but Takashi suggests to try model=generic.
  52. [16:08] <swenzel> debianuser: I'm using only stereo, currently... I also thought it could be the right one... but what is then the other one right below it good for?
  53. [16:08] <swenzel> where do i have to put this model=whatever at all?
  54. [16:09] <gnarface> if you want it to stick through reboots, it depends on the distro
  55. [16:09] <debianuser> Top-to-bottom right-to-left they are: Line In/Mic In Jack, Line Out, Optical S/PDIF, Center/Subwoofer Speaker Out, Rear Speaker Out, Headphone/Speaker Out (that's according to the manual)
  56. [16:09] <swenzel> debianuser: ehm i mean the lower left one... with the speaker and headphone sign
  57. [16:10] <gnarface> swenzel: temporarily though, you would: rmmod snd-hda-intel && modprobe snd-hda-intel model=[whatever]
  58. [16:10] <gnarface> swenzel: (as root)
  59. [16:11] <swenzel> or i leave it in lineout and hope that win8 doesn't care and works anyway
  60. [16:11] <gnarface> swenzel: if your speakers have their own amp, i don't see a real problem with that
  61. [16:11] <swenzel> they do
  62. [16:11] <debianuser> Ah... Then it's a misdetection. Other jacks are disabled, we can fix that with hda-jack-retask/hda-verb, but if you found a working one, and you're using stereo speakers anyway, do you need to dig any further? I mean is there still something you want to fix?
  63. [16:12] <swenzel> maybe it could be of some help for other people...
  64. [16:17] <debianuser> I'm not sure the model= option would help, since I don't see any models in https://www.kernel.org/doc/Documentation/sound/alsa/HD-Audio-Models.txt or in sound/pci/hda/patch_ca0132.c But I can explain how to enable other jacks with hda-verb, if you want to try. It's just if you don't need them anyway...
  65. [16:21] <swenzel> debianuser: how much work is it to write one?
  66. [16:22] <debianuser> swenzel: Well, for example it seems that you can enable the disabled lineout jack with `sudo hda-verb /dev/snd/hwC0D2 0x0f SET_PIN_WIDGET_CONTROL 0x40`
  67. [16:23] <debianuser> (in Ubuntu `hda-verb` is a part of alsa-tools)
  68. [16:23] <debianuser> (i.e. `sudo apt-get install alsa-tools` if you don't have them yet)
  69. [16:24] <swenzel> alsamixer still shows the same channels
  70. [16:24] <debianuser> No, nothing would change in alsamixer
  71. [16:25] <debianuser> but you should now hear the same sound from both jacks
  72. [16:25] <swenzel> ah
  73. [16:25] <swenzel> indeed, it works
  74. [16:26] <debianuser> It's like your codec has a "Pin Complex" node 0x0f that is probably some jack, but it was not configured as IN or OUT. It just was not configured at all, i.e. it was doing nothing. With that command I configured it to be OUT pin.
  75. [16:28] <swenzel> but it is only temporary?
  76. [16:28] <debianuser> it's a runtime change, i.e. it would be lost on reboot. But if you like it you can add that command to e.g. /etc/rc.local :)
  77. [16:28] <swenzel> nah... I'll stay with lineout jack then :D
  78. [16:28] <debianuser> As you wish. :)
  79. [16:30] <debianuser> Also, if you wish, you can report that as a bug to alsa-devel mailing list (since it is a bug, it should just work, without messing with hda-verb). If you do — describe the problem and add a link to your alsa-info output ( http://www.alsa-project.org/db/?f=8f57f0b72d65046469b8b6ce8a57ff6fe0371769 ). And then maybe alsa developers would fix it in next kernel...
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement