People love to complain about CMake, often with valid complaints as well. But it - to this day - remains the only build system where I’ll actually trust a project when they say they are cross-platform.
Being the Windows maintainer for OpenMW, it used to be absolute hell back a decade and half ago when an indirect dependency changed - and used something like SCons or Premake while claiming to be “cross-platform”, used to be that I had to write my own build solutions for Windows since it was all hardcoded against Linux paths and libraries.
CMake might not be the coolest, most hip, build system, but it delivers on actually letting you build your software regardless of platform. So it remains my go-to for whenever I need to actually build something that’s supposed to be used.
For personal things I still often hack together a couple of Makefiles though, it’s just a lot faster to do.
Not really, WSL seems like it was mainly supposed to stop people leaping ship to be able to develop Node without the horribly painful Windows JS experience. And wouldn’t you know it, Microsoft has been making their own JavaScript language in Typescript.
CMake has been around forever and is flexible enough to build really complex software. You just need to pull out enough hair when you want it to do something.
If you’re compiling something huge like Chrome, having a separate compilation stage for the build files makes sense. For a normal sized project it’s overkill.
I haven’t had any recent issue with those either. Just make sure both the nvidia driver and the kernel are from your distros repository, and you always update them both at the same time.
My new laptop has a nvidia card in it. One time it stopped working after a update so I downgraded the drivers so I can wait entail the next update they do work. Besides that it have worked great. I am on fedora so rpmfusion is where the drivers are from.
I never have. Just thinking about WiFi and Bluetooth drivers on random laptops still puts me into a full flashback state. (My first experience was back in 2002, I think?)
However, getting all of that stuff working was the best learning experience I ever had. At the time, I was just learning about IT security and WiFi pcap was all the rage back then.
I never have. Just thinking about WiFi and Bluetooth drivers on random laptops still puts me into a full flashback state. (My first experience was back in 2002, I think?)
Same, flashbacks to being in college trying to get Wi-Fi working in Fedora on my laptop and then struggling to get it to work with my uni’s new Wi-Fi system. Frustrating, but a great learning experience as you said.
Even a decade ago it usually meant ticking a box that you also allowed nonfree drivers.
Even Debian allowed you to download the specific nonfree driver you needed and add it (without Internet) at imaging so post install you could connect with wifi and not just Ethernet.
It’s come a long way. But doesn’t anyone else remember when windows did not have drivers and you’d constantly be confronted with “have disk”?
I mean, the amount of drivers for old hardware I still have saved… Because before win10 nothing would reliability always fetch the driver you need from the net…
Ticking the non-free driver box was child’s play. As late as like 2012 I remember needing to download NDISwrapper so I could make the windows drivers work through a compatibility layer
I recall jaunty jackalope being the Ubuntu version that became my full time os. It was that version that my IBM x31 had everything taken care of on install with the third party drivers checked. I feel like the LTS version following that was where you could buy a generation previous of any hardware and it’d work without much fuss.
This reminds me of the big USB drive of drivers that we had at a PC repair shop. When Windows 7 failed to find drivers, we’d stick that in and give it a scan.
The nvidia driver has had this bug for a year now, still unfixed. Games will randomly crash with an Xid 109 error in dmesg. Some people (including myself) are unable to play games like Cyberpunk, Resident Evil 2-3-4-7-8 and Metro Exodus. And it’s not linked to proton either, it sometimes also crashes xorg itself, forcing a reboot. I’m starting to think nvidia will never bother fixing it.
This isn’t a Linux compatibility issue. You bought a device where the manufacturer told you in advance that a driver for the built-in wifi module doesn’t exist yet. It’s a product at the development stage.
So just follow the manufacturer’s recommendation from the product page: use a wifi dongle for now and pat yourself on the back for being an early adopter.
Having the device, I already tether the wifi. But it is indeed a compatibility issue: the old kernel drivers for the chip were janky and it’s doubtful how well they even worked the time. The code is apparently such a hot mess that the people who were working on it have stopped making progress. There is now skepticism that it will ever be fully functional.
The one I had was completely minor. The wifi on my NUC doesn't work if you use the proprietary driver but it does work with whatever the kernel for Mint 21.2 has in it.
It’s not so bad if you’re running a major distro kernel and they do some prerelease testing before cutting new kernel packages. But if you’re using the latest release from the kernel.org stable tree WiFi driver regressions happen somewhat regularly.
10-15 years ago, it was a problem dire enough to drive me back to windows until about the start of the pando, and I've not even thought about Wi-Fi drivers since coming back to Linux.
I did have issues with a cheap USB Wi-Fi dongle thing a few years back, but that was likely the fault of the dongle more than anything else, I know because it didn't really work under widows either.
If you want some irony, on a recent Ubuntu install I was able to access WiFi out of the box but the small windoze dual boot partition refused to connect to a WiFi 6 router. Tried upgrading driver, downgrading drivers, nothing… The computer came shipped with windows 10.
infosec.pub
Oldest