[Stable Update] 2018-12-23 - Kernels, Cinnamon, XFCE, Nvidia, Pamac, Firmware, Brave

update
stable

#84

All fine in my notebook

uname -a
Linux toshiba 4.19.12-2-MANJARO #1 SMP PREEMPT Sun Dec 23 19:08:00 UTC 2018 x86_64 GNU/Linux


#85

Really liking 4.20, my three minute shutdown time is gone!!


#86

Have to agree, even on my ancient machine, 4.20 is snappy as can be.


#87

I tried the first solution to the systemd issue and it did nothing and tried the second and got the error error: '/var/cache/pacman/pkg/linux-firmware-20181218.0f22c85-1-any.pkg.tar.xz': package missing required signature


#88

You can try to install the downloaded package via sudo pacman -U /var/cache/pacman/pkg/linux-firmware-20181218.0f22c85-1-any.pkg.tar.xz


#89

I eventually chrooted in, used wget to download both packages and used Pacman -U to install them. This worked fine but then I noticed one application in particular (luckybackup) wouldn’t launch as it complained about needing Qt 5.12 so I just went back to unstable.


#90

It has just hit Arch Community Testing repo, if all goes well it should hit Manjaro unstable relatively soon, assuming the kernel extramodules for vbox 6 build without issues.


#91

I could not boot into 18.0.1. The 20181026.1cb4e51-1 did not work for me. The 20181218.0f22c85-1 does. Thanks for the help fixing the problem.


#92

Just reinstalled KDE and switched to kernel 4.20 with no problem.


#93

So it’s affecting the entirety of the RX500 line it seems.


#94

@torbido given that firmware 20181214 is buggy, I wouldn’t recommend it.


#95

I am in Colorado right now. (No, I am not near that trail marker) And longer I stay here, more drug joke I make. Already, I joked about Polar Express train smoking a lot of coke.


#96

Ive downgrade using pacui here are the details:

Fixed!!!
[noxl@nox-pc ~]$ pacui

                  PacUI - Package manager                      

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ 1 Update System 2 Maintain System β”‚
β”‚ 3 Install Packages 4 Remove Packages and Deps β”‚
β”‚---------------------------------------------------------------β”‚
β”‚ 5 Dependency Tree 6 Reverse Dependency Tree β”‚
β”‚ 7 List Package Files 8 Search Package Files β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
9 Roll Back System 10 Fix Pacman Errors
11 Edit Config Files 12 List Packages by Size
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ 14 List Installed from AUR β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

Enter number or marked letter(s) - 00 Help - 0 Quit
9

[sudo] password for noxl:
loading packages…
warning: downgrading package linux-firmware (20181214.8aa9e3e-1 => 20181026.1cb4e51-1)
resolving dependencies…
looking for conflicting packages…

Packages (1) linux-firmware-20181026.1cb4e51-1

Total Installed Size: 412.16 MiB
Net Upgrade Size: -4.43 MiB

:: Proceed with installation? [Y/n] y
(1/1) checking keys in keyring [######################] 100%
(1/1) checking package integrity [######################] 100%
(1/1) loading package files [######################] 100%
(1/1) checking for file conflicts [######################] 100%
(1/1) checking available disk space [######################] 100%
:: Running pre-transaction hooks…
(1/1) Save Linux kernel modules
:: Processing package changes…
(1/1) downgrading linux-firmware [######################] 100%
:: Running post-transaction hooks…
(1/3) Restore Linux kernel modules

==> Warning:
-> This computer hasn’t been restarted for a while.
-> You are running an old kernel. In order to use a
-> new version of the kernel, please restart your
-> computer as soon as possible.

(2/3) Creating temporary files…
(3/3) Arming ConditionNeedsUpdate…

System roll back finished. To return to PacUI press ENTER


#97

We are currently working on fresh v18.0.2 ISOs. The first preview is already online, based on our testing branch.


#98

That seems to be the problem; I’ve got a 560


#99

Friends don’t let friends ignore NVidia.


#100

I had so many problems with proprietary Nvidia drivers for so long that I changed to AMD and I’ll never go back.


#101

Sorry, AMD has problems too. There is always some way to work around it. Change OS, Change Driver, whatever it takes. Changing hardware is often beyond the average user abilities. I have options and you may too: Run "mhwd -l -d " in Terminal w/o quotes.

[bob@Manjaro-Stable ~]$ mhwd -l -d
--------------------------------------------------------------------------------
> PCI Device: /devices/pci0000:00/0000:00:1c.5/0000:03:00.0 (0200:10ec:8168)
  Network controller Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
--------------------------------------------------------------------------------
  > INSTALLED:

   NAME:	network-r8168
   ATTACHED:	PCI
   VERSION:	2016.04.20
   INFO:	RealTek RTL-8168 Gigabit Ethernet driver
   PRIORITY:	0
   FREEDRIVER:	true
   DEPENDS:	-
   CONFLICTS:	-
   CLASSIDS:	0200 
   VENDORIDS:	1186 10ec 



  > AVAILABLE:

   NAME:	network-r8168
   ATTACHED:	PCI
   VERSION:	2016.04.20
   INFO:	RealTek RTL-8168 Gigabit Ethernet driver
   PRIORITY:	0
   FREEDRIVER:	true
   DEPENDS:	-
   CONFLICTS:	-
   CLASSIDS:	0200 
   VENDORIDS:	1186 10ec 


--------------------------------------------------------------------------------
> PCI Device: /devices/pci0000:00/0000:00:01.0/0000:01:00.0 (0300:10de:1286)
  Display controller nVidia Corporation GK208 [GeForce GT 720]
--------------------------------------------------------------------------------
  > INSTALLED:

   NAME:	video-nvidia
   ATTACHED:	PCI
   VERSION:	2018.08.09
   INFO:	Closed source NVIDIA drivers for linux.
   PRIORITY:	5
   FREEDRIVER:	false
   DEPENDS:	-
   CONFLICTS:	video-hybrid-intel-nvidia-bumblebee video-hybrid-intel-nvidia-390xx-bumblebee video-nvidia-304xx video-nvidia-340xx video-nvidia-390xx 
   CLASSIDS:	0300 0302 
   VENDORIDS:	10de 



  > AVAILABLE:

   NAME:	video-nvidia
   ATTACHED:	PCI
   VERSION:	2018.08.09
   INFO:	Closed source NVIDIA drivers for linux.
   PRIORITY:	5
   FREEDRIVER:	false
   DEPENDS:	-
   CONFLICTS:	video-hybrid-intel-nvidia-bumblebee video-hybrid-intel-nvidia-390xx-bumblebee video-nvidia-304xx video-nvidia-340xx video-nvidia-390xx 
   CLASSIDS:	0300 0302 
   VENDORIDS:	10de 

   NAME:	video-nvidia-390xx
   ATTACHED:	PCI
   VERSION:	2018.08.09
   INFO:	Closed source NVIDIA drivers for linux.
   PRIORITY:	4
   FREEDRIVER:	false
   DEPENDS:	-
   CONFLICTS:	video-hybrid-intel-nvidia-bumblebee video-hybrid-intel-nvidia-390xx-bumblebee video-nvidia-304xx video-nvidia-340xx video-nvidia 
   CLASSIDS:	0300 0302 
   VENDORIDS:	10de 

   NAME:	video-nvidia-340xx
   ATTACHED:	PCI
   VERSION:	2018.08.09
   INFO:	Closed source NVIDIA legacy drivers for linux.
   PRIORITY:	3
   FREEDRIVER:	false
   DEPENDS:	-
   CONFLICTS:	video-hybrid-intel-nvidia-bumblebee video-hybrid-intel-nvidia-304xx-bumblebee video-hybrid-intel-nvidia-390xx-bumblebee video-nvidia video-nvidia-304xx video-nvidia-390xx 
   CLASSIDS:	0300 0302 
   VENDORIDS:	10de 

   NAME:	video-linux
   ATTACHED:	PCI
   VERSION:	2018.05.04
   INFO:	Standard open source drivers.
   PRIORITY:	2
   FREEDRIVER:	true
   DEPENDS:	-
   CONFLICTS:	-
   CLASSIDS:	0300 0380 0302 
   VENDORIDS:	1002 8086 10de 

   NAME:	video-vesa
   ATTACHED:	PCI
   VERSION:	2017.03.12
   INFO:	X.org vesa video driver.
   PRIORITY:	0
   FREEDRIVER:	true
   DEPENDS:	-
   CONFLICTS:	-
   CLASSIDS:	0300 
   VENDORIDS:	* 

#103

at least not generally, i’ve got a 580 and have got no problems with firmware 20181214.8aa9e3e-1 on 4.19 and 4.20


#104

If it works for you, great, that information is useful to the devs because it’ll help them see what changed between the hardware to narrow down what is causing the bug. For others like the 590 it doesn’t work (but then I’m not expecting full support for the 590 for at least another month).