Linux
Welcome to c/linux!
Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!
Rules:
-
Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
-
Be respectful: Treat fellow community members with respect and courtesy.
-
Quality over quantity: Share informative and thought-provoking content.
-
No spam or self-promotion: Avoid excessive self-promotion or spamming.
-
No NSFW adult content
-
Follow general lemmy guidelines.
view the rest of the comments
If that's an every time thing, I'd be tempted to compile myself a very simple C program that uses
systemorexeclto run/usr/sbin/iwconfigand my preferred parameters. Then I'd change the owner to root, give it the SUID bit and then put a call to it somewhere in my startup.(As to where on the system I'd put it,
/usr/local/sbinis probably the best choice. Where/when in the startup is slightly more difficult. On a single user machine, it might be OK, or even work best, in the GUI's Startup Applications, rather than anywhere like/etc/init.d/)If I was really curious, I'd go digging to find anything else that might already be doing that and if not, where the default settings are kept and see if they can be changed, making the above unnecessary.
For the sake of this comment I had a quick dig around and didn't find anything obvious on my own machine, but then, this isn't a Mac nor do I use wireless, which might be hampering my efforts.
I was tempted too. That's why I did that, and bricked my laptop, and had to do a fresh install.
It wasn't the best choice.
Not there.
I am no longer curious. I can just type this command every time, no big deal. As for the computer, it's fine for light development work and surfing the net, as long as I don't need sound. I might use it for torrenting, it works for that OK.
Mac is notoriously difficult to install Linux on, even if it's Linux Mint. Not sure what I did wrong, but other people have the same model and I've seen them get everything to work including the touch bar. I wish they'd share their documentation.
Well shoot. Now I want to know why that didn't work. But I don't fancy having to work my system back to useable if it refuses to boot.
I mean, it booted… into a black screen
Seems like removing the file from
/home/YOURUSER/.config/autostart/ought to have undone the problem. Booting from external media of course, so as to be able to get to it, which you have to do anyway to reinstall.I realise this is long after the fact.
Having something just sitting there in
/usr/local/sbinshouldn't have any effect at all, so I can't imagine that was the issue, so calling it must be.And the only thing I can think of is if there was a permissions problem and Cinnamon choked because the
exec-er refused to run.Yeah a permissions problem causing an error is a likely culprit, when I try again I will take more detailed notes and actually put them in a safe place
Is it T2 Mac? Did you use T2Linux?
T2 started in 2018. The A1706/7 were only 2016-2017.
No, it is not a T2 Mac and I didn’t use T2 Linux. However I am thinking of trying t2 just to see if it works better for some reason
At least check the T2Linux wiki. On T2 Macs, certain modules needs to be loaded in specific order for the TouchBar to work. https://wiki.t2linux.org/guides/postinstall/
yes this is my next try, I'm just burnt out on it for now