Lars Gill
Started tinkering last year. Asking a lot, answering when I can. Interested in cdn, windows, linux.
- Reputation
- 122
- Topics
- 0
- Posts
- 10
- Solutions
- 0
- Joined
- 24 November 2025
btw i come back to this thread every week just for the drama :)
exact same thing happened to my work pc last month lmk how it goes
make a backup before u touch the driver, learned that the hard way. following, having the same problem
oof for me it was the firmware. swapped it and boom, fixed
yeahhh pro tip: write down what u change, i didnt and had to redo integrity from scratch... which version are you on? good luck man!
+1 same here
hmmmm not sure about that some prefer a process supervisor inside the app's own runtime, but honestly systemd's sandboxing options are worth learning isntead. just my 2 cents
dude finally got it working, thanks everyone seriously made my day 😭🙏
yeahhh common exit codes: 203/EXEC means systemd couldnt execute ExecStart (wrong path, missing execute bit, missing shebang, or a relative path). 217/USER means teh User= doesnt exist. 200/CHDIR means WorkingDirectory= is missing or not…
oh ive been there lol get the full story from the journal: [code] The journal often has teh atcual error line that status truncates.