MX-19 Feedback

Message
Author
User avatar
dolphin_oracle
Developer
Posts: 22058
Joined: Sun Dec 16, 2007 12:17 pm

Re: MX-19 Feedback

#11 Post by dolphin_oracle »

GuiGuy wrote: Tue Oct 22, 2019 9:45 am Please explain the name "patito feo".... :confused:.
"ugly duckling" in spanish. A tongue-in-cheek shout out to all the folks who find Xfce, and MX in particular, "ugly".

BTW, its meant as ironic. I think MX 19 looks great!
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.

User avatar
GuiGuy
Posts: 832
Joined: Sun Dec 16, 2007 5:29 pm

Re: MX-19 Feedback

#12 Post by GuiGuy »

Thanks, D.O. :happy: .

User avatar
8bit
Posts: 139
Joined: Thu Sep 19, 2019 12:00 pm

Re: MX-19 Feedback

#13 Post by 8bit »

GuiGuy wrote: Tue Oct 22, 2019 9:45 am Please explain the name "patito feo".... :confused:.
Spanish for the ugly duckling. Why? I don't know.

8bit

User avatar
Eadwine Rose
Administrator
Posts: 14463
Joined: Wed Jul 12, 2006 2:10 am

Re: MX-19 Feedback

#14 Post by Eadwine Rose »

Read DO's reply above.
MX-23.6_x64 July 31 2023 * 6.1.0-34amd64 ext4 Xfce 4.20.0 * 8-core AMD Ryzen 7 2700
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.216.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030

User avatar
Fibogacci
Posts: 165
Joined: Sun Dec 30, 2018 3:19 pm

Re: MX-19 Feedback

#15 Post by Fibogacci »

junoluna wrote: Tue Oct 22, 2019 7:57 am Anyway ... given that MX 18 is working very well across the board, is there any need to upgrade at this stage?
I would prefer to wait til I start to break stuff (probably not long)
There is no need to upgrade if MX 18 is working ok with you.

I have one old laptop in my family which still uses MX 16.1 (well, I will install MX 19 soon) and it works fine.

I will probably stay for a while with MX 18.3 on my main computer (or at least I will have Live USB with MX 18.3). There are no a few packages yet in new MX 19 which I like/use (which probably will come with time), and these packages are in MX 18.3 (eg. Fsearch, Typecatcher etc.).

MX 19 is fresh born baby and has great future ahead ;)

For a new installations/computers I definitely choose MX 19 (I have already installed 19 RC1 on old P4 1,8 GHz and 1 GB RAM and it works fine).
MX-18 Continuum x86_64: laptop Dell Inspiron N7110, Intel Core i5-2410M @ 2.900GHz, 4GB RAM, Kernel: 4.19, DE: Xfce

User avatar
Eadwine Rose
Administrator
Posts: 14463
Joined: Wed Jul 12, 2006 2:10 am

Re: MX-19 Feedback

#16 Post by Eadwine Rose »

Interesting little something I just discovered on screen tearing with the default nvidia driver and compositors.

I have this youtube video that I test with: https://www.youtube.com/watch?v=5xkNy9gfKOg
Putting that full screen and then moving the mouse over it clearly shows if I have screen tearing or not.


When I have the compositor on Xfwm everything is fine.
If I change it to Compton I get tearing.
Change it back to Xfwm and all is fine again.

Code: Select all

System:    Host: eadwineMX19 Kernel: 4.19.0-6-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
           parameters: BOOT_IMAGE=/boot/vmlinuz-4.19.0-6-amd64 
           root=UUID=c7f614c9-c448-4560-93c2-9e9748b4ae8f ro quiet 
           Desktop: Xfce 4.14.1 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-19_x64 patito feo October 21  2019 base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Desktop Mobo: ASUSTeK model: TUF B450-PLUS GAMING v: Rev X.0x serial: <filter> 
           UEFI: American Megatrends v: 1607 date: 06/17/2019 
Battery:   Device-1: hidpp_battery_0 model: Logitech MX Ergo Multi-Device Trackball 
           serial: <filter> charge: 100% (should be ignored) rechargeable: yes 
           status: Discharging 
CPU:       Topology: 8-Core model: AMD Ryzen 7 2700 bits: 64 type: MT MCP arch: Zen+ 
           family: 17 (23) model-id: 8 stepping: 2 microcode: 800820C L2 cache: 4096 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm 
           bogomips: 102192 
           Speed: 1376 MHz min/max: 1550/3200 MHz boost: enabled Core speeds (MHz): 1: 1378 
           2: 1441 3: 1477 4: 1545 5: 1383 6: 1387 7: 1547 8: 1546 9: 1377 10: 1546 11: 1379 
           12: 1378 13: 1546 14: 1546 15: 1547 16: 1544 
           Vulnerabilities: 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 
Graphics:  Device-1: NVIDIA GP107 [GeForce GTX 1050 Ti] vendor: ASUSTeK driver: nvidia v: 418.74 
           bus ID: 08:00.0 chip ID: 10de:1c82 
           Display: x11 server: X.Org 1.20.4 driver: nvidia 
           unloaded: fbdev,modesetting,nouveau,vesa alternate: nv 
           resolution: 1920x1080~60Hz, 1920x1080~60Hz 
           OpenGL: renderer: GeForce GTX 1050 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 418.74 
           direct render: Yes 
Audio:     Device-1: Conexant Systems CX23887/8 PCIe Broadcast Audio and Video Decoder with 3D 
           Comb 
           vendor: Hauppauge works driver: cx23885 v: 0.0.4 bus ID: 07:00.0 chip ID: 14f1:8880 
           Device-2: NVIDIA GP107GL High Definition Audio vendor: ASUSTeK driver: snd_hda_intel 
           v: kernel bus ID: 08:00.1 chip ID: 10de:0fb9 
           Device-3: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel 
           bus ID: 0a:00.3 chip ID: 1022:1457 
           Device-4: Logitech QuickCam E 3500 type: USB driver: snd-usb-audio,uvcvideo 
           bus ID: 3-1:2 chip ID: 046d:09a4 serial: <filter> 
           Sound Server: ALSA v: k4.19.0-6-amd64 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK 
           driver: r8169 v: kernel port: f000 bus ID: 03:00.0 chip ID: 10ec:8168 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
           Device-2: Ralink MT7601U Wireless Adapter type: USB driver: mt7601u bus ID: 1-1:2 
           chip ID: 148f:7601 serial: <filter> 
           IF: wlan0 state: down mac: <filter> 
Drives:    Local Storage: total: 1.82 TiB used: 72.97 GiB (3.9%) 
           ID-1: /dev/sda vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 2B6Q scheme: GPT 
           ID-2: /dev/sdb vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 2B6Q scheme: GPT 
           ID-3: /dev/sdc vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 3B6Q scheme: GPT 
           ID-4: /dev/sdd type: USB vendor: Seagate model: BUP Slim RD size: 931.51 GiB 
           block size: physical: 4096 B logical: 512 B serial: <filter> rev: 0109 scheme: MBR 
           ID-5: /dev/sde vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 3B6Q scheme: GPT 
Partition: ID-1: / raw size: 58.59 GiB size: 57.42 GiB (98.00%) used: 5.90 GiB (10.3%) fs: ext4 
           dev: /dev/sdc1 
           ID-2: /home raw size: 166.48 GiB size: 162.87 GiB (97.83%) used: 150.4 MiB (0.1%) 
           fs: ext4 dev: /dev/sdc3 
           ID-3: swap-1 size: 7.81 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sdc2 
Sensors:   System Temperatures: cpu: 33.9 C mobo: 27.0 C gpu: nvidia temp: 35 C 
           Fan Speeds (RPM): cpu: 532 mobo: 168750 fan-2: fan-3: 0 fan-4: 757 fan-6: 0 
           gpu: nvidia fan: 25% 
           Voltages: 12v: N/A 5v: N/A 3.3v: 3.36 vbat: 3.27 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/antix.list 
           1: deb http://iso.mxrepo.com/antix/buster buster main
           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://mxrepo.com/mx/repo/ buster main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 343 Uptime: 5m Memory: 31.41 GiB used: 1.12 GiB (3.6%) 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 
MX-23.6_x64 July 31 2023 * 6.1.0-34amd64 ext4 Xfce 4.20.0 * 8-core AMD Ryzen 7 2700
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.216.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030

User avatar
chrispop99
Global Moderator
Posts: 3333
Joined: Tue Jan 27, 2009 2:07 pm

Re: MX-19 Feedback

#17 Post by chrispop99 »

Eadwine Rose wrote: Tue Oct 22, 2019 10:43 am Interesting little something I just discovered on screen tearing with the default nvidia driver and compositors.

I have this youtube video that I test with: https://www.youtube.com/watch?v=5xkNy9gfKOg
Putting that full screen and then moving the mouse over it clearly shows if I have screen tearing or not.


When I have the compositor on Xfwm everything is fine.
If I change it to Compton I get tearing.
Change it back to Xfwm and all is fine again.

Code: Select all

System:    Host: eadwineMX19 Kernel: 4.19.0-6-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
           parameters: BOOT_IMAGE=/boot/vmlinuz-4.19.0-6-amd64 
           root=UUID=c7f614c9-c448-4560-93c2-9e9748b4ae8f ro quiet 
           Desktop: Xfce 4.14.1 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-19_x64 patito feo October 21  2019 base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Desktop Mobo: ASUSTeK model: TUF B450-PLUS GAMING v: Rev X.0x serial: <filter> 
           UEFI: American Megatrends v: 1607 date: 06/17/2019 
Battery:   Device-1: hidpp_battery_0 model: Logitech MX Ergo Multi-Device Trackball 
           serial: <filter> charge: 100% (should be ignored) rechargeable: yes 
           status: Discharging 
CPU:       Topology: 8-Core model: AMD Ryzen 7 2700 bits: 64 type: MT MCP arch: Zen+ 
           family: 17 (23) model-id: 8 stepping: 2 microcode: 800820C L2 cache: 4096 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm 
           bogomips: 102192 
           Speed: 1376 MHz min/max: 1550/3200 MHz boost: enabled Core speeds (MHz): 1: 1378 
           2: 1441 3: 1477 4: 1545 5: 1383 6: 1387 7: 1547 8: 1546 9: 1377 10: 1546 11: 1379 
           12: 1378 13: 1546 14: 1546 15: 1547 16: 1544 
           Vulnerabilities: 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 
Graphics:  Device-1: NVIDIA GP107 [GeForce GTX 1050 Ti] vendor: ASUSTeK driver: nvidia v: 418.74 
           bus ID: 08:00.0 chip ID: 10de:1c82 
           Display: x11 server: X.Org 1.20.4 driver: nvidia 
           unloaded: fbdev,modesetting,nouveau,vesa alternate: nv 
           resolution: 1920x1080~60Hz, 1920x1080~60Hz 
           OpenGL: renderer: GeForce GTX 1050 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 418.74 
           direct render: Yes 
Audio:     Device-1: Conexant Systems CX23887/8 PCIe Broadcast Audio and Video Decoder with 3D 
           Comb 
           vendor: Hauppauge works driver: cx23885 v: 0.0.4 bus ID: 07:00.0 chip ID: 14f1:8880 
           Device-2: NVIDIA GP107GL High Definition Audio vendor: ASUSTeK driver: snd_hda_intel 
           v: kernel bus ID: 08:00.1 chip ID: 10de:0fb9 
           Device-3: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel 
           bus ID: 0a:00.3 chip ID: 1022:1457 
           Device-4: Logitech QuickCam E 3500 type: USB driver: snd-usb-audio,uvcvideo 
           bus ID: 3-1:2 chip ID: 046d:09a4 serial: <filter> 
           Sound Server: ALSA v: k4.19.0-6-amd64 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK 
           driver: r8169 v: kernel port: f000 bus ID: 03:00.0 chip ID: 10ec:8168 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
           Device-2: Ralink MT7601U Wireless Adapter type: USB driver: mt7601u bus ID: 1-1:2 
           chip ID: 148f:7601 serial: <filter> 
           IF: wlan0 state: down mac: <filter> 
Drives:    Local Storage: total: 1.82 TiB used: 72.97 GiB (3.9%) 
           ID-1: /dev/sda vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 2B6Q scheme: GPT 
           ID-2: /dev/sdb vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 2B6Q scheme: GPT 
           ID-3: /dev/sdc vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 3B6Q scheme: GPT 
           ID-4: /dev/sdd type: USB vendor: Seagate model: BUP Slim RD size: 931.51 GiB 
           block size: physical: 4096 B logical: 512 B serial: <filter> rev: 0109 scheme: MBR 
           ID-5: /dev/sde vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 3B6Q scheme: GPT 
Partition: ID-1: / raw size: 58.59 GiB size: 57.42 GiB (98.00%) used: 5.90 GiB (10.3%) fs: ext4 
           dev: /dev/sdc1 
           ID-2: /home raw size: 166.48 GiB size: 162.87 GiB (97.83%) used: 150.4 MiB (0.1%) 
           fs: ext4 dev: /dev/sdc3 
           ID-3: swap-1 size: 7.81 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sdc2 
Sensors:   System Temperatures: cpu: 33.9 C mobo: 27.0 C gpu: nvidia temp: 35 C 
           Fan Speeds (RPM): cpu: 532 mobo: 168750 fan-2: fan-3: 0 fan-4: 757 fan-6: 0 
           gpu: nvidia fan: 25% 
           Voltages: 12v: N/A 5v: N/A 3.3v: 3.36 vbat: 3.27 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/antix.list 
           1: deb http://iso.mxrepo.com/antix/buster buster main
           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://mxrepo.com/mx/repo/ buster main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 343 Uptime: 5m Memory: 31.41 GiB used: 1.12 GiB (3.6%) 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 
That's exactly the same video I use for tearing tests.

With Intel graphics, there is a significant reduction in tearing for me when using Xfce 4.14.

Chris
MX Facebook Group Administrator.
Home-built desktop - Core i5 9400, 970 EVO Plus, 8GB
DELL XPS 15
Lots of test machines

User avatar
Jerry3904
Administrator
Posts: 23062
Joined: Wed Jul 19, 2006 6:13 am

Re: MX-19 Feedback

#18 Post by Jerry3904 »

Here too, on Intel graphics. Haven't tried the desktop yet where Nvidia rules...
Production: 5.10, MX-23 Xfce, AMD FX-4130 Quad-Core, GeForce GT 630/PCIe/SSE2, 16 GB, SSD 120 GB, Data 1TB
Personal: Lenovo X1 Carbon with MX-23 Fluxbox
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin

User avatar
Eadwine Rose
Administrator
Posts: 14463
Joined: Wed Jul 12, 2006 2:10 am

Re: MX-19 Feedback

#19 Post by Eadwine Rose »

If I decide to use Compton I have to use that nvidia line in session and startup to prevent tearing

Code: Select all

nvidia-settings --assign CurrentMetaMode="nvidia-auto-select +0+0 { ForceFullCompositionPipeline = On }"
and then when I reboot the whole config of the screens gets messed up (left becomes right and such) and have to put xrandr to use to sort that out again

Code: Select all

/usr/bin/xrandr --output VGA-0 --off --output DVI-D-0 --mode 1920x1080 --pos 1920x0 --rotate normal --output HDMI-0 --primary --mode 1920x1080 --pos 0x0 --rotate normal
I am glad I now found out how to avoid it. Purely by accident mind you.


Also.. now that I see that +0+0 and the xrandr line I guess I could somehow combine the two to not have to use xrandr, but it's not needed since I am using Xfwm now. ;)
MX-23.6_x64 July 31 2023 * 6.1.0-34amd64 ext4 Xfce 4.20.0 * 8-core AMD Ryzen 7 2700
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.216.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030

Don_in_Vermont
Posts: 13
Joined: Tue Apr 02, 2019 1:58 pm

Re: MX-19 Feedback

#20 Post by Don_in_Vermont »

Just did a fresh install on other system and all was good then decided to install vbox and system crashed.
Rebooted and now no GUI, terminal login showing "Loading VirtualBox kernal modules ....
Fail startpar: service(s) returned failure: plymouth...failed

How do I get back to GUI?

Locked

Return to “General”