MX-17 Beta 2 Feedback

[dolphin_oracle]

Fails to boot to X after Nvidia install.

Chris

I did a fresh install, used the PI to drop the kernel to 4.9, and then used ddm-mx to install the Nvidia driver.

It booted successfully, so I'm guessing it is a problem related to the 4.13 kernel.

Chris

Probably...the classic problem with new kernels...dkms module building.

[BitJam]

FWIW, there are patches to let the legacy nvidia 340.102 driver work with kernels up to 4.12: Fully Working Patch for Nvidia Driver 340.102and Linux Kernel 4.12. It might work for 4.13.

For more recent nvidia hardware: NVIDIA 384.59 Driver Is Playing Fine With Linux 4.13.

edit: 420.102 --> 320.102 --> 340.102

edit: Patches for linux 4.13: Patches (2 of them) for NVIDIA Driver 340.104 with Linux Kernel 4.13 and 4.14

It is obviously well past my naptime. Apologies to Adrian.

[Jerry3904]

Please remove some of old xfce themes which are ugly

Or don't work...

That is a good reminder for us, we have intended to some theme-cleaning in the past but somehow keep forgetting.

[Stevo]

We'll have to see if those legacy drivers are already patched in stretch-backports for the 4.13 kernel there.


I did an install in Virtual Box and upgraded to the 4.13.0-1 (4.13.13) kernel in our test repo from the stock bpo 4.13.0-0, and it's running fine. This is seen as a new package, not an upgrade, so the stock kernel is still installed, but I just installed the newer one via the linux-image and headers metapackages.The guest-dkms modules built automatically. One rather big difference is that the stock bpo kernel throws a TSC error at the start of boot and recommends a firmware upgrade when starting in VBox, but the newer kernel doesn't show this. This might be enough to make this the standard kernel, as well as its extended support for amdgpu and the higher kernel frequency...so let's test the new kernel.

[dolphin_oracle]

We'll have to see if those legacy drivers are already patched in stretch-backports for the 4.13 kernel there.


I did an install in Virtual Box and upgraded to the 4.13.0-1 (4.13.13) kernel in our test repo from the stock bpo 4.13.0-0, and it's running fine. This is seen as a new package, not an upgrade, so the stock kernel is still installed, but I just installed the newer one via the linux-image and headers metapackages.The guest-dkms modules built automatically. One rather big difference is that the stock bpo kernel throws a TSC error at the start of boot and recommends a firmware upgrade when starting in VBox, but the newer kernel doesn't show this. This might be enough to make this the standard kernel, as well as its extended support for amdgpu and the higher kernel frequency...so let's test the new kernel.

chris tried the debian-backports hosted nvidia installation and they also failed.

[Stevo]

Add Antivirus to This release i think no distro is using antivirus in linux if we add one which will be useful to scan pendrives and other small stuff
and is it possible to add our image on whisker menu icon where a person pic is already in default on the whisker menu ?
Is it possible to add Startup screen for mx 17 like lubuntu branding instead of the default text appearing when we boot on the system?
Thanks..

I doubt we'll add any antivirus. Probably not any bootup screen, either--many devs like the text. Maybe we can add plymouth with debian-plymouth-manager to the package installer to make it easy to add and configure, but we don't presently don't have any custom MX plymouth theme, and we have to remember that Ubuntu plymouth themes won't work in MX/Debian, and plymouth just zips by in a second or two if you are booting from an SSD.

[anticapitalista]

Does virtualbox build ok with the latest kernel used on beta2?

[Stevo]

We'll have to see if those legacy drivers are already patched in stretch-backports for the 4.13 kernel there.


I did an install in Virtual Box and upgraded to the 4.13.0-1 (4.13.13) kernel in our test repo from the stock bpo 4.13.0-0, and it's running fine. This is seen as a new package, not an upgrade, so the stock kernel is still installed, but I just installed the newer one via the linux-image and headers metapackages.The guest-dkms modules built automatically. One rather big difference is that the stock bpo kernel throws a TSC error at the start of boot and recommends a firmware upgrade when starting in VBox, but the newer kernel doesn't show this. This might be enough to make this the standard kernel, as well as its extended support for amdgpu and the higher kernel frequency...so let's test the new kernel.

chris tried the debian-backports hosted nvidia installation and they also failed.

Ahh, OK. I know the main 375.82 Nvidia driver has no problem with the 4.13 kernel.

I just watched this Youtube review, I know you saw it: https://www.youtube.com/watch?v=rQWnFTIMDQo&t=1020s

where he adds the freaking upstream Debian repos to get one tiny upgrade that we already have in our test repo. Obviously this guy doesn't like to read the Fine Manual; horse-water-can't make drink problem...

[Stevo]

Virtualbox 5.1.30 and the 5.2 from Oracle are good with the 4.13 kernel.

[Stevo]

The changelog for the 340xx Nivida drivers in Buster says they are patched for 4.14, so a backport should work. There's also a newer 304xx in Buster that should work, too.