MX-19.2 KDE Beta 1 feedback thread

Message
Author
User avatar
Sparky
Posts: 1205
Joined: Sun Dec 23, 2018 6:07 pm

Re: MX-19.2 KDE Beta 1 feedback thread

#51 Post by Sparky »

dolphin_oracle wrote: Tue Jul 07, 2020 7:40 am
Sparky wrote: Tue Jul 07, 2020 7:39 am It looks great and runs great. I only had a side effect. When I startup the computer It asks for what kind of session I want, XFCE, Plasma, or fluxbox. Not sure how fluxbox got there.
where does it ask?

only plasma is on the iso.
On the top left of the monitor, its a drop down menu. If it helps, I installed it from MXPI
MX Linux Asus F552, 12GB RAM, 500GB WD SSD MX19.2
Dell Inspiron 7559 16GB RAM 1X 256GB SSD & 1TB SSD MX KDE 21.1 & Windows 11
Mini Tower PC 2X 256GB SSD MX KDE21.1

User avatar
sunrat
Posts: 664
Joined: Mon Mar 28, 2016 9:54 pm

Re: MX-19.2 KDE Beta 1 feedback thread

#52 Post by sunrat »

dolphin_oracle wrote: Tue Jul 07, 2020 8:22 am
sunrat wrote: Mon Jul 06, 2020 9:10 pm It's a UEFI install using existing partitions with / on sda7 and ESP on sda1, no other partitions used for MX.

Here's minstall.log , I couldn't make sense of it as I don't quite know what to look for: http://paste.debian.net/1155421/
according to the log, grub was not installed.
Thanks for looking. Almost at the end of the installation routine I recall text displaying "Installing GRUB" even though I unchecked the install GRUB box. It didn't install, but did wipe out the existing GRUB.

User avatar
asqwerth
Developer
Posts: 7935
Joined: Sun May 27, 2007 5:37 am

Re: MX-19.2 KDE Beta 1 feedback thread

#53 Post by asqwerth »

Sparky wrote: Tue Jul 07, 2020 8:30 am
dolphin_oracle wrote: Tue Jul 07, 2020 7:40 am
Sparky wrote: Tue Jul 07, 2020 7:39 am It looks great and runs great. I only had a side effect. When I startup the computer It asks for what kind of session I want, XFCE, Plasma, or fluxbox. Not sure how fluxbox got there.
where does it ask?

only plasma is on the iso.
If it helps, I installed it from MXPI
Then you are not testing the Beta iso but merely installing KDE packages into your existing MX installation. It's not the same as there are tweaks not picked up when you merely install standard or full KDE.

By the way, normal MX19.1 or 19.2 iso has mx-fluxbox added to it.
Desktop: Intel i5-4460, 16GB RAM, Intel integrated graphics
Clevo N130WU-based Ultrabook: Intel i7-8550U (Kaby Lake R), 16GB RAM, Intel integrated graphics (UEFI)
ASUS X42D laptop: AMD Phenom II, 6GB RAM, Mobility Radeon HD 5400

User avatar
fehlix
Developer
Posts: 12700
Joined: Wed Apr 11, 2018 5:09 pm

Re: MX-19.2 KDE Beta 1 feedback thread

#54 Post by fehlix »

sunrat wrote: Tue Jul 07, 2020 8:39 am
dolphin_oracle wrote: Tue Jul 07, 2020 8:22 am
sunrat wrote: Mon Jul 06, 2020 9:10 pm It's a UEFI install using existing partitions with / on sda7 and ESP on sda1, no other partitions used for MX.

Here's minstall.log , I couldn't make sense of it as I don't quite know what to look for: http://paste.debian.net/1155421/
according to the log, grub was not installed.
Thanks for looking. Almost at the end of the installation routine I recall text displaying "Installing GRUB" even though I unchecked the install GRUB box. It wasn't installed, but wiped out the existing GRUB.
On UEFI, GRUB comes within different players. Taking out for now secureboot's shim. The first would be the grubx64.efi GRUB loader, which is placed with a subdir on the ESP. This grubx64.efi would be register with the UEFI firmware's NVRAM-table as a valid or the first to choosen bootloader.
The grubx64-efi will load the remaining "grub-stuff" and the menu from the /boot folder on the /root (or boot partition,
What could have happed, is this: You'r default grubx64.efi was loading from /dev/sda7 and displays a nice grub menu.
When you now wipe out and reinstall on /dev/sda7 , the existing grubx64.efi loaded at boot, cannot find any grub-stuff on the new install on /dev/sda7.
You propaby just need to choose another valid grub-efi loader with the NVRAM table to get loaded.
Either by using efibootmgr or select at start up (by pressing e.g F12) another loader.
:puppy:

rrhobbs
Posts: 15
Joined: Thu Jan 02, 2020 7:35 pm

Re: MX-19.2 KDE Beta 1 feedback thread

#55 Post by rrhobbs »

fehlix wrote: Mon Jul 06, 2020 6:51 pm
rrhobbs wrote: Mon Jul 06, 2020 10:13 am On boot there is a notice ... in Grub I guess? "(VMX) outside text not allowed per bios"
Such warning can be ignored. OTOH, have you disable VM-bits (VT-x in intel) in bios. You might try to anable VT / Vm in bios.
Here some patch discussion on kerenel.org:
https://patchwork.kernel.org/patch/11250771/
So probably nothing to worry about ...
Thanks yes there is indeed a switch in the bios / enabled VT / the boot msg disappeared.

User avatar
fehlix
Developer
Posts: 12700
Joined: Wed Apr 11, 2018 5:09 pm

Re: MX-19.2 KDE Beta 1 feedback thread

#56 Post by fehlix »

Sparky wrote: Tue Jul 07, 2020 8:30 am
dolphin_oracle wrote: Tue Jul 07, 2020 7:40 am
Sparky wrote: Tue Jul 07, 2020 7:39 am It looks great and runs great. I only had a side effect. When I startup the computer It asks for what kind of session I want, XFCE, Plasma, or fluxbox. Not sure how fluxbox got there.
where does it ask?

only plasma is on the iso.
On the top left of the monitor, its a drop down menu. If it helps, I installed it from MXPI
Thats's another topic, yes, it is related to KDE - but this thread is about feedback of the released MX KDE Beta1 ISO, not about KDE installation through MXPI.

rrhobbs
Posts: 15
Joined: Thu Jan 02, 2020 7:35 pm

Re: MX-19.2 KDE Beta 1 feedback thread

#57 Post by rrhobbs »

Gerson wrote: Tue Jul 07, 2020 7:38 am
baldyeti wrote: Tue Jul 07, 2020 7:13 am
Gerson wrote: Tue Jul 07, 2020 7:06 am 2.- tutanota-desktop-linux.AppImage that worked fine in XFCE, it doesn't start in KDE
if you start that app from the command line (not from a graphical launcher) do you see any error message ?
Always in XFCE I started it by double-clicking on the file, in KDE it doesn't even start by command line.
Didu right click / ...properties / enable as an app ?

User avatar
wdscharff
Posts: 1106
Joined: Mon Feb 24, 2020 1:07 am

Re: MX-19.2 KDE Beta 1 feedback thread

#58 Post by wdscharff »

Because of the view over the plate edge the KDE beta installed.
When I switched to Linux 5 years ago, I had done the first 2 months of Mint (xfce, what else) as a production system and on the side my personal distribution and desktop manager rally. I ended up at opensuse (xfxe, what else) for the next years.
I didn't warm up to KDE at that time and I guess nothing has changed.
Installation without problems (second disk, Grub in the MBR of the second disk, so it's called via the Grub of the primary installation) incl. the latest Nvidia driver from the test repo (if you want to, you can)

What I noticed negatively, the processor load. One thread was always at 100%, so in idle state the total processor load was generally between 4-5%. The processor fan was running continuously (which it does not do while writing this text under xfce). If it's possibly the NVIDIA driver, I will verify the next days.
My memory requirements are momenatly higher than with XFCE, but there I have already thrown out stuff in the autostart, which might still be loaded by KDE, whereby I don't give a damn about 50mb less or more
Now it's installed, now I'm watching it too ;-)

if of interest, QSI

Code: Select all

System:    Host: mx Kernel: 5.6.0-2-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.6.0-2-amd64 
           root=UUID=574d2ad3-8237-4c50-924a-9a3adc8d31ec ro quiet splash 
           Desktop: KDE Plasma 5.14.5 wm: kwin_x11 dm: SDDM 
           Distro: MX-19.2_KDE-beta1_x64 patito feo July 5  2020 
           base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Desktop Mobo: Gigabyte model: B450 AORUS M v: x.x serial: <filter> 
           UEFI [Legacy]: American Megatrends v: F50 date: 11/27/2019 
CPU:       Topology: 12-Core model: AMD Ryzen 9 3900X bits: 64 type: MT MCP arch: Zen 
           family: 17 (23) model-id: 71 (113) stepping: N/A microcode: 8701013 
           L2 cache: 6144 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm 
           bogomips: 182061 
           Speed: 2193 MHz min/max: 2200/3800 MHz boost: enabled Core speeds (MHz): 1: 2197 
           2: 2194 3: 2191 4: 2196 5: 2193 6: 2191 7: 2191 8: 4440 9: 1974 10: 1971 
           11: 2018 12: 2015 13: 2196 14: 2455 15: 2195 16: 2195 17: 2195 18: 4477 19: 1995 
           20: 1991 21: 2014 22: 2021 23: 2513 24: 2196 
           Vulnerabilities: Type: itlb_multihit status: Not affected 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 
           mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full AMD retpoline, IBPB: conditional, STIBP: 
           conditional, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: NVIDIA GP107 [GeForce GTX 1050 Ti] vendor: Micro-Star MSI 
           driver: nvidia v: 440.82 bus ID: 07:00.0 chip ID: 10de:1c82 
           Display: x11 server: X.Org 1.20.4 driver: nvidia 
           unloaded: fbdev,modesetting,nouveau,vesa alternate: nv compositor: kwin_x11 
           resolution: 1920x1200~60Hz 
           OpenGL: renderer: GeForce GTX 1050 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 440.82 
           direct render: Yes 
Audio:     Device-1: NVIDIA GP107GL High Definition Audio vendor: Micro-Star MSI 
           driver: snd_hda_intel v: kernel bus ID: 07:00.1 chip ID: 10de:0fb9 
           Device-2: AMD Starship/Matisse HD Audio vendor: Gigabyte driver: snd_hda_intel 
           v: kernel bus ID: 09:00.4 chip ID: 1022:1487 
           Sound Server: ALSA v: k5.6.0-2-amd64 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
           vendor: Gigabyte driver: r8169 v: kernel port: f000 bus ID: 04:00.0 
           chip ID: 10ec:8168 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 3.18 TiB used: 8.54 GiB (0.3%) 
           ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO Plus 1TB size: 931.51 GiB 
           block size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 
           serial: <filter> rev: 2B2QEXM7 scheme: GPT 
           ID-2: /dev/sda vendor: Samsung model: SSD 850 EVO 1TB size: 931.51 GiB 
           block size: physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> 
           rev: 1B6Q scheme: MBR 
           ID-3: /dev/sdb type: USB vendor: Samsung model: SSD 860 EVO 500G 
           size: 465.76 GiB block size: physical: 4096 B logical: 512 B serial: <filter> 
           rev: 0223 scheme: GPT 
           ID-4: /dev/sdc type: USB vendor: Samsung model: SSD 860 QVO 1TB size: 931.51 GiB 
           block size: physical: 4096 B logical: 512 B serial: <filter> rev: 0223 
           scheme: MBR 
Partition: ID-1: / raw size: 59.62 GiB size: 58.43 GiB (98.01%) used: 8.54 GiB (14.6%) 
           fs: ext4 dev: /dev/sda2 
           ID-2: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap 
           swappiness: 15 (default 60) cache pressure: 100 (default) dev: /dev/nvme0n1p3 
Sensors:   System Temperatures: cpu: 62.8 C mobo: N/A gpu: nvidia temp: 37 C 
           Fan Speeds (RPM): N/A gpu: nvidia fan: 35% 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian buster-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian buster main contrib non-free
           2: deb http://deb.debian.org/debian-security buster/updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx/repo/ buster main non-free
           2: deb http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx/repo/ buster ahs
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 375 Uptime: 1m Memory: 31.37 GiB used: 783.6 MiB (2.4%) 
           Init: SysVinit v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 
           Shell: bash v: 5.0.3 running in: quick-system-in inxi: 3.0.36 

Translated with www.DeepL.com/Translator (free version)
my working horse Desktop AMD Ryzen 9 3900x, 32GB Ram // SSD ... enough
mx-fluxbox, what else?

In nature there are neither rewards nor punishments.
There are consequences.


my wallpaper gallery

User avatar
baldyeti
Posts: 717
Joined: Sat Dec 05, 2009 3:37 pm

Re: MX-19.2 KDE Beta 1 feedback thread

#59 Post by baldyeti »

fehlix wrote: Tue Jul 07, 2020 8:12 amAs it apprears the KDE Beta1 ISO does not contain most the changelog files, probably due to space constrains.
Alright, makes sense; nothing crucial missing anyway.

User avatar
Gerson
Posts: 879
Joined: Sun Nov 12, 2017 9:58 am

Re: MX-19.2 KDE Beta 1 feedback thread

#60 Post by Gerson »

rrhobbs wrote: Tue Jul 07, 2020 8:59 am
Gerson wrote: Tue Jul 07, 2020 7:38 am
baldyeti wrote: Tue Jul 07, 2020 7:13 am
if you start that app from the command line (not from a graphical launcher) do you see any error message ?
Always in XFCE I started it by double-clicking on the file, in KDE it doesn't even start by command line.
Didu right click / ...properties / enable as an app ?
It was the first thing I did. Give him permission to run.
No todos ignoramos las mismas cosas. :confused:

Locked

Return to “General”