How can I install the sound modules [closed]
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgO9GURib1T8z7lCwjOGLQaGtrueEthgQ8LO42ZX8cOfTqDK4jvDDpKkLFwf2J49kYCMNW7d4ABih_XCb_2UXdq5fPJDkoyg7-8g_YfRUot-XnaXkNYycsNp7lA5_TW9td0FFpLQ2APzKcZ/s1600/1.jpg)
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhYQ0N5W1qAOxLP7t7iOM6O6AzbZnkXUy16s7P_CWfOb5UbTQY_aDsc727chyphenhyphen5W4IppVNernMMQeaUFTB_rFzAd95_CDt-tnwN-nBx6JyUp2duGjPaL5-VgNO41AVsA_vu30EJcipdDG409/s400/Clash+Royale+CLAN+TAG%2523URR8PPP.png)
up vote
0
down vote
favorite
I am running Ubuntu 16.04 LTS bash on Windows 10. When I have installed a command line music player, it couldn't play any track - Error: unable to play audio.
The command aplay -l
shows aplay: device_list268: no soundcards found.
So it looks like I need to install the sound modules. How can I do it? I have tried this:
$ sudo apt-get install linux-restricted-modules-uname -r linux-generic
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package linux-restricted-modules-4.4.0-43-Microsoft
E: Couldn't find any package by glob 'linux-restricted-modules-4.4.0-43-Microsoft'
E: Couldn't find any package by regex 'linux-restricted-modules-4.4.0-43-Microsoft'
Also, when running the command lspci -nnk | grep -A3 -Fe '[0403]'
it shows the following:
pcilib: Cannot open /proc/bus/pci
lspci: Cannot find any working access method.
apt package-management sound alsa windows-subsystem-for-linux
closed as off-topic by David Foerster, N0rbert, user68186, earthmeLon, Eric Carvalho May 12 at 23:22
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "This is not about Ubuntu. Questions about other Linux distributions can be asked on Unix & Linux, those about Windows on Super User, those about Apple products on Ask Different and generic programming questions on Stack Overflow." â David Foerster, N0rbert, user68186
 |Â
show 1 more comment
up vote
0
down vote
favorite
I am running Ubuntu 16.04 LTS bash on Windows 10. When I have installed a command line music player, it couldn't play any track - Error: unable to play audio.
The command aplay -l
shows aplay: device_list268: no soundcards found.
So it looks like I need to install the sound modules. How can I do it? I have tried this:
$ sudo apt-get install linux-restricted-modules-uname -r linux-generic
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package linux-restricted-modules-4.4.0-43-Microsoft
E: Couldn't find any package by glob 'linux-restricted-modules-4.4.0-43-Microsoft'
E: Couldn't find any package by regex 'linux-restricted-modules-4.4.0-43-Microsoft'
Also, when running the command lspci -nnk | grep -A3 -Fe '[0403]'
it shows the following:
pcilib: Cannot open /proc/bus/pci
lspci: Cannot find any working access method.
apt package-management sound alsa windows-subsystem-for-linux
closed as off-topic by David Foerster, N0rbert, user68186, earthmeLon, Eric Carvalho May 12 at 23:22
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "This is not about Ubuntu. Questions about other Linux distributions can be asked on Unix & Linux, those about Windows on Super User, those about Apple products on Ask Different and generic programming questions on Stack Overflow." â David Foerster, N0rbert, user68186
I have done everything you said but still not working
â Helio
Apr 26 at 20:45
1
WSL is no full Linux system and doesn't allow full hardware access. Thus it doesn't even have a kernel that would allow hardware access (via loadable modules or otherwise). It may be possible to get this to work but not how one would do it in a stand-alone Ubuntu installation, which means your question is off topic here on Ask Ubuntu. You may have more lock over on Super User.
â David Foerster
Apr 27 at 12:52
Please repost this question at Super User.
â karel
Apr 27 at 21:49
This question is cross-posted as of now (superuser.com/q/1317998/84807) and getting different answersâ¦
â Melebius
May 10 at 6:54
1
I'm voting to close this question as off-topic because others feel it is off topic, and the poster has cross-posted to superuser.com/q/1317998/84807 . I am confused that we have WSL tag, with no mention of it not being on-topic, and would like clarification if there is any.
â earthmeLon
May 12 at 19:40
 |Â
show 1 more comment
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I am running Ubuntu 16.04 LTS bash on Windows 10. When I have installed a command line music player, it couldn't play any track - Error: unable to play audio.
The command aplay -l
shows aplay: device_list268: no soundcards found.
So it looks like I need to install the sound modules. How can I do it? I have tried this:
$ sudo apt-get install linux-restricted-modules-uname -r linux-generic
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package linux-restricted-modules-4.4.0-43-Microsoft
E: Couldn't find any package by glob 'linux-restricted-modules-4.4.0-43-Microsoft'
E: Couldn't find any package by regex 'linux-restricted-modules-4.4.0-43-Microsoft'
Also, when running the command lspci -nnk | grep -A3 -Fe '[0403]'
it shows the following:
pcilib: Cannot open /proc/bus/pci
lspci: Cannot find any working access method.
apt package-management sound alsa windows-subsystem-for-linux
I am running Ubuntu 16.04 LTS bash on Windows 10. When I have installed a command line music player, it couldn't play any track - Error: unable to play audio.
The command aplay -l
shows aplay: device_list268: no soundcards found.
So it looks like I need to install the sound modules. How can I do it? I have tried this:
$ sudo apt-get install linux-restricted-modules-uname -r linux-generic
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package linux-restricted-modules-4.4.0-43-Microsoft
E: Couldn't find any package by glob 'linux-restricted-modules-4.4.0-43-Microsoft'
E: Couldn't find any package by regex 'linux-restricted-modules-4.4.0-43-Microsoft'
Also, when running the command lspci -nnk | grep -A3 -Fe '[0403]'
it shows the following:
pcilib: Cannot open /proc/bus/pci
lspci: Cannot find any working access method.
apt package-management sound alsa windows-subsystem-for-linux
edited Apr 27 at 12:51
![](https://i.stack.imgur.com/E0SEH.png?s=32&g=1)
![](https://i.stack.imgur.com/E0SEH.png?s=32&g=1)
David Foerster
26k1361106
26k1361106
asked Apr 26 at 8:56
Helio
11
11
closed as off-topic by David Foerster, N0rbert, user68186, earthmeLon, Eric Carvalho May 12 at 23:22
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "This is not about Ubuntu. Questions about other Linux distributions can be asked on Unix & Linux, those about Windows on Super User, those about Apple products on Ask Different and generic programming questions on Stack Overflow." â David Foerster, N0rbert, user68186
closed as off-topic by David Foerster, N0rbert, user68186, earthmeLon, Eric Carvalho May 12 at 23:22
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "This is not about Ubuntu. Questions about other Linux distributions can be asked on Unix & Linux, those about Windows on Super User, those about Apple products on Ask Different and generic programming questions on Stack Overflow." â David Foerster, N0rbert, user68186
I have done everything you said but still not working
â Helio
Apr 26 at 20:45
1
WSL is no full Linux system and doesn't allow full hardware access. Thus it doesn't even have a kernel that would allow hardware access (via loadable modules or otherwise). It may be possible to get this to work but not how one would do it in a stand-alone Ubuntu installation, which means your question is off topic here on Ask Ubuntu. You may have more lock over on Super User.
â David Foerster
Apr 27 at 12:52
Please repost this question at Super User.
â karel
Apr 27 at 21:49
This question is cross-posted as of now (superuser.com/q/1317998/84807) and getting different answersâ¦
â Melebius
May 10 at 6:54
1
I'm voting to close this question as off-topic because others feel it is off topic, and the poster has cross-posted to superuser.com/q/1317998/84807 . I am confused that we have WSL tag, with no mention of it not being on-topic, and would like clarification if there is any.
â earthmeLon
May 12 at 19:40
 |Â
show 1 more comment
I have done everything you said but still not working
â Helio
Apr 26 at 20:45
1
WSL is no full Linux system and doesn't allow full hardware access. Thus it doesn't even have a kernel that would allow hardware access (via loadable modules or otherwise). It may be possible to get this to work but not how one would do it in a stand-alone Ubuntu installation, which means your question is off topic here on Ask Ubuntu. You may have more lock over on Super User.
â David Foerster
Apr 27 at 12:52
Please repost this question at Super User.
â karel
Apr 27 at 21:49
This question is cross-posted as of now (superuser.com/q/1317998/84807) and getting different answersâ¦
â Melebius
May 10 at 6:54
1
I'm voting to close this question as off-topic because others feel it is off topic, and the poster has cross-posted to superuser.com/q/1317998/84807 . I am confused that we have WSL tag, with no mention of it not being on-topic, and would like clarification if there is any.
â earthmeLon
May 12 at 19:40
I have done everything you said but still not working
â Helio
Apr 26 at 20:45
I have done everything you said but still not working
â Helio
Apr 26 at 20:45
1
1
WSL is no full Linux system and doesn't allow full hardware access. Thus it doesn't even have a kernel that would allow hardware access (via loadable modules or otherwise). It may be possible to get this to work but not how one would do it in a stand-alone Ubuntu installation, which means your question is off topic here on Ask Ubuntu. You may have more lock over on Super User.
â David Foerster
Apr 27 at 12:52
WSL is no full Linux system and doesn't allow full hardware access. Thus it doesn't even have a kernel that would allow hardware access (via loadable modules or otherwise). It may be possible to get this to work but not how one would do it in a stand-alone Ubuntu installation, which means your question is off topic here on Ask Ubuntu. You may have more lock over on Super User.
â David Foerster
Apr 27 at 12:52
Please repost this question at Super User.
â karel
Apr 27 at 21:49
Please repost this question at Super User.
â karel
Apr 27 at 21:49
This question is cross-posted as of now (superuser.com/q/1317998/84807) and getting different answersâ¦
â Melebius
May 10 at 6:54
This question is cross-posted as of now (superuser.com/q/1317998/84807) and getting different answersâ¦
â Melebius
May 10 at 6:54
1
1
I'm voting to close this question as off-topic because others feel it is off topic, and the poster has cross-posted to superuser.com/q/1317998/84807 . I am confused that we have WSL tag, with no mention of it not being on-topic, and would like clarification if there is any.
â earthmeLon
May 12 at 19:40
I'm voting to close this question as off-topic because others feel it is off topic, and the poster has cross-posted to superuser.com/q/1317998/84807 . I am confused that we have WSL tag, with no mention of it not being on-topic, and would like clarification if there is any.
â earthmeLon
May 12 at 19:40
 |Â
show 1 more comment
1 Answer
1
active
oldest
votes
up vote
1
down vote
The dependency in futex is fixed in Skip-Ahead builds which only leaves actual hardware support.
Installing Xrdp (apt install xrdp
), starting the service (sudo service xrdp start
), and then mstsc
in the Run line with assigned port from xrdp (127.0.0.X:port#
) will likely get you running a near-full desktop experience that will include sound (you get most of everything else in Fall Creator's Update and up to start with).
So running PulseAudio is very much possible. Again the only caveat is you need to be on Skip-Ahead Insider builds. There may be ways to get sound working outside of this method but I don't know them.
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
The dependency in futex is fixed in Skip-Ahead builds which only leaves actual hardware support.
Installing Xrdp (apt install xrdp
), starting the service (sudo service xrdp start
), and then mstsc
in the Run line with assigned port from xrdp (127.0.0.X:port#
) will likely get you running a near-full desktop experience that will include sound (you get most of everything else in Fall Creator's Update and up to start with).
So running PulseAudio is very much possible. Again the only caveat is you need to be on Skip-Ahead Insider builds. There may be ways to get sound working outside of this method but I don't know them.
add a comment |Â
up vote
1
down vote
The dependency in futex is fixed in Skip-Ahead builds which only leaves actual hardware support.
Installing Xrdp (apt install xrdp
), starting the service (sudo service xrdp start
), and then mstsc
in the Run line with assigned port from xrdp (127.0.0.X:port#
) will likely get you running a near-full desktop experience that will include sound (you get most of everything else in Fall Creator's Update and up to start with).
So running PulseAudio is very much possible. Again the only caveat is you need to be on Skip-Ahead Insider builds. There may be ways to get sound working outside of this method but I don't know them.
add a comment |Â
up vote
1
down vote
up vote
1
down vote
The dependency in futex is fixed in Skip-Ahead builds which only leaves actual hardware support.
Installing Xrdp (apt install xrdp
), starting the service (sudo service xrdp start
), and then mstsc
in the Run line with assigned port from xrdp (127.0.0.X:port#
) will likely get you running a near-full desktop experience that will include sound (you get most of everything else in Fall Creator's Update and up to start with).
So running PulseAudio is very much possible. Again the only caveat is you need to be on Skip-Ahead Insider builds. There may be ways to get sound working outside of this method but I don't know them.
The dependency in futex is fixed in Skip-Ahead builds which only leaves actual hardware support.
Installing Xrdp (apt install xrdp
), starting the service (sudo service xrdp start
), and then mstsc
in the Run line with assigned port from xrdp (127.0.0.X:port#
) will likely get you running a near-full desktop experience that will include sound (you get most of everything else in Fall Creator's Update and up to start with).
So running PulseAudio is very much possible. Again the only caveat is you need to be on Skip-Ahead Insider builds. There may be ways to get sound working outside of this method but I don't know them.
edited May 10 at 6:58
Melebius
3,74841636
3,74841636
answered May 9 at 18:16
JustWhy
111
111
add a comment |Â
add a comment |Â
I have done everything you said but still not working
â Helio
Apr 26 at 20:45
1
WSL is no full Linux system and doesn't allow full hardware access. Thus it doesn't even have a kernel that would allow hardware access (via loadable modules or otherwise). It may be possible to get this to work but not how one would do it in a stand-alone Ubuntu installation, which means your question is off topic here on Ask Ubuntu. You may have more lock over on Super User.
â David Foerster
Apr 27 at 12:52
Please repost this question at Super User.
â karel
Apr 27 at 21:49
This question is cross-posted as of now (superuser.com/q/1317998/84807) and getting different answersâ¦
â Melebius
May 10 at 6:54
1
I'm voting to close this question as off-topic because others feel it is off topic, and the poster has cross-posted to superuser.com/q/1317998/84807 . I am confused that we have WSL tag, with no mention of it not being on-topic, and would like clarification if there is any.
â earthmeLon
May 12 at 19:40