Page 1 of 1
MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 6:45 am
by dolphin_oracle
Place feedback from the MX-18 beta 1 testing iso here.
If posting hardware issues, please post the output of the terminal command "inxi -F" or use our "Quick-system-info" from the menu, at a minimum.
If posting nvidia-installer issues, please post the contents of /var/log/ddm.log.
If posting remaster issues, please include the contents of /var/log/live/live-remaster.log
If posting issues with MX-PackeageInstaller "Popular Apps", please post contents of /var/log/mxpi.log or /var/log/mxpi.log.old (whichever contains the log of your issue).
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 7:09 am
by PPC
dolphin_oracle wrote: Mon Dec 03, 2018 6:45 am
Place feedback from the MX-18 beta 1 testing iso here.
If posting hardware issues, please post the output of the terminal command "inxi -F" or use our "Quick-system-info" from the menu, at a minimum.
If posting nvidia-installer issues, please post the contents of /var/log/ddm.log.
If posting remaster issues, please include the contents of /var/log/live/live-remaster.log
If posting issues with MX-PackeageInstaller "Popular Apps", please post contents of /var/log/mxpi.log or /var/log/mxpi.log.old (whichever contains the log of your issue).
Hi.
The only real "problem" I had with MX 17 was installing the nvidea driver. My MX box is my work pc, so if I test it, it's via live USB... Is there a way of installing the driver on it? with/without activating persistency?
P.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 7:57 am
by dolphin_oracle
PPC wrote: Mon Dec 03, 2018 7:09 am
dolphin_oracle wrote: Mon Dec 03, 2018 6:45 am
Place feedback from the MX-18 beta 1 testing iso here.
If posting hardware issues, please post the output of the terminal command "inxi -F" or use our "Quick-system-info" from the menu, at a minimum.
If posting nvidia-installer issues, please post the contents of /var/log/ddm.log.
If posting remaster issues, please include the contents of /var/log/live/live-remaster.log
If posting issues with MX-PackeageInstaller "Popular Apps", please post contents of /var/log/mxpi.log or /var/log/mxpi.log.old (whichever contains the log of your issue).
Hi.
The only real "problem" I had with MX 17 was installing the nvidea driver. My MX box is my work pc, so if I test it, it's via live USB... Is there a way of installing the driver on it? with/without activating persistency?
P.
no, not really. they will install, but there seems to be issues with getting them working on a live system.
and please check the "known issues" on the beta 1 - nvidia driver install from the main repos may not install yet. those from debian-backports should, and we will have new ones in the main repo before final release.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 8:19 am
by richb
Installed on ssd, no encryption, full disk. Configured to my preferences in about 10 minutes including adding Google Chrome and GC extensions. Looking good.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 8:37 am
by Paul..
Installed on nvme, no encryption, nvme0n1p2...went smoothly but 'nVidia driver installation' failed with dependency problems both on Main and Backports option:
Code: Select all
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
libnvidia-encode1 : Depends: libcuda1 (= 384.130-1) but it is not going to be installed
Depends: libnvcuvid1 (>= 260) but it is not going to be installed
nvidia-driver : Depends: nvidia-driver-libs (= 384.130-1) but it is not going to be installed or
nvidia-driver-libs-nonglvnd (= 384.130-1) but it is not going to be installed
Depends: nvidia-driver-bin (= 384.130-1) but it is not going to be installed
Depends: xserver-xorg-video-nvidia (= 384.130-1) but it is not going to be installed
Depends: nvidia-vdpau-driver (= 384.130-1) but it is not going to be installed
Depends: nvidia-alternative (= 384.130-1)
Recommends: nvidia-persistenced
nvidia-kernel-dkms : Depends: nvidia-kernel-support--v1
nvidia-settings : Depends: nvidia-alternative
Depends: libxnvctrl0 (= 384.111-1~deb9u1) but 390.67-1~mx17+1 is to be installed
Recommends: libgl1-nvidia-glvnd-glx but it is not going to be installed or
libgl1-nvidia-glx but it is not going to be installed
Recommends: nvidia-vdpau-driver but it is not going to be installed
Recommends: libnvidia-ml1 but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
/usr/local/bin/ddm-mx: line 472: creating /etc/X11/xorg.conf file: No such file or directory
/usr/local/bin/ddm-mx: line 473: nvidia-xconfig: command not found
Finished
New Rig:
Code: Select all
System: Host: XXXXXX Kernel: 4.19.0-1-amd64 x86_64 bits: 64 compiler: gcc v: 6.3.0
Desktop: Xfce 4.12.3 Distro: MX-18b1_x64 Continuum December 3 2018
base: Debian GNU/Linux 9 (stretch)
Machine: Type: Desktop Mobo: ASUSTeK model: PRIME X470-PRO v: Rev X.0x serial: <filter>
UEFI: American Megatrends v: 4011 date: 04/19/2018
CPU: Topology: Quad Core model: AMD Ryzen 5 1400 bits: 64 type: MT MCP arch: Zen rev: 1
L2 cache: 2048 KiB
flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 51097
Speed: 2054 MHz min/max: 1550/3200 MHz Core speeds (MHz): 1: 1537 2: 1471 3: 1367
4: 1375 5: 1854 6: 2090 7: 2266 8: 2225
Graphics: Device-1: NVIDIA GM107 [GeForce GTX 750 Ti] driver: nouveau v: kernel bus ID: 09:00.0
Display: x11 server: X.Org 1.19.2 driver: nouveau unloaded: fbdev,modesetting,vesa
resolution: 1920x1080~60Hz
OpenGL: renderer: NV117 v: 4.3 Mesa 18.2.6 direct render: Yes
Audio: Device-1: NVIDIA driver: snd_hda_intel v: kernel bus ID: 09:00.1
Device-2: AMD driver: snd_hda_intel v: kernel bus ID: 0b:00.3
Sound Server: ALSA v: k4.19.0-1-amd64
Network: Device-1: Intel I211 Gigabit Network driver: igb v: 5.4.0-k port: e000
bus ID: 07:00.0
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives: Local Storage: total: 698.65 GiB used: 147.41 GiB (21.1%)
ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO 250GB size: 232.89 GiB
ID-2: /dev/sda vendor: Samsung model: SSD 860 EVO 500GB size: 465.76 GiB
Partition: ID-1: / size: 47.81 GiB used: 5.47 GiB (11.4%) fs: ext4 dev: /dev/nvme0n1p2
ID-2: swap-1 size: 15.62 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/nvme0n1p5
Sensors: System Temperatures: cpu: 31.9 C mobo: N/A gpu: nouveau temp: 33 C
Fan Speeds (RPM): cpu: 0 gpu: nouveau fan: 1080
Repos: Active apt repos in: /etc/apt/sources.list.d/antix.list
1: deb http://mirrors.rit.edu/mxlinux/mx-packages/antix/stretch/ stretch main
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://ftp.us.debian.org/debian/ stretch-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://ftp.us.debian.org/debian/ stretch main contrib non-free
2: deb http://security.debian.org/ stretch/updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/google-chrome.list
1: deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ stretch main non-free
No active apt repos in: /etc/apt/sources.list.d/various.list
Info: Processes: 295 Uptime: 43m Memory: 15.66 GiB used: 3.31 GiB (21.1%) Init: SysVinit
runlevel: 5 Compilers: gcc: 6.3.0 Shell: bash v: 4.4.12 inxi: 3.0.25
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 8:46 am
by Gerson
I installed the beta MX-18 on the installation of MX-17.1 keeping only the /home, it took 11 minutes and it works fine.
I did not like the Plymouth they chose and I have a doubt about the last item in the choice of partitions. I do not know what to place if MX is the only system I use.
It's something new for me, the "boot".
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 9:06 am
by richb
You can choose a different Plymouth splash screen with MX Boot Options. As I am sure you can appreciate tastes vary and all cannot be pleased. That is why an option is provided.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 9:48 am
by chrispop99
Currently, Package Installer>Popular Applications tab does not show currently installed kernel.
(I understand why, but users used to seeing it there might not.)
Chris
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 10:01 am
by Eadwine Rose
Tried installing Nvidia using the MX setup option.
Haven't done anything else yet, not even reloaded synaptic or anything. Only disabled the splash screen and set things to very detailed.
Code: Select all
About to execute /usr/local/bin/ddm-mx -i nvidia.
This command needs root privileges to be executed.
Using su...
Enter root password at prompt.
Password:
creating lock ...
===================================
Install drivers for: nvidia
Start at (m/d/y): 12/03/2018 15:57:29
===================================
Candidate is: 384.130-1
Installed is: (none)
Would you like to check debian-backports for a later version?
Yes or No?
1: Yes
2: No
Enter Number of selection
2
Ok...
Candidate is: 384.130-1
Installed is: (none)
Need driver: nvidia-driver (384.130-1)
packages to install are nvidia-driver nvidia-settings nvidia-kernel-dkms libnvidia-encode1 nvidia-xconfig
Continue?
1) yes (default)
2) no
Press <Enter> for the default entry
Use 'q' to quit
1
Frontend:
Nvidia command = apt-get install --reinstall -y --force-yes nvidia-driver nvidia-settings nvidia-kernel-dkms libnvidia-encode1 nvidia-xconfig
Reading package lists...
Building dependency tree...
Reading state information...
Reinstallation of linux-headers-4.19.0-1-amd64 is not possible, it cannot be downloaded.
Reinstallation of firmware-linux-nonfree is not possible, it cannot be downloaded.
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 1 not upgraded.
Need to get 0 B/7,346 B of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 324469 files and directories currently installed.)
Preparing to unpack .../build-essential_12.3_amd64.deb ...
Unpacking build-essential (12.3) over (12.3) ...
Setting up build-essential (12.3) ...
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
libnvidia-encode1 : Depends: libcuda1 (= 384.130-1) but it is not going to be installed
Depends: libnvcuvid1 (>= 260) but it is not going to be installed
nvidia-driver : Depends: nvidia-driver-libs (= 384.130-1) but it is not going to be installed or
nvidia-driver-libs-nonglvnd (= 384.130-1) but it is not going to be installed
Depends: nvidia-driver-bin (= 384.130-1) but it is not going to be installed
Depends: xserver-xorg-video-nvidia (= 384.130-1) but it is not going to be installed
Depends: nvidia-vdpau-driver (= 384.130-1) but it is not going to be installed
Depends: nvidia-alternative (= 384.130-1)
Recommends: nvidia-persistenced
nvidia-kernel-dkms : Depends: nvidia-kernel-support--v1
nvidia-settings : Depends: nvidia-alternative
Depends: libxnvctrl0 (= 384.111-1~deb9u1) but 390.67-1~mx17+1 is to be installed
Recommends: libgl1-nvidia-glvnd-glx but it is not going to be installed or
libgl1-nvidia-glx but it is not going to be installed
Recommends: nvidia-vdpau-driver but it is not going to be installed
Recommends: libnvidia-ml1 but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
/usr/local/bin/ddm-mx: line 472: creating /etc/X11/xorg.conf file: No such file or directory
/usr/local/bin/ddm-mx: line 473: nvidia-xconfig: command not found
Finished
Press <Enter> to exit
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 10:04 am
by Eadwine Rose
Second try, attempting backports and installing that...
Code: Select all
About to execute /usr/local/bin/ddm-mx -i nvidia.
This command needs root privileges to be executed.
Using su...
Enter root password at prompt.
Password:
creating lock ...
===================================
Install drivers for: nvidia
Start at (m/d/y): 12/03/2018 16:02:15
===================================
Candidate is: 384.130-1
Installed is: (none)
Would you like to check debian-backports for a later version?
Yes or No?
1: Yes
2: No
Enter Number of selection
1
Ok...
Enabling backports repo
Running apt-get update...
Hit:1 http://ftp.nl.debian.org/debian stretch-updates InRelease
Hit:2 http://nl.mxrepo.com/antix/stretch stretch InRelease
Hit:3 http://nl.mxrepo.com/mx/repo stretch InRelease
Get:4 http://ftp.debian.org/debian stretch-backports InRelease [91.8 kB]
Ign:5 http://ftp.nl.debian.org/debian stretch InRelease
Hit:6 http://ftp.nl.debian.org/debian stretch Release
Hit:7 http://security-cdn.debian.org stretch/updates InRelease
Get:8 http://ftp.debian.org/debian stretch-backports/main i386 Packages [509 kB]
Get:9 http://ftp.debian.org/debian stretch-backports/main amd64 Packages [515 kB]
Get:10 http://ftp.debian.org/debian stretch-backports/main Translation-en [393 kB]
Get:11 http://ftp.debian.org/debian stretch-backports/contrib i386 Packages [7,252 B]
Get:12 http://ftp.debian.org/debian stretch-backports/contrib amd64 Packages [7,620 B]
Get:13 http://ftp.debian.org/debian stretch-backports/contrib Translation-en [6,233 B]
Get:14 http://ftp.debian.org/debian stretch-backports/non-free amd64 Packages [29.1 kB]
Get:15 http://ftp.debian.org/debian stretch-backports/non-free i386 Packages [19.4 kB]
Get:16 http://ftp.debian.org/debian stretch-backports/non-free Translation-en [33.8 kB]
Fetched 1,611 kB in 1s (1,161 kB/s)
Reading package lists...
Installing latest nvidia-detect package
Reading package lists...
Building dependency tree...
Reading state information...
The following packages will be upgraded:
nvidia-detect
1 upgraded, 0 newly installed, 0 to remove and 119 not upgraded.
Need to get 193 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://ftp.debian.org/debian stretch-backports/non-free amd64 nvidia-detect amd64 390.87-2~bpo9+1 [193 kB]
Fetched 193 kB in 0s (3,056 kB/s)
(Reading database ... 324469 files and directories currently installed.)
Preparing to unpack .../nvidia-detect_390.87-2~bpo9+1_amd64.deb ...
Unpacking nvidia-detect (390.87-2~bpo9+1) over (390.87-2~bpo9+1~mx17+2) ...
Setting up nvidia-detect (390.87-2~bpo9+1) ...
Main repo candidate is: 384.130-1
Debian backports candidate is: 390.87-2~bpo9+1
Installed is: (none)
Which driver do you wish to install
Main repos or debian-backports?
1: Main 384.130-1
2: debian-backports 390.87-2~bpo9+1
3: Exit
Enter Number of selection
2
Ok...
Need driver: nvidia-driver (390.87-2~bpo9+1)
packages to install are nvidia-driver nvidia-settings nvidia-kernel-dkms libnvidia-encode1 nvidia-xconfig
Continue?
1) yes (default)
2) no
Press <Enter> for the default entry
Use 'q' to quit
1
Frontend:
Nvidia command = apt-get install --reinstall -y --force-yes -t stretch-backports nvidia-driver nvidia-settings nvidia-kernel-dkms libnvidia-encode1 nvidia-xconfig
Reading package lists...
Building dependency tree...
Reading state information...
Reinstallation of linux-headers-4.19.0-1-amd64 is not possible, it cannot be downloaded.
Reinstallation of firmware-linux-nonfree is not possible, it cannot be downloaded.
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 1 not upgraded.
Need to get 0 B/7,346 B of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 324469 files and directories currently installed.)
Preparing to unpack .../build-essential_12.3_amd64.deb ...
Unpacking build-essential (12.3) over (12.3) ...
Setting up build-essential (12.3) ...
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
nvidia-settings : Depends: libxnvctrl0 (= 390.48-2~bpo9+1) but 390.67-1~mx17+1 is to be installed
E: Unable to correct problems, you have held broken packages.
/usr/local/bin/ddm-mx: line 472: creating /etc/X11/xorg.conf file: No such file or directory
/usr/local/bin/ddm-mx: line 473: nvidia-xconfig: command not found
Finished
Hit:1 http://nl.mxrepo.com/antix/stretch stretch InRelease
Hit:2 http://nl.mxrepo.com/mx/repo stretch InRelease
Hit:3 http://ftp.nl.debian.org/debian stretch-updates InRelease
Ign:4 http://ftp.nl.debian.org/debian stretch InRelease
Hit:6 http://ftp.nl.debian.org/debian stretch Release
Hit:5 http://security-cdn.debian.org stretch/updates InRelease
Reading package lists... Done
Press <Enter> to exit
Nope... trying that bit again and then keeping the version 384..
Hmm wait.. nvidia detect is already at that latest 390 one.. rebooting and see...
Nope, no such luck:
Code: Select all
System: Host: mx18b1 Kernel: 4.19.0-1-amd64 x86_64 bits: 64 compiler: gcc v: 6.3.0
Desktop: Xfce 4.12.3 Distro: MX-18b1_x64 Continuum December 3 2018
base: Debian GNU/Linux 9 (stretch)
Machine: Type: Desktop Mobo: ASUSTeK model: M4A785TD-V EVO v: Rev X.0x serial: <filter>
BIOS: American Megatrends v: 2005 date: 04/15/2010
Battery: Device-1: hidpp_battery_0 model: Logitech MX Ergo Multi-Device Trackball
charge: Normal status: Discharging
CPU: Topology: Quad Core model: AMD Athlon II X4 635 bits: 64 type: MCP arch: K10 rev: 3
L2 cache: 2048 KiB
flags: lm nx pae sse sse2 sse3 sse4a svm bogomips: 23304
Speed: 800 MHz min/max: 800/2900 MHz Core speeds (MHz): 1: 800 2: 800 3: 2900 4: 2900
Graphics: Device-1: NVIDIA GK208 [GeForce GT 640 Rev. 2] driver: nouveau v: kernel
bus ID: 01:00.0
Display: x11 server: X.Org 1.19.2 driver: nouveau unloaded: fbdev,modesetting,vesa
resolution: 1920x1080~60Hz
OpenGL: renderer: NV108 v: 4.3 Mesa 18.2.6 direct render: Yes
Audio: Device-1: AMD SBx00 Azalia driver: snd_hda_intel v: kernel bus ID: 00:14.2
Device-2: NVIDIA GK208 HDMI/DP Audio driver: snd_hda_intel v: kernel bus ID: 01:00.1
Device-3: Brooktree Bt878 Video Capture driver: bttv v: 0.9.19 bus ID: 03:06.0
Device-4: Brooktree Bt878 Audio Capture driver: snd_bt87x v: kernel bus ID: 03:06.1
Device-5: Logitech QuickCam E 3500 type: USB driver: snd-usb-audio,uvcvideo
bus ID: 1-1:2
Sound Server: ALSA v: k4.19.0-1-amd64
Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169
v: kernel port: d800 bus ID: 02:00.0
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: Ralink MT7601U Wireless Adapter type: USB driver: mt7601u bus ID: 2-2:3
IF: wlan0 state: down mac: <filter>
Drives: Local Storage: total: 1.37 TiB used: 4.87 GiB (0.3%)
ID-1: /dev/sda vendor: Hitachi model: HDP725050GLA360 size: 465.76 GiB
ID-2: /dev/sdb type: USB vendor: Western Digital model: WD My Passport 25E1
size: 931.48 GiB
ID-3: /dev/sdc type: USB model: USB DISK 2.0 size: 3.73 GiB
Partition: ID-1: / size: 455.45 GiB used: 4.87 GiB (1.1%) fs: ext4 dev: /dev/sda1
ID-2: swap-1 size: 2.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2
Sensors: System Temperatures: cpu: 22.5 C mobo: N/A gpu: nouveau temp: 36 C
Fan Speeds (RPM): N/A
Repos: Active apt repos in: /etc/apt/sources.list.d/antix.list
1: deb http://nl.mxrepo.com/antix/stretch stretch main
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://ftp.nl.debian.org/debian/ stretch-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://ftp.nl.debian.org/debian/ stretch main contrib non-free
2: deb http://security.debian.org/ stretch/updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://nl.mxrepo.com/mx/repo/ stretch main non-free
No active apt repos in: /etc/apt/sources.list.d/various.list
Info: Processes: 201 Uptime: 1m Memory: 7.79 GiB used: 452.4 MiB (5.7%) Init: SysVinit
runlevel: 5 Compilers: gcc: 6.3.0 Shell: bash v: 4.4.12 inxi: 3.0.25
Nope..
Code: Select all
About to execute /usr/local/bin/ddm-mx -i nvidia.
This command needs root privileges to be executed.
Using su...
Enter root password at prompt.
Password:
creating lock ...
===================================
Install drivers for: nvidia
Start at (m/d/y): 12/03/2018 16:09:08
===================================
Candidate is: 384.130-1
Installed is: (none)
Would you like to check debian-backports for a later version?
Yes or No?
1: Yes
2: No
Enter Number of selection
1
Ok...
Enabling backports repo
Running apt-get update...
Hit:1 http://nl.mxrepo.com/antix/stretch stretch InRelease
Hit:2 http://nl.mxrepo.com/mx/repo stretch InRelease
Get:3 http://ftp.debian.org/debian stretch-backports InRelease [91.8 kB]
Hit:4 http://ftp.nl.debian.org/debian stretch-updates InRelease
Ign:5 http://ftp.nl.debian.org/debian stretch InRelease
Hit:6 http://ftp.nl.debian.org/debian stretch Release
Hit:7 http://security-cdn.debian.org stretch/updates InRelease
Get:8 http://ftp.debian.org/debian stretch-backports/main i386 Packages [509 kB]
Get:9 http://ftp.debian.org/debian stretch-backports/main amd64 Packages [515 kB]
Get:10 http://ftp.debian.org/debian stretch-backports/main Translation-en [393 kB]
Get:11 http://ftp.debian.org/debian stretch-backports/contrib i386 Packages [7,252 B]
Get:12 http://ftp.debian.org/debian stretch-backports/contrib amd64 Packages [7,620 B]
Get:13 http://ftp.debian.org/debian stretch-backports/contrib Translation-en [6,233 B]
Get:14 http://ftp.debian.org/debian stretch-backports/non-free amd64 Packages [29.1 kB]
Get:15 http://ftp.debian.org/debian stretch-backports/non-free i386 Packages [19.4 kB]
Get:16 http://ftp.debian.org/debian stretch-backports/non-free Translation-en [33.8 kB]
Fetched 1,611 kB in 1s (1,146 kB/s)
Reading package lists...
Installing latest nvidia-detect package
Reading package lists...
Building dependency tree...
Reading state information...
nvidia-detect is already the newest version (390.87-2~bpo9+1).
0 upgraded, 0 newly installed, 0 to remove and 119 not upgraded.
Main repo candidate is: 384.130-1
Debian backports candidate is: 390.87-2~bpo9+1
Installed is: (none)
Which driver do you wish to install
Main repos or debian-backports?
1: Main 384.130-1
2: debian-backports 390.87-2~bpo9+1
3: Exit
Enter Number of selection
1
Ok...
Need driver: nvidia-driver (390.87-2~bpo9+1)
packages to install are nvidia-driver nvidia-settings nvidia-kernel-dkms libnvidia-encode1 nvidia-xconfig
Continue?
1) yes (default)
2) no
Press <Enter> for the default entry
Use 'q' to quit
Frontend:
Nvidia command = apt-get install --reinstall -y --force-yes nvidia-driver nvidia-settings nvidia-kernel-dkms libnvidia-encode1 nvidia-xconfig
Reading package lists...
Building dependency tree...
Reading state information...
Reinstallation of linux-headers-4.19.0-1-amd64 is not possible, it cannot be downloaded.
Reinstallation of firmware-linux-nonfree is not possible, it cannot be downloaded.
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 1 not upgraded.
Need to get 0 B/7,346 B of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 324469 files and directories currently installed.)
Preparing to unpack .../build-essential_12.3_amd64.deb ...
Unpacking build-essential (12.3) over (12.3) ...
Setting up build-essential (12.3) ...
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
libnvidia-encode1 : Depends: libcuda1 (= 384.130-1) but it is not going to be installed
Depends: libnvcuvid1 (>= 260) but it is not going to be installed
nvidia-driver : Depends: nvidia-driver-libs (= 384.130-1) but it is not going to be installed or
nvidia-driver-libs-nonglvnd (= 384.130-1) but it is not going to be installed
Depends: nvidia-driver-bin (= 384.130-1) but it is not going to be installed
Depends: xserver-xorg-video-nvidia (= 384.130-1) but it is not going to be installed
Depends: nvidia-vdpau-driver (= 384.130-1) but it is not going to be installed
Depends: nvidia-alternative (= 384.130-1)
Recommends: nvidia-persistenced
nvidia-kernel-dkms : Depends: nvidia-kernel-support--v1
nvidia-settings : Depends: nvidia-alternative
Depends: libxnvctrl0 (= 384.111-1~deb9u1) but 390.67-1~mx17+1 is to be installed
Recommends: libgl1-nvidia-glvnd-glx but it is not going to be installed or
libgl1-nvidia-glx but it is not going to be installed
Recommends: nvidia-vdpau-driver but it is not going to be installed
Recommends: libnvidia-ml1 but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
/usr/local/bin/ddm-mx: line 472: creating /etc/X11/xorg.conf file: No such file or directory
/usr/local/bin/ddm-mx: line 473: nvidia-xconfig: command not found
Finished
Hit:1 http://nl.mxrepo.com/antix/stretch stretch InRelease
Hit:2 http://nl.mxrepo.com/mx/repo stretch InRelease
Hit:3 http://ftp.nl.debian.org/debian stretch-updates InRelease
Ign:4 http://ftp.nl.debian.org/debian stretch InRelease
Hit:5 http://ftp.nl.debian.org/debian stretch Release
Hit:6 http://security-cdn.debian.org stretch/updates InRelease
Reading package lists... Done
Press <Enter> to exit
Let's see what synaptic is saying about those broken things..
nothing except mx welcome that can be upgraded.
Color me confused.
Going back to my 17.1 install now.. I gots other stuff to do
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 10:19 am
by dolphin_oracle
I guess the nvidia drivers won't update till we migrate the new stuff to main.
Im more concerned with why you couldn't make an usb with mx-LUM
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 10:22 am
by Eadwine Rose
I have no idea.. it didn't work with either usb stick.. is there a log file somewhere.. should be on the system I am in now.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 10:24 am
by sdibaja
first run, tried to install Mate from the MX Package Installer
unmet dependencies:
mate-core: Depends: mate-desktop-environment-core ........
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 11:59 am
by Richard
@Gerson,
just leave boot set to root
that is where it has always been.
Some people and servers like to use a separate boot partition,
but I think you'd need to create a /boot if you wanted to use one.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 12:10 pm
by Gaer Boy
Live usb booted OK and went straight to install on SSD. Halfway through install notifier showed 1 update - mx-welcome. Ignored it. Did not install grub - booted MX-17 to update grub, then booted 18 Beta. Boot failed early. screen messages far more voluble that previously, but the final ones were:
Code: Select all
Running /script/init-bottom failed. No such file or directory.
mounting /run on /root/run failed.
Target filesystem doesn't have requested /sbin/init.
No init found.
ISO md5 is OK. No other oddities seen.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 12:18 pm
by dolphin_oracle
Gaer Boy wrote: Mon Dec 03, 2018 12:10 pm
Live usb booted OK and went straight to install on SSD. Halfway through install notifier showed 1 update - mx-welcome. Ignored it. Did not install grub - booted MX-17 to update grub, then booted 18 Beta. Boot failed early. screen messages far more voluble that previously, but the final ones were:
Code: Select all
Running /script/init-bottom failed. No such file or directory.
mounting /run on /root/run failed.
Target filesystem doesn't have requested /sbin/init.
No init found.
ISO md5 is OK. No other oddities seen.
did you enable any encryption options?
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 12:25 pm
by Gaer Boy
No - accepted most defaults.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 12:27 pm
by dolphin_oracle
Gaer Boy wrote: Mon Dec 03, 2018 12:25 pm
No - accepted most defaults.
can you post the grub entry that you used to launch the installed system?
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 12:43 pm
by Gaer Boy
From grub.cfg
Code: Select all
menuentry 'MX 18 Continuum (18) (on /dev/sdb5)' --class mx --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-8a1b6bd1-cadd-4fce-8bb3-37f3d76fc534' {
insmod part_gpt
insmod ext2
set root='hd1,gpt5'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt5 --hint-efi=hd1,gpt5 --hint-baremetal=ahci1,gpt5 8a1b6bd1-cadd-4fce-8bb3-37f3d76fc534
else
search --no-floppy --fs-uuid --set=root 8a1b6bd1-cadd-4fce-8bb3-37f3d76fc534
fi
linux /boot/vmlinuz-4.19.0-1-amd64 root=/dev/sdb5
initrd /boot/initrd.img-4.19.0-1-amd64
}
I forgot to mention it's a UEFI boot.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 12:51 pm
by richb
Beta 1 installed and runs fine. However it did not create a grub entry for a previously installed encrypted alpha on another internal drive. Is it because it is encrypted? It did create an entry for MX 17.1 on a third internal drive. Same happened in an alpha install but thought it was an anomaly and did not report it.
PS It is an updated MX 17 beta 3 to final.
The encrypted drive can be accessed with thunar, and shows in disk manager.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 12:53 pm
by dolphin_oracle
richb wrote: Mon Dec 03, 2018 12:51 pm
Beta 1 installed and runs fine. However it did not create a grub entry for a previously installed encrypted alpha on another internal drive. It did create an entry for MX 17.1 on a third internal drive. Same happened in an alpha install but thought it was an anomaly and did not report it.
PS It is an updated MX 17 beta 3 to final.
The encrypted drive can be accessed with thunar, and shows in disk manager.
looks like you wiped out the boot partition at some point. that's what the os-prober will pick up.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 12:55 pm
by richb
dolphin_oracle wrote: Mon Dec 03, 2018 12:53 pm
richb wrote: Mon Dec 03, 2018 12:51 pm
Beta 1 installed and runs fine. However it did not create a grub entry for a previously installed encrypted alpha on another internal drive. It did create an entry for MX 17.1 on a third internal drive. Same happened in an alpha install but thought it was an anomaly and did not report it.
PS It is an updated MX 17 beta 3 to final.
The encrypted drive can be accessed with thunar, and shows in disk manager.
looks like you wiped out the boot partition at some point. that's what the os-prober will pick up.
I thought that was sdc1. the first entry that has a boot flag
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 12:59 pm
by dolphin_oracle
richb wrote: Mon Dec 03, 2018 12:55 pm
dolphin_oracle wrote: Mon Dec 03, 2018 12:53 pm
richb wrote: Mon Dec 03, 2018 12:51 pm
Beta 1 installed and runs fine. However it did not create a grub entry for a previously installed encrypted alpha on another internal drive. It did create an entry for MX 17.1 on a third internal drive. Same happened in an alpha install but thought it was an anomaly and did not report it.
PS It is an updated MX 17 beta 3 to final.
The encrypted drive can be accessed with thunar, and shows in disk manager.
looks like you wiped out the boot partition at some point. that's what the os-prober will pick up.
I thought that was sdc1. the first entry that has a boot flag
that's the ESP for uefi boots. different thing the /boot.
also, without an uncrypted /boot (like the installer requires), os-prober has no way to know what's in an encrypted partition, so they won't be picked up. not being able to tell what's in an encrypted partition is kind of the point.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 1:00 pm
by dolphin_oracle
Gaer Boy wrote: Mon Dec 03, 2018 12:43 pm
From grub.cfg
Code: Select all
menuentry 'MX 18 Continuum (18) (on /dev/sdb5)' --class mx --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-8a1b6bd1-cadd-4fce-8bb3-37f3d76fc534' {
insmod part_gpt
insmod ext2
set root='hd1,gpt5'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt5 --hint-efi=hd1,gpt5 --hint-baremetal=ahci1,gpt5 8a1b6bd1-cadd-4fce-8bb3-37f3d76fc534
else
search --no-floppy --fs-uuid --set=root 8a1b6bd1-cadd-4fce-8bb3-37f3d76fc534
fi
linux /boot/vmlinuz-4.19.0-1-amd64 root=/dev/sdb5
initrd /boot/initrd.img-4.19.0-1-amd64
}
I forgot to mention it's a UEFI boot.
can you try setting your
to
Code: Select all
root=UUID=Actual_UUID_Of_The_Device_here
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 1:03 pm
by richb
shoot wrong image posted. That drive does have an entry, this one does not.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 1:06 pm
by dolphin_oracle
in that case...don't know.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 1:13 pm
by Gaer Boy
The boot edit worked fine - posting from MX-18 Beta now. I have 10 minutes to look around.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 1:14 pm
by richb
dolphin_oracle wrote: Mon Dec 03, 2018 1:06 pm
in that case...don't know.
I do not need that install. I just posted in case it was an issue "seeing" an encrypted drive if grub was re-wriiten by another OS.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 1:26 pm
by Stevo
Those trying to install the Nvidia drivers might try enabling the test repository in Synaptic, then running ddm-mx to install. We have the 390.87 drivers there also that you need to be able to build on the 4.19 kernel.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 1:30 pm
by chrispop99
(Trivial)
Using the Package Installer to add 'HP Printing' adds an entry to Settings, but it has no icon. This was the same in MX-17.
Chris
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 1:33 pm
by Gordon Cooper
I see comments about MX-18 Beta, but where is it ? Is there a release note somewhere ?
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 1:36 pm
by Richard
In the other thread about MX-18 beta 1
viewtopic.php?f=131&t=47190
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 1:39 pm
by Gordon Cooper
Thanks Richard. Found it down the list.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 2:02 pm
by freefreeno
Will we be able to go from testing version to regular when time comes??
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 2:03 pm
by Eadwine Rose
Works fine for me:
https://sourceforge.net/projects/mx-lin ... ting/MX18/
Here is the link to the download area.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 2:05 pm
by dolphin_oracle
freefreeno wrote: Mon Dec 03, 2018 2:02 pm
Will we be able to go from testing version to regular when time comes??
its not officially supported from beta just because there is always the potential for some major change somewhere, but for the most part yes once we migrate our dev repo to main. but the beta will always report itself as a beta in "inxi" output.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 2:09 pm
by richb
chrispop99 wrote: Mon Dec 03, 2018 1:30 pm
(Trivial)
Using the Package Installer to add 'HP Printing' adds an entry to Settings, but it has no icon. This was the same in MX-17.
Chris
Confirmed.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 2:11 pm
by danielson
Snapiest MX yet!
Installation went under 7 minutes for sure!
Sleep mode isn't working for me.
Have to do hard shutdown and reboot.
$ inxi -F
System: Host: Kernel: 4.19.0-1-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3
Distro: MX-18b1_x64 Continuum December 3 2018
Machine: Type: Laptop System: Hewlett-Packard product: HP EliteBook 8460p v: A0001D02
serial: <root required>
Mobo: Hewlett-Packard model: 161C v: KBC Version 97.4E serial: <root required>
BIOS: Hewlett-Packard v: 68SCF Ver. F.65 date: 04/06/2017
Battery: ID-1: BAT0 charge: 39.3 Wh condition: 39.6/39.6 Wh (100%)
CPU: Topology: Dual Core model: Intel Core i5-2520M bits: 64 type: MT MCP
L2 cache: 3072 KiB
Speed: 798 MHz min/max: 800/3200 MHz Core speeds (MHz): 1: 798 2: 798 3: 798 4: 798
Graphics: Device-1: AMD Seymour [Radeon HD 6400M/7400M Series] driver: radeon v: kernel
Display: x11 server: X.Org 1.19.2 driver: ati,radeon unloaded: fbdev,modesetting,vesa
resolution: 1600x900~60Hz, 1680x1050~60Hz
OpenGL: renderer: AMD CAICOS (DRM 2.50.0 / 4.19.0-1-amd64 LLVM 7.0.0)
v: 3.3 Mesa 18.2.6
Audio: Device-1: Intel 6 Series/C200 Series Family High Definition Audio
driver: snd_hda_intel
Device-2: Logitech Headset H390 type: USB driver: hid-generic,snd-usb-audio,usbhid
Sound Server: ALSA v: k4.19.0-1-amd64
Network: Device-1: Intel 82579LM Gigabit Network driver: e1000e
IF: eth0 state: down mac: e4:11:5b:26:66:28
Device-2: Intel Centrino Advanced-N 6205 [Taylor Peak] driver: iwlwifi
IF: wlan0 state: down mac: ea:f2:00:39:f7:c4
Device-3: ASIX AX88772B type: USB driver: asix
IF: eth1 state: up speed: 100 Mbps duplex: full mac: 00:50:b6:23:18:cc
Drives: Local Storage: total: 223.57 GiB used: 9.14 GiB (4.1%)
ID-1: /dev/sda vendor: PNY model: CS1311 240GB SSD size: 223.57 GiB
Partition: ID-1: / size: 53.15 GiB used: 9.14 GiB (17.2%) fs: ext4 dev: /dev/sda3
Sensors: System Temperatures: cpu: 46.0 C mobo: N/A gpu: radeon temp: 44 C
Fan Speeds (RPM): N/A
Info: Processes: 193 Uptime: 7m Memory: 15.62 GiB used: 1.14 GiB (7.3%) Shell: bash
inxi: 3.0.25
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 2:23 pm
by Stevo
sdibaja wrote: Mon Dec 03, 2018 10:24 am
first run, tried to install Mate from the MX Package Installer
unmet dependencies:
mate-core: Depends: mate-desktop-environment-core ........
This is because the development repo that contains the newer libglib2.0-bin than mate-control-center requires was disabled on this beta. You will be able to install MATE when we move the dev repo stuff to main.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 2:47 pm
by sdibaja
Stevo wrote: Mon Dec 03, 2018 2:23 pm
sdibaja wrote: Mon Dec 03, 2018 10:24 am
first run, tried to install Mate from the MX Package Installer
unmet dependencies:
mate-core: Depends: mate-desktop-environment-core ........
This is because the development repo that contains the newer libglib2.0-bin than mate-control-center requires was disabled on this beta. You will be able to install MATE when we move the dev repo stuff to main.
Ok, thanks
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 2:59 pm
by bigbenaugust
Installing the beta in a VM now. I'll be excited to slap this on a work machine it goes gold.
... looks good, used LUKS/LVM on a DOS partition set up.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 3:30 pm
by Gordon Cooper
Good that other users are succeeding. I have hmade 5 attempts to download MX-18 from Source Forge, each one failed before completion. Will for America to go to bed then try again.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 3:43 pm
by Eadwine Rose
Have you clicked the "problems downloading" button?
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 3:47 pm
by Gordon Cooper
@ ER Yes, tried a closer mirror, and two different machines here. Each time the download gets within a few second of the finish, then stalls and eventually fails.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 3:49 pm
by Eadwine Rose
How annoying!!
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 3:52 pm
by old_guy
Wine
Tried to install from MXPI and got:
...
unmet dependencies:
winehq-staging : Depends: wine-staging (=2.21-1mx17+1)
E: Unable to correct problems, you have held broken packages
earl
bash: winecfg: command not found
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 4:38 pm
by yonosoyesa
Still buggy Thunar 1.6.12!!
MX 18 could be a good opportunity to update Thunar to 1.6.15 that is working beautifully in my MX 17 since last June.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 4:45 pm
by Mauser
I was just checking out MX-18 beta 1 and so far looks great except I found that password box is an inconsistent strange size on MX-18 as it was in MX-17.1 when you right click on the update icon and select check updates opposed to left clicking on it. I wasn't able to do a screen shot on MX-18 but I show you what I mean on MX-17.1 since it's the same inconsistency. Resizing it to match all the password boxes would give MX-18 a spit shine polish. The top picture shows the weird odd size while the bottom picture shows the correct size.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 4:57 pm
by Stevo
yonosoyesa wrote: Mon Dec 03, 2018 4:38 pm
Still buggy Thunar 1.6.12!!
MX 18 could be a good opportunity to update Thunar to 1.6.15 that is working beautifully in my MX 17 since last June.
I've just asked for 1.6.15 to be moved to main. Thanks for catching that!
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 4:59 pm
by manyroads
I installed on a VirtualBox using UEFI... the install and build went well; as did my customization. On reboot I have a complete and total crash. I will download and try again; as time permits.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 5:01 pm
by Stevo
Gordon Cooper wrote: Mon Dec 03, 2018 3:47 pm
@ ER Yes, tried a closer mirror, and two different machines here. Each time the download gets within a few second of the finish, then stalls and eventually fails.
I've just uploaded the 64-bit to archive.org:
https://archive.org/download/MX18b1X64
Also interested if the torrent they create actually works. Uploading 32-bit now.
Edit: 32-bit uploaded:
https://archive.org/details/MX18b1386.iso
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 5:10 pm
by sunrat
Not looking good for the torrent:
Code: Select all
Error: Requested download is not authorised for use with this tracker
Error shows in the "Trackers" tab of Ktorrent. Maybe it's not ready, will try again later.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 5:13 pm
by baldyeti
Hello, i tried i386 as i figured it might be getting less attention. Installed fine to HD AFAICT (pretty much all set to defaults)
only thing i noticed:
- grub did not initially create an entry for the windows install on the same HD. Running update-grub corrected this but it might scare a newbie
- got some warning that installing from the stick i had booted in UEFI would result in a non-bootable hard disk (mbr-partitioned). I proceeded anyway and it turned out the system boots just fine.
Not sure what else devs might be interested in, just let me know.
PS: Oh, and i wish the new release included some more of the fine wallpapers that were posted (but please include some abstract ones as well, sharp/pretty pictures are too distracting)
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 5:17 pm
by Jerry3904
The MX-18 Art work has mostly not been included in this beta
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 5:22 pm
by fehlix
sunrat wrote: Mon Dec 03, 2018 5:10 pm
Not looking good for the torrent:
Code: Select all
Error: Requested download is not authorised for use with this tracker
Error shows in the "Trackers" tab of Ktorrent. Maybe it's not ready, will try again later.
Looks very good. Just put the torrent link into transmssion:
Code: Select all
https://archive.org/download/MX18b1X64/MX18b1X64_archive.torrent
and it loads just fine - with full speed for me:
Torrents2.png
EDIT: and after a bit more than 4 minutes I got them all with on go:
Code: Select all
$ ls -nhl ./Torrents/MX18b1X64
insgesamt 1,3G
-rw-r--r-- 1 1000 1000 1,3G Dez 3 23:21 MX-18b1_x64.iso
-rw-r--r-- 1 1000 1000 50 Dez 3 23:16 MX-18b1_x64.iso.md5
-rw-r--r-- 1 1000 1000 82 Dez 3 23:16 MX-18b1_x64.iso.sha256
-rw-r--r-- 1 1000 1000 566 Dez 3 23:16 MX-18b1_x64.iso.sig
-rw-r--r-- 1 1000 1000 2,6M Dez 3 23:20 MX-18b1_x64.iso.zsync
-rw-r--r-- 1 1000 1000 16K Dez 3 23:16 MX18b1X64_meta.sqlite
-rw-r--r-- 1 1000 1000 742 Dez 3 23:16 MX18b1X64_meta.xml
and with a perfect validating signature too:
Code: Select all
#---------------------------------------------
gpgv --verbose MX-18b1_x64.iso.sig MX-18b1_x64.iso
#---------------------------------------------
gpgv: Signature made Mo 03 Dez 2018 02:48:14 CET
gpgv: using RSA key F62EDEAA3AE70A9C99DAC4189B68A1E8B9B6375C
gpgv: Good signature from "Dolphin Oracle (mxlinux) <dolphinoracle@gmail.com>"
gpgv: binary signature, digest algorithm SHA256, key algorithm rsa4096
#---------------- DONE ----------------------
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 5:31 pm
by dolphin_oracle
manyroads wrote: Mon Dec 03, 2018 4:59 pm
I installed on a VirtualBox using UEFI... the install and build went well; as did my customization. On reboot I have a complete and total crash. I will download and try again; as time permits.
keep in mind that Virtualbox UEFI does not emulate nvram necessary for a shtudown/reboot cycle to work. usually they can survive a reboot but once you shut them down, you have to use the Virtualbox boot manager to boot the EFI file manually, which isn't hard, but its not obvious (type exit a lot).
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 5:44 pm
by Stevo
fehlix wrote: Mon Dec 03, 2018 5:22 pm
(archive.org ISO torrent works great in Transmission)
Thanks for the test! Maybe it's just something with KTorrent, or it took a while to set up a tracker. It appears that archive.org sets up two full seeders for each torrent.
Edit: added a screenshot!
How? Just upload it with the rest of the files--or in this case, add it.
https://archive.org/details/MX18b1X64
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 6:00 pm
by rasat
I didn't install, just to check kernel 4.19 with UEFI. The install CD boots well in Inspiron 5567 (didn't work with 4.15, I was using 4.9).
Cosmetic comment: the blue wallpaper is beautiful.
I will wait for the final release.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 6:13 pm
by richb
rasat wrote: Mon Dec 03, 2018 6:00 pm
I didn't install, just to check kernel 4.19 with UEFI. The install CD boots well in Inspiron 5567 (didn't work with 4.15, I was using 4.9).
Cosmetic comment: the blue wallpaper is beautiful.
I will wait for the final release.
The wallpaper is thanks to antechdesigns who has contributed many fine wallpaper on the Community website.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 6:26 pm
by Richard
@Gordon,
Have you tried axel?
It has helped me overcome bad connections for several years.
axel -a "
https://sourceforge.net/projects/mx-lin ... o/download"
It will keep restarting for quite a few attemps.
If it seems hung, I stop it with Ctrl-c and then up arrow and enter to start it manually.
Usually no intervention is necessary but occasionally the internet here is not constant.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 6:56 pm
by kmathern
Mauser wrote: Mon Dec 03, 2018 4:45 pm
I was just checking out MX-18 beta 1 and so far looks great except I found that password box is an inconsistent strange size on MX-18 as it was in MX-17.1 when you right click on the update icon and select check updates opposed to left clicking on it. I wasn't able to do a screen shot on MX-18 but I show you what I mean on MX-17.1 since it's the same inconsistency. Resizing it to match all the password boxes would give MX-18 a spit shine polish. The top picture shows the weird odd size while the bottom picture shows the correct size.
Actually it's supposed look something like what's shown below for that dialog, but there was a coding error (that's been there for awhile) that I just found.
I just made a commit to fix it:
https://github.com/MX-Linux/apt-notifie ... 8c814bbfd1
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 7:03 pm
by manyroads
Hi all. I have run a 2nd test using my VirtualBox install and this time did NOT use UEFI.
The results are stellar thus far. I have reformatted almost everything including installation of the applications base I prefer... For giggles, I have included 2 screenshots.
MX18 beta1 -2.jpg
MX18 beta1 -1.jpg
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 7:14 pm
by Gordon Cooper
@ Richard. What I seem to have is a handshake problem with sourceforge. The downloads go quite well at about 5-6 minutes for the file until the very end. The progress monitor then says " A few seconds remaining" and the download comes to a grinding halt, then it times out. A failure. This happening on two computers, and just in case it was a bug in my MX-17.1, I stoked up MX15 and tried from there. Same thing happened. Also tried a download from Stevo's archive, same thing again. So the problem is not just with sourceforge. Somehow, the source is not being told that everything has been received. Also my download is marked as a part file and cannot be used.
Will try your suggestion of Ctrl-c etc. and report back.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 7:35 pm
by freefreeno
I have these screen shots showing that I am booting in uefi .I can't install because for some reason mx thinks I am in legacy but I am not. This is the same exact thing that has been going on with the MX installer before and why I was not on MX. I decided today to go ahead and install windows and use rufus to create my installer because that is only way I have ever gotten it to work on MX but now this. Funny thing about this is the usb booted while I had secure boot enabled. I had forgot it momentarly and some how it booted anyways.
https://imageshack.com/a/img922/339/Dy9UhV.png
https://imageshack.com/a/img921/7033/JpyX3L.png
https://imageshack.com/a/img921/4756/V8mc5v.png
https://imageshack.com/a/img923/715/g1hNTU.png I would love to figure this out once and for all. I know someone is gonna say disable uefi but the way I see that is if I am having problems then other people will also have problems and some people do not like installing stuff that either starts with a problem or either they dont want to live in the stone ages with legacy boot. I just want to figure out why the installer is not working properly.
I have spent hours trying to figure this out just today not counting other days.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 7:39 pm
by dolphin_oracle
Ok, the screenshots don't show any errors. what is the error you are getting?
and yes, the live media will boot with secure boot still on. this is actually a feature of secure boot and how it manages a "secure" boot chain.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 7:47 pm
by freefreeno
The screenshots show it all. Right where you see the screen offering boot option. That option shouldnt even be there at all if it has picked up that I am installing in uefi mode. (It is trying to install in mbr legacy mode and I am not in legacy boot. I am in uefi. It is trying to get me to add boot to root. ONLY OPTION FOR BOOT IS ROOT AND THAT IS LEGACY
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 7:49 pm
by Gordon Cooper
@ Richard. Nope, no joy so will abandon this and go do some real high tech work - in the galley, while I think about the problem
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 7:54 pm
by Stevo
Gordon Cooper wrote: Mon Dec 03, 2018 7:49 pm
@ Richard. Nope, no joy so will abandon this and go do some real high tech work - in the galley, while I think about the problem
Did you try the torrent from archive.org?
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 7:58 pm
by dolphin_oracle
freefreeno wrote: Mon Dec 03, 2018 7:47 pm
The screenshots show it all. Right where you see the screen offering boot option. That option shouldnt even be there at all if it has picked up that I am installing in uefi mode. (It is trying to install in mbr legacy mode and I am not in legacy boot. I am in uefi. It is trying to get me to add boot to root. ONLY OPTION FOR BOOT IS ROOT AND THAT IS LEGACY
no its not. that's the /boot partition, which can be a separate partition (this was a requested feature) and is also useful for encrypted boots the way we have it set up.
this would replace the /boot directory in the root partition the same way the /home partition replaces the /home directory in the root partition. /boot holds all the files for grub and the linux initrd components that don't go into either the mbr or the esps
looking at your system, you should see ESP as an option for grub installation at the grub install phase.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 8:02 pm
by freefreeno
That entire screen is different if it correctly picks up uefi or it was just a few day ago. If the installer hasn't changed then that is the legacy boot installer screen. I dont need legacy boot installer screen. I am booted in uefi so legacy installer shouldnt even be there. The installer changes a little betweeen the two modes if I am not mistaken . The 4th box on the choose the partitions screen will not be there if installing in uefi mode. Or like I said it wasnt the two or three times I have ever manged to get it installed. The only installer I have ever gotten to work in the stock mx 17 iso without the updates. The mx 17 iso with updates will not work so something changed and now I cant install apparently in uefi and I don't go for that give up and install how it forces me to stuff.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 8:04 pm
by fehlix
manyroads wrote: Mon Dec 03, 2018 4:59 pm
I installed on a VirtualBox using UEFI... the install and build went well; as did my customization. On reboot I have a complete and total crash. I will download and try again; as time permits.
One easy way to have MX18b1_x64 to get installed in Oracle VM VirtualBox UEFI mode together with
straight booting into the Grub-menu without any issues in UEFI mode:
Booting MX18-Linux in UEFI-mode in VirtualBox
This in UEFI install from the LiveISO on Oracle VM VirtualBox.
After installation, rebooting with VirtualBox internal boot menu by selecting manual /EFI/MX18/gubx64.efi.
Within booted MX18-Linux those additonal stepps need to be performed or verified:
1- check/create missing fstab-entry for ESP/efi partition
Code: Select all
echo "UUID=$(lsblk -no 'UUID,LABEL,FSTYPE,PARTLABEL' | grep -m1 -iE 'vfat|esp|efi' | cut -d' ' -f1) /boot/efi vfat defaults 0 0" | sudo tee -a /etc/fstab
UUID=A555-0A81 /boot/efi vfat defaults 0 0
Code: Select all
sudo "mkdir -p /boot/efi/EFI/BOOT && cp /boot/efi/EFI/MX18/grubx64.efi /boot/efi/EFI/BOOT/bootx64.efi"
That's it. Reboot and the Grub menu will show up.
Note: The above steps could also made within booted LiveISO or potentially as a nice adjustment to the existing installer.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 8:06 pm
by dolphin_oracle
freefreeno wrote: Mon Dec 03, 2018 8:02 pm
That entire screen is different if it correctly picks up uefi or it was just a few day ago. If the installer hasn't changed then that is the legacy boot installer screen. I dont need legacy boot installer screen. I am booted in uefi so legacy installer shouldnt even be there. The installer changes a little betweeen the two modes if I am not mistaken . The 4th box on the choose the partitions screen will not be there if installing in uefi mode. Or like I said it wasnt the two or three times I have ever manged to get it installed. The only installer I have ever gotten to work in the stock mx 17 iso without the updates. The mx 17 iso with updates will not work so something changed and now I cant install apparently in uefi and I don't go for that give up and install how it forces me to stuff.
the screens you post are not the legacy installer screens, they are the partition selection screens. this is the grub install screen, which you did not show a picture of in your post.
grub-install.png
actually the installer has changed a lot, adding encryption and such, and the parititon selection screen is the screen everyone will get. if /boot option should be present in all modes, as well as the new encryption options. If they are not, that's the bug.
the installer only changes in one place depending on UEFI vs. Legacy boot...at grub install screen.
and you don't have to use a separate /boot...just leave it set to root, which is where we've always had it in the past.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 8:08 pm
by freefreeno
Maybe this will help it is only offering sda2 for boot and that is my root. I tried just leaving it with an blue no boot device screen. Boot is already set on the root option when you get to that page. Nothing I can do about that.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 8:11 pm
by dolphin_oracle
freefreeno wrote: Mon Dec 03, 2018 8:08 pm
Maybe this will help it is only offering sda2 for boot and that is my root. I tried just leaving it with an blue no boot device screen.
it should be offering "root" as the default option, which sounds like what you want.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 8:15 pm
by dolphin_oracle
@freefreeno
I'm not saying there might not be some problem in the installer...but if so its not the problem you think it is, and maybe with some more screenshots or info we can work it out.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 8:23 pm
by Adrian
Maybe we need to explains things a bit better, I was not excited about adding /boot extra partition exactly for this reason...
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 8:29 pm
by fehlix
freefreeno wrote: Mon Dec 03, 2018 7:47 pm
The screenshots show it all. Right where you see the screen offering boot option. That option shouldnt even be there at all if it has picked up that I am installing in uefi mode. (It is trying to install in mbr legacy mode and I am not in legacy boot. I am in uefi. It is trying to get me to add boot to root. ONLY OPTION FOR BOOT IS ROOT AND THAT IS LEGACY
This is propably an misinterpretation. Where you mount or not mount the folder /boot (e.g. either keep it as a normal directory or have it mounted from extra "boot"-partition) has nothing todo with MBR/BIOS(legacy) or UEFI booting.
The finaly mounted directory structure ( "/, "/boot" and or "/boot/efi" ) is realy only for grub and kernel-booting, nothing todo with the underlying bootload-mechanism.
Please explain explicitly what issues you have, perhaps we can provide more clarity here.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 8:34 pm
by fehlix
freefreeno wrote: Mon Dec 03, 2018 8:08 pm
Maybe this will help it is only offering sda2 for boot and that is my root. I tried just leaving it with an blue no boot device screen. Boot is already set on the root option when you get to that page. Nothing I can do about that.
The default is not to have an extra "boot" partition (this is only defaulted/used for disk-encryted installation).
But you can manual create an extra "boot" partition if you like. The default installer just does not offer to create one.
As its is not needed, you can create one - or just simply leave the /boot directory unter the /root-partition
Thats it - simple and straight.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 8:57 pm
by Gordon Cooper
Stevo wrote: Mon Dec 03, 2018 7:54 pm
Did you try the torrent from archive.org?
Yes, I did tried with both Transmission and QbitTorrent. Downloaded the torrent file from the archive, no difficulty, but trying to progress , QbitTorrent's log said this
in red print:
"4/12/18 2:47 PM - URL seed lookup failed for URL: '/5/items/', message: MX18b1X64 url seed (/5/items/) failed: unsupported URL protocol"
URL looks OK to me.
Re: MX-18 beta 1 feedback-GRUB difficulties
Posted: Mon Dec 03, 2018 9:18 pm
by entropyfoe
First report:
Downloaded this morning from the forum announcement link.
I checked md5, was good, so I burned it to a USB with the Live USB creator tool on MX 17.1 .
Boots fast on this signature machine. Internet and sound worked, youtube worked, so I clicked install. As usual I divide my system disks into 4 partitions, three for a traditional Warren style install (/, swap, and separate home) and the fourth partition is an experimental partition for testing. So as usual (like I did with MX17 betas) installed to that P4 on the nvme drive. The progress bar stalls a bit at 95%, but then zooms to 99% and completion, about 4-5 minutes.
But I had problems with installing GRUB to root. The P4 never showed up in the installer window. I don't want to MBR, as that is my main MX 17.1 system. The installer asks "OK to install GRUB bootloader at ?", so maybe it is not seeing that 4th nvme partition for some reason. It offered the option to not install grub, complete installation, and then reboot and use the grub repair tool.
I set the timezones, clicked next, and the installer vanished ! (not sure what happened, did I press a wrong button??!!?!?)
So, I rebooted, and repeated everything the same, still the same GRUB error. But this time the installation went fine. I rebooted and tried the GRUB repair. Again it does not see P4 with the MX 18 install. I used disk manager to mount the 4th partition from live, and sure enough, the MX 18install was there.
So, I rebooted back to MX-17, and did update-grub as root. It found MX18 continuum(18). But this option would not be available to many users withoout another MX install on the same machine.
Then I rebooted again and selected MX 18 beta 1 from a normal MX 17 GRUB, and I am posting from it now.
I will play around some more and report back.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 9:28 pm
by Jerry3904
The installer asks "OK to install GRUB bootloader at ?"
I saw that too, and assumed a root slash was missing.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 9:30 pm
by Adrian
I set the timezones, clicked next, and the installer vanished ! (not sure what happened, did I press a wrong button??!!?!?)
Possibly an installer crash, it never happened to me at that step though... not sure what's went on.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 9:31 pm
by Adrian
Jerry3904 wrote: Mon Dec 03, 2018 9:28 pm
The installer asks "OK to install GRUB bootloader at ?"
I saw that too, and assumed a root slash was missing.
Probably missing a %1 tag or something, easy to fix.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 9:39 pm
by entropyfoe
I just grabbed 6 synaptic upgrades and added 26 packages.
Next I'll try and reboot, maybe try the nvidia installer.
Here's the HW info including the disks
Code: Select all
inxi -F
System: Host: Ryzen Kernel: 4.19.0-1-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3
Distro: MX-18b1_x64 Continuum December 3 2018
Machine: Type: Desktop Mobo: ASUSTeK model: PRIME X370-PRO v: Rev X.0x serial: <root required>
UEFI [Legacy]: American Megatrends v: 1201 date: 10/18/2017
CPU: Topology: 6-Core model: AMD Ryzen 5 1600X bits: 64 type: MT MCP L2 cache: 3072 KiB
Speed: 1884 MHz min/max: 2200/3600 MHz Core speeds (MHz): 1: 1887 2: 1888 3: 1886
4: 2049 5: 1887 6: 1891 7: 1877 8: 1874 9: 1904 10: 1883 11: 1888 12: 1893
Graphics: Device-1: NVIDIA GK208 [GeForce GT 710B] driver: nouveau v: kernel
Display: x11 server: X.Org 1.19.2 driver: nouveau unloaded: fbdev,modesetting,vesa
resolution: 1920x1080~60Hz
OpenGL: renderer: NV106 v: 4.3 Mesa 18.2.6
Audio: Device-1: NVIDIA GK208 HDMI/DP Audio driver: snd_hda_intel
Device-2: AMD driver: snd_hda_intel
Sound Server: ALSA v: k4.19.0-1-amd64
Network: Device-1: Intel I211 Gigabit Network driver: igb
IF: eth0 state: up speed: 100 Mbps duplex:
Drives: Local Storage: total: 1.14 TiB used: 5.02 GiB (0.4%)
ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 960 EVO 250GB size: 232.89 GiB
ID-2: /dev/sda vendor: Samsung model: SSD 850 EVO 1TB size: 931.51 GiB
Partition: ID-1: / size: 100.88 GiB used: 5.02 GiB (5.0%) fs: ext4 dev: /dev/nvme0n1p4
ID-2: swap-1 size: 16.60 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/nvme0n1p2
Sensors: System Temperatures: cpu: 32.2 C mobo: N/A gpu: nouveau temp: 44 C
Fan Speeds (RPM): cpu: 0
Info: Processes: 250 Uptime: 30m Memory: 15.66 GiB used: 1.12 GiB (7.1%) Shell: bash
inxi: 3.0.25
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 9:45 pm
by Adrian
Adrian wrote: Mon Dec 03, 2018 9:31 pm
Jerry3904 wrote: Mon Dec 03, 2018 9:28 pm
The installer asks "OK to install GRUB bootloader at ?"
I saw that too, and assumed a root slash was missing.
Probably missing a %1 tag or something, easy to fix.
Actually now, it probably doesn't find the boot partition for some reason, will investigate
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 10:00 pm
by asqwerth
Note that freefreeno states that his installer issues started with updates to mx17.
only installer I have ever gotten to work in the stock mx 17 iso without the updates. The mx 17 iso with updates will not work so something changed and now I cant install apparently in uefi and I don't go for that give up and install how it forces me to stuff.
The changes may have happened before the beta?
Also wonder if it might be the bios setting. Some machines have different settings for each device. E.g the main HDD or ssd may be set to boot UEFI first but USB stick is set to boot legacy first.
Might this confuse the installer?
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 10:13 pm
by entropyfoe
OK, first try at the MXPI nvidia installer,
Per a post earlier, I enabled the test repo in synaptic.
Fails out:
Code: Select all
Password:
creating lock ...
===================================
Install drivers for: nvidia
Start at (m/d/y): 12/03/2018 21:05:01
===================================
Candidate is: 384.130-1
Installed is: (none)
Would you like to check debian-backports for a later version?
Yes or No?
1: Yes
2: No
Enter Number of selection
1
Ok...
Enabling backports repo
Running apt-get update...
Hit:1 http://iso.mxrepo.com/antix/stretch stretch InRelease
Get:2 http://ftp.debian.org/debian stretch-backports InRelease [91.8 kB]
Get:3 http://ftp.debian.org/debian stretch-backports/main amd64 Packages [515 kB]
Get:4 http://ftp.debian.org/debian stretch-backports/main i386 Packages [509 kB]
Get:5 http://ftp.debian.org/debian stretch-backports/main Translation-en [393 kB]
Get:6 http://ftp.debian.org/debian stretch-backports/contrib amd64 Packages [7,620 B]
Get:7 http://ftp.debian.org/debian stretch-backports/contrib i386 Packages [7,252 B]
GePassword:
creating lock ...
===================================
Install drivers for: nvidia
Start at (m/d/y): 12/03/2018 21:05:01
===================================
Candidate is: 384.130-1
Installed is: (none)
Would you like to check debian-backports for a later version?
Yes or No?
1: Yes
2: No
Enter Number of selection
1
Ok...
Enabling backports repo
Running apt-get update...
Hit:1 http://iso.mxrepo.com/antix/stretch stretch InRelease
Get:2 http://ftp.debian.org/debian stretch-backports InRelease [91.8 kB]
Get:3 http://ftp.debian.org/debian stretch-backports/main amd64 Packages [515 kB]
Get:4 http://ftp.debian.org/debian stretch-backports/main i386 Packages [509 kB]
Get:5 http://ftp.debian.org/debian stretch-backports/main Translation-en [393 kB]
Get:6 http://ftp.debian.org/debian stretch-backports/contrib amd64 Packages [7,620 B]
Get:7 http://ftp.debian.org/debian stretch-backports/contrib i386 Packages [7,252 B]
Get:8 http://ftp.debian.org/debian stretch-backports/contrib Translation-en [6,233 B]
Get:9 http://ftp.debian.org/debian stretch-backports/non-free i386 Packages [19.4 kB]
Get:10 http://ftp.debian.org/debian stretch-backports/non-free amd64 Packages [29.1 kB]
Get:11 http://ftp.debian.org/debian stretch-backports/non-free Translation-en [33.8 kB]
Hit:12 http://security.debian.org stretch/updates InRelease
Get:13 http://ftp.us.debian.org/debian stretch-updates InRelease [91.0 kB]
Hit:14 http://mxrepo.com/mx/repo stretch InRelease
Get:15 http://mxrepo.com/mx/testrepo stretch InRelease [4,967 B]
Ign:16 http://ftp.us.debian.org/debian stretch InRelease
Get:17 http://mxrepo.com/mx/testrepo stretch/test Sources [286 kB]
Hit:18 http://ftp.us.debian.org/debian stretch Release
Fetched 1,993 kB in 6s (307 kB/s)
Reading package lists...
Installing latest nvidia-detect package
Reading package lists...
Building dependency tree...
Reading state information...
The following packages will be upgraded:
nvidia-detect
1 upgraded, 0 newly installed, 0 to remove and 121 not upgraded.
Need to get 193 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://ftp.debian.org/debian stretch-backports/non-free amd64 nvidia-detect amd64 390.87-2~bpo9+1 [193 kB]
Fetched 193 kB in 1s (158 kB/s)
(Reading database ... 326248 files and directories currently installed.)
Preparing to unpack .../nvidia-detect_390.87-2~bpo9+1_amd64.deb ...
Unpacking nvidia-detect (390.87-2~bpo9+1) over (390.87-2~bpo9+1~mx17+2) ...
Setting up nvidia-detect (390.87-2~bpo9+1) ...
Main repo candidate is: 384.130-1
Debian backports candidate is: 390.87-2~bpo9+1
Installed is: (none)
Which driver do you wish to install
Main repos or debian-backports?
1: Main 384.130-1
2: debian-backports 390.87-2~bpo9+1
3: Exit
Enter Number of selection
2
Ok...
Need driver: nvidia-driver (390.87-2~bpo9+1)
packages to install are nvidia-driver nvidia-settings nvidia-kernel-dkms libnvidia-encode1 nvidia-xconfig
Continue?
1) yes (default)
2) no
Press <Enter> for the default entry
Use 'q' to quit
Frontend:
Nvidia command = apt-get install --reinstall -y --force-yes -t stretch-backports nvidia-driver nvidia-settings nvidia-kernel-dkms libnvidia-encode1 nvidia-xconfig
Reading package lists...
Building dependency tree...
Reading state information...
Reinstallation of linux-headers-4.19.0-1-amd64 is not possible, it cannot be downloaded.
Reinstallation of firmware-linux-nonfree is not possible, it cannot be downloaded.
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 1 not upgraded.
Need to get 7,346 B of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://ftp.us.debian.org/debian stretch/main amd64 build-essential amd64 12.3 [7,346 B]
Fetched 7,346 B in 0s (27.0 kB/s)
(Reading database ... 326248 files and directories currently installed.)
Preparing to unpack .../build-essential_12.3_amd64.deb ...
Unpacking build-essential (12.3) over (12.3) ...
Setting up build-essential (12.3) ...
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
nvidia-settings : Depends: libxnvctrl0 (= 390.48-2~bpo9+1) but 390.67-1~mx17+1 is to be installed
E: Unable to correct problems, you have held broken packages.
/usr/local/bin/ddm-mx: line 472: creating /etc/X11/xorg.conf file: No such file or directory
/usr/local/bin/ddm-mx: line 473: nvidia-xconfig: command not found
Finished
Hit:1 http://security.debian.org stretch/updates InRelease
Hit:2 http://iso.mxrepo.com/antix/stretch stretch InRelease
Hit:3 http://ftp.us.debian.org/debian stretch-updates InRelease
Hit:4 http://mxrepo.com/mx/repo stretch InRelease
Ign:5 http://ftp.us.debian.org/debian stretch InRelease
Hit:6 http://mxrepo.com/mx/testrepo stretch InRelease
Hit:7 http://ftp.us.debian.org/debian stretch Release
Reading package lists... Done
Press <Enter> to exit
t:8 http://ftp.debian.org/debian stretch-backports/contrib Translation-en [6,233 B]
Get:9 http://ftp.debian.org/debian stretch-backports/non-free i386 Packages [19.4 kB]
Get:10 http://ftp.debian.org/debian stretch-backports/non-free amd64 Packages [29.1 kB]
Get:11 http://ftp.debian.org/debian stretch-backports/non-free Translation-en [33.8 kB]
Hit:12 http://security.debian.org stretch/updates InRelease
Get:13 http://ftp.us.debian.org/debian stretch-updates InRelease [91.0 kB]
Hit:14 http://mxrepo.com/mx/repo stretch InRelease
Get:15 http://mxrepo.com/mx/testrepo stretch InRelease [4,967 B]
Ign:16 http://ftp.us.debian.org/debian stretch InRelease
Get:17 http://mxrepo.com/mx/testrepo stretch/test Sources [286 kB]
Hit:18 http://ftp.us.debian.org/debian stretch Release
Fetched 1,993 kB in 6s (307 kB/s)
Reading package lists...
Installing latest nvidia-detect package
Reading package lists...
Building dependency tree...
Reading state information...
The following packages will be upgraded:
nvidia-detect
1 upgraded, 0 newly installed, 0 to remove and 121 not upgraded.
Need to get 193 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://ftp.debian.org/debian stretch-backports/non-free amd64 nvidia-detect amd64 390.87-2~bpo9+1 [193 kB]
Fetched 193 kB in 1s (158 kB/s)
(Reading database ... 326248 files and directories currently installed.)
Preparing to unpack .../nvidia-detect_390.87-2~bpo9+1_amd64.deb ...
Unpacking nvidia-detect (390.87-2~bpo9+1) over (390.87-2~bpo9+1~mx17+2) ...
Setting up nvidia-detect (390.87-2~bpo9+1) ...
Main repo candidate is: 384.130-1
Debian backports candidate is: 390.87-2~bpo9+1
Installed is: (none)
Which driver do you wish to install
Main repos or debian-backports?
1: Main 384.130-1
2: debian-backports 390.87-2~bpo9+1
3: Exit
Enter Number of selection
2
Ok...
Need driver: nvidia-driver (390.87-2~bpo9+1)
packages to install are nvidia-driver nvidia-settings nvidia-kernel-dkms libnvidia-encode1 nvidia-xconfig
Continue?
1) yes (default)
2) no
Press <Enter> for the default entry
Use 'q' to quit
Frontend:
Nvidia command = apt-get install --reinstall -y --force-yes -t stretch-backports nvidia-driver nvidia-settings nvidia-kernel-dkms libnvidia-encode1 nvidia-xconfig
Reading package lists...
Building dependency tree...
Reading state information...
Reinstallation of linux-headers-4.19.0-1-amd64 is not possible, it cannot be downloaded.
Reinstallation of firmware-linux-nonfree is not possible, it cannot be downloaded.
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 1 not upgraded.
Need to get 7,346 B of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://ftp.us.debian.org/debian stretch/main amd64 build-essential amd64 12.3 [7,346 B]
Fetched 7,346 B in 0s (27.0 kB/s)
(Reading database ... 326248 files and directories currently installed.)
Preparing to unpack .../build-essential_12.3_amd64.deb ...
Unpacking build-essential (12.3) over (12.3) ...
Setting up build-essential (12.3) ...
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
nvidia-settings : Depends: libxnvctrl0 (= 390.48-2~bpo9+1) but 390.67-1~mx17+1 is to be installed
E: Unable to correct problems, you have held broken packages.
/usr/local/bin/ddm-mx: line 472: creating /etc/X11/xorg.conf file: No such file or directory
/usr/local/bin/ddm-mx: line 473: nvidia-xconfig: command not found
Finished
Hit:1 http://security.debian.org stretch/updates InRelease
Hit:2 http://iso.mxrepo.com/antix/stretch stretch InRelease
Hit:3 http://ftp.us.debian.org/debian stretch-updates InRelease
Hit:4 http://mxrepo.com/mx/repo stretch InRelease
Ign:5 http://ftp.us.debian.org/debian stretch InRelease
Hit:6 http://mxrepo.com/mx/testrepo stretch InRelease
Hit:7 http://ftp.us.debian.org/debian stretch Release
Reading package lists... Done
Press <Enter> to exit
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 10:15 pm
by mmikeinsantarosa
Maybe set the min heights for the widgets inside tweak's tabs. They can squish down to where they're unreadable.
tweak-min-vert-sizes.png
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 10:30 pm
by freefreeno
Just to let you know you cleared up my confusion with the root and boot deal and I am using MX again and I just want to say thank all ya'll for your help and once again this is the best forum on the internet.
Re: MX-18 beta 1 feedback-GRUB difficulties
Posted: Mon Dec 03, 2018 10:32 pm
by Adrian
entropyfoe wrote: Mon Dec 03, 2018 9:18 pm
But I had problems with installing GRUB to root. The P4 never showed up in the installer window. I don't want to MBR, as that is my main MX 17.1 system. The installer asks "OK to install GRUB bootloader at ?", so maybe it is not seeing that 4th nvme partition for some reason. It offered the option to not install grub, complete installation, and then reboot and use the grub repair tool.
Thanks for this report, the installer is fixed I think, the update should come in a pool shortly, but you can also try the fixed package from here:
https://github.com/MX-Linux/gazelle-ins ... _amd64.deb
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 10:42 pm
by entropyfoe
So far looks good after reboots, many packages added/upgraded, many desktop tweaks. Just the two problems noted so far:
1. The GRUB problem- surmounted by update-grub from existing MX 17 install.
2, The nvidia installer-
The following packages have unmet dependencies:
nvidia-settings : Depends: libxnvctrl0 (= 390.48-2~bpo9+1) but 390.67-1~mx17+1 is to be installed
E: Unable to correct problems, you have held broken packages.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 10:49 pm
by entropyfoe
Adrian,
How would I test a new installer? It has to be part of the MX 18 ISO right?
Maybe I will just wait until the next beta is out, maybe with the nvidia fix as well.
So far pretty good except for these two items. Everything seems to work, the installed packages, desk-top customizations, internet, sound, you-tube
I was looking for the GRUB customizer as I recalled from MX 17. Where do I find that?
I want to see if I still have the kernel parameter that I need to pass at boot to fix the Ryzen crash at idle problem.
[rcu_nocbs=0-11]. I never could find out if that kernel bug was squashed, so the boot parameter may not be needed any longer.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 10:56 pm
by dolphin_oracle
freefreeno wrote: Mon Dec 03, 2018 10:30 pm
Just to let you know you cleared up my confusion with the root and boot deal and I am using MX again and I just want to say thank all ya'll for your help and once again this is the best forum on the internet.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 11:23 pm
by Adrian
How would I test a new installer? It has to be part of the MX 18 ISO right?
Not really, if you have internet access you can update it in the live environment, the update should come shortly from the pool, otherwise you can click on the link I posted install it (I think gdebi takes care of it -- use "root" for password when asked) and then try to install again. I'm pretty confident that issue with installing GRUB on root should be fixed.
Re: MX-18 beta 1 feedback -installer now sees the root partition
Posted: Tue Dec 04, 2018 12:03 am
by entropyfoe
Adrian,
You figured it out, at least to my eye.
As you suggested I booted into the live session again, and updated the installer to 18.12.
Then I installed (preserving /home) again to that p4 on the nvme drive. This time when it came time to install GRUB, the correct root partition was displayed (nvme01 P4) and not the question mark.
The install completed normally.
Fast detective work and fixing !
Thanks - now to get the nvidia driver. Is the grub customizer installed?
So far, this beta looks good, time for a stability check over night.
Re: MX-18 beta 1 feedback
Posted: Tue Dec 04, 2018 1:29 am
by bicyclist56
old_guy wrote: Mon Dec 03, 2018 3:52 pm
Tried to install from MXPI and got:
...
unmet dependencies:
winehq-staging : Depends: wine-staging (=2.21-1mx17+1)
E: Unable to correct problems, you have held broken packages
earl
bash: winecfg: command not found
I have the same. This question has not yet been answered.
And the second problem, when starting virtualbox:
Kernel driver not installed (rc=-1908)
The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall virtualbox-dkms package and load the kernel module by executing
sudo 'modprobe vboxdrv'
as root.
where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT.
OK, I do:
Code: Select all
sudo apt-get remove virtualbox-dkms
sudo apt-get install virtualbox-dkms
Loading new virtualbox-5.2.6 DKMS files...
Building for 4.19.0-1-amd64
Building initial module for 4.19.0-1-amd64
Error! Bad return status for module build on kernel: 4.19.0-1-amd64 (x86_64)
Consult /var/lib/dkms/virtualbox/5.2.6/build/make.log for more information.
[ ok ] Unloading VirtualBox kernel modules....
[....] Loading VirtualBox kernel modules...[....] No suitable module for running[FAILel found ... failed!
failed!
invoke-rc.d: initscript virtualbox, action "restart" failed.
Code: Select all
vvv@mx-vvv ~ $ inxi -F
System:
Host: mx-vvv Kernel: 4.19.0-1-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3
Distro: MX-18b1_x64 Continuum December 3 2018
Machine:
Type: Laptop Mobo: INTEL model: ChiefRiver serial: <root required>
BIOS: American Megatrends v: 4.6.5 date: 05/29/2014
CPU:
Topology: Dual Core model: Intel Core i5-3317U bits: 64 type: MT MCP
L2 cache: 3072 KiB
Speed: 1751 MHz min/max: 800/2600 MHz Core speeds (MHz): 1: 1751 2: 1729
3: 2377 4: 1412
Graphics:
Device-1: Intel 3rd Gen Core processor Graphics driver: i915 v: kernel
Display: x11 server: X.Org 1.19.2 driver: modesetting unloaded: fbdev,vesa
resolution: 1600x900~60Hz
OpenGL: renderer: Mesa DRI Intel Ivybridge Mobile v: 4.2 Mesa 18.2.6
Audio:
Device-1: Intel 7 Series/C216 Family High Definition Audio
driver: snd_hda_intel
Sound Server: ALSA v: k4.19.0-1-amd64
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
driver: r8169
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: 00:e0:4c:68:05:ea
Device-2: Broadcom Limited BCM43225 802.11b/g/n driver: wl
IF: wlan0 state: dormant mac: a6:2c:af:fc:ec:a5
Drives:
Local Storage: total: 231.03 GiB used: 92.45 GiB (40.0%)
ID-1: /dev/sda vendor: Kingfast model: KingFast size: 119.24 GiB
ID-2: /dev/sdb vendor: Kingston model: SV300S37A120G size: 111.79 GiB
Partition:
ID-1: / size: 11.75 GiB used: 6.30 GiB (53.6%) fs: ext4 dev: /dev/sda1
ID-2: /home size: 103.23 GiB used: 72.91 GiB (70.6%) fs: ext4
dev: /dev/sda2
ID-3: swap-1 size: 2.24 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda3
Sensors:
System Temperatures: cpu: 45.0 C mobo: N/A
Fan Speeds (RPM): N/A
Info:
Processes: 214 Uptime: 4h 16m Memory: 7.69 GiB used: 2.00 GiB (26.0%)
Shell: bash inxi: 3.0.25
Re: MX-18 beta 1 feedback
Posted: Tue Dec 04, 2018 2:11 am
by freefreeno
Observation: I looked for months for linux OS that would not make my fans go crazy on this Lenovo Yoga and today MX-18 has finally satisfied me on that. It has never been the fact that my laptop ran hot but just the oposite it ran really cool but fans would come on anyways. Just wanted to let you all know this is great for Lenovo laptops. Also gonna leave some screen shots here for you. This is temps. I have some very screwy problems with my synaptics touchpad being jumpy so maybe someone might help me with that. Its usable but could be much smoother.
Adapter: ISA adapter
Package id 0: +35.0°C (high = +100.0°C, crit = +100.0°C)
Core 0: +34.0°C (high = +100.0°C, crit = +100.0°C)
Core 1: +34.0°C (high = +100.0°C, crit = +100.0°C)
https://imageshack.com/a/img923/3857/WlDIm0.png
https://imageshack.com/a/img924/1931/laCBuY.png
https://imageshack.com/a/img924/8400/JY0kzF.png
https://imageshack.com/a/img922/17/QBfqlG.png
https://imageshack.com/a/img923/342/3WtTya.png
https://imageshack.com/a/img922/8899/AJ0vzj.png
Re: MX-18 beta 1 feedback
Posted: Tue Dec 04, 2018 3:06 am
by asqwerth
bicyclist56 wrote: Tue Dec 04, 2018 1:29 am
old_guy wrote: Mon Dec 03, 2018 3:52 pm
Tried to install from MXPI and got:
...
unmet dependencies:
winehq-staging : Depends: wine-staging (=2.21-1mx17+1)
E: Unable to correct problems, you have held broken packages
earl
bash: winecfg: command not found
I have the same. This question has not yet been answered.
And the second problem, when starting virtualbox:
Kernel driver not installed (rc=-1908)
The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall virtualbox-dkms package and load the kernel module by executing
sudo 'modprobe vboxdrv'
as root.
where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT.
....
Hold on a while until the Developers wake up (diff timezone!) and decide on the best way forward for testing.
This is my basic understanding:
Certain upgraded packages and applications which were not yet tested enough for MX Test Repo were placed in a non-public dev repo for early testing.
The MX18 beta did not enable the dev repo, so the Beta does not have some of these updated packages. For some users, they may not need these packages, so the Beta runs fine for them. But I think some of the dev repo packages are stuff needed for the new kernel to work with certain graphics drivers (maybe Virtualbox as well?).
I think the Devs will be making a decision on how to go about allowing access to these packages to testers of the Beta 1, without affecting current MX17 users (MX17/18 are both built on the same Debian Stretch base) until the stability of the packages is confirmed.
From what I can see so far of the beta feedback, a fair number of the issues reported about packages or dependencies not being present, might be related to this situation where the needed packages are in dev repo.
-----------------------------------------------------------------------------
Note: Some of us enabled the dev repo on our existing MX17 installs to see if pulling in these updated applications and packages would destabilise our current system. It didn't cause any problems for me, but I'm on an older kernel and I just used my system the way I normally would.
Re: MX-18 beta 1 feedback
Posted: Tue Dec 04, 2018 3:19 am
by bicyclist56
Well,
asqwerth, these things are not in a hurry. Let's wait.
And the Telegram (from
https://desktop.telegram.org/) does not work yet:
Code: Select all
~/MyApps/Telegram/Telegram
Fontconfig warning: line 5: unknown element "its:rules"
Fontconfig warning: line 6: unknown element "its:translateRule"
Fontconfig error: line 6: invalid attribute 'translate'
...
Fontconfig error: Cannot load default config file
Added programs, they work successfully: Chromium Googleearth KeepassX Calibre Openshot apt-transport-https bleachbit devilspie ncdu streamripper clipgrab gpsbabel gpsbabel-gui unetbootin nitroshare mail.ru-cloud vidcutter (v.5.5.0, otherwise no font displayed) xnviewmp turtlesport zim gpsprune freefilesync tor-browser viber
And no: wine virtualbox Telegram
P.S. I turned on dev repo -
viewtopic.php?f=94&t=47201, wine and virtualbox have become working. The problem with fonts for Telegram remains, but it can be used in the browser.
Re: MX-18 beta 1 feedback
Posted: Tue Dec 04, 2018 4:36 am
by chrispop99
On one machine, QupZilla installs from the PI, but crashes at launch every time. It runs fine on two other machines.
tower.txt
Chris
Re: MX-18 beta 1 feedback
Posted: Tue Dec 04, 2018 4:58 am
by Gaer Boy
Adrian wrote: Mon Dec 03, 2018 9:30 pm
I set the timezones, clicked next, and the installer vanished ! (not sure what happened, did I press a wrong button??!!?!?)
Possibly an installer crash, it never happened to me at that step though... not sure what's went on.
This also happened for me the first time, but I was distracted by conversation and assumed I'd clicked the wrong button.
Re: MX-18 beta 1 feedback
Posted: Tue Dec 04, 2018 5:01 am
by chrispop99
Latest update to 'MX Welcome' reverts the title to the MX-17 one.
Chris
Re: MX-18 beta 1 feedback
Posted: Tue Dec 04, 2018 5:03 am
by chrispop99
(Trivial)
On an install with full disk encryption, a text message is displayed over the Plymouth screen, which is aesthetically unpleasant.
Chris
Re: MX-18 beta 1 feedback
Posted: Tue Dec 04, 2018 5:28 am
by Raitsa
archive.org MX18b1X64 torrent download, transferred to USB with the live usb maker and installed to an Intel NUC 5CPYH very smoothly.
Re: MX-18 beta 1 feedback
Posted: Tue Dec 04, 2018 5:44 am
by CaputAlista
Hi all. I boot from a usb. In this version sometimes (as it acts with ubuntu) in the first boot it consumes a lot of cpu and the ram is highly occupied and it is increasing the normal is 400 MB), with the option no acpi is regulated but the wifi does not work. In this version and the previous one sometimes the realtek sound (I have an hpx360) works and sometimes not. The mouse menu to change owner a folder or file is lost.
Re: MX-18 beta 1 feedback
Posted: Tue Dec 04, 2018 5:51 am
by fehlix
chrispop99 wrote: Tue Dec 04, 2018 4:36 am
On one machine, QupZilla installs from the PI, but crashes at launch every time. It runs fine on two other machines.
seems that within the package dependency of qupzilla at least two libs are missing:
please install these two missing qml-modules:
Code: Select all
sudo apt install qml-module-qtwebengine qml-module-qtquick2
Re: MX-18 beta 1 feedback
Posted: Tue Dec 04, 2018 5:53 am
by fehlix
chrispop99 wrote: Tue Dec 04, 2018 5:03 am
On an install with full disk encryption, a text message is displayed over the Plymouth screen, which is aesthetically unpleasant.
is that the password prompt or something else?
Re: MX-18 beta 1 feedback
Posted: Tue Dec 04, 2018 5:58 am
by fehlix
CaputAlista wrote: Tue Dec 04, 2018 5:44 am
Hi all. I boot from a usb. In this version sometimes (as it acts with ubuntu) in the first boot it consumes a lot of cpu and the ram is highly occupied and it is increasing the normal is 400 MB), with the option no acpi is regulated but the wifi does not work.
Please provide system information, by runing the Quick System Info tool from the menu.
Paste the output, which automatically put into the clipboard here.
CaputAlista wrote: Tue Dec 04, 2018 5:44 am
The mouse menu to change owner a folder or file is lost.
It was intentionally removed, as it caused to many severe issues for lot of users.
Re: MX-18 beta 1 feedback
Posted: Tue Dec 04, 2018 6:03 am
by Fornhamfred
Installed this morning. Using MX Tweak appearance default font style description is in a foreign language.
Re: MX-18 beta 1 feedback
Posted: Tue Dec 04, 2018 6:25 am
by richb
fehlix wrote: Tue Dec 04, 2018 5:53 am
chrispop99 wrote: Tue Dec 04, 2018 5:03 am
On an install with full disk encryption, a text message is displayed over the Plymouth screen, which is aesthetically unpleasant.
is that the password prompt or something else?
It may be the encryption password prompt as I reported during alpha it was centered right over the ribbon. Chris please confirm.
Re: MX-18 beta 1 feedback
Posted: Tue Dec 04, 2018 6:28 am
by fehlix
Fornhamfred wrote: Tue Dec 04, 2018 6:03 am
Installed this morning. Using MX Tweak appearance default font style description is in a foreign language.
We are not good guessing what your language and what a foreign language for you might be.
Re: MX-18 beta 1 feedback
Posted: Tue Dec 04, 2018 7:14 am
by Eadwine Rose
Fornhamfred wrote: Tue Dec 04, 2018 6:03 am
Installed this morning. Using MX Tweak appearance default font style description is in a foreign language.
Can you provide a screenshot?
Re: MX-18 beta 1 feedback
Posted: Tue Dec 04, 2018 7:55 am
by chrispop99
fehlix wrote: Tue Dec 04, 2018 5:53 am
chrispop99 wrote: Tue Dec 04, 2018 5:03 am
On an install with full disk encryption, a text message is displayed over the Plymouth screen, which is aesthetically unpleasant.
is that the password prompt or something else?
Something else.
After entering the encryption password, text relating to that is displayed top-left of the screen. It's trivial, but something that slightly detracts from having Plymouth.
Chris
Re: MX-18 beta 1 feedback
Posted: Tue Dec 04, 2018 8:01 am
by dolphin_oracle
chrispop99 wrote: Tue Dec 04, 2018 7:55 am
fehlix wrote: Tue Dec 04, 2018 5:53 am
chrispop99 wrote: Tue Dec 04, 2018 5:03 am
On an install with full disk encryption, a text message is displayed over the Plymouth screen, which is aesthetically unpleasant.
is that the password prompt or something else?
Something else.
After entering the encryption password, text relating to that is displayed top-left of the screen. It's trivial, but something that slightly detracts from having Plymouth.
Chris
yep, its a "feature" of plymouth that certain kinds of messages bleed through the splash image, including the successful cryptsetup messages.
Re: MX-18 beta 1 feedback
Posted: Tue Dec 04, 2018 8:09 am
by chrispop99
fehlix wrote: Tue Dec 04, 2018 5:51 am
chrispop99 wrote: Tue Dec 04, 2018 4:36 am
On one machine, QupZilla installs from the PI, but crashes at launch every time. It runs fine on two other machines.
seems that within the package dependency of qupzilla at least two libs are missing:
please install these two missing qml-modules:
Code: Select all
sudo apt install qml-module-qtwebengine qml-module-qtquick2
It still crashes with those libs installed.
Launching from a terminal reveals there is a crash log. Here is the text in case it helps:
Code: Select all
Time: Tue Dec 4 09:30:47 2018
Qt version: 5.7.1 (compiled with 5.7.1)
QupZilla version: 2.1.2
Rendering engine: QtWebEngine
============== BACKTRACE ==============
#0: qupzilla(+0x35e2) [0x56472ed645e2]
#1: /lib/x86_64-linux-gnu/libc.so.6(+0x33060) [0x7ff93bb15060]
#2: /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so(+0x657ea7) [0x7ff91870aea7]
#3: /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so(+0x5c6184) [0x7ff918679184]
#4: /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so(+0x651e8f) [0x7ff918704e8f]
#5: /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2(+0x3cac) [0x7ff917c9fcac]
#6: /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2(+0x410f) [0x7ff917ca010f]
#7: /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2(nouveau_pushbuf_kick+0x10) [0x7ff917ca0cc0]
#8: /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so(+0x652336) [0x7ff918705336]
#9: /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so(+0x270c81) [0x7ff918323c81]
#10: /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5(+0x1afc726) [0x7ff93ffef726]
#11: /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5(+0x2741280) [0x7ff940c34280]
#12: /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5(+0x26dd4c1) [0x7ff940bd04c1]
#13: /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5(+0x270b6f2) [0x7ff940bfe6f2]
#14: /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5(+0x275bfda) [0x7ff940c4efda]
#15: /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5(+0x271fd0a) [0x7ff940c12d0a]
#16: /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5(+0x19077c1) [0x7ff93fdfa7c1]
#17: /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5(+0x190b0a1) [0x7ff93fdfe0a1]
#18: /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5(+0x190640e) [0x7ff93fdf940e]
#19: /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5(+0x207e170) [0x7ff940571170]
#20: /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5(+0x2027378) [0x7ff94051a378]
#21: /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5(+0x2027fe9) [0x7ff94051afe9]
#22: /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5(+0x20284b2) [0x7ff94051b4b2]
#23: /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5(+0x202a4d9) [0x7ff94051d4d9]
#24: /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5(+0x203c7b4) [0x7ff94052f7b4]
#25: /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5(+0x2026705) [0x7ff940519705]
#26: /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5(+0x205574a) [0x7ff94054874a]
#27: /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5(+0x2051a8c) [0x7ff940544a8c]
#28: /lib/x86_64-linux-gnu/libpthread.so.0(+0x7494) [0x7ff93c725494]
#29: /lib/x86_64-linux-gnu/libc.so.6(clone+0x3f) [0x7ff93bbcaacf]
Chris
Re: MX-18 beta 1 feedback
Posted: Tue Dec 04, 2018 8:44 am
by CaputAlista
<< Post by CaputAlista » Tue Dec 04, 2018 5:14 pm Hi all. I boot from a usb. In this version sometimes (as it acts with ubuntu) in the first boot it consumes a lot of cpu and the ram is highly occupied and it is increasing the normal is 400 MB), with the option no acpi is regulated but the wifi does not work. In this version and the previous one sometimes the realtek sound (I have an hpx360) works and sometimes not. The mouse menu to change owner a folder or file is lost.>>
Code: Select all
System:
Host: mx1 Kernel: 4.19.0-1-amd64 x86_64 bits: 64 compiler: gcc v: 6.3.0
Desktop: Xfce 4.12.3 Distro: MX-18b1_x64 Continuum December 3 2018
base: Debian GNU/Linux 9 (stretch)
Machine:
Type: N/A System: HP product: HP Pavilion x360 Convertible
v: Type1ProductConfigId serial: <filter>
Mobo: HP model: 81A9 v: 57.53 serial: <filter> UEFI [Legacy]: Insyde
v: F.35 date: 06/25/2018
Battery:
ID-1: BAT0 charge: 41.9 Wh condition: 41.9/41.9 Wh (100%)
model: 313-54-41 ON03041XL status: Full
CPU:
Topology: Dual Core model: Intel Core i5-7200U bits: 64 type: MT MCP
arch: Kaby Lake rev: 9 L2 cache: 3072 KiB
flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 21696
Speed: 1027 MHz min/max: 400/3100 MHz Core speeds (MHz): 1: 570 2: 592
3: 582 4: 590
Graphics:
Device-1: Intel driver: i915 v: kernel bus ID: 00:02.0
Display: x11 server: X.Org 1.19.2 driver: modesetting unloaded: fbdev,vesa
resolution: 1366x768~60Hz
OpenGL: renderer: Mesa DRI Intel HD Graphics 620 (Kaby Lake GT2)
v: 4.5 Mesa 18.2.6 direct render: Yes
Audio:
Device-1: Intel driver: snd_hda_intel v: kernel bus ID: 00:1f.3
Sound Server: ALSA v: k4.19.0-1-amd64
Network:
Device-1: Realtek RTL8723BE PCIe Wireless Network Adapter
driver: rtl8723be v: kernel port: 3000 bus ID: 01:00.0
IF: wlan0 state: up mac: <filter>
Drives:
Local Storage: total: 469.40 GiB used: 73.4 MiB (0.0%)
ID-1: /dev/sda vendor: Western Digital model: WD5000LPCX-60VHAT0
size: 465.76 GiB
ID-2: /dev/sdb type: USB model: MXT-USB Storage Device size: 3.64 GiB
Partition:
ID-1: / size: 2.94 GiB used: 73.4 MiB (2.4%) fs: overlay dev: ERR-102
Sensors:
System Temperatures: cpu: 49.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/stretch stretch main
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://ftp.us.debian.org/debian/ stretch-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://ftp.us.debian.org/debian/ stretch main contrib non-free
2: deb http://security.debian.org/ stretch/updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://iso.mxrepo.com/mx/repo/ stretch main non-free
No active apt repos in: /etc/apt/sources.list.d/various.list
Info:
Processes: 201 Uptime: 5m Memory: 3.73 GiB used: 815.0 MiB (21.3%)
Init: SysVinit runlevel: 5 Compilers: gcc: 6.3.0 Shell: bash v: 4.4.12
inxi: 3.0.25
obs: the cpu and ram under use but sound not raltek alc295 according to alsamixer in this report
+++
Mod note: Please put console text-output between code-tags: [
code] text goes here [/code] .
To insert code-tags press
</>-icon above the editor window.
Quick System Info (from menu) will wrap code-tags to clipboard-copied system info automatically.
Re: MX-18 beta 1 feedback
Posted: Tue Dec 04, 2018 9:57 am
by entropyfoe
So, the Ryzen stability test has failed.
This morning I came down to the machine, and it had rebooted spontaneously over night at idle.
This is the same Issue I had last year, a kernel bug that needs a parameter passed at boot to the kernel. I was hoping by 4.19 this would have been fixed.
I rebooted back to the beta for another idle test today while I am at work.
But I think I must add the line to grub.
Now, where do I find the grub customizer in the new beta?
I could not find it last night.
I am sure there is another way to pass this command, but the customizer was easy.
Re: MX-18 beta 1 feedback
Posted: Tue Dec 04, 2018 10:13 am
by richb
entropyfoe wrote: Tue Dec 04, 2018 9:57 am
So, the Ryzen stability test has failed.
This morning I came down to the machine, and it had rebooted spontaneously over night at idle.
This is the same Issue I had last year, a kernel bug that needs a parameter passed at boot to the kernel. I was hoping by 4.19 this would have been fixed.
I rebooted back to the beta for another idle test today while I am at work.
But I think I must add the line to grub.
Now, where do I find the grub customizer in the new beta?
I could not find it last night.
I am sure there is another way to pass this command, but the customizer was easy.
Grub-customizer was removed as it caused issues for users, You can install it from the repos. I did as I agree it has an easy way to add grub parameters. If you use a persist Live usb it will stay through reboots.
Re: MX-18 beta 1 feedback
Posted: Tue Dec 04, 2018 10:14 am
by dolphin_oracle
entropyfoe wrote: Tue Dec 04, 2018 9:57 am
So, the Ryzen stability test has failed.
This morning I came down to the machine, and it had rebooted spontaneously over night at idle.
This is the same Issue I had last year, a kernel bug that needs a parameter passed at boot to the kernel. I was hoping by 4.19 this would have been fixed.
I rebooted back to the beta for another idle test today while I am at work.
But I think I must add the line to grub.
Now, where do I find the grub customizer in the new beta?
I could not find it last night.
I am sure there is another way to pass this command, but the customizer was easy.
you can install it from synaptic.
or just add your parameter to this area of /etc/default/grub
Code: Select all
GRUB_CMDLINE_LINUX_DEFAULT="quiet"
so that it looks like this
Code: Select all
GRUB_CMDLINE_LINUX_DEFAULT="quiet rcu_nocbs=0-11"
and then run
[code]
sudo update-grub
for the change to take effect.
BTW new this go around is if you add the parameter to your live boot, it should carry over to an installed system.
Re: MX-18 beta 1 feedback
Posted: Tue Dec 04, 2018 10:25 am
by entropyfoe
Thanks to both Richb and the d_o.
I will use one of those tonight. Curious, what issues were caused by the grub customizer? It always worked well for me.
And second on the agenda is nvidia. My card is running about 7 degrees hotter with the noveau driver. In a different thread I see d_o posted to
add this to the repo list and update. (Can I add this through synaptic or the MX repo manager also?
Code: Select all
deb http://mxrepo.com/mx/testrepo/ mx18 dev
Those running the current MX Beta 1 can also enable the devrepo to enable installation nvidia drivers via the nvidia-driver tool.
So, projected status, If I add the boot parameter, and successfully add the nvidia driver, I think I am very happy with the beta. Great work to all the developers !
Re: MX-18 beta 1 feedback
Posted: Tue Dec 04, 2018 10:35 am
by Fornhamfred
Screenshot.png
Eadwine Rose wrote: Tue Dec 04, 2018 7:14 am
Fornhamfred wrote: Tue Dec 04, 2018 6:03 am
Installed this morning. Using MX Tweak appearance default font style description is in a foreign language.
Can you provide a screenshot?
Re: MX-18 beta 1 feedback
Posted: Tue Dec 04, 2018 10:46 am
by richb
Confirmed. Arial, Courier New and Times New Roman exhibit the same. All others are OK.
Re: MX-18 beta 1 feedback
Posted: Tue Dec 04, 2018 10:46 am
by entropyfoe
Looks like Czech.
The C with the little "v" over it is Czech or some other similar Slavic language.
Re: MX-18 beta 1 feedback
Posted: Tue Dec 04, 2018 10:49 am
by dolphin_oracle
Ok that's weird.
Re: MX-18 beta 1 feedback
Posted: Tue Dec 04, 2018 11:17 am
by Fornhamfred
Trying to install Teamviewer with mxpi gave the following output:
Code: Select all
Hit:1 http://security.debian.org stretch/updates InRelease
Hit:2 http://ftp.uk.debian.org/debian stretch-updates InRelease
Ign:3 http://ftp.uk.debian.org/debian stretch InRelease
Hit:4 http://ftp.uk.debian.org/debian stretch Release
Hit:5 http://nl.mxrepo.com/antix/stretch stretch InRelease
Hit:6 http://nl.mxrepo.com/mx/repo stretch InRelease
Reading package lists...
--2018-12-04 16:09:44-- http://download.teamviewer.com/download/teamviewer_i386.deb
Resolving download.teamviewer.com (download.teamviewer.com)... 52.143.143.83
Connecting to download.teamviewer.com (download.teamviewer.com)|52.143.143.83|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://dl.tvcdn.de/download/version_12x/teamviewer_12.0.137452_i386.deb [following]
--2018-12-04 16:09:44-- https://dl.tvcdn.de/download/version_12x/teamviewer_12.0.137452_i386.deb
Resolving dl.tvcdn.de (dl.tvcdn.de)... 2600:9000:201f:3200:c:b82f:7ac8:dfa1, 2600:9000:201f:2c00:c:b82f:7ac8:dfa1, 2600:9000:201f:5600:c:b82f:7ac8:dfa1, ...
Connecting to dl.tvcdn.de (dl.tvcdn.de)|2600:9000:201f:3200:c:b82f:7ac8:dfa1|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 46848618 (45M) [application/octet-stream]
Saving to: ‘teamviewer_i386.deb’
37500K .......... .......... .......... .......... .......... 82% 1.59M 4s
37550K .......... .......... .......... .......... .......... 82% 2.15M 4s
37600K .......... .......... .......... .......... .......... 82% 2.14M 4s
37650K .......... .......... .......... .......... .......... 82% 2.15M 4s
37700K .......... .......... .......... .......... .......... 82% 2.17M 4s
37750K .......... .......... .......... .......... .......... 82% 1.96M 4s
37800K .......... .......... .......... .......... .......... 82% 2.17M 4s
37850K .......... .......... .......... .......... .......... 82% 2.14M 4s
37900K .......... .......... .......... .......... .......... 82% 2.15M 4s
37950K .......... .......... .......... .......... .......... 83% 2.06M 4s
38000K .......... .......... .......... .......... .......... 83% 1.64M 4s
38050K .......... .......... .......... .......... .......... 83% 2.16M 4s
38100K .......... .......... .......... .......... .......... 83% 2.06M 4s
38150K .......... .......... .......... .......... .......... 83% 2.22M 4s
38200K .......... .......... .......... .......... .......... 83% 2.07M 4s
38250K .......... .......... .......... .......... .......... 83% 2.15M 4s
38300K .......... .......... .......... .......... .......... 83% 2.14M 4s
38350K .......... .......... .......... .......... .......... 83% 2.15M 4s
38400K .......... .......... .......... .......... .......... 84% 1.65M 3s
38450K .......... .......... .......... .......... .......... 84% 2.17M 3s
38500K .......... .......... .......... .......... .......... 84% 2.14M 3s
38550K .......... .......... .......... .......... .......... 84% 2.14M 3s
38600K .......... .......... .......... .......... .......... 84% 2.05M 3s
38650K .......... .......... .......... .......... .......... 84% 2.08M 3s
38700K .......... .......... .......... .......... .......... 84% 2.12M 3s
38750K .......... .......... .......... .......... .......... 84% 2.28M 3s
38800K .......... .......... .......... .......... .......... 84% 1.54M 3s
38850K .......... .......... .......... .......... .......... 85% 2.15M 3s
38900K .......... .......... .......... .......... .......... 85% 2.15M 3s
38950K .......... .......... .......... .......... .......... 85% 2.14M 3s
39000K .......... .......... .......... .......... .......... 85% 2.14M 3s
39050K .......... .......... .......... .......... .......... 85% 2.17M 3s
39100K .......... .......... .......... .......... .......... 85% 1.70M 3s
39150K .......... .......... .......... .......... .......... 85% 2.25M 3s
39200K .......... .......... .......... .......... .......... 85% 2.46M 3s
39250K .......... .......... .......... .......... .......... 85% 1.97M 3s
39300K .......... .......... .......... .......... .......... 86% 1.78M 3s
39350K .......... .......... .......... .......... .......... 86% 2.12M 3s
39400K .......... .......... .......... .......... .......... 86% 213K 3s
39450K .......... .......... .......... .......... .......... 86% 137M 3s
39500K .......... .......... .......... .......... .......... 86% 1.91M 3s
39550K .......... .......... .......... .......... .......... 86% 2.16M 3s
39600K .......... .......... .......... .......... .......... 86% 2.19M 3s
39650K .......... .......... .......... .......... .......... 86% 124M 3s
39700K .......... .......... .......... .......... .......... 86% 139M 3s
39750K .......... .......... .......... .......... .......... 86% 1.24M 3s
39800K .......... .......... .......... .......... .......... 87% 124M 3s
39850K .......... .......... .......... .......... .......... 87% 160M 3s
39900K .......... .......... .......... .......... .......... 87% 145M 3s
39950K .......... .......... .......... .......... .......... 87% 176M 3s
40000K .......... .......... .......... .......... .......... 87% 145M 3s
40050K .......... .......... .......... .......... .......... 87% 175M 3s
40100K .......... .......... .......... .......... .......... 87% 5.69M 3s
40150K .......... .......... .......... .......... .......... 87% 2.03M 3s
40200K .......... .......... .......... .......... .......... 87% 2.16M 3s
40250K .......... .......... .......... .......... .......... 88% 2.14M 3s
40300K .......... .......... .......... .......... .......... 88% 2.15M 3s
40350K .......... .......... .......... .......... .......... 88% 2.15M 3s
40400K .......... .......... .......... .......... .......... 88% 1.66M 3s
40450K .......... .......... .......... .......... .......... 88% 2.25M 3s
40500K .......... .......... .......... .......... .......... 88% 2.14M 2s
40550K .......... .......... .......... .......... .......... 88% 2.25M 2s
40600K .......... .......... .......... .......... .......... 88% 2.15M 2s
40650K .......... .......... .......... .......... .......... 88% 1.55M 2s
40700K .......... .......... .......... .......... .......... 89% 2.22M 2s
40750K .......... .......... .......... .......... .......... 89% 2.08M 2s
40800K .......... .......... .......... .......... .......... 89% 2.14M 2s
40850K .......... .......... .......... .......... .......... 89% 2.14M 2s
40900K .......... .......... .......... .......... .......... 89% 2.15M 2s
40950K .......... .......... .......... .......... .......... 89% 2.17M 2s
41000K .......... .......... .......... .......... .......... 89% 2.13M 2s
41050K .......... .......... .......... .......... .......... 89% 1.60M 2s
41100K .......... .......... .......... .......... .......... 89% 2.15M 2s
41150K .......... .......... .......... .......... .......... 90% 2.47M 2s
41200K .......... .......... .......... .......... .......... 90% 2.06M 2s
41250K .......... .......... .......... .......... .......... 90% 1.96M 2s
41300K .......... .......... .......... .......... .......... 90% 2.15M 2s
41350K .......... .......... .......... .......... .......... 90% 2.17M 2s
41400K .......... .......... .......... .......... .......... 90% 2.04M 2s
41450K .......... .......... .......... .......... .......... 90% 2.17M 2s
41500K .......... .......... .......... .......... .......... 90% 1.54M 2s
41550K .......... .......... .......... .......... .......... 90% 2.15M 2s
41600K .......... .......... .......... .......... .......... 91% 2.27M 2s
41650K .......... .......... .......... .......... .......... 91% 2.04M 2s
41700K .......... .......... .......... .......... .......... 91% 2.16M 2s
41750K .......... .......... .......... .......... .......... 91% 2.15M 2s
41800K .......... .......... .......... .......... .......... 91% 2.24M 2s
41850K .......... .......... .......... .......... .......... 91% 2.06M 2s
41900K .......... .......... .......... .......... .......... 91% 1.72M 2s
41950K .......... .......... .......... .......... .......... 91% 2.03M 2s
42000K .......... .......... .......... .......... .......... 91% 2.17M 2s
42050K .......... .......... .......... .......... .......... 92% 1.88M 2s
42100K .......... .......... .......... .......... .......... 92% 2.08M 2s
42150K .......... .......... .......... .......... .......... 92% 2.25M 2s
42200K .......... .......... .......... .......... .......... 92% 2.05M 2s
42250K .......... .......... .......... .......... .......... 92% 2.15M 2s
42300K .......... .......... .......... .......... .......... 92% 2.17M 2s
42350K .......... .......... .......... .......... .......... 92% 2.12M 2s
42400K .......... .......... .......... .......... .......... 92% 1.61M 2s
42450K .......... .......... .......... .......... .......... 92% 2.14M 2s
42500K .......... .......... .......... .......... .......... 93% 2.15M 2s
42550K .......... .......... .......... .......... .......... 93% 2.17M 2s
42600K .......... .......... .......... .......... .......... 93% 2.12M 1s
42650K .......... .......... .......... .......... .......... 93% 2.17M 1s
42700K .......... .......... .......... .......... .......... 93% 2.15M 1s
42750K .......... .......... .......... .......... .......... 93% 2.12M 1s
42800K .......... .......... .......... .......... .......... 93% 1.61M 1s
42850K .......... .......... .......... .......... .......... 93% 2.05M 1s
42900K .......... .......... .......... .......... .......... 93% 2.25M 1s
42950K .......... .......... .......... .......... .......... 93% 2.08M 1s
43000K .......... .......... .......... .......... .......... 94% 2.21M 1s
43050K .......... .......... .......... .......... .......... 94% 2.08M 1s
43100K .......... .......... .......... .......... .......... 94% 2.14M 1s
43150K .......... .......... .......... .......... .......... 94% 2.15M 1s
43200K .......... .......... .......... .......... .......... 94% 1.83M 1s
43250K .......... .......... .......... .......... .......... 94% 1.92M 1s
43300K .......... .......... .......... .......... .......... 94% 2.21M 1s
43350K .......... .......... .......... .......... .......... 94% 2.18M 1s
43400K .......... .......... .......... .......... .......... 94% 2.23M 1s
43450K .......... .......... .......... .......... .......... 95% 1.65M 1s
43500K .......... .......... .......... .......... .......... 95% 2.17M 1s
43550K .......... .......... .......... .......... .......... 95% 2.04M 1s
43600K .......... .......... .......... .......... .......... 95% 2.27M 1s
43650K .......... .......... .......... .......... .......... 95% 2.05M 1s
43700K .......... .......... .......... .......... .......... 95% 2.12M 1s
43750K .......... .......... .......... .......... .......... 95% 2.17M 1s
43800K .......... .......... .......... .......... .......... 95% 2.16M 1s
43850K .......... .......... .......... .......... .......... 95% 1.89M 1s
43900K .......... .......... .......... .......... .......... 96% 1.99M 1s
43950K .......... .......... .......... .......... .......... 96% 1.89M 1s
44000K .......... .......... .......... .......... .......... 96% 2.38M 1s
44050K .......... .......... .......... .......... .......... 96% 2.14M 1s
44100K .......... .......... .......... .......... .......... 96% 1.59M 1s
44150K .......... .......... .......... .......... .......... 96% 2.15M 1s
44200K .......... .......... .......... .......... .......... 96% 2.17M 1s
44250K .......... .......... .......... .......... .......... 96% 2.12M 1s
44300K .......... .......... .......... .......... .......... 96% 2.16M 1s
44350K .......... .......... .......... .......... .......... 97% 2.13M 1s
44400K .......... .......... .......... .......... .......... 97% 2.16M 1s
44450K .......... .......... .......... .......... .......... 97% 1.78M 1s
44500K .......... .......... .......... .......... .......... 97% 2.12M 1s
44550K .......... .......... .......... .......... .......... 97% 2.08M 1s
44600K .......... .......... .......... .......... .......... 97% 2.05M 1s
44650K .......... .......... .......... .......... .......... 97% 2.23M 1s
44700K .......... .......... .......... .......... .......... 97% 1.99M 0s
44750K .......... .......... .......... .......... .......... 97% 2.24M 0s
44800K .......... .......... .......... .......... .......... 98% 1.65M 0s
44850K .......... .......... .......... .......... .......... 98% 2.08M 0s
44900K .......... .......... .......... .......... .......... 98% 2.12M 0s
44950K .......... .......... .......... .......... .......... 98% 2.17M 0s
45000K .......... .......... .......... .......... .......... 98% 2.14M 0s
45050K .......... .......... .......... .......... .......... 98% 2.14M 0s
45100K .......... .......... .......... .......... .......... 98% 2.06M 0s
45150K .......... .......... .......... .......... .......... 98% 1.76M 0s
45200K .......... .......... .......... .......... .......... 98% 2.15M 0s
45250K .......... .......... .......... .......... .......... 99% 2.08M 0s
45300K .......... .......... .......... .......... .......... 99% 2.11M 0s
45350K .......... .......... .......... .......... .......... 99% 2.17M 0s
45400K .......... .......... .......... .......... .......... 99% 2.15M 0s
45450K .......... .......... .......... .......... .......... 99% 2.14M 0s
45500K .......... .......... .......... .......... .......... 99% 1.60M 0s
45550K .......... .......... .......... .......... .......... 99% 2.04M 0s
45600K .......... .......... .......... .......... .......... 99% 1.99M 0s
45650K .......... .......... .......... .......... .......... 99% 1.97M 0s
45700K .......... .......... .......... .......... .......... 99% 2.24M 0s
45750K 100% 1151G=22s
2018-12-04 16:10:06 (2.05 MB/s) - ‘teamviewer_i386.deb’ saved [46848618/46848618]
Selecting previously unselected package teamviewer:i386.
(Reading database ... 334011 files and directories currently installed.)
Preparing to unpack teamviewer_i386.deb ...
Unpacking teamviewer:i386 (12.0.137452) ...
dpkg: dependency problems prevent configuration of teamviewer:i386:
teamviewer:i386 depends on libasound2.
teamviewer:i386 depends on libdbus-1-3.
teamviewer:i386 depends on libexpat1.
teamviewer:i386 depends on libfontconfig1.
teamviewer:i386 depends on libfreetype6.
teamviewer:i386 depends on libjpeg62.
teamviewer:i386 depends on libsm6.
teamviewer:i386 depends on libxdamage1.
teamviewer:i386 depends on libxext6.
teamviewer:i386 depends on libxfixes3.
teamviewer:i386 depends on libxinerama1.
teamviewer:i386 depends on libxrandr2.
teamviewer:i386 depends on libxrender1.
teamviewer:i386 depends on libxtst6.
teamviewer:i386 depends on zlib1g.
dpkg: error processing package teamviewer:i386 (--install):
dependency problems - leaving unconfigured
Processing triggers for desktop-file-utils (0.23-1) ...
Processing triggers for mime-support (3.60) ...
Processing triggers for hicolor-icon-theme (0.15-1) ...
Errors were encountered while processing:
teamviewer:i386
Reading package lists...
Building dependency tree...
Reading state information...
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
libamd2 libbabl-0.1-0 libcamd2 libccolamd2 libcholmod3 libgegl-0.4-0
libgegl-common libgexiv2-2 libgimp2.0 libgnome2-canvas-perl
libgnome2-vfs-perl libheif1 libjson-c3 libmetis5 libmypaint-1.3-0
libmypaint-common libumfpack5 libwebpmux3 libwmf0.2-7 libx265-146
Use 'apt autoremove' to remove them.
The following packages will be REMOVED:
asunder gimp gnome-hearts gnome-ppp gsmartcontrol hardinfo libgnome2-perl
libreoffice-gtk2 lxrandr teamviewer:i386 thunar-archive-plugin
xfce4-cpugraph-plugin xfce4-dict xfce4-genmon-plugin xfce4-mount-plugin
xfce4-netload-plugin xfce4-quicklauncher-plugin xfce4-sensors-plugin
xfce4-session xfce4-smartbookmark-plugin xfce4-systemload-plugin
xfce4-verve-plugin
0 upgraded, 0 newly installed, 22 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 184 MB disk space will be freed.
Do you want to continue? [Y/n] (Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 334311 files and directories currently installed.)
Removing teamviewer:i386 (12.0.137452) ...
Removing asunder (2.8-5) ...
Removing gimp (2.10.8-0.1~mx17+1) ...
Removing gnome-hearts (0.3-2.2+b1) ...
Removing gnome-ppp (0.3.23-2.1) ...
Removing gsmartcontrol (0.8.7-1.2) ...
Removing hardinfo (0.5.1-1.5+b3) ...
Removing libgnome2-perl (1.046-3+b1) ...
Removing libreoffice-gtk2 (1:6.0.1-1~bpo9+1) ...
Removing lxrandr (0.3.1-1) ...
Removing thunar-archive-plugin (0.3.1-4) ...
Removing xfce4-cpugraph-plugin (1.0.5-1+b1) ...
Removing xfce4-dict (0.7.2-1) ...
Removing xfce4-genmon-plugin (3.4.0-2+b1) ...
Removing xfce4-mount-plugin (0.6.7-1+b1) ...
Removing xfce4-netload-plugin (1.2.4-2) ...
Removing xfce4-quicklauncher-plugin (1.9.4-11+b1) ...
Removing xfce4-sensors-plugin (1.2.6-1+b1) ...
Removing xfce4-session (4.12.1-5) ...
Removing xfce4-smartbookmark-plugin (0.4.6-2) ...
Removing xfce4-systemload-plugin (1.1.2-1+b1) ...
Removing xfce4-verve-plugin (1.1.0-1) ...
Processing triggers for mime-support (3.60) ...
Processing triggers for libreoffice-common (1:6.0.1-1~bpo9+1) ...
Processing triggers for desktop-file-utils (0.23-1) ...
Processing triggers for menu (2.1.47+b1) ...
Processing triggers for libc-bin (2.24-11+deb9u3) ...
Processing triggers for man-db (2.7.6.1-2) ...
Processing triggers for hicolor-icon-theme (0.15-1) ...
Re: MX-18 beta 1 feedback
Posted: Tue Dec 04, 2018 11:31 am
by dolphin_oracle
Fornhamfred wrote: Tue Dec 04, 2018 11:17 am
Trying to install Teamviewer with mxpi gave the following output:
Code: Select all
Hit:1 http://security.debian.org stretch/updates InRelease
Hit:2 http://ftp.uk.debian.org/debian stretch-updates InRelease
Ign:3 http://ftp.uk.debian.org/debian stretch InRelease
Hit:4 http://ftp.uk.debian.org/debian stretch Release
Hit:5 http://nl.mxrepo.com/antix/stretch stretch InRelease
Hit:6 http://nl.mxrepo.com/mx/repo stretch InRelease
Reading package lists...
--2018-12-04 16:09:44-- http://download.teamviewer.com/download/teamviewer_i386.deb
Resolving download.teamviewer.com (download.teamviewer.com)... 52.143.143.83
Connecting to download.teamviewer.com (download.teamviewer.com)|52.143.143.83|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://dl.tvcdn.de/download/version_12x/teamviewer_12.0.137452_i386.deb [following]
--2018-12-04 16:09:44-- https://dl.tvcdn.de/download/version_12x/teamviewer_12.0.137452_i386.deb
Resolving dl.tvcdn.de (dl.tvcdn.de)... 2600:9000:201f:3200:c:b82f:7ac8:dfa1, 2600:9000:201f:2c00:c:b82f:7ac8:dfa1, 2600:9000:201f:5600:c:b82f:7ac8:dfa1, ...
Connecting to dl.tvcdn.de (dl.tvcdn.de)|2600:9000:201f:3200:c:b82f:7ac8:dfa1|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 46848618 (45M) [application/octet-stream]
Saving to: ‘teamviewer_i386.deb’
37500K .......... .......... .......... .......... .......... 82% 1.59M 4s
37550K .......... .......... .......... .......... .......... 82% 2.15M 4s
37600K .......... .......... .......... .......... .......... 82% 2.14M 4s
37650K .......... .......... .......... .......... .......... 82% 2.15M 4s
37700K .......... .......... .......... .......... .......... 82% 2.17M 4s
37750K .......... .......... .......... .......... .......... 82% 1.96M 4s
37800K .......... .......... .......... .......... .......... 82% 2.17M 4s
37850K .......... .......... .......... .......... .......... 82% 2.14M 4s
37900K .......... .......... .......... .......... .......... 82% 2.15M 4s
37950K .......... .......... .......... .......... .......... 83% 2.06M 4s
38000K .......... .......... .......... .......... .......... 83% 1.64M 4s
38050K .......... .......... .......... .......... .......... 83% 2.16M 4s
38100K .......... .......... .......... .......... .......... 83% 2.06M 4s
38150K .......... .......... .......... .......... .......... 83% 2.22M 4s
38200K .......... .......... .......... .......... .......... 83% 2.07M 4s
38250K .......... .......... .......... .......... .......... 83% 2.15M 4s
38300K .......... .......... .......... .......... .......... 83% 2.14M 4s
38350K .......... .......... .......... .......... .......... 83% 2.15M 4s
38400K .......... .......... .......... .......... .......... 84% 1.65M 3s
38450K .......... .......... .......... .......... .......... 84% 2.17M 3s
38500K .......... .......... .......... .......... .......... 84% 2.14M 3s
38550K .......... .......... .......... .......... .......... 84% 2.14M 3s
38600K .......... .......... .......... .......... .......... 84% 2.05M 3s
38650K .......... .......... .......... .......... .......... 84% 2.08M 3s
38700K .......... .......... .......... .......... .......... 84% 2.12M 3s
38750K .......... .......... .......... .......... .......... 84% 2.28M 3s
38800K .......... .......... .......... .......... .......... 84% 1.54M 3s
38850K .......... .......... .......... .......... .......... 85% 2.15M 3s
38900K .......... .......... .......... .......... .......... 85% 2.15M 3s
38950K .......... .......... .......... .......... .......... 85% 2.14M 3s
39000K .......... .......... .......... .......... .......... 85% 2.14M 3s
39050K .......... .......... .......... .......... .......... 85% 2.17M 3s
39100K .......... .......... .......... .......... .......... 85% 1.70M 3s
39150K .......... .......... .......... .......... .......... 85% 2.25M 3s
39200K .......... .......... .......... .......... .......... 85% 2.46M 3s
39250K .......... .......... .......... .......... .......... 85% 1.97M 3s
39300K .......... .......... .......... .......... .......... 86% 1.78M 3s
39350K .......... .......... .......... .......... .......... 86% 2.12M 3s
39400K .......... .......... .......... .......... .......... 86% 213K 3s
39450K .......... .......... .......... .......... .......... 86% 137M 3s
39500K .......... .......... .......... .......... .......... 86% 1.91M 3s
39550K .......... .......... .......... .......... .......... 86% 2.16M 3s
39600K .......... .......... .......... .......... .......... 86% 2.19M 3s
39650K .......... .......... .......... .......... .......... 86% 124M 3s
39700K .......... .......... .......... .......... .......... 86% 139M 3s
39750K .......... .......... .......... .......... .......... 86% 1.24M 3s
39800K .......... .......... .......... .......... .......... 87% 124M 3s
39850K .......... .......... .......... .......... .......... 87% 160M 3s
39900K .......... .......... .......... .......... .......... 87% 145M 3s
39950K .......... .......... .......... .......... .......... 87% 176M 3s
40000K .......... .......... .......... .......... .......... 87% 145M 3s
40050K .......... .......... .......... .......... .......... 87% 175M 3s
40100K .......... .......... .......... .......... .......... 87% 5.69M 3s
40150K .......... .......... .......... .......... .......... 87% 2.03M 3s
40200K .......... .......... .......... .......... .......... 87% 2.16M 3s
40250K .......... .......... .......... .......... .......... 88% 2.14M 3s
40300K .......... .......... .......... .......... .......... 88% 2.15M 3s
40350K .......... .......... .......... .......... .......... 88% 2.15M 3s
40400K .......... .......... .......... .......... .......... 88% 1.66M 3s
40450K .......... .......... .......... .......... .......... 88% 2.25M 3s
40500K .......... .......... .......... .......... .......... 88% 2.14M 2s
40550K .......... .......... .......... .......... .......... 88% 2.25M 2s
40600K .......... .......... .......... .......... .......... 88% 2.15M 2s
40650K .......... .......... .......... .......... .......... 88% 1.55M 2s
40700K .......... .......... .......... .......... .......... 89% 2.22M 2s
40750K .......... .......... .......... .......... .......... 89% 2.08M 2s
40800K .......... .......... .......... .......... .......... 89% 2.14M 2s
40850K .......... .......... .......... .......... .......... 89% 2.14M 2s
40900K .......... .......... .......... .......... .......... 89% 2.15M 2s
40950K .......... .......... .......... .......... .......... 89% 2.17M 2s
41000K .......... .......... .......... .......... .......... 89% 2.13M 2s
41050K .......... .......... .......... .......... .......... 89% 1.60M 2s
41100K .......... .......... .......... .......... .......... 89% 2.15M 2s
41150K .......... .......... .......... .......... .......... 90% 2.47M 2s
41200K .......... .......... .......... .......... .......... 90% 2.06M 2s
41250K .......... .......... .......... .......... .......... 90% 1.96M 2s
41300K .......... .......... .......... .......... .......... 90% 2.15M 2s
41350K .......... .......... .......... .......... .......... 90% 2.17M 2s
41400K .......... .......... .......... .......... .......... 90% 2.04M 2s
41450K .......... .......... .......... .......... .......... 90% 2.17M 2s
41500K .......... .......... .......... .......... .......... 90% 1.54M 2s
41550K .......... .......... .......... .......... .......... 90% 2.15M 2s
41600K .......... .......... .......... .......... .......... 91% 2.27M 2s
41650K .......... .......... .......... .......... .......... 91% 2.04M 2s
41700K .......... .......... .......... .......... .......... 91% 2.16M 2s
41750K .......... .......... .......... .......... .......... 91% 2.15M 2s
41800K .......... .......... .......... .......... .......... 91% 2.24M 2s
41850K .......... .......... .......... .......... .......... 91% 2.06M 2s
41900K .......... .......... .......... .......... .......... 91% 1.72M 2s
41950K .......... .......... .......... .......... .......... 91% 2.03M 2s
42000K .......... .......... .......... .......... .......... 91% 2.17M 2s
42050K .......... .......... .......... .......... .......... 92% 1.88M 2s
42100K .......... .......... .......... .......... .......... 92% 2.08M 2s
42150K .......... .......... .......... .......... .......... 92% 2.25M 2s
42200K .......... .......... .......... .......... .......... 92% 2.05M 2s
42250K .......... .......... .......... .......... .......... 92% 2.15M 2s
42300K .......... .......... .......... .......... .......... 92% 2.17M 2s
42350K .......... .......... .......... .......... .......... 92% 2.12M 2s
42400K .......... .......... .......... .......... .......... 92% 1.61M 2s
42450K .......... .......... .......... .......... .......... 92% 2.14M 2s
42500K .......... .......... .......... .......... .......... 93% 2.15M 2s
42550K .......... .......... .......... .......... .......... 93% 2.17M 2s
42600K .......... .......... .......... .......... .......... 93% 2.12M 1s
42650K .......... .......... .......... .......... .......... 93% 2.17M 1s
42700K .......... .......... .......... .......... .......... 93% 2.15M 1s
42750K .......... .......... .......... .......... .......... 93% 2.12M 1s
42800K .......... .......... .......... .......... .......... 93% 1.61M 1s
42850K .......... .......... .......... .......... .......... 93% 2.05M 1s
42900K .......... .......... .......... .......... .......... 93% 2.25M 1s
42950K .......... .......... .......... .......... .......... 93% 2.08M 1s
43000K .......... .......... .......... .......... .......... 94% 2.21M 1s
43050K .......... .......... .......... .......... .......... 94% 2.08M 1s
43100K .......... .......... .......... .......... .......... 94% 2.14M 1s
43150K .......... .......... .......... .......... .......... 94% 2.15M 1s
43200K .......... .......... .......... .......... .......... 94% 1.83M 1s
43250K .......... .......... .......... .......... .......... 94% 1.92M 1s
43300K .......... .......... .......... .......... .......... 94% 2.21M 1s
43350K .......... .......... .......... .......... .......... 94% 2.18M 1s
43400K .......... .......... .......... .......... .......... 94% 2.23M 1s
43450K .......... .......... .......... .......... .......... 95% 1.65M 1s
43500K .......... .......... .......... .......... .......... 95% 2.17M 1s
43550K .......... .......... .......... .......... .......... 95% 2.04M 1s
43600K .......... .......... .......... .......... .......... 95% 2.27M 1s
43650K .......... .......... .......... .......... .......... 95% 2.05M 1s
43700K .......... .......... .......... .......... .......... 95% 2.12M 1s
43750K .......... .......... .......... .......... .......... 95% 2.17M 1s
43800K .......... .......... .......... .......... .......... 95% 2.16M 1s
43850K .......... .......... .......... .......... .......... 95% 1.89M 1s
43900K .......... .......... .......... .......... .......... 96% 1.99M 1s
43950K .......... .......... .......... .......... .......... 96% 1.89M 1s
44000K .......... .......... .......... .......... .......... 96% 2.38M 1s
44050K .......... .......... .......... .......... .......... 96% 2.14M 1s
44100K .......... .......... .......... .......... .......... 96% 1.59M 1s
44150K .......... .......... .......... .......... .......... 96% 2.15M 1s
44200K .......... .......... .......... .......... .......... 96% 2.17M 1s
44250K .......... .......... .......... .......... .......... 96% 2.12M 1s
44300K .......... .......... .......... .......... .......... 96% 2.16M 1s
44350K .......... .......... .......... .......... .......... 97% 2.13M 1s
44400K .......... .......... .......... .......... .......... 97% 2.16M 1s
44450K .......... .......... .......... .......... .......... 97% 1.78M 1s
44500K .......... .......... .......... .......... .......... 97% 2.12M 1s
44550K .......... .......... .......... .......... .......... 97% 2.08M 1s
44600K .......... .......... .......... .......... .......... 97% 2.05M 1s
44650K .......... .......... .......... .......... .......... 97% 2.23M 1s
44700K .......... .......... .......... .......... .......... 97% 1.99M 0s
44750K .......... .......... .......... .......... .......... 97% 2.24M 0s
44800K .......... .......... .......... .......... .......... 98% 1.65M 0s
44850K .......... .......... .......... .......... .......... 98% 2.08M 0s
44900K .......... .......... .......... .......... .......... 98% 2.12M 0s
44950K .......... .......... .......... .......... .......... 98% 2.17M 0s
45000K .......... .......... .......... .......... .......... 98% 2.14M 0s
45050K .......... .......... .......... .......... .......... 98% 2.14M 0s
45100K .......... .......... .......... .......... .......... 98% 2.06M 0s
45150K .......... .......... .......... .......... .......... 98% 1.76M 0s
45200K .......... .......... .......... .......... .......... 98% 2.15M 0s
45250K .......... .......... .......... .......... .......... 99% 2.08M 0s
45300K .......... .......... .......... .......... .......... 99% 2.11M 0s
45350K .......... .......... .......... .......... .......... 99% 2.17M 0s
45400K .......... .......... .......... .......... .......... 99% 2.15M 0s
45450K .......... .......... .......... .......... .......... 99% 2.14M 0s
45500K .......... .......... .......... .......... .......... 99% 1.60M 0s
45550K .......... .......... .......... .......... .......... 99% 2.04M 0s
45600K .......... .......... .......... .......... .......... 99% 1.99M 0s
45650K .......... .......... .......... .......... .......... 99% 1.97M 0s
45700K .......... .......... .......... .......... .......... 99% 2.24M 0s
45750K 100% 1151G=22s
2018-12-04 16:10:06 (2.05 MB/s) - ‘teamviewer_i386.deb’ saved [46848618/46848618]
Selecting previously unselected package teamviewer:i386.
(Reading database ... 334011 files and directories currently installed.)
Preparing to unpack teamviewer_i386.deb ...
Unpacking teamviewer:i386 (12.0.137452) ...
dpkg: dependency problems prevent configuration of teamviewer:i386:
teamviewer:i386 depends on libasound2.
teamviewer:i386 depends on libdbus-1-3.
teamviewer:i386 depends on libexpat1.
teamviewer:i386 depends on libfontconfig1.
teamviewer:i386 depends on libfreetype6.
teamviewer:i386 depends on libjpeg62.
teamviewer:i386 depends on libsm6.
teamviewer:i386 depends on libxdamage1.
teamviewer:i386 depends on libxext6.
teamviewer:i386 depends on libxfixes3.
teamviewer:i386 depends on libxinerama1.
teamviewer:i386 depends on libxrandr2.
teamviewer:i386 depends on libxrender1.
teamviewer:i386 depends on libxtst6.
teamviewer:i386 depends on zlib1g.
dpkg: error processing package teamviewer:i386 (--install):
dependency problems - leaving unconfigured
Processing triggers for desktop-file-utils (0.23-1) ...
Processing triggers for mime-support (3.60) ...
Processing triggers for hicolor-icon-theme (0.15-1) ...
Errors were encountered while processing:
teamviewer:i386
Reading package lists...
Building dependency tree...
Reading state information...
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
libamd2 libbabl-0.1-0 libcamd2 libccolamd2 libcholmod3 libgegl-0.4-0
libgegl-common libgexiv2-2 libgimp2.0 libgnome2-canvas-perl
libgnome2-vfs-perl libheif1 libjson-c3 libmetis5 libmypaint-1.3-0
libmypaint-common libumfpack5 libwebpmux3 libwmf0.2-7 libx265-146
Use 'apt autoremove' to remove them.
The following packages will be REMOVED:
asunder gimp gnome-hearts gnome-ppp gsmartcontrol hardinfo libgnome2-perl
libreoffice-gtk2 lxrandr teamviewer:i386 thunar-archive-plugin
xfce4-cpugraph-plugin xfce4-dict xfce4-genmon-plugin xfce4-mount-plugin
xfce4-netload-plugin xfce4-quicklauncher-plugin xfce4-sensors-plugin
xfce4-session xfce4-smartbookmark-plugin xfce4-systemload-plugin
xfce4-verve-plugin
0 upgraded, 0 newly installed, 22 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 184 MB disk space will be freed.
Do you want to continue? [Y/n] (Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 334311 files and directories currently installed.)
Removing teamviewer:i386 (12.0.137452) ...
Removing asunder (2.8-5) ...
Removing gimp (2.10.8-0.1~mx17+1) ...
Removing gnome-hearts (0.3-2.2+b1) ...
Removing gnome-ppp (0.3.23-2.1) ...
Removing gsmartcontrol (0.8.7-1.2) ...
Removing hardinfo (0.5.1-1.5+b3) ...
Removing libgnome2-perl (1.046-3+b1) ...
Removing libreoffice-gtk2 (1:6.0.1-1~bpo9+1) ...
Removing lxrandr (0.3.1-1) ...
Removing thunar-archive-plugin (0.3.1-4) ...
Removing xfce4-cpugraph-plugin (1.0.5-1+b1) ...
Removing xfce4-dict (0.7.2-1) ...
Removing xfce4-genmon-plugin (3.4.0-2+b1) ...
Removing xfce4-mount-plugin (0.6.7-1+b1) ...
Removing xfce4-netload-plugin (1.2.4-2) ...
Removing xfce4-quicklauncher-plugin (1.9.4-11+b1) ...
Removing xfce4-sensors-plugin (1.2.6-1+b1) ...
Removing xfce4-session (4.12.1-5) ...
Removing xfce4-smartbookmark-plugin (0.4.6-2) ...
Removing xfce4-systemload-plugin (1.1.2-1+b1) ...
Removing xfce4-verve-plugin (1.1.0-1) ...
Processing triggers for mime-support (3.60) ...
Processing triggers for libreoffice-common (1:6.0.1-1~bpo9+1) ...
Processing triggers for desktop-file-utils (0.23-1) ...
Processing triggers for menu (2.1.47+b1) ...
Processing triggers for libc-bin (2.24-11+deb9u3) ...
Processing triggers for man-db (2.7.6.1-2) ...
Processing triggers for hicolor-icon-theme (0.15-1) ...
thanks we will check that out.
Re: MX-18 beta 1 feedback
Posted: Tue Dec 04, 2018 11:43 am
by male
[OT on
teamviewer has long been obsolete
The magic word today is
anyDesk
OT off]
Re: MX-18 beta 1 feedback
Posted: Tue Dec 04, 2018 12:07 pm
by Fornhamfred
OK seem to have broken the install. Setup two samba shares to connect continuously, now will not load past login. Tried with both user and root.
Re: MX-18 beta 1 feedback
Posted: Tue Dec 04, 2018 12:52 pm
by dolphin_oracle
fehlix wrote: Mon Dec 03, 2018 8:04 pm
manyroads wrote: Mon Dec 03, 2018 4:59 pm
I installed on a VirtualBox using UEFI... the install and build went well; as did my customization. On reboot I have a complete and total crash. I will download and try again; as time permits.
One easy way to have MX18b1_x64 to get installed in Oracle VM VirtualBox UEFI mode together with
straight booting into the Grub-menu without any issues in UEFI mode:
Booting MX18-Linux in UEFI-mode in VirtualBox
This in UEFI install from the LiveISO on Oracle VM VirtualBox.
After installation, rebooting with VirtualBox internal boot menu by selecting manual /EFI/MX18/gubx64.efi.
Within booted MX18-Linux those additonal stepps need to be performed or verified:
1- check/create missing fstab-entry for ESP/efi partition
Code: Select all
echo "UUID=$(lsblk -no 'UUID,LABEL,FSTYPE,PARTLABEL' | grep -m1 -iE 'vfat|esp|efi' | cut -d' ' -f1) /boot/efi vfat defaults 0 0" | sudo tee -a /etc/fstab
UUID=A555-0A81 /boot/efi vfat defaults 0 0
Code: Select all
sudo "mkdir -p /boot/efi/EFI/BOOT && cp /boot/efi/EFI/MX18/grubx64.efi /boot/efi/EFI/BOOT/bootx64.efi"
That's it. Reboot and the Grub menu will show up.
Note: The above steps could also made within booted LiveISO or potentially as a nice adjustment to the existing installer.
I've looked at that in the past, but because the fallback EFI is in the same location for all OS's, including windows, we have avoided setting it. Its getting to be less of an issue, but in the early days of UEFI boots, many manufacturers shipped stupid UEFI setups that only looked at the fallback location, which could be bad for dual-booters that decide not to dual boot anymore.
Re: MX-18 beta 1 feedback
Posted: Tue Dec 04, 2018 1:09 pm
by fehlix
dolphin_oracle wrote: Tue Dec 04, 2018 12:52 pm
fehlix wrote: Mon Dec 03, 2018 8:04 pm
manyroads wrote: Mon Dec 03, 2018 4:59 pm
I installed on a VirtualBox using UEFI... the install and build went well; as did my customization. On reboot I have a complete and total crash. I will download and try again; as time permits.
One easy way to have MX18b1_x64 to get installed in Oracle VM VirtualBox UEFI mode together with
straight booting into the Grub-menu without any issues in UEFI mode:
Booting MX18-Linux in UEFI-mode in VirtualBox
This in UEFI install from the LiveISO on Oracle VM VirtualBox.
After installation, rebooting with VirtualBox internal boot menu by selecting manual /EFI/MX18/gubx64.efi.
Within booted MX18-Linux those additonal stepps need to be performed or verified:
1- check/create missing fstab-entry for ESP/efi partition
Code: Select all
echo "UUID=$(lsblk -no 'UUID,LABEL,FSTYPE,PARTLABEL' | grep -m1 -iE 'vfat|esp|efi' | cut -d' ' -f1) /boot/efi vfat defaults 0 0" | sudo tee -a /etc/fstab
UUID=A555-0A81 /boot/efi vfat defaults 0 0
Code: Select all
sudo "mkdir -p /boot/efi/EFI/BOOT && cp /boot/efi/EFI/MX18/grubx64.efi /boot/efi/EFI/BOOT/bootx64.efi"
That's it. Reboot and the Grub menu will show up.
Note: The above steps could also made within booted LiveISO or potentially as a nice adjustment to the existing installer.
I've looked at that in the past, but because the fallback EFI is in the same location for all OS's, including windows, we have avoided setting it. Its getting to be less of an issue, but in the early days of UEFI boots, many manufacturers shipped stupid UEFI setups that only looked at the fallback location, which could be bad for dual-booters that decide not to dual boot anymore.
At least it could be considerd optional, i.e. if no fallbak /EFI/BOOT/bootx64.efi is already available we could provide the MX-fallback.
This would help lot of user who cannt boot even after having susccesfully installed, for whatever reasons.
Or even smarter: not copy MX18/grubx64.efi but use shims real fallbak.efi copied to /EFI/BOOT/bootx64.efi and have
/EFI/MX18/BOOT.CSV with the content of pointing to boot into MX. By this we could even reinstall grub (i.e. regenrating grubx64.efi).
shims falback.efi to look for /EFI/MX18/BOOT.CSV which inturn boots into /EFI/MX18/grubx64.efi .
The /EFI/MX18/BOOT.CSV would look something like
Code: Select all
grubx64.efi,MX_Linux,,MX Linux Grub Boot Menu
EDIT: Note the bootx64.efi falbak is normaly not used, even provided by MS. It's just made such in case that it will always boot in to winOS.
winOS has normal it's own nvram entry which is used. only of nvram table is empty the fallbak get's triggered. and if we show an option to boot into MX in such a case, the user still can boot winOS. we could even offer to revert bak the original ms-fallback....
Re: MX-18 beta 1 feedback
Posted: Tue Dec 04, 2018 1:42 pm
by Adrian
entropyfoe wrote: Tue Dec 04, 2018 10:46 am
Looks like Czech.
The C with the little "v" over it is Czech or some other similar Slavic language.
Also Greek the first entry, it's something that shows in Xfce Settings -> Appearance -> Fonts -> Arial
Re: MX-18 beta 1 feedback
Posted: Tue Dec 04, 2018 2:02 pm
by fehlix
Adrian wrote: Tue Dec 04, 2018 1:42 pm
entropyfoe wrote: Tue Dec 04, 2018 10:46 am
Looks like Czech.
The C with the little "v" over it is Czech or some other similar Slavic language.
Also Greek the first entry, it's something that shows in Xfce Settings -> Appearance -> Fonts -> Arial
Those are all part of the downloaded mscorefonts, the are not part of the debian system. Problay we need top look for a fixed version.
Re: MX-18 beta 1 feedback
Posted: Tue Dec 04, 2018 2:16 pm
by Stevo
You can currently install the compatible Virtual Box 5.2.22 on the beta from the test repo, but we're moving it to main to eliminate the problem with MXPI.
Re: MX-18 beta 1 feedback
Posted: Tue Dec 04, 2018 2:18 pm
by dolphin_oracle
fehlix wrote: Tue Dec 04, 2018 2:02 pm
Adrian wrote: Tue Dec 04, 2018 1:42 pm
entropyfoe wrote: Tue Dec 04, 2018 10:46 am
Looks like Czech.
The C with the little "v" over it is Czech or some other similar Slavic language.
Also Greek the first entry, it's something that shows in Xfce Settings -> Appearance -> Fonts -> Arial
Those are all part of the downloaded mscorefonts, the are not part of the debian system. Problay we need top look for a fixed version.
possible. could be a build problem too.
but we also updated libfontconfig and libfreetype, which could also be related.
Is there a font cache rebuild function, and if so, does that clear up the problem?
Re: MX-18 beta 1 feedback
Posted: Tue Dec 04, 2018 2:20 pm
by Stevo
dolphin_oracle wrote: Tue Dec 04, 2018 11:31 am
Fornhamfred wrote: Tue Dec 04, 2018 11:17 am
Trying to install Teamviewer with mxpi gave the following output:
Code: Select all
Hit:1 http://security.debian.org stretch/updates InRelease
Hit:2 http://ftp.uk.debian.org/debian stretch-updates InRelease
Ign:3 http://ftp.uk.debian.org/debian stretch InRelease
Hit:4 http://ftp.uk.debian.org/debian stretch Release
Hit:5 http://nl.mxrepo.com/antix/stretch stretch InRelease
Hit:6 http://nl.mxrepo.com/mx/repo stretch InRelease
Reading package lists...
--2018-12-04 16:09:44-- http://download.teamviewer.com/download/teamviewer_i386.deb
Resolving download.teamviewer.com (download.teamviewer.com)... 52.143.143.83
Connecting to download.teamviewer.com (download.teamviewer.com)|52.143.143.83|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://dl.tvcdn.de/download/version_12x/teamviewer_12.0.137452_i386.deb [following]
--2018-12-04 16:09:44-- https://dl.tvcdn.de/download/version_12x/teamviewer_12.0.137452_i386.deb
Resolving dl.tvcdn.de (dl.tvcdn.de)... 2600:9000:201f:3200:c:b82f:7ac8:dfa1, 2600:9000:201f:2c00:c:b82f:7ac8:dfa1, 2600:9000:201f:5600:c:b82f:7ac8:dfa1, ...
Connecting to dl.tvcdn.de (dl.tvcdn.de)|2600:9000:201f:3200:c:b82f:7ac8:dfa1|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 46848618 (45M) [application/octet-stream]
Saving to: ‘teamviewer_i386.deb’
37500K .......... .......... .......... .......... .......... 82% 1.59M 4s
37550K .......... .......... .......... .......... .......... 82% 2.15M 4s
37600K .......... .......... .......... .......... .......... 82% 2.14M 4s
37650K .......... .......... .......... .......... .......... 82% 2.15M 4s
37700K .......... .......... .......... .......... .......... 82% 2.17M 4s
37750K .......... .......... .......... .......... .......... 82% 1.96M 4s
37800K .......... .......... .......... .......... .......... 82% 2.17M 4s
37850K .......... .......... .......... .......... .......... 82% 2.14M 4s
37900K .......... .......... .......... .......... .......... 82% 2.15M 4s
37950K .......... .......... .......... .......... .......... 83% 2.06M 4s
38000K .......... .......... .......... .......... .......... 83% 1.64M 4s
38050K .......... .......... .......... .......... .......... 83% 2.16M 4s
38100K .......... .......... .......... .......... .......... 83% 2.06M 4s
38150K .......... .......... .......... .......... .......... 83% 2.22M 4s
38200K .......... .......... .......... .......... .......... 83% 2.07M 4s
38250K .......... .......... .......... .......... .......... 83% 2.15M 4s
38300K .......... .......... .......... .......... .......... 83% 2.14M 4s
38350K .......... .......... .......... .......... .......... 83% 2.15M 4s
38400K .......... .......... .......... .......... .......... 84% 1.65M 3s
38450K .......... .......... .......... .......... .......... 84% 2.17M 3s
38500K .......... .......... .......... .......... .......... 84% 2.14M 3s
38550K .......... .......... .......... .......... .......... 84% 2.14M 3s
38600K .......... .......... .......... .......... .......... 84% 2.05M 3s
38650K .......... .......... .......... .......... .......... 84% 2.08M 3s
38700K .......... .......... .......... .......... .......... 84% 2.12M 3s
38750K .......... .......... .......... .......... .......... 84% 2.28M 3s
38800K .......... .......... .......... .......... .......... 84% 1.54M 3s
38850K .......... .......... .......... .......... .......... 85% 2.15M 3s
38900K .......... .......... .......... .......... .......... 85% 2.15M 3s
38950K .......... .......... .......... .......... .......... 85% 2.14M 3s
39000K .......... .......... .......... .......... .......... 85% 2.14M 3s
39050K .......... .......... .......... .......... .......... 85% 2.17M 3s
39100K .......... .......... .......... .......... .......... 85% 1.70M 3s
39150K .......... .......... .......... .......... .......... 85% 2.25M 3s
39200K .......... .......... .......... .......... .......... 85% 2.46M 3s
39250K .......... .......... .......... .......... .......... 85% 1.97M 3s
39300K .......... .......... .......... .......... .......... 86% 1.78M 3s
39350K .......... .......... .......... .......... .......... 86% 2.12M 3s
39400K .......... .......... .......... .......... .......... 86% 213K 3s
39450K .......... .......... .......... .......... .......... 86% 137M 3s
39500K .......... .......... .......... .......... .......... 86% 1.91M 3s
39550K .......... .......... .......... .......... .......... 86% 2.16M 3s
39600K .......... .......... .......... .......... .......... 86% 2.19M 3s
39650K .......... .......... .......... .......... .......... 86% 124M 3s
39700K .......... .......... .......... .......... .......... 86% 139M 3s
39750K .......... .......... .......... .......... .......... 86% 1.24M 3s
39800K .......... .......... .......... .......... .......... 87% 124M 3s
39850K .......... .......... .......... .......... .......... 87% 160M 3s
39900K .......... .......... .......... .......... .......... 87% 145M 3s
39950K .......... .......... .......... .......... .......... 87% 176M 3s
40000K .......... .......... .......... .......... .......... 87% 145M 3s
40050K .......... .......... .......... .......... .......... 87% 175M 3s
40100K .......... .......... .......... .......... .......... 87% 5.69M 3s
40150K .......... .......... .......... .......... .......... 87% 2.03M 3s
40200K .......... .......... .......... .......... .......... 87% 2.16M 3s
40250K .......... .......... .......... .......... .......... 88% 2.14M 3s
40300K .......... .......... .......... .......... .......... 88% 2.15M 3s
40350K .......... .......... .......... .......... .......... 88% 2.15M 3s
40400K .......... .......... .......... .......... .......... 88% 1.66M 3s
40450K .......... .......... .......... .......... .......... 88% 2.25M 3s
40500K .......... .......... .......... .......... .......... 88% 2.14M 2s
40550K .......... .......... .......... .......... .......... 88% 2.25M 2s
40600K .......... .......... .......... .......... .......... 88% 2.15M 2s
40650K .......... .......... .......... .......... .......... 88% 1.55M 2s
40700K .......... .......... .......... .......... .......... 89% 2.22M 2s
40750K .......... .......... .......... .......... .......... 89% 2.08M 2s
40800K .......... .......... .......... .......... .......... 89% 2.14M 2s
40850K .......... .......... .......... .......... .......... 89% 2.14M 2s
40900K .......... .......... .......... .......... .......... 89% 2.15M 2s
40950K .......... .......... .......... .......... .......... 89% 2.17M 2s
41000K .......... .......... .......... .......... .......... 89% 2.13M 2s
41050K .......... .......... .......... .......... .......... 89% 1.60M 2s
41100K .......... .......... .......... .......... .......... 89% 2.15M 2s
41150K .......... .......... .......... .......... .......... 90% 2.47M 2s
41200K .......... .......... .......... .......... .......... 90% 2.06M 2s
41250K .......... .......... .......... .......... .......... 90% 1.96M 2s
41300K .......... .......... .......... .......... .......... 90% 2.15M 2s
41350K .......... .......... .......... .......... .......... 90% 2.17M 2s
41400K .......... .......... .......... .......... .......... 90% 2.04M 2s
41450K .......... .......... .......... .......... .......... 90% 2.17M 2s
41500K .......... .......... .......... .......... .......... 90% 1.54M 2s
41550K .......... .......... .......... .......... .......... 90% 2.15M 2s
41600K .......... .......... .......... .......... .......... 91% 2.27M 2s
41650K .......... .......... .......... .......... .......... 91% 2.04M 2s
41700K .......... .......... .......... .......... .......... 91% 2.16M 2s
41750K .......... .......... .......... .......... .......... 91% 2.15M 2s
41800K .......... .......... .......... .......... .......... 91% 2.24M 2s
41850K .......... .......... .......... .......... .......... 91% 2.06M 2s
41900K .......... .......... .......... .......... .......... 91% 1.72M 2s
41950K .......... .......... .......... .......... .......... 91% 2.03M 2s
42000K .......... .......... .......... .......... .......... 91% 2.17M 2s
42050K .......... .......... .......... .......... .......... 92% 1.88M 2s
42100K .......... .......... .......... .......... .......... 92% 2.08M 2s
42150K .......... .......... .......... .......... .......... 92% 2.25M 2s
42200K .......... .......... .......... .......... .......... 92% 2.05M 2s
42250K .......... .......... .......... .......... .......... 92% 2.15M 2s
42300K .......... .......... .......... .......... .......... 92% 2.17M 2s
42350K .......... .......... .......... .......... .......... 92% 2.12M 2s
42400K .......... .......... .......... .......... .......... 92% 1.61M 2s
42450K .......... .......... .......... .......... .......... 92% 2.14M 2s
42500K .......... .......... .......... .......... .......... 93% 2.15M 2s
42550K .......... .......... .......... .......... .......... 93% 2.17M 2s
42600K .......... .......... .......... .......... .......... 93% 2.12M 1s
42650K .......... .......... .......... .......... .......... 93% 2.17M 1s
42700K .......... .......... .......... .......... .......... 93% 2.15M 1s
42750K .......... .......... .......... .......... .......... 93% 2.12M 1s
42800K .......... .......... .......... .......... .......... 93% 1.61M 1s
42850K .......... .......... .......... .......... .......... 93% 2.05M 1s
42900K .......... .......... .......... .......... .......... 93% 2.25M 1s
42950K .......... .......... .......... .......... .......... 93% 2.08M 1s
43000K .......... .......... .......... .......... .......... 94% 2.21M 1s
43050K .......... .......... .......... .......... .......... 94% 2.08M 1s
43100K .......... .......... .......... .......... .......... 94% 2.14M 1s
43150K .......... .......... .......... .......... .......... 94% 2.15M 1s
43200K .......... .......... .......... .......... .......... 94% 1.83M 1s
43250K .......... .......... .......... .......... .......... 94% 1.92M 1s
43300K .......... .......... .......... .......... .......... 94% 2.21M 1s
43350K .......... .......... .......... .......... .......... 94% 2.18M 1s
43400K .......... .......... .......... .......... .......... 94% 2.23M 1s
43450K .......... .......... .......... .......... .......... 95% 1.65M 1s
43500K .......... .......... .......... .......... .......... 95% 2.17M 1s
43550K .......... .......... .......... .......... .......... 95% 2.04M 1s
43600K .......... .......... .......... .......... .......... 95% 2.27M 1s
43650K .......... .......... .......... .......... .......... 95% 2.05M 1s
43700K .......... .......... .......... .......... .......... 95% 2.12M 1s
43750K .......... .......... .......... .......... .......... 95% 2.17M 1s
43800K .......... .......... .......... .......... .......... 95% 2.16M 1s
43850K .......... .......... .......... .......... .......... 95% 1.89M 1s
43900K .......... .......... .......... .......... .......... 96% 1.99M 1s
43950K .......... .......... .......... .......... .......... 96% 1.89M 1s
44000K .......... .......... .......... .......... .......... 96% 2.38M 1s
44050K .......... .......... .......... .......... .......... 96% 2.14M 1s
44100K .......... .......... .......... .......... .......... 96% 1.59M 1s
44150K .......... .......... .......... .......... .......... 96% 2.15M 1s
44200K .......... .......... .......... .......... .......... 96% 2.17M 1s
44250K .......... .......... .......... .......... .......... 96% 2.12M 1s
44300K .......... .......... .......... .......... .......... 96% 2.16M 1s
44350K .......... .......... .......... .......... .......... 97% 2.13M 1s
44400K .......... .......... .......... .......... .......... 97% 2.16M 1s
44450K .......... .......... .......... .......... .......... 97% 1.78M 1s
44500K .......... .......... .......... .......... .......... 97% 2.12M 1s
44550K .......... .......... .......... .......... .......... 97% 2.08M 1s
44600K .......... .......... .......... .......... .......... 97% 2.05M 1s
44650K .......... .......... .......... .......... .......... 97% 2.23M 1s
44700K .......... .......... .......... .......... .......... 97% 1.99M 0s
44750K .......... .......... .......... .......... .......... 97% 2.24M 0s
44800K .......... .......... .......... .......... .......... 98% 1.65M 0s
44850K .......... .......... .......... .......... .......... 98% 2.08M 0s
44900K .......... .......... .......... .......... .......... 98% 2.12M 0s
44950K .......... .......... .......... .......... .......... 98% 2.17M 0s
45000K .......... .......... .......... .......... .......... 98% 2.14M 0s
45050K .......... .......... .......... .......... .......... 98% 2.14M 0s
45100K .......... .......... .......... .......... .......... 98% 2.06M 0s
45150K .......... .......... .......... .......... .......... 98% 1.76M 0s
45200K .......... .......... .......... .......... .......... 98% 2.15M 0s
45250K .......... .......... .......... .......... .......... 99% 2.08M 0s
45300K .......... .......... .......... .......... .......... 99% 2.11M 0s
45350K .......... .......... .......... .......... .......... 99% 2.17M 0s
45400K .......... .......... .......... .......... .......... 99% 2.15M 0s
45450K .......... .......... .......... .......... .......... 99% 2.14M 0s
45500K .......... .......... .......... .......... .......... 99% 1.60M 0s
45550K .......... .......... .......... .......... .......... 99% 2.04M 0s
45600K .......... .......... .......... .......... .......... 99% 1.99M 0s
45650K .......... .......... .......... .......... .......... 99% 1.97M 0s
45700K .......... .......... .......... .......... .......... 99% 2.24M 0s
45750K 100% 1151G=22s
2018-12-04 16:10:06 (2.05 MB/s) - ‘teamviewer_i386.deb’ saved [46848618/46848618]
Selecting previously unselected package teamviewer:i386.
(Reading database ... 334011 files and directories currently installed.)
Preparing to unpack teamviewer_i386.deb ...
Unpacking teamviewer:i386 (12.0.137452) ...
dpkg: dependency problems prevent configuration of teamviewer:i386:
teamviewer:i386 depends on libasound2.
teamviewer:i386 depends on libdbus-1-3.
teamviewer:i386 depends on libexpat1.
teamviewer:i386 depends on libfontconfig1.
teamviewer:i386 depends on libfreetype6.
teamviewer:i386 depends on libjpeg62.
teamviewer:i386 depends on libsm6.
teamviewer:i386 depends on libxdamage1.
teamviewer:i386 depends on libxext6.
teamviewer:i386 depends on libxfixes3.
teamviewer:i386 depends on libxinerama1.
teamviewer:i386 depends on libxrandr2.
teamviewer:i386 depends on libxrender1.
teamviewer:i386 depends on libxtst6.
teamviewer:i386 depends on zlib1g.
dpkg: error processing package teamviewer:i386 (--install):
dependency problems - leaving unconfigured
Processing triggers for desktop-file-utils (0.23-1) ...
Processing triggers for mime-support (3.60) ...
Processing triggers for hicolor-icon-theme (0.15-1) ...
Errors were encountered while processing:
teamviewer:i386
Reading package lists...
Building dependency tree...
Reading state information...
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
libamd2 libbabl-0.1-0 libcamd2 libccolamd2 libcholmod3 libgegl-0.4-0
libgegl-common libgexiv2-2 libgimp2.0 libgnome2-canvas-perl
libgnome2-vfs-perl libheif1 libjson-c3 libmetis5 libmypaint-1.3-0
libmypaint-common libumfpack5 libwebpmux3 libwmf0.2-7 libx265-146
Use 'apt autoremove' to remove them.
The following packages will be REMOVED:
asunder gimp gnome-hearts gnome-ppp gsmartcontrol hardinfo libgnome2-perl
libreoffice-gtk2 lxrandr teamviewer:i386 thunar-archive-plugin
xfce4-cpugraph-plugin xfce4-dict xfce4-genmon-plugin xfce4-mount-plugin
xfce4-netload-plugin xfce4-quicklauncher-plugin xfce4-sensors-plugin
xfce4-session xfce4-smartbookmark-plugin xfce4-systemload-plugin
xfce4-verve-plugin
0 upgraded, 0 newly installed, 22 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 184 MB disk space will be freed.
Do you want to continue? [Y/n] (Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 334311 files and directories currently installed.)
Removing teamviewer:i386 (12.0.137452) ...
Removing asunder (2.8-5) ...
Removing gimp (2.10.8-0.1~mx17+1) ...
Removing gnome-hearts (0.3-2.2+b1) ...
Removing gnome-ppp (0.3.23-2.1) ...
Removing gsmartcontrol (0.8.7-1.2) ...
Removing hardinfo (0.5.1-1.5+b3) ...
Removing libgnome2-perl (1.046-3+b1) ...
Removing libreoffice-gtk2 (1:6.0.1-1~bpo9+1) ...
Removing lxrandr (0.3.1-1) ...
Removing thunar-archive-plugin (0.3.1-4) ...
Removing xfce4-cpugraph-plugin (1.0.5-1+b1) ...
Removing xfce4-dict (0.7.2-1) ...
Removing xfce4-genmon-plugin (3.4.0-2+b1) ...
Removing xfce4-mount-plugin (0.6.7-1+b1) ...
Removing xfce4-netload-plugin (1.2.4-2) ...
Removing xfce4-quicklauncher-plugin (1.9.4-11+b1) ...
Removing xfce4-sensors-plugin (1.2.6-1+b1) ...
Removing xfce4-session (4.12.1-5) ...
Removing xfce4-smartbookmark-plugin (0.4.6-2) ...
Removing xfce4-systemload-plugin (1.1.2-1+b1) ...
Removing xfce4-verve-plugin (1.1.0-1) ...
Processing triggers for mime-support (3.60) ...
Processing triggers for libreoffice-common (1:6.0.1-1~bpo9+1) ...
Processing triggers for desktop-file-utils (0.23-1) ...
Processing triggers for menu (2.1.47+b1) ...
Processing triggers for libc-bin (2.24-11+deb9u3) ...
Processing triggers for man-db (2.7.6.1-2) ...
Processing triggers for hicolor-icon-theme (0.15-1) ...
thanks we will check that out.
Probably the same problem as the Wine staging installs (teamviewer uses its own Wine), which is probably due to that wanting to install some i386 Mesa libraries with the dev repo disabled, so they aren't available.
Re: MX-18 beta 1 feedback
Posted: Tue Dec 04, 2018 3:18 pm
by j2mcgreg
Everything works on an HP Pavillion P7-1019 including the NVidia video card. Here's the inxi output:
Code: Select all
CPU: Topology: Dual Core model: Intel Pentium G620 bits: 64 type: MCP L2 cache: 3072 KiB
Speed: 1596 MHz min/max: 1600/2600 MHz Core speeds (MHz): 1: 1596 2: 1596
Graphics: Device-1: NVIDIA GT218 [GeForce 8400 GS Rev. 3] driver: nouveau v: kernel
Display: x11 server: X.Org 1.19.2 driver: nouveau unloaded: fbdev,modesetting,vesa
resolution: 1600x900~60Hz
OpenGL: renderer: NVA8 v: 3.3 Mesa 18.2.6
Audio: Device-1: Intel 6 Series/C200 Series Family High Definition Audio
driver: snd_hda_intel
Device-2: NVIDIA High Definition Audio driver: snd_hda_intel
Sound Server: ALSA v: k4.19.0-1-amd64
Network: Device-1: Ralink RT5390 Wireless 802.11n 1T/1R PCIe driver: rt2800pci
IF: wlan0 state: down mac: 0e:4a:44:67:38:cc
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169
IF: eth0 state: down mac: e0:69:95:da:27:94
Drives: Local Storage: total: 960.39 GiB used: 27.93 GiB (2.9%)
ID-1: /dev/sda vendor: Hitachi model: HDS721010CLA332 size: 931.51 GiB
ID-2: /dev/sdf type: USB vendor: Kingston model: DataTraveler 3.0 size: 28.88 GiB
Partition: ID-1: / size: 913.89 GiB used: 4.63 GiB (0.5%) fs: ext4 dev: /dev/sda1
ID-2: swap-1 size: 2.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2
Sensors: System Temperatures: cpu: 32.0 C mobo: N/A gpu: nouveau temp: 36 C
Fan Speeds (RPM): N/A
Info: Processes: 170 Uptime: 6m Memory: 3.84 GiB used: 476.7 MiB (12.1%) Shell: bash
inxi: 3.0.25
Re: MX-18 beta 1 feedback
Posted: Tue Dec 04, 2018 8:09 pm
by danielson
Could having no swap partition but only / be the reason sleep mode not working for me?
Have decent SSD with 8Gs of RAM.
Re: MX-18 beta 1 feedback
Posted: Tue Dec 04, 2018 8:14 pm
by Adrian
danielson wrote: Tue Dec 04, 2018 8:09 pm
Could having no swap partition but only / be the reason sleep mode not working for me?
Have decent SSD with 8Gs of RAM.
I don't think so, hibernation needs swap, sleep uses RAM.
Re: MX-18 beta 1 feedback
Posted: Tue Dec 04, 2018 8:34 pm
by fehlix
Stevo wrote: Tue Dec 04, 2018 2:20 pm
dolphin_oracle wrote: Tue Dec 04, 2018 11:31 am
Fornhamfred wrote: Tue Dec 04, 2018 11:17 am
Trying to install Teamviewer with mxpi ..
thanks we will check that out.
Probably the same problem as the Wine staging installs (teamviewer uses its own Wine), which is probably due to that wanting to install some i386 Mesa libraries with the dev repo disabled, so they aren't available.
Yes,Teamviewer 12 installs and runs fine in "MX18_x64 Continuum March 14 2018"-upgraded from MX17.1 with having dev-repo enabled.
Re: MX-18 beta 1 feedback-now working perfectly
Posted: Tue Dec 04, 2018 9:07 pm
by entropyfoe
Excellent ! After a fresh reboot uses 449M of memory. Samba working automatically OTB.
I had the crash at idle again, so the boot code is needed.
I added manually to /etc/default/grub, the line rcu_nocbs=0-11
This completely stabilized my MX 17, so I am sure this will work again. [wish those kernel gurus would fix that]
Update-grub as root.
Reboot, looks good.
Now for nvidia-
I added the mx18 dev repo to synapic manually, once I figured out no space between MX and 18 !
Reload repos.
Use the MXPI nvidia installer. The only tricky part is which version to pick?
1. main 390.87-2-bpo9+1MX17+2 or
2. debian-backports 390.87-2-bpo9+1
I chose 1, as they seem the same, except one says MX17.
Rebooted, and voila, correct nvidia driver is loaded, and the nvidia card runs 5 degrees cooler !
Should I keep that MX18 dev repo enabled?
All that remains is the stability test, and based on past experience with the Ryzen, if this machine is still running tomorrow morning, stability is there, this time tomorrow, confirmed.
So this is pretty much equal to the MX 17.1 as far as functionality once stability is confirmed. Again, looks great, excellent beta quality, with some help from the experts
[adrian, d_o, Richb, Stevo....] here, fixing the installer grub to root, describing how to get the nvidia, and add the grub line with no grub customizer - this is close to a keeper, certainly I will use as a daily driver, do more testing, until the next beta or RC.
Code: Select all
System: Host: Ryzen Kernel: 4.19.0-1-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3
Distro: MX-18b1_x64 Continuum December 3 2018
Machine: Type: Desktop Mobo: ASUSTeK model: PRIME X370-PRO v: Rev X.0x serial: <root required>
UEFI [Legacy]: American Megatrends v: 1201 date: 10/18/2017
CPU: Topology: 6-Core model: AMD Ryzen 5 1600X bits: 64 type: MT MCP L2 cache: 3072 KiB
Speed: 3590 MHz min/max: 2200/3600 MHz Core speeds (MHz): 1: 1880 2: 1878 3: 1880
4: 1879 5: 1878 6: 1879 7: 1881 8: 1879 9: 1879 10: 1878 11: 1909 12: 2015
Graphics: Device-1: NVIDIA GK208 [GeForce GT 710B] driver: nvidia v: 390.87
Display: x11 server: X.Org 1.19.2 driver: nvidia resolution: 1920x1080~60Hz
OpenGL: renderer: GeForce GT 710/PCIe/SSE2 v: 4.6.0 NVIDIA 390.87
Audio: Device-1: NVIDIA GK208 HDMI/DP Audio driver: snd_hda_intel
Device-2: AMD driver: snd_hda_intel
Sound Server: ALSA v: k4.19.0-1-amd64
Network: Device-1: Intel I211 Gigabit Network driver: igb
IF: eth0 state: up speed: 100 Mbps duplex:
Drives: Local Storage: total: 1.14 TiB used: 469.36 GiB (40.3%)
ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 960 EVO 250GB size: 232.89 GiB
ID-2: /dev/sda vendor: Samsung model: SSD 850 EVO 1TB size: 931.51 GiB
Partition: ID-1: / size: 100.88 GiB used: 5.88 GiB (5.8%) fs: ext4 dev: /dev/nvme0n1p4
ID-2: swap-1 size: 16.60 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/nvme0n1p2
Sensors: System Temperatures: cpu: 25.4 C mobo: N/A gpu: nvidia temp: 39 C
Fan Speeds (RPM): cpu: 0 gpu: nvidia fan: 50%
Info: Processes: 260 Uptime: 7m Memory: 15.66 GiB used: 535.5 MiB (3.3%) Shell: bash
inxi: 3.0.25
Re: MX-18 beta 1 feedback
Posted: Wed Dec 05, 2018 12:05 am
by zukahn1
Have tried this on several USB setups great distro works good on older Dell Latitude laptop with 2.0 USB live basic setup with persistence very good. Does not really work good with worlds slowest new USB emtec under 5mb rw bench speed pretty much expected and doesn't work worth NTFS formated multiboot also pretty much expected. Works great with YUMI Fat32 multi. One minor issue that is a bit annoying many of the Conky's that should default to right side are centered including Geeky-tower which is one I really like.
Re: MX-18 beta 1 feedback
Posted: Wed Dec 05, 2018 12:11 am
by asqwerth
zukahn1 wrote: Wed Dec 05, 2018 12:05 am... One minor issue that is a bit annoying many of the Conky's that should default to right side are centered including Geeky-tower which is one I really like.
Geeky-tower should be defaulting to the right side.
Did you install the iso on your laptop? And how big is the screen?
After installation, reboot, and if it still doesn't appear on the right, post back with your system info (MX-Tools>>Quick System Info) and the conky configuration (open Conky Manager, click on the Edit button (pencil icon) and copy the config text that appears in your text editor).
Re: MX-18 beta 1 feedback-now working perfectly
Posted: Wed Dec 05, 2018 3:06 am
by Paul..
entropyfoe wrote: Tue Dec 04, 2018 9:07 pm
I had the crash at idle again, so the boot code is needed.
I added manually to /etc/default/grub, the line rcu_nocbs=0-11
This completely stabilized my MX 17, so I am sure this will work again. [wish those kernel gurus would fix that]
I have a very similar new rig...(see sig) with the Asus X470 mother board and Ryzen 5 1400 (4 cores, 8 threads). In my case, I've stabilized the system by un-checking all options in "Power manager settings"...
...I did try the boot option rcu_nocbs (in my case, rcu_nocbs=0-7) but it doesn't seem to work on this particular rig. Go figure...I dunno why.
Like you, I'm hoping the kernel gods figure this one out. We should stay in touch and continue to share notes.
Code: Select all
System: Host: BigDaddy Kernel: 4.19.0-1-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3
Distro: MX-18b1_x64 Continuum December 3 2018
Machine: Type: Desktop Mobo: ASUSTeK model: PRIME X470-PRO v: Rev X.0x serial: <root required>
UEFI: American Megatrends v: 4011 date: 04/19/2018
CPU: Topology: Quad Core model: AMD Ryzen 5 1400 bits: 64 type: MT MCP L2 cache: 2048 KiB
Speed: 1375 MHz min/max: 1550/3200 MHz Core speeds (MHz): 1: 1375 2: 1375 3: 1375
4: 1375 5: 1367 6: 1566 7: 1977 8: 1748
Graphics: Device-1: NVIDIA GM107 [GeForce GTX 750 Ti] driver: nouveau v: kernel
Display: x11 server: X.Org 1.19.2 driver: nouveau unloaded: fbdev,modesetting,vesa
resolution: 1920x1080~60Hz
OpenGL: renderer: NV117 v: 4.3 Mesa 18.2.6
Audio: Device-1: NVIDIA driver: snd_hda_intel
Device-2: AMD driver: snd_hda_intel
Sound Server: ALSA v: k4.19.0-1-amd64
Network: Device-1: Intel I211 Gigabit Network driver: igb
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: 4c:ed:fb:72:e9:c5
Drives: Local Storage: total: 727.29 GiB used: 151.43 GiB (20.8%)
ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO 250GB size: 232.89 GiB
ID-2: /dev/sda vendor: Samsung model: SSD 860 EVO 500GB size: 465.76 GiB
ID-3: /dev/sdb type: USB vendor: SanDisk model: Ultra size: 28.64 GiB
Partition: ID-1: / size: 47.81 GiB used: 9.49 GiB (19.9%) fs: ext4 dev: /dev/nvme0n1p2
ID-2: swap-1 size: 15.62 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/nvme0n1p5
Sensors: System Temperatures: cpu: 31.5 C mobo: N/A gpu: nouveau temp: 33 C
Fan Speeds (RPM): cpu: 0 gpu: nouveau fan: 1080
Info: Processes: 266 Uptime: 10h 05m Memory: 15.66 GiB used: 3.25 GiB (20.7%) Shell: bash
inxi: 3.0.25
Re: MX-18 beta 1 feedback
Posted: Wed Dec 05, 2018 5:33 am
by Jerry3904
zukahn1 wrote: Wed Dec 05, 2018 12:05 am
Have tried this on several USB setups great distro works good on older Dell Latitude laptop with 2.0 USB live basic setup with persistence very good. Does not really work good with worlds slowest new USB emtec under 5mb rw bench speed pretty much expected and doesn't work worth NTFS formated multiboot also pretty much expected. Works great with YUMI Fat32 multi. One minor issue that is a bit annoying many of the Conky's that should default to right side are centered including Geeky-tower which is one I really like.
All the conkies are set to the center, will change once we have a default wallpaper. For now, just open Conky Manager, highlight the active conkies and click on the little great icon to change location. All laid out in the Wiki Help files.
https://mxlinux.org/wiki/help-files/help-conky-manager
https://mxlinux.org/wiki/help-files/help-mx-conky
Re: MX-18 beta 1 feedback
Posted: Wed Dec 05, 2018 5:38 am
by Fornhamfred
Yes I confirm that Teamviewer 12 installed and runs fine in "MX18_x64 Continuum March 14 2018"-upgraded from MX17.1 with having dev-repo enabled.
Code: Select all
System: Host: mx17 Kernel: 4.15.0-1-amd64 x86_64 bits: 64 compiler: gcc v: 6.3.0
Desktop: Xfce 4.12.3 Distro: MX-18_x64 Continuum March 14 2018
base: Debian GNU/Linux 9 (stretch)
Machine: Type: Desktop Mobo: ASUSTeK model: P8Z68-V LX v: Rev X.0x serial: <filter>
BIOS: American Megatrends v: 0703 date: 10/21/2011
CPU: Topology: Quad Core model: Intel Core i5-2500K bits: 64 type: MCP arch: Sandy Bridge
rev: 7 L2 cache: 6144 KiB
flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 27195
Speed: 1648 MHz min/max: 1600/5900 MHz Core speeds (MHz): 1: 1740 2: 1725 3: 1648
4: 1648
Graphics: Device-1: AMD Turks XT [Radeon HD 6670/7670] driver: radeon v: kernel bus ID: 01:00.0
Display: x11 server: X.Org 1.19.2 driver: ati,radeon unloaded: fbdev,modesetting,vesa
resolution: 1360x768~60Hz
OpenGL: renderer: AMD TURKS (DRM 2.50.0 / 4.15.0-1-amd64 LLVM 7.0.0)
v: 3.3 Mesa 18.2.6 direct render: Yes
Audio: Device-1: Intel 6 Series/C200 Series Family High Definition Audio
driver: snd_hda_intel v: kernel bus ID: 00:1b.0
Device-2: AMD Turks HDMI Audio [Radeon HD 6500/6600 / 6700M Series]
driver: snd_hda_intel v: kernel bus ID: 01:00.1
Sound Server: ALSA v: k4.15.0-1-amd64
Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169
v: 2.3LK-NAPI port: d000 bus ID: 07:00.0
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives: Local Storage: total: 2.04 TiB used: 16.05 GiB (0.8%)
ID-1: /dev/sda vendor: Seagate model: ST2000DL003-9VT166 size: 1.82 TiB
ID-2: /dev/sdb vendor: Kingston model: SA400S37240G size: 223.57 GiB
Partition: ID-1: / size: 20.06 GiB used: 6.59 GiB (32.8%) fs: ext4 dev: /dev/sdb7
ID-2: /home size: 29.67 GiB used: 2.37 GiB (8.0%) fs: ext4 dev: /dev/sdb8
Sensors: System Temperatures: cpu: 34.0 C mobo: N/A gpu: radeon temp: 36 C
Fan Speeds (RPM): cpu: 0
Repos: Active apt repos in: /etc/apt/sources.list.d/antix.list
1: deb http://nl.mxrepo.com/antix/stretch stretch main
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://ftp.uk.debian.org/debian/ stretch-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://ftp.uk.debian.org/debian/ stretch main contrib non-free
2: deb http://security.debian.org/ stretch/updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/devrepo.list
Re: MX-18 beta 1 feedback
Posted: Wed Dec 05, 2018 6:05 am
by mystic
Speaking about conky.
I have usually been able to drag it with Alt + left click but now it doesn't seem to work that often. Some of the conkies work but others don't such as geeky tower.
Re: MX-18 beta 1 feedback
Posted: Wed Dec 05, 2018 9:05 am
by danielson
Don't want to wear out this issue, but the only thing that happens (appears) after pressing the power button to get out of sleep mode, is the MX18 beta screen.
- - - - -
Now where can i configure the lock screen key...?
Need another cup of mojo.
Re: MX-18 beta 1 feedback
Posted: Wed Dec 05, 2018 9:37 am
by bumper
ok still no help, impossible to run some of my favorite programs, Cliqz browser, etc and a few more, so maybe in a newer version so switch back to my old hard drive. downloads of videos a big problem, watching videos many pauses, any browsers hang up, a few programs in MX are old versions and I can't upgrade them.
Re: MX-18 beta 1 feedback, Serban S
Posted: Wed Dec 05, 2018 9:38 am
by Serban
I upgraded, instead of installing from ISO.
Everything went smooth. I loved the terminal window that kept me in the loop!
I have many things to solve now, but generally speaking, nothing close to what is usually called "objection".
Everything works fine!
Thanks a lot to each and everyone in this team!
Now, I'm going to perform the Repo update, as pointed out in an earlier post, then I think I'll install the Apps I usually use. I have a script so it will go smooth, since I wrote it for apt (apt-get).
SO FAR:
- Lots of useful things on system administration side. Cool!
- The Installer, looks great!
- The upgrade, is very straightforward and IT WORKS!
- The RAM consumption is OK> 430 - 480 MB with Double Commander and Task Manager in Startup and somewhere around 1,5 GB with FireFox running some Pink Flod YouTubes.
- CPU, goes from 25% to some 45%.
- Sadly, Linux Mint 18.x (x = 0, 1, 2, 3) uses all available RAM for the same tasks!
Now, I am writing this post from MX Linux 18 Beta 1
(
External USB drive, 160 GB Hitachi on a Lenovo ThinkPad T400, 4 GB RAM DDR III, CPU Intel Core2Duo T9400@2,53 GHz, HDD 1 TB SATA)
Re: MX-18 beta 1 feedback
Posted: Wed Dec 05, 2018 10:07 am
by danielson
Probably not specific to 18 beta, but can't see entries when trying to edit them in Google Contacts (when using dark themes).
Must highlight typed info to see them.
Re: MX-18 beta 1 feedback
Posted: Wed Dec 05, 2018 10:23 am
by entropyfoe
Paul,
Yes our systems are very similar. You have the newer chip set and newer board the X470 .
With the Ryzen, an nvme for boot, lots of fast RAM, and an SSD for data these systems are very snappy.
There is really no computing task that really can stress this system, though I love running the MX snapshot and seeing CPU at 1100%.
The kernel bug has been a long journey. I tried the power options, but no luck, with the rcu_nocbs fix I was stable on MX 17 for over 147 days of uptime.
This link indicates that some of the newer BIOS may help. Some are claiming that a new BIOS power supply option (set to typical current) fixes it without the rcu_nocbs line.
https://community.amd.com/thread/225795
You could also try going from noveau to the nvidia driver, in early troubleshooting, that helped minimize some crashes.
Is your system absolutely stable with only the power options off?
The main thing is MX18 beta1 is now stable, my system remained up over night, where without the fix it would not even make it over night at idle. If it is still up (and I expect so) tonight when I get home, I will claim victory.
This MX18 viable for a long time, as the 4.19 kernel is a LTS kernel. So, people can run MX18 for years if needed.
Re: MX-18 beta 1 feedback
Posted: Wed Dec 05, 2018 12:23 pm
by zukahn1
asqwerth wrote: Wed Dec 05, 2018 12:11 am
zukahn1 wrote: Wed Dec 05, 2018 12:05 am... One minor issue that is a bit annoying many of the Conky's that should default to right side are centered including Geeky-tower which is one I really like.
Geeky-tower should be defaulting to the right side.
Did you install the iso on your laptop? And how big is the screen?
After installation, reboot, and if it still doesn't appear on the right, post back with your system info (MX-Tools>>Quick System Info) and the conky configuration (open Conky Manager, click on the Edit button (pencil icon) and copy the config text that appears in your text editor).
I'm running a Dell Latittude D630 Laptop with 14 inch using the ISO on a live USB with persistance. Tried it on two different USB one setup with rufus and just MX18 and one with a a Yumi multi and MX17 same thing on both the Geeky-tower defaults to the center and won't move tried most of the other conky's and they seem to work fine.
Code: Select all
System:
Host: mx1 Kernel: 4.19.0-1-amd64 x86_64 bits: 64 compiler: gcc v: 6.3.0
Desktop: Xfce 4.12.3 Distro: MX-18b1_x64 Continuum December 3 2018
base: Debian GNU/Linux 9 (stretch)
Machine:
Type: Portable System: Dell product: Latitude D630 v: N/A serial: <filter>
Mobo: Dell model: 0KU184 serial: <filter> BIOS: Dell v: A19
date: 06/04/2013
CPU:
Topology: Dual Core model: Intel Core2 Duo T7500 bits: 64 type: MCP
arch: Core Merom rev: B L2 cache: 4096 KiB
flags: lm nx pae sse sse2 sse3 ssse3 vmx bogomips: 8775
Speed: 798 MHz max: 800 MHz Core speeds (MHz): 1: 798 2: 798
Graphics:
Device-1: Intel Mobile GM965/GL960 Integrated Graphics driver: i915
v: kernel bus ID: 00:02.0
Display: x11 server: X.Org 1.19.2 driver: intel resolution: 1280x800~60Hz
OpenGL: renderer: Mesa DRI Intel 965GM v: 2.1 Mesa 18.2.6
direct render: Yes
Audio:
Device-1: Intel 82801H HD Audio driver: snd_hda_intel v: kernel
bus ID: 00:1b.0
Sound Server: ALSA v: k4.19.0-1-amd64
Network:
Device-1: Broadcom Limited NetXtreme BCM5755M Gigabit Ethernet PCI Express
driver: tg3 v: 3.137 port: 10c0 bus ID: 09:00.0
IF: eth0 state: down mac: <filter>
Device-2: Intel PRO/Wireless 3945ABG [Golan] Network driver: iwl3945
v: in-tree:s port: 10c0 bus ID: 0c:00.0
IF: wlan0 state: up mac: <filter>
Device-3: Dell Wireless 360 Bluetooth type: USB driver: btusb
bus ID: 1-2:2
Drives:
Local Storage: total: 80.08 GiB used: 800.0 MiB (1.0%)
ID-1: /dev/sda vendor: Seagate model: ST980813ASG size: 74.53 GiB
ID-2: /dev/sdb type: USB vendor: Verbatim model: STORE N GO size: 5.55 GiB
Partition:
ID-1: / size: 2.08 GiB used: 800.0 MiB (37.6%) fs: overlay dev: ERR-102
Sensors:
System Temperatures: cpu: 52.0 C mobo: N/A sodimm: 49.0 C
Fan Speeds (RPM): cpu: 0
Repos:
Active apt repos in: /etc/apt/sources.list.d/antix.list
1: deb http://iso.mxrepo.com/antix/stretch stretch main
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://ftp.us.debian.org/debian/ stretch-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://ftp.us.debian.org/debian/ stretch main contrib non-free
2: deb http://security.debian.org/ stretch/updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/google-chrome.list
1: deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://mxrepo.com/mx/repo/ stretch main non-free
No active apt repos in: /etc/apt/sources.list.d/various.list
Info:
Processes: 186 Uptime: 17m Memory: 2.92 GiB used: 869.4 MiB (29.0%)
Init: SysVinit runlevel: 5 Compilers: gcc: 6.3.0 Shell: bash v: 4.4.12
inxi: 3.0.25
Re: MX-18 beta 1 feedback
Posted: Wed Dec 05, 2018 12:45 pm
by Jerry3904
Follow the directions I posted after asqwerth's, there is
no problem at all moving it with Conky Manager. If you prefer doing it manually, open the script and change it according to this:
Code: Select all
# Text alignment, other possible values are commented
#alignment top_left
alignment top_right
#alignment bottom_left
#alignment bottom_right
Re: MX-18 beta 1 feedback
Posted: Wed Dec 05, 2018 1:29 pm
by Stevo
bumper wrote: Wed Dec 05, 2018 9:37 am
ok still no help , impossible to run some of my favorite programs , Cliqz browser, etc and a few more, so maybe in a newer version so switch back to my old hard drive.
Cliqz is built on Ubuntu, so should only be expected to be compatible with that. There's ways for the developers to make it more compatible, I believe, but it looks like the packagers aren't that interested in that. Maybe they'll make a flatpak or AppImage.
Re: MX-18 beta 1 feedback
Posted: Wed Dec 05, 2018 2:39 pm
by Paul..
entropyfoe wrote: Wed Dec 05, 2018 10:23 am
Paul,
Yes our systems are very similar. You have the newer chip set and newer board the X470 .
With the Ryzen, an nvme for boot, lots of fast RAM, and an SSD for data these systems are very snappy.
There is really no computing task that really can stress this system, though I love running the MX snapshot and seeing CPU at 1100%.
The kernel bug has been a long journey. I tried the power options, but no luck, with the rcu_nocbs fix I was stable on MX 17 for over 147 days of uptime.
This link indicates that some of the newer BIOS may help. Some are claiming that a new BIOS power supply option (set to typical current) fixes it without the rcu_nocbs line.
https://community.amd.com/thread/225795
You could also try going from noveau to the nvidia driver, in early troubleshooting, that helped minimize some crashes.
Is your system absolutely stable with only the power options off?
The main thing is MX18 beta1 is now stable, my system remained up over night, where without the fix it would not even make it over night at idle. If it is still up (and I expect so) tonight when I get home, I will claim victory.
This MX18 viable for a long time, as the 4.19 kernel is a LTS kernel. So, people can run MX18 for years if needed.
The story has changed...Turns out my new rig needed a new brain, that the instability was from the motherboard UEFI firmware!!!...I flashed the UEFI/BIOS with a new version and my instability went away. So the cause was not kernel/CPU-related as far as I can tell.
On the Asus Prime X470-Pro there is a feature to download and install directly over the net via the UEFI setup. It worked perfectly (I was very surprised) and now I can let the MX-18 Power manager handle the screen (tick the box, "Handle display power management") without crashing and use the Power button on the Whisker menu to manually "Suspend" and have it come back w/o crashing, too.
The biggest clue staring me in the face was erratic USB behavior. I was having mucho problems with USB2&3 compatibility...simple stuff like my favorite Goldtouch USB2 keyboard (I am a writer) disconnecting and Evoluent wireless mouse with USB2 RF transmitter becoming randomly sporadic, freezing and then flying all over the screen, then not being able to read certain known-to-be-reliable Sandisk USB3 flashdrives suddenly not found when plugged in, etc. That's what drove me to reflash the UEFI. EDIT: I re-flashed to the newest version
Don't know if you've tried re-flashing UEFI firmware but it really helped my machine's instability.
Re: MX-18 beta 1 feedback
Posted: Wed Dec 05, 2018 8:40 pm
by entropyfoe
Paul, I was hoping the 4.19 would no longer require the rcu_nocbs boot parameter.
But alas, MX 18 is stable now one day (without the boot parameter, one day experienced 2 crashes at idle).
Yes I have flashed the BIOS on this board at least 3 times in the early days seeking stability.
Now let me know if you can run stable without the rcu_nocbs grub line.
If the new BIOS fixes it, then we no longer need to mess with this on each install.
I might consider another flash then. My rule, dont't flash if everything works. This is a gray area, it works with some messing about.
Re: MX-18 beta 1 feedback
Posted: Wed Dec 05, 2018 11:23 pm
by freefreeno
Command section in whisker properties where you can remove the comands like logout and mugshots isnt working for some commands. Unchecking the box doesn't remove some commands like mugshot.
Re: MX-18 beta 1 feedback
Posted: Thu Dec 06, 2018 2:12 am
by KoO
I have updated to MX-18-b1 on both my main desktop & T430 Lappy
Both machines are running i3 & xfce. and sgfxi=415.18
This is from my desktop..
Code: Select all
System: Host: mx-17.1 Kernel: 4.15.0-1-amd64 x86_64 bits: 64 Desktop: i3 4.16
Distro: MX-18_x64 Continuum March 14 2018
Congratulations Lady's and Gentlemen Not one problem..
Re: MX-18 beta 1 feedback
Posted: Thu Dec 06, 2018 2:35 am
by asqwerth
I'm thinking we need more feedback from people actually trying the new Beta iso instead of just upgrading their MX17 install.
Because:
1) the new installer needs some testing. It has more encryption options now, plus the layout of the window for selecting device, root, swap and boot (this is new and optional) partitions has changed. Does it work?
2) people who upgrade from MX17 may not change to the new kernel on the Beta. But does that new kernel work?
Re: MX-18 beta 1 feedback
Posted: Thu Dec 06, 2018 3:36 am
by chrispop99
freefreeno wrote: Wed Dec 05, 2018 11:23 pm
Command section in whisker properties where you can remove the comands like logout and mugshots isnt working for some commands. Unchecking the box doesn't remove some commands like mugshot.
It works the same as on MX-17. You can turn all the functions on or off, but the 'Edit Profile' checkbox function may not be doing what you expect. It doesn't remove the 'Mugshot' icon, it toggles the ability to edit profile information by clicking that icon.
It's something that puzzled me when I first came across it!
Chris
Re: MX-18 beta 1 feedback
Posted: Thu Dec 06, 2018 4:18 am
by freefreeno
It works the same as on MX-17. You can turn all the functions on or off, but the 'Edit Profile' checkbox function may not be doing what you expect. It doesn't remove the 'Mugshot' icon, it toggles the ability to edit profile information by clicking that icon.
It's something that puzzled me when I first came across it
Well that works kinda weird but thanks for letting me know that it doesnt do what the rest of them do by default. Weird though. I do not like this little rinky dink volume control in panel. I like the ones that open the little menu not just a little tiny slider.
Re: MX-18 beta 1 feedback
Posted: Thu Dec 06, 2018 4:24 am
by asqwerth
freefreeno wrote: Thu Dec 06, 2018 4:18 am... I do not like this little rinky dink volume control in panel. I like the ones that open the little menu not just a little tiny slider.
There is a separate xfce pulseaudio applet for the panel that you can add to said panel. The fancy version of the applet used to be in Test Repo, but it may have since been moved to Stable Repo. Check Test Repo first.
Re: MX-18 beta 1 feedback
Posted: Thu Dec 06, 2018 5:03 am
by chrispop99
Today's update to MX Welcome has reverted to the MX 17 "Horizon" title.
Chris
Re: MX-18 beta 1 feedback
Posted: Thu Dec 06, 2018 6:18 am
by dolphin_oracle
chrispop99 wrote: Thu Dec 06, 2018 5:03 am
Today's update to MX Welcome has reverted to the MX 17 "Horizon" title.
Chris
Really? I thought I fixed that. The new version is in the dev repo. Or t least I thought so.
Re: MX-18 beta 1 feedback
Posted: Thu Dec 06, 2018 7:03 am
by chrispop99
dolphin_oracle wrote: Thu Dec 06, 2018 6:18 am
chrispop99 wrote: Thu Dec 06, 2018 5:03 am
Today's update to MX Welcome has reverted to the MX 17 "Horizon" title.
Chris
Really? I thought I fixed that. The new version is in the dev repo. Or t least I thought so.
You had, but updates done in the last few hours included MX Welcome, and it now shows the MX 17 title. To be sure, I just updated 3 other machines, and they all went from 18 to 17.
Chris
Re: MX-18 beta 1 feedback
Posted: Thu Dec 06, 2018 7:31 am
by dolphin_oracle
chrispop99 wrote: Thu Dec 06, 2018 7:03 am
dolphin_oracle wrote: Thu Dec 06, 2018 6:18 am
chrispop99 wrote: Thu Dec 06, 2018 5:03 am
Today's update to MX Welcome has reverted to the MX 17 "Horizon" title.
Chris
Really? I thought I fixed that. The new version is in the dev repo. Or t least I thought so.
You had, but updates done in the last few hours included MX Welcome, and it now shows the MX 17 title. To be sure, I just updated 3 other machines, and they all went from 18 to 17.
Chris
can you give me the version number on the mx-welcome? (apt-cache policy mx-welcome)
Re: MX-18 beta 1 feedback
Posted: Thu Dec 06, 2018 7:42 am
by Jerry3904
I just updated, welcome was not in today's pkgs. History shows last update 3 days ago (18.11). The problem is not only the word "Horizon," it's just the wrong one altogether (no FAQs, etc.).
Re: MX-18 beta 1 feedback
Posted: Thu Dec 06, 2018 7:50 am
by chrispop99
dolphin_oracle wrote: Thu Dec 06, 2018 7:31 am
chrispop99 wrote: Thu Dec 06, 2018 7:03 am
dolphin_oracle wrote: Thu Dec 06, 2018 6:18 am
Really? I thought I fixed that. The new version is in the dev repo. Or t least I thought so.
You had, but updates done in the last few hours included MX Welcome, and it now shows the MX 17 title. To be sure, I just updated 3 other machines, and they all went from 18 to 17.
Chris
can you give me the version number on the mx-welcome? (apt-cache policy mx-welcome)
On a machine that was updated this morning via MX-Updater, I double-checked it was updated by apt dist-upgrade; there was nothing to upgrade. The version number of mx-welcome is 18.11.
Chris
Re: MX-18 beta 1 feedback
Posted: Thu Dec 06, 2018 7:53 am
by rej
I have found a work-around for this and am posting in case any of it is helpful. This pertains only to installing on an external hard drive or partition on an internal hard drive and has most likely already been resolved...
Currently running the 18 beta1 on a T60p ThinkPad, T420 ThinkPad, and external USB 320gb Hard Drive. It seems to run flawlessly so far. Had a problem with Grub though -
Grub did not want to install to external USB HD. "Ok to install Grub bootloader at ?" - then failed. Just a question mark - no sda#. Same on a partition on internal HD. Able to boot on the internal drive because MX17.1 is the controlling grub. Could not boot from the ext USB HD - even after several tries at re-installing bootloader from MX17 USB flashdrive snapshot and original MX18 USB install media. [Hope all this is complete and makes sense]
Ran live USB install media:
Installed updates-then MX Tools-reinstall grub [to the ext HD that is missing grub]-no longer is there a question mark-tried loading grub to MBR [which I never select on Ext HD...] and then root [2 separate attempts]
-reboot each - same result:
black screen with:
GNU GRUB version2.02[tilde]beta3-5+deb9u1
Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists possible device or file completions.
grub>
=================
Have no idea what all the output means after tabbing:
"extract_entries_configfile extract..............."
====================
Made a snapshot on the fully configured installed partition - same ThinkPad T60p and installed on same external HD - no grub problem at all.
Installed T60p Snapshot on T420 ThinkPad partition. Went to MX17 partition with controlling Grub after install to configure. Have 4 partitions with antiX and 2 others with MX. MX18 partiton could not be found, until I viewed the "Removed items", and there it was.
Also, the default conky is somewhat scrambled.
Aside from Grub, I would not know it was beta. It is excellent, as usual.
Code: Select all
rj@mx18:~
$ inxi -Fz
System: Host: mx18 Kernel: 4.19.0-1-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3
Distro: MX-18b1_x64 Continuum December 3 2018
Machine: Type: Laptop System: LENOVO product: 8742AL9 v: ThinkPad T60p serial: <filter>
Mobo: LENOVO model: 8742AL9 serial: <filter> BIOS: LENOVO v: 7IET30WW (1.11 )
date: 07/13/2007
Battery: ID-1: BAT0 charge: 15.4 Wh condition: 15.7/56.2 Wh (28%)
CPU: Topology: Dual Core model: Intel Core2 T7400 bits: 64 type: MCP L2 cache: 4096 KiB
Speed: 998 MHz min/max: 1000/2167 MHz Core speeds (MHz): 1: 998 2: 998
Graphics: Device-1: AMD RV530/M66 GL [Mobility FireGL V5250] driver: radeon v: kernel
Display: x11 server: X.Org 1.19.2 driver: ati,radeon unloaded: fbdev,modesetting,vesa
resolution: 1680x1050~60Hz
OpenGL: renderer: ATI RV530 v: 2.1 Mesa 18.2.6
Audio: Device-1: Intel NM10/ICH7 Family High Definition Audio driver: snd_hda_intel
Sound Server: ALSA v: k4.19.0-1-amd64
Network: Device-1: Intel 82573L Gigabit Ethernet driver: e1000e
IF: eth0 state: down mac: <filter>
Device-2: Intel PRO/Wireless 3945ABG [Golan] Network driver: iwl3945
IF: wlan0 state: up mac: <filter>
Drives: Local Storage: total: 327.00 GiB used: 10.69 GiB (3.3%)
ID-1: /dev/sda vendor: Samsung model: HM321HI size: 298.09 GiB
ID-2: /dev/sdb type: USB vendor: PNY model: USB 2.0 FD size: 28.91 GiB
Partition: ID-1: / size: 28.71 GiB used: 7.07 GiB (24.6%) fs: ext4 dev: /dev/sda9
ID-2: swap-1 size: 7.81 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda5
Sensors: System Temperatures: cpu: 40.0 C mobo: 27.0 C
Fan Speeds (RPM): cpu: 2976
Info: Processes: 174 Uptime: 7m Memory: 2.93 GiB used: 429.6 MiB (14.3%) Shell: bash
inxi: 3.0.25
rj@mx18:~
$
====================================
Code: Select all
rj@mx18:~
$ inxi -Fz
System: Host: mx18 Kernel: 4.19.0-1-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3
Distro: MX-18b1_x64 Continuum December 3 2018
Machine: Type: Laptop System: LENOVO product: 42365MO v: ThinkPad T420 serial: <filter>
Mobo: LENOVO model: 42365MO serial: <filter> UEFI [Legacy]: LENOVO
v: 83ET79WW (1.49 ) date: 09/05/2016
Battery: ID-1: BAT0 charge: 27.6 Wh condition: 27.6/47.5 Wh (58%)
CPU: Topology: Dual Core model: Intel Core i5-2540M bits: 64 type: MT MCP
L2 cache: 3072 KiB
Speed: 797 MHz min/max: 800/3300 MHz Core speeds (MHz): 1: 797 2: 797 3: 800 4: 849
Graphics: Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics driver: i915
v: kernel
Display: x11 server: X.Org 1.19.2 driver: modesetting unloaded: fbdev,vesa
resolution: 1600x900~60Hz
OpenGL: renderer: Mesa DRI Intel Sandybridge Mobile v: 3.3 Mesa 18.2.6
Audio: Device-1: Intel 6 Series/C200 Series Family High Definition Audio
driver: snd_hda_intel
Sound Server: ALSA v: k4.19.0-1-amd64
Network: Device-1: Intel 82579LM Gigabit Network driver: e1000e
IF: eth0 state: down mac: <filter>
Device-2: Intel Centrino Advanced-N 6205 [Taylor Peak] driver: iwlwifi
IF: wlan0 state: up mac: <filter>
Drives: Local Storage: total: 698.64 GiB used: 5.39 GiB (0.8%)
ID-1: /dev/sda vendor: Seagate model: ST750LX003-1AC154 size: 698.64 GiB
Partition: ID-1: / size: 38.20 GiB used: 5.39 GiB (14.1%) fs: ext4 dev: /dev/sda12
Sensors: System Temperatures: cpu: 41.0 C mobo: N/A
Fan Speeds (RPM): cpu: 0
Info: Processes: 191 Uptime: 3h 35m Memory: 7.68 GiB used: 480.2 MiB (6.1%) Shell: bash
inxi: 3.0.25
rj@mx18:~
$
====================
[External 320gb USB hard drive on T60p:]
--------------------
Code: Select all
rj@mx18:~
$ inxi -Fz
System: Host: mx18 Kernel: 4.19.0-1-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3
Distro: MX-18b1_x64 Continuum December 3 2018
Machine: Type: Laptop System: LENOVO product: 8742AL9 v: ThinkPad T60p serial: <filter>
Mobo: LENOVO model: 8742AL9 serial: <filter> BIOS: LENOVO v: 7IET30WW (1.11 )
date: 07/13/2007
Battery: ID-1: BAT0 charge: 15.4 Wh condition: 15.7/56.2 Wh (28%)
CPU: Topology: Dual Core model: Intel Core2 T7400 bits: 64 type: MCP L2 cache: 4096 KiB
Speed: 998 MHz min/max: 1000/2167 MHz Core speeds (MHz): 1: 998 2: 998
Graphics: Device-1: AMD RV530/M66 GL [Mobility FireGL V5250] driver: radeon v: kernel
Display: x11 server: X.Org 1.19.2 driver: ati,radeon unloaded: fbdev,modesetting,vesa
resolution: 1680x1050~60Hz
OpenGL: renderer: ATI RV530 v: 2.1 Mesa 18.2.6
Audio: Device-1: Intel NM10/ICH7 Family High Definition Audio driver: snd_hda_intel
Sound Server: ALSA v: k4.19.0-1-amd64
Network: Device-1: Intel 82573L Gigabit Ethernet driver: e1000e
IF: eth0 state: down mac: <filter>
Device-2: Intel PRO/Wireless 3945ABG [Golan] Network driver: iwl3945
IF: wlan0 state: up mac: <filter>
Drives: Local Storage: total: 596.18 GiB used: 5.24 GiB (0.9%)
ID-1: /dev/sda vendor: Samsung model: HM321HI size: 298.09 GiB
ID-2: /dev/sdb type: USB model: CLOVER CN-M320MBB E361M8E320G6N234 size: 298.09 GiB
Partition: ID-1: / size: 280.80 GiB used: 5.24 GiB (1.9%) fs: ext4 dev: /dev/sdb1
ID-2: swap-1 size: 11.80 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sdb2
Sensors: System Temperatures: cpu: 38.0 C mobo: 22.0 C
Fan Speeds (RPM): cpu: 0
Info: Processes: 180 Uptime: 1m Memory: 2.93 GiB used: 409.7 MiB (13.6%) Shell: bash
inxi: 3.0.25
rj@mx18:~
$
Re: MX-18 beta 1 feedback
Posted: Thu Dec 06, 2018 7:56 am
by Jerry3904
<corrected the use of the code tag>
Re: MX-18 beta 1 feedback
Posted: Thu Dec 06, 2018 8:12 am
by entropyfoe
rej
We saw the same thing when trying to install grub, see my first comments in this thread. (post 80) Jerry spotted that as well.
Grub did not want to install to external USB HD. "Ok to install Grub bootloader at ?" - then failed. Just a question mark - no sda#. Same on a partition on internal HD
Adrian had a quick fix for that. From the live session, upgrade the installer with synaptic. Then do the install. In my case, it found my 4th partition on the nvme drive and installed. See post 90,
viewtopic.php?p=470112#p470112
Re: MX-18 beta 1 feedback
Posted: Thu Dec 06, 2018 8:42 am
by chrispop99
(MX Welcome issue)
I've just booted live, invoked MX Updater, and one of the updates is for MX Welcome. The version installed, and the version to be installed, are the same - 18.11.
I'm thinking that might be a clue to the problem?
Screenshot.png
Chris
Re: MX-18 beta 1 feedback
Posted: Thu Dec 06, 2018 9:11 am
by dolphin_oracle
chrispop99 wrote: Thu Dec 06, 2018 8:42 am
(MX Welcome issue)
I've just booted live, invoked MX Updater, and one of the updates is for MX Welcome. The version installed, and the version to be installed, are the same - 18.11.
I'm thinking that might be a clue to the problem?
Screenshot.png
Chris
yes that helps. the new version is in the dev repo, which is not enabled by default on the beta.
I just checked the repo lists, and unless I packaged the same one twice (which ispossible), the mx-welcome in the dev repo should be 18.12.05 and have the MX-18 text in it.
Re: MX-18 beta 1 feedback
Posted: Thu Dec 06, 2018 9:17 am
by Paul..
Yeah, I have the dev repo enabled...and it mx-welcome is
Code: Select all
mx-welcome:
Installed: 18.12.05
Candidate: 18.12.05
Version table:
*** 18.12.05 500
500 http://mxrepo.com/mx/testrepo mx18/dev amd64 Packages
100 /var/lib/dpkg/status
18.11 500
500 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo stretch/main amd64 Packages
Re: MX-18 beta 1 feedback
Posted: Thu Dec 06, 2018 10:11 am
by male
asqwerth wrote:
I'm thinking we need more feedback from people actually trying the new Beta iso instead of just upgrading their MX17 install.
Because:
1) the new installer needs some testing. It has more encryption options now, plus the layout of the window for selecting device, root, swap and boot (this is new and optional) partitions has changed. Does it work?
Due to space problems I have the Beta1 on a virtual fat plate with QEMU to install
The installation program did an excellent job.
The task was:
-on the virtual disk of 30GB to perform the installation on sda6.
-to replace the existing installation with bunsenlabs
-Integrate the existing swap
-to accept my deselection of the preselected "designations
-Grub in the MBR of sda and to integrate two more Distris with os-prober and to adopt the changed resolution of the Live on 1360x768 in the new installation.
Duration approx. 15-20 minutes
result
Re: MX-18 beta 1 feedback
Posted: Thu Dec 06, 2018 10:16 am
by richb
Installed from iso 64 bit to ssd. In MX-Repo Manager and MX-Packages Installer clicking about and then the link to
http://mxlinux.org, results in
Failed to execute default Web Browser.
Others, eg MX Select Sound does open the Community site in the default browser. I have not checked all of them.
Re: MX-18 beta 1 feedback
Posted: Thu Dec 06, 2018 10:45 am
by johnf1971
Hello. I'll confess I'm a "noob" here so apologies if what I'm about to say seems either simplistic or if I cause offence in any way (not intended, I assure you). I've run MX17 and have tested MX18-beta on a Dell XPS 13" 9360 with a 4K screen. I've always had to reduce the resolution to 1920x1080 in order to make things readable. However, in other distributions with an xfce desktop environment (e.g. Mint, Manjaro, Antergos) there have been options to scale down to 2560x1440 or 2048x1152. These do not appear in MX. Would it be possible to add them? I realise the difference isn't vast and that it won't be relevant to anyone else other than those running Hidpi screens but it would be greatly appreciated. So, more of a request rather than a bug.
Re: MX-18 beta 1 feedback
Posted: Thu Dec 06, 2018 10:53 am
by richb
johnf1971 wrote: Thu Dec 06, 2018 10:45 am
Hello. I'll confess I'm a "noob" here so apologies if what I'm about to say seems either simplistic or if I cause offence in any way (not intended, I assure you). I've run MX17 and have tested MX18-beta on a Dell XPS 13" 9360 with a 4K screen. I've always had to reduce the resolution to 1920x1080 in order to make things readable. However, in other distributions with an xfce desktop environment (e.g. Mint, Manjaro, Antergos) there have been options to scale down to 2560x1440 or 2048x1152. These do not appear in MX. Would it be possible to add them? I realise the difference isn't vast and that it won't be relevant to anyone else other than those running Hidpi screens but it would be greatly appreciated. So, more of a request rather than a bug.
Not what you are asking for, but I have a 1920x 1080 max resolution 21 inch monitor. I increase the dpi in the System Settings>Fonts dialogue to between 140 and 150 to be able to comfortably read the text. The other option is to increase the font size.
Re: MX-18 beta 1 feedback
Posted: Thu Dec 06, 2018 11:29 am
by freefreeno
Only way to stop video tearing with the modesetting driver is to disable all compositor or you will have really bad horizontal rippling when scrolling pages in any browser. I have intel HD 620. I really hope this can worked out. I have not installed anyhting extra on MX-18b1. If you enable synchonize drawing to vertical blank with default compositor you will get corner to corner tearing.
Re: MX-18 beta 1 feedback
Posted: Thu Dec 06, 2018 11:39 am
by chrispop99
johnf1971 wrote: Thu Dec 06, 2018 10:45 am
Hello. I'll confess I'm a "noob" here so apologies if what I'm about to say seems either simplistic or if I cause offence in any way (not intended, I assure you). I've run MX17 and have tested MX18-beta on a Dell XPS 13" 9360 with a 4K screen. I've always had to reduce the resolution to 1920x1080 in order to make things readable. However, in other distributions with an xfce desktop environment (e.g. Mint, Manjaro, Antergos) there have been options to scale down to 2560x1440 or 2048x1152. These do not appear in MX. Would it be possible to add them? I realise the difference isn't vast and that it won't be relevant to anyone else other than those running Hidpi screens but it would be greatly appreciated. So, more of a request rather than a bug.
Where in Mint Xfce is the setting for scaling? As far as I can see, it only has the custom DPI setting for fonts; that's exactly the same as MX.
Mint
Cinnamon has a setting where you can scale by x2, which is better than nothing, but I think the only Linux DE that does 'proper' scaling is KDE.
One of the rare places where Windows actually does things better, I'm afraid.
Chris
Re: MX-18 beta 1 feedback
Posted: Thu Dec 06, 2018 11:44 am
by rasat
I took a look at your Dell model (XPS 13" 9360), the display seems to be 13.3" FHD 1920 x 1080 AG Non-touch InfinityEdge display, or you have a different card?
https://www.dell.com/en-us/shop/dell-la ... fncwt5128s
Re: MX-18 beta 1 feedback
Posted: Thu Dec 06, 2018 11:50 am
by richb
chrispop99 wrote: Thu Dec 06, 2018 11:39 am
johnf1971 wrote: Thu Dec 06, 2018 10:45 am
Hello. I'll confess I'm a "noob" here so apologies if what I'm about to say seems either simplistic or if I cause offence in any way (not intended, I assure you). I've run MX17 and have tested MX18-beta on a Dell XPS 13" 9360 with a 4K screen. I've always had to reduce the resolution to 1920x1080 in order to make things readable. However, in other distributions with an xfce desktop environment (e.g. Mint, Manjaro, Antergos) there have been options to scale down to 2560x1440 or 2048x1152. These do not appear in MX. Would it be possible to add them? I realise the difference isn't vast and that it won't be relevant to anyone else other than those running Hidpi screens but it would be greatly appreciated. So, more of a request rather than a bug.
Where in Mint Xfce is the setting for scaling? As far as I can see, it only has the custom DPI setting for fonts; that's exactly the same as MX.
Mint
Cinnamon has a setting where you can scale by x2, which is better than nothing, but I think the only Linux DE that does 'proper' scaling is KDE.
One of the rare places where Windows actually does things better, I'm afraid.
Chris
The xrandr command does scale. But I am not sure how executing it would look on his monitor.
Code: Select all
xrandr --output VGA-1 --scale 0.9x0.9
The 0.9x0.9 would scale down. Of course those numbers could be changed to other parameters.
Re: MX-18 beta 1 feedback
Posted: Thu Dec 06, 2018 11:53 am
by chrispop99
The XPS comes with a choice of 2 display options - 1920x1080 non-touch, or QHD 3200x1800 touch-enabled.
The QHD (which I have) is fantastic, but somewhat problematic with Xfce.
Chris
Re: MX-18 beta 1 feedback
Posted: Thu Dec 06, 2018 12:40 pm
by paulfsams
I installed the MX-18 alpha release just before the B1 Release. It is working well. I have been using just Debian Stretch with XFCE4. I was using the MX community repo for some packages with strect. I decided to make the jump to MX-Linux. I think I'm here to stay. So far, I have stayed with the default repos, and not using the test repo, or the Test-dv repo. I did go back to the Debian Stretch Kernel, the only reason for that is my mouse/touchpad is working better, I could not yet get it adjusted to the MX-kernel. I'm am hoping when MX-18 goes final, I can update in place. I think this will be my go to distro. You folks have done a great job. A number of years ago, Mepis Linux opened the door to the linux world for me. I think the version I had was based on Debian Sarge. I hope I have posted in the proper place.
Thank you.
CPU: Dual Core Intel Core i5-7200U (-MT MCP-)
speed/min/max: 621/400/3100 MHz Kernel: 4.9.0-3-amd64 x86_64 Up: 1h 11m
Mem: 1444.5/7870.8 MiB (18.4%) Storage: 465.76 GiB (28.2% used) Procs: 239
Shell: bash 4.4.12 inxi: 3.0.25
Re: MX-18 beta 1 feedback
Posted: Thu Dec 06, 2018 2:26 pm
by rej
Adrian had a quick fix for that. From the live session, upgrade the installer with synaptic. Then do the install. In my case, it found my 4th partition on the nvme drive and installed. See post 90, viewtopic.php?p=470112#p470112
This seems to go to a "404" page. Is there another access to it?
Re: MX-18 beta 1 feedback
Posted: Thu Dec 06, 2018 2:57 pm
by Adrian
I installed the MX-18 alpha release just before the B1 Release
I'm curious where you found it, Alpha is supposed to be "internal testing" and we didn't publish a link to it...
Re: MX-18 beta 1 feedback
Posted: Thu Dec 06, 2018 3:30 pm
by entropyfoe
rej
Just scroll backwards in this thread to post 80 where I reported the problem.
Then in posts 90 and 94 Adrian proposes the fix which he uploaded.
In the live session, use synaptic to upgrade the installer.
Then install as normal, that worked and the fix will surely be in the next beta.
Re: MX-18 beta 1 feedback
Posted: Thu Dec 06, 2018 3:53 pm
by paulfsams
If I remember correctly, I think it was on sourceforge, the iso was listed MX-18a1_x64.iso. I see that "testing folder" is now listing MX-18B1_x64.1so. I was looking for the Novenber iso of MX-17. I tried the alpha on usb, then decided to install it, and then go back to the November iso of MX-17.1. It is working so well, I haven't bothered. I am not using the test repositories in the sources.list, only the debian repos, and of course, the MX and I believe the antix repo. It's been rock solid so far. Have there been any changes to the sources list. I have remained with the stable repos, not testing.
Re: MX-18 beta 1 feedback
Posted: Thu Dec 06, 2018 3:55 pm
by Stevo
chrispop99 wrote: Thu Dec 06, 2018 11:39 am
johnf1971 wrote: Thu Dec 06, 2018 10:45 am
Hello. I'll confess I'm a "noob" here so apologies if what I'm about to say seems either simplistic or if I cause offence in any way (not intended, I assure you). I've run MX17 and have tested MX18-beta on a Dell XPS 13" 9360 with a 4K screen. I've always had to reduce the resolution to 1920x1080 in order to make things readable. However, in other distributions with an xfce desktop environment (e.g. Mint, Manjaro, Antergos) there have been options to scale down to 2560x1440 or 2048x1152. These do not appear in MX. Would it be possible to add them? I realise the difference isn't vast and that it won't be relevant to anyone else other than those running Hidpi screens but it would be greatly appreciated. So, more of a request rather than a bug.
Where in Mint Xfce is the setting for scaling? As far as I can see, it only has the custom DPI setting for fonts; that's exactly the same as MX.
Mint
Cinnamon has a setting where you can scale by x2, which is better than nothing, but I think the only Linux DE that does 'proper' scaling is KDE.
One of the rare places where Windows actually does things better, I'm afraid.
Chris
Didn't fehlix have that xrandr command to scale everything up, not just fonts? Edit: Oh, richb posted it, but for my laptop the output is eDP1, not VGA-1. Use "xrandr -q" to see what output your laptop is using.
Re: MX-18 beta 1 feedback
Posted: Thu Dec 06, 2018 3:59 pm
by richb
Stevo wrote: Thu Dec 06, 2018 3:55 pm
chrispop99 wrote: Thu Dec 06, 2018 11:39 am
johnf1971 wrote: Thu Dec 06, 2018 10:45 am
Hello. I'll confess I'm a "noob" here so apologies if what I'm about to say seems either simplistic or if I cause offence in any way (not intended, I assure you). I've run MX17 and have tested MX18-beta on a Dell XPS 13" 9360 with a 4K screen. I've always had to reduce the resolution to 1920x1080 in order to make things readable. However, in other distributions with an xfce desktop environment (e.g. Mint, Manjaro, Antergos) there have been options to scale down to 2560x1440 or 2048x1152. These do not appear in MX. Would it be possible to add them? I realise the difference isn't vast and that it won't be relevant to anyone else other than those running Hidpi screens but it would be greatly appreciated. So, more of a request rather than a bug.
Where in Mint Xfce is the setting for scaling? As far as I can see, it only has the custom DPI setting for fonts; that's exactly the same as MX.
Mint
Cinnamon has a setting where you can scale by x2, which is better than nothing, but I think the only Linux DE that does 'proper' scaling is KDE.
One of the rare places where Windows actually does things better, I'm afraid.
Chris
Didn't fehlix have that xrandr command to scale everything up, not just fonts?
Yes, that is what it does.
Re: MX-18 beta 1 feedback
Posted: Thu Dec 06, 2018 4:02 pm
by Paul..
entropyfoe wrote: Wed Dec 05, 2018 8:40 pm
Paul, I was hoping the 4.19 would no longer require the rcu_nocbs boot parameter.
But alas, MX 18 is stable now one day (without the boot parameter, one day experienced 2 crashes at idle).
Yes I have flashed the BIOS on this board at least 3 times in the early days seeking stability.
Now let me know if you can run stable without the rcu_nocbs grub line.
If the new BIOS fixes it, then we no longer need to mess with this on each install.
I might consider another flash then. My rule, dont't flash if everything works. This is a gray area, it works with some messing about.
My machine finally succumbed...I turned on various Power manager settings such as "System power saving->System sleep mode=Suspend, When inactive 30 minutes." Crashed somewhere after 30 min.
Have now added rcu_nocbs=0-7 to GRUB_CMDLINE_LINUX_DEFAULT="BOOT_IMAGE=/antiX/vmlinuz quiet
rec_nocbs=0-7"
Re: MX-18 beta 1 feedback
Posted: Thu Dec 06, 2018 4:50 pm
by entropyfoe
Paul, similar here...My MX18 also was crashed out to the log-in screen this morning. I have the rcu line added in grub, and I think the power settings are off, though I must re-check this tonight. So it made it a day and a half.
I don't know if it is the new kernel, but my MX17 and 17.1 with 4.15 kernel are unconditionally stable on the same machine. (uptime as high as 147 days).
Did you try adding the nvidia driver?
Re: MX-18 beta 1 feedback
Posted: Thu Dec 06, 2018 5:41 pm
by Paul..
entropyfoe wrote: Thu Dec 06, 2018 4:50 pm
Paul, similar here...My MX18 also was crashed out to the log-in screen this morning. I have the rcu line added in grub, and I think the power settings are off, though I must re-check this tonight. So it made it a day and a half.
I don't know if it is the new kernel, but my MX17 and 17.1 with 4.15 kernel are unconditionally stable on the same machine. (uptime as high as 147 days).
Did you try adding the nvidia driver?
Okay...didn't realize the 4.15 kernel was unconditionally stable for you...I will try that tonight...I assume with rcu line in grub, right?
I'm certainly not wedded to 4.19.0-1-amd64 for any reason. EDIT: not using nVidia driver until I get a stable kernel
Re: MX-18 beta 1 feedback
Posted: Thu Dec 06, 2018 6:06 pm
by Gerson
I had turned off the Conky toogle and today I replaced it by choosing the MX-LSD theme and I can see it on the activated desktop but as soon as I click on the desktop it disappears.
Everything else works perfect in the MX 18 beta
Re: MX-18 beta 1 feedback
Posted: Thu Dec 06, 2018 6:11 pm
by entropyfoe
Paul,
I am using the antiX kernel...from an earlier post. That 4.15.5-antix is needed because it has some other parameters enabled that make the rcu-nocbs work. It should be available from the MXPI, though I have not looked lately.
Rebooted, all is good with the 4.15.5-antix.1. (still stable with the rcu_nocbs=0-11 boot parameter. )
In my early testing last year, adding the nvidia was also helpful in preventing some of the crashes. (though that depends probably on your vid card)
Re: MX-18 beta 1 feedback
Posted: Thu Dec 06, 2018 7:19 pm
by caprea
@entropyfoe, @paul
I'm still following the bug-reports with the ryzens with interest.I just can't stay calm.
The rcu_nocbs=1-11 parameter does only work on kernels which have the rcu_nocbs-flag set to yes.
This is the case for the antix-kernels but not the mx-kernels.
Code: Select all
$ sudo cat /boot/config-4.19.4-antix.1-amd64-smp | grep CONFIG_RCU_NOCB_CPU
[sudo] Passwort für helga:
CONFIG_RCU_NOCB_CPU=y
But I cant believe this is still not solved.It seems a bios-update should fix it in most cases.
Paul, following the bug-reports you have to set "Power Supply Idle Control" to "Typical Current Idle" Is this really not offered by the newest bios flash?
It's not your motherboard and a german thread, but a picture of an Asus-board-uefi.Power Supply Idle Control is there.
https://www.hardwareluxx.de/community/f ... st26232426
Re: MX-18 beta 1 feedback
Posted: Thu Dec 06, 2018 7:29 pm
by rej
Just scroll backwards in this thread to post 80 where I reported the problem.
Then in posts 90 and 94 Adrian proposes the fix which he uploaded.
In the live session, use synaptic to upgrade the installer.
Then install as normal, that worked and the fix will surely be in the next beta.
entropyfoe-
Thanks - will try this.
Re: MX-18 beta 1 feedback
Posted: Thu Dec 06, 2018 8:48 pm
by Paul..
caprea wrote: Thu Dec 06, 2018 7:19 pm
@entropyfoe, @paul
I'm still following the bug-reports with the ryzens with interest.I just can't stay calm.
The rcu_nocbs=1-11 parameter does only work on kernels which have the rcu_nocbs-flag set to yes.
This is the case for the antix-kernels but not the mx-kernels.
Code: Select all
$ sudo cat /boot/config-4.19.4-antix.1-amd64-smp | grep CONFIG_RCU_NOCB_CPU
[sudo] Passwort für helga:
CONFIG_RCU_NOCB_CPU=y
But I cant believe this is still not solved.It seems a bios-update should fix it in most cases.
Paul, following the bug-reports you have to set "Power Supply Idle Control" to "Typical Current Idle" Is this really not offered by the newest bios flash?
It's not your motherboard and a german thread, but a picture of an Asus-board-uefi.Power Supply Idle Control is there.
https://www.hardwareluxx.de/community/f ... st26232426
Thanks, caprea. Yes, my UEFI update screens are the same as shown on the german thread...I'll try that "Typical Current Idle" setting. I'm using the 4.15.5-antix.1-amd64-smp and I checked CONFIG_RCU_NOCB_CPU=y
Re: MX-18 beta 1 feedback
Posted: Thu Dec 06, 2018 9:22 pm
by paulfsams
I earlier posted that I had installed from an Alpha iso (MX-18a1_x64.iso). I think I saw the image on sourceforge, it was over the weekend I think. I had read on the forum, something about using the latest installer, I had encountered trouble installing grub on updated iso(s). On the Alpha, I again updated Mx-Installer. Since everything was working fine, I stayed with this version, and simply applied all of the available updates. I enabled the test-dev repo and now using the 4.19 Kernel. The twitchy mouse I had with the original install is gone. The mouse is working fine. I don't know if this information is helpful, I hope so.
Paul Sams
Code: Select all
System:
Host: acer Kernel: 4.19.0-1-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3
Distro: MX-18a1_x64 Continuum November 26 2018
Machine:
Type: Laptop System: Acer product: Aspire A515-51 v: V1.05
serial: <root required>
Mobo: KBL model: Charmander_KL v: V1.05 serial: <root required>
UEFI: Insyde v: 1.05 date: 05/17/2017
Battery:
ID-1: BAT1 charge: 49.7 Wh condition: 49.7/48.9 Wh (102%)
CPU:
Topology: Dual Core model: Intel Core i5-7200U bits: 64 type: MT MCP
L2 cache: 3072 KiB
Speed: 1000 MHz min/max: 400/3100 MHz Core speeds (MHz): 1: 1000 2: 1000
3: 1000 4: 1002
Graphics:
Device-1: Intel driver: i915 v: kernel
Display: x11 server: X.Org 1.19.2 driver: modesetting unloaded: fbdev,vesa
resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa DRI Intel HD Graphics 620 (Kaby Lake GT2)
v: 4.5 Mesa 18.2.6
Audio:
Device-1: Intel driver: snd_hda_intel
Sound Server: ALSA v: k4.19.0-1-amd64
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
driver: r8169
IF: eth0 state: down mac: fc:45:96:ec:23:8a
Device-2: Intel driver: iwlwifi
IF: wlan0 state: up mac: 10:f0:05:c3:7e:8b
IF-ID-1: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A
Drives:
Local Storage: total: 465.76 GiB used: 131.87 GiB (28.3%)
ID-1: /dev/sda vendor: Samsung model: SSD 850 EVO 500GB size: 465.76 GiB
Partition:
ID-1: / size: 13.69 GiB used: 7.22 GiB (52.7%) fs: ext4 dev: /dev/sda2
ID-2: /home size: 436.28 GiB used: 124.65 GiB (28.6%) fs: ext4
dev: /dev/sda4
ID-3: swap-1 size: 7.45 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda3
Sensors:
System Temperatures: cpu: 51.0 C mobo: N/A
Fan Speeds (RPM): N/A
Info:
Processes: 200 Uptime: 1m Memory: 7.68 GiB used: 752.6 MiB (9.6%)
Shell: bash inxi: 3.0.25
[/code]
Re: MX-18 beta 1 feedback
Posted: Thu Dec 06, 2018 9:28 pm
by richb
Please enclose listings in code tags. Highlight the text "[code}text[/code}" and click on </> at the top of the post.
Re: MX-18 beta 1 feedback
Posted: Thu Dec 06, 2018 9:34 pm
by caprea
Paul.. wrote: Thu Dec 06, 2018 8:48 pm Code: Select all
I'm using the 4.15.5-antix.1-amd64-smp and I checked CONFIG_RCU_NOCB_CPU=y
If the Typical Current Idle works the way its supposed to do, a rcu_nocbs-parameter should not be necessary.
Re: MX-18 beta 1 feedback
Posted: Thu Dec 06, 2018 9:37 pm
by paulfsams
@richb Thank you richb. I know just enough to be dangerous.
Re: MX-18 beta 1 feedback
Posted: Thu Dec 06, 2018 9:41 pm
by richb
paulfsams wrote: Thu Dec 06, 2018 9:37 pm
@richb Thank you richb. I know just enough to be dangerous.
Don't worry I am in the same boat.
MX18 Beta1 MXPI
Posted: Thu Dec 06, 2018 10:44 pm
by entropyfoe
I am trying to install the 4.19.4-antix.1-amd64-smp kernel with the MX Package installer.
This may be useful as it was the 4.15 antix kernel that was stable. I think as caprea wrote, the antix kernels have another rcu parameter set so the rcu_nocbs=0-11 fix for Ryzen crashing. There may also be some new BIOS fixes that Paul is testing that may make the parameter un-necessary. Though reading on AMD boards, some report that it is still necessary. I think it is way too complex, and may depend on the motherboard, the BIOS, the kernel, and on maybe even the power supply !
But it hangs up with this message
Code: Select all
Hit:1 http://mxrepo.com/mx/testrepo mx18 InRelease
Hit:2 http://mxrepo.com/mx/repo stretch InRelease
Get:3 http://ftp.us.debian.org/debian stretch-updates InRelease [91.0 kB]
Ign:4 http://ftp.us.debian.org/debian stretch InRelease
Hit:5 http://ftp.us.debian.org/debian stretch Release
Hit:7 http://security.debian.org stretch/updates InRelease
Err:8 http://iso.mxrepo.com/antix/stretch stretch InRelease
Could not connect to iso.mxrepo.com:80 (168.235.87.212), connection timed out [IP: 168.235.87.212 80]
Fetched 91.0 kB in 4min 0s (378 B/s)
Reading package lists...
W: Failed to fetch http://iso.mxrepo.com/antix/stretch/dists/stretch/InRelease Could not connect to iso.mxrepo.com:80 (168.235.87.212), connection timed out [IP: 168.235.87.212 80]
W: Some index files failed to download. They have been ignored, or old ones used instead.
Reading package lists...
Building dependency tree...
Reading state information...
The following packages were automatically installed and are no longer required:
ecryptfs-utils libecryptfs1 libtspi1
Use 'apt autoremove' to remove them.
The following NEW packages will be installed:
linux-headers-4.19.4-antix.1-amd64-smp linux-image-4.19.4-antix.1-amd64-smp
:
Re: MX-18 beta 1 feedback
Posted: Thu Dec 06, 2018 11:57 pm
by freefreeno
Nomacs image viewer stopped following system theme in my system sometime between yesterday and today. I'm Mx18b1
Re: MX-18 beta 1 feedback
Posted: Fri Dec 07, 2018 2:10 am
by skidoo
The MX Welcome window cannot be minimized. Okay, but... after closing it, a brand new user would need to hunt for it.
If a desktop icon for it isn't amenable, please at least consider listing it among the WhiskerMenu "favorites".
Quick access to MX User Manual is a standout feature. IIRC, what tripped me up while wearing my "noob user" tester hat:
When MXUM is launched from the welcome dialog, the welcome dialog autohides (and no taskbar item for it).
Please consider using nohup or disown in the Welcome--}MXUM launchstring, as well as for a select few other launchers presented within the Welcome dialog.
_________________
The panel icon contains a paperclip icon. No mouseover "hint" is provided for that item (suggest adding hint text).
Left click on paperclip icon does nothing. Upon right click, we discover it is the "clipit" clipboard manager utility.
While attempting to check whether the pre-assigned clipit "Hot Key" keybinds conflict with the predefined firefox shortcut keybinds, I discovered a clipit bug.
-=-
When the clipit preferences window is open (but not necessarily focused), pressing Ctrl+Alt+h causes clipit to hang // becomes unresponsive & must be killed.
Launched from commandline, we can note the details of the "gtk:Critical" error. I reckon this is something that must be fixed by the upstream maintainer.
-=-
Separately, upon entering a fresh session, I noted that htop indicates THREE clipit processes are running.
After "killall clipit" and launching from commandline, yep, three clipit processes (hmm, or are they just multiple "threads" of one precess?)
__________________
noticed: Volume Label of the LiveUSB is "antiXlive". Maybe you'll want to replace that with "MXlive"?
Re: MX-18 beta 1 feedback
Posted: Fri Dec 07, 2018 4:15 am
by chrispop99
skidoo wrote: Fri Dec 07, 2018 2:10 am
The panel icon contains a paperclip icon. No mouseover "hint" is provided for that item (suggest adding hint text).
Left click on paperclip icon does nothing. Upon right click, we discover it is the "clipit" clipboard manager utility.
While attempting to check whether the pre-assigned clipit "Hot Key" keybinds conflict with the predefined firefox shortcut keybinds, I discovered a clipit bug.
-=-
When the clipit preferences window is open (but not necessarily focused), pressing Ctrl+Alt+h causes clipit to hang // becomes unresponsive & must be killed.
Launched from commandline, we can note the details of the "gtk:Critical" error. I reckon this is something that must be fixed by the upstream maintainer.
(Checked on 2xMX-18 installs.)
Both L-click and R-click do exactly the same thing here - open the ClipIt dialogue. That's not new behaviour; ClipIt has always been like that.
With ClipIt Preferences open, Ctrl-Alt-h just flashes the currently open tab. It performs normally afterwards, with no need to kill it.
I agree a tool-tip would be a useful addition.
Chris
Re: MX-18 beta 1 feedback
Posted: Fri Dec 07, 2018 4:21 am
by chrispop99
skidoo wrote: Fri Dec 07, 2018 2:10 am
Separately, upon entering a fresh session, I noted that htop indicates THREE clipit processes are running.
After "killall clipit" and launching from commandline, yep, three clipit processes (hmm, or are they just multiple "threads" of one precess?)
htop here only shows one instance of ClipIt on boot. If I launch it from the terminal, it starts with a message about the Ctrl-Alt-H keybinding failing. A second instance starts, as shown by two icons on the panel. htop then shows two running instances. That is expected behaviour.
Not sure what is going on with your install, but it's not happening here.
Chris
Re: MX-18 beta 1 feedback
Posted: Fri Dec 07, 2018 5:35 am
by Paul..
caprea wrote: Thu Dec 06, 2018 9:34 pm
Paul.. wrote: Thu Dec 06, 2018 8:48 pm Code: Select all
I'm using the 4.15.5-antix.1-amd64-smp and I checked CONFIG_RCU_NOCB_CPU=y
If the Typical Current Idle works the way its supposed to do, a rcu_nocbs-parameter should not be necessary.
Ran all night with no problems using: Typical Current Idle + rcu_nocbs + 4.15.5-antix.1-amd64-smp
Will remove rcu_nocbs today and see...
Thanks caprea!!
Re: MX-18 beta 1 feedback
Posted: Fri Dec 07, 2018 8:33 am
by Gerson
How can I place a screensaver? The option does not appear and neither Grub-customizer.
Re: MX-18 beta 1 feedback-MXPI not installing kernel
Posted: Fri Dec 07, 2018 10:02 am
by entropyfoe
See my post #204 in this MX18 beta1 thread.
I am still fighting the Ryzen crash/reboot at idle problem.
From caprea's comments, and Pauls trials, I am trying to install the 4.19-antix.1 kernel with the MX Package installer.
But I get the errors in the #204 post, so I cannot try that kernel.
1. Any ideas why the MXPI did not install the kernel? I updated both MX 17.1 and 18 grubs.
Are my repositories messed up? I do have the dev repo enables (to get the nvidia driver-which worked).
2. Or can I some how install another parameter at grub time to make the rcu-nocbs=0-11 fix work in the MX kernel?
That may be this line...
CONFIG_RCU_NOCB_CPU=y
Re: MX-18 beta 1 feedback-MXPI not installing kernel
Posted: Fri Dec 07, 2018 10:51 am
by fehlix
entropyfoe wrote: Fri Dec 07, 2018 10:02 am
See my post #204 in this MX18 beta1 thread.
But I get the errors in the #204 post, so I cannot try that kernel.
1. Any ideas why the MXPI did not install the kernel? I updated both MX 17.1 and 18 grubs.
Are my repositories messed up? I do have the dev repo enables (to get the nvidia driver-which worked).
I might have missed something. If you are referring to the timeout "Could not connect to iso.mxrepo.com",
then the answer is simple: In such cases just select another repo-mirror with MX Repo Manager.
You might either select manually or try to select fastest. Note the later selection will only check the server is up,
but will not check the functionality to work properly as repo-server.
Having a pool of repo-mirrors is not only in respect of download bandwidth but also to cater for the case
if one repo is temporarily not available, which can happen.
BTW, meanwhile iso.mxrepo.com should be back again.
Re: MX-18 beta 1 feedback
Posted: Fri Dec 07, 2018 10:55 am
by Adrian
skidoo wrote: Fri Dec 07, 2018 2:10 am
Quick access to MX User Manual is a standout feature. IIRC, what tripped me up while wearing my "noob user" tester hat:
When MXUM is launched from the welcome dialog, the welcome dialog autohides (and no taskbar item for it).
Please consider using nohup or disown in the Welcome--}MXUM launchstring, as well as for a select few other launchers presented within the Welcome dialog.
OK, I can see having to have MXUM running in parallel with other apps, so I think it's a good suggestion to make it run with disown, for the rest of the apps I think I prefer the way it works now, meaning there's a clear workflow, you press on Teaks you do your teaks, finish with that and close it, Welcome screen comes back on.
Re: MX-18 beta 1 feedback
Posted: Fri Dec 07, 2018 11:05 am
by fehlix
Adrian wrote: Fri Dec 07, 2018 10:55 am
skidoo wrote: Fri Dec 07, 2018 2:10 am
Quick access to MX User Manual is a standout feature. IIRC, what tripped me up while wearing my "noob user" tester hat:
When MXUM is launched from the welcome dialog, the welcome dialog autohides (and no taskbar item for it).
Please consider using nohup or disown in the Welcome--}MXUM launchstring, as well as for a select few other launchers presented within the Welcome dialog.
OK, I can see having to have MXUM running in parallel with other apps, so I think it's a good suggestion to make it run with disown, for the rest of the apps I think I prefer the way it works now, meaning there's a clear workflow, you press on Teaks you do your teaks, finish with that and close it, Welcome screen comes back on.
I support skiddo's proposal.
Remember, newbies don't have a workflow, they want to look around first. A disappearance of the Welcome screen is rather irritating, not only for newbies for me too.
Re: MX-18 beta 1 feedback
Posted: Fri Dec 07, 2018 11:13 am
by Adrian
fehlix wrote: Fri Dec 07, 2018 11:05 am
Adrian wrote: Fri Dec 07, 2018 10:55 am
skidoo wrote: Fri Dec 07, 2018 2:10 am
Quick access to MX User Manual is a standout feature. IIRC, what tripped me up while wearing my "noob user" tester hat:
When MXUM is launched from the welcome dialog, the welcome dialog autohides (and no taskbar item for it).
Please consider using nohup or disown in the Welcome--}MXUM launchstring, as well as for a select few other launchers presented within the Welcome dialog.
OK, I can see having to have MXUM running in parallel with other apps, so I think it's a good suggestion to make it run with disown, for the rest of the apps I think I prefer the way it works now, meaning there's a clear workflow, you press on Teaks you do your teaks, finish with that and close it, Welcome screen comes back on.
I support skiddo's proposal.
Remember, newbies don't have a workflow, they want to look around first. A disappearance of the Welcome screen is rather irritating, not only for newbies for me too.
OK, fine, I wanted to avoid something like this:
Re: MX-18 beta 1 feedback
Posted: Fri Dec 07, 2018 11:24 am
by fehlix
Adrian wrote: Fri Dec 07, 2018 11:13 am
fehlix wrote: Fri Dec 07, 2018 11:05 am
Adrian wrote: Fri Dec 07, 2018 10:55 am
OK, I can see having to have MXUM running in parallel with other apps, so I think it's a good suggestion to make it run with disown, for the rest of the apps I think I prefer the way it works now, meaning there's a clear workflow, you press on Teaks you do your teaks, finish with that and close it, Welcome screen comes back on.
I support skiddo's proposal.
Remember, newbies don't have a workflow, they want to look around first. A disappearance of the Welcome screen is rather irritating, not only for newbies for me too.
OK, fine, I wanted to avoid something like this:
[/url]
Understand. It might be less irritating keeping the Welcom screen up, then this disappearing and suddenly appearing again.
It's now kind of/like Whisker-menu disappears when clicking an app, but suddenly from nowhere it appears again.
Re: MX-18 beta 1 feedback
Posted: Fri Dec 07, 2018 11:37 am
by richb
I would find leaving the Welcome screen up annoying.
Re: MX-18 beta 1 feedback
Posted: Fri Dec 07, 2018 11:40 am
by fehlix
richb wrote: Fri Dec 07, 2018 11:37 am
I would find leaving the Welcome screen up annoying.
You are not newbie
Re: MX-18 beta 1 feedback
Posted: Fri Dec 07, 2018 11:47 am
by richb
fehlix wrote: Fri Dec 07, 2018 11:40 am
richb wrote: Fri Dec 07, 2018 11:37 am
I would find leaving the Welcome screen up annoying.
You are not newbie
I think after a week of use a newbie would find it annoying. Just an opinion and not verifiable. I see nothing wrong with the current setup. For quick access put MX Welcome in Favorites.
EDIT: By the way MX Tools works the same way.
Re: MX-18 beta 1 feedback
Posted: Fri Dec 07, 2018 11:54 am
by fehlix
richb wrote: Fri Dec 07, 2018 11:47 am
fehlix wrote: Fri Dec 07, 2018 11:40 am
richb wrote: Fri Dec 07, 2018 11:37 am
I would find leaving the Welcome screen up annoying.
You are not newbie
... after a week of use a newbie would ...
... probably rarely open the Welcome screen anyway, if at all. :lipsrsealed:
Re: MX-18 beta 1 feedback
Posted: Fri Dec 07, 2018 11:55 am
by richb
fehlix wrote: Fri Dec 07, 2018 11:54 am
richb wrote: Fri Dec 07, 2018 11:47 am
fehlix wrote: Fri Dec 07, 2018 11:40 am
You are not newbie
... after a week of use a newbie would ...
... probably rarely open the Welcome screen anyway, if at all. :lipsrsealed:
Me either but we are not newbies.
Re: MX-18 beta 1 feedback
Posted: Fri Dec 07, 2018 12:03 pm
by dreamer
I agree with fehlix. Windows that disappear and reappear are not good UX design. Good UX design is predictable. Like the physical world. Things don't appear and disappear without physical interaction. It's the basics of the desktop metaphor. Each window is a real world folder or document. You can put them away by minimizing them or closing them.
I respect that other people might prefer a more "slick" experience, I'm old-fashioned.
So yes, my opinion is that MX Tools window is equally annoying.
I grew up with PCs, not smartphones so the desktop metaphor is pretty strong in me and so is old-school thinking.
Re: MX-18 beta 1 feedback
Posted: Fri Dec 07, 2018 12:06 pm
by Adrian
OK, let's end this discussion about MX Welcome, the code is changed, D_O will review it later on today.
Re: MX-18 beta 1 feedback
Posted: Fri Dec 07, 2018 12:18 pm
by Fornhamfred
On my Mx17 upgraded to 18 beta the login screen is displayed momentarily during shutdown. Just tested my fresh MX18 install and that does the same.
Re: MX-18 beta 1 feedback
Posted: Fri Dec 07, 2018 12:26 pm
by Paul..
Ryzen crash update --
This looks like a keeper
Asus Prime X470-Pro motherboard w/Ryzen 5 1400 CPU...stable for 5 hours...and will keep it running overnight
-
OS version: MX-18b1_x64 Continuum December 3 2018
-
Kernel: 4.15.5-antix.1-amd64-smp
-
UEFI setup: Advanced->AMD CBS ->Power Supply Idle Control->Typical Current Idle
-
Boot option: Not using "rcu_nocbs=0-7"
Note: will test other kernels tomorrow.
Re: MX-18 beta 1 feedback
Posted: Fri Dec 07, 2018 1:03 pm
by mmikeinsantarosa
Gerson wrote: Fri Dec 07, 2018 8:33 am
How can I place a screensaver? The option does not appear and neither Grub-customizer.
You may see screensavers in mxpi soon. And use mx boot options instead of grub customizer.
mike
Re: MX-18 beta 1 feedback
Posted: Fri Dec 07, 2018 5:19 pm
by Jerry3904
Well this is fun! Just received an MSI U135 from one of our users for testing purposes, and the beta runs OK, if a bit slow. It seems that everything is functioning normally:
Code: Select all
System: Host: mx1 Kernel: 4.19.0-1-amd64 x86_64 bits: 64 compiler: gcc v: 6.3.0
Desktop: Xfce 4.12.3 Distro: MX-18b1_x64 Continuum December 3 2018
base: Debian GNU/Linux 9 (stretch)
Machine: Type: Laptop System: MICRO-STAR product: MS-N014 v: REV:1.0 serial: <filter>
Mobo: MICRO-STAR model: MS-N014 v: REV:1.0 serial: <filter> BIOS: American Megatrends
v: EN014IMS.30k date: 01/08/2010
Battery: ID-1: BAT1 charge: 45.5 Wh condition: 48.2/48.8 Wh (99%) model: MSI Corp. MS-N014
status: Charging
Device-1: hidpp_battery_0 model: Logitech Wireless Mouse charge: Normal
status: Discharging
CPU: Topology: Single Core model: Intel Atom N450 bits: 64 type: MT arch: Bonnell rev: A
L2 cache: 512 KiB
flags: lm nx pae sse sse2 sse3 ssse3 bogomips: 6649
Speed: 1599 MHz min/max: 1000/1667 MHz Core speeds (MHz): 1: 1238 2: 1233
Graphics: Device-1: Intel Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics driver: i915
v: kernel bus ID: 00:02.0
Display: x11 server: X.Org 1.19.2 driver: intel resolution: 1024x600~60Hz
OpenGL: renderer: Mesa DRI Intel Pineview M v: 1.4 Mesa 18.2.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
Sound Server: ALSA v: k4.19.0-1-amd64
Network: Device-1: Qualcomm Atheros AR9285 Wireless Network Adapter driver: ath9k v: kernel
port: f000 bus ID: 01:00.0
IF: wlan0 state: up mac: <filter>
Device-2: Realtek RTL8101/2/6E PCI Express Fast/Gigabit Ethernet driver: r8169
v: kernel port: e000 bus ID: 02:00.0
IF: eth0 state: down mac: <filter>
Drives: Local Storage: total: 122.04 GiB used: 1.33 GiB (1.1%)
ID-1: /dev/sda vendor: Toshiba model: MK1032GSX size: 93.16 GiB
ID-2: /dev/sdb type: USB vendor: PNY model: USB 3.0 FD size: 28.88 GiB
Partition: ID-1: / size: 1.51 GiB used: 258.9 MiB (16.7%) fs: overlay dev: ERR-102
Sensors: System Temperatures: cpu: 45.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/stretch stretch main
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://ftp.us.debian.org/debian/ stretch-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://ftp.us.debian.org/debian/ stretch main contrib non-free
2: deb http://security.debian.org/ stretch/updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://mxrepo.com/mx/repo/ stretch main non-free
No active apt repos in: /etc/apt/sources.list.d/various.list
Info: Processes: 172 Uptime: 9m Memory: 1.94 GiB used: 651.7 MiB (32.8%) Init: SysVinit
runlevel: 5 Compilers: gcc: 6.3.0 Shell: bash v: 4.4.12 inxi: 3.0.25
Re: MX-18 beta 1 feedback
Posted: Fri Dec 07, 2018 5:42 pm
by Gerson
@mmikeinsantarosa
With MX boot options I can only change the background of the grub but I like to change the color of the typefaces.
Re: MX-18 beta 1 feedback
Posted: Fri Dec 07, 2018 5:52 pm
by richb
Gerson wrote: Fri Dec 07, 2018 5:42 pm
@mmikeinsantarosa
With MX boot options I can only change the background of the grub but I like to change the color of the typefaces.
You can install grub-customizer from the repos.
Re: MX-18 beta 1 feedback
Posted: Fri Dec 07, 2018 10:38 pm
by entropyfoe
Paul, How is that typical idle current stetting working? With or without the rcu_nocbs?
I was able to use the MX Package installer to get the 4.19-antix kernel, which I have installed. All went smoothly, updated the grubs, and am posting from MX18 b1 with the 4.19.4-antix.1 kernel.
I think the LTS support of this kernel will make it useful to us and attractive to the potential users. This should be stressed in the PR and distrowatch pronouncements !
The hypothesis is, the antix kernels have some rcu option set that makes the rcu_ncbs=0-11 effective. For me this was certainly true with the 4.15 antix kernel.
So now I will test for stability, before it was three crashes in two days.
Depending on what Paul finds, I may update the BIOS. This idle current setting, most say it fixes it, though a minority on the amd boards say they still get crashes.
Re: MX-18 beta 1 feedback
Posted: Sat Dec 08, 2018 3:58 am
by chrispop99
Jerry3904 wrote: Fri Dec 07, 2018 5:19 pm
Well this is fun! Just received an MSI U135 from one of our users for testing purposes, and the beta runs OK, if a bit slow. It seems that everything is functioning normally:
Code: Select all
System: Host: mx1 Kernel: 4.19.0-1-amd64 x86_64 bits: 64 compiler: gcc v: 6.3.0
Desktop: Xfce 4.12.3 Distro: MX-18b1_x64 Continuum December 3 2018
base: Debian GNU/Linux 9 (stretch)
Machine: Type: Laptop System: MICRO-STAR product: MS-N014 v: REV:1.0 serial: <filter>
Mobo: MICRO-STAR model: MS-N014 v: REV:1.0 serial: <filter> BIOS: American Megatrends
v: EN014IMS.30k date: 01/08/2010
Battery: ID-1: BAT1 charge: 45.5 Wh condition: 48.2/48.8 Wh (99%) model: MSI Corp. MS-N014
status: Charging
Device-1: hidpp_battery_0 model: Logitech Wireless Mouse charge: Normal
status: Discharging
CPU: Topology: Single Core model: Intel Atom N450 bits: 64 type: MT arch: Bonnell rev: A
L2 cache: 512 KiB
flags: lm nx pae sse sse2 sse3 ssse3 bogomips: 6649
Speed: 1599 MHz min/max: 1000/1667 MHz Core speeds (MHz): 1: 1238 2: 1233
Graphics: Device-1: Intel Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics driver: i915
v: kernel bus ID: 00:02.0
Display: x11 server: X.Org 1.19.2 driver: intel resolution: 1024x600~60Hz
OpenGL: renderer: Mesa DRI Intel Pineview M v: 1.4 Mesa 18.2.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
Sound Server: ALSA v: k4.19.0-1-amd64
Network: Device-1: Qualcomm Atheros AR9285 Wireless Network Adapter driver: ath9k v: kernel
port: f000 bus ID: 01:00.0
IF: wlan0 state: up mac: <filter>
Device-2: Realtek RTL8101/2/6E PCI Express Fast/Gigabit Ethernet driver: r8169
v: kernel port: e000 bus ID: 02:00.0
IF: eth0 state: down mac: <filter>
Drives: Local Storage: total: 122.04 GiB used: 1.33 GiB (1.1%)
ID-1: /dev/sda vendor: Toshiba model: MK1032GSX size: 93.16 GiB
ID-2: /dev/sdb type: USB vendor: PNY model: USB 3.0 FD size: 28.88 GiB
Partition: ID-1: / size: 1.51 GiB used: 258.9 MiB (16.7%) fs: overlay dev: ERR-102
Sensors: System Temperatures: cpu: 45.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/stretch stretch main
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://ftp.us.debian.org/debian/ stretch-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://ftp.us.debian.org/debian/ stretch main contrib non-free
2: deb http://security.debian.org/ stretch/updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://mxrepo.com/mx/repo/ stretch main non-free
No active apt repos in: /etc/apt/sources.list.d/various.list
Info: Processes: 172 Uptime: 9m Memory: 1.94 GiB used: 651.7 MiB (32.8%) Init: SysVinit
runlevel: 5 Compilers: gcc: 6.3.0 Shell: bash v: 4.4.12 inxi: 3.0.25
One of my test machines is Atom-based, and also works without issue.
Chris
Re: MX-18 beta 1 feedback
Posted: Sat Dec 08, 2018 4:27 am
by Gerson
My report MX 18 beta after 5 days of use without problem, except that the Conky when clicking on the desktop disappears:
Code: Select all
System: Host: Compaq Kernel: 4.19.0-1-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3
Distro: MX-18b1_x64 Continuum December 3 2018
Machine: Type: Laptop System: COMPAQ product: Presario 21 VerK v: N/A serial: <root required>
Mobo: EA model: K21 v: Type2 - Board Version serial: <root required> UEFI: COMPAQ
v: fd date: 02/27/2016
Battery: ID-1: BAT1 charge: 46.1 Wh condition: 48.1/N/A Wh
CPU: Topology: Dual Core model: Intel Core i3-6100U bits: 64 type: MT MCP
L2 cache: 3072 KiB
Speed: 900 MHz min/max: 400/2300 MHz Core speeds (MHz): 1: 900 2: 902 3: 900 4: 900
Graphics: Device-1: Intel HD Graphics 520 driver: i915 v: kernel
Display: x11 server: X.Org 1.19.2 driver: modesetting unloaded: fbdev,vesa
resolution: 1366x768~60Hz
OpenGL: renderer: Mesa DRI Intel HD Graphics 520 (Skylake GT2) v: 4.5 Mesa 18.2.6
Audio: Device-1: Intel Sunrise Point-LP HD Audio driver: snd_hda_intel
Sound Server: ALSA v: k4.19.0-1-amd64
Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169
IF: eth0 state: up speed: 100 Mbps duplex: full mac: 00:e0:4c:69:89:db
Device-2: Intel Wireless 3160 driver: iwlwifi
IF: wlan0 state: up mac: 78:0c:b8:f4:da:30
Drives: Local Storage: total: 931.51 GiB used: 367.59 GiB (39.5%)
ID-1: /dev/sda vendor: HGST (Hitachi) model: HTS541010A7E630 size: 931.51 GiB
Partition: ID-1: / size: 22.57 GiB used: 6.07 GiB (26.9%) fs: ext4 dev: /dev/sda2
ID-2: /home size: 95.62 GiB used: 29.19 GiB (30.5%) fs: ext4 dev: /dev/sda3
ID-3: swap-1 size: 4.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda4
Sensors: System Temperatures: cpu: 36.0 C mobo: N/A
Fan Speeds (RPM): N/A
Info: Processes: 210 Uptime: 16m Memory: 3.77 GiB used: 1.13 GiB (30.1%) Shell: bash
inxi: 3.0.25
Re: MX-18 beta 1 feedback
Posted: Sat Dec 08, 2018 4:38 am
by asqwerth
A lot depends on the way a particular conky config was written, and its interaction with your desktop, what compositing and window manager you use, etc.
You could probably ask in the conky thread, male might be able to solve the issue if you provide your conky config in your post there.
If it's solved, let us know . But it may not be a solution that requires changing the beta packages. Others may or may not have the same issue. Let's see .
Re: MX-18 beta 1 feedback
Posted: Sat Dec 08, 2018 5:50 am
by Ghost67
No problems to report back here as yet, aside from Steam not installing due to certain 32bit packages being held back. Not a problem for daily use though.
Possibly I can fix by using another repo but I'm not prepared to change defaults, regardless of the OS. I'm a stickler like that :)
Re: MX-18 beta 1 feedback
Posted: Sat Dec 08, 2018 5:53 am
by Paul..
Paul.. wrote: Fri Dec 07, 2018 12:26 pm
Ryzen crash update --
This looks like a keeper
Asus Prime X470-Pro motherboard w/Ryzen 5 1400 CPU...stable for 5 hours...and will keep it running overnight
-
OS version: MX-18b1_x64 Continuum December 3 2018
-
Kernel: 4.15.5-antix.1-amd64-smp
-
UEFI setup: Advanced->AMD CBS ->Power Supply Idle Control->Typical Current Idle
-
Boot option: Not using "rcu_nocbs=0-7"
@entropyfoe
Kernel: 4.19.0-1-amd64 is good with config above (this kernel does not support "rcu_nocbs" option) ...Uptime: 12h 30m
will test 4.15.5-antix.1-amd64-smp (which does support "rcu_nocbs option) all day today
@caprea...many thanks for pointing us all to the UEFI setup for these Asus Motherboards
Re: MX-18 beta 1 feedback
Posted: Sat Dec 08, 2018 7:31 am
by Richard
MX Boot Options changes not sticking...
moved to ...
viewtopic.php?f=108&t=47262#p470901
Re: MX-18 beta 1 feedback
Posted: Sat Dec 08, 2018 7:41 am
by anticapitalista
entropyfoe wrote: Fri Dec 07, 2018 10:38 pm
Paul, How is that typical idle current stetting working? With or without the rcu_nocbs?
I was able to use the MX Package installer to get the 4.19-antix kernel, which I have installed.
All went smoothly, updated the grubs, and am posting from MX18 b1 with the 4.19.4-antix.1 kernel.
I think the LTS support of this kernel will make it useful to us and attractive to the potential users. This should be stressed in the PR and distrowatch pronouncements !
The hypothesis is, the antix kernels have some rcu option set that makes the rcu_ncbs=0-11 effective. For me this was certainly true with the 4.15 antix kernel.
So now I will test for stability, before it was three crashes in two days.
Depending on what Paul finds, I may update the BIOS. This idle current setting, most say it fixes it, though a minority on the amd boards say they still get crashes.
antiX now has 4.19.7-antix.1 kernel
Re: MX-18 beta 1 feedback
Posted: Sat Dec 08, 2018 8:40 am
by Paul..
Thanks, anti. I will add that to the list to test.
Re: MX-18 beta 1 feedback
Posted: Sat Dec 08, 2018 9:21 am
by entropyfoe
Thanks anti, what is the advantage of running the 4.19.7 over the 4.19.4?
More security patches?
So far the antix kernel has remained up for >12 hours, encouraging, but too early to claim stability. I should be more confident by say Sunday night.
Paul, the MX kernel, as you wrote does not support the rcu_nocbs, so that explains why we had the crashes.
I will test this kernel for a few days. I downloaded the latest BIOS and have it ready for testing after I see that the kernel approach is stable.
It makes sense that the motherboard manufacturers would figure a way to fix this with a BIOS change. I hope that works of you, and then me !
Re: MX-18 beta 1 feedback
Posted: Sat Dec 08, 2018 10:30 am
by Paul..
entropyfoe wrote: Sat Dec 08, 2018 9:21 am
Thanks anti, what is the advantage of running the 4.19.7 over the 4.19.4?
More security patches?
So far the antix kernel has remained up for >12 hours, encouraging, but too early to claim stability. I should be more confident by say Sunday night.
Paul, the MX kernel, as you wrote does not support the rcu_nocbs, so that explains why we had the crashes.
I will test this kernel for a few days. I downloaded the latest BIOS and have it ready for testing after I see that the kernel approach is stable.
It makes sense that the motherboard manufacturers would figure a way to fix this with a BIOS change. I hope that works of you, and then me !
Looks like one difference is:
4.19.7-antix.1-amd64-smp (does not support rcu_nocbs)
4.19.4-antix.1-amd64-smp (does support rcu_nocbs)
Re: MX-18 beta 1 feedback
Posted: Sat Dec 08, 2018 10:46 am
by anticapitalista
Paul.. wrote: Sat Dec 08, 2018 10:30 am
Looks like one difference is:
4.19.7-antix.1-amd64-smp (does not support rcu_nocbs)
4.19.4-antix.1-amd64-smp (does support rcu_nocbs)
Yes. See how it works without rcu_nocbs.
If it doen't work well, then I'll reverse the kernel config and put it back.
Re: MX-18 beta 1 feedback
Posted: Sat Dec 08, 2018 10:50 am
by Paul..
you're the best, antiC
Re: MX-18 beta 1 feedback
Posted: Sat Dec 08, 2018 11:09 am
by baldyeti
anticapitalista wrote: Sat Dec 08, 2018 7:41 amantiX now has 4.19.7-antix.1 kernel
Not to request every single kernel dot version, but given the
following, wouldn't 4.19.8+ be a better choice for the RC/MX18-release ?
Re: MX-18 beta 1 feedback
Posted: Sat Dec 08, 2018 11:09 am
by Gerson
@asqwerth
On the same machine I use the same Conky that I used in MX 17.1 and it is this:
~/.conky/MX-LSD/lsd2/conkyrc
Re: MX-18 beta 1 feedback
Posted: Sat Dec 08, 2018 11:13 am
by entropyfoe
Then obviously I need the .4.
Why would there be a difference?
Re: MX-18 beta 1 feedback
Posted: Sat Dec 08, 2018 11:21 am
by asqwerth
Gerson wrote: Sat Dec 08, 2018 11:09 am
@asqwerth
On the same machine I use the same Conky that I used in MX 17.1 and it is this:
~/.conky/MX-LSD/lsd2/conkyrc
Is desktop compositing on? Settings exactly the same as in 17.1?
Wait, hang on. Fehlix did some tweaks to some conkys to automatically follow the 12/24 hour time settings of your system, so the config for LSD conky may not be exactly the same as in 17.1.
You'll need to check with fehlix.
Re: MX-18 beta 1 feedback
Posted: Sat Dec 08, 2018 11:41 am
by spdanis65
MX 18 beta1 very sluggish attemping install on Thinkpad E565 though MX17.1 is fine. The Lenovo Edge is their "Cheez Whiz" series. Booting with an Atheros AR9271 stick as the particular built-in Broadcom wifi adapter is not supported.
Re: MX-18 beta 1 feedback
Posted: Sat Dec 08, 2018 11:52 am
by chrispop99
spdanis65 wrote: Sat Dec 08, 2018 11:41 am
MX 18 beta1 very sluggish attemping install on Thinkpad E565 though MX17.1 is fine. The Lenovo Edge is their "Cheez Whiz" series. Booting with an Atheros AR9271 stick as the particular built-in Broadcom wifi adapter is not supported.
Welcome, and thanks for the report.
Did it run OK live? Was it the install that was sluggish, or the performance after the install?
Would you please post the output of Quick System Info, from the MX Tools menu.
Chris
Re: MX-18 beta 1 feedback
Posted: Sat Dec 08, 2018 11:56 am
by fehlix
asqwerth wrote: Sat Dec 08, 2018 11:21 am
Gerson wrote: Sat Dec 08, 2018 11:09 am
@asqwerth
On the same machine I use the same Conky that I used in MX 17.1 and it is this:
~/.conky/MX-LSD/lsd2/conkyrc
.. some tweaks to some conkys to automatically follow the 12/24 hour time settings of your system, so the config for LSD conky may not be exactly the same as in 17.1.
This is one of those magic lua-script conkies which was not touched regarding the 12/24 display issue.
The issue of suddenly not displaying when clicking on the desktop is reproducable and will be fixed via pull request asap.
Re: MX-18 beta 1 feedback
Posted: Sat Dec 08, 2018 12:45 pm
by Jerry3904
Glad to hear that.
Re: MX-18 beta 1 feedback
Posted: Sat Dec 08, 2018 8:17 pm
by Paul..
Asus motherboard + AMD Ryzen crash testing with various kernels --
Base Test System
OS: MX-18b1_x64 (Upgraded from devrepo)
Motherboard: Asus Prime X470-Pro
CPU: AMD Ryzen 5 1400
UEFI option: Advanced->AMD CBS ->Power Supply Idle Control->Typical Current Idle
Kernel option: Not using "rcu_nocbs..."
Kernels that tested stable so far (5+ hours)
- 4.15.5-antix.1-amd64-smp
- 4.19.0-1-amd64
- 4.19.4-antix.1-amd64-smp
- 4.19.7-antix.1-amd64-smp
EDIT: 4.19.8-antix.1-amd64-smp
Conclusion: Best avenue appears to be using "Typical Current Idle" setting available via upgraded UEFI firmware
Re: MX-18 beta 1 feedback
Posted: Sun Dec 09, 2018 6:29 am
by Gerson
Suggestion to translate into Spanish: "Cento Multimedia" (Multimedia center) no "Centro de medias"; (medias = socks)
Re: MX-18 beta 1 feedback
Posted: Sun Dec 09, 2018 7:07 am
by anticapitalista
Used live-usb-maker to make an encrypted live stick (32 bit version), but on first boot on this T60, I get this error.
Failed to set up dm-crypt key mapping for device /dev/sdb2
Check that kernel supports aes-xts-plin64 cipher
Using live-ub-maker without encryption and the stick boots fine and beta1 works well even live (usb2)
Re: MX-18 beta 1 feedback
Posted: Sun Dec 09, 2018 7:39 am
by richb
anticapitalista wrote: Sun Dec 09, 2018 7:07 am
Used live-usb-maker to make an encrypted live stick (32 bit version), but on first boot on this T60, I get this error.
Failed to set up dm-crypt key mapping for device /dev/sdb2
Check that kernel supports aes-xts-plin64 cipher
Using live-ub-maker without encryption and the stick boots fine and beta1 works well even live (usb2)
Made an encrypted live stick (64 bit version), first boot on AMD desktop booted to desktop after asking to set encryption password and asking for same password to continue.. Posted this for another data point.
Code: Select all
System: Host: mx Kernel: 4.19.0-1-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: F2A68HM-H v: x.x serial: <root required> UEFI: American Megatrends v: FB
date: 04/22/2015
CPU: Topology: Quad Core model: AMD A8-7600 Radeon R7 10 Compute Cores 4C+6G bits: 64 type: MCP
L2 cache: 2048 KiB
Speed: 1828 MHz min/max: 1400/3100 MHz Core speeds (MHz): 1: 1821 2: 1811 3: 1523 4: 1471
Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Kaveri [Radeon R7 Graphics] driver: radeon v: kernel
Display: x11 server: X.Org 1.19.2 driver: ati,radeon unloaded: fbdev,modesetting,vesa
resolution: 1920x1080~60Hz
OpenGL: renderer: AMD KAVERI (DRM 2.50.0 4.19.0-1-amd64 LLVM 7.0.0) v: 4.5 Mesa 18.2.6
Audio: Device-1: Advanced Micro Devices [AMD/ATI] Kaveri HDMI/DP Audio driver: snd_hda_intel
Device-2: Advanced Micro Devices [AMD] FCH Azalia driver: snd_hda_intel
Sound Server: ALSA v: k4.19.0-1-amd64
Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169
IF: eth0 state: down mac: 40:8d:5c:0d:62:1b
Device-2: Qualcomm Atheros AR93xx Wireless Network Adapter driver: ath9k
IF: wlan0 state: up mac: 60:e3:27:08:b6:6c
Drives: Local Storage: total: 757.78 GiB used: 116.94 GiB (15.4%)
ID-1: /dev/sda vendor: Samsung model: SSD 850 EVO 250GB size: 232.89 GiB
ID-2: /dev/sdb vendor: Samsung model: SSD 850 EVO 250GB size: 232.89 GiB
ID-3: /dev/sdc vendor: Samsung model: SSD 850 EVO 250GB size: 232.89 GiB
ID-4: /dev/sdd type: USB vendor: PNY model: USB 3.0 FD size: 59.12 GiB
Partition: ID-1: / size: 225.02 GiB used: 14.97 GiB (6.7%) fs: ext4 dev: /dev/sda2
ID-2: swap-1 size: 2.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda3
Sensors: System Temperatures: cpu: 10.1 C mobo: N/A gpu: radeon temp: 12 C
Fan Speeds (RPM): N/A
Info: Processes: 238 Uptime: 5m Memory: 14.69 GiB used: 1.16 GiB (7.9%) Shell: bash inxi: 3.0.25
Re: MX-18 beta 1 feedback
Posted: Sun Dec 09, 2018 9:24 am
by chrispop99
anticapitalista wrote: Sun Dec 09, 2018 7:07 am
Used live-usb-maker to make an encrypted live stick (32 bit version), but on first boot on this T60, I get this error.
Failed to set up dm-crypt key mapping for device /dev/sdb2
Check that kernel supports aes-xts-plin64 cipher
Using live-ub-maker without encryption and the stick boots fine and beta1 works well even live (usb2)
Problem confirmed with Dell D610.
Chris
Re: MX-18 beta 1 feedback
Posted: Sun Dec 09, 2018 9:41 am
by manyroads
Just a quick update on my three MX18 pcs. All are working exceptionally well with only tiny items / errors noted.
- I had one Dell Latitude lose both its mouse and trackpad. I can not get the error to repeat. A shutdown/ reboot fixed things, I think.
- I experience a usability issue writing a Personal backup to USB. My USB was too small and the dd (LiveUSB creation function) abended (old geek's term) without a helpful error message. Replacing the USB with a larger capacity USB allowed the USB to write successfully. A pre-test for USB size appropriateness test would be helpful. Minimally a better error message would help.
Otherwise, the system seems exceptionally 'smooth' and polished, to me and my little user community of three test users/machines.
Re: MX-18 beta 1 feedback
Posted: Sun Dec 09, 2018 9:58 am
by entropyfoe
Paul,
So you have total >25 hours with the idle current typical setting with different kernels, and no rcu_nocbs.
That is encouraging.
I crashed with the antix kernel AND rcu_nocbs, so....
Last night I installed the latest BIOS (4024) and rebooted with the idle current set to typical (default was AUTO).
SO far 16 hours, but it will take a few days to be sure.
Other than the Ryzen specific problem, the beta1 is running smoothly.
The crashes were only at idle, when running actively, never a problem.
Re: MX-18 beta 1 feedback
Posted: Sun Dec 09, 2018 10:24 am
by Paul..
entropyfoe wrote: Sun Dec 09, 2018 9:58 am
Paul,
So you have total >25 hours with the idle current typical setting with different kernels, and no rcu_nocbs.
That is encouraging.
I crashed with the antix kernel AND rcu_nocbs, so....
Last night I installed the latest BIOS (4024) and rebooted with the idle current set to typical (default was AUTO).
SO far 16 hours, but it will take a few days to be sure.
Other than the Ryzen specific problem, the beta1 is running smoothly.
The crashes were only at idle, when running actively, never a problem.
4024 is the same version as I installed...looking good!
Re: MX-18 beta 1 feedback
Posted: Sun Dec 09, 2018 10:25 am
by dolphin_oracle
anticapitalista wrote: Sun Dec 09, 2018 7:07 am
Used live-usb-maker to make an encrypted live stick (32 bit version), but on first boot on this T60, I get this error.
Failed to set up dm-crypt key mapping for device /dev/sdb2
Check that kernel supports aes-xts-plin64 cipher
Using live-ub-maker without encryption and the stick boots fine and beta1 works well even live (usb2)
I'm looking at the kernel configs for hte 64bit vs. the 32 bit and I'm not seeing a big difference. these are the items with aes in them.
Code: Select all
CONFIG_CRYPTO_AES=y
# CONFIG_CRYPTO_AES_TI is not set
CONFIG_CRYPTO_AES_586=m
CONFIG_CRYPTO_AES_NI_INTEL=m
and
they appear to be the same in both kernels.
any other ideas where to look?
Re: MX-18 beta 1 feedback
Posted: Sun Dec 09, 2018 11:11 am
by Old Giza
Gerson wrote: Sun Dec 09, 2018 6:29 am
Suggestion to translate into Spanish: "Cento Multimedia" (Multimedia center) no "Centro de medias"; (medias = socks)
Done. Changed to "Centro multimedia" as per screenshot. (It will come through normal updates, not necessarily with MX-18 release.)
Re: MX-18 beta 1 feedback
Posted: Sun Dec 09, 2018 12:12 pm
by anticapitalista
CONFIG_CRYPTO_XTS is needed from what I found on the net.
Re: MX-18 beta 1 feedback
Posted: Sun Dec 09, 2018 12:17 pm
by dolphin_oracle
anticapitalista wrote: Sun Dec 09, 2018 12:12 pm
CONFIG_CRYPTO_XTS is needed from what I found on the net.
here's what we have on the 32 bit.
I'm trying one of the antiX kernels.
Re: MX-18 beta 1 feedback
Posted: Sun Dec 09, 2018 12:34 pm
by anticapitalista
antiX kernels has that as CONFIG_CRYPTO_XTS=y
Re: MX-18 beta 1 feedback
Posted: Sun Dec 09, 2018 12:42 pm
by davemx
I installed it last night, on Desktop only. I'm using it now. So far the stuff I've done so far works, but GIMP 2.10 clashes with data files needed for MyPaint (no such problem with 2.8 and I hate the grey scheme but none of that is the fault of this excellent distro). Hopefully I'll be able to push a few things and test them over the next few days.
Can report now: Printing and Scanning working perfectly
To revert GIMP interface theme:
https://www.daviesmediadesign.com/custo ... interface/
Re: MX-18 beta 1 feedback
Posted: Sun Dec 09, 2018 1:02 pm
by dolphin_oracle
anticapitalista wrote: Sun Dec 09, 2018 12:34 pm
antiX kernels has that as CONFIG_CRYPTO_XTS=y
I tried a snapshot with the antix 4.19.7 kernel but I'm getting a copy modules error in the cli LUM.
Re: MX-18 beta 1 feedback
Posted: Sun Dec 09, 2018 3:05 pm
by Stevo
Don't "=y" and "=m" both enable the feature? One just makes it part of the monolithic kernel and the other makes it a loadable module.
Re: MX-18 beta 1 feedback
Posted: Sun Dec 09, 2018 3:10 pm
by dolphin_oracle
Stevo wrote: Sun Dec 09, 2018 3:05 pm
Don't "=y" and "=m" both enable the feature? One just makes it part of the monolithic kernel and the other makes it a loadable module.
honestly not sure, but the 64 bit has an "m" as well.
I've only tried 2, but I can't make a 32 bit encrypted usb with a 4.19 kernel, yet.
building a 64 bit encrypted usb seems to work fine with our kernel (confirming richb's post)
Re: MX-18 beta 1 feedback
Posted: Sun Dec 09, 2018 3:27 pm
by mystic
MX-LSD conky disappears when I click anywhere on the desktop
Re: MX-18 beta 1 feedback
Posted: Sun Dec 09, 2018 4:33 pm
by dolphin_oracle
dolphin_oracle wrote: Sun Dec 09, 2018 3:10 pm
Stevo wrote: Sun Dec 09, 2018 3:05 pm
Don't "=y" and "=m" both enable the feature? One just makes it part of the monolithic kernel and the other makes it a loadable module.
honestly not sure, but the 64 bit has an "m" as well.
I've only tried 2, but I can't make a 32 bit encrypted usb with a 4.19 kernel, yet.
building a 64 bit encrypted usb seems to work fine with our kernel (confirming richb's post)
same story with the 4.18 kernel. 32 bit kernel from alpha 1
Re: MX-18 beta 1 feedback
Posted: Sun Dec 09, 2018 4:43 pm
by anticapitalista
dolphin_oracle wrote: Sun Dec 09, 2018 4:33 pm
dolphin_oracle wrote: Sun Dec 09, 2018 3:10 pm
Stevo wrote: Sun Dec 09, 2018 3:05 pm
Don't "=y" and "=m" both enable the feature? One just makes it part of the monolithic kernel and the other makes it a loadable module.
honestly not sure, but the 64 bit has an "m" as well.
I've only tried 2, but I can't make a 32 bit encrypted usb with a 4.19 kernel, yet.
building a 64 bit encrypted usb seems to work fine with our kernel (confirming richb's post)
same story with the 4.18 kernel. 32 bit kernel from alpha 1
same with antiX-4.19.7 kernel (on antiX).
I know the 4.9 antiX kernel does work.
Re: MX-18 beta 1 feedback
Posted: Sun Dec 09, 2018 4:51 pm
by fehlix
mystic wrote: Sun Dec 09, 2018 3:27 pm
MX-LSD conky disappears when I click anywhere on the desktop
Open conky manager navigate to MX-LSD,
click on the pencil-icon to edit and replace/change this line
to
save and stop/start the conky.
Re: MX-18 beta 1 feedback
Posted: Sun Dec 09, 2018 5:17 pm
by dolphin_oracle
anticapitalista wrote: Sun Dec 09, 2018 4:43 pm
dolphin_oracle wrote: Sun Dec 09, 2018 4:33 pm
dolphin_oracle wrote: Sun Dec 09, 2018 3:10 pm
honestly not sure, but the 64 bit has an "m" as well.
I've only tried 2, but I can't make a 32 bit encrypted usb with a 4.19 kernel, yet.
building a 64 bit encrypted usb seems to work fine with our kernel (confirming richb's post)
same story with the 4.18 kernel. 32 bit kernel from alpha 1
same with antiX-4.19.7 kernel (on antiX).
I know the 4.9 antiX kernel does work.
ok, got some successs.
we need to add "xts" to the copy_initrd_modules in build-iso, and I assume snapshot as well. I just booted up a default mx18b1 32bit iso this way.
Code: Select all
CRYPT_LIST="
aes
blowfish
dm-crypt
dm-mod
serpent
sha256
xts
"
Re: MX-18 beta 1 feedback
Posted: Sun Dec 09, 2018 5:19 pm
by anticapitalista
dolphin_oracle wrote: Sun Dec 09, 2018 5:17 pm
ok, got some successs.
we need to add "xts" to the copy_initrd_modules in build-iso, and I assume snapshot as well. I just booted up a default mx18b1 32bit iso this way.
Code: Select all
CRYPT_LIST="
aes
blowfish
dm-crypt
dm-mod
serpent
sha256
xts
"
I thought the same. You beat me to it. I'll need to add it to cli-shell-utils as well.
Re: MX-18 beta 1 feedback
Posted: Sun Dec 09, 2018 5:24 pm
by dolphin_oracle
anticapitalista wrote: Sun Dec 09, 2018 5:19 pm
dolphin_oracle wrote: Sun Dec 09, 2018 5:17 pm
ok, got some successs.
we need to add "xts" to the copy_initrd_modules in build-iso, and I assume snapshot as well. I just booted up a default mx18b1 32bit iso this way.
Code: Select all
CRYPT_LIST="
aes
blowfish
dm-crypt
dm-mod
serpent
sha256
xts
"
I thought the same. You beat me to it. I'll need to add it to cli-shell-utils as well.
Your comment earlier about the kernel config parameter was the key
Re: MX-18 beta 1 feedback
Posted: Sun Dec 09, 2018 5:40 pm
by anticapitalista
Installed new version of cli-shell-utils with new copy_initrd_modules and successfully booted encrypted live usb
Re: MX-18 beta 1 feedback
Posted: Sun Dec 09, 2018 5:49 pm
by anticapitalista
BTW we have copy_initrd_modules and copy-initrd-programs in cli-shell-utils (usr/local/lib/cli-shell-utils/bin) which is a depencency of live-usb-maker so we don't need copy_initrd_modules and copy-initrd-programs in snapshot. But, that probably means some editing of the snapshot app since that app puts copy_initrd_modules and copy-initrd-programs in /usr/sbin
Re: MX-18 beta 1 feedback
Posted: Sun Dec 09, 2018 6:47 pm
by Adrian
anticapitalista wrote: Sun Dec 09, 2018 5:49 pm
BTW we have copy_initrd_modules and copy-initrd-programs in cli-shell-utils (usr/local/lib/cli-shell-utils/bin) which is a depencency of live-usb-maker so we don't need copy_initrd_modules and copy-initrd-programs in snapshot. But, that probably means some editing of the snapshot app since that app puts copy_initrd_modules and copy-initrd-programs in /usr/sbin
I can update those after a quick review (that's one reason MX Snapshot includes the scripts by itself to give me an opportunity to review how the changes affect the tool), but I don't see the new cli-shell-utils in the repo yet.
Re: MX-18 beta 1 feedback
Posted: Sun Dec 09, 2018 7:13 pm
by Coastie
Is now maybe the time to reconsider locating the panel to the bottom of the screen. Might look less strange to to new comers to MX Linux.
Re: MX-18 beta 1 feedback
Posted: Sun Dec 09, 2018 7:30 pm
by Gordon Cooper
Coastie wrote: Sun Dec 09, 2018 7:13 pm
Is now maybe the time to reconsider locating the panel to the bottom of the screen. Might look less strange to to new comers to MX Linux.
Definitely NOT as far I am concerned. It easy to move for those with bottom preference, but not me.
Re: MX-18 beta 1 feedback
Posted: Sun Dec 09, 2018 7:37 pm
by Stevo
davemx wrote: Sun Dec 09, 2018 12:42 pm
I installed it last night, on Desktop only. I'm using it now. So far the stuff I've done so far works, but GIMP 2.10 clashes with data files needed for MyPaint (no such problem with 2.8 and I hate the grey scheme but none of that is the fault of this excellent distro). Hopefully I'll be able to push a few things and test them over the next few days.
Can report now: Printing and Scanning working perfectly
To revert GIMP interface theme:
https://www.daviesmediadesign.com/custo ... interface/
We have a tweaked version of MyPaint in the test repo that is compatible with GIMP 2.10, I'll ask Tim to move it to main.
You can switch back to the colorful icons for GIMP 2.10 somewhere in the settings, probably in Appearance or Interface. We should probably have that in a FAQ for MX 18.
Re: MX-18 beta 1 feedback
Posted: Sun Dec 09, 2018 7:41 pm
by Buck Fankers
Coastie wrote: Sun Dec 09, 2018 7:13 pm
Is now maybe the time to reconsider locating the panel to the bottom of the screen. Might look less strange to to new comers to MX
I disagree as new at MX. As a long term windows user I didn't like it at first, but after I learned explanation I decided to give it a try and I LOVE it now.
Maybe a suggestion, at install, one of msgs could be an explanation, why is panel on the side and another msg, how easy it is, to move it around.
Re: MX-18 beta 1 feedback
Posted: Sun Dec 09, 2018 7:48 pm
by Coastie
Easy for you and me but maybe not for newbies.
I know:
Re: MX-18 beta 1 feedback
Posted: Sun Dec 09, 2018 7:57 pm
by Jerry3904
How to move the Panel is now the top item in the FAQ list at the top of the new Welcome screen. If they will not bother to look at the FAQs, never mind the Manual, then we can't help them.
Re: MX-18 beta 1 feedback
Posted: Sun Dec 09, 2018 8:34 pm
by Adrian
Jerry3904 wrote: Sun Dec 09, 2018 7:57 pm
How to move the Panel is now the top item in the FAQ list at the top of the new Welcome screen. If they will not bother to look at the FAQs, never mind the Manual, then we can't help them.
Heck, it's probably better to filter out such users...
Re: MX-18 beta 1 feedback
Posted: Sun Dec 09, 2018 8:45 pm
by Richard
When they are ready, Linux is ready.
Re: MX-18 beta 1 feedback
Posted: Sun Dec 09, 2018 8:49 pm
by Buck Fankers
Adrian wrote: Sun Dec 09, 2018 8:34 pm
Jerry3904 wrote: Sun Dec 09, 2018 7:57 pm
How to move the Panel is now the top item in the FAQ list at the top of the new Welcome screen. If they will not bother to look at the FAQs, never mind the Manual, then we can't help them.
Heck, it's probably better to filter out such users...
LOL that's funny ;-)
Re: MX-18 beta 1 feedback
Posted: Sun Dec 09, 2018 9:24 pm
by Gordon Cooper
Maybe we are incorrect with the classification of newbies. To me, a newbie is a person who has zero or very little computer experience and therefore has formed no firm ideas about the placement of panels and other Linux norms.
Whereas, a person coming with experience with Macs, or the products of Redmond, could be classed as an immigrant ?
Re: MX-18 beta 1 feedback
Posted: Sun Dec 09, 2018 9:51 pm
by skidoo
Adrian wrote: Sun Dec 09, 2018 8:34 pm
Jerry3904 wrote: Sun Dec 09, 2018 7:57 pm
How to move the Panel is now the top item in the FAQ list at the top of the new Welcome screen. If they will not bother to look at the FAQs, never mind the Manual, then we can't help them.
Heck, it's probably better to filter out such users...
On the subject of "helping them", I advocate inclusion of the following during the build process
in order to prevent (assidentally) launching an elevated-permissions instance of the default web browser:
touch /root/.mozilla
ln /root/.mozilla /dev/null
FWIW, I sent the above as a pull request to antiX. It was merged & distributed. Then, without explanation, it was reverted a few months later.
Why it would EVER be desirable to launch a root-permissioned web browser?!?
n.b: Any reply citing the "Principle of least surprise" as the rationale for the status quo... yeah, that would be interpreted as a "cop-out".
Re: MX-18 beta 1 feedback
Posted: Sun Dec 09, 2018 10:16 pm
by dolphin_oracle
I would like to mention here that firefox no longer launches as root.
Re: MX-18 beta 1 feedback
Posted: Sun Dec 09, 2018 10:50 pm
by Mauser
I see it so many times from people who are new to MX Linux make the mistake of not opening MX Tools and Tweak when they install MX Linux. To help those strangers or reviewers of MX Linux it would be a good idea to put in big capital letters in the welcome box when the first time MX Linux is started "OPEN MX TOOLS AND TWEAK".
Re: MX-18 beta 1 feedback
Posted: Sun Dec 09, 2018 11:14 pm
by dreamer
Just want to post the freetype 2.8 TTF font rendering fix that I have referred to earlier. I haven't tested it myself, but there was a lot of complaints about font rendering with freetype 2.8. Some were fixed with 2.8.1. But it seems TTF defaults were changed permanently.
From this bug report (similar can be found for Debian, Arch etc - doesn't really matter):
https://bugs.launchpad.net/ubuntu/+sour ... ug/1722508
The solution to achieve freetype 2.6 TTF font rendering without downgrading seems to be found in post 36.
In german ubuntuusers forum there is an simpler solution without need to downgrade libfreetype.
https://forum.ubuntuusers.de/post/8914328/
Just add
FREETYPE_PROPERTIES="truetype:interpreter-version=35 cff:no-stem-darkening=1 autofitter:warping=1"
in /etc/environment and restart x-server or reboot.
The posts following this one confirm that this fixes this particular issue with freetype 2.8.1, for example:
Thanks for the tip! Defining the FREETYPE_PROPERTIES as you suggested in /etc/environment did indeed disable hinting and renders the same crisper fonts as was in earlier versions of Ubuntu. Personally, I still prefer to disable hinting in the source code but your suggestion works just as well.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 10, 2018 12:46 am
by vamsi
Content Deleted shifted to other thread
viewtopic.php?f=108&t=47288
Sorry for Noob question in this thread can LIVE USB MAKER can make windows / other linux ditributions bootable usb drives? If not possible is there any chance to include them and other problem is whenever i use linux commands to make bootable usb using gparted to format the usb drive makes it some time difficult i hope if there is any one app ( ONE CLICK PENDRIVE FORMAT AND ONE CLICK BOOTABLE USB MAKER) to care bot of these would be much helpful and make things easier for newbies
Re: MX-18 beta 1 feedback
Posted: Mon Dec 10, 2018 2:06 am
by Adrian
vamsi wrote: Mon Dec 10, 2018 12:46 am
Sorry for Noob question in this thread can LIVE USB MAKER can make windows / other linux ditributions bootable usb drives? If not possible is there any chance to include them and other problem is whenever i use linux commands to make bootable usb using gparted to format the usb drive makes it some time difficult i hope if there is any one app ( ONE CLICK PENDRIVE FORMAT AND ONE CLICK BOOTABLE USB MAKER) to care bot of these would be much helpful and make things easier for newbies
So if you are aware you ask in the wrong thread why do you do it? Do you think your question will be ignored if you ask in a separate thread? You can use the tool to create other USB that can be created with dd (basically all modern linux distros that have ISOs created with isohybrid) it cannot be used to create Windows bootable drives, for that you use Windows live maker tool, if you don't have access to Windows I think there are some ways to do it but it's beyond my interests and especially beyond of the scope of this thread.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 10, 2018 2:40 am
by ekeimaja
Now installing it in VBox in my laptop, and everything has worked fine. Could you now take Flash away from default installation, so users, who wants it, can install it manually.
Also there is a bug (or feature) in the installer, which I have discovered in MX 17 installer too. When defining created partitions for root, home and swap, and putting them encrypted gives error if not unencrypted boot partition has been defined, and continue button is then disabled even you fix the problem and only solution is to go back to previous step and then return.
EDIT: after installing when rebooting I got error: FATAL: keyboard error: 995. But when restarted the VM, booted normally.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 10, 2018 5:30 am
by skidoo
unexpected (by me) content present in the top-level directory:
------------------------------
/Build/ (26MB ~~ the content of build-iso)
/.fehbg
/.config
/.cache
dpkg -S /.fehbg
^---v
dpkg-query: no path found matching pattern /.fehbg
mx-snapshot-exclude.list
persist-save-exclude.list
live-remaster-exclude.list
---------- CONSIDER ADDING PATTERNS FOR THESE "EXPENSIVE" DIRS:
home/*/.cache/mozilla/firefox/*/thumbnails/*
home/*/.thumbnails/*
mx-snapshot-exclude.list (AND/OR other lists)
home/*/.mozilla/firefox/*/Cache/*
^-------- must now be home/*/.mozilla/firefox/*/cache2/*
persist-save-exclude.list
---------- ? hmm, should contents of trash be preserved across live sessions? (tough question)
---------- perhaps persist-save script should test/warn if trash content exceeds some threshhold ?
home/*/.Trash*
home/*/.local/share/Trash/*
live-remaster-exclude.list
---------- ? should "cache2", "trash", and "...thumbnails/*" be added to this list also?
________________
noticed in ~/.xsession-errors:
"(xfce4-session:9933): xfce4-session-WARNING **: 23:01:10.553: xfsm_manager_load_session: Something wrong with
/home/demo/.cache/sessions/xfce4-session-mx1:0, Does it exist? Permissions issue?"
-=-
"cat: /home/demo/.config/mx-sounds/startupsound.conf: No such file or directory"
-=-
"(clipit:9989): GLib-GObject-WARNING **: 23:01:11.029: ../../../../gobject/gsignal.c:2523: signal 'child-added' is
invalid for instance '0x55dbef624130' of type 'GtkMenu' "
-=-
"No window manager registered on screen 0. To start the xfdesktop without this check, run with --disable-wm-check."
-=-
"conky: Syntax error (/home/demo/.conky/MX-Default/Hermoso_sys_mx171:1: '=' expected near 'no') while reading config file."
noticed in /var/log/user.log:
" [pulseaudio] authkey.c: Failed to open cookie file '/home/demo/.pulse-cookie': No such file or directory"
" [pulseaudio] authkey.c: Failed to load authentication key '/home/demo/.config/pulse "
---------------^ aha, matches the unexpected top-level dir content
noticed in /var/log/live/make-fstab.log:
(idunno the expected result)
Code: Select all
Create new /etc/fstab
Put 1 hard drive entry into /etc/fstab
Exit: Swap only
Exit: add /dev/sdc: no filesystem uuid
Exit: add /dev/sda: no filesystem uuid
Exit: add /dev/sdb: no filesystem uuid
Exit: no fstab.hotplug file
Exit: no fstab.hotplug file
Exit: add /dev/sdc3: no filesystem uuid
Exit: no fstab.hotplug file
Exit: no fstab.hotplug file
Exit: no fstab.hotplug file
Exit: no fstab.hotplug file
Exit: no fstab.hotplug file
Exit: no fstab.hotplug file
Exit: no fstab.hotplug file
Exit: add /dev/sdd: no filesystem uuid
Exit: no fstab.hotplug file
noticed in /var/log/boot: CUPS is autostarted, yet saned is disabled (if that's the desired default, okay)
noticed in /var/log/dmesg:
"usb_common: module verification failed: signature and/or required key missing - tainting kernel"
Re: MX-18 beta 1 feedback
Posted: Mon Dec 10, 2018 6:50 am
by Jerry3904
Could you now take Flash away from default installation, so users, who wants it, can install it manually.
Sorry, that's not the way we operate. Please take a look at the Users Manual Section 1.7.2 on non-free software. Fundamental point:
MX Linux is fundamentally user-oriented, so includes a certain amount of non-free software to assure that the system works out of the box as much as possible.
Flash is easily uninstalled using the Package Installer.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 10, 2018 7:43 am
by mg979
Hello, I have a question. MX 18 recognizes the wifi of my laptop, whereas MX 17.1 can't. If I install MX 18 on the hard drive, will I have to reinstall the stable release? Or will it be 'promoted' thorough updates? Thanks
Re: MX-18 beta 1 feedback
Posted: Mon Dec 10, 2018 7:54 am
by Jerry3904
mg979 wrote: Mon Dec 10, 2018 7:43 am
Hello, I have a question. MX 18 recognizes the wifi of my laptop, whereas MX 17.1 can't. If I install MX 18 on the hard drive, will I have to reinstall the stable release? Or will it be 'promoted' thorough updates? Thanks
I'm not understanding the question, sorry. In general: MX-18 will be the stable release, and there will be no reason to install any earlier version along with that.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 10, 2018 7:56 am
by dolphin_oracle
mg979 wrote: Mon Dec 10, 2018 7:43 am
Hello, I have a question. MX 18 recognizes the wifi of my laptop, whereas MX 17.1 can't. If I install MX 18 on the hard drive, will I have to reinstall the stable release? Or will it be 'promoted' thorough updates? Thanks
We support upgrades from the Release Candidate (RC) stage forward. a beta iso will receive updates, but it will always identify itself as a beta. There are a few items that cannot be fixed via update that will be fixed on the RC iso (soon to come).
Re: MX-18 beta 1 feedback
Posted: Mon Dec 10, 2018 8:01 am
by mg979
Thanks to both of you. I asked because right now it's the only way I can have Linux with wifi on my laptop, not even Ubuntu works. When will the stable release or the RC be available, approximatively? I guess I'll have to wait for that one. Thanks
Re: MX-18 beta 1 feedback
Posted: Mon Dec 10, 2018 8:01 am
by asqwerth
Jerry3904 wrote: Mon Dec 10, 2018 7:54 am
mg979 wrote: Mon Dec 10, 2018 7:43 am
Hello, I have a question. MX 18 recognizes the wifi of my laptop, whereas MX 17.1 can't. If I install MX 18 on the hard drive, will I have to reinstall the stable release? Or will it be 'promoted' thorough updates? Thanks
I'm not understanding the question, sorry. In general: MX-18 will be the stable release, and there will be no reason to install any earlier version along with that.
Maybe wifi works in MX18 because of the new kernel. If you keep MX17, a full update will pull in all the updated packages when everything is ready, BUT you still have to manually install the new
kernel. If that enables your wifi to work, fine. Why don't you try that first when the new kernel is officially added to the MX17/18 repo upon official release?
If that still doesn't work, you can install MX18 fresh, but in the installer, choose the "preserve /home partition" option. That will save the settings of your current MX17 install.
Note that MX18 will also be a stable release, based on the same Debian base, once officially released. So all the packages will be part of the MX17 repo anyway.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 10, 2018 8:02 am
by vamsi
Adrian wrote: Mon Dec 10, 2018 2:06 am
vamsi wrote: Mon Dec 10, 2018 12:46 am
Sorry for Noob question in this thread can LIVE USB MAKER can make windows / other linux ditributions bootable usb drives? If not possible is there any chance to include them and other problem is whenever i use linux commands to make bootable usb using gparted to format the usb drive makes it some time difficult i hope if there is any one app ( ONE CLICK PENDRIVE FORMAT AND ONE CLICK BOOTABLE USB MAKER) to care bot of these would be much helpful and make things easier for newbies
So if you are aware you ask in the wrong thread why do you do it? Do you think your question will be ignored if you ask in a separate thread? You can use the tool to create other USB that can be created with dd (basically all modern linux distros that have ISOs created with isohybrid) it cannot be used to create Windows bootable drives, for that you use Windows live maker tool, if you don't have access to Windows I think there are some ways to do it but it's beyond my interests and especially beyond of the scope of this thread.
Sorry for hijacking thread shifted the content to other thread.
Thanks
Re: MX-18 beta 1 feedback
Posted: Mon Dec 10, 2018 8:36 am
by mg979
asqwerth wrote: Mon Dec 10, 2018 8:01 am
Jerry3904 wrote: Mon Dec 10, 2018 7:54 am
mg979 wrote: Mon Dec 10, 2018 7:43 am
Hello, I have a question. MX 18 recognizes the wifi of my laptop, whereas MX 17.1 can't. If I install MX 18 on the hard drive, will I have to reinstall the stable release? Or will it be 'promoted' thorough updates? Thanks
I'm not understanding the question, sorry. In general: MX-18 will be the stable release, and there will be no reason to install any earlier version along with that.
Maybe wifi works in MX18 because of the new kernel. If you keep MX17, a full update will pull in all the updated packages when everything is ready, BUT you still have to manually install the new
kernel. If that enables your wifi to work, fine. Why don't you try that first when the new kernel is officially added to the MX17/18 repo upon official release?
If that still doesn't work, you can install MX18 fresh, but in the installer, choose the "preserve /home partition" option. That will save the settings of your current MX17 install.
Note that MX18 will also be a stable release, based on the same Debian base, once officially released. So all the packages will be part of the MX17 repo anyway.
Thanks. I just don't have Linux installed on this laptop, so I don't need to upgrade MX 17, it will be a fresh install anyway. I'll try to install the beta, then install the stable, preserving home as you said.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 10, 2018 10:37 am
by manyroads
Hello all.
I didn't see this noted elsewhere but the User Manual needs to update version references from MX 17 to MX 18. I know it's a nit. :lipsrsealed:
Re: MX-18 beta 1 feedback
Posted: Mon Dec 10, 2018 10:43 am
by Jerry3904
Nope, it just hadn't been updated yet, though a new (draft only) version is in the pipes now. We wait until the RC is ready, otherwise there are too many changes that have to be made all over again.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 10, 2018 12:43 pm
by Buck Fankers
Mauser wrote: Sun Dec 09, 2018 10:50 pm
I see it so many times from people who are new to MX Linux make the mistake of not opening MX Tools and Tweak when they install MX Linux. To help those strangers or reviewers of MX Linux it would be a good idea to put in big capital letters in the welcome box when the first time MX Linux is started "OPEN MX TOOLS AND TWEAK".
Agree
Re: MX-18 beta 1 feedback
Posted: Mon Dec 10, 2018 1:05 pm
by Adrian
We don't want to shout at people, those are listed in MX Welcome and in manual, if one cannot find those easy options then it's pretty much a lost cause. It might affect some superficial reviewers but I'm not that concerned that our users will miss that if they do minimum due diligence.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 10, 2018 1:23 pm
by Richard
Maybe post a note for reviewers:
"Please read the Quik-start guide before installing.
The [MX Welcome page] contains useful tools for users.
The MX User Manual is [here]."
Or something to that effect.
Granted, "You can lead a horse to water, but you can't make him drink."
Re: MX-18 beta 1 feedback
Posted: Mon Dec 10, 2018 2:20 pm
by Stevo
mg979 wrote: Mon Dec 10, 2018 8:01 am
Thanks to both of you. I asked because right now it's the only way I can have Linux with wifi on my laptop, not even Ubuntu works. When will the stable release or the RC be available, approximatively? I guess I'll have to wait for that one. Thanks
No doubt it's the newer kernel and firmware that gets the wi-fi working, but you can also add those to MX 17 to get it working there. Just see the thread about the test upgrade from MX 17 to MX 18.
What does "inxi -N" say about your wi-fi in MX 18, by the way?
Re: MX-18 beta 1 feedback
Posted: Mon Dec 10, 2018 3:24 pm
by balarm
Impossible to install "Mate desktop and wine" via MxPI into a live-Usb Mx18.
I get: there are not satisfied dependencies. Some packages are damaged.
I control via synaptic filter damaged, but there aren't any.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 10, 2018 3:33 pm
by fehlix
balarm wrote: Mon Dec 10, 2018 3:24 pm
Impossible to install "Mate desktop and wine" via MxPI into a live-Usb Mx18.
I get: there are not satisfied dependencies. Some packages are damaged.
I control via synaptic filter damaged, but there aren't any.
I have succefully installed wine with MXPI-> popular apps.
Which one you are referring to? in MXPI: PopularApps, Stable, Test Repo, Debian backports
Re: MX-18 beta 1 feedback
Posted: Mon Dec 10, 2018 3:43 pm
by timkb4cq
I just installed Mate and Wine into my MX-17.1 upgraded to MX-18.
The problem you are having may be because Mate has to pull in some packages from the MX18/dev repository for each of those installs, and I believe that repo is disabled on the MX-18b1 LiveUSB. Those packages will be moved to main in a day or two and the problem will be solved.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 10, 2018 3:52 pm
by balarm
Hi, @fehlix: I meant popular apps for both; I'll wait some days when packages move to main.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 10, 2018 4:37 pm
by pemartins
I do not have the chance right now to load MX 18 to test this and I apologize if it's already done but is it possible to create the keyboard shortcut XF86Calculator for Galculator?
At least in MX 17 it does not exist by default.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 10, 2018 4:38 pm
by baldyeti
A minor oddity i noticed in 18b1: the firefox about box mentions MX-Linux 1.0 (?!?)
Re: MX-18 beta 1 feedback
Posted: Mon Dec 10, 2018 6:49 pm
by Stevo
baldyeti wrote: Mon Dec 10, 2018 4:38 pm
A minor oddity i noticed in 18b1: the firefox about box mentions MX-Linux 1.0 (?!?)
Not just in the Beta, for any current version of MX: 16, 17, etc. It's a quirk of the distribution.ini file we add.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 10, 2018 9:20 pm
by entropyfoe
Paul, caprea, and namida,
THis Ryzen is rocking with this MX18 beta1 now.
Over two days uptime, mostly idling (which causes the crash) still solid.
I will leave the rcu_nocbs for now, but when the RC comes, I will ommit the grub line.
So the key is a newer BIOS, for me 4024, that has a new option in the advanced tab, Power Supply Idle Control, and this is set from the Auto to "Typical Current Idle".
Many report on the AMD boards that this is a fix, though a minority ( a few) still have the problem. One key issue was you should reboot from cold after changing the parameter in the BIOS. In any case is is a long way from 143 days uptime on MX 17 using an antix 4.15 kernel and the rcu_nocbs fix, but this looks good.
Re: MX-18 beta 1 feedback
Posted: Tue Dec 11, 2018 3:38 am
by baldyeti
Sorry to repeat myself, but i have not seen
this problem acknowledged - on my mbr-partitioned 18b1 HDD install, there was initially no entry for windows in grub.cfg. A subsequent update-grub fixed this, but still. Is nobody else seeing this behaviour ?
Re: MX-18 beta 1 feedback
Posted: Tue Dec 11, 2018 3:45 am
by Eadwine Rose
When I installed MX18b1 on my new harddrive it put an entry in grub for Windows, right on the bottom, so nope.. not seeing the behavior here.
Re: MX-18 beta 1 feedback
Posted: Tue Dec 11, 2018 4:57 am
by baldyeti
Thanks Rose. I seem to recall somebody mentioning that same issue with MX17 in the past, but cannot find back that thread.
Later tonight i'll add some details about this particular system, although it seems rather standard to me.
Re: MX-18 beta 1 feedback
Posted: Tue Dec 11, 2018 6:15 am
by dolphin_oracle
baldyeti wrote: Tue Dec 11, 2018 4:57 am
Thanks Rose. I seem to recall somebody mentioning that same issue with MX17 in the past, but cannot find back that thread.
Later tonight i'll add some details about this particular system, although it seems rather standard to me.
It can happen. I haven't found a fix but a workaround is to run update-grub after install and first boot.
Re: MX-18 beta 1 feedback
Posted: Tue Dec 11, 2018 6:31 am
by Richard
I think it is a quirk in update-grub.
Was told several years ago,
that if the first run fails, run again.
Some run it twice, just in case.
Never heard a reason why?
Perhaps a late change in permissions?
Re: MX-18 beta 1 feedback
Posted: Tue Dec 11, 2018 6:53 am
by baldyeti
I am aware of the work-around, just concerned of the fit it might give a newbie to reboot to a startup menu that does not include the other OS.
No idea how often this occurs; perhaps the installer could run upgrade-grub a 2nd time (unconditionally would make it slower for everyone I guess, so perhaps if there is a bootable MS-type partition yet no "windows" entry in the 1st grub.cfg ?)
Re: MX-18 beta 1 feedback
Posted: Tue Dec 11, 2018 6:56 am
by dolphin_oracle
We do runs update-grub, but there seem to be some key differences when running inside the chroot environment the installer sets up.
Not picking up windows is one. Another is not using uuids for the root partition designation on grub.cfg.
Re: MX-18 beta 1 feedback
Posted: Tue Dec 11, 2018 6:57 am
by chrispop99
Is xscreensaver going to be available in the Package Installer for Final?
At the moment, if using MX-18 testrepo, it appears and installs from the PI, but neither of the extra screensavers install, failing with an 'Unable to locate package' error.
Chris
Re: MX-18 beta 1 feedback
Posted: Tue Dec 11, 2018 7:03 am
by baldyeti
dolphin_oracle wrote: Tue Dec 11, 2018 6:56 amWe do runs update-grub, but there seem to be some key differences when running inside the chroot environment the installer sets up.
Alright, i doubt indeed that re-running update-grub in the same (installer) environment would yield a different result. The fix probably comes from running it from the rebooted, non-chrooted system. I see this is covered in the fine manual (2.6.1 - No operating system found)
Re: MX-18 beta 1 feedback
Posted: Tue Dec 11, 2018 9:58 am
by manyroads
Hello all... I believe the problem described in this thread may be an MX18 beta bug with the snapshot creation function:
viewtopic.php?f=92&t=47305
Re: MX-18 beta 1 feedback
Posted: Tue Dec 11, 2018 12:33 pm
by darth.severus
Hi, I need to decide what to install. Has it any disadvantages to install MX-17.1 instead waiting for MX-18. Since there is no new Debian.
Also, can someone who tested MX-18 beta as a new install please point out how the system encryption per installer is working now. Will boot be encrypted?
Re: MX-18 beta 1 feedback
Posted: Tue Dec 11, 2018 12:35 pm
by dolphin_oracle
darth.severus wrote: Tue Dec 11, 2018 12:33 pm
Hi, I need to decide what to install. Has it any disadvantages to install MX-17.1 instead waiting for MX-18. Since there is no new Debian.
Also, can someone who tested MX-18 beta as a new install please point out how the system encryption per installer is working now. Will boot be encrypted?
boot is not encrypted. at this time we require an unencrypted boot partition.
Re: MX-18 beta 1 feedback
Posted: Tue Dec 11, 2018 12:43 pm
by Adrian
darth.severus wrote: Tue Dec 11, 2018 12:33 pm
Hi, I need to decide what to install. Has it any disadvantages to install MX-17.1 instead waiting for MX-18. Since there is no new Debian.
Also, can someone who tested MX-18 beta as a new install please point out how the system encryption per installer is working now. Will boot be encrypted?
No problems, I do recommend updating at least the installer before you install to get the latest fixes (including the ability to install on encrypted partitions)
/boot will not be encrypted either with MX17 or MX18. In our view there's no security info available there and if somebody has access to your computer to change stuff on /boot then you have bigger problems than encryption. I've heard that GRUB should be able to boot from encrypted /boot, I could not make it work in my tests.
Re: MX-18 beta 1 feedback
Posted: Tue Dec 11, 2018 12:45 pm
by richb
dolphin_oracle wrote: Tue Dec 11, 2018 12:35 pm
darth.severus wrote: Tue Dec 11, 2018 12:33 pm
Hi, I need to decide what to install. Has it any disadvantages to install MX-17.1 instead waiting for MX-18. Since there is no new Debian.
Also, can someone who tested MX-18 beta as a new install please point out how the system encryption per installer is working now. Will boot be encrypted?
I had no problem installing with encryption MX 18 b1 64 bit. (less the /boot partition as do indicated.)
Re: MX-18 beta 1 feedback
Posted: Tue Dec 11, 2018 11:10 pm
by Hierax_ca
Thinkpad 600x (1999-2001)
Display Color and Audio Sound issues persist (started with antix-17 and mx-17, works properly with MX-14.4 and 16.1):
Color Problem:
-
colors display as inverted/opposite -- e.g., yellow=purple, blue=green. Note: this problem doesn't happen in AntiX-core cli console interface, issue occurs only with xorg running.
$ inxi -Gxxx
Code: Select all
Graphics:
Device-1: Neomagic NM2360 [MagicMedia 256ZX] vendor: IBM ThinkPad 600X
driver: N/A bus ID: 01:00.0 chip ID: 10c8:0006
Display: x11 server: X.Org 1.19.2 driver: vesa resolution: 1024x768~61Hz
OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.3 Mesa 18.2.6 compat-v: 3.1
direct render: Yes
Color Solution:
- sudo nano on /etc/X11/xorg.conf
- changed color depth to 16-bit by adding last line: "DefaultDepth 16"
Is there a way to have the color depth detected on install and change this automatically or semi-manually with an Fn button option in the Live boot or installer? Or some MX tool for low color resolution? Or something to get color displaying properly on ancient computers like this? Was whatever that did this before (with MX-14.4 and -16.1) removed?
Sound Problem:
- MX Select Sound: "
No sound cards/devices were found"
Before Fix
$ inxi -Axxx
Code: Select all
Audio:
Device-1: Cirrus Logic CS 4614/22/24/30 [CrystalClear SoundFusion Audio
Accelerator]
vendor: IBM ThinkPad 600X/A20m driver: N/A bus ID: 00:06.0 chip ID: 1013:6003
Sound Server: ALSA v: k4.19.0-1-686-pae
Sound Solution (manual):
- download latest old firmware:
ftp://ftp.alsa-project.org/pub/firmware ... 29.tar.bz2 (2015-02-20)
- right click in Thunar extract here
- copy cs46xx folder
- open Root Thunar
- paste to /lib/firmware/
- open terminal "sudo modprobe -r snd-cs46xx" then "sudo modprobe snd-cs46xx"
Could this cs46xx firmware be included in the 32-bit .iso (or an MX tool created that could extract and paste the needed driver)? There are also numerous other old sound cards here in the file that might help other people with really old laptops.
After Fix:
$ inxi -Axxx
Code: Select all
Audio:
Device-1: Cirrus Logic CS 4614/22/24/30 [CrystalClear SoundFusion Audio
Accelerator]
vendor: IBM ThinkPad 600X/A20m driver: snd_cs46xx v: kernel bus ID: 00:06.0
chip ID: 1013:6003
Sound Server: ALSA v: k4.19.0-1-686-pae
Full inxi
sudo inxi -v8 -z
Code: Select all
System: Host: mx1 Kernel: 4.19.0-1-686-pae i686 bits: 32 compiler: gcc v: 6.3.0 Desktop: Xfce 4.12.3
tk: Gtk 2.24.31 info: xfce4-panel wm: xfwm4 dm: LightDM 1.18.3
Distro: MX-18b1_386 Continuum December 3 2018 base: Debian GNU/Linux 9 (stretch)
Machine: Type: Laptop System: IBM product: 26468EU v: N/A serial: <filter> Chassis: type: 10
serial: N/A
Mobo: IBM model: 26468EU serial: <filter> BIOS: IBM v: ITET55WW date: 11/30/1999
Battery: ID-1: BAT0 charge: 43.3 Wh condition: 45.4/45.4 Wh (100%) volts: 11.8/10.8
model: IBM Corporation ThinkPad Battery type: Li-ion serial: N/A status: Unknown
Memory: RAM: total: 494.6 MiB used: 234.3 MiB (47.4%)
Array-1: capacity: 768 MiB note: est. slots: 3 EC: None max module size: 256 MiB
Device-1: DIMM 0 size: 64 MiB info: single-bank speed: type: Other detail: synchronous
bus width: 64 bits total: 64 bits manufacturer: N/A part-no: N/A serial: N/A
Device-2: DIMM 1 size: 256 MiB info: double-bank speed: type: Other detail: synchronous
bus width: 64 bits total: 64 bits manufacturer: N/A part-no: N/A serial: N/A
Device-3: DIMM 2 size: 256 MiB info: double-bank speed: type: Other detail: synchronous
bus width: 64 bits total: 64 bits manufacturer: N/A part-no: N/A serial: N/A
PCI Slots: Slot: Adapter 0, Socket 0 type: 32-bit PC Card (PCMCIA) CardBus Slot 1 status: Available
length: Other
Slot: Adapter 0, Socket 1 type: 32-bit PC Card (PCMCIA) CardBus Slot 2 status: Available
length: Other
CPU: Topology: Single Core model: Pentium III (Coppermine) bits: 32 type: MCP
arch: P6 III Coppermine family: 6 model-id: 8 stepping: 6 microcode: 9 L1 cache: 32 KiB
L2 cache: 256 KiB bogomips: 1694
Speed: 850 MHz min/max: 700/850 MHz Core speed (MHz): 1: 850
Flags: cmov cpuid cx8 de fpu fxsr mca mce mmx msr mtrr pae pge pse pse36 pti sep sse tsc vme
Vulnerabilities: Type: l1tf mitigation: PTE Inversion
Type: meltdown mitigation: PTI
Type: spec_store_bypass status: Vulnerable
Type: spectre_v1 mitigation: __user pointer sanitization
Type: spectre_v2 mitigation: Full generic retpoline
Graphics: Device-1: Neomagic NM2360 [MagicMedia 256ZX] vendor: IBM ThinkPad 600X driver: N/A
bus ID: 01:00.0 chip ID: 10c8:0006
Display: server: X.Org 1.19.2 driver: vesa resolution: 1024x768~61Hz
OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.3 Mesa 18.2.6 compat-v: 3.1
direct render: Yes
Audio: Device-1: Cirrus Logic CS 4614/22/24/30 [CrystalClear SoundFusion Audio Accelerator]
vendor: IBM ThinkPad 600X/A20m driver: N/A bus ID: 00:06.0 chip ID: 1013:6003
Sound Server: ALSA v: k4.19.0-1-686-pae
Network: Device-1: Intel 82371AB/EB/MB PIIX4 ISA type: network bridge driver: N/A port: 4400
bus ID: 00:07.0 chip ID: 8086:7110
Device-2: Intel 82371AB/EB/MB PIIX4 ACPI type: network bridge driver: N/A port: 4000
bus ID: 00:07.3 chip ID: 8086:7113
Device-3: Ralink RT2800 802.11n PCI driver: rt2800pci v: 2.3.0 port: 4000 bus ID: 06:00.0
chip ID: 1814:0601
IF: wlan0 state: down mac: <filter>
WAN IP: No WAN IP data found. Connected to the web? SSL issues?
Drives: Local Storage: total: 119.24 GiB used: 35.7 MiB (0.0%)
ID-1: /dev/sda vendor: Crucial model: CT128M550SSD3 size: 119.24 GiB block size:
physical: 4096 B logical: 512 B speed: <unknown> serial: <filter> rev: MU01 temp: 43 C
scheme: MBR
Floppy-1: /dev/fd0
Optical-1: /dev/sr0 vendor: TOSHIBA model: DVD-ROM SD-C2612 rev: 1011 dev-links: cdrom,dvd
Features: speed: 24 multisession: yes audio: yes dvd: yes rw: none state: running
RAID: Message: No RAID data was found.
Partition: ID-1: / raw size: N/A size: 374.0 MiB used: 19.7 MiB (5.3%) fs: overlay dev: ERR-102
label: N/A uuid: N/A
ID-2: /live/boot-dev raw size: 1.29 GiB size: 1.29 GiB (99.94%) used: 1.29 GiB (100.0%)
fs: iso9660 block size: 2048 B dev: /dev/sr0 label: antiXlive uuid: 2018-12-03-02-22-49-00
ID-3: swap-1 size: 2.05 GiB used: 16.0 MiB (0.8%) fs: swap swappiness: 60 (default)
cache pressure: 100 (default) dev: /dev/sda2 label: N/A
uuid: e1d91df4-8549-41c8-9868-b42919b504c1
Unmounted: ID-1: /dev/sda1 size: 117.20 GiB fs: ext4 label: N/A
uuid: 5c84ae89-d35e-46b9-bb10-905c61f3f9b9
USB: Hub: 1-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s chip ID: 1d6b:0001
Sensors: Message: No sensors data was found. Is sensors configured?
Repos: Active apt repos in: /etc/apt/sources.list.d/antix.list
1: deb http://iso.mxrepo.com/antix/stretch stretch main
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://ftp.us.debian.org/debian/ stretch-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://ftp.us.debian.org/debian/ stretch main contrib non-free
2: deb http://security.debian.org/ stretch/updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://mxrepo.com/mx/repo/ stretch main non-free
No active apt repos in: /etc/apt/sources.list.d/various.list
Processes: CPU top: 5
1: cpu: 15.5% command: sudo pid: 4482 mem: 4.97 MiB (1.0%)
2: cpu: 6.9% command: xfce4-terminal pid: 4417 mem: 30.8 MiB (6.2%)
3: cpu: 6.1% command: libwhiskermenu.so started by: wrapper-1.0 pid: 4108 mem: 26.4 MiB (5.3%)
4: cpu: 5.2% command: xfwm4 pid: 3972 mem: 18.0 MiB (3.6%)
5: cpu: 5.1% command: xfsettingsd pid: 4052 mem: 15.8 MiB (3.2%)
Memory top: 5
1: mem: 61.2 MiB (12.3%) command: apt-notifier.py started by: python pid: 4082 cpu: 3.9%
2: mem: 31.0 MiB (6.2%) command: xorg pid: 3536 cpu: 4.2%
3: mem: 30.8 MiB (6.2%) command: xfce4-terminal pid: 4417 cpu: 6.9%
4: mem: 29.7 MiB (5.9%) command: nm-applet pid: 4024 cpu: 3.5%
5: mem: 27.9 MiB (5.6%) command: yad pid: 4029 cpu: 3.2%
Info: Processes: 152 Uptime: 10m Init: SysVinit v: 2.88 runlevel: 5 default: 5 Compilers: gcc: 6.3.0
alt: 6 Shell: bash (sudo) v: 4.4.12 running in: xfce4-terminal inxi: 3.0.25
Re: MX-18 beta 1 feedback
Posted: Tue Dec 11, 2018 11:14 pm
by Hierax_ca
Thinkpad A31p (2002-2003):
Works fine!
sudo inxi -v8 -z
Code: Select all
System: Host: Thinkpad-A31p-Linux-MX18b1 Kernel: 4.19.0-1-686-pae i686 bits: 32 compiler: gcc v: 6.3.0
Desktop: Xfce 4.12.3 tk: Gtk 2.24.31 info: xfce4-panel wm: xfwm4 dm: LightDM 1.18.3
Distro: MX-18b1_386 Continuum December 3 2018 base: Debian GNU/Linux 9 (stretch)
Machine: Type: Laptop System: IBM product: 2653R4U v: N/A serial: <filter> Chassis: type: 10 serial: N/A
Mobo: IBM model: 2653R4U serial: <filter> BIOS: IBM v: 1NET16WW (1.10 ) date: 10/19/2006
Battery: ID-1: BAT0 charge: 45.7 Wh condition: 45.7/47.5 Wh (96%) volts: 12.4/10.8
model: SANYO IBM-COMPATIBLE type: Li-ion serial: <filter> status: Full
ID-2: BAT1 charge: 17.9 Wh condition: 18.7/38.9 Wh (48%) volts: 12.4/10.8
model: SANYO IBM-02K6817 type: Li-ion serial: <filter> status: Unknown
Memory: RAM: total: 1.91 GiB used: 301.3 MiB (15.4%)
Array-1: capacity: 2 GiB note: est. slots: 2 EC: None max module size: 1 GiB note: est.
Device-1: DIMM 1 size: 1 GiB info: double-bank speed: Unknown type: SDRAM detail: synchronous
bus width: 64 bits total: 64 bits manufacturer: N/A part-no: Not Specified serial: <filter>
Device-2: DIMM 2 size: 1 GiB info: double-bank speed: Unknown type: SDRAM detail: synchronous
bus width: 64 bits total: 64 bits manufacturer: N/A part-no: Not Specified serial: <filter>
PCI Slots: Slot: Adapter 0, Socket 0 type: 32-bit PC Card (PCMCIA) CardBus Slot 1 status: Available
length: Other
Slot: Adapter 1, Socket 0 type: 32-bit PC Card (PCMCIA) CardBus Slot 2 status: Available
length: Other
Slot: 1 type: 32-bit PCI Mini-PCI Slot 1 status: Available length: Other
CPU: Topology: Single Core model: Mobile Intel Pentium 4 - M bits: 32 type: MCP
arch: Netburst Northwood family: F (15) model-id: 2 stepping: 7 microcode: 39 L1 cache: 8 KiB
L2 cache: 512 KiB bogomips: 2397
Speed: 1200 MHz min/max: 1200/2000 MHz Core speed (MHz): 1: 1200
Flags: acpi bts cid clflush cmov cpuid cx8 de dts fpu fxsr ht mca mce mmx msr mtrr pae pat pbe
pebs pge pse pse36 pti sep ss sse sse2 tm tsc vme xtpr
Vulnerabilities: Type: l1tf mitigation: PTE Inversion
Type: meltdown mitigation: PTI
Type: spec_store_bypass status: Vulnerable
Type: spectre_v1 mitigation: __user pointer sanitization
Type: spectre_v2 mitigation: Full generic retpoline
Graphics: Device-1: Advanced Micro Devices [AMD/ATI] RV200/M7 GL [Mobility FireGL 7800] vendor: IBM
driver: radeon v: kernel bus ID: 01:00.0 chip ID: 1002:4c58
Display: server: X.Org 1.19.2 driver: ati,radeon unloaded: fbdev,modesetting,vesa
resolution: 1600x1200~60Hz
OpenGL: renderer: Mesa DRI R100 (RV200 4C58) x86/MMX/SSE2 DRI2 v: 1.3 Mesa 18.2.6
direct render: Yes
Audio: Device-1: Intel 82801CA/CAM AC97 Audio vendor: IBM ThinkPad T30 driver: snd_intel8x0 v: kernel
bus ID: 00:1f.5 chip ID: 8086:2485
Sound Server: ALSA v: k4.19.0-1-686-pae
Network: Device-1: Intel PRO/Wireless 2200BG [Calexico2] Network driver: ipw2200 v: 1.2.2kmprq port: 3000
bus ID: 02:02.0 chip ID: 8086:4220
IF: eth1 state: down mac: <filter>
Device-2: Intel 82801CAM PRO/100 VE Ethernet vendor: IBM ThinkPad A/T/X Series driver: e100
v: 3.5.24-k2-NAPI port: 8000 bus ID: 02:08.0 chip ID: 8086:1031
IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
IP v4: <filter> type: dynamic scope: global broadcast: <filter>
IP v6: <filter> type: dynamic scope: global
IP v6: <filter> type: noprefixroute dynamic scope: global
IP v6: <filter> scope: link
Device-3: Ralink RT2800 802.11n PCI driver: rt2800pci v: 2.3.0 port: 8000 bus ID: 03:00.0
chip ID: 1814:0601
IF: wlan0 state: down mac: <filter>
WAN IP: No WAN IP data found. Connected to the web? SSL issues?
Drives: Local Storage: total: 465.76 GiB used: 4.78 GiB (1.0%)
ID-1: /dev/sda vendor: Samsung model: SSD 860 EVO mSATA 500GB size: 465.76 GiB block size:
physical: 512 B logical: 512 B speed: <unknown> serial: <filter> rev: 1B6Q scheme: MBR
Floppy-1: /dev/fd0
Optical-1: /dev/sr0 vendor: HL-DT-ST model: RW/DVD GCC-4240N rev: 0211 dev-links: cdrom,cdrw,dvd
Features: speed: 24 multisession: yes audio: yes dvd: yes rw: cd-r,cd-rw state: running
RAID: Message: No RAID data was found.
Partition: ID-1: / raw size: 32.00 GiB size: 31.25 GiB (97.65%) used: 4.72 GiB (15.1%) fs: ext4
block size: 4096 B dev: /dev/sda1 label: rootMX18 uuid: c7ea50f9-3dd7-48a3-be9f-e28afbf5d241
ID-2: /home raw size: 216.00 GiB size: 211.61 GiB (97.97%) used: 94.1 MiB (0.0%) fs: ext4
block size: 4096 B dev: /dev/sda2 label: homeMX18 uuid: 7959cf3f-8255-47c1-9b67-a91ee7f9e4a6
ID-3: /media/jason/DATA raw size: 215.76 GiB size: 211.37 GiB (97.97%) used: 60.0 MiB (0.0%)
fs: ext4 block size: 4096 B dev: /dev/sda3 label: DATA uuid: 7ea00ee0-1f86-4aec-8c4f-1063960309e6
ID-4: swap-1 size: 2.00 GiB used: 0 KiB (0.0%) fs: swap swappiness: 60 (default)
cache pressure: 100 (default) dev: /dev/sda4 label: SWAP
uuid: 231da768-e783-418a-a4fa-54dbc85841ef
Unmounted: Message: No unmounted partitions found.
USB: Hub: 1-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s chip ID: 1d6b:0001
Hub: 2-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s chip ID: 1d6b:0001
Hub: 3-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s chip ID: 1d6b:0001
Sensors: System Temperatures: cpu: 41.0 C mobo: 24.0 C
Fan Speeds (RPM): cpu: 3405
Repos: Active apt repos in: /etc/apt/sources.list.d/antix.list
1: deb http://iso.mxrepo.com/antix/stretch stretch main
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://ftp.ca.debian.org/debian/ stretch-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://ftp.ca.debian.org/debian/ stretch main contrib non-free
2: deb http://security.debian.org/ stretch/updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://iso.mxrepo.com/mx/repo/ stretch main non-free
No active apt repos in: /etc/apt/sources.list.d/various.list
Processes: CPU top: 5
1: cpu: 5.1% command: xorg pid: 2327 mem: 41.4 MiB (2.1%)
2: cpu: 3.2% command: applet.py started by: python3 pid: 3308 mem: 25.4 MiB (1.3%)
3: cpu: 2.4% command: conky pid: 3530 mem: 10.2 MiB (0.5%)
4: cpu: 2.0% command: sudo pid: 4017 mem: 5.14 MiB (0.2%)
5: cpu: 1.5% command: apt-notifier.py started by: python pid: 3398 mem: 75.7 MiB (3.8%)
Memory top: 5
1: mem: 75.7 MiB (3.8%) command: apt-notifier.py started by: python pid: 3398 cpu: 1.5%
2: mem: 41.4 MiB (2.1%) command: xorg pid: 2327 cpu: 5.1%
3: mem: 35.0 MiB (1.7%) command: xfce4-terminal pid: 3145 cpu: 1.1%
4: mem: 34.9 MiB (1.7%) command: tumblerd pid: 3164 cpu: 0.8%
5: mem: 32.7 MiB (1.6%) command: xfdesktop pid: 3115 cpu: 1.1%
Info: Processes: 157 Uptime: 2m Init: SysVinit v: 2.88 runlevel: 5 default: 5 Compilers: gcc: 6.3.0
alt: 6 Shell: bash (sudo) v: 4.4.12 running in: xfce4-terminal inxi: 3.0.25
Re: MX-18 beta 1 feedback
Posted: Tue Dec 11, 2018 11:16 pm
by Hierax_ca
Thinkpad T43p (2005-2006):
Works fine!
sudo inxi -v8 -z
Code: Select all
System: Host: Thinkpad-T43p-Linux-MX18b1 Kernel: 4.19.0-1-686-pae i686 bits: 32 compiler: gcc v: 6.3.0
Desktop: Xfce 4.12.3 tk: Gtk 2.24.31 info: xfce4-panel wm: xfwm4 dm: LightDM 1.18.3
Distro: MX-18b1_386 Continuum December 3 2018 base: Debian GNU/Linux 9 (stretch)
Machine: Type: Laptop System: IBM product: 2668H2U v: ThinkPad T43p serial: <filter> Chassis: type: 10
serial: N/A
Mobo: IBM model: 2668H2U serial: <filter> BIOS: IBM v: 1YET59WW (1.24 ) date: 11/07/2005
Battery: ID-1: BAT0 charge: 62.4 Wh condition: 62.4/77.8 Wh (80%) volts: 12.5/10.8
model: Panasonic IBM-92P1068 type: Li-ion serial: <filter> status: Full
Memory: RAM: total: 1.90 GiB used: 297.5 MiB (15.3%)
Array-1: capacity: 2 GiB note: est. slots: 2 EC: None max module size: 1 GiB
Device-1: DIMM 1 size: 1 GiB info: double-bank speed: Unknown type: DDR detail: synchronous
bus width: 64 bits total: 64 bits manufacturer: N/A part-no: Not Specified serial: <filter>
Device-2: DIMM 2 size: 1 GiB info: double-bank speed: Unknown type: DDR detail: synchronous
bus width: 64 bits total: 64 bits manufacturer: N/A part-no: Not Specified serial: <filter>
PCI Slots: Slot: Adapter 0, Socket 0 type: 32-bit PC Card (PCMCIA) CardBus Slot 1 status: Available
length: Other
Slot: 1 type: 32-bit PCI Mini-PCI Slot 1 status: Available length: Other
CPU: Topology: Single Core model: Intel Pentium M bits: 32 type: MCP arch: M Dothan family: 6
model-id: D (13) stepping: 8 microcode: 20 L1 cache: 32 KiB L2 cache: 2048 KiB bogomips: 1596
Speed: 800 MHz min/max: 800/2133 MHz Core speed (MHz): 1: 1066
Flags: acpi apic bts clflush cmov cpuid cx8 de dts est fpu fxsr mca mce mmx msr mtrr nx pae pbe
pge pse pti sep ss sse sse2 tm tm2 tsc vme
Vulnerabilities: Type: l1tf mitigation: PTE Inversion
Type: meltdown mitigation: PTI
Type: spec_store_bypass status: Vulnerable
Type: spectre_v1 mitigation: __user pointer sanitization
Type: spectre_v2 mitigation: Full generic retpoline
Graphics: Device-1: Advanced Micro Devices [AMD/ATI] RV380/M24 GL [Mobility FireGL V3200] vendor: IBM
driver: radeon v: kernel bus ID: 01:00.0 chip ID: 1002:3154
Display: server: X.Org 1.19.2 driver: ati,radeon unloaded: fbdev,modesetting,vesa
resolution: 1600x1200~60Hz
OpenGL: renderer: ATI RV380 v: 2.1 Mesa 18.2.6 direct render: Yes
Audio: Device-1: Intel 82801FB/FBM/FR/FW/FRW AC97 Audio vendor: IBM driver: snd_intel8x0 v: kernel
bus ID: 00:1e.2 chip ID: 8086:266e
Sound Server: ALSA v: k4.19.0-1-686-pae
Network: Device-1: Broadcom Limited NetXtreme BCM5751M Gigabit Ethernet PCI Express
vendor: IBM ThinkPad X41 / Z60t driver: tg3 v: 3.137 port: 3000 bus ID: 02:00.0
chip ID: 14e4:167d
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
IP v4: <filter> type: dynamic scope: global broadcast: <filter>
IP v6: <filter> type: dynamic scope: global
IP v6: <filter> type: noprefixroute dynamic scope: global
IP v6: <filter> scope: link
Device-2: Intel PRO/Wireless 2200BG [Calexico2] Network driver: ipw2200 v: 1.2.2kmprq port: 3000
bus ID: 04:02.0 chip ID: 8086:4220
IF: eth1 state: up mac: <filter>
IP v4: <filter> type: dynamic scope: global broadcast: <filter>
IP v6: <filter> type: dynamic scope: global
IP v6: <filter> type: noprefixroute dynamic scope: global
IP v6: <filter> scope: link
Device-3: Ralink RT2800 802.11n PCI driver: rt2800pci v: 2.3.0 port: 3000 bus ID: 05:00.0
chip ID: 1814:0601
IF: wlan0 state: up mac: <filter>
IP v4: <filter> type: dynamic scope: global broadcast: <filter>
IP v6: <filter> type: dynamic scope: global
IP v6: <filter> type: noprefixroute dynamic scope: global
IP v6: <filter> scope: link
WAN IP: No WAN IP data found. Connected to the web? SSL issues?
Drives: Local Storage: total: 298.09 GiB used: 8.32 GiB (2.8%)
ID-1: /dev/sda vendor: Western Digital model: WD3200BEVE-00A0HT0 size: 298.09 GiB block size:
physical: 512 B logical: 512 B speed: <unknown> rotation: 5400 rpm serial: <filter> rev: 1A11
temp: 25 C scheme: MBR
Floppy-1: /dev/fd0
Optical-1: /dev/sr0 vendor: MATSHITA model: DVD-RAM UJ-822S rev: 1.61
dev-links: cdrom,cdrw,dvd,dvdrw
Features: speed: 24 multisession: yes audio: yes dvd: yes rw: cd-r,cd-rw,dvd-r,dvd-ram
state: running
RAID: Message: No RAID data was found.
Partition: ID-1: / raw size: 296.09 GiB size: 290.44 GiB (98.09%) used: 8.32 GiB (2.9%) fs: ext4
block size: 4096 B dev: /dev/sda1 label: rootMX18 uuid: 9c1f7067-ce25-4d9f-a3d7-4db42bf19598
ID-2: swap-1 size: 2.00 GiB used: 0 KiB (0.0%) fs: swap swappiness: 60 (default)
cache pressure: 100 (default) dev: /dev/sda2 label: SWAP
uuid: db30d1e2-4571-4c44-8dc8-b29bb5b5d542
Unmounted: Message: No unmounted partitions found.
USB: Hub: 1-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s chip ID: 1d6b:0001
Hub: 2-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s chip ID: 1d6b:0001
Hub: 3-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s chip ID: 1d6b:0001
Device-1: 3-2:2 info: STMicro Fingerprint Reader type: <vendor specific> driver: N/A
interfaces: 1 rev: 1.0 speed: 12 Mb/s chip ID: 0483:2016
Hub: 4-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s chip ID: 1d6b:0001
Hub: 5-0:1 info: Full speed (or root) Hub ports: 8 rev: 2.0 speed: 480 Mb/s chip ID: 1d6b:0002
Sensors: System Temperatures: cpu: 39.0 C mobo: 37.0 C
Fan Speeds (RPM): cpu: 3081
Repos: Active apt repos in: /etc/apt/sources.list.d/antix.list
1: deb http://iso.mxrepo.com/antix/stretch stretch main
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://ftp.ca.debian.org/debian/ stretch-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://ftp.ca.debian.org/debian/ stretch main contrib non-free
2: deb http://security.debian.org/ stretch/updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://iso.mxrepo.com/mx/repo/ stretch main non-free
No active apt repos in: /etc/apt/sources.list.d/various.list
Processes: CPU top: 5
1: cpu: 2.0% command: applet.py started by: python3 pid: 3719 mem: 25.5 MiB (1.3%)
2: cpu: 1.9% command: xorg pid: 2420 mem: 62.5 MiB (3.2%)
3: cpu: 1.7% command: conky pid: 4121 mem: 10.7 MiB (0.5%)
4: cpu: 1.6% command: hp-systray started by: python3 pid: 3684 mem: 76.9 MiB (3.9%)
5: cpu: 1.0% command: networkmanager pid: 2431 mem: 13.7 MiB (0.7%)
Memory top: 5
1: mem: 76.9 MiB (3.9%) command: hp-systray started by: python3 pid: 3684 cpu: 1.6%
2: mem: 74.3 MiB (3.8%) command: apt-notifier.py started by: python pid: 3970 cpu: 0.8%
3: mem: 62.5 MiB (3.2%) command: xorg pid: 2420 cpu: 1.9%
4: mem: 34.0 MiB (1.7%) command: xfce4-terminal pid: 3476 cpu: 0.6%
5: mem: 32.6 MiB (1.6%) command: xfdesktop pid: 3451 cpu: 0.7%
Info: Processes: 161 Uptime: 2m Init: SysVinit v: 2.88 runlevel: 5 default: 5 Compilers: gcc: 6.3.0
alt: 6 Shell: bash (sudo) v: 4.4.12 running in: xfce4-terminal inxi: 3.0.25
Re: MX-18 beta 1 feedback
Posted: Tue Dec 11, 2018 11:18 pm
by Hierax_ca
Thinkpad T60p (2006-2007):
Works fine!
sudo inxi -v8 -z
Code: Select all
System: Host: Thinkpad-T60p-Linux-MX18b1 Kernel: 4.19.0-1-amd64 x86_64 bits: 64 compiler: gcc v: 6.3.0
Desktop: Xfce 4.12.3 tk: Gtk 2.24.31 info: xfce4-panel wm: xfwm4 dm: LightDM 1.18.3
Distro: MX-18b1_x64 Continuum December 3 2018 base: Debian GNU/Linux 9 (stretch)
Machine: Type: Laptop System: LENOVO product: 2007WLY v: ThinkPad T60p serial: <filter> Chassis: type: 10
serial: N/A
Mobo: LENOVO model: 2007WLY serial: <filter> BIOS: LENOVO v: 79ETE7WW (2.27 ) date: 03/21/2011
Battery: ID-1: BAT0 charge: 64.5 Wh condition: 64.5/84.2 Wh (77%) volts: 12.4/10.8
model: Panasonic 92P1133 type: Li-ion serial: <filter> status: Full
Memory: RAM: total: 2.93 GiB used: 385.7 MiB (12.9%)
Array-1: capacity: 4 GiB note: est. slots: 2 EC: None max module size: 2 GiB
Device-1: DIMM 1 size: 2 GiB info: double-bank speed: Unknown type: DDR2 detail: synchronous
bus width: 64 bits total: 64 bits manufacturer: N/A part-no: Not Specified serial: <filter>
Device-2: DIMM 2 size: 2 GiB info: double-bank speed: Unknown type: DDR2 detail: synchronous
bus width: 64 bits total: 64 bits manufacturer: N/A part-no: Not Specified serial: <filter>
PCI Slots: Slot: 0 type: x1 PCI Express ExpressCard Slot 1 status: Available length: Other
Slot: Adapter 1, Socket 0 type: 32-bit PC Card (PCMCIA) CardBus Slot 1 status: Available
length: Other
CPU: Topology: Dual Core model: Intel Core2 T7200 bits: 64 type: MCP arch: Core Merom family: 6
model-id: F (15) stepping: 6 microcode: D1 L1 cache: 128 KiB L2 cache: 4096 KiB bogomips: 7979
Speed: 1810 MHz min/max: 1000/2000 MHz Core speeds (MHz): 1: 997 2: 997
Flags: acpi aperfmperf apic arch_perfmon bts clflush cmov constant_tsc cpuid cx16 cx8 de ds_cpl
dtes64 dtherm dts est fpu fxsr ht lahf_lm lm mca mce mmx monitor msr mtrr nopl nx pae pat pbe
pdcm pebs pge pni pse pse36 pti rep_good sep ss sse sse2 ssse3 syscall tm tm2 tpr_shadow tsc vme
vmx xtpr
Vulnerabilities: Type: l1tf mitigation: PTE Inversion; VMX: EPT disabled
Type: meltdown mitigation: PTI
Type: spec_store_bypass status: Vulnerable
Type: spectre_v1 mitigation: __user pointer sanitization
Type: spectre_v2 mitigation: Full generic retpoline
Graphics: Device-1: Advanced Micro Devices [AMD/ATI] RV530/M56 GL [Mobility FireGL V5200]
vendor: Lenovo ThinkPad T60p driver: radeon v: kernel bus ID: 01:00.0 chip ID: 1002:71c4
Display: server: X.Org 1.19.2 driver: ati,radeon unloaded: fbdev,modesetting,vesa
resolution: 1600x1200~60Hz
OpenGL: renderer: ATI RV530 v: 2.1 Mesa 18.2.6 direct render: Yes
Audio: Device-1: Intel NM10/ICH7 Family High Definition Audio vendor: Lenovo ThinkPad R60/T60/X60 series
driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:27d8
Sound Server: ALSA v: k4.19.0-1-amd64
Network: Device-1: Intel 82573L Gigabit Ethernet vendor: Lenovo ThinkPad T60 driver: e1000e v: 3.2.6-k
port: 3000 bus ID: 02:00.0 chip ID: 8086:109a
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
IP v4: <filter> type: dynamic scope: global broadcast: <filter>
IP v6: <filter> type: dynamic scope: global
IP v6: <filter> type: noprefixroute dynamic scope: global
IP v6: <filter> scope: link
Device-2: Intel Ultimate N WiFi Link 5300 driver: iwlwifi v: kernel port: 3000 bus ID: 03:00.0
chip ID: 8086:4236
IF: wlan0 state: up mac: <filter>
IP v4: <filter> type: dynamic scope: global broadcast: <filter>
IP v6: <filter> type: dynamic scope: global
IP v6: <filter> type: noprefixroute dynamic scope: global
IP v6: <filter> scope: link
WAN IP: No WAN IP data found. Connected to the web? SSL issues?
Drives: Local Storage: total: 238.47 GiB used: 4.84 GiB (2.0%)
ID-1: /dev/sda vendor: Samsung model: SSD PM810 FDE 2.5 256GB size: 238.47 GiB block size:
physical: 512 B logical: 512 B speed: 1.5 Gb/s serial: <filter> rev: 7D1Q scheme: MBR
Optical-1: /dev/sr0 vendor: HL-DT-ST model: DVDRAM GSA-4083N rev: 1.08
dev-links: cdrom,cdrw,dvd,dvdrw
Features: speed: 24 multisession: yes audio: yes dvd: yes rw: cd-r,cd-rw,dvd-r,dvd-ram
state: running
RAID: Message: No RAID data was found.
Partition: ID-1: / raw size: 234.47 GiB size: 229.79 GiB (98.00%) used: 4.84 GiB (2.1%) fs: ext4
block size: 4096 B dev: /dev/sda1 label: rootMX18 uuid: d95553fb-6eeb-40da-85d3-cc5e104d64ba
ID-2: swap-1 size: 4.00 GiB used: 0 KiB (0.0%) fs: swap swappiness: 60 (default)
cache pressure: 100 (default) dev: /dev/sda2 label: SWAP
uuid: ef0e0fef-4bbc-4485-888d-d98c7e38ba3d
Unmounted: Message: No unmounted partitions found.
USB: Hub: 1-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s chip ID: 1d6b:0001
Hub: 2-0:1 info: Full speed (or root) Hub ports: 8 rev: 2.0 speed: 480 Mb/s chip ID: 1d6b:0002
Hub: 3-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s chip ID: 1d6b:0001
Device-1: 3-1:2 info: Sierra Wireless MC5720 Wireless Modem type: <vendor specific>
driver: sierra interfaces: 1 rev: 1.1 speed: 12 Mb/s chip ID: 1199:0218
Hub: 4-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s chip ID: 1d6b:0001
Hub: 5-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s chip ID: 1d6b:0001
Device-2: 5-1:2 info: Broadcom BCM2045B (BDC-2) [Bluetooth Controller] type: Bluetooth
driver: btusb interfaces: 4 rev: 2.0 speed: 12 Mb/s chip ID: 0a5c:2110
Device-3: 5-2:3 info: STMicro Fingerprint Reader type: <vendor specific> driver: N/A
interfaces: 1 rev: 1.0 speed: 12 Mb/s chip ID: 0483:2016
Sensors: System Temperatures: cpu: 46.0 C mobo: 29.0 C
Fan Speeds (RPM): cpu: 0
Repos: Active apt repos in: /etc/apt/sources.list.d/antix.list
1: deb http://iso.mxrepo.com/antix/stretch stretch main
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://ftp.ca.debian.org/debian/ stretch-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://ftp.ca.debian.org/debian/ stretch main contrib non-free
2: deb http://security.debian.org/ stretch/updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://iso.mxrepo.com/mx/repo/ stretch main non-free
No active apt repos in: /etc/apt/sources.list.d/various.list
Processes: CPU top: 5
1: cpu: 1.3% command: xorg pid: 2692 mem: 69.9 MiB (2.3%)
2: cpu: 1.3% command: conky pid: 4420 mem: 11.7 MiB (0.3%)
3: cpu: 1.2% command: modemmanager pid: 2843 mem: 8.63 MiB (0.2%)
4: cpu: 0.7% command: applet.py started by: python3 pid: 4032 mem: 33.1 MiB (1.1%)
5: cpu: 0.5% command: init pid: 1 mem: 1.86 MiB (0.0%)
Memory top: 5
1: mem: 82.4 MiB (2.7%) command: apt-notifier.py started by: python pid: 4307 cpu: 0.2%
2: mem: 69.9 MiB (2.3%) command: xorg pid: 2692 cpu: 1.3%
3: mem: 39.5 MiB (1.3%) command: tumblerd pid: 3913 cpu: 0.2%
4: mem: 36.8 MiB (1.2%) command: xfce4-terminal pid: 3875 cpu: 0.2%
5: mem: 36.0 MiB (1.2%) command: nm-applet pid: 4009 cpu: 0.4%
Info: Processes: 180 Uptime: 4m Init: SysVinit v: 2.88 runlevel: 5 default: 5 Compilers: gcc: 6.3.0
alt: 6 Shell: bash (sudo) v: 4.4.12 running in: xfce4-terminal inxi: 3.0.25
Re: MX-18 beta 1 feedback
Posted: Tue Dec 11, 2018 11:25 pm
by Hierax_ca
Thinkpad x60 Tablet aka x60t (2006-2007):
Boot Delay error still there! Need to implement fix from forums!
Fix (manual):
-
update MX-18 to X.Org 1.19.6 as per stevo:
-
viewtopic.php?f=134&t=45522
can this update be included in MX-18? It's been working fine in MX17.1 for a while.
Screen Rotation and Wacom Pen Alignment problem also persists.
Display > Rotation works correctly but the pen/mouse/pointer doesn't match the rotation making the pen useful only in non-rotated mode. I have no fix for this but it is a long-standing linux issue.
sudo inxi -v8 -z
Code: Select all
System: Host: Thinkpad-x60t-Linux-MX18b1 Kernel: 4.19.0-1-amd64 x86_64 bits: 64 compiler: gcc v: 6.3.0
Desktop: Xfce 4.12.3 tk: Gtk 2.24.31 info: xfce4-panel wm: xfwm4 dm: LightDM 1.18.3
Distro: MX-18b1_x64 Continuum December 3 2018 base: Debian GNU/Linux 9 (stretch)
Machine: Type: Laptop System: LENOVO product: 6363C7U v: ThinkPad X60 Tablet serial: <filter> Chassis:
type: 10 serial: N/A
Mobo: LENOVO model: 6363C7U serial: <filter> BIOS: LENOVO v: 7JET30WW (1.15 ) date: 11/20/2008
Battery: ID-1: BAT0 charge: 42.4 Wh condition: 42.7/66.2 Wh (64%) volts: 16.5/14.4 model: SANYO 93P5032
type: Li-ion serial: <filter> status: Unknown
Memory: RAM: total: 2.92 GiB used: 366.7 MiB (12.2%)
Array-1: capacity: 4 GiB note: est. slots: 2 EC: None max module size: 2 GiB
Device-1: DIMM 1 size: 2 GiB info: double-bank speed: Unknown type: DDR2 detail: synchronous
bus width: 64 bits total: 64 bits manufacturer: N/A part-no: Not Specified serial: <filter>
Device-2: DIMM 2 size: 2 GiB info: double-bank speed: Unknown type: DDR2 detail: synchronous
bus width: 64 bits total: 64 bits manufacturer: N/A part-no: Not Specified serial: <filter>
PCI Slots: Slot: Adapter 1, Socket 0 type: 32-bit PC Card (PCMCIA) CardBus Slot 1 status: Available
length: Other
Slot: N/A type: SD Card Slot 1 status: Available length: Other
CPU: Topology: Dual Core model: Intel Core2 L7400 bits: 64 type: MCP arch: Core Merom family: 6
model-id: F (15) stepping: 6 microcode: D1 L1 cache: 128 KiB L2 cache: 4096 KiB bogomips: 5984
Speed: 1418 MHz min/max: 1000/1500 MHz Core speeds (MHz): 1: 1209 2: 1068
Flags: acpi aperfmperf apic arch_perfmon bts clflush cmov constant_tsc cpuid cx16 cx8 de ds_cpl
dtes64 dtherm dts est fpu fxsr ht lahf_lm lm mca mce mmx monitor msr mtrr nopl nx pae pat pbe pdcm
pebs pge pni pse pse36 pti rep_good sep ss sse sse2 ssse3 syscall tm tm2 tpr_shadow tsc vme vmx xtpr
Vulnerabilities: Type: l1tf mitigation: PTE Inversion
Type: meltdown mitigation: PTI
Type: spec_store_bypass status: Vulnerable
Type: spectre_v1 mitigation: __user pointer sanitization
Type: spectre_v2 mitigation: Full generic retpoline
Graphics: Device-1: Intel Mobile 945GM/GMS 943/940GML Express Integrated Graphics
vendor: Lenovo ThinkPad R60/T60/X60 series driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:27a2
Display: server: X.Org 1.19.2 driver: intel resolution: 1400x1050~50Hz
OpenGL: renderer: Mesa DRI Intel 945GM v: 1.4 Mesa 18.2.6 direct render: Yes
Audio: Device-1: Intel NM10/ICH7 Family High Definition Audio vendor: Lenovo ThinkPad R60/T60/X60 series
driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:27d8
Sound Server: ALSA v: k4.19.0-1-amd64
Network: Device-1: vendor: Lenovo driver: N/A port: 2000 bus ID: 02:00.0 chip ID: 682c:109a
Device-2: Intel PRO/Wireless 3945ABG [Golan] Network driver: iwl3945 v: in-tree:s port: 2000
bus ID: 03:00.0 chip ID: 8086:4227
IF: wlan0 state: down mac: <filter>
WAN IP: No WAN IP data found. Connected to the web? SSL issues?
Drives: Local Storage: total: 1.82 TiB used: 4.63 GiB (0.2%)
ID-1: /dev/sda vendor: Seagate model: ST2000LX001-1RG174 size: 1.82 TiB block size: physical: 4096 B
logical: 512 B speed: 1.5 Gb/s rotation: 5400 rpm serial: <filter> rev: SDM1 temp: 42 C scheme: MBR
Optical-1: /dev/sr0 vendor: Optiarc model: DVD RW AD-7910A rev: 1.D1 dev-links: cdrom,cdrw,dvd,dvdrw
Features: speed: 24 multisession: yes audio: yes dvd: yes rw: cd-r,cd-rw,dvd-r,dvd-ram
state: running
RAID: Message: No RAID data was found.
Partition: ID-1: / raw size: 929.51 GiB size: 913.92 GiB (98.32%) used: 4.63 GiB (0.5%) fs: ext4
block size: 4096 B dev: /dev/sda3 label: rootMX18 uuid: 3d3361da-db6b-4b6a-b8c6-e5bf2475c769
ID-2: swap-1 size: 4.00 GiB used: 0 KiB (0.0%) fs: swap swappiness: 60 (default)
cache pressure: 100 (default) dev: /dev/sda4 label: SWAP-Linux
uuid: bab3f890-e58e-4ce4-9aa6-6651414abf0b
Unmounted: ID-1: /dev/sda1 size: 100.0 MiB fs: ntfs label: System Reserved uuid: A61CD5F91CD5C489
ID-2: /dev/sda2 size: 929.41 GiB fs: ntfs label: N/A uuid: 4662E92B62E92083
USB: Hub: 1-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s chip ID: 1d6b:0001
Hub: 2-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s chip ID: 1d6b:0001
Hub: 3-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s chip ID: 1d6b:0001
Hub: 4-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s chip ID: 1d6b:0001
Device-1: 4-1:2 info: STMicro Fingerprint Reader type: <vendor specific> driver: N/A interfaces: 1
rev: 1.0 speed: 12 Mb/s chip ID: 0483:2016
Device-2: 4-2:3 info: Broadcom BCM2045B (BDC-2) [Bluetooth Controller] type: Bluetooth driver: btusb
interfaces: 4 rev: 2.0 speed: 12 Mb/s chip ID: 0a5c:2110
Hub: 5-0:1 info: Full speed (or root) Hub ports: 8 rev: 2.0 speed: 480 Mb/s chip ID: 1d6b:0002
Hub: 5-6:2 info: Lenovo Hub ports: 4 rev: 2.0 speed: 480 Mb/s chip ID: 17ef:1000
Sensors: System Temperatures: cpu: 50.0 C mobo: 49.0 C
Fan Speeds (RPM): cpu: 3467
Repos: Active apt repos in: /etc/apt/sources.list.d/antix.list
1: deb http://iso.mxrepo.com/antix/stretch stretch main
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://ftp.ca.debian.org/debian/ stretch-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://ftp.ca.debian.org/debian/ stretch main contrib non-free
2: deb http://security.debian.org/ stretch/updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://iso.mxrepo.com/mx/repo/ stretch main non-free
No active apt repos in: /etc/apt/sources.list.d/various.list
Processes: CPU top: 5
1: cpu: 1.4% command: xfwm4 pid: 3359 mem: 20.8 MiB (0.6%)
2: cpu: 0.9% command: conky pid: 3881 mem: 13.7 MiB (0.4%)
3: cpu: 0.6% command: xorg pid: 2900 mem: 21.7 MiB (0.7%)
4: cpu: 0.6% command: xfsettingsd pid: 3370 mem: 20.2 MiB (0.6%)
5: cpu: 0.6% command: applet.py started by: python3 pid: 3425 mem: 33.2 MiB (1.1%)
Memory top: 5
1: mem: 82.8 MiB (2.7%) command: apt-notifier.py started by: python pid: 3586 cpu: 0.3%
2: mem: 37.9 MiB (1.2%) command: tumblerd pid: 3545 cpu: 0.2%
3: mem: 37.4 MiB (1.2%) command: nm-applet pid: 3452 cpu: 0.6%
4: mem: 36.8 MiB (1.2%) command: xfce4-terminal pid: 3784 cpu: 0.6%
5: mem: 33.2 MiB (1.1%) command: applet.py started by: python3 pid: 3425 cpu: 0.6%
Info: Processes: 172 Uptime: 8m Init: SysVinit v: 2.88 runlevel: 5 default: 5 Compilers: gcc: 6.3.0 alt: 6
Shell: bash (sudo) v: 4.4.12 running in: xfce4-terminal inxi: 3.0.25
Re: MX-18 beta 1 feedback
Posted: Tue Dec 11, 2018 11:28 pm
by Hierax_ca
This Tablet Rotation and Pen Alignment error also applies to the Thinkpads x61t, x200t, and x220t. Presumably others too, does anyone have a pen tablet working properly with Linux?
Re: MX-18 beta 1 feedback
Posted: Tue Dec 11, 2018 11:36 pm
by Hierax_ca
General random notes on MX-18b1 32-bit testing:
MX-18 Testing Beta 1 32-bit
General:
- MX Welcome Tools icon doesn't match regular icon for mxtools, make same (also codecs).
- add AntiX-cli-cc to MX Testing Repo, if not popular apps
- LibreOffice 1:6.1.3-1~bpo9+2 from Backports might be the last 32-bit LibreOffice (no 32-bit 6.2 from TDF), be good to have it as the default (if GIMP can be newer than stable 2.10.8 vs. 2.8.22 (?) why not LibreOffice just moving to a more stable bug-fixed version?). FWIW, latest is 2018-11-30:
https://downloadarchive.documentfoundat ... 1.4.1/deb/
- MX Package Installer:
- re-order tabs, Backports should be before Test repo
- Audio: add exfalso, quodlibet, maybe add old audio packages from alsa project (see 600x fix above)
- Browsers: add palemoon-nonsse2 single core to Popular apps on 32-bit for older low-spec computers (to match kernel option), Dillo, Links2 because Firefox struggles on really old computers!
- Desktop Environments: LXQT
- Development : add Bluefish
- FileManagers: add xfe
- Games: DOSBOX! ScummVM, gnugo, gnubg, pychess, triplea, etc...
- Graphics: AZpainter, LightZone, Scribus should be 1.4.7 for main popular option, 1.5.x for testing
- Office: FocusWriter
- Wallpapers: MX17, AntiX
- Window Managers: add i3, update iceWM to 1.4.3.0~pre-20181030-2 (so that sending app to workspace works properly, this has been working well for me in antiX 17.x Testing/Buster)
- add a section for Terminal apps: include the amazing AntiX-cli-cc
Re: MX-18 beta 1 feedback
Posted: Wed Dec 12, 2018 1:48 am
by Stevo
Hierax_ca wrote: Tue Dec 11, 2018 11:10 pm
Thinkpad 600x (1999-2001)
Display Color and Audio Sound issues persist (started with antix-17 and mx-17, works properly with MX-14.4 and 16.1):
Color Problem:
-
colors display as inverted/opposite -- e.g., yellow=purple, blue=green. Note: this problem doesn't happen in AntiX-core cli console interface, issue occurs only with xorg running.
$ inxi -Gxxx
Code: Select all
Graphics:
Device-1: Neomagic NM2360 [MagicMedia 256ZX] vendor: IBM ThinkPad 600X
driver: N/A bus ID: 01:00.0 chip ID: 10c8:0006
Display: x11 server: X.Org 1.19.2 driver: vesa resolution: 1024x768~61Hz
OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.3 Mesa 18.2.6 compat-v: 3.1
direct render: Yes
Color Solution:
- sudo nano on /etc/X11/xorg.conf
- changed color depth to 16-bit by adding last line: "DefaultDepth 16"
Is there a way to have the color depth detected on install and change this automatically or semi-manually with an Fn button option in the Live boot or installer? Or some MX tool for low color resolution? Or something to get color displaying properly on ancient computers like this? Was whatever that did this before (with MX-14.4 and -16.1) removed?
Sound Problem:
- MX Select Sound: "
No sound cards/devices were found"
Before Fix
$ inxi -Axxx
Code: Select all
Audio:
Device-1: Cirrus Logic CS 4614/22/24/30 [CrystalClear SoundFusion Audio
Accelerator]
vendor: IBM ThinkPad 600X/A20m driver: N/A bus ID: 00:06.0 chip ID: 1013:6003
Sound Server: ALSA v: k4.19.0-1-686-pae
Sound Solution (manual):
- download latest old firmware:
ftp://ftp.alsa-project.org/pub/firmware ... 29.tar.bz2 (2015-02-20)
- right click in Thunar extract here
- copy cs46xx folder
- open Root Thunar
- paste to /lib/firmware/
- open terminal "sudo modprobe -r snd-cs46xx" then "sudo modprobe snd-cs46xx"
Could this cs46xx firmware be included in the 32-bit .iso (or an MX tool created that could extract and paste the needed driver)? There are also numerous other old sound cards here in the file that might help other people with really old laptops.
After Fix:
$ inxi -Axxx
Code: Select all
Audio:
Device-1: Cirrus Logic CS 4614/22/24/30 [CrystalClear SoundFusion Audio
Accelerator]
vendor: IBM ThinkPad 600X/A20m driver: snd_cs46xx v: kernel bus ID: 00:06.0
chip ID: 1013:6003
Sound Server: ALSA v: k4.19.0-1-686-pae
Full inxi
sudo inxi -v8 -z
Code: Select all
System: Host: mx1 Kernel: 4.19.0-1-686-pae i686 bits: 32 compiler: gcc v: 6.3.0 Desktop: Xfce 4.12.3
tk: Gtk 2.24.31 info: xfce4-panel wm: xfwm4 dm: LightDM 1.18.3
Distro: MX-18b1_386 Continuum December 3 2018 base: Debian GNU/Linux 9 (stretch)
Machine: Type: Laptop System: IBM product: 26468EU v: N/A serial: <filter> Chassis: type: 10
serial: N/A
Mobo: IBM model: 26468EU serial: <filter> BIOS: IBM v: ITET55WW date: 11/30/1999
Battery: ID-1: BAT0 charge: 43.3 Wh condition: 45.4/45.4 Wh (100%) volts: 11.8/10.8
model: IBM Corporation ThinkPad Battery type: Li-ion serial: N/A status: Unknown
Memory: RAM: total: 494.6 MiB used: 234.3 MiB (47.4%)
Array-1: capacity: 768 MiB note: est. slots: 3 EC: None max module size: 256 MiB
Device-1: DIMM 0 size: 64 MiB info: single-bank speed: type: Other detail: synchronous
bus width: 64 bits total: 64 bits manufacturer: N/A part-no: N/A serial: N/A
Device-2: DIMM 1 size: 256 MiB info: double-bank speed: type: Other detail: synchronous
bus width: 64 bits total: 64 bits manufacturer: N/A part-no: N/A serial: N/A
Device-3: DIMM 2 size: 256 MiB info: double-bank speed: type: Other detail: synchronous
bus width: 64 bits total: 64 bits manufacturer: N/A part-no: N/A serial: N/A
PCI Slots: Slot: Adapter 0, Socket 0 type: 32-bit PC Card (PCMCIA) CardBus Slot 1 status: Available
length: Other
Slot: Adapter 0, Socket 1 type: 32-bit PC Card (PCMCIA) CardBus Slot 2 status: Available
length: Other
CPU: Topology: Single Core model: Pentium III (Coppermine) bits: 32 type: MCP
arch: P6 III Coppermine family: 6 model-id: 8 stepping: 6 microcode: 9 L1 cache: 32 KiB
L2 cache: 256 KiB bogomips: 1694
Speed: 850 MHz min/max: 700/850 MHz Core speed (MHz): 1: 850
Flags: cmov cpuid cx8 de fpu fxsr mca mce mmx msr mtrr pae pge pse pse36 pti sep sse tsc vme
Vulnerabilities: Type: l1tf mitigation: PTE Inversion
Type: meltdown mitigation: PTI
Type: spec_store_bypass status: Vulnerable
Type: spectre_v1 mitigation: __user pointer sanitization
Type: spectre_v2 mitigation: Full generic retpoline
Graphics: Device-1: Neomagic NM2360 [MagicMedia 256ZX] vendor: IBM ThinkPad 600X driver: N/A
bus ID: 01:00.0 chip ID: 10c8:0006
Display: server: X.Org 1.19.2 driver: vesa resolution: 1024x768~61Hz
OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.3 Mesa 18.2.6 compat-v: 3.1
direct render: Yes
Audio: Device-1: Cirrus Logic CS 4614/22/24/30 [CrystalClear SoundFusion Audio Accelerator]
vendor: IBM ThinkPad 600X/A20m driver: N/A bus ID: 00:06.0 chip ID: 1013:6003
Sound Server: ALSA v: k4.19.0-1-686-pae
Network: Device-1: Intel 82371AB/EB/MB PIIX4 ISA type: network bridge driver: N/A port: 4400
bus ID: 00:07.0 chip ID: 8086:7110
Device-2: Intel 82371AB/EB/MB PIIX4 ACPI type: network bridge driver: N/A port: 4000
bus ID: 00:07.3 chip ID: 8086:7113
Device-3: Ralink RT2800 802.11n PCI driver: rt2800pci v: 2.3.0 port: 4000 bus ID: 06:00.0
chip ID: 1814:0601
IF: wlan0 state: down mac: <filter>
WAN IP: No WAN IP data found. Connected to the web? SSL issues?
Drives: Local Storage: total: 119.24 GiB used: 35.7 MiB (0.0%)
ID-1: /dev/sda vendor: Crucial model: CT128M550SSD3 size: 119.24 GiB block size:
physical: 4096 B logical: 512 B speed: <unknown> serial: <filter> rev: MU01 temp: 43 C
scheme: MBR
Floppy-1: /dev/fd0
Optical-1: /dev/sr0 vendor: TOSHIBA model: DVD-ROM SD-C2612 rev: 1011 dev-links: cdrom,dvd
Features: speed: 24 multisession: yes audio: yes dvd: yes rw: none state: running
RAID: Message: No RAID data was found.
Partition: ID-1: / raw size: N/A size: 374.0 MiB used: 19.7 MiB (5.3%) fs: overlay dev: ERR-102
label: N/A uuid: N/A
ID-2: /live/boot-dev raw size: 1.29 GiB size: 1.29 GiB (99.94%) used: 1.29 GiB (100.0%)
fs: iso9660 block size: 2048 B dev: /dev/sr0 label: antiXlive uuid: 2018-12-03-02-22-49-00
ID-3: swap-1 size: 2.05 GiB used: 16.0 MiB (0.8%) fs: swap swappiness: 60 (default)
cache pressure: 100 (default) dev: /dev/sda2 label: N/A
uuid: e1d91df4-8549-41c8-9868-b42919b504c1
Unmounted: ID-1: /dev/sda1 size: 117.20 GiB fs: ext4 label: N/A
uuid: 5c84ae89-d35e-46b9-bb10-905c61f3f9b9
USB: Hub: 1-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s chip ID: 1d6b:0001
Sensors: Message: No sensors data was found. Is sensors configured?
Repos: Active apt repos in: /etc/apt/sources.list.d/antix.list
1: deb http://iso.mxrepo.com/antix/stretch stretch main
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://ftp.us.debian.org/debian/ stretch-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://ftp.us.debian.org/debian/ stretch main contrib non-free
2: deb http://security.debian.org/ stretch/updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://mxrepo.com/mx/repo/ stretch main non-free
No active apt repos in: /etc/apt/sources.list.d/various.list
Processes: CPU top: 5
1: cpu: 15.5% command: sudo pid: 4482 mem: 4.97 MiB (1.0%)
2: cpu: 6.9% command: xfce4-terminal pid: 4417 mem: 30.8 MiB (6.2%)
3: cpu: 6.1% command: libwhiskermenu.so started by: wrapper-1.0 pid: 4108 mem: 26.4 MiB (5.3%)
4: cpu: 5.2% command: xfwm4 pid: 3972 mem: 18.0 MiB (3.6%)
5: cpu: 5.1% command: xfsettingsd pid: 4052 mem: 15.8 MiB (3.2%)
Memory top: 5
1: mem: 61.2 MiB (12.3%) command: apt-notifier.py started by: python pid: 4082 cpu: 3.9%
2: mem: 31.0 MiB (6.2%) command: xorg pid: 3536 cpu: 4.2%
3: mem: 30.8 MiB (6.2%) command: xfce4-terminal pid: 4417 cpu: 6.9%
4: mem: 29.7 MiB (5.9%) command: nm-applet pid: 4024 cpu: 3.5%
5: mem: 27.9 MiB (5.6%) command: yad pid: 4029 cpu: 3.2%
Info: Processes: 152 Uptime: 10m Init: SysVinit v: 2.88 runlevel: 5 default: 5 Compilers: gcc: 6.3.0
alt: 6 Shell: bash (sudo) v: 4.4.12 running in: xfce4-terminal inxi: 3.0.25
There is an xserver-xorg-video-neomagic video driver in Synaptic, but maybe it's not for your chipset, or else you need to specify it in an xorg.conf type file if you have it installed and it's still using the vesa driver.
Re: MX-18 beta 1 feedback
Posted: Wed Dec 12, 2018 2:23 am
by Gordon Cooper
Thought I had commented here before. But no. Must have been writing to myself.
Hierax, many thanks for the MX-18/Thinkpad reports. There is a place for these on the MX Wiki. Meantime, will wait and see it there are any changes in the Mx-18 final release that may change the compatibility of those Thinkpads. IMHO you may be a bit hopeful with the X600, it is a old machine and perhaps has reached the end of its use by date ?
G.
Re: MX-18 beta 1 feedback
Posted: Wed Dec 12, 2018 4:01 am
by Hierax_ca
Yeah, I hear you, the Thinkpad 600x, being a turn of the millennium machine, is right on the edge. AntiX 17.2.1 Core Buster is probably the sweet spot where I'll use it most, but still good to push things and see just how old of a computer MX-18 can handle when figuring out the minimum system requirements, 18-20 years is a bit of a "stretch"
Moving up from 576MB of RAM to 2GB, and from a 500-850MHz P3 CPU to a 2GHz P4, shows a marked difference in ancient usefulness of a 600x vs. an A31p, those few years of difference are telling.
Re: MX-18 beta 1 feedback
Posted: Wed Dec 12, 2018 4:06 am
by Hierax_ca
Stevo wrote: Wed Dec 12, 2018 1:48 am
There is an xserver-xorg-video-neomagic video driver in Synaptic, but maybe it's not for your chipset, or else you need to specify it in an xorg.conf type file if you have it installed and it's still using the vesa driver.
I tried installing (and uninstalling and reinstalling) the neomagic driver but it didn't get it going right, so I'll play with it more and see if I can figure that out in the xorg.conf for Beta2 or RC1 or whatever is next...
Re: MX-18 beta 1 feedback
Posted: Wed Dec 12, 2018 6:05 am
by Hierax_ca
Thinkpad x301 (2009):
Optical Drive Issue persists (going back to at least MX-15b2
(https://mxlinux.org/forum/viewtopic.php ... 4b#p374032)):
starts to boot off of live DVD but then:
Code: Select all
Fatal Error
Could not find file antiX/linuxfs
Searched devices: /dev/sr0
Searched types: usb,cd
All block devices: /dev/sro /dev/sda2 /dev/sda1 /dev/sda
Please contact BitJam at https://mxlinux.org
BitJam, looks like the same issue as with 15.x, 16.x, and 17.x. Probably nothing can be done that we didn't try before but just noting it here in case anything new has come up.
FWIW, I've come to terms with using an extra HDD or extra battery in the ultrabay with MX to get around this issue, so no big deal for me but I'll keep trying with every major update, just in case. Revisit this again with antiX-19 Buster...
Extra info:
sudo lshw
Code: Select all
...
*-cdrom
description: DVD-RAM writer
product: DVD-RAM UJ-844
vendor: MATSHITA
physical id: 0.0.0
bus info: scsi@3:0.0.0
logical name: /dev/cdrom
logical name: /dev/cdrw
logical name: /dev/dvd
logical name: /dev/dvdrw
logical name: /dev/sr0
version: RC05
capabilities: removable audio cd-r cd-rw dvd dvd-r dvd-ram
configuration: ansiversion=5 status=open
Besides Optical issues, boots fine and installs from USB:
sudo inxi -v8 -z
Code: Select all
System: Host: Thinkpad-x301-Linux-MX18b1 Kernel: 4.19.0-1-amd64 x86_64 bits: 64 compiler: gcc v: 6.3.0
Desktop: Xfce 4.12.3 tk: Gtk 2.24.31 info: xfce4-panel wm: xfwm4 dm: LightDM 1.18.3
Distro: MX-18b1_x64 Continuum December 3 2018 base: Debian GNU/Linux 9 (stretch)
Machine: Type: Laptop System: LENOVO product: 277633U v: ThinkPad X301 serial: <filter> Chassis: type: 10
serial: N/A
Mobo: LENOVO model: 277633U serial: <filter> BIOS: LENOVO v: 6EET47WW (3.07 ) date: 10/13/2009
Battery: ID-1: BAT0 charge: 23.4 Wh condition: 24.0/43.2 Wh (55%) volts: 12.6/10.8 model: SANYO 42T4643
type: Li-ion serial: <filter> status: Charging
Memory: RAM: total: 7.69 GiB used: 434.4 MiB (5.5%)
Array-1: capacity: 8 GiB note: est. slots: 2 EC: None max module size: 4 GiB
Device-1: DIMM 1 size: 4 GiB info: double-bank speed: 800 MHz type: DDR3 detail: synchronous
bus width: 64 bits total: 64 bits manufacturer: 859B part-no: CT51264BF160B.C16F serial: <filter>
Device-2: DIMM 2 size: 4 GiB info: double-bank speed: 800 MHz type: DDR3 detail: synchronous
bus width: 64 bits total: 64 bits manufacturer: 859B part-no: CT51264BF160B.C16F serial: <filter>
PCI Slots: Slot: Adapter 1, Socket 0 type: 32-bit PC Card (PCMCIA) CardBus Slot 1 status: Available
length: Other
CPU: Topology: Dual Core model: Intel Core2 Duo U9600 bits: 64 type: MCP arch: Penryn family: 6
model-id: 17 (23) stepping: A (10) microcode: A0B L1 cache: 128 KiB L2 cache: 3072 KiB
bogomips: 6383
Speed: 923 MHz min/max: 800/1601 MHz boost: enabled Core speeds (MHz): 1: 798 2: 798
Flags: acpi aperfmperf apic arch_perfmon bts clflush cmov constant_tsc cpuid cx16 cx8 de ds_cpl
dtes64 dtherm dts est flexpriority fpu fxsr ht ida lahf_lm lm mca mce mmx monitor msr mtrr nopl nx
pae pat pbe pdcm pebs pge pni pse pse36 pti sep smx ss sse sse2 sse4_1 ssse3 syscall tm tm2
tpr_shadow tsc vme vmx vnmi xsave xtpr
Vulnerabilities: Type: l1tf mitigation: PTE Inversion
Type: meltdown mitigation: PTI
Type: spec_store_bypass status: Vulnerable
Type: spectre_v1 mitigation: __user pointer sanitization
Type: spectre_v2 mitigation: Full generic retpoline
Graphics: Device-1: Intel Mobile 4 Series Integrated Graphics vendor: Lenovo driver: i915 v: kernel
bus ID: 00:02.0 chip ID: 8086:2a42
Display: server: X.Org 1.19.2 driver: intel resolution: 1440x900~60Hz
OpenGL: renderer: Mesa DRI Mobile Intel GM45 Express v: 2.1 Mesa 18.2.6 direct render: Yes
Audio: Device-1: Intel 82801I HD Audio vendor: Lenovo driver: snd_hda_intel v: kernel bus ID: 00:1b.0
chip ID: 8086:293e
Sound Server: ALSA v: k4.19.0-1-amd64
Network: Device-1: Intel 82567LM Gigabit Network vendor: Lenovo driver: e1000e v: 3.2.6-k port: 1840
bus ID: 00:19.0 chip ID: 8086:10f5
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
IP v4: <filter> type: dynamic scope: global broadcast: <filter>
IP v6: <filter> type: dynamic scope: global
IP v6: <filter> type: noprefixroute dynamic scope: global
IP v6: <filter> scope: link
Device-2: Intel PRO/Wireless 5100 AGN [Shiloh] Network driver: iwlwifi v: kernel port: 1c60
bus ID: 03:00.0 chip ID: 8086:4237
IF: wlan0 state: down mac: <filter>
WAN IP: No WAN IP data found. Connected to the web? SSL issues?
Drives: Local Storage: total: 261.53 GiB used: 4.80 GiB (1.8%)
ID-1: /dev/sda vendor: Crucial model: CT250MX200SSD3 size: 232.89 GiB block size: physical: 4096 B
logical: 512 B speed: 3.0 Gb/s serial: <filter> rev: MU02 temp: 36 C scheme: MBR
ID-2: /dev/sdb type: USB vendor: SanDisk model: Ultra Fit size: 28.64 GiB block size:
physical: 512 B logical: 512 B serial: <filter> rev: 1.00 scheme: MBR
Optical-1: /dev/sr0 vendor: MATSHITA model: DVD-RAM UJ-844 rev: RC05 dev-links: cdrom,cdrw,dvd,dvdrw
Features: speed: 24 multisession: yes audio: yes dvd: yes rw: cd-r,cd-rw,dvd-r,dvd-ram
state: running
RAID: Message: No RAID data was found.
Partition: ID-1: / raw size: 224.88 GiB size: 220.35 GiB (97.99%) used: 4.80 GiB (2.2%) fs: ext4
block size: 4096 B dev: /dev/sda1 label: rootMX18 uuid: ad9c9104-ce3f-4315-8cd3-42fa32ce780d
ID-2: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap swappiness: 60 (default)
cache pressure: 100 (default) dev: /dev/sda2 label: SWAP uuid: bba2d4ab-2858-49e6-9427-1ecd6286f177
Unmounted: ID-1: /dev/sdb1 size: 28.64 GiB fs: vfat label: N/A uuid: 1059-467C
USB: Hub: 1-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s chip ID: 1d6b:0001
Device-1: 1-2:2 info: AuthenTec AES2810 type: <vendor specific> driver: N/A interfaces: 1 rev: 2.0
speed: 12 Mb/s chip ID: 08ff:2810
Hub: 2-0:1 info: Full speed (or root) Hub ports: 6 rev: 2.0 speed: 480 Mb/s chip ID: 1d6b:0002
Device-2: 2-6:4 info: Lenovo UVC Camera type: Video driver: uvcvideo interfaces: 2 rev: 2.0
speed: 480 Mb/s chip ID: 17ef:4807
Hub: 3-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s chip ID: 1d6b:0001
Device-3: 3-2:2 info: Broadcom BCM2045B (BDC-2.1) [Bluetooth Controller] type: Bluetooth
driver: btusb interfaces: 4 rev: 2.0 speed: 12 Mb/s chip ID: 0a5c:2145
Hub: 4-0:1 info: Full speed (or root) Hub ports: 6 rev: 2.0 speed: 480 Mb/s chip ID: 1d6b:0002
Device-4: 4-2:2 info: SanDisk type: Mass Storage driver: usb-storage interfaces: 1 rev: 2.1
speed: 480 Mb/s chip ID: 0781:5583 serial: <filter>
Hub: 5-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s chip ID: 1d6b:0001
Hub: 6-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s chip ID: 1d6b:0001
Hub: 7-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s chip ID: 1d6b:0001
Hub: 8-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s chip ID: 1d6b:0001
Sensors: System Temperatures: cpu: 43.0 C mobo: 43.0 C
Fan Speeds (RPM): cpu: 4942
Repos: Active apt repos in: /etc/apt/sources.list.d/antix.list
1: deb http://iso.mxrepo.com/antix/stretch stretch main
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://ftp.ca.debian.org/debian/ stretch-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://ftp.ca.debian.org/debian/ stretch main contrib non-free
2: deb http://security.debian.org/ stretch/updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://iso.mxrepo.com/mx/repo/ stretch main non-free
No active apt repos in: /etc/apt/sources.list.d/various.list
Processes: CPU top: 5
1: cpu: 4.4% command: blueman-applet started by: python3 pid: 3320 mem: 56.8 MiB (0.7%)
2: cpu: 4.3% command: xfwm4 pid: 3296 mem: 22.0 MiB (0.2%)
3: cpu: 4.3% command: nm-applet pid: 3343 mem: 42.0 MiB (0.5%)
4: cpu: 4.0% command: yad pid: 3377 mem: 37.2 MiB (0.4%)
5: cpu: 3.9% command: xfsettingsd pid: 3313 mem: 19.9 MiB (0.2%)
Memory top: 5
1: mem: 66.7 MiB (0.8%) command: apt-notifier.py started by: python pid: 3784 cpu: 0.9%
2: mem: 56.8 MiB (0.7%) command: blueman-applet started by: python3 pid: 3320 cpu: 4.4%
3: mem: 42.0 MiB (0.5%) command: nm-applet pid: 3343 cpu: 4.3%
4: mem: 40.2 MiB (0.5%) command: tumblerd pid: 3758 cpu: 0.8%
5: mem: 37.6 MiB (0.4%) command: xfce4-terminal pid: 3969 cpu: 1.0%
Info: Processes: 182 Uptime: 1m Init: SysVinit v: 2.88 runlevel: 5 default: 5 Compilers: gcc: 6.3.0 alt: 6
Shell: bash (sudo) v: 4.4.12 running in: xfce4-terminal inxi: 3.0.25
After installed to the SSD, checking the optical drive I get CD-Audio/music working correctly in vlc, clementine, audacious, and smplayer but DVD-video/movie failing in both vlc and smplayer.
Re: MX-18 beta 1 feedback
Posted: Wed Dec 12, 2018 9:59 am
by Gerson
Every time I receive an update of MX 18 beta I have to fix the key deposit that is activated and is annoying,
I have already put a solution but it is not definitive.
Re: MX-18 beta 1 feedback
Posted: Wed Dec 12, 2018 11:17 am
by fehlix
Gerson wrote: Wed Dec 12, 2018 9:59 am
Every time I receive an update of MX 18 beta I have to fix the key deposit that is activated and is annoying,
I have already put a solution but it is not definitive.
The proposed solution you posted of using an empty password for the gnome-keyring is neither a solution nor anything we do recommend since we introduced automatically unlock of Gnome-keying using libpam during login.
Please read the Wiki entry about
Gnome-keyring, how to setup this correctly. And please do update your published "insecure solution" accordingly .
Re: MX-18 beta 1 feedback
Posted: Wed Dec 12, 2018 11:59 am
by Gerson
@fehlix
If Gnome-keyring is installed by default on MX Linux and used to manage security credentials, such as user names and passwords; So, why every time there is an update in MX 18 beta the type of problem reappears? Even if I set it up, (without the method I proposed) the annoying windows still appear and the only way to solve it partially is the method I suggested. I did not know he was insecure. This never happened to me in MX 17 and 17.1
Delete the existing keyrings folder: ~/.local/share/keyrings log out and back in.
I'll wait for a next update to see if it is solved.
Re: MX-18 beta 1 feedback
Posted: Wed Dec 12, 2018 12:17 pm
by fehlix
Gerson wrote: Wed Dec 12, 2018 11:59 am
@fehlix
If Gnome-keyring is installed by default on MX Linux and used to manage security credentials, such as user names and passwords; So, why every time there is an update in MX 18 beta the type of problem reappears? Even if I set it up, (without the method I proposed) the annoying windows still appear and the only way to solve it partially is the method I suggested. I did not know he was insecure. This never happened to me in MX 17 and 17.1
Delete the existing keyrings folder: ~/.local/share/keyrings log out and back in.
I'll wait for a next update to see if it is solved.
If you have read the Gnome-keyring wiki entry, you would know how to check this:
Ok, just do this to check: Do remove all keyrings in ~/.local/share/keyrings.
Logout and login. Open password and keys and check whether you have a freshly new login-keyring created.
The login-keyring will be created by libpam.
If not, you either have not installed libpam-gnome-keyring, or something else is wrongly wonky
.
Re: MX-18 beta 1 feedback
Posted: Wed Dec 12, 2018 12:41 pm
by Gerson
@fehlix
libpam-gnome-keyring is installed by default, I deleted the folder ~/.local/ share/keyrings and restarted, for now it does not ask me for keys or Chrome or Vivaldi. I did everything that is in the wiki
(Gnome-keyring), hopefully it is resolved and do not change anything with an update of beta MX18
Re: MX-18 beta 1 feedback
Posted: Wed Dec 12, 2018 2:37 pm
by davemx
Stevo wrote: Sun Dec 09, 2018 7:37 pm
davemx wrote: Sun Dec 09, 2018 12:42 pm
I installed it last night, on Desktop only. I'm using it now. So far the stuff I've done so far works, but GIMP 2.10 clashes with data files needed for MyPaint (no such problem with 2.8 and I hate the grey scheme but none of that is the fault of this excellent distro). Hopefully I'll be able to push a few things and test them over the next few days.
Can report now: Printing and Scanning working perfectly
To revert GIMP interface theme:
https://www.daviesmediadesign.com/custo ... interface/
We have a tweaked version of MyPaint in the test repo that is compatible with GIMP 2.10, I'll ask Tim to move it to main.
You can switch back to the colorful icons for GIMP 2.10 somewhere in the settings, probably in Appearance or Interface. We should probably have that in a FAQ for MX 18.
Yes, GIMP 2.10 now usable! How do some programmers think it's easy to use dark grey backgrounds with slightly darker grey text is beyond me. Though I'm having problems getting it to respond to stylus pressure using my HUION tablet. On the testing version of MyPaint, the Stylus Pressure works just fine though. (Yep, no problems setting up Huion tablet in this version).
My Brother Printer/Scanner, HUION tablet, Facebook videos on Vivaldi, and using vdirsyncer to sync Orage with Google Calendar, work, and were set up, in exactly the same way as they did with 17.1. Everything seems to be working perfectly.
Re: MX-18 beta 1 feedback
Posted: Wed Dec 12, 2018 3:29 pm
by rasat
davemx wrote: Wed Dec 12, 2018 2:37 pm
How do some programmers think it's easy to use dark grey backgrounds with slightly darker grey text is beyond me.
I agree. Change the theme in <Edit><Preferences><Interface><Theme>
Re: MX-18 beta 1 feedback
Posted: Thu Dec 13, 2018 7:36 am
by 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
Re: MX-18 beta 1 feedback
Posted: Thu Dec 13, 2018 9:25 am
by 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.
Re: MX-18 beta 1 feedback
Posted: Thu Dec 13, 2018 9:36 am
by dolphin_oracle
entropyfoe wrote: Thu Dec 13, 2018 9:25 am
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.
Re: MX-18 beta 1 feedback
Posted: Thu Dec 13, 2018 6:24 pm
by Richard
moved.
Re: MX-18 beta 1 feedback
Posted: Fri Dec 14, 2018 9:11 am
by 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?
Re: MX-18 beta 1 feedback
Posted: Fri Dec 14, 2018 9:22 am
by 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.
Re: MX-18 beta 1 feedback
Posted: Fri Dec 14, 2018 9:25 am
by Eadwine Rose
OK.. when on the screen.. don't type anything, just leave it empty and hit enter.
If you tried that already, sorry.
Re: MX-18 beta 1 feedback
Posted: Fri Dec 14, 2018 9:35 am
by manyroads
@Gerson @Eadwine Rose, Eadwine's solution works for me.
Re: MX-18 beta 1 feedback
Posted: Fri Dec 14, 2018 9:49 am
by 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.
Re: MX-18 beta 1 feedback
Posted: Fri Dec 14, 2018 10:45 am
by Eadwine Rose
Ah glad that worked!
Does it stay like that even after a reboot? Only then is it truly solved (at least, imho
)
Re: MX-18 beta 1 feedback
Posted: Fri Dec 14, 2018 3:03 pm
by Gerson
@Eadwine Rose
I have fixed it in two ways:
1.- Opening "Passwords and keys", right click on "Login" then click on "Change password" and generate a blank.
2.- Deleting the folder (~/.local/share/keyrings) and closing and opening session or restarting.
I do not understand why in the updates of MX Package Installer breaks the subject of the keys.
Re: MX-18 beta 1 feedback
Posted: Fri Dec 14, 2018 3:15 pm
by Eadwine Rose
Ah well.. at least it's sorted now!
Re: MX-18 beta 1 feedback (VBoxClient Error)
Posted: Sat Dec 15, 2018 12:17 pm
by manyroads
Using MX 18-beta1, I kept getting the following error message on login:
"VBoxClient: the VirtualBox kernel service is not running. Exiting."
To fix the problem, I removed the pre-installed VirtualBox as follows:
sudo apt purge virtualbox*
Unchecked xfce auto start for vboxclient
And then re-installed VirtualBox using MX Package Installer which seems to have fixed the problem.
Re: MX-18 beta 1 feedback
Posted: Fri Jan 11, 2019 10:15 pm
by golden45
Thats why i have removed conky and installed screenlets,I only use the clock it works well as i just want to see time thanks john
Re: MX-18 beta 1 feedback
Posted: Fri Jan 11, 2019 10:34 pm
by figueroa
golden45, you put the clock on the panel. Wait!, the clock is on the panel! :-)
Re: MX-18 beta 1 feedback
Posted: Fri Jan 11, 2019 11:33 pm
by Eadwine Rose
Beta1 has long come and gone, please open a topic on specifics, thanks! This one is now closed.
