2016-05-04, 00:02
First of all I would like to say that I resolved the issue I was having with there being no sound in desktop mode. I would also like to say that I've been using Kodi for awhile on various computers, and when it works, it works fine and I like it. But when it doesn't work, god help you if you're normally a Windows user.
I'm posting this not because I solved the issue, but because I have no idea how I solved it. In fact technically it should not be working yet now it is.
Okay lets start at the beginning. I was using an old Dell Optiplex GX-620 as a general purpose video player and YouTube machine, running Kodibuntu. It worked well for what it was, but a Pentium 4, even a high end one (3.4 Ghz) just doesn't have the horse power for YouTube anymore. Well I had a Socket FM1 CPU that I got for free and a spare stick of DDR3, so I decided to purchase a suitable motherboard and build a system with better horse power.
I purchased an MSI A55M-P33 motherboard, put the CPU (technically APU, an AMD a3400) into it, 2 GB of RAM, an old PCi WiFi card and it was ready to go.
Except there was no sound.
My first troubleshooting step was to reinstall Kodibuntu from scratch. I had initially just taken the hard drive from the GX-620 and popped it in the new machine. Linux being generally okay with moving from one chipset to another I figured I'd pop in the HDD and that would be the end of it. But it wasn't, so I formatted and reinstalled. That didn't fix the issue.
Eventually after trying various things inculding updating Kodi to 16.1, and verifying that the sound hardware did indeed work by installing an old copy of Ubuntu, I formatted and reinstalled Kodibuntu again. Using tips from this forum I got the sound to work in KODI itself. The issue is my new motherboard technically has two sound cards, one HDMI and one analog... weird since this board does not feature an HDMI port, but moving on...
I now had sound in Kodi proper, but the desktop mode still did not have sound. I tried playing with settings in alsamixer, no luck. Then I saw the post about creating a file in the /etc folder asound.conf I believe.
So I set out to try that but there was another problem. By default the kodibuntu installation does not have a text editor as far as I can tell. So I went to the package manager and picked one to install with an easy to remember name... kwrite. So just install that and simple, right?
264 MB of packages later... all that just so I can make a text file? And being a Windows user I expected the new program to appear in the "start menu" or some kind of shortcut or icon that I could click on to open it. Nope! Had to open it from the terminal.
Now here is where it gets really weird. I followed the steps to make the asound.conf file, but when I went to save it, I was denied due to permissions... I should have done sudo kwrite I guess. However then I heard a blip and saw a notification for a multimedia device. Went to YouTube and sure enough the sound was working!
Sound now works in Kodi and the desktop mode, but there is no asound.conf file. I checked the /etc folder, looked for hidden files, and it is not there. Sound continues to work even after rebooting the system. There's no volume control, but running alsamixer I can adjust it.
So how the heck did I fix it? And, this is a question that goes back to ~2001 back when I first tried Mandrake linux... Why is linux in general still so weird and user unfriendly in certain spots after so many years? I mean it has gotten a bit better and if you're going to use it for a few specific tasks you'll be fine, but dig deeper and it's still a nightmare.
I'm posting this not because I solved the issue, but because I have no idea how I solved it. In fact technically it should not be working yet now it is.
Okay lets start at the beginning. I was using an old Dell Optiplex GX-620 as a general purpose video player and YouTube machine, running Kodibuntu. It worked well for what it was, but a Pentium 4, even a high end one (3.4 Ghz) just doesn't have the horse power for YouTube anymore. Well I had a Socket FM1 CPU that I got for free and a spare stick of DDR3, so I decided to purchase a suitable motherboard and build a system with better horse power.
I purchased an MSI A55M-P33 motherboard, put the CPU (technically APU, an AMD a3400) into it, 2 GB of RAM, an old PCi WiFi card and it was ready to go.
Except there was no sound.
My first troubleshooting step was to reinstall Kodibuntu from scratch. I had initially just taken the hard drive from the GX-620 and popped it in the new machine. Linux being generally okay with moving from one chipset to another I figured I'd pop in the HDD and that would be the end of it. But it wasn't, so I formatted and reinstalled. That didn't fix the issue.
Eventually after trying various things inculding updating Kodi to 16.1, and verifying that the sound hardware did indeed work by installing an old copy of Ubuntu, I formatted and reinstalled Kodibuntu again. Using tips from this forum I got the sound to work in KODI itself. The issue is my new motherboard technically has two sound cards, one HDMI and one analog... weird since this board does not feature an HDMI port, but moving on...
I now had sound in Kodi proper, but the desktop mode still did not have sound. I tried playing with settings in alsamixer, no luck. Then I saw the post about creating a file in the /etc folder asound.conf I believe.
So I set out to try that but there was another problem. By default the kodibuntu installation does not have a text editor as far as I can tell. So I went to the package manager and picked one to install with an easy to remember name... kwrite. So just install that and simple, right?
264 MB of packages later... all that just so I can make a text file? And being a Windows user I expected the new program to appear in the "start menu" or some kind of shortcut or icon that I could click on to open it. Nope! Had to open it from the terminal.
Now here is where it gets really weird. I followed the steps to make the asound.conf file, but when I went to save it, I was denied due to permissions... I should have done sudo kwrite I guess. However then I heard a blip and saw a notification for a multimedia device. Went to YouTube and sure enough the sound was working!
Sound now works in Kodi and the desktop mode, but there is no asound.conf file. I checked the /etc folder, looked for hidden files, and it is not there. Sound continues to work even after rebooting the system. There's no volume control, but running alsamixer I can adjust it.
So how the heck did I fix it? And, this is a question that goes back to ~2001 back when I first tried Mandrake linux... Why is linux in general still so weird and user unfriendly in certain spots after so many years? I mean it has gotten a bit better and if you're going to use it for a few specific tasks you'll be fine, but dig deeper and it's still a nightmare.