Clevo Fan Control for Linux

Discussion in 'Sager and Clevo' started by Dennismungai, Oct 31, 2018.

  1. Dennismungai

    Dennismungai Notebook Deity

    Reputations:
    526
    Messages:
    746
    Likes Received:
    646
    Trophy Points:
    106
    Great success, glad it works for you.
     
  2. banskt

    banskt Notebook Enthusiast

    Reputations:
    0
    Messages:
    11
    Likes Received:
    1
    Trophy Points:
    6
    Thank you and props to Tuxedo for this wonderful piece of software. I made some minor changes in the source code and managed to build and run it on a Clevo P651SE bought from CEG-Hardcorecustom running the premamod BIOS. Basically, I had to bypass the check for vendor name and board / BIOS model before compiling the source code. I never had such a silent Clevo before.

    Thanks again!
     
  3. Dennismungai

    Dennismungai Notebook Deity

    Reputations:
    526
    Messages:
    746
    Likes Received:
    646
    Trophy Points:
    106
    You may want to create a pull request for that, as other Prema-mod BIOS systems may be affected by the whitelist that your patch bypasses.
     
  4. banskt

    banskt Notebook Enthusiast

    Reputations:
    0
    Messages:
    11
    Likes Received:
    1
    Trophy Points:
    6
    I do not think that is a good idea because the existing source code purposefully checks for computers from Tuxedo and their motherboard. Bypassing that is vulnerable. It is a very simple change but very risky. I would be happy to help if anyone is interested.

    See these 3 functions: isTuxedoDevice(), getDmiModelVendor() and getDmiModelName() in src/common/system.ts (https://github.com/tuxedocomputers/tuxedo-fan-control/blob/master/src/common/system.ts)
     
  5. Dennismungai

    Dennismungai Notebook Deity

    Reputations:
    526
    Messages:
    746
    Likes Received:
    646
    Trophy Points:
    106
    It's also documented.
     
  6. Dennismungai

    Dennismungai Notebook Deity

    Reputations:
    526
    Messages:
    746
    Likes Received:
    646
    Trophy Points:
    106
    Related, I have opened up an issue on the same which suggests a saner approach to this vendor check routine.
     
Loading...

Share This Page