Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No audio devices found after update #190

Open
bwestover opened this issue Jun 18, 2016 · 3 comments
Open

No audio devices found after update #190

bwestover opened this issue Jun 18, 2016 · 3 comments

Comments

@bwestover
Copy link

I recently updated to v.3.3.0 on a RPI 3. After this update I don't have any sound.

Apologies for the double post (I also logged this on the community forum: http://world.kano.me/forum/topic/upgraded-to-3.3.0-now-audio-devices-are-not-found). I'm not sure if that location is monitored and I figured you would want to know about this asap. 🙇

I have done a bit of troubleshooting:

It seems ALSA can't see the device:

$ sudo aplay -l
aplay: device_list:268: no soundcards found...

Let me know if any additional information would be helpful

@Ealdwulf
Copy link
Contributor

Hi @bwestover , sorry about this.
On the pi3, there is supposed to be an entry in the config file /boot/config.txt which enables the audio device. Could you post your config.txt? It is on the SD card as just 'config.txt' if you plug it into a pc.
It should contain the line dtparam=audio=on at some point.
If this is missing we would like to know how this happened, so it would be useful also to post any logs you might have from the update. These can be printed by kano-logs show -l kano-updater
Thank you.

@bwestover
Copy link
Author

@Ealdwulf that parameters was indeed missing. Adding it and rebooting fixes the sound 🎉

I'm afraid the output from that log command doesn't look to have much:

2016-06-19 21:08:17 kano-updater[5595] warning The notification pipe not found at /home/brett/.kano-notifications.fifo

@Ealdwulf
Copy link
Contributor

Thanks! I'll let the customer support team know the solution in case it affected anyone else.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants