Martin
Martin
I can't reproduce it with a fake module(same error, but return code 4), so I presume a condition is that a module already has to be installed, or some other...
I am not sure yet what triggered it, I just had a bunch of broken dkms builds on two machines for non-existent kernel and driver versions, I suspect some weird...
```bash # 3.0.12 [0] % sudo dkms status Error! Could not locate dkms.conf file. File: /var/lib/dkms/nvidia/550.54.14/source/dkms.conf does not exist. ``` ```bash # 3.0.13 [0] % sudo dkms status nvidia/550.54.14: broken...
The issue is `ProtectHome=yes`, systemctl edit ollama and create an override: ```ini [Service] ProtectHome= ``` This is a hack and you shouldn't do it, and you SHOULD NOT try to...
To fix this(on Arch Linux anyway), pull and update dependencies: ```terminal git checkout master; git pull && pip install -r requirements_versions.txt --prefer-binary ``` Clone the missing repo: ```terminal git clone...
@kozec Friendly ping, have you been able to sort out your GitHub trouble?
   Taking cue from similar tools and improving upon it: Add user-configurable: * `free bytes` warning and critical thresholds * `free %` warning and critical thresholds * Optional...
I had no clue, that's neat. Could have `compact`, `medium`, `big` sizes, being `1x`, `2x`, `4x`(or something akin to that) of the current size, keeping the precision without reworking much...
My opinion on the size of the use bar might change if threshold colors are implemented, so I would perhaps leave that for a later, separate issue, if that's something...
Well, we need 4 states for my suggestion, how about keeping the current orange as warning, current green as space-used below warning, and current green in shrunk, maybe dot, form...