@Overdraft - eviltoast
  • 0 Posts
  • 5 Comments
Joined 11 months ago
Cake day: December 20th, 2023
  • Overdraft@lemmy.mltoLinux Gaming@lemmy.world•Options for Lian Li Fan ControlEnglish
    1·
    3 months ago

    I’m not familiar with Nobara, but I can at least show how I would install pyUSB for use in Debian:

    If you follow the instructions exactly as in the readme, it will error:

    $ pip install pyusb
error: externally-managed-environment

× This environment is externally managed
╰─> To install Python packages system-wide, try apt install
    python3-xyz, where xyz is the package you are trying to
    install.
    
    If you wish to install a non-Debian-packaged Python package,
    create a virtual environment using python3 -m venv path/to/venv.
    Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make
    sure you have python3-full installed.
    
    If you wish to install a non-Debian packaged Python application,
    it may be easiest to use pipx install xyz, which will manage a
    virtual environment for you. Make sure you have pipx installed.
    
    See /usr/share/doc/python3.11/README.venv for more information.

note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.
hint: See PEP 668 for the detailed specification.

    Instead, I would create a virtual environment (I’m using virtualenv instead of venv)

    $ virtualenv unihub_test

    Then activate the environment and run the install with pip

    $ source ~/unihub_test/bin/activate
(unihub_test) $ pip install pyusb
Collecting pyusb
  Using cached pyusb-1.2.1-py3-none-any.whl.metadata (2.2 kB)
Using cached pyusb-1.2.1-py3-none-any.whl (58 kB)
Installing collected packages: pyusb
Successfully installed pyusb-1.2.1

(unihub_test) $ python3
>>> import usb #this should not error
>>> exit()
(unihub_test) $ deactivate
$

    Without the actual hub, that’s as far as I can go I think - but maybe this will help give you some options and documentation to explore!

  • Overdraft@lemmy.mltoLinux Gaming@lemmy.world•Options for Lian Li Fan ControlEnglish
    1·
    3 months ago

    Geeze, that’s extremely frustrating… they really switched up the headaches between v1 and v2. I’m sorry I couldn’t be more help! Hopefully you can find a software solution to get it going.

    I don’t mean to repeat troubleshooting you’ve already done with the python script, apologies in advance if this is stuff you’ve already done. If it’s erroring immediately, you may want to double check that you have pyUSB in place and UDEV rules to get access to the device if you’re not running the script as root.

    edit: You may also need to check that your Vendor ID and Product ID match what the script was written for, given that there seem to be some different iterations of Lian Li’s hardware just in general.

  • Overdraft@lemmy.mltoLinux Gaming@lemmy.world•Options for Lian Li Fan ControlEnglish
    1·
    3 months ago

    Sorry for the delayed response - I saw what you meant in the v2 manual about the proprietary connector and thought I would just leave it at that, but I had another thought.

    It sounds like you do have some access to Windows/L-Connect, have you switched the fan profiles to sync with the MB? This should stick after a shutdown and not need to be re-set, you will lose the ability to create fan curves in L-Connect:

    Also, are you connecting the UNI HUB directly to the MB pins, or is it running through a splitter or extender? It looks like the UNI HUB v2 does have a sense pin (the v1 does NOT, that’s the reason for the workaround I have to use); some additional extenders and splitters are missing the sense pin, so even though you can control the fan speed from BIOS, you can’t see the RPMs in BIOS so it might look like it’s not recognized.