Page 1 of 1
Two installs have display resolution problems two don't
Posted: Mon Feb 27, 2023 2:11 pm
by jmarkus
I have installed 21.3 wildflower ahs three times now - two times as quests in Virtualbox (Windows 10 and UbuntuMATE v22.04.1 hosts which work great) - and 21.3 wildflower 32bit one time directly to the hard drive. I had one from each category of install lose the ability to display the install which required me using the "safe video", and the "failsafe" in order to get a complete error free install. These two that I used the flags/switches on both have an asterisk by 1024x768 resolution, a couple lower resolution choices, but nothing higher?
The VM one (AHS) doesn't see the Thinkpad laptop monitor's specs (1366x768), and no matter what configuration file I edit - nothing sticks. I tried adding the VirtualBox guest addons, but it claims they are already installed? The graphics are the Intel HD variety on the Intel i5
The direct to drive install (32bit) is a dual boot with Ubuntu Studio v20.04.2 attached to a 55" Sony TV. Graphics are the nVidia 8400gs. I installed the nvidia driver (v340) which messed it up, so I had to do the "sudo ddm-mx -p nvidia" through the terminal to get back.
I got here assuming I could sort it out after getting it installed, but now I don't know enough about MX/Debian to know what I should do next.
Is there a terminal command to query which monitor is connected after installing in "safe video" ,or "failsafe" mode?
Is there a terminal command to reconfigure the display resolution?
Is there a way to upgrade the 32 bit install to AHS?
Any help would be appreciated
Re: Two installs have display resolution problems two don't
Posted: Mon Feb 27, 2023 2:23 pm
by CharlesV
Post your QSI and it will tell both us what your hardware is, your drivers as well, and then should show you ( and us) what the machine sees for monitors
Re: Two installs have display resolution problems two don't
Posted: Mon Feb 27, 2023 2:41 pm
by jmarkus
Here is the laptop QSI - the other one is busy right now
Code: Select all
System: Kernel: 6.0.0-6mx-amd64 [6.0.12-1~mx21+1] x86_64 bits: 64 compiler: gcc v: 10.2.1
parameters: BOOT_IMAGE=/boot/vmlinuz-6.0.0-6mx-amd64
root=UUID=<filter> ro quiet splash
Desktop: Xfce 4.18.1 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm 4.18.0 vt: 7
dm: LightDM 1.26.0 Distro: MX-21.3_ahs_x64 Wildflower January 15 2023
base: Debian GNU/Linux 11 (bullseye)
Machine: Type: Virtualbox System: innotek product: VirtualBox v: 1.2 serial: <filter>
Chassis: Oracle Corporation type: 1 serial: <filter>
Mobo: Oracle model: VirtualBox v: 1.2 serial: <filter> BIOS: innotek v: VirtualBox
date: 12/01/2006
Battery: ID-1: BAT0 charge: 49.5 Wh (99.0%) condition: 50.0/50.0 Wh (100.0%) volts: 10.0
min: 10.0 model: innotek 1 type: Unknown serial: N/A status: Not charging
CPU: Info: Dual Core model: Intel Core i5 M 520 bits: 64 type: MCP arch: Nehalem family: 6
model-id: 25 (37) stepping: 5 microcode: N/A cache: L2: 3 MiB
flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 bogomips: 9575
Speed: 2394 MHz min/max: N/A Core speeds (MHz): 1: 2394 2: 2394
Vulnerabilities: Type: itlb_multihit status: KVM: VMX unsupported
Type: l1tf mitigation: PTE Inversion
Type: mds
status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT Host state unknown
Type: meltdown mitigation: PTI
Type: mmio_stale_data status: Unknown: No mitigations
Type: retbleed status: Not affected
Type: spec_store_bypass status: Vulnerable
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2
mitigation: Retpolines, STIBP: disabled, RSB filling, PBRSB-eIBRS: Not affected
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics: Device-1: VMware SVGA II Adapter driver: N/A bus-ID: 00:02.0 chip-ID: 15ad:0405
class-ID: 0300
Display: x11 server: X.Org 1.20.14 compositor: xfwm4 v: 4.18.0 driver: loaded: vesa
display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1024x768 s-dpi: 96 s-size: 271x203mm (10.7x8.0")
s-diag: 339mm (13.3")
Monitor-1: default res: 1024x768
OpenGL: renderer: llvmpipe (LLVM 14.0.5 128 bits) v: 4.5 Mesa 22.0.5 direct render: Yes
Audio: Device-1: Intel 82801AA AC97 Audio vendor: Dell driver: snd_intel8x0 v: kernel
bus-ID: 00:05.0 chip-ID: 8086:2415 class-ID: 0401
Sound Server-1: ALSA v: k6.0.0-6mx-amd64 running: yes
Sound Server-2: PulseAudio v: 14.2 running: yes
Network: Device-1: Intel 82540EM Gigabit Ethernet driver: e1000 v: kernel port: d020
bus-ID: 00:03.0 chip-ID: 8086:100e class-ID: 0200
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: Intel 82371AB/EB/MB PIIX4 ACPI type: network bridge driver: piix4_smbus
v: N/A modules: i2c_piix4 port: d200 bus-ID: 00:07.0 chip-ID: 8086:7113 class-ID: 0680
Drives: Local Storage: total: 23 GiB used: 6.78 GiB (29.5%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: VirtualBox model: VBOX HARDDISK size: 23 GiB
block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s type: N/A serial: <filter>
rev: 1.0 scheme: MBR
Partition: ID-1: / raw-size: 21.74 GiB size: 21.23 GiB (97.66%) used: 6.78 GiB (31.9%) fs: ext4
dev: /dev/sda1 maj-min: 8:1
Swap: Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 1.25 GiB used: 0 KiB (0.0%) priority: -2
dev: /dev/sda2 maj-min: 8:2
Sensors: Message: No sensor data found. Is lm-sensors configured?
Repos: Packages: note: see --pkg apt: 1971 lib: 993 flatpak: 0
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 bullseye-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian bullseye main contrib non-free
2: deb http://security.debian.org/debian-security bullseye-security 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/ bullseye main non-free
2: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bullseye ahs
Info: Processes: 179 Uptime: 1m wakeups: 3 Memory: 3.51 GiB used: 963.8 MiB (26.8%)
Init: SysVinit v: 2.96 runlevel: 5 default: 5 tool: systemctl Compilers: gcc: N/A
alt: 10 Client: shell wrapper v: 5.1.4-release inxi: 3.3.06
Boot Mode: BIOS (legacy, CSM, MBR)
Re: Two installs have display resolution problems two don't
Posted: Mon Feb 27, 2023 3:15 pm
by jmarkus
This is the QSI from the 32bit install which is using a Sony 55" TV as a monitor. The desired resolution should be 1920x1080 instead of 1024x768.
Code: Select all
System: Kernel: 5.10.0-21-686-pae [5.10.162-1] i686 bits: 32 compiler: gcc v: 10.2.1
parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-21-686-pae
root=UUID=<filter> ro quiet splash
Desktop: Xfce 4.18.1 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm 4.18.0 vt: 7
dm: LightDM 1.26.0 Distro: MX-21.3_386 Wildflower January 15 2023
base: Debian GNU/Linux 11 (bullseye)
Machine: Type: Desktop Mobo: Shuttle model: FG31 v: V10 serial: <filter> BIOS: Phoenix
v: 6.00 PG date: 11/15/2007
CPU: Info: Dual Core model: Intel Core2 Duo E8600 bits: 64 type: MCP arch: Penryn family: 6
model-id: 17 (23) stepping: A (10) microcode: A0B cache: L2: 6 MiB
flags: lm nx pae sse sse2 sse3 sse4_1 ssse3 vmx bogomips: 5319
Speed: 1330 MHz min/max: N/A Core speeds (MHz): 1: 1330 2: 1330
Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf mitigation: PTE Inversion; VMX: EPT disabled
Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled
Type: meltdown mitigation: PTI
Type: mmio_stale_data status: Unknown: No mitigations
Type: retbleed status: Not affected
Type: spec_store_bypass status: Vulnerable
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2
mitigation: Retpolines, STIBP: disabled, RSB filling, PBRSB-eIBRS: Not affected
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics: Device-1: NVIDIA GT218 [GeForce 8400 GS Rev. 3] vendor: eVga.com. driver: N/A
alternate: nouveau bus-ID: 01:00.0 chip-ID: 10de:10c3 class-ID: 0300
Display: x11 server: X.Org 1.20.11 compositor: xfwm4 v: 4.18.0 driver:
loaded: nouveau,vesa unloaded: fbdev,modesetting alternate: nv display-ID: :0.0
screens: 1
Screen-1: 0 s-res: 1024x768 s-dpi: 96 s-size: 271x203mm (10.7x8.0")
s-diag: 339mm (13.3")
Monitor-1: default res: 1024x768
OpenGL: renderer: llvmpipe (LLVM 11.0.1 128 bits) v: 4.5 Mesa 20.3.5 compat-v: 3.1
direct render: Yes
Audio: Device-1: Intel NM10/ICH7 Family High Definition Audio
vendor: Holco Enterprise Co /Shuttle driver: snd_hda_intel v: kernel bus-ID: 00:1b.0
chip-ID: 8086:27d8 class-ID: 0403
Device-2: NVIDIA High Definition Audio vendor: eVga.com. driver: snd_hda_intel
v: kernel bus-ID: 01:00.1 chip-ID: 10de:0be3 class-ID: 0403
Sound Server-1: ALSA v: k5.10.0-21-686-pae running: yes
Sound Server-2: PulseAudio v: 14.2 running: yes
Network: Device-1: Marvell 88E8056 PCI-E Gigabit Ethernet vendor: Holco Enterprise Co /Shuttle
driver: sky2 v: 1.30 port: ce00 bus-ID: 03:00.0 chip-ID: 11ab:4364 class-ID: 0200
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives: Local Storage: total: 111.79 GiB used: 11.04 GiB (9.9%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: PNY model: CS900 120GB SSD size: 111.79 GiB
block-size: physical: 512 B logical: 512 B speed: <unknown> type: SSD serial: <filter>
rev: 0613 scheme: MBR
Partition: ID-1: / raw-size: 33.75 GiB size: 32.68 GiB (96.80%) used: 11.04 GiB (33.8%) fs: ext4
dev: /dev/sda1 maj-min: 8:1
Swap: Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 5.62 GiB used: 0 KiB (0.0%) priority: -2
dev: /dev/sda2 maj-min: 8:2
Sensors: System Temperatures: cpu: 42.0 C mobo: N/A
Fan Speeds (RPM): N/A
Repos: Packages: note: see --pkg apt: 2255 lib: 1189 flatpak: 0
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 bullseye-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian bullseye main contrib non-free
2: deb http://security.debian.org/debian-security bullseye-security 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/ bullseye main non-free
Info: Processes: 184 Uptime: 2m wakeups: 1 Memory: 3.87 GiB used: 1.38 GiB (35.8%)
Init: SysVinit v: 2.96 runlevel: 5 default: 5 tool: systemctl Compilers: gcc: 10.2.1
alt: 10 Client: shell wrapper v: 5.1.4-release inxi: 3.3.06
Boot Mode: BIOS (legacy, CSM, MBR)
Re: Two installs have display resolution problems two don't
Posted: Mon Feb 27, 2023 3:20 pm
by Stevo
I don't think AHS will help on a sixteen year old machine:
Code: Select all
Graphics: Device-1: NVIDIA GT218 [GeForce 8400 GS Rev. 3] vendor: eVga.com. driver: N/A
alternate: nouveau bus-ID: 01:00.0 chip-ID: 10de:10c3 class-ID: 0300
Display: x11 server: X.Org 1.20.11 compositor: xfwm4 v: 4.18.0 driver:
loaded: nouveau,vesa
Maybe you need to force nouveau to load and blacklist vesa.
We really don't have official AHS support for 32-bit, since that's more of a legacy platform.
I do build 32-bit AHS packages while I've got the sources teed up, though.
Re: Two installs have display resolution problems two don't
Posted: Mon Feb 27, 2023 3:45 pm
by jmarkus
"I don't think AHS will help on a sixteen year old machine" Hehe
I know it's old. It is to replace an older purpose built box used for many years to digitize my LP, Cassette, Music, etc collection. Previously Puppy v7.52 did fine until my TV died, and the single core athlon/agp graphics just were not up to driving the new 4k TV. It is hooked up with both analog, and digital to my stereo. I've only got about 50 albums to go, and 35-40 cassettes. I am fine with it remaining 32bit- just want the graphics to work properly.
EDIT
I had been thinking that the AHS would give the option of using nVidia's v470 driver which I thought might solve the problem.
Re: Two installs have display resolution problems two don't
Posted: Mon Feb 27, 2023 4:08 pm
by Huckleberry Finn
It may say "no such file or directory", no harm. But if it gives no output, just reboot.
Re: Two installs have display resolution problems two don't
Posted: Mon Feb 27, 2023 4:20 pm
by Stevo
jmarkus wrote: Mon Feb 27, 2023 3:45 pm
"I don't think AHS will help on a sixteen year old machine" Hehe
I know it's old. It is to replace an older purpose built box used for many years to digitize my LP, Cassette, Music, etc collection. Previously Puppy v7.52 did fine until my TV died, and the single core athlon/agp graphics just were not up to driving the new 4k TV. It is hooked up with both analog, and digital to my stereo. I've only got about 50 albums to go, and 35-40 cassettes. I am fine with it remaining 32bit- just want the graphics to work properly.
EDIT
I had been thinking that the AHS would give the option of using nVidia's v470 driver which I thought might solve the problem.
Nvidia is known for dropping support for older hardware like it's hot, drop it like it's hot...but use the MX Nvidia Installer to be sure, since it looks at the hardware. The last Nvidia driver to support 32-bit was 390 legacy, but I have a feeling that nouveau is the only option in MX 21. MX 19, which is still supported, might support your hardware with the 304 or 340 legacy drivers.
Re: Two installs have display resolution problems two don't
Posted: Mon Feb 27, 2023 4:32 pm
by Huckleberry Finn
Stevo wrote: Mon Feb 27, 2023 4:20 pm...The last Nvidia driver to support 32-bit was 390 legacy, but I have a feeling that nouveau is the only option in MX 21. MX 19, which is still supported, might support your hardware with the 304 or 340 legacy drivers...
Already did:
jmarkus wrote: Mon Feb 27, 2023 2:11 pm...
installed the nvidia driver (v340) which messed it up, so I had to do the "sudo ddm-mx -p nvidia" through the terminal to get back...
Re: Two installs have display resolution problems two don't
Posted: Mon Feb 27, 2023 4:36 pm
by Huckleberry Finn
@jmarkus Other than the above, does it let you do this?
(You know: If no output, it's ok, loaded.)
Re: Two installs have display resolution problems two don't
Posted: Mon Feb 27, 2023 4:44 pm
by jmarkus
Huckleberry Finn wrote: Mon Feb 27, 2023 4:08 pm
It may say "no such file or directory", no harm. But if it gives no output, just reboot.
That's what it did - no such..
Re: Two installs have display resolution problems two don't
Posted: Mon Feb 27, 2023 4:47 pm
by jmarkus
It let me do it, but no reply
Re: Two installs have display resolution problems two don't
Posted: Mon Feb 27, 2023 4:49 pm
by Huckleberry Finn
So fine (no reply=it's done), then just:
Code: Select all
sudo modprobe nouveau ; sudo update-initramfs -uk all
Reboot.
Re: Two installs have display resolution problems two don't
Posted: Mon Feb 27, 2023 4:53 pm
by Huckleberry Finn
In the meantime, my Nvidia is also old that can have 340 max. , and like you, I go on with Nouveau as it's much better than the 340.
But, there was a known suspend/wake-up issue with 5.xx kernels and such older Nvidia cards. (It can't suspend (takes forever) or can suspend but cannot wake-up (black screen)
So, everything's ok with these 2:
antiX 4.9 and the latest 6.1 kernel.
You can try both from MX Package Installer (though 4.9 has reached EOL..)
Re: Two installs have display resolution problems two don't
Posted: Mon Feb 27, 2023 5:01 pm
by jmarkus
came back after reboot with same issue. During terminal command it twice said "I: Set the RESUME variable to override this" ???
Huckleberry Finn wrote: Mon Feb 27, 2023 4:49 pm
So fine (no reply=it's done), then just:
Code: Select all
sudo modprobe nouveau ; sudo update-initramfs -uk all
Reboot.
Re: Two installs have display resolution problems two don't
Posted: Mon Feb 27, 2023 5:05 pm
by jmarkus
i'LL HAVE TO TRY THIS TOMORROW - THANKS
Huckleberry Finn wrote: Mon Feb 27, 2023 4:53 pm
In the meantime, my Nvidia is also old that can have 340 max. , and like you, I go on with Nouveau as it's much better than the 340.
But, there was a known suspend/wake-up issue with 5.xx kernels and such older Nvidia cards. (It can't suspend (takes forever) or can suspend but cannot wake-up (black screen)
So, everything's ok with these 2:
antiX 4.9 and the latest 6.1 kernel.
You can try both from MX Package Installer (though 4.9 has reached EOL..)
Re: Two installs have display resolution problems two don't
Posted: Mon Feb 27, 2023 5:07 pm
by Huckleberry Finn
You can ignore that message.
Code: Select all
echo -e 'nouveau\n\nloop' | sudo tee /etc/modules
Code: Select all
sudo tee /etc/X11/xorg.conf.d/20-nouveau.conf <<!
Section "Device"
Identifier "Device0"
Driver "nouveau"
EndSection
!
(It's normal that the terminal warns you about security, just click "paste" and press enter)
Reboot.
Re: Two installs have display resolution problems two don't
Posted: Mon Feb 27, 2023 6:10 pm
by Huckleberry Finn
jmarkus wrote: Mon Feb 27, 2023 2:11 pm...required me using the "safe video", and the "failsafe" in order to get a complete error free install. These two that I used the flags/switches on both have an asterisk by 1024x768 resolution, a couple lower resolution choices, but nothing higher?..
On live session:
as the boot parameter (without others like failsafe , nomodeset etc.).
Re: Two installs have display resolution problems two don't
Posted: Mon Feb 27, 2023 7:59 pm
by jmarkus
I found a solution to the VirtualBox install on the laptop. I switched display drivers in VirtualBox settings to VBoxSVGA from VMSVGA which caused an "invalid settings warning to appear. I booted MX anyway and ended up at a 800x600 desktop. However, in the MX Display Settings were all my missing resolution settings. Chose 1366x768 - desktop resized - asked to keep settings - then asked to make them permanent. Upon reboot it is running 1366x768 and somehow VirtualBox reverted to the VMSVGA driver and cleared the invalid settings. One down one to go.
http://www.photomatter.com/2023/Untitled-1.jpg
Re: Two installs have display resolution problems two don't
Posted: Tue Feb 28, 2023 4:56 am
by Eadwine Rose
Image changed to link, please read the forum rules, thanks.
Re: Two installs have display resolution problems two don't
Posted: Tue Feb 28, 2023 4:33 pm
by jmarkus
These left me with a black screen. I will sort the TV box out later.
Huckleberry Finn wrote: Mon Feb 27, 2023 5:07 pm
You can ignore that message.
Code: Select all
echo -e 'nouveau\n\nloop' | sudo tee /etc/modules
Code: Select all
sudo tee /etc/X11/xorg.conf.d/20-nouveau.conf <<!
Section "Device"
Identifier "Device0"
Driver "nouveau"
EndSection
!
(It's normal that the terminal warns you about security, just click "paste" and press enter)
Reboot.
Re: Two installs have display resolution problems two don't
Posted: Tue Feb 28, 2023 4:58 pm
by Huckleberry Finn
You can just delete the /etc/X11/xorg.conf.d/20-nouveau.conf
Either using a live session and the file manager
or first Ctrl+Alt+F1 and then login manually, then
Code: Select all
sudo rm /etc/X11/xorg.conf.d/20-nouveau.conf
Re: Two installs have display resolution problems two don't
Posted: Tue Feb 28, 2023 6:43 pm
by jmarkus
:not found" - still black. I can get to the command line. How can I re-install the safe video driver?
Huckleberry Finn wrote: Tue Feb 28, 2023 4:58 pm
You can just delete the /etc/X11/xorg.conf.d/20-nouveau.conf
Either using a live session and the file manager
or first Ctrl+Alt+F1 and then login manually, then
Code: Select all
sudo rm /etc/X11/xorg.conf.d/20-nouveau.conf
Re: Two installs have display resolution problems two don't
Posted: Tue Feb 28, 2023 7:24 pm
by Huckleberry Finn
Press E on Grub, add nomodeset after quiet splash etc.. press F10 to go on boot.
If it's ok with that, make it permanent: add into "Kernel Parameters" box in "MX Boot Options".
However there's something wrong: It doesn't want Nouveau ...
Re: Two installs have display resolution problems two don't
Posted: Tue Feb 28, 2023 9:04 pm
by jmarkus
btw,Thanks for the all the help Mr Finn.
I tried the nomodeset, but it does not work. Then went immediate to the command line, and line above is saying "Plymouth failed". I thought to just wipe that partition and put a clean install on the drive - problem is it doesn't see the Ubuntu Studio install on the same drive (which works fine).
I really am impressed with the seemly small memory/resource footprint of MX. I really makes old hardware feel snappy again. I have another idea, but I am waiting on an old processor to arrive in the mail to try it. Today I put the 32 bit mx 21.3 on a Shuttle XS35V4 a very low power (15watt) quad core computer the size of a paperback book. Runs great!
Re: Two installs have display resolution problems two don't
Posted: Wed Mar 01, 2023 4:24 am
by Huckleberry Finn
So, you tried
this and it worked?
Or, does it now load Nouveau no matter you tried that or not?
And you installed Grub (which's checked by default) ?
At least nothing to lose to update grub once manually: sudo update-grub
Re: Two installs have display resolution problems two don't
Posted: Wed Mar 01, 2023 4:45 pm
by jmarkus
No it did not work. The TV install on the Shuttle SG31G2 is still broken.
Are there command lines to fix and repair dependencies, broken packages, or to install graphics drivers from the command line/terminal?
At one point I did a search for available nvidia drivers through though the command line. It returned 9 or 10 items. Some were source, some were driver version 340, some had mx21 in their name, and one was driver v390 that the name said it was debian bullseye stable. Earlier I tried the invidia install tool when I could boot to a low resolution GUI - the only option was driver v340. Which I had to undo as the computer became unbootable graphically.
Re: Two installs have display resolution problems two don't
Posted: Thu Mar 02, 2023 1:30 pm
by jmarkus
Closing the book on this one. I tried everything I possibly could to get mx 21.3 32bit working using a Sony 55" TV as the monitor and it refuses to work. Same hardware through Ubuntu Studio v20.04.2 does work - so that is the OS I will use with my music. I tried the nvidia v340 driver again, and v390 plus went back to the nouveau drivers multiple times. I honestly think the TV is the issue. It is suppose to have some kind of ai that optimizes settings, and the type of hdmi settings were changed by the TV multiple times. Thank you everyone for the help.
