Some middle-aged guy on the Internet. Seen a lot of it, occasionally regurgitating it, trying to be amusing and informative.

Lurked Digg until v4. Commented on Reddit (same username) until it went full Musk.

Was on kbin.social (dying/dead) and kbin.run (mysteriously vanished). Now here on fedia.io.

Really hoping he hasn’t brought the jinx with him.

Other Adjectives: Neurodivergent; Nerd; Broken; British; Ally; Leftish

  • 2 Posts
  • 354 Comments
Joined 2 years ago
cake
Cake day: August 13th, 2024

help-circle


  • Until I saw this, I assumed it must be a problem with newer Nvidia cards because I almost never had a problem with my ancient GTS450 on Mint and LMDE.

    And that “almost” is because of the one time something got added to the kernel that didn’t play nice with the OEM driver. Later kernels didn’t have the same problem.

    All that said, I’m team AMD again and am likely to stay that way. The old computer was built during a very brief window about 15 years ago where it wasn’t uncool to buy Intel CPUs and NVidia graphics and, I assume, AMD were having problems.

    The PC before that was AMD/ATI, hence “again” now.






  • 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/sbin shouldn’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.



  • If that’s an every time thing, I’d be tempted to compile myself a very simple C program that uses system or execl to run /usr/sbin/iwconfig and 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/sbin is 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.