Well, that last update was so bad for me that now my work machine is running openSUSE Tumbleweed. Let me recap:
A month ago, my company gave me a new laptop on which I attempted to install Manjaro, which resulted in this thread, which ultimately resulted in this thread. At the time, I was able to use the Manjaro-Architect installer to get Manjaro installed without MHWD trying to do anything automatic.
After the install, I installed but disabled bumblebee and bbswitch and the nonfree nvidia drivers. Why? If I enabled bumblebee at boot, the system would lock. If, however, I let X load and then started bumblebee, everything was fine. Nouveau would lock the machine, so that was not an option.
After the last stable update, I had no working X configuration. It would just exit. I spent 2 hours trying and failing to figure out why X was dead. I removed the modesetting driver configuration, but then X would just exit automatically. I had none of the problems people posted about–my update had gone smoothly and everything installed that needed to be installed.
Because this is my work machine, I determined 2 hours of work time lost was enough to attempt a reinstall. On another machine, I downloaded the 17.0.1 ISO, but it has the same problems the earlier one did: it never made it to X because of MHWD. I then attempted the Manjaro-Architect installer, but now when it’s installing its base config it also installs MHWD and the Nouveau driver, which locks the machine.
After that, I tried the Arch Anywhere installer, and it does the same thing: it tries to load Nouveau and locks the machine. Not wanting to go through a full-blown Arch install and have it fail on X again, I started doing research, and I found this:
Presumably, this is the patch Dell uses to support Linux on this machine. Being a KDE guy, I didn’t want to install Ubuntu (or Kubuntu; been down that road), so I tried openSUSE, which I know tracks hardware closely. Everything, including Bumblebee running at boot, works flawlessly as it does on any other system, so I can only assume they have also integrated this patch.
I am guessing at this point that Arch-based distros simply don’t have this patch in their kernels. I know Manjaro produces its own kernels. Would it be possible to integrate this patch into the Manjaro kernel?
Here’s the hardware I’m working with. Unfortunately, since this is my work machine, I can’t simply reinstall a bunch of times; I have to be able to get work done.
System: Host: enterprise Kernel: 4.10.5-1-default x86_64 (64 bit) Desktop: KDE Plasma 5.9.4 Distro: openSUSE Tumbleweed Machine: Device: laptop System: Dell product: Precision 5520 Mobo: Dell model: 06X96V v: A00 UEFI: Dell v: 1.1.3 date: 01/18/2017 Battery BAT0: charge: 85.1 Wh 110.9% condition: 76.7/85.1 Wh (90%) CPU: Quad core Intel Xeon E3-1505M v6 (-HT-MCP-) cache: 8192 KB clock speeds: max: 4000 MHz 1: 799 MHz 2: 799 MHz 3: 799 MHz 4: 799 MHz 5: 799 MHz 6: 799 MHz 7: 799 MHz 8: 799 MHz Graphics: Card-1: Intel Device 591d Card-2: NVIDIA GM107GLM [Quadro M1200 Mobile] Display Server: X.org 1.19.3 drivers: modesetting (unloaded: fbdev,vesa) Resolution: 120x33 Audio: Card Intel Device a171 driver: snd_hda_intel Sound: ALSA v: k4.10.5-1-default Network: Card: Intel Wireless 8265 / 8275 driver: iwlwifi IF: wlp2s0 state: up mac: 00:28:f8:24:96:f4 Drives: HDD Total Size: NA (-) ID-1: /dev/nvme0n1 model: N/A size: 1024.2GB Partition: ID-1: / size: 98G used: 9.3G (10%) fs: ext4 dev: /dev/nvme0n1p2 ID-2: /home size: 792G used: 330G (44%) fs: ext4 dev: /dev/nvme0n1p5 ID-3: swap-1 size: 34.36GB used: 0.00GB (0%) fs: swap dev: /dev/nvme0n1p3 Sensors: None detected - is lm-sensors installed and configured? Info: Processes: 290 Uptime: 5:47 Memory: 5704.0/31899.1MB Init: systemd runlevel: 5 Client: Shell (bash) inxi: 2.3.8