Hey, as long as I ignore the thousand of entries in the error log I get every day from the iwlwifi kernel module crashing and restarting every 10 minutes its fine.
Yeah, they came in later on and that’s why I think they were “better”… learned from experience with the wifi drivers. And they weren’t really better, most of them still use binary blobs.
What killed my interest in Linux in highschool. Kept trying to get Ubuntu working but couldn’t get the internet to work for anything. Given that every help guide boiled down to “Go to this website and download x” and I didn’t have internet because… no wifi, I ended up getting frustrated enough to quit the whole thing. Maybe someday.
I’ve only had problems with wifi drivers twice, immediately after clean-installing fedora 38 on two different devices. Plugging my device into ethernet and updating fixed it instantly.
Not sure about iPhones, but I’ve used an android phone a couple times to both USB tether with data and to act as a WiFi receiver to download drivers in a pinch.
Use a second computer or a friend’s one to download the updates, get a USB ethernet adapter (a 100mbps one is like $5), put the system drive in a computer with lan, tether with another device via USB (phone, pi zero, etc) or use a different version/distro. I’m sure there are a bunch of other solutions.
I guess an ethernet to USB adapter might be your next best bet.
Alternatively, you could USB tether your phone if you have a good data plan
If you are in the unlikely event that you don’t have ethernet port to plug your device into, and no cell service, such as I was, you can use a spare wireless AP to get wifi if you’ve got one
Yes, you can. But the usual setup is to have a file system root that is nothing but subvolumes, which you can then use and mount basically as if they were independent partitions. But when you don't create a root subvolume for your system root first, you install the system directly on the file system root alongside created subvolumes. This tends to get messy as strictly speaking the file system root is a subvolume, too. So now you have that with your system installed and all other subvolumes nested inside it.
Yes. Usually the OS installer takes care of creating a root and home subvolume. Except Arch and similar barebones installer have instructions in the wiki.
The last time I had an issue with Linux drivers was in 2002, trying to set up a pppoe connection. I had no smartphone and there were no YouTube, Reddit, wikis, forums etc.
Back in 2016 I helped install some wifi drivers on a friend’s laptop in Ubuntu 16.04, which was not really a big deal.
I feel like these memes are made by Windows users :)
It’s insane how I just had this problem today. Had to tear out my network card in my Asus VivoBook 16. The drivers aren’t out for the MediaTek network card so I had to change it to an Intel one that I previously used.
Lemmy needs polls. The last time I had problems with WIFI drivers was… 15 years ago? On a laptop bought in a supermarket that originally came with Windows Vista. Oh, and the raspberry pi - fuck raspberry pis. They can’t pick wifi module worth shit.
I mean it isn’t Linux fault, but I wanted to install balenaos on my RaspberryPi and they don’t support a WiFi chip in their kernel. Without WiFi the whole idea won’t work for me. And I don’t want to buy a new WiFi usb only because they don’t want to add the drivers.
My attempts to add it to the kernel and build it myself failed so far.
I’m not faulting linux, I’m faulting the Raspberry Pi Foundation. Linux is their main operating system and they haven’t picked a good WIFI hardware module for years. Dunno if the new raspberrypi 4 is better, but I’m not paying to find out.
All single board computers have driver problems because they require custom kernel forks that can’t or don’t get mainlined for whatever reason (usually laziness), but Raspberry PI is actually the best when it comes to that stuff.
So when you buy an SBC, you need to ask yourself: will the company continue to develop/update/patch their custom kernel fork now that they shipped? Or will they just abandon it and move on to the next product? 9 times out of 9.01, it’s the latter.
Raspberry, seriously? What problems are you seeing?
I have a raspberry pi 3 acting as a 5GHz access point for as long as it’s been on the market, I can remember one time I had to restart it because of some wonkiness. About a dozen others as clients, never had an issue there either, fast and stable enough.
All using the default os (raspbian first, raspberry os later).
After that, I gave up on WiFi on Raspberries and used LAN, but they are so underpowered… my nextcloud instance took ages to do anything, XBMC (now Kodi) was slow and couldn’t render videos > 720p (it was struggling with 720p honestly), even a simple audio proxy over bluetooth (forward bluetooth audio from phone to speaker) barely functioned as the bluetooth cut out or it was janky as hell.
It’s easier to put a old phone as a server than a raspberrypi.
There are some oddball cards out there that need the linux firmware xxx (insert manufacturer instead of xxx) binary blobs in order to work, but yes, those cards are rare nowadays and mostly older hardware uses that (as you mentioned, hardware from 10+ years ago).
Had problems about 3 years ago, got a new laptop from work and the WiFi hardware was too new and didn’t have support in the kernel yet. Took a year or something, maybe less, until it worked.
you can create them afterwards and move the stuff into the subvol. do it from a live usb and don’t forget to update fstab. be sure to use rsync with the flag to keep permissions etc
That’s simple, but it’s a completely unnecessary waste of I/O. You could create a writable snapshot of the btrfs root as a subvolume, edit the fstab and any other relevant files within that new subvolume, reconfigure the bootloader to specify that subvolume as the root filesystem (as a Linux kernel command line argument) instead of the btrfs root, and then reboot. After rebooting, the original btrfs root can be mounted, and everything unwanted from the original root (other than the new subvolume and its ancestor directories, obviously) can be deleted. Do not delete anything that you didn’t want to lose the changes to on the original root subvolume that you did after creating the snapshot, as the snapshot only remembers what you did before, as well as the changes made specific only to it (like the fstab).
If one wanted to create multiple subvolumes for different purposes, the above procedure can be modified. For instance, if one wanted a separate subvolume mounted at / vs /home, then one can create two writable snapshots, empty out the contents of home in new subvolume 1 (but not the /home directory itself because you want the directory to exist for something to mount onto it), empty out everything outside of home within new subvolume 2, move the contents of home therein up one directory and remove the /home directory itself. Now, one can edit the fstab in new subvolume 1 as appropriate (not forgetting to have new subvolume 2 mount at /home), edit any other relevant files, reconfigure the bootloader to tell the Linux to use new subvolume 1 as the root subvolume, then reboot. Finally, one can remove the unnecessary files from the original root.
Edit:
It is arguably better to manually specify the new root when booting in the Linux kernel command line, and not reconfigure the bootloader until you successfully boot. After success, (if the following is relevant to your system) use update-grub, and it should look at fstab to automatically reconfigure the bootloader accordingly to use the appropriate new subvolume as specified at fstab.
This is what I did years ago to one of my own systems, although I don’t know anything about Timeshift and how it requires things to be set up (I have my own backup scripts that are run by cron). I could have just snapshotted the btrfs root directly for snapshots, but I wanted the snapshots to be cleanly separated from the subvolume used as the Linux VFS root (except when I explicitly mount them).
I have a few wifi adapters from china who only work properly under Linux lmfao
Did Microsoft actually infiltrate Lemmy or something? I’m hearing of issues about Linux that haven’t existed since the very first days of desktop Linux
The wifi chipset on my new MSI mobo isn’t supported on current LTS version of Mint - I had to install a more recent kernel, so there are still issues with newer hardware
Yeah, the Chinese stuff seems to work better under Linux… for some reason 😂. I one based on a Realtek chip (I think 🤔) and I couldn’t get passed a few hundred KB in Windows. Linux fried that baby, it did 1.5MB 😂.
I still have wifi woes on my old tablet. Works fine for a few minutes, then dies. Works fine in Windows. I’m about to reinstall on it. Maybe the next distro I try will work?
This is probably some sort of firmware power management bug that the windows driver is working around. Try and see if you can find any documentation on it
infosec.pub
Oldest