this post was submitted on 24 Dec 2023
517 points (85.9% liked)

linuxmemes

21160 readers
1532 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

  • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] [email protected] 1 points 10 months ago (1 children)

    Try frimware binary blob packages, those usually have whatever to make the thingie work with the Linux kernel.

    [–] [email protected] 1 points 10 months ago (1 children)

    I’m not sure what do you mean by firmware blob but Ive done the following:

    1. Added non-free to the sources file.
    2. Installed Surface-linux lib.

    There is a guide in surface-linux library which requires compiling something with CMAKE. I’m not comfortable at the moment to do it since I don’t have the time to fix it if something went wrong.

    I couldn’t find a good touch gui for debian so ill give ubuntu a shot.

    [–] [email protected] 1 points 10 months ago

    In the non-free repo, there should be something like firmware-broadcom, firmware-amd, firmware-intel, etc. Those are binary blobs, closed source firmware (supplied by the manufacturer) that is loaded in the device in order to make it work with the linux kernel. See the make and model od the device via lspci or lsusb (depends on how the device is connected to the PC) and see the make and model. If it's, let's say, Broadcom, install the Broadcom firmware package and restart the rig.

    Regarding cmake, you could use BTRFS to revert everything back to the way it was, just make a restore point before doing make install.