Start the linuxa or alinux project and off you trot. Find a better name than I did here and you'll be fine.

Please do a little research before trying random stuff. After checking to see if you are actually using the iwlwifi module, why not find out a bit about whether the mentioned param. is available to you and what it does:

Am I using the module. If the output from this is blank, then no:

$ lsmod | grep iwlwifi
iwlwifi               622592  1 iwlmvm
cfg80211             1331200  3 iwlmvm,iwlwifi,mac80211

Also verify with lspci -k as above:

$ lspci -k | grep iwlwifi -A2 -B2
        DeviceName: WLAN
        Subsystem: Intel Corporation Raptor Lake PCH CNVi WiFi
        Kernel driver in use: iwlwifi
        Kernel modules: iwlwifi
00:15.0 Serial bus controller: Intel Corporation Alder Lake PCH Serial IO I2C Controller #0 (rev 01)
        Subsystem: Hewlett-Packard Company Alder Lake PCH Serial IO I2C Controller

# modinfo iwlwifi
   ...
parm:           swcrypto:using crypto in software (default 0 [hardware]) (int)
parm:           11n_disable:disable 11n functionality, bitmap: 1: full, 2: disable agg TX, 4: disable agg RX, 8 enable agg TX (uint)
parm:           amsdu_size:amsdu size 0: 12K for multi Rx queue devices, 2K for AX210 devices, 4K for other devices 1:4K 2:8K 3:12K (16K buffers) 4: 2K (default 0) (int)
parm:           fw_restart:restart firmware in case of error (default true) (bool)
parm:           nvm_file:NVM file name (charp)
parm:           uapsd_disable:disable U-APSD functionality bitmap 1: BSS 2: P2P Client (default: 3) (uint)
parm:           enable_ini:0:disable, 1-15:FW_DBG_PRESET Values, 16:enabled without preset value defined,Debug INI TLV FW debug infrastructure (default: 16) (uint)
parm:           bt_coex_active:enable wifi/bt co-exist (default: enable) (bool)
parm:           led_mode:0=system default, 1=On(RF On)/Off(RF Off), 2=blinking, 3=Off (default: 0) (int)
parm:           power_save:enable WiFi power management (default: disable) (bool)
parm:           power_level:default power save level (range from 1 - 5, default: 1) (int)
parm:           disable_11ac:Disable VHT capabilities (default: false) (bool)
parm:           remove_when_gone:Remove dev from PCIe bus if it is deemed inaccessible (default: false) (bool)
parm:           disable_11ax:Disable HE capabilities (default: false) (bool)
parm:           disable_11be:Disable EHT capabilities (default: false) (bool)

sysfs is a pseudo filesystem with lots of info in it. cat the files here:

$ ls -l /sys/module/iwlwifi/parameters/

... to see what your current values are set at. You can install sysfstools and run this for a neat report:

$ systool -vm iwlwifi
Module = "iwlwifi"

  Attributes:
     ...
  Parameters:
    11n_disable         = "0"
    amsdu_size          = "0"
    bt_coex_active      = "Y"
    disable_11ac        = "N"
    disable_11ax        = "N"
    disable_11be        = "N"
    enable_ini          = "16"
    fw_restart          = "Y"
    led_mode            = "0"
    nvm_file            = "(null)"
    power_level         = "0"
    power_save          = "N"
    remove_when_gone    = "N"
    swcrypto            = "0"
    uapsd_disable       = "3"

Mint has managed to become a meme and that's no bad thing, per se, but it can look a bit odd to the cognoscenti. Anyone doing research by search engine looking to escape MS towards Linux will find Mint as the outstanding suggestion.

That's just the way it is at the moment: Mint is the gateway to Linux. Embrace that fact and you are on the way to enlightenment.

I am the MD of a small IT company in the UK. I've run Gentoo and then Arch on my daily drivers for around 25 years. The rest of my company insist on Windows or Apples. Obviously, I was never going to entice anyone over with Gentoo or even Arch, although my wife rocks Arch on her laptop but I manage that and she doesn't care what I call Facebook and email.

We are now at an inflection point - MS are shuffling everyone over to Azure with increasing desperation: Outlook/Exchange and MS Office will be severely off prem. by around 2026. So if you are going to move towards the light, now is a good time to get your arse in gear.

I now have Kubuntu on my work desktop and laptop. You get secure boot out of the box, along with full disc encryption and you can also run a full endpoint suite (ESET for us). That scores a series of ticks on the Cyber Essentials Plus accreditation and that is required in my world.

AD etc: CID - https://cid-doc.github.io/ pretty nifty. I've defined the equivalent of Windows drive letters as mounts under home, eg: ~/H: - that works really well.

Email - Gnome Evolution with EWS. Just works. Used it for years.

Office - Libre Office. I used to teach people how to use spreadsheets, word processors, databases and so on. LO is fine. Anyone attempting to tell me that LO can't deal with ... something ... often gets ... educated. All software has bugs - fine, we can deal with that. I recently showed someone how decimal alignment works. I also had to explain that it is standard and not a feature of LO.

For my company the year of Linux on the desktop has to be 2025 (with options on 2026). I have two employees who insist on it now and I have to cobble together something that will do the trick. I get one attempt at it and I've been doing application integration and systems and all that stuff for quite a while.

Linux has so much to give as an ecosystem but we do need to tick some boxes to go properly mainstream on the desktop and that needs to happen sooner rather than later.

I do IT security for a living. It is quite complicated but not unrealistic for you to DIY.

Do a risk assessment first off - how important is your data to you and a hostile someone else? Outputs from the risk assessment might be fixing up backups first. Think about which data might be attractive to someone else and what you do not want to lose. Your photos are probably irreplaceable and your password spreadsheet should probably be a Keepass database. This is personal stuff, work out what is important.

After you've thought about what is important, then you start to look at technologies.

Decide how you need to access your data, when off site. I'll give you a clue: VPN always until you feel proficient to expose your services directly on the internet. IPSEC or OpenVPN or whatevs.

After sorting all that out, why not look into monitoring?

Errm, Wireshark. Please bear with me.

Wireshark is a shining example of an open source project completely and utterly crapping on the closed source competition. As a result we all benefit. I recall spending a lot of someone else's money on buying a sort of ruggedized laptop with two ethernet ports to do the job back in the day.

Nowdays, I can run up a tcpdump session on a firewall remotely with some carefully chosen timings and filters and download it to my PC and analyse it with Wireshark.

OK, all so convenient but is it any use?

Say you have a VoIP issue of some sort. The PCAP from tcpdump that you pass to Wireshark can analyse it to the nth degree. Wireshark knows all about SIP and RTP (and IAX) and you can even play back the voice streams or have them graphed so you can see what is wrong or whatever. That's just VoIP, it has loads of other dissectors and decorators built in.

So what?

The UK (for example) will be dispensing with boring old, but reliable, POTS (Plain Old Telephony System) by 2025. Our entire copper telephony and things like RedCare (defunct soon) will go away.

We are swapping out circuit switching for packet switching. To be fair, a lot of the backend is already TCP/UDP/IP that is shielded away from us proles. When SoGEA (Single Order Generic Ethernet Access) really kicks in then the old school electric end to end connection will be lost in favour of packet switching, which never fails (honest guv).

If you are an IT bod of any sort, you really should be conversant with Wireshark.

I use Linux (Arch actually) as my daily driver - I'm the MD of a small IT business in the UK. I have at least one employee who is asking me to create a Linux standard deployment to replace Windows because they don't like it anymore - W11 is quite divisive.

For a corp laptop/desktop you might need Exchange email - so that might be Evolution with EWS. You'll want "drive letters" - Samba, Winbind and perhaps autofs. You'll need an office suite - Libre Office works fine. There's this too: https://cid-doc.github.io/ for more MS integration - if that's your bag.

I often see people getting whizzed up about whether LO can compete with MSO. I wrote a finite (yes, finite) capacity scheduler for a factory in MS Excel, back in 1995/6 - it involved a lot of VBA and a mass of checksums etc. I used to teach word processing and DTP (Quark, Word, Ventura and others). LO cuts it. It gets on my nerves when I'm told that LO isn't capable by someone who is incapable of fixing a widow or orphan or for whom leading and kerning are incomprehensible.

Did anyone really think that making UEFI systems the equivalent of a mini OS was a good idea

UEFI and Secure Boot were pushed forcibly by MS. That's why FAT32 is the ESP filesystem.

If I had to guess, a brief was drafted at MS to improve on BIOS, which is pretty shit, it has to be said. It was probably engineering led and not an embrace, extinguish thing. A budget and dev team and a crack team of lawyers would have been whistled up and given a couple of years to deliver. The other usual suspects (Intel and co) would be strong armed in to take whatever was produced and off we trot. No doubt the best and brightest would have been employed but they only had a couple of years and they were only a few people.

UEFI and its flaws are testament to the sheer arrogance of a huge company that thinks it can put a man on the moon with a Clapham omnibus style budget and approach. Management identify a snag and say "fiat" (let it be). Well it was and is and it has a few problems.

The fundamental problem with UEFI is it was largely designed by one team. The wikipedia page: https://en.wikipedia.org/wiki/UEFI is hilarious in describing it as open. Yes it is open ... per se ... provided you decide that FAT32 (patent encumbered) is a suitable file system for the foundations of an open standard.

I love open, me.

Perhaps but if you are doing a show and tell, why not do the full tell?

I can remember when Google didn't exist and Altavista was the cool kid, or when the www didn't exist and gopher and WAIS were the tools of choice. ... and I can go much further back.

My real point is: If you are going to show a bit of ankle, and it is yours, make sure that everyone realises it is your ankle. If it isn't your ankle, then tell us whose it is. It's not fair asking people to search for pictures of ankles and then try to guess which one you have posted about.

Me too. I just ran time tree across my home directory a few times. Native console (ie C-A-F3) - 54 seconds, Konsole - eight seconds.

Waveterm is still installing (Arch AUR). The fan has a Gentooesque sound to it as a suspiciously complicated thing gets built. Oh God ... electon ... terminal shaking ... golang ... fans whining ... lap melting ..... the Old Ones are stirring.

The deps for this thing are many. " I watched Firefox builds on Gentoo glitter in the dark near the Tannhäuser Gate". OK, its now arrived and my laptop case is making ping noises as it cools.

It takes 10 seconds or so to start up. Look pretty. Accept license agreement (wtf). Now what? Hmm lets try typing in that box. OK. time tree. Go back to Lemmy to type the last two paras of this comment, get bored and uninstall waveterm.

No. Those tools are tried and well tested. Yes there may still be bugs lurking but simply rewriting in Rust does not guarantee safety. I do hope that this: https://doc.rust-lang.org/book/ch19-01-unsafe-rust.html doesn't get used in that repo.

That said, I'll take a look in say five years and see how they are getting on.

I've spent over 25 years with Linux. With multiple distros and a lot of that with Gentoo and Arch. At work I specify Ubuntu or Debian, for simplicity and stability. I always used to use the minimal Ubuntu, because it was tiny with no frills. For quite a few years I managed a fleet of Gentoo systems across multiple customers - with Puppet. Those have quietly gone away. I've dallied with SuSE (all varieties), Mandrake, Mandriva, RedHat, Slackware, Yggdrassil and more.

Arch is surprisingly stable and being a rolling job there are no big jumps. When I replace one of our laptops, I simply clone the old one to it and crack on. I used to do the same with Gentoo - my Gentoo laptops went from an OpenRC job with dual Nokia N95 ppp connections around 2007 to through to around 2018 with systemd and decent wifi when I switched to Arch to allow the burns on my lap to heal. I still have a Gentoo VM running (amongst friends) on the esxi in my attic.

It was installed in 2006 according to some of the kernel config files. I left it for way too long and had to use git to make Portage advance forwards in time and fix around a decade of neglect. It would have been too easy to wipe and start again. It took about a fortnight to sort out. At one point I even fixed an issue following a forum post I made myself years ago.

Anyway, Arch is pretty stable.

My wife uses Arch (actually). She calls it the internet, when she really means Facebook. She knows it isn't Apple but it gets a bit vague after that!

The last time I had to fire up the Mesh Central client to sort something out on her desktop from work was around three months ago. Every couple of weeks I ssh into it, update it and schedule a reboot for 03:00.