Per the request of a commenter on my Netger AirCard 340u (aka AT&T Beam) on Linux post, below are some debugging outputs from both an older AirCard 340u with the 01.05.11.52 firmware (plus v4 linux patch), and a newer AirCard 340u with more modern firmware.
Tired of waiting for a 3D XPoint based SSD to become available, I decided to grab a 512GB Intel SSD 600p for my XPS 15 9550. The intent was to switch over from Windows 10 to Linux on the 9550 while preserving the original SSD should I want to go back.
The actual SSD swap was not too difficult. A Torx T5 and small Phillips screwdriver are needed to remove the back of the 9550 and the m.2 SSD. This being my first NVMe system, I ran into a few gotchas while getting Linux installed. Though, the bulk of the issues are related to Broadcom’s poor Linux support.
If you’re having issues getting your Bluetooth device to automatically reconnect between KDE sessions (or rebooting your computer), try opening a terminal (e.g. Konsole) and clear the contents of your /var/lib/bluetooth directory. After doing this you will need to restart the bluetooth daemon. For reference, in a Gentoo/Funtoo system,
rm -rf /var/lib/bluetooth/* /etc/init.d/bluetooth restart
Note that the above needs to be run as root (or use
sudo). After removing the contents of your /var/lib/bluetooth directory, you will need re-pair your device in the Bluetooth manager. When paring your device, make sure it is set a trusted device.
Now, KDE should automatically reconnect the Bluetooth device after rebooting your computer. Note that the device may not reconnect until after you have logged in. To reconnect sooner, try using a command line Bluetooth device manager.
[end of transmission, stay tuned]
After acquiring a Broadwell generation Core i3 NUC (the NUC5i3RYK to be exact) and installing Linux, KDE/X.Org would lockup and crash frequently. Checking dmesg, the following messages appeared:
[drm] stuck on render ring
[drm] GPU HANG:…
From the dmesg report, it is clear the crashes were caused by the GPU hanging. After further inspection of the dmesg logs, it appears this is due to a bug between Intel’s graphics and IOMMU drivers. The easiest way to work around this is to disable Intel IOMMU support.
Since I had compiled IOMMU support into my kernel, removing IOMMU support involved a kernel recompile. When configuring your kernel using menuconfig, make sure that “Support for Intel IOMMU using DMA Remapping Devices” under “Device Drivers > IOMMU Hardware Support” is unchecked. This is equivalent to ensuring that
INTEL_MMU = n in your .config file. For the NUC, that was all that was required to keep the GPU driver from crashing and taking X.Org and KDE down with it.
[end of transmission, stay tuned]
Lately, I’ve found attempting to do web development on a local environment without Internet access while travelling just doesn’t cut it anymore. This is especially true for long roadtrips. Rather than dealing with tethering or a mobile hotspot, I decided to spring for a Netgear AirCard 340u. For GSM networks in the US, it happens to be the best USB wireless broadband modem currently available. It supports everything from GPRS through LTE on what appears to be most of the bands AT&T and T-Mobile currently use (a true rarity, though I can not confirm support of LTE on band 2 (1900MHz PCS), I do get T-Mobile LTE in Twin Cities).