MX Linux Forum

Posted: **Mon Dec 03, 2018 10:42 pm**

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.

Posted: **Mon Dec 03, 2018 10:49 pm**

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.

Posted: **Mon Dec 03, 2018 10:56 pm**

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.

Posted: **Mon Dec 03, 2018 11:23 pm**

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.

Posted: **Tue Dec 04, 2018 12:03 am**

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.

Posted: **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.

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

Posted: **Tue Dec 04, 2018 2:11 am**

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

Posted: **Tue Dec 04, 2018 3:06 am**

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.

Posted: **Tue Dec 04, 2018 3:19 am**

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.

Posted: **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.

tower.txt

Chris

MX Linux Forum

MX-18 beta 1 feedback

Re: MX-18 beta 1 feedback

Re: MX-18 beta 1 feedback

Re: MX-18 beta 1 feedback

Re: MX-18 beta 1 feedback

Re: MX-18 beta 1 feedback -installer now sees the root partition

Re: MX-18 beta 1 feedback

Re: MX-18 beta 1 feedback

Re: MX-18 beta 1 feedback

Re: MX-18 beta 1 feedback

Re: MX-18 beta 1 feedback