MX-19 Beta 2.1 Feedback

[chrispop99]

so install virtualgl (although in my tests it should have installed).

It did!

Code: Select all

root@mx19b2NV:/home/chris/Desktop# apt install virtualgl
Reading package lists... Done
Building dependency tree       
Reading state information... Done
virtualgl is already the newest version (2.6.2-0mx19+2).

I should mention that this machine (or one like it) was used to test when Stevo was trying to get this working.

He had a setup that worked for him, but didn't on this Dell. We eventually got it working, and it does work on 18.3, but if anyone else can test it would be great.

(Coincidentally I was looking at a Thinkpad T430 on eBay recently, but didn't proceed because it had dual graphics.)

Chris

[dolphin_oracle]

so the drivers installed, but optirun still doesn't work.

ok, let's simulate installing primus now

Code: Select all

sudo apt install primus -s

and provide the output.

FWIW, I think we are circling around a dependency issue with the way the nvidia graphics drivers are currently packaged.

[kmathern]

When running the recent beta (MX-19beta-2.1_x64 patito feo September 8 2019) with the systemd advanced boot option. Right click on the MX Updater item in the panel, and nothing happens (no options menu is raised). Mouse clicks elsewhere on the panel work as well as in sysV.

Have tried this when running under both virtualbox and on normal HD partition, with similar results. My virtualbox quickinfo is:

confirmed. thank you for the report.

I think I've found the cause and have a fix.

[chrispop99]

so the drivers installed, but optirun still doesn't work.

ok, let's simulate installing primus now

Code: Select all

sudo apt install primus -s

and provide the output.

FWIW, I think we are circling around a dependency issue with the way the nvidia graphics drivers are currently packaged.

I get the 'primus is already the newest version' message.

Chris

[dolphin_oracle]

so the drivers installed, but optirun still doesn't work.

ok, let's simulate installing primus now

Code: Select all

sudo apt install primus -s

and provide the output.

FWIW, I think we are circling around a dependency issue with the way the nvidia graphics drivers are currently packaged.

I get the 'primus is already the newest version' message.

Chris

ok, so

optirun -b primus "inxi -G"

[chrispop99]

so the drivers installed, but optirun still doesn't work.

ok, let's simulate installing primus now

Code: Select all

sudo apt install primus -s

and provide the output.

FWIW, I think we are circling around a dependency issue with the way the nvidia graphics drivers are currently packaged.

I get the 'primus is already the newest version' message.

Chris

ok, so

optirun -b primus "inxi -G"

Code: Select all

chris@mx19b2NV:~/Desktop
$ optirun -b primus "inxi -G"
[ 8433.534725] [ERROR]Cannot access secondary GPU - error: Could not load GPU driver

[ 8433.534793] [ERROR]Aborting because fallback start is disabled.

Chris

[dolphin_oracle]

I guess try primusrun directly (although I don't understand why primus is even installed).

Code: Select all

primusrun glxgears

[Gerson]

I don't know if it's already reported but since beta 1 when the command to restart or turn off is given, the Login screen appears for a few seconds and confuses. You should execute the command without that screen appearing.

[chrispop99]

I guess try primusrun directly (although I don't understand why primus is even installed).

Code: Select all

primusrun glxgears

Code: Select all

chris@mx19b2NV:~/Desktop
$ primusrun glxgears
/usr/bin/primusrun: line 41: warning: command substitution: ignored null byte in input
primus: fatal: Bumblebee daemon reported: error: Could not load GPU driver

Perhaps we should put this to one side for now?

I won't ever be running Linux on this laptop, and it might well be that the Nvidia installer will work OK with other dual graphic machines.

I'm happy to keep trying, but don't want to bog you down in something that is not going to affect the vast majority of users.

Chris

[attila123]

MX-19 Beta 2.1 installing to a partition on MBR did not add the boot flag
Hi, I did an installation to an existing MBR partition table (which had 3 partitions). During installation I launched gparted and manually deleted sda1, which was an old system partition (so at this point it lost the boot flag).
Then, when asked, I did the manual setting, and set sda1 to the root partition and chose to install grub to the MBR. The installer installed the system correctly to sda1, but did not set the boot flag on sda1. So the system was not bootable (because the BIOS did not find the bootable flag on any partition). It was confusing and it took me some time to realize what the problem may be. When I got the idea, I rebooted to the live system and manually added the bootable flag to sda1 (using fdisk), and finally I could boot into the installed system.