AVLinux only finds one of three monitors

Help on all MX Re-spins
Forum rules
Post Reply
Message
Author
Huckleberry Finn

Re: AVLinux only finds one of three monitors

#21 Post by Huckleberry Finn »

Boone777 wrote: Sat Dec 24, 2022 9:14 am... my main problems are that I can't change resolution ...
Normal because you have failsafe nomodeset in boot parameters.
Top
Boone777
Posts: 52
Joined: Mon Nov 23, 2020 9:45 am

Re: AVLinux only finds one of three monitors

#22 Post by Boone777 »

Huckleberry Finn wrote: Sat Dec 24, 2022 12:19 pm
Boone777 wrote: Sat Dec 24, 2022 9:14 am... my main problems are that I can't change resolution ...
Normal because you have failsafe nomodeset in boot parameters.
Alright but if I don't I have a black screen so what is the solution ?
Top
Huckleberry Finn

Re: AVLinux only finds one of three monitors

#23 Post by Huckleberry Finn »

You can try (remove the failsafe nomodeset and ... )

Code: Select all

i915.invert_brightness=1
If still not, it may be due to Liquorix kernel. You can try MX (and if that's ok, then MX with 6.0 kernel) if you like, to see ...
Top
Boone777
Posts: 52
Joined: Mon Nov 23, 2020 9:45 am

Re: AVLinux only finds one of three monitors

#24 Post by Boone777 »

Huckleberry Finn wrote: Sat Dec 24, 2022 12:39 pm You can try (remove the failsafe nomodeset and ... )

Code: Select all

i915.invert_brightness=1
If still not, it may be due to Liquorix kernel. You can try MX (and if that's ok, then MX with 6.0 kernel) if you like, to see ...
No it did not work, so what I'm trying to do is bring back the parameter that made it work on my PC I just don't know what to try.
But it did work in the first place so I don't see why this would be a Liquorix problem. It's rather that now the usb is now set to load on my laptop and forgot the parameters needed to work on my PC.
Top
Huckleberry Finn

Re: AVLinux only finds one of three monitors

#25 Post by Huckleberry Finn »

Ok, but different parameters needed for different hardware. For example if you try this on another Intel card machine (that boots normally) then it will be black screen. Or if you try (let's say) xorg=nvidia on an Nvidia machine (or any other card) where Nvidia driver was not installed, then again will cause a black screen. Something like: Any medicine may be so good for you, but can be a poison for someone else.
Top
Boone777
Posts: 52
Joined: Mon Nov 23, 2020 9:45 am

Re: AVLinux only finds one of three monitors

#26 Post by Boone777 »

Huckleberry Finn wrote: Sat Dec 24, 2022 1:59 pm Ok, but different parameters needed for different hardware. For example if you try this on another Intel card machine (that boots normally) then it will be black screen. Or if you try (let's say) xorg=nvidia on an Nvidia machine (or any other card) where Nvidia driver was not installed, then again will cause a black screen. Something like: Any medicine may be so good for you, but can be a poison for someone else.
How about I boot from a fresh install of AVLinux on another usb on my PC and post the info here ? Will we be able to determine what is the default settings that makes it work in the first place ?
Top
Huckleberry Finn

Re: AVLinux only finds one of three monitors

#27 Post by Huckleberry Finn »

That would be good. At least we'll compare a few things.
Top
Boone777
Posts: 52
Joined: Mon Nov 23, 2020 9:45 am

Re: AVLinux only finds one of three monitors

#28 Post by Boone777 »

Huckleberry Finn wrote: Sat Dec 24, 2022 2:18 pm That would be good. At least we'll compare a few things.

Code: Select all

System:    Kernel: 6.0.0-10.1-liquorix-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1 
           parameters: audit=0 intel_pstate=disable hpet=disable rcupdate.rcu_expedited=1 
           BOOT_IMAGE=/antiX/vmlinuz quiet threadirqs nosplash 
           Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm 4.16.1 vt: 7 
           dm: LightDM 1.26.0 Distro: Debian GNU/Linux 11 (bullseye) 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Desktop System: Gigabyte product: N/A v: N/A serial: <filter> Chassis: type: 3 
           serial: <filter> 
           Mobo: Gigabyte model: B75M-D3H serial: <filter> UEFI: American Megatrends v: F13 
           date: 02/27/2013 
CPU:       Info: Quad Core model: Intel Core i7-3770 bits: 64 type: MT MCP arch: Ivy Bridge 
           family: 6 model-id: 3A (58) stepping: 9 microcode: 15 cache: L2: 8 MiB 
           flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 54277 
           Speed: 3901 MHz min/max: 1600/3901 MHz boost: enabled Core speeds (MHz): 1: 3901 
           2: 3885 3: 3901 4: 3901 5: 3901 6: 3901 7: 3901 8: 3901 
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
           Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable 
           Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable 
           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: Vulnerable: No microcode 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel IvyBridge GT2 [HD Graphics 4000] 
           vendor: Gigabyte Xeon E3-1200 v2/3rd Gen Core processor driver: i915 v: kernel 
           bus-ID: 00:02.0 chip-ID: 8086:0162 class-ID: 0380 
           Device-2: NVIDIA GP107 [GeForce GTX 1050 Ti] driver: nouveau v: kernel bus-ID: 01:00.0 
           chip-ID: 10de:1c82 class-ID: 0300 
           Device-3: Cubeternet GL-UPC822 UVC WebCam type: USB driver: uvcvideo bus-ID: 1-1.5.2:8 
           chip-ID: 1e4e:0102 class-ID: 0e02 
           Display: x11 server: X.Org 1.20.14 compositor: compton v: 1 driver: loaded: modesetting 
           unloaded: fbdev,vesa display-ID: :0.0 screens: 1 
           Screen-1: 0 s-res: 3840x1080 s-dpi: 96 s-size: 1016x285mm (40.0x11.2") 
           s-diag: 1055mm (41.5") 
           Monitor-1: DVI-I-1 res: 1920x1080 hz: 60 dpi: 96 size: 509x286mm (20.0x11.3") 
           diag: 584mm (23") 
           Monitor-2: HDMI-3 res: 1920x1080 hz: 60 dpi: 96 size: 509x286mm (20.0x11.3") 
           diag: 584mm (23") 
           OpenGL: renderer: NVCF v: 4.3 Mesa 22.0.5 direct render: Yes 
Audio:     Device-1: Intel 7 Series/C216 Family High Definition Audio vendor: Gigabyte 
           driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:1e20 class-ID: 0403 
           Device-2: NVIDIA GF116 High Definition Audio driver: snd_hda_intel v: kernel 
           bus-ID: 01:00.1 chip-ID: 10de:0bee class-ID: 0403 
           Device-3: BEHRINGER UMC204HD 192k type: USB driver: snd-usb-audio bus-ID: 1-1.2:4 
           chip-ID: 1397:0508 class-ID: fe01 
           Sound Server-1: ALSA v: k6.0.0-10.1-liquorix-amd64 running: yes 
           Sound Server-2: JACK v: 1.9.21 running: no 
           Sound Server-3: PulseAudio v: 14.2 running: yes 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Gigabyte 
           driver: r8169 v: kernel port: d000 bus-ID: 04:00.0 chip-ID: 10ec:8168 class-ID: 0200 
           IF: enp4s0 state: up speed: 100 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 13.19 TiB used: 3.87 GiB (0.0%) 
           SMART Message: Unable to run smartctl. Root privileges required. 
           ID-1: /dev/sda maj-min: 8:0 vendor: KingDian model: S400 480GB size: 447.13 GiB 
           block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> 
           rev: 1A0 scheme: GPT 
           ID-2: /dev/sdb maj-min: 8:16 vendor: Western Digital model: WDS500G2B0A-00SM50 
           size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s type: SSD 
           serial: <filter> rev: 90WD scheme: GPT 
           ID-3: /dev/sdc maj-min: 8:32 vendor: Western Digital model: WDS500G2B0A-00SM50 
           size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s type: SSD 
           serial: <filter> rev: 90WD scheme: GPT 
           ID-4: /dev/sdd maj-min: 8:48 vendor: Toshiba model: DT01ACA200 size: 1.82 TiB 
           block-size: physical: 4096 B logical: 512 B speed: 3.0 Gb/s type: HDD rpm: 7200 
           serial: <filter> rev: ABB0 scheme: MBR 
           ID-5: /dev/sde maj-min: 8:64 type: USB vendor: Toshiba model: HDWD130 size: 2.73 TiB 
           block-size: physical: 4096 B logical: 512 B type: HDD rpm: 7200 serial: <filter> 
           scheme: MBR 
           ID-6: /dev/sdf maj-min: 8:80 type: USB vendor: Toshiba model: HDWR180 size: 7.28 TiB 
           block-size: physical: 4096 B logical: 512 B type: HDD rpm: 7200 serial: <filter> 
           scheme: GPT 
           ID-7: /dev/sdg maj-min: 8:96 type: USB vendor: SanDisk model: Ultra Fit size: 14.32 GiB 
           block-size: physical: 512 B logical: 512 B type: N/A serial: <filter> rev: 1.00 
           scheme: MBR 
           SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure? 
Swap:      Alert: No swap data was found. 
Sensors:   System Temperatures: cpu: 64.0 C mobo: 27.8 C gpu: nouveau temp: 40.0 C 
           Fan Speeds (RPM): N/A gpu: nouveau fan: 1650 
Repos:     Packages: note: see --pkg apt: 2564 lib: 1429 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://mxrepo.com/mx/repo/ bullseye main non-free
           2: deb http://mxrepo.com/mx/repo/ bullseye ahs
Info:      Processes: 257 Uptime: 1m wakeups: 1 Memory: 15.51 GiB used: 919.1 MiB (5.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: UEFI
Top
Huckleberry Finn

Re: AVLinux only finds one of three monitors

#29 Post by Huckleberry Finn »

Boot parameters (other than persist keyboard etc.) are same (though they are used twice on the non-booting one)

The only difference are the usb sticks:

Doesn't boot:

ID-7: /dev/sdg maj-min: 8:96 type: USB vendor: SanDisk model: USB 3.2Gen1
size: 114.61 GiB block-size: physical: 512 B logical: 512 B type: N/A serial: <filter>
rev: 1.00 scheme: MBR

Boots:

ID-7: /dev/sdg maj-min: 8:96 type: USB vendor: SanDisk model: Ultra Fit size: 14.32 GiB
block-size: physical: 512 B logical: 512 B type: N/A serial: <filter> rev: 1.00
scheme: MBR


Since it's a persistent one: Do you remember creating any .conf files in /etc/X11/xorg.conf.d/ ?
In the meantime if there is such a file just delete it: /etc/X11/xorg.conf

Maybe you tried MX Tweak and it created such a file: /etc/X11/xorg.conf.d/20-intel.conf (that tells the system to use Intel instead of modesetting)

Consequently: It must be such a thing cause the persistent usb boots if you use nomodeset. If it wasn't booting no matter what you do, then we would say the culprit was the usb stick..
Top
Boone777
Posts: 52
Joined: Mon Nov 23, 2020 9:45 am

Re: AVLinux only finds one of three monitors

#30 Post by Boone777 »

There is 2 files in /etc/X11/xorg.conf.d/ : 10-evdev.conf and 20-synaptics.conf

There is this one xorg.conf file in X11:


#-----------------------------------------------------------------------------
# xorg.conf file
#
# Generated by make-xorg-conf sometime around Sat Dec 24 16:19:49 EST 2022
#
# If you want to save customizations, delete the line above or this
# file will get automatically deleted on the next live boot.
#
# Command line parameters: --output=/etc/X11/xorg.conf fbdev
#-----------------------------------------------------------------------------

Section "Device"
Identifier "Device0"
Driver "fbdev"
EndSection
Top
Post Reply

Return to “MX Respins”