Problem with screen resolution using live persistent on multiple devices  [Solved]

Help for Current Versions of MX
When asking for help, use Quick System Info from MX Tools. It will be properly formatted using the following steps.
1. Click on Quick System Info in MX Tools
2. Right click in your post and paste.
Message
Author
travis82
Posts: 9
Joined: Mon Nov 23, 2015 2:35 am

Problem with screen resolution using live persistent on multiple devices

#1 Post by travis82 »

Hi
I decided to use MX live persistent as my production system on home and office machines. There are reasons for this decision that I am not going to explain here. However I have some issues with live persistent.
Putting aside speed related issues that I ask in separate thread, there is a problem concerning screen resolution while using persistence on my machines.
My work system has Nvidia graphic card while my laptop has dual intel-nvidia GPUs. When I use my live USB on laptop, the system offload nouveau and uses Intel GPU for power saving (which I like). If I use persistent mode (either static or dynamic) and then use this usb on my work system, MX loaded with noveau disabled and hence I ended up with low screen resolution on my full hd display.
Is there a permanent solution to have persistence on both machines without this cost?

Thank you in advance and sorry for my English.

Charlie Brown

Re: Problem with screen resolution using live persistent on multiple devices

#2 Post by Charlie Brown »

Was an Nvidia driver installed ?

In fact, a "QSI" from that low res. system would be good.

travis82
Posts: 9
Joined: Mon Nov 23, 2015 2:35 am

Re: Problem with screen resolution using live persistent on multiple devices

#3 Post by travis82 »

Sorry
I posted the OP from my phone. Here is the QSI of my work machine:

Code: Select all

System:
  Kernel: 6.1.0-13-amd64 [6.1.55-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 parameters: persist_all
    quiet splasht nosplash
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm v: 4.18.0 vt: 7
    dm: LightDM v: 1.26.0 Distro: MX-23.1_x64 Libretto July 31  2023 base: Debian GNU/Linux 12
    (bookworm)
Machine:
  Type: Desktop Mobo: ASUSTeK model: P5P41T-LE v: Rev X.0x serial: <superuser required>
    BIOS: American Megatrends v: 0503 date: 07/19/2010
CPU:
  Info: model: Intel Core2 Duo E7500 bits: 64 type: MCP arch: Penryn level: v1 built: 2008
    process: Intel 45nm family: 6 model-id: 0x17 (23) stepping: 0xA (10) microcode: 0xA07
  Topology: cpus: 1x cores: 2 smt: <unsupported> cache: L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB
    L2: 3 MiB desc: 1x3 MiB
  Speed (MHz): avg: 1628 high: 1656 min/max: 1603/2936 scaling: driver: acpi-cpufreq
    governor: ondemand cores: 1: 1656 2: 1600 bogomips: 11736
  Flags: ht lm nx pae sse sse2 sse3 sse4_1 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: KVM: Split huge pages
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT 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_rstack_overflow 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 G98 [GeForce 8400 GS Rev. 2] vendor: XFX Pine driver: nouveau v: kernel
    non-free: series: 340.xx status: legacy (EOL) last: release: 340.108 kernel: 5.4 xorg: 1.20
    arch: Tesla process: 40-80nm built: 2006-13 pcie: gen: 1 speed: 2.5 GT/s lanes: 16 ports:
    active: VGA-1 empty: DVI-I-1 bus-ID: 01:00.0 chip-ID: 10de:06e4 class-ID: 0300 temp: 49.0 C
  Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X:
    loaded: modesetting unloaded: fbdev,vesa dri: nouveau gpu: nouveau display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93")
  Monitor-1: VGA-1 model: LG (GoldStar) E2260 built: 2011 res: 1920x1080 hz: 60 dpi: 102
    gamma: 1.2 size: 477x268mm (18.78x10.55") diag: 547mm (21.5") ratio: 16:9 modes: max: 1920x1080
    min: 720x400
  API: OpenGL v: 3.3 Mesa 22.3.6 renderer: NV98 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 class-ID: 0403
  API: ALSA v: k6.1.0-13-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 0.3.65 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Qualcomm Atheros AR8121/AR8113/AR8114 Gigabit or Fast Ethernet vendor: ASUSTeK P5KPL-CM
    driver: ATL1E v: N/A modules: atl1e pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: ec00
    bus-ID: 02:00.0 chip-ID: 1969:1026 class-ID: 0200
  IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 672.8 GiB used: 266.79 GiB (39.7%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Seagate model: ST3500418AS size: 465.76 GiB block-size:
    physical: 512 B logical: 512 B speed: <unknown> type: HDD rpm: 7200 serial: <filter> rev: CC46
    scheme: MBR
  ID-2: /dev/sdb maj-min: 8:16 vendor: Maxtor model: STM3160215A size: 149.05 GiB block-size:
    physical: 512 B logical: 512 B speed: <unknown> type: N/A serial: <filter> rev: C scheme: MBR
  ID-3: /dev/sdc maj-min: 8:32 type: USB model: 6557 USB DISK 3.0 size: 57.99 GiB block-size:
    physical: 512 B logical: 512 B type: N/A serial: <filter> rev: 2.00 scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
  Message: No partition data found.
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 5 GiB used: 12.1 MiB (0.2%) priority: -2
    file: /live/boot-dev/swap-file
Sensors:
  System Temperatures: cpu: 31.0 C mobo: 29.0 C gpu: nouveau temp: 49.0 C
  Fan Speeds (RPM): cpu: 3245 case-1: 0
  Power: 12v: 12.30 5v: N/A 3.3v: 3.41 vbat: N/A
Repos:
  Packages: pm: dpkg pkgs: 2088 libs: 1048 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 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://archive.debian.petiak.ir/debian bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://archive.debian.petiak.ir/debian bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/microsoft-edge.list
    1: deb [arch=amd64] https://packages.microsoft.com/repos/edge/ stable main
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb https://mirror.23m.com/mx-packages/mx/repo/ bookworm main non-free
Info:
  Processes: 237 Uptime: 3h 9m wakeups: 1 Memory: 7.75 GiB used: 5.72 GiB (73.8%) Init: SysVinit
  v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12 Client: shell wrapper
  v: 5.2.15-release inxi: 3.3.26
Boot Mode: BIOS (legacy, CSM, MBR)
Note that the temporary solution is going to /usr/lib/modprobe.d/video-card-disable.conf file and commenting out this line:

Code: Select all

options nouveau modeset=0
But this file will be rewritten every time that I use persistent mode on my laptop and I need to comment out this line again on my work system and reboot.

Charlie Brown

Re: Problem with screen resolution using live persistent on multiple devices  [Solved]

#4 Post by Charlie Brown »

travis82 wrote: Tue Oct 17, 2023 6:15 am... the temporary solution is going to /usr/lib/modprobe.d/video-card-disable.conf file and commenting out this line: ...
Actually that was the reason why I asked whether an Nvidia driver was installed/removed etc.. for I suspected such a blacklist somewhere.


You can first try:

Code: Select all

nouveau.modeset=1
in boot parameters temporarily: press E on grub (welcome screen) then add (type) it after ... persist_all quiet splasht nosplash

... then press F10 to go on boot. (nothing to worry as this way is just temporary)


... Then... in case it works, you can make it permanent, placing the parameter in "MX Boot Options", or manually editing the grub.cfg file ..


P.S. Yes, different than the line in the file: Note that there's a dot bw. them, when using as a boot parameter.

P.P.S. On the other pc (Intel & Nvidia) that (permanent parameter) won't be a problem I guess, cause it'll go on with Intel no matter the Nouveau driver was loaded/enabled/disabled .

Charlie Brown

Re: Problem with screen resolution using live persistent on multiple devices

#5 Post by Charlie Brown »

travis82 wrote: Tue Oct 17, 2023 6:15 am... /usr/lib/modprobe.d/video-card-disable.conf file and ...
In the meantime: did you create it yourself? No such file by default.

You can even try renaming it to .old (to disable completely) and boot without any additional parameters:

Code: Select all

sudo mv /usr/lib/modprobe.d/video-card-disable.conf{,.old}

travis82
Posts: 9
Joined: Mon Nov 23, 2015 2:35 am

Re: Problem with screen resolution using live persistent on multiple devices

#6 Post by travis82 »

Charlie Brown wrote: Tue Oct 17, 2023 7:25 am
travis82 wrote: Tue Oct 17, 2023 6:15 am... /usr/lib/modprobe.d/video-card-disable.conf file and ...
In the meantime: did you create it yourself? No such file by default.

You can even try renaming it to .old (to disable completely) and boot without any additional parameters:

Code: Select all

sudo mv /usr/lib/modprobe.d/video-card-disable.conf{,.old}
No, I don't create that. I think it's created by my laptop and I want this feature as it prevent energy consumption and overheating due to running both GPUs. And I think renaming this file does't help since when I use persistent on laptop this file will created again. However your solution is a better workaround, at least I don't have to boot to low res screen, edit the file and reboot. I can live with that. Let me test and report.

Thank you so much.

Charlie Brown

Re: Problem with screen resolution using live persistent on multiple devices

#7 Post by Charlie Brown »

Ok, but, meanwhile, nothing to worry about "running both GPUs", cause the 2nd one (Nvidia) will be used when only needed or called by you manually. By default Intel will work alone.

Post Reply

Return to “MX Help”