MX-19 Beta 3 Feedback
-
- Posts: 13
- Joined: Tue Apr 02, 2019 1:58 pm
Re: MX-19 Beta 3 Feedback
I am aware that 19.3 will not be upgradeable to final but want to make sure I can install Ancestris the proper way so at final all will go well.
Re: MX-19 Beta 3 Feedback
I've noticed that the fan on my cpu cooler isn't speeding up properly when cpu is under load.
In MX beta 3 when I run stressapptest, the cpu temp. will peak at 67 celcius. The fan doesn't appear to accelerate. I have booted Windows to test it and the fan can be very clearly heard to speed up; when I run prime95 stress test, the fan holds the cpu temp. at precisely 45 celcius as set in the BIOS (see screenshot).
The cooler is quite a beefy aftermarket addition with a big fan that shouldn't struggle to keep the temperature well below what I'm seeing in MX, so it would be good to fix this!
edit: looking at the info below, it seems that MX is mis-identifying the cpu fan as fan-1. The cpu: 0 reading is incorrect (I've opened the case to check). I imagine this can be fixed, but I don't want to break my system before asking the experts.
I used Psensor to monitor my temps, but several sensors were missing - after running sudo sensors-detect, the driver f71882fg was added to /etc/modules.
I suspect that fan1 is my cpu fan; the speed does ramp up under load, but not enough to maintain the temprature specified in BIOS settings. I wonder if it is linked to motherboard temp rather than CPU temp?
In MX beta 3 when I run stressapptest, the cpu temp. will peak at 67 celcius. The fan doesn't appear to accelerate. I have booted Windows to test it and the fan can be very clearly heard to speed up; when I run prime95 stress test, the fan holds the cpu temp. at precisely 45 celcius as set in the BIOS (see screenshot).
The cooler is quite a beefy aftermarket addition with a big fan that shouldn't struggle to keep the temperature well below what I'm seeing in MX, so it would be good to fix this!
edit: looking at the info below, it seems that MX is mis-identifying the cpu fan as fan-1. The cpu: 0 reading is incorrect (I've opened the case to check). I imagine this can be fixed, but I don't want to break my system before asking the experts.
Code: Select all
System: Host: mx 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=baaf804d-1179-4f05-acf7-4137d2ab017b ro quiet splash
Desktop: Xfce 4.14.1 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0
Distro: MX-19beta-3_x64 patito feo September 22 2019
base: Debian GNU/Linux 10 (buster)
Machine: Type: Desktop Mobo: MSI model: 760GA-P43(FX) (MS-7699) v: 1.0 serial: <filter>
BIOS: American Megatrends v: 1.3 date: 10/14/2014
CPU: Topology: 6-Core model: AMD FX-6300 bits: 64 type: MCP arch: Bulldozer
family: 15 (21) model-id: 2 stepping: N/A microcode: 6000852 L2 cache: 2048 KiB
flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 41999
Speed: 1434 MHz min/max: 1400/3500 MHz boost: enabled Core speeds (MHz): 1: 1460
2: 1521 3: 1400 4: 1400 5: 1400 6: 1399
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 GP106 [GeForce GTX 1060 3GB] vendor: ZOTAC driver: nvidia v: 418.74
bus ID: 01:00.0 chip ID: 10de:1c02
Display: x11 server: X.Org 1.20.4 driver: nvidia
unloaded: fbdev,modesetting,nouveau,vesa alternate: nv resolution: 1920x1080~60Hz
OpenGL: renderer: GeForce GTX 1060 3GB/PCIe/SSE2 v: 4.6.0 NVIDIA 418.74
direct render: Yes
Audio: Device-1: AMD SBx00 Azalia vendor: Micro-Star MSI driver: snd_hda_intel v: kernel
bus ID: 00:14.2 chip ID: 1002:4383
Device-2: NVIDIA GP106 High Definition Audio vendor: ZOTAC driver: snd_hda_intel
v: kernel bus ID: 01:00.1 chip ID: 10de:10f1
Sound Server: ALSA v: k4.19.0-6-amd64
Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Micro-Star MSI driver: r8169 v: kernel port: c800 bus ID: 02:00.0
chip ID: 10ec:8168
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives: Local Storage: total: 1.49 TiB used: 94.77 GiB (6.2%)
ID-1: /dev/sda vendor: Seagate model: ST1000DM003-1ER162 size: 931.51 GiB block size:
physical: 4096 B logical: 512 B speed: 3.0 Gb/s rotation: 7200 rpm serial: <filter>
rev: CC45 scheme: MBR
ID-2: /dev/sdb vendor: Western Digital model: WD6400AAKS-22A7B2 size: 596.17 GiB
block size: physical: 512 B logical: 512 B speed: 3.0 Gb/s serial: <filter> rev: 3B01
scheme: MBR
Partition: ID-1: / raw size: 27.94 GiB size: 27.38 GiB (97.98%) used: 8.92 GiB (32.6%) fs: ext4
dev: /dev/sda5
ID-2: /home raw size: 383.58 GiB size: 376.55 GiB (98.17%) used: 85.85 GiB (22.8%)
fs: ext4 dev: /dev/sda7
ID-3: swap-1 size: 488.0 MiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60)
cache pressure: 100 (default) dev: /dev/sda6
Sensors: System Temperatures: cpu: 53.0 C mobo: 37.0 C gpu: nvidia temp: 42 C
Fan Speeds (RPM): cpu: 0 fan-1: 666 fan-3: 0 gpu: nvidia fan: 56%
Voltages: 12v: N/A 5v: N/A 3.3v: 3.36 vbat: 3.25
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
Active apt repos in: /etc/apt/sources.list.d/vivaldi.list
1: deb http://repo.vivaldi.com/stable/deb/ stable main
Info: Processes: 246 Uptime: 6m Memory: 15.66 GiB used: 1.71 GiB (10.9%) 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
I suspect that fan1 is my cpu fan; the speed does ramp up under load, but not enough to maintain the temprature specified in BIOS settings. I wonder if it is linked to motherboard temp rather than CPU temp?
Code: Select all
$ sensors
f71868a-isa-0e80
Adapter: ISA adapter
+3.3V: +3.38 V
in1: +1.16 V
in2: +0.00 V
in3: +0.86 V
in4: +0.00 V
in5: +1.29 V
in6: +1.11 V
3VSB: +3.39 V
Vbat: +3.25 V
5VSB: +5.04 V
fan1: 669 RPM
fan2: 0 RPM ALARM
fan3: 0 RPM ALARM
temp1: +34.0°C (high = +255.0°C, hyst = +251.0°C) ALARM (CRIT)
(crit = +255.0°C, hyst = +251.0°C) sensor = transistor
temp2: +49.0°C (high = +255.0°C, hyst = +249.0°C) ALARM
(crit = +100.0°C, hyst = +94.0°C) sensor = thermistor
temp3: +29.0°C (high = +255.0°C, hyst = +253.0°C) ALARM (CRIT)
(crit = +255.0°C, hyst = +253.0°C) sensor = transistor
fam15h_power-pci-00c4
Adapter: PCI adapter
power1: 86.26 W (crit = 94.99 W)
k10temp-pci-00c3
Adapter: PCI adapter
temp1: +20.1°C (high = +70.0°C)
(crit = +70.0°C, hyst = +68.0°C)
You do not have the required permissions to view the files attached to this post.
Last edited by fossean on Mon Oct 14, 2019 4:02 pm, edited 6 times in total.
- chrispop99
- Global Moderator
- Posts: 3333
- Joined: Tue Jan 27, 2009 2:07 pm
Re: MX-19 Beta 3 Feedback
I've asked for it to be added as I will need it myself. I'm sure if it can be done, the packaging team will do it.Don_in_Vermont wrote: Mon Oct 14, 2019 10:59 am I am aware that 19.3 will not be upgradeable to final but want to make sure I can install Ancestris the proper way so at final all will go well.
Chris
MX Facebook Group Administrator.
Home-built desktop - Core i5 9400, 970 EVO Plus, 8GB
DELL XPS 15
Lots of test machines
Home-built desktop - Core i5 9400, 970 EVO Plus, 8GB
DELL XPS 15
Lots of test machines
Re: MX-19 Beta 3 Feedback
O.K., I think the 'problem' is actually one of my own making. Due to the extra transparency of the Linux OS, I've been confusing the CPU sensor with the CPU diode. I booted Windows again and checked in Aida64 and HWiNFO -- under load, I now see the same temps, with CPU at 67 C and CPU diode at 45 C. After a bit of research I now think the CPU sensor is inaccurate; it's supposed to measure the temp at the heat spreader, but is affected by the heat from the proximity of the VRM.fossean wrote: Mon Oct 14, 2019 11:06 am I've noticed that the fan on my cpu cooler isn't speeding up properly when cpu is under load.
So, apologies if anyone got distracted by my post. If anything, MX seems to manage high loads better than Windows, with significantly less fan noise.
- yonosoyesa
- Posts: 10
- Joined: Wed May 11, 2016 2:47 am
Re: MX-19 Beta 3 Feedback
I'm trying MX19 beta3. I can't install mailwatch plugin for the panel. Synaptic gives this (for me) criptic message...
xfce4-mailwatch-plugin:
Depends: xfce-panel (<4.13) but 4.14.1-1-mx19+1 is to be installed
... and then deselects the plugin so it's impossible to install.
Before I installed clipman plugin with no problem.
xfce4-mailwatch-plugin:
Depends: xfce-panel (<4.13) but 4.14.1-1-mx19+1 is to be installed
... and then deselects the plugin so it's impossible to install.
Before I installed clipman plugin with no problem.
Re: MX-19 Beta 3 Feedback
Not really cryptic: that plugin you tried to install has not been ported to Xfce 4.14. I did a web search on "debian xfce4-mailwatch-plugin" and downloaded and installed the version in the next Debian version (Bullseye). It installed fine on MX-19 beta, and I'm waiting to see if it actually works.
Yes it does.
Yes it does.
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
Personal: Lenovo X1 Carbon with MX-23 Fluxbox
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Re: MX-19 Beta 3 Feedback
FYI I reinstalled 19b3 yesterday and this time didn't install Nvidia drivers, and just kept it at nouveau which has a working opengl renderer.. VLC plays videos and guvcview runs.
If anyone can point me toward any particular log files that might show why the renderer is "N/A" in inxi -G with the Nvidia driver installed, I can reinstall it and check the log(s) for clues. Or maybe someone with a spare desktop PC and an old Nvidia card in their junk box can test it and see if they get the same results? Or maybe any Nvidia card would work for testing if the installer offers the 340 driver in a list of choices?
If anyone can point me toward any particular log files that might show why the renderer is "N/A" in inxi -G with the Nvidia driver installed, I can reinstall it and check the log(s) for clues. Or maybe someone with a spare desktop PC and an old Nvidia card in their junk box can test it and see if they get the same results? Or maybe any Nvidia card would work for testing if the installer offers the 340 driver in a list of choices?
Please read the Forum Rules, How To Ask For Help, How to Break Your System and Don't Break Debian. Always include your full Quick System Info (QSI) with each and every new help request.
Re: MX-19 Beta 3 Feedback
XFCE-14 packages just became stable in Gentoo. I experienced quite by accident that many panel items were darkly grayed out until I activated the compositor. I'm a minimalist and hadn't activated the compositor for many years. I haven't tried MX-19 Beta yet, but some of you are might check that out. Is the compositor on by default (Window Manager Tweaks). In 18.3 compositing is off by default, but I have it turned on after installation.
Re: MX-19 Beta 3 Feedback
I installed b3 on my 32-bit netbook in a dual-boot configuration with Win7. Grub was able to detect Windows with no problem and they both boot. 19 is fast! Faster than either 18 or Windows 7 anyway.
Code: Select all
System: Host: mx19b3-386 Kernel: 4.19.0-6-686-pae i686 bits: 32 compiler: gcc v: 8.3.0
parameters: BOOT_IMAGE=/boot/vmlinuz-4.19.0-6-686-pae
root=UUID=d68cb09c-5fac-4a80-9d37-f200289f42df ro quiet splash
Desktop: Xfce 4.14.1 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0
Distro: MX-19beta-3_386 patito feo October 3 2019 base: Debian GNU/Linux 10 (buster)
Machine: Type: Other-vm? System: AVERATEC product: N1130 v: N/A serial: <filter>
Chassis: No Enclosure type: 1 serial: <filter>
Mobo: AVERATEC model: N1130 serial: <filter> BIOS: Phoenix
v: NAPA0001.86C.0056.D.0907311757 date: 07/31/09
Battery: ID-1: BAT0 charge: 65.3 Wh condition: 65.3/65.4 Wh (100%) volts: 65.5/N/A
model: AVERATEC N1130 type: Li-ion serial: N/A status: Full
CPU: Topology: Single Core model: Intel Atom N270 bits: 32 type: MT arch: Bonnell
family: 6 model-id: 1C (28) stepping: 2 microcode: 218 L2 cache: 512 KiB
flags: nx pae sse sse2 sse3 ssse3 bogomips: 6385
Speed: 1078 MHz min/max: 800/1600 MHz Core speeds (MHz): 1: 804 2: 907
Vulnerabilities: Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: spec_store_bypass status: Not affected
Type: spectre_v1 status: Not affected
Type: spectre_v2 status: Not affected
Graphics: Device-1: Intel Mobile 945GSE Express Integrated Graphics driver: i915 v: kernel
bus ID: 00:02.0 chip ID: 8086:27ae
Display: x11 server: X.Org 1.20.4 driver: intel unloaded: fbdev,modesetting,vesa
resolution: 1024x600~60Hz
OpenGL: renderer: Mesa DRI Intel 945GME x86/MMX/SSE2 v: 1.4 Mesa 18.3.6
direct render: Yes
Audio: Device-1: Intel NM10/ICH7 Family High Definition Audio driver: snd_hda_intel
v: kernel bus ID: 00:1b.0 chip ID: 8086:27d8
Sound Server: ALSA v: k4.19.0-6-686-pae
Network: Device-1: Ralink RT3090 Wireless 802.11n 1T/1R PCIe driver: rt2800pci v: 2.3.0
port: 18e0 bus ID: 02:00.0 chip ID: 1814:3090
IF: wlan0 state: up mac: <filter>
Device-2: Realtek RTL8101/2/6E PCI Express Fast/Gigabit Ethernet driver: r8169
v: kernel port: 2000 bus ID: 04:00.0 chip ID: 10ec:8136
IF: eth0 state: down mac: <filter>
Drives: Local Storage: total: 111.79 GiB used: 4.92 GiB (4.4%)
ID-1: /dev/sda vendor: Gigabyte model: GP-GSTFS31120GNTD size: 111.79 GiB block size:
physical: 512 B logical: 512 B speed: <unknown> serial: <filter> rev: 61.3
scheme: MBR
Partition: ID-1: / raw size: 52.02 GiB size: 50.96 GiB (97.95%) used: 4.92 GiB (9.7%) fs: ext4
dev: /dev/sda3
ID-2: swap-1 size: 3.02 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60)
cache pressure: 100 (default) dev: /dev/sda4
Sensors: System Temperatures: cpu: 46.0 C mobo: N/A
Fan Speeds (RPM): N/A
Repos: 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: 168 Uptime: 19m Memory: 1.90 GiB used: 536.9 MiB (27.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
Please read the Forum Rules, How To Ask For Help, How to Break Your System and Don't Break Debian. Always include your full Quick System Info (QSI) with each and every new help request.
Re: MX-19 Beta 3 Feedback
I tried installing MX beta 2 or 3 on the ssd and found the following - if before was installed *buntu, then the partition "/home" (ext4) is visible and saved when formatting other partitions.
If I reinstall the system on itself with the formatting of the partitions "/" and "/root", the system writes that the partition "/home" can't be detected and formats it as well.
By itself data is not saved on it (I have to restore everything from backup).
But when I installing *buntu instead of MX, I can properly format both partitions ("boot" and "/") and save the data in the partition "/home"
The disk, of course, is not encrypted in all cases.
If I reinstall the system on itself with the formatting of the partitions "/" and "/root", the system writes that the partition "/home" can't be detected and formats it as well.
By itself data is not saved on it (I have to restore everything from backup).
But when I installing *buntu instead of MX, I can properly format both partitions ("boot" and "/") and save the data in the partition "/home"
The disk, of course, is not encrypted in all cases.