MX Linux Forum

Posted: **Sat May 29, 2021 1:01 pm**

Hello to all,

I have searched the forum recursively and tried various solutions to install proprietary Nvidia drivers, but no luck for this configuration, so I start a new post.

I have tried the method of @burrezo and followed posts from @JayM and have been guided by @tony37 and @Huckleberry Finn . I thank you all for your help, but here I will try to do it better. I want to install proprietary drivers from NVIDIA. I have downloaded them. The last version is NVIDIA-Linux-x86_64-334.21. The machine lacks memory (only two gigs). I think proprietary drivers would make the machine work.

I am trying to follow NVIDIA's official solution, enter runlevel 3, exit the xserver and terminate all OpenGL applications so I can install the proprietary driver on a kernel that would do the job for this dinosaur laptop. Currently, I am in the middle of a solution from @burrezo and messed things around.
I go for a clean solution to fix this so I can enjoy my dinosaur laptop!

The configuration below is from the live stick because I can enter only from a terminal to the machine. I am no expert.

Code: Select all

Snaphot created on: 20200915_1434
System:    Host: <filter> Kernel: 4.19.0-9-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
           parameters: quiet nosplash 
           Desktop: Xfce 4.14.2 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-19.2_x64 patito feo May 31  2020 base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Laptop System: ASUSTeK product: F3JC v: 1.0 serial: <filter> Chassis: type: 10 
           serial: <filter> 
           Mobo: ASUSTeK model: F3JC v: 1.0 serial: <filter> BIOS: American Megatrends v: 305 
           date: 02/15/2007 
Battery:   ID-1: BAT0 charge: 1.8 Wh condition: 1.8/50.6 Wh (4%) volts: 12.4/11.1 
           model: ASUSTEK F3---24 type: Li-ion serial: <filter> status: Unknown 
CPU:       Topology: Dual Core model: Intel Core2 T5500 bits: 64 type: MCP arch: Core Merom 
           family: 6 model-id: F (15) stepping: 6 microcode: D1 L2 cache: 2048 KiB 
           flags: lm nx pae sse sse2 sse3 ssse3 bogomips: 6649 
           Speed: 997 MHz min/max: 996/1660 MHz Core speeds (MHz): 1: 1045 2: 1038 
           Vulnerabilities: Type: itlb_multihit status: KVM: Vulnerable 
           Type: l1tf mitigation: PTE Inversion 
           Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled 
           Type: meltdown mitigation: PTI 
           Type: spec_store_bypass status: Vulnerable 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full generic retpoline, STIBP: disabled, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: NVIDIA G72M [Quadro NVS 110M/GeForce Go 7300] vendor: ASUSTeK 
           driver: nouveau v: kernel bus ID: 01:00.0 chip ID: 10de:01d7 
           Display: x11 server: X.Org 1.20.4 driver: nouveau unloaded: fbdev,modesetting,vesa 
           alternate: nv resolution: 1280x800~60Hz 
           OpenGL: renderer: NV46 v: 2.1 Mesa 18.3.6 direct render: Yes 
Audio:     Device-1: Intel NM10/ICH7 Family High Definition Audio vendor: ASUSTeK 
           driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:27d8 
           Sound Server: ALSA v: k4.19.0-9-amd64 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK 
           driver: r8169 v: kernel port: c800 bus ID: 02:00.0 chip ID: 10ec:8168 
           IF: eth0 state: down mac: <filter> 
           Device-2: Intel PRO/Wireless 3945ABG [Golan] Network driver: iwl3945 v: in-tree:s 
           port: c800 bus ID: 03:00.0 chip ID: 8086:4222 
           IF: wlan0 state: up mac: <filter> 
Drives:    Local Storage: total: 116.93 GiB used: 1.76 GiB (1.5%) 
           ID-1: /dev/sda vendor: SanDisk model: SDSSDP064G size: 59.63 GiB block size: 
           physical: 512 B logical: 512 B speed: <unknown> serial: <filter> scheme: MBR 
           ID-2: /dev/sdb type: USB vendor: SanDisk model: Ultra USB 3.0 size: 57.30 GiB 
           block size: physical: 512 B logical: 512 B serial: <filter> rev: 1.00 scheme: MBR 
Partition: ID-1: / raw size: N/A size: 1.52 GiB used: 80.0 MiB (5.1%) fs: overlay 
           source: ERR-102 
           ID-2: swap-1 size: 2.00 GiB used: 256 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sda2 
Sensors:   System Temperatures: cpu: 32.0 C mobo: N/A gpu: nouveau temp: 53 C 
           Fan Speeds (RPM): N/A 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian buster-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian buster main contrib non-free
           2: deb http://deb.debian.org/debian-security buster/updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ buster main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 191 Uptime: 11m Memory: 1.95 GiB used: 915.5 MiB (45.9%) Init: SysVinit 
           v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: quick-system-in 
           running in: quick-system-in inxi: 3.0.36

Thank you all. If no solution is found, no problem, we can all enjoy a beer and be happy anyways! Cheers

Posted: **Sat May 29, 2021 1:10 pm**

What about this? First open a small space and install MX 18.3 there, then install Nvidia easily with 1-2 clicks. At least to see if it makes a noticeable change, if it's worth it (with an old card)..

Meanwhile if you like to be able to boot to your installed MX 19 (purge all Nvidia) we can go on ..

Posted: **Sat May 29, 2021 1:17 pm**

Ok. @Huckleberry Finn. Anyway, the system needs fixing, so I will try to purge all Nvidia. This is done by

Code: Select all

apt-get purge nvidia.

?

By the way I am on

Code: Select all

4.19.0-16amd64 #1 SMP Debian 4.19.181-1

Posted: **Sat May 29, 2021 1:27 pm**

Yes, but it's better to use ddm-mx as it will automatically re-enable nouveau ..

And (for some reason, a kind of known bug) ddm doesn't work on chroot, so:

If you're able to boot into a tty (login manually on black screen, - you can also press Ctrl+Alt+F1 for that - type username & pw...) on installed MX :

Code: Select all

sudo ddm-mx -p nvidia

(If still not, we'll do the other way ...)

Posted: **Sat May 29, 2021 1:34 pm**

Ok @Huckleberry Finn

Let's do this. I have purged all nvidia and did

Code: Select all

sudo ddm-mx -p nvidia

What's next?

Posted: **Sat May 29, 2021 1:37 pm**

Reboot .. Can you now access desktop ?

(While you're at it / If still not: sudo rm /etc/X11/xorg.conf )

Posted: **Sat May 29, 2021 1:43 pm**

No I can't. I did

Code: Select all

sudo rm /etc/X11/xorg.conf

but I get

Code: Select all

rm: cannot remove /etc/X11/xorg.conf : no such file or directory

Posted: **Sat May 29, 2021 1:46 pm**

Ok, the last one was just "in case" there was such an "unwanted" file.. So you made it sure..

So, we need to find out why it doesn't boot, or whether it loads Nouveau ..

You can

Code: Select all

inxi -Fxxxrza > qsi.txt

And you'll find qsi.txt in your home folder. Then you can post it on live session (will be on installed MX's home.. in Thunar.. )

Posted: **Sat May 29, 2021 1:59 pm**

Code: Select all

Snapshot created on: 20200915_1434
System:    Host: <filter> Kernel: 4.19.0-9-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
           parameters: quiet nosplash 
           Desktop: Xfce 4.14.2 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: N/A 
           Distro: MX-19.4_x64 patito feo May 31  2020 base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Laptop System: ASUSTeK product: F3JC v: 1.0 serial: <filter> Chassis: type: 10 
           serial: N/A 
           Mobo: ASUSTeK model: F3JC v: 1.0 serial: <filter> BIOS: American Megatrends v: 305 
           date: 02/15/2007 
Battery:   ID-1: BAT0 charge: 1.7 Wh condition: 1.8/50.6 Wh (4%) volts: 12.4/11.1 
           model: ASUSTEK F3---24 type: Li-ion serial: <filter> status: Unknown 
CPU:       Topology: Dual Core model: Intel Core2 T5500 bits: 64 type: MCP arch: Core Merom 
           family: 6 model-id: F (15) stepping: 6 microcode: D1 L1 cache: 64 KiB 
           L2 cache: 2048 KiB 
           flags: lm nx pae sse sse2 sse3 ssse3 bogomips: 6649 
           Speed: 997 MHz min/max: 996/1660 MHz Core speeds (MHz): 1: 997 2: 997 
           Vulnerabilities: Type: itlb_multihit status: KVM: Vulnerable 
           Type: l1tf mitigation: PTE Inversion 
           Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled 
           Type: meltdown mitigation: PTI 
           Type: spec_store_bypass status: Vulnerable 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full generic retpoline, STIBP: disabled, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: NVIDIA G72M [Quadro NVS 110M/GeForce Go 7300] vendor: ASUSTeK 
           driver: nouveau v: kernel bus ID: 01:00.0 chip ID: 10de:01d7 
           Display: server: X.Org 1.20.4 driver: nouveau unloaded: fbdev,modesetting,vesa 
           alternate: nv resolution: 1280x800~60Hz 
           OpenGL: renderer: NV46 v: 2.1 Mesa 18.3.6 direct render: Yes 
Audio:     Device-1: Intel NM10/ICH7 Family High Definition Audio vendor: ASUSTeK 
           driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:27d8 
           Sound Server: ALSA v: k4.19.0-9-amd64 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK 
           driver: r8169 v: kernel port: c800 bus ID: 02:00.0 chip ID: 10ec:8168 
           IF: eth0 state: down mac: <filter> 
           Device-2: Intel PRO/Wireless 3945ABG [Golan] Network driver: iwl3945 v: in-tree:s 
           port: c800 bus ID: 03:00.0 chip ID: 8086:4222 
           IF: wlan0 state: up mac: <filter> 
Drives:    Local Storage: total: 116.93 GiB used: 13.90 GiB (11.9%) 
           ID-1: /dev/sda vendor: SanDisk model: SDSSDP064G size: 59.63 GiB block size: 
           physical: 512 B logical: 512 B speed: <unknown> serial: <filter> scheme: MBR 
           ID-2: /dev/sdb type: USB vendor: SanDisk model: Ultra USB 3.0 size: 57.30 GiB 
           block size: physical: 512 B logical: 512 B serial: <filter> rev: 1.00 scheme: MBR 
Partition: ID-1: / raw size: 57.59 GiB size: 56.44 GiB (98.00%) used: 13.90 GiB (24.6%) fs: ext4 
           block size: 4096 B dev: /dev/sda1 
           ID-2: swap-1 size: 2.00 GiB used: 1.2 MiB (0.1%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sda2 
Sensors:   System Temperatures: cpu: 29.0 C mobo: N/A gpu: nouveau temp: 49 C 
           Fan Speeds (RPM): N/A 
Repos:     No active apt repos in: /etc/apt/sources.list 
Info:      Processes: 198 Uptime: 14m Memory: 1.95 GiB used: 926.8 MiB (46.5%) Init: SysVinit 
           v: 2.93 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: quick-system-in (sudo) 
           running in: quick-system-in inxi: 3.0.36

Posted: **Sat May 29, 2021 2:01 pm**

Oh no, this is the live-session's qsi :)

Partition: ID-1: / raw size: N/A size: 1.52 GiB used: 87.2 MiB (5.6%) fs: overlay source: ERR-102
__________________________

You can also first chroot on live session (Menu => Chroot Rescue Scan) then

Code: Select all

quick-system-info-mx

or

Code: Select all

inxi -Fxxxrza

__________________________

(The above was to be issued in that tty screen to create a txt file ... later post it on live session.. as the chroot may not give correct info about graphics.. )

Posted: **Sat May 29, 2021 2:05 pm**

Code: Select all

Snapshot created on: 20200915_1434
System:    Host: <filter> Kernel: 4.19.0-9-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
           parameters: quiet nosplash 
           Desktop: Xfce 4.14.2 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: N/A 
           Distro: MX-19.4_x64 patito feo May 31  2020 base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Laptop System: ASUSTeK product: F3JC v: 1.0 serial: <filter> Chassis: type: 10 
           serial: N/A 
           Mobo: ASUSTeK model: F3JC v: 1.0 serial: <filter> BIOS: American Megatrends v: 305 
           date: 02/15/2007 
Battery:   ID-1: BAT0 charge: 1.7 Wh condition: 1.8/50.6 Wh (4%) volts: 12.4/11.1 
           model: ASUSTEK F3---24 type: Li-ion serial: <filter> status: Unknown 
CPU:       Topology: Dual Core model: Intel Core2 T5500 bits: 64 type: MCP arch: Core Merom 
           family: 6 model-id: F (15) stepping: 6 microcode: D1 L1 cache: 64 KiB 
           L2 cache: 2048 KiB 
           flags: lm nx pae sse sse2 sse3 ssse3 bogomips: 6649 
           Speed: 997 MHz min/max: 996/1660 MHz Core speeds (MHz): 1: 997 2: 997 
           Vulnerabilities: Type: itlb_multihit status: KVM: Vulnerable 
           Type: l1tf mitigation: PTE Inversion 
           Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled 
           Type: meltdown mitigation: PTI 
           Type: spec_store_bypass status: Vulnerable 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full generic retpoline, STIBP: disabled, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: NVIDIA G72M [Quadro NVS 110M/GeForce Go 7300] vendor: ASUSTeK 
           driver: nouveau v: kernel bus ID: 01:00.0 chip ID: 10de:01d7 
           Display: server: X.Org 1.20.4 driver: nouveau unloaded: fbdev,modesetting,vesa 
           alternate: nv resolution: 1280x800~60Hz 
           OpenGL: renderer: NV46 v: 2.1 Mesa 18.3.6 direct render: Yes 
Audio:     Device-1: Intel NM10/ICH7 Family High Definition Audio vendor: ASUSTeK 
           driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:27d8 
           Sound Server: ALSA v: k4.19.0-9-amd64 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK 
           driver: r8169 v: kernel port: c800 bus ID: 02:00.0 chip ID: 10ec:8168 
           IF: eth0 state: down mac: <filter> 
           Device-2: Intel PRO/Wireless 3945ABG [Golan] Network driver: iwl3945 v: in-tree:s 
           port: c800 bus ID: 03:00.0 chip ID: 8086:4222 
           IF: wlan0 state: up mac: <filter> 
Drives:    Local Storage: total: 116.93 GiB used: 13.90 GiB (11.9%) 
           ID-1: /dev/sda vendor: SanDisk model: SDSSDP064G size: 59.63 GiB block size: 
           physical: 512 B logical: 512 B speed: <unknown> serial: <filter> scheme: MBR 
           ID-2: /dev/sdb type: USB vendor: SanDisk model: Ultra USB 3.0 size: 57.30 GiB 
           block size: physical: 512 B logical: 512 B serial: <filter> rev: 1.00 scheme: MBR 
Partition: ID-1: / raw size: 57.59 GiB size: 56.44 GiB (98.00%) used: 13.90 GiB (24.6%) fs: ext4 
           block size: 4096 B dev: /dev/sda1 
           ID-2: swap-1 size: 2.00 GiB used: 1.2 MiB (0.1%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sda2 
Sensors:   System Temperatures: cpu: 29.0 C mobo: N/A gpu: nouveau temp: 49 C 
           Fan Speeds (RPM): N/A 
Repos:     No active apt repos in: /etc/apt/sources.list 
Info:      Processes: 198 Uptime: 14m Memory: 1.95 GiB used: 926.8 MiB (46.5%) Init: SysVinit 
           v: 2.93 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: quick-system-in (sudo) 
           running in: quick-system-in inxi: 3.0.36

Posted: **Sat May 29, 2021 2:10 pm**

So, it looks ok now:

Graphics: Device-1: NVIDIA G72M [Quadro NVS 110M/GeForce Go 7300] vendor: ASUSTeK
driver: nouveau v: kernel bus ID: 01:00.0 chip ID: 10de:01d7
Display: server: X.Org 1.20.4 driver: nouveau

Then there's something else preventing boot ...

Where does it stop when you boot? Or what happens if you issue startX (after logging in manually) or pressing Ctrl+Alt+F7 ?

Posted: **Sat May 29, 2021 2:14 pm**

I have changed the list to Debian stretch and moved all lists to /home/user/repos to try to follow the method of @burrezo, but I got stuck in the middle.

Posted: **Sat May 29, 2021 2:16 pm**

What happens if you issue startx (after logging in manually) or pressing Ctrl+Alt+F7 ?

Posted: **Sat May 29, 2021 2:19 pm**

I need to install proprietary drivers via console. I have extracted them, and I am on just my way to sh the installer. I change to runlevel 3, but I want to terminate all applications so I can run it

Posted: **Sat May 29, 2021 2:28 pm**

Huckleberry Finn wrote: Sat May 29, 2021 2:16 pm What happens if you issue startx (after logging in manually) or pressing Ctrl+Alt+F7 ?

Ctrl+altl+F7 is doing nothing. startx gives me

Code: Select all

xinit: giving up xinit: unable to connect to X server: connection refused xinit: server error

Posted: **Sat May 29, 2021 2:41 pm**

@dimi maybe that's because you have removed all xserver-xorg packages and haven't reinstalled them

Code: Select all

apt policy xserver-xorg-core xserver-xorg-video-all

Posted: **Sat May 29, 2021 2:59 pm**

ok @tony37 . Should I reinstall? My intention is different!

Posted: **Sat May 29, 2021 3:01 pm**

can you please give output if you want me to help you
of course you can't do anything without xserver-xorg-core

Posted: **Sat May 29, 2021 3:08 pm**

Code: Select all

xserver-xorg-core: 

Installed: (none)
candidate: (none)
version table: 2:1.20.4-1+deb10u3 -1
100 /var/lib/dpkg/status
xserver-xorg-video-all:
Installed: (none)
Candidate: (none)
version table:

Posted: **Sat May 29, 2021 3:12 pm**

from chroot, or from runlevel 3

Posted: **Sat May 29, 2021 3:17 pm**

I am on runlevel 3 @tony37. What command should I input?

Posted: **Sat May 29, 2021 3:18 pm**

as I said:

Code: Select all

apt policy xserver-xorg-core xserver-xorg-video-all

Posted: **Sat May 29, 2021 3:24 pm**

Code: Select all

xserver-xorg-core: 

Installed: (none)
candidate: (none)
version table: 2:1.20.4-1+deb10u3 -1
100 /var/lib/dpkg/status
xserver-xorg-video-all:
Installed: (none)
Candidate: (none)
Version table:

Posted: **Sat May 29, 2021 3:35 pm**

On live session: Chroot Rescue Scan from Menu.. proceed

Code: Select all

apt update ; apt install xserver-xorg-core xserver-xorg-video-all -y

(Yes, no need to sudo)
_______________________

hoping they were the only missing things..

Posted: **Sat May 29, 2021 3:41 pm**

Code: Select all

Reading package lists... Done
Building dependency tree       
Reading state information... Done
All packages are up to date.
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Package xserver-xorg-core is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
  xserver-xorg-legacy xserver-common

Package xserver-xorg-video-all is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'xserver-xorg-core' has no installation candidate
E: Package 'xserver-xorg-video-all' has no installation candidate

Posted: **Sat May 29, 2021 3:47 pm**

Maybe for you'd changed repos etc. This is in fact a Franken-MX .. That's why I'd suggested to first try Nvidia on 18.3 easily...

Posted: **Sat May 29, 2021 3:49 pm**

Ok @Huckleberry Finn

18.3. How do I proceed?

Posted: **Sat May 29, 2021 3:50 pm**

If you like, while on chroot:

Code: Select all

mx-repo-manager

And reset to defaults, then try again...

Posted: **Sat May 29, 2021 3:55 pm**

@Huckleberry Finn I checked to reset, but I find no option. MX and Debian repos have the option of selecting the fastest and individual apt sources have the restore option, which gives me "could not download original APT files". The other previous options are also not working.

Posted: **Sat May 29, 2021 3:56 pm**

Just on live session, GParted: open some space (8-10GB is enough)

http://it.mxrepo.com/Downloads/Snapshots/

You can also install 4.15 kernel (for it was reported to work when installing 304.xx , default kernel is 4.19) from MXPI (it may be in Popular Apps)

Then boot with it (Advanced Options on Grub) and start Nvidia Driver Installer from Menu ...

Posted: **Sat May 29, 2021 4:01 pm**

dimi wrote: Sat May 29, 2021 3:55 pm @Huckleberry Finn I checked to reset but I find no option.

Anyway, that MX is not healthy ... you need to repair everywhere, so, a clean 19.4 will be the best and fastest (sadly)

Shortly: You just need a clean 19.4 and a clean 18.3 . Takes 15x2 = 30 min roughly :)

Posted: **Sun May 30, 2021 4:54 am**

Ok @Huckleberry Finn . Should I go for the
MX 18.3 2019-09-16 17:43 1.4G and,
MX 19.4 2021-05-16 05:25 1.6G iso's?

Would they do the job?

Posted: **Sun May 30, 2021 9:11 am**

Yes, but imho no need for 32bit on 64 (to make it lighter etc.) .. Just "KISS" :)

http://it.mxrepo.com/Downloads/Snapshot ... er_x64.iso
http://it.mxrepo.com/Downloads/Snapshot ... iso.sha512

http://it.mxrepo.com/Downloads/Snapshot ... ay_x64.iso
http://it.mxrepo.com/Downloads/Snapshot ... iso.sha512

Posted: **Mon May 31, 2021 12:49 pm**

Ok.

So @Huckleberry Finn I have installed 18.3 on a partition, entered 4.15.0-1, updated and upgraded. During the installation of NVIDIA, though, I get an error of unmet dependencies. Plus, I got broken packages.

Posted: **Mon May 31, 2021 1:47 pm**

for MX 18.3 you need to do this tweak to get the 304xx driver: viewtopic.php?p=616973#p616973

Posted: **Mon May 31, 2021 3:13 pm**

Thank you for the link @tony37! Until this point, I have an 18.3 kernel with the proprietary driver. Do I install

Code: Select all

NVIDIA-Linux-x86_64-334.21

on this system? If yes, how? Thank you twice, by the way!

Posted: **Mon May 31, 2021 3:44 pm**

You make the preferences file as in the link in post #36, and then again use MX Nvidia Installer.
If you want to make the preferences file with one command:

Code: Select all

echo -e "Package: glx-alternative-nvidia glx-alternative-mesa glx-diversions update-glx\nPin: release o=Debian\nPin-Priority: 1000\n" | sudo tee /etc/apt/preferences.d/nvidia

Also, please don't use downloaded files when there are better options, like repos.

Posted: **Tue Jun 01, 2021 1:46 am**

What about this? First, open a small space and install MX 18.3 there, then install Nvidia easily with 1-2 clicks. At least to see if it makes a noticeable change if it's worth it (with an old card).

@Huckleberry Finn It makes a huge difference. The system is working with no interruptions or freezes. Proprietary drivers are definitely the way to go. I intend to install the latest proprietary drivers on 19.4. I am sure there is a way to do it.

Posted: **Tue Jun 01, 2021 3:15 am**

Code: Select all

Graphics:  Device-1: NVIDIA G72M [Quadro NVS 110M/GeForce Go 7300] vendor: ASUSTeK 
           driver: nvidia v: 304.137 bus ID: 01:00.0 chip ID: 10de:01d7 
           Display: x11 server: X.Org 1.19.2 driver: nvidia resolution: 1280x800~60Hz 
           OpenGL: renderer: GeForce Go 7300/PCIe/SSE2 v: 2.1.2 NVIDIA 304.137 
           direct render: Yes

Posted: **Tue Jun 01, 2021 4:48 am**

So glad to hear that :)

That's thanks to @tony37 's workaround.

I hope @Lilium23 , too comes with good news :)
_______________________________________________________________

Before I forget: When everything's fine after you customize it according to your taste, remember to run MX Snapshot from Menu and create your own iso. No matter it's MX 18 / 19 / 21 .. at least you'll have an MX system ready with Nvidia.. On live session, to install back etc..

Also note : to boot on live session you need to type xorg=nvidia in boot options. If you like you can make it permanent but this time you'll need to do the reverse (delete that) to boot on another -especially non-nvidia- pc .

Posted: **Tue Jun 01, 2021 5:07 am**

Meanwhile, though your real intention / question was to install on MX 19 , if you mark the thread as solved, it'll help others to find "how to / what to do" easily :)

P.S. Yes, of course there will be ways / workarounds to install it on 19 (maybe 21 soon). But just next time keep your main system and install another MX on a small partition and make all experiments there, break it as much as you like :)
(And go on keeping your 18.3 snapshot iso somewhere).

Posted: **Wed Jun 02, 2021 8:38 am**

@Huckleberry Finn Yes indeed. My initial question was how to install NVIDIA-Linux-x86_64-334.21 on 19.4 or 18.3. I read the documentation from Nvidia after downloading the driver and, I am sure that I am doing something wrong during installation. I understand that everything is better when installing drivers from the distribution repos since it's also written in the documentation. Still, I will search a little more to find a clear solution. For the moment, I got once a system freeze yesterday, but the system is much more stable under 18.3 with the proprietary drivers. I will check to find 2 gigs more

I will add them and give it some time. If you recommend anything else hardware-wise, I would love to hear from you. Processors are still working full during some difficult operations. I don't expect a lot since phones have more memory and processing power than this old machine. I try to keep it calm with hard tasks and change governors mode also if necessary. It might help.

I didn't manage to create a snapshot. I have tried twice, but I get a space problem. I am struggling to resize my partition since I have 15 gigs of partition, 9 gigs of free space on 18.3. Isn't it enough?

P.S.: How do I fire up the terminal over here at 18.3? It's not CTRL+Alt+T? I have been searching to change the shortcuts but no luck.

Posted: **Wed Jun 02, 2021 9:02 am**

F4 will open a terminal (drop-down).. For shortcuts: "Keyboard" from Menu. (Also Alt + F1 for MXUM :) )

You can select another place as the destination for the snapshot to be created, say another partition (when mounted and when permissions are ok) or a usb stick big enough .. Also you can select .xz to compress it max. Yes, normally it's a big space but it needs (calculates) some more space for temp files (not to approach to 100 % full during process)

Posted: **Wed Jun 02, 2021 9:08 am**

Just one note: Yes, there are "tips & tricks" or "how to" threads.. like that, "how to install Nvidia 304.xxx on MX 19" etc..

But they're not official, all by users .. Therefore (as a general rule) support should be provided by the Original Poster when someone is stuck on any stage or someone breaks his/her system.

Posted: **Wed Jun 02, 2021 9:23 am**

dimi wrote: Wed Jun 02, 2021 8:38 amMy initial question was how to install NVIDIA-Linux-x86_64-334.21 on 19.4 or 18.3. I read the documentation from Nvidia after downloading the driver and, I am sure that I am doing something wrong during installation. I understand that everything is better when installing drivers from the distribution repos since it's also written in the documentation. Still, I will search a little more to find a clear solution.

This didn't work?

MX Linux Forum

[Solved] Installation of proprietary NVIDIA Quadro NVS 110M GeForce Go 7300

[Solved] Installation of proprietary NVIDIA Quadro NVS 110M GeForce Go 7300

Re: Installation of proprietary NVIDIA Quadro NVS 110M GeForce Go 7300

Re: Installation of proprietary NVIDIA Quadro NVS 110M GeForce Go 7300

Re: Installation of proprietary NVIDIA Quadro NVS 110M GeForce Go 7300

Re: Installation of proprietary NVIDIA Quadro NVS 110M GeForce Go 7300

Re: Installation of proprietary NVIDIA Quadro NVS 110M GeForce Go 7300

Re: Installation of proprietary NVIDIA Quadro NVS 110M GeForce Go 7300

Re: Installation of proprietary NVIDIA Quadro NVS 110M GeForce Go 7300

Re: Installation of proprietary NVIDIA Quadro NVS 110M GeForce Go 7300

Re: Installation of proprietary NVIDIA Quadro NVS 110M GeForce Go 7300

Re: Installation of proprietary NVIDIA Quadro NVS 110M GeForce Go 7300

Re: Installation of proprietary NVIDIA Quadro NVS 110M GeForce Go 7300

Re: Installation of proprietary NVIDIA Quadro NVS 110M GeForce Go 7300

Re: Installation of proprietary NVIDIA Quadro NVS 110M GeForce Go 7300

Re: Installation of proprietary NVIDIA Quadro NVS 110M GeForce Go 7300

Re: Installation of proprietary NVIDIA Quadro NVS 110M GeForce Go 7300

Re: Installation of proprietary NVIDIA Quadro NVS 110M GeForce Go 7300

Re: Installation of proprietary NVIDIA Quadro NVS 110M GeForce Go 7300

Re: Installation of proprietary NVIDIA Quadro NVS 110M GeForce Go 7300

Re: Installation of proprietary NVIDIA Quadro NVS 110M GeForce Go 7300

Re: Installation of proprietary NVIDIA Quadro NVS 110M GeForce Go 7300

Re: Installation of proprietary NVIDIA Quadro NVS 110M GeForce Go 7300

Re: Installation of proprietary NVIDIA Quadro NVS 110M GeForce Go 7300

Re: Installation of proprietary NVIDIA Quadro NVS 110M GeForce Go 7300

Re: Installation of proprietary NVIDIA Quadro NVS 110M GeForce Go 7300

Re: Installation of proprietary NVIDIA Quadro NVS 110M GeForce Go 7300

Re: Installation of proprietary NVIDIA Quadro NVS 110M GeForce Go 7300

Re: Installation of proprietary NVIDIA Quadro NVS 110M GeForce Go 7300

Re: Installation of proprietary NVIDIA Quadro NVS 110M GeForce Go 7300

Re: Installation of proprietary NVIDIA Quadro NVS 110M GeForce Go 7300

Re: Installation of proprietary NVIDIA Quadro NVS 110M GeForce Go 7300

Re: Installation of proprietary NVIDIA Quadro NVS 110M GeForce Go 7300

Re: Installation of proprietary NVIDIA Quadro NVS 110M GeForce Go 7300

Re: Installation of proprietary NVIDIA Quadro NVS 110M GeForce Go 7300

Re: Installation of proprietary NVIDIA Quadro NVS 110M GeForce Go 7300

Re: Installation of proprietary NVIDIA Quadro NVS 110M GeForce Go 7300

Re: Installation of proprietary NVIDIA Quadro NVS 110M GeForce Go 7300

Re: Installation of proprietary NVIDIA Quadro NVS 110M GeForce Go 7300

Re: Installation of proprietary NVIDIA Quadro NVS 110M GeForce Go 7300

Re: Installation of proprietary NVIDIA Quadro NVS 110M GeForce Go 7300

Re: Installation of proprietary NVIDIA Quadro NVS 110M GeForce Go 7300

Re: Installation of proprietary NVIDIA Quadro NVS 110M GeForce Go 7300

Re: Installation of proprietary NVIDIA Quadro NVS 110M GeForce Go 7300

Re: Installation of proprietary NVIDIA Quadro NVS 110M GeForce Go 7300

Re: Installation of proprietary NVIDIA Quadro NVS 110M GeForce Go 7300

Re: Installation of proprietary NVIDIA Quadro NVS 110M GeForce Go 7300