lsmod gives error: “could not get list of modules†on Debian running on WSL
Clash Royale CLAN TAG#URR8PPP
up vote
1
down vote
favorite
When I run lsmod or sudo lsmod, I get an error that says:
libkmod: ERROR ../libkmod/libkmod-module.c:1655 kmod_module_new_from_loaded: could not open /proc/modules: No such file or directory
Error: could not get list of modules: No such file or directory
I searched on a lot of forums but am unable to find a solution for this. I'm running Debian on Windows Subsystem for Linux.
I was recently also trying to edit the sysctl.conf file for the purpose of disabling ipv6. I had added the following lines:
net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1
net.ipv6.conf.lo.disable_ipv6 = 1
And when I tried sudo sysctl -p, it returned this error:
sysctl: cannot stat /proc/sys/net/ipv6/conf/all/disable_ipv6: No such file or directory
sysctl: cannot stat /proc/sys/net/ipv6/conf/default/disable_ipv6: No such file or directory
sysctl: cannot stat /proc/sys/net/ipv6/conf/lo/disable_ipv6: No such file or directory
I'm not sure if the above 2 errors are connected. I was trying to run Linux shell on Windows. Any solution to the problem?
debian kernel-modules sysctl windows-subsystem-for-linux
edited 2 hours ago
Rui F Ribeiro
34.5k1269113
asked Apr 20 at 13:29
Momo Senpai
83
add a comment |Â
up vote
1
down vote
favorite
When I run lsmod or sudo lsmod, I get an error that says:
libkmod: ERROR ../libkmod/libkmod-module.c:1655 kmod_module_new_from_loaded: could not open /proc/modules: No such file or directory
Error: could not get list of modules: No such file or directory
I searched on a lot of forums but am unable to find a solution for this. I'm running Debian on Windows Subsystem for Linux.
I was recently also trying to edit the sysctl.conf file for the purpose of disabling ipv6. I had added the following lines:
net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1
net.ipv6.conf.lo.disable_ipv6 = 1
And when I tried sudo sysctl -p, it returned this error:
sysctl: cannot stat /proc/sys/net/ipv6/conf/all/disable_ipv6: No such file or directory
sysctl: cannot stat /proc/sys/net/ipv6/conf/default/disable_ipv6: No such file or directory
sysctl: cannot stat /proc/sys/net/ipv6/conf/lo/disable_ipv6: No such file or directory
I'm not sure if the above 2 errors are connected. I was trying to run Linux shell on Windows. Any solution to the problem?
debian kernel-modules sysctl windows-subsystem-for-linux
edited 2 hours ago
Rui F Ribeiro
34.5k1269113
asked Apr 20 at 13:29
Momo Senpai
83
2
Debian on WSL is not exactly the same thing...I am not much surprised about the IPv6 tidbit.
– Rui F Ribeiro
Apr 20 at 13:35
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
When I run lsmod or sudo lsmod, I get an error that says:
libkmod: ERROR ../libkmod/libkmod-module.c:1655 kmod_module_new_from_loaded: could not open /proc/modules: No such file or directory
Error: could not get list of modules: No such file or directory
I searched on a lot of forums but am unable to find a solution for this. I'm running Debian on Windows Subsystem for Linux.
I was recently also trying to edit the sysctl.conf file for the purpose of disabling ipv6. I had added the following lines:
net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1
net.ipv6.conf.lo.disable_ipv6 = 1
And when I tried sudo sysctl -p, it returned this error:
sysctl: cannot stat /proc/sys/net/ipv6/conf/all/disable_ipv6: No such file or directory
sysctl: cannot stat /proc/sys/net/ipv6/conf/default/disable_ipv6: No such file or directory
sysctl: cannot stat /proc/sys/net/ipv6/conf/lo/disable_ipv6: No such file or directory
I'm not sure if the above 2 errors are connected. I was trying to run Linux shell on Windows. Any solution to the problem?
debian kernel-modules sysctl windows-subsystem-for-linux
edited 2 hours ago
Rui F Ribeiro
34.5k1269113
asked Apr 20 at 13:29
Momo Senpai
83
When I run lsmod or sudo lsmod, I get an error that says:
libkmod: ERROR ../libkmod/libkmod-module.c:1655 kmod_module_new_from_loaded: could not open /proc/modules: No such file or directory
Error: could not get list of modules: No such file or directory
I searched on a lot of forums but am unable to find a solution for this. I'm running Debian on Windows Subsystem for Linux.
I was recently also trying to edit the sysctl.conf file for the purpose of disabling ipv6. I had added the following lines:
net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1
net.ipv6.conf.lo.disable_ipv6 = 1
And when I tried sudo sysctl -p, it returned this error:
sysctl: cannot stat /proc/sys/net/ipv6/conf/all/disable_ipv6: No such file or directory
sysctl: cannot stat /proc/sys/net/ipv6/conf/default/disable_ipv6: No such file or directory
sysctl: cannot stat /proc/sys/net/ipv6/conf/lo/disable_ipv6: No such file or directory
I'm not sure if the above 2 errors are connected. I was trying to run Linux shell on Windows. Any solution to the problem?
debian kernel-modules sysctl windows-subsystem-for-linux
edited 2 hours ago
Rui F Ribeiro
34.5k1269113
asked Apr 20 at 13:29
Momo Senpai
83
edited 2 hours ago
Rui F Ribeiro
34.5k1269113
edited 2 hours ago
Rui F Ribeiro
34.5k1269113
edited 2 hours ago
Rui F Ribeiro
34.5k1269113
34.5k1269113
asked Apr 20 at 13:29
Momo Senpai
83
asked Apr 20 at 13:29
Momo Senpai
83
asked Apr 20 at 13:29
Momo Senpai
83
83
2
Debian on WSL is not exactly the same thing...I am not much surprised about the IPv6 tidbit.
– Rui F Ribeiro
Apr 20 at 13:35
add a comment |Â
2
Debian on WSL is not exactly the same thing...I am not much surprised about the IPv6 tidbit.
– Rui F Ribeiro
Apr 20 at 13:35
2
2
Debian on WSL is not exactly the same thing...I am not much surprised about the IPv6 tidbit.
– Rui F Ribeiro
Apr 20 at 13:35
Debian on WSL is not exactly the same thing...I am not much surprised about the IPv6 tidbit.
– Rui F Ribeiro
Apr 20 at 13:35
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
4
down vote
accepted
In both cases, you’re trying to interact with the kernel. Any Linux environment running on WSL isn’t running a Linux kernel, it’s running on the Windows kernel; so anything tied to the Linux kernel (including modules and system controls) won’t work.
In the IPv6 case, you need to configure the network using Windows’ tools.
answered Apr 20 at 13:54
Stephen Kitt
140k22303364
Is there any work around to this? And could there be instances where I would need to probably interact with the kernel in order to perform some important task? Is there a workaround in that case?
– Momo Senpai
Apr 20 at 14:17
The workaround is to run a full Linux environment, e.g. in a VM. There are some things which you can only do with a Linux kernel, just as there are others you can only do with Windows. You need to use the appropriate tool for your requirements; WSL gives you a Linux user-space on Windows, but it isn’t Linux.
– Stephen Kitt
Apr 20 at 14:30
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
4
down vote
accepted
In both cases, you’re trying to interact with the kernel. Any Linux environment running on WSL isn’t running a Linux kernel, it’s running on the Windows kernel; so anything tied to the Linux kernel (including modules and system controls) won’t work.
In the IPv6 case, you need to configure the network using Windows’ tools.
answered Apr 20 at 13:54
Stephen Kitt
140k22303364
Is there any work around to this? And could there be instances where I would need to probably interact with the kernel in order to perform some important task? Is there a workaround in that case?
– Momo Senpai
Apr 20 at 14:17
The workaround is to run a full Linux environment, e.g. in a VM. There are some things which you can only do with a Linux kernel, just as there are others you can only do with Windows. You need to use the appropriate tool for your requirements; WSL gives you a Linux user-space on Windows, but it isn’t Linux.
– Stephen Kitt
Apr 20 at 14:30
add a comment |Â
up vote
4
down vote
accepted
In both cases, you’re trying to interact with the kernel. Any Linux environment running on WSL isn’t running a Linux kernel, it’s running on the Windows kernel; so anything tied to the Linux kernel (including modules and system controls) won’t work.
In the IPv6 case, you need to configure the network using Windows’ tools.
answered Apr 20 at 13:54
Stephen Kitt
140k22303364
Is there any work around to this? And could there be instances where I would need to probably interact with the kernel in order to perform some important task? Is there a workaround in that case?
– Momo Senpai
Apr 20 at 14:17
The workaround is to run a full Linux environment, e.g. in a VM. There are some things which you can only do with a Linux kernel, just as there are others you can only do with Windows. You need to use the appropriate tool for your requirements; WSL gives you a Linux user-space on Windows, but it isn’t Linux.
– Stephen Kitt
Apr 20 at 14:30
add a comment |Â
up vote
4
down vote
accepted
up vote
4
down vote
accepted
In both cases, you’re trying to interact with the kernel. Any Linux environment running on WSL isn’t running a Linux kernel, it’s running on the Windows kernel; so anything tied to the Linux kernel (including modules and system controls) won’t work.
In the IPv6 case, you need to configure the network using Windows’ tools.
answered Apr 20 at 13:54
Stephen Kitt
140k22303364
In both cases, you’re trying to interact with the kernel. Any Linux environment running on WSL isn’t running a Linux kernel, it’s running on the Windows kernel; so anything tied to the Linux kernel (including modules and system controls) won’t work.
In the IPv6 case, you need to configure the network using Windows’ tools.
answered Apr 20 at 13:54
Stephen Kitt
140k22303364
answered Apr 20 at 13:54
Stephen Kitt
140k22303364
answered Apr 20 at 13:54
Stephen Kitt
140k22303364
answered Apr 20 at 13:54
Stephen Kitt
140k22303364
140k22303364
Is there any work around to this? And could there be instances where I would need to probably interact with the kernel in order to perform some important task? Is there a workaround in that case?
– Momo Senpai
Apr 20 at 14:17
The workaround is to run a full Linux environment, e.g. in a VM. There are some things which you can only do with a Linux kernel, just as there are others you can only do with Windows. You need to use the appropriate tool for your requirements; WSL gives you a Linux user-space on Windows, but it isn’t Linux.
– Stephen Kitt
Apr 20 at 14:30
add a comment |Â
Is there any work around to this? And could there be instances where I would need to probably interact with the kernel in order to perform some important task? Is there a workaround in that case?
– Momo Senpai
Apr 20 at 14:17
The workaround is to run a full Linux environment, e.g. in a VM. There are some things which you can only do with a Linux kernel, just as there are others you can only do with Windows. You need to use the appropriate tool for your requirements; WSL gives you a Linux user-space on Windows, but it isn’t Linux.
– Stephen Kitt
Apr 20 at 14:30
Is there any work around to this? And could there be instances where I would need to probably interact with the kernel in order to perform some important task? Is there a workaround in that case?
– Momo Senpai
Apr 20 at 14:17
Is there any work around to this? And could there be instances where I would need to probably interact with the kernel in order to perform some important task? Is there a workaround in that case?
– Momo Senpai
Apr 20 at 14:17
The workaround is to run a full Linux environment, e.g. in a VM. There are some things which you can only do with a Linux kernel, just as there are others you can only do with Windows. You need to use the appropriate tool for your requirements; WSL gives you a Linux user-space on Windows, but it isn’t Linux.
– Stephen Kitt
Apr 20 at 14:30
The workaround is to run a full Linux environment, e.g. in a VM. There are some things which you can only do with a Linux kernel, just as there are others you can only do with Windows. You need to use the appropriate tool for your requirements; WSL gives you a Linux user-space on Windows, but it isn’t Linux.
– Stephen Kitt
Apr 20 at 14:30
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f438940%2flsmod-gives-error-could-not-get-list-of-modules-on-debian-running-on-wsl%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
2
Debian on WSL is not exactly the same thing...I am not much surprised about the IPv6 tidbit.
– Rui F Ribeiro
Apr 20 at 13:35