MX-18 beta 1 feedback

[Otter]

All working fine, no issues.

Although, I encountered black screen on the 1st install. Black screen with both normal & liquorix kernel. Alt + F2, command line works fine. startx gives that usual generic can't find display error.

1) Install
2) Update
3) Install liquorix kernel (oh xxxxxxx forgot to install "nvidia driver first" moment)
4) Install nvidia driver
5) Reboot

Black screen with both normal & liquorix kernel.

2nd install

1) Install
2) Update
3) install nvidia driver first
4) Reboot
5) Boots fine
6) Install liquorix kernel
7) Reboot & boots fine

Code: Select all

❯ inxi -F
System:    Host: TheBuildBot Kernel: 4.19.0-8.1-liquorix-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3 
           Distro: MX-18b1_x64 Continuum December 3  2018 
Machine:   Type: Desktop System: Gigabyte product: N/A v: N/A serial: <root required> 
           Mobo: Gigabyte model: 970A-DS3P v: x.x serial: <root required> BIOS: American Megatrends v: F2j 
           date: 12/29/2014 
CPU:       Topology: 8-Core model: AMD FX-8320 bits: 64 type: MCP L2 cache: 2048 KiB 
           Speed: 1405 MHz min/max: 1400/3500 MHz Core speeds (MHz): 1: 1406 2: 1404 3: 1432 4: 1464 5: 1405 
           6: 1402 7: 1417 8: 1454 
Graphics:  Device-1: NVIDIA GM107 [GeForce GTX 750 Ti] driver: nvidia v: 390.87 
           Display: x11 server: X.Org 1.19.2 driver: nvidia resolution: 1920x1080~60Hz 
           OpenGL: renderer: GeForce GTX 750 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 390.87 
Audio:     Device-1: Advanced Micro Devices [AMD/ATI] SBx00 Azalia driver: snd_hda_intel 
           Device-2: NVIDIA driver: snd_hda_intel 
           Sound Server: ALSA v: k4.19.0-8.1-liquorix-amd64 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: 94:de:80:c8:0d:72 
Drives:    Local Storage: total: 2.49 TiB used: 1.44 TiB (57.6%) 
           ID-1: /dev/sda vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB 
           ID-2: /dev/sdb vendor: Kingston model: SA400S37240G size: 223.57 GiB 
           ID-3: /dev/sdc vendor: Seagate model: ST2000DM006-2DM164 size: 1.82 TiB 
           ID-4: /dev/sdd vendor: Western Digital model: WD2500BEVS-60UST0 size: 232.89 GiB 
Partition: ID-1: / size: 19.58 GiB used: 6.40 GiB (32.7%) fs: ext4 dev: /dev/sda1 
           ID-2: swap-1 size: 10.11 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sdd4 
Sensors:   System Temperatures: cpu: 36.4 C mobo: N/A gpu: nvidia temp: 41 C 
           Fan Speeds (RPM): N/A gpu: nvidia fan: 30% 
Info:      Processes: 252 Uptime: 3h 04m Memory: 15.63 GiB used: 2.13 GiB (13.6%) Shell: bash inxi: 3.0.25 

Also getting the following error while updating initramfs.

Code: Select all

update-initramfs: Generating /boot/initrd.img-4.19.0-1-amd64
W: Possible missing firmware /lib/firmware/nvidia/gv100/sec2/sig.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gv100/sec2/image.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gv100/sec2/desc.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gv100/nvdec/scrubber.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_method_init.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_bundle_init.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_nonctx.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_ctx.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_sig.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_data.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_inst.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_bl.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_sig.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_data.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_inst.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_bl.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/ucode_unload.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/ucode_load.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/unload_bl.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/bl.bin for module nouveau

[entropyfoe]

I did synaptic updates last night and noticed new kernel.

What is the new kernel for? For the RC?

Uptime >5 days with the BIOS fix, so I took out the rcu_nocbs line in grub and rebooted. Still running this morning.

Verdict, the beta1 is still stable on the Ryzen hardware.

[dolphin_oracle]

I did synaptic updates last night and noticed new kernel.

What is the new kernel for? For the RC?

Uptime >5 days with the BIOS fix, so I took out the rcu_nocbs line in grub and rebooted. Still running this morning.

Verdict, the beta1 is still stable on the Ryzen hardware.

the new kernel updates the kernel supplied on beta 1, which had a potential filesystem corruption bug.

[Richard]

moved.

[manyroads]

LightDM Bug? Feature?

I just noticed that in my LightDM GTK + Greeter Settings when I set (check) "Use user wallpaper if available" the LightDM Greeter background does not match that on my Desktop. Any ideas or suggestions on how I can fix it so they are synchronized? Or if this is simply a bug?

[Gerson]

@fehlix
Today again it happened after receiving the MX 18 beta update.
I have done everything they recommend in the wiki, I even deleted the folder (~/.local/share/keyrings) but again I ask for keys, libpam-gnome-keyring is installed by default.
When I open Chrome or Vivaldi or another application, it asks for keys.
I made a collage of the photos taken with a cell phone because it did not allow me to take a screen print.

[Eadwine Rose]

OK.. when on the screen.. don't type anything, just leave it empty and hit enter.


If you tried that already, sorry.

[manyroads]

@Gerson @Eadwine Rose, Eadwine's solution works for me.

[Gerson]

@manyroads:
Thank you. The only thing that works for me is to delete the folder (~/.local/share/keyrings) and restart, it does not ask me for passwords again.

[Eadwine Rose]

Ah glad that worked!

Does it stay like that even after a reboot? Only then is it truly solved (at least, imho )