MX Linux Forum

this live usb KDE RC1 boots very, very slowiy off a usb 2.0 AND is very sluggish, near non-responsive, after booting and when shutting down 'save-persist is as slow as molasses.

Quick System Info of the machine I'm live usb booting on is as follows...(which btw is otherwise pretty fast)
Without using persistence the live usb is fine. I'm thinking I'll just install to a SSD and play with it that way.


System: Host: <filter> Kernel: 4.19.0-13-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0
parameters: BOOT_IMAGE=/boot/vmlinuz-4.19.0-13-amd64
root=UUID=<filter> ro quiet splash
Desktop: Xfce 4.14.2 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0
Distro: MX-19.3_x64 patito feo November 11 2020 base: Debian GNU/Linux 10 (buster)
Machine: Type: Desktop Mobo: Gigabyte model: B450M DS3H V2 v: x.x serial: <filter>
UEFI [Legacy]: American Megatrends v: F1 date: 08/17/2020
CPU: Topology: Quad Core model: AMD Ryzen 5 3400G with Radeon Vega Graphics bits: 64
type: MT MCP arch: Zen+ family: 17 (23) model-id: 18 (24) stepping: 1
microcode: 8108109 L2 cache: 2048 KiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 59090
Speed: 1259 MHz min/max: 1400/3700 MHz boost: enabled Core speeds (MHz): 1: 1260
2: 1280 3: 1258 4: 1259 5: 1280 6: 1371 7: 1355 8: 1264
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: disabled, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics: Device-1: AMD Picasso vendor: Gigabyte driver: N/A bus ID: 06:00.0 chip ID: 1002:15d8
Display: x11 server: X.Org 1.20.4 driver: vesa resolution: 1920x1080~N/A
OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.3 Mesa 18.3.6 compat-v: 3.1
direct render: Yes
Audio: Device-1: AMD Raven/Raven2/Fenghuang HDMI/DP Audio driver: snd_hda_intel v: kernel
bus ID: 06:00.1 chip ID: 1002:15de
Device-2: AMD Family 17h HD Audio vendor: Gigabyte driver: snd_hda_intel v: kernel
bus ID: 06:00.6 chip ID: 1022:15e3
Sound Server: ALSA v: k4.19.0-13-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: 100 Mbps duplex: full mac: <filter>
Drives: Local Storage: total: 409.88 GiB used: 145.64 GiB (35.5%)
ID-1: /dev/sda model: SATA SSD size: 111.79 GiB block size: physical: 512 B
logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 61.3 scheme: GPT
ID-2: /dev/sdb vendor: Western Digital model: WD3200AAJS-65M0A0 size: 298.09 GiB
block size: physical: 512 B logical: 512 B speed: 3.0 Gb/s serial: <filter> rev: 3E01
scheme: MBR
Partition: ID-1: / raw size: 111.79 GiB size: 109.78 GiB (98.21%) used: 33.51 GiB (30.5%)
fs: ext4 dev: /dev/sda1
Sensors: System Temperatures: cpu: 35.8 C mobo: N/A
Fan Speeds (RPM): N/A
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://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ buster main non-free
No active apt repos in: /etc/apt/sources.list.d/various.list
Info: Processes: 243 Uptime: 2h 15m Memory: 13.71 GiB used: 689.1 MiB (4.9%) Init: SysVinit
v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: quick-system-in
running in: quick-system-in inxi: 3.0.36

@jackdotnet thanks for the report. In the mean time can you please put your QSI back into code tags for readability. QSI automatically adds them for easy pasting into the forums.

@SwampRabbit I'd be happy use code tags but I don't know how to. I'm in my 75th year and just learning linux and other things! I'll try to figure code tags out. Thanks for your request.

@jackdotnet no worries at all boss.

You select the text you want to put in code tags and click the </> icon up top.

Note: you need to be in "Full Editor & Preview" not "Quick Reply" to get that icon.

this live usb KDE RC1 boots very, very slowiy off a usb 2.0 AND is very sluggish, near non-responsive, after booting and when shutting down 'save-persist is as slow as molasses.

Not surprised, 2.0 does only 60MB/s (and that's the maximum it can do, normal speed are slower)

Distro: MX-19.3_x64

Seems like you are in the wrong thread.

krename is not installed by default

Dolphin service menus "Actions" > "Rename with KRename" require it to work

markol wrote: Sat Oct 09, 2021 5:47 am Spectacle in RC1 crashes every time I close it (verified on 2 machines)

baldyeti wrote: Wed Oct 13, 2021 5:37 am Sadly i can confirm that spectacle crashes (both under init and systemd)

On plain bullseye+KDE, it does not crash even though it seems to be using the exact same package version (20.12.3-1)

I sent up an updated kimageannotator 0.5.2-1, hopefully it fixes this segfault, if you get this update can you verify if it's fixed or not? Thanks

SwampRabbit wrote: Tue Oct 19, 2021 12:24 am

markol wrote: Sat Oct 09, 2021 5:47 am Spectacle in RC1 crashes every time I close it (verified on 2 machines)

baldyeti wrote: Wed Oct 13, 2021 5:37 am Sadly i can confirm that spectacle crashes (both under init and systemd)

On plain bullseye+KDE, it does not crash even though it seems to be using the exact same package version (20.12.3-1)

I sent up an updated kimageannotator 0.5.2-1, hopefully it fixes this segfault, if you get this update can you verify if it's fixed or not? Thanks

Thank you, that seems to have fixed it -- Spectacle no longer crashing on close.

@Adrian MX-21 KDE RC1 live usb 2.0 with persistence all runs as slow as molasses on my machine...the qsi I posted is from my machine I'm booting the live usb on which is normally running MX-19.3. I guess I could run qsi in MX-21 KDE RC1 live usb but all the hardware would be exactly the same. I bet if I put the RC on a live usb 3.0 I'd get molasses again.

jackdotnet wrote: Tue Oct 19, 2021 9:00 am @Adrian MX-21 KDE RC1 live usb 2.0 with persistence all runs as slow as molasses on my machine...the qsi I posted is from my machine I'm booting the live usb on which is normally running MX-19.3. I guess I could run qsi in MX-21 KDE RC1 live usb but all the hardware would be exactly the same. I bet if I put the RC on a live usb 3.0 I'd get molasses again.

probably if you are using the vesa graphics driver like your output above then yes, plasma will be dog slow.

when people talk about how light plasma has become, they don't really talk about the load placed on the graphics subsystem. they usually just think of ram. plasma has a lot of 3d acceleration going on, and vesa/llvmpipe isn't going to keep up.