this post was submitted on 21 Sep 2024
20 points (95.5% liked)

linux4noobs

1349 readers
1 users here now

linux4noobs


Noob Friendly, Expert Enabling

Whether you're a seasoned pro or the noobiest of noobs, you've found the right place for Linux support and information. With a dedication to supporting free and open source software, this community aims to ensure Linux fits your needs and works for you. From troubleshooting to tutorials, practical tips, news and more, all aspects of Linux are warmly welcomed. Join a community of like-minded enthusiasts and professionals driving Linux's ongoing evolution.


Seeking Support?

Community Rules

founded 1 year ago
MODERATORS
 

Since I installed the official fan script, and it did nothing, I kept searching. I found a second user made script for controlling the fan, however I'm too inexperienced with linux to even understand what's being asked.

Full page is listed at

https://gitlab.com/DarkElvenAngel/argononed

How To Install Firstly you need to have a build environment setup, that includes the following gcc dtc git bash linux-headers make git NOTE : The package names will be different depending on your OS so I've only given their binary names. Refer to your distribution for what you need to install. I've tried to make the installer as simple as possible. After cloning this repo simply run ./install You may need to reboot for full functionality.

What does he mean "build the environment setup"? And how do I clone a repo?

I'm trying this out on raspberry pi OS 64 bit, which is listed as compatible. If I can learn HOW to do this, I'll do it on my main SD card OS, TwisterOS, which is also listed as compatible.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 8 points 1 month ago (1 children)

They are saying you need to know the distro package names on the command line. I don't have a Rπ handy to check the packages for you. Use sudo apt-get install gcc dtc git bash linux-headers make git then see what fails. Whatever fails is likely just due to the package name being different in aptitude. The way you find the package name in Debian or any distro is a combination of searching different places and/or looking up the host repo on GitHub/GitLab/etc. Often they will list the names of the package in different distros.

Note that, anything Debian based may be old and outdated in Aptitude packages. You can still use it just the same. It is old by design. That is what Stable distro means. If you find documentation online or you need some newer feature, you must install stuff manually. It is probably a non issue for you at this stage, but just be aware. If you see info about a ppa this is how you add the more recent packages to aptitude so that it overrides the older stable packages.

[–] [email protected] 2 points 1 month ago (1 children)

Ok, I did this in terminal.

bighat@raspberrypi:~ $ sudo apt-get install gcc dtc git bash linux-headers
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Note, selecting 'raspberrypi-kernel-headers' instead of 'linux-headers'
E: Unable to locate package dtc
bighat@raspberrypi:~ $ 

and then searched "raspberry pi os dtc package" and got this page

https://snapcraft.io/install/device-tree-compiler/raspbian

Is this what I want?

[–] [email protected] 1 points 1 month ago

Sounds right. The thing to do is try it and see. Most Linux packages like this are tiny. Just get in the habit of installing, trying, uninstalling what doesn't work. Take on a more scientific mindset. The Doz attempts to make a person act helpless like a dependent toddler that needs their hand held and to pay for the right to hold that hand. This is manipulative nonsense. Linux has thousands of people learning and solving problems in hundreds of ways. Just find some people doing it in a way that works for you too. Any issue likely has dozens of paths to a solution from different angles. Learn to keep looking for stuff even after you find one thing. Just be open to new stuff. Also be weary of older user based solutions that are not kept up to date. These often do not work.