!wifi
!!anger

I bought a new wlan card to fix my infuriating wifi issues. It's a TPLink Archer T6E, supports ac, and ostensibly uses Ath9k drivers. Multiple reviews said "installed, booted, and connected! So easy."

Guess what?
I've spent the past two hours trying to get it to work. No banana.

Some other reviews have them fighting with the drivers for days. Looks like that's going to be me, too. 😡

Why the fuck is wifi so fucking difficult?

tl;dr:
The Debian 10 live disc and installer say: Heavens me, just look at the time! I’m late for my <segmentation fault

—————

tl:
The Debian 10 live cd and its new “calamares” installer are both complete crap. I’ve never had any issues with installing Debian prior to this, save with getting WiFi to work (as expected). But this version? Ugh. Here are the things I’ve run into:

Unknown root password; easy enough to get around as there is no user password; still annoying after the 10th time.

Also, the login screen doesn’t work off-disc because it won’t accept a blank password, so don’t idle or you’ll get locked out.

The lock screen is overzealous and hard-locks the computer after awhile; not even the magic kernel keys work!

The live disc doesn’t have many standard utilities, or a graphical partition editor. Thankfully I’m comfortable with fdisk.

The graphical installer (calamares) randomly segfaults, even from innocuous things like clicking [change partition] when you don’t have a partition selected. Derp.

It also randomly segfaults while writing partitions to disk — usually on the second partition.

It strangely seems less likely to segfault if the partitions are already there, even if it needs to “reformat” (recreate) them.

It also defaults to using MBR instead of GPT for the partition table, despite the tooltip telling you that MBR is deprecated and limited, and that GPT is recommended for new systems. You cannot change this without doing the partitions manually.

If you do the partitions manually and it can’t figure out where to install things, it just crashes. This is great because you can’t tell it where to install things, and specifying mount points like /boot, /, and /home don’t seem to be enough.

It also tries installing 32bit grub instead of 64bit, causing the grub installer to fail.

If you tell it to install grub on /boot, it complains when that partition isn’t encrypted — fair — but if you tell it to encrypt /boot like it wants you to, it then tries installing grub on the encrypted partition it just created, apparently without decrypting it, so that obviously fails — specific error: cannot read file system.

On the rare chance that everything else goes correctly, the install process can still segfault.

The log does include entries for errors, but doesn’t include an error message. Literally: “ERROR: Installation failed:” and the log ends. Helpful!

If the installer doesn’t segfault and the install process manages to complete, the resulting install might not even boot, even when installed without any drive encryption. Why? My guess is it never bothered to install Grub, or put it in the wrong place, or didn’t mark it as bootable, or who knows what.

Even when using the live disc that includes non-free firmware (including Ath9k) it still cannot detect my wlan card (that uses Ath9k).

I’ve attempted to install thirty plus times now, and only managed to get a working install once — where I neglected to include the Ath9k firmware.

I’m now trying the cli-only installer option instead of the live session; it seems to behave at least. I’m just terrified that the resulting install will be just as unstable as the live session.

All of this to copy the contents of my encrypted disks over so I can use them on a different system. =/

I haven’t decided which I’m going with next, but likely Arch, Void, or Gentoo. I’d go with Qubes if I had more time to experiment.

But in all seriousness, the Debian devs need some serious help. I would be embarrassed if I released this quality of hot garbage.

(This same system ran both Debian 8 and 9 flawlessly for years)

This is a followup to my earlier RealTek networking rant.

After reviewing and researching all of the wlan adapter suggestions on that rant, as well as a few more, I settled on an Alfa AWUS036ACH usb3 wireless-ac adapter. Every Alfa I've ever owned has been amazing, so I happily bought it.

It arrived today, and I excitedly threw my existing RealTek garbage across the room, hooked up my fancy new toy, and... nothing.

Fearing it was doa, I ran `lsusb` to see if it was even showing up... and it was! but identifying itself as a RealTek device...?

All of my research showed it uses the Atheros9k chipset. It's advertised and praised as using the "famous Atheros AR9271 chipset" and the Ath9k drivers. Except this particular unit appears to use the RTL8821AU chipset, therefore requiring RealTek drivers. askfja;sldf.

I unhappily fetched the garbage from the dirty laundry where it landed, installed it, and began my research anew.

I found, among all of the wonderful promises of Ath9k bliss, a thread on the Kali forums corroborating the RealTek driver nonsense, and it explained how to get the RTL8821 drivers working with it. which is pretty much the very last thing I want to do.

If you've read any of my networking rants, well, they've all been about how totally awful RealTek linux drivers are, and that's pretty much common knowledge anyway. So I'm like extremely pissed off.

ARGH WHY IS NETWORKING WITH LINUX ALWAYS SO FREAKING DIFFICULT? haslkfjasgdskg