I did try sudo modprobe ec_sys and I'm getting the failed to load message.
I think I have to make a new .conf file here /usr/lib/modprobe.d/ but I'm not sure how. I can't create anything from Dolphin file manager (I think I need admin privileges and I don't know how to do that there) and if I try it from Double Commander file manager I'm getting a bad file number error.
I'll keep reading.
Yeah, maybe I'll find a way to load this module later.
sudo modprobe ec_sys and sudo modprobe ec_sys write_support=1 don't seem to do anything because when I start MControlCenter I keep getting an error message saying that the module failed to load and all text and options are grayed out in the app.
Strange, I checked the Issues section of the GitHub project and the developer says that if the module is present there should be no errors and no user intervention needed, in other words I shouldn't have to write anything in the terminal.
: (
[deleted] This is what fedora docs say
On modern systems, kernel modules are automatically loaded by various mechanisms when the conditions call for it. However, there are occasions when it is necessary to load or unload modules manually, such as when one module is preferred over another although either could provide basic functionality, or when a module is misbehaving
Their are no dependents of ec_sys and the sudo modprobe ec_sys write_support=1
should have done it so not sure why its not loading.
Maybe check out dmesg when trying to run it see if it shows anything
Does anybody know if we have libqt5widgets5 installed with qt5 or what package has it?
Thank you Axios!
I never thought about checking if the libqt5widgets5 is installed. I always assumed it was (I'm running Solus Plasma).
The Arch wiki has a great doc on kernel modules. You've already found the kernel module you need. In order to load it automatically at every boot, take a look at "Automatic module loading", 2.1 systemd.
To pass the parameter you want for ec_sys, see the "Setting module options" section 4.2. Once you've set up the file with your module and parameters, reboot the system. Make sure it's loaded with
lsmod | grep ec_sysIf the module is returned, you know it's loaded. Once it's loaded, you should be able to run the installer for MControlCenter and run the program itself. Let us know how it goes.
Hmm..
I made a file ec_sys.conf with the contents ec_sys and I placed it in /etc/modules-load.d/.
I made a file ec_sys.conf with the contents options ec_sys write_support=1 and I placed it in /etc/modprobe.d/.
I did a reboot.
After login I opened the terminal and I did lsmod | grep ec_sys. This is the result: ec_sys 12288 0.
MControlCenter still doesn't work as intended. When I start the program I get this:
And this is how MControlCenter looks:
[deleted] Up to this point I would say you did everything you know of properly
I did notice on his github somebody posted same issue but with debian if it was you ignore.
Not sure whos at fault when you run it will call the (ec_sys and we know its loaded now) looks like issue between the two.
Just thinking
@Axios I did not post anything about this on GitHub.
edit: Hmm.. Should I ask for assistance with this issue on the MControlCenter GitHub's page? I'm thinking not because it seems to be a distribution issue but I'm asking what you think anyway.
edit 2: Just for confirmation Secure Boot is disabled on my system!
I'll take a wait and see approach then. : )
[deleted] On budgie I get same error on ec_sys
Uh uninstall mcontrol and reinstall it see what that does (from terminal sudo ./install .sh)
I got error on first install uninstalled decided to put it back and ran but no error (it doesnt read anything
I dont have msi)
If I install it fresh it runs 1st time no error---close it and try run again get ec_sys error
Uninstall it and run again no error 1st time.
See if this is happening to yours
I did, I uninstalled and then reinstalled and I'm getting the same error as before.
I'm sharing some info from gdb bt maybe someone will know more.
(gdb) bt
#0 0x00007ffff631a8bf in poll () at /usr/lib/glibc-hwcaps/x86-64-v3/libc.so.6
#1 0x00007ffff5316e57 in ??? () at /usr/lib/libglib-2.0.so.0
#2 0x00007ffff5317571 in g_main_context_iteration ()
at /usr/lib/libglib-2.0.so.0
#3 0x00007ffff6cd31cb in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
#4 0x00007ffff6c66906 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>)
() at /usr/lib/libQt5Core.so.5
#5 0x00007ffff6c6ba24 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5
#6 0x000000000040b2d7 in main ()
(gdb) Edit.
I have qt5-base installed.
eopkg sf libQt5Core.so.5
Szukanie : libQt5Core.so.5
Package qt5-base has file /usr/lib64/libQt5Core.so.5
Package qt5-base has file /usr/lib64/libQt5Core.so.5.15
Package qt5-base has file /usr/lib64/libQt5Core.so.5.15.12eopkg li | grep qt5-base
qt5-base - Cross platform application and UI framework
qt5-base-devel - Development files for qt5-baseAlright @TraceyC. Thank you for the advice! I'll do that and report back when the issue is fixed. If it will be fixed. : )
Hmm .. even though (after all this time) I still don't have a definite Best Answer I feel like I have to update this thread.
I have asked for assistance on the MControlCenter GitHub page and I've been ignored, kind of. Irrelevant though, because some time ago, after one of the weekly Solus updates I decided to restart the app and see if it runs properly and it kind of did, most modules loaded. Mode (Power Profiles) are still grayed out but Info, Battery, Fan Control and some Settings work.
Solus team, whatever you did, you did good!
Thank you! : )
fahim You can enable Secure Boot from the BIOS.