-
Notifications
You must be signed in to change notification settings - Fork 46
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
Segmentation Faults ubuntu 22.10 x64 #142
Comments
Are you using 64bits? I had some back and forths with 22.04, have you tried to install with these changes? |
I'm using mate 64 bit and have the same issue. Installed with install-ubuntu-64.sh and added the compilation of fanStop.c. Why is /dev/ttyUSB0 not created? |
no idea... sorry |
I seem to have figured it out, due to the complications in my installation; for whatever reason |
@jzazo I'll look at using the linked patches as well, thanks for the tip! |
@TardisJacker thx, ttyUSB0 is now available. but calling: |
please check your OS platform, if you are using 64bit arch, please use pwmfancontrol64 it is a 64bit binary file, pwmfancontrol is 32bit |
try to cope pwmFanControl64 to /usr/bin/ location and then execute :
|
@yoyojacky i'm using mate 64bit
|
I've got a deskpi pro with the Ubuntu latest 22.10 image installed booting via the USB SSD adapter that came as a part of the kit. I've pulled and installed the latest version and have issues with Segmentation Fault errors without any further information. It seems that these tools are not yet ready for 22.10.
/boot/firmware/configs.txt
and that ttyUSB0 wasn't found. a test case for where the configs are may be appropriateInfo provided by:
journalctl -xeu deskpi.service
and from
systemctl status deskpi.service
I'll start looking into how the build is being done and if there are other issues in here that may have fixes via patches or changes to the systemd service portions but at this point the only hint I've got is a Segmentation Fault with return code 11 if anyone has any insight there
The text was updated successfully, but these errors were encountered: