Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux? |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
02-09-2021, 01:50 PM
|
#1
|
Member
Registered: Jul 2012
Posts: 66
Rep: 
|
Cannot change default screen resolution in Arch
Hello everyone,
Here's the problem: I recently bought LG's FullHD Monitor/TV. I am using Arch Linux with NVIDIA Corporation GF119 [GeForce GT 610] display adapter. (Adapter type acquired from lspci). Hardware is HP Pavillion, quite old version. Original monitor can display 1600xsomething.
When I switched to this monitor Arch somehow detected default screen resolution at start and limited maximum resolution to 1024x768. I have tried original monitor after that and it can still manage 1600xsomething.
xrandr gives the following:
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 640 x 480, current 1024 x 768, maximum 1024 x 768
default connected primary 1024x768+0+0 0mm x 0mm
1024x768 0.00*
800x600 0.00
640x480 0.00
lspci gives the following:
00:00.0 RAM memory: NVIDIA Corporation MCP61 Memory Controller (rev a1)
00:01.0 ISA bridge: NVIDIA Corporation MCP61 LPC Bridge (rev a2)
00:01.1 SMBus: NVIDIA Corporation MCP61 SMBus (rev a2)
00:01.2 RAM memory: NVIDIA Corporation MCP61 Memory Controller (rev a2)
00:02.0 USB controller: NVIDIA Corporation MCP61 USB 1.1 Controller (rev a3)
00:02.1 USB controller: NVIDIA Corporation MCP61 USB 2.0 Controller (rev a3)
00:04.0 PCI bridge: NVIDIA Corporation MCP61 PCI bridge (rev a1)
00:05.0 Audio device: NVIDIA Corporation MCP61 High Definition Audio (rev a2)
00:06.0 IDE interface: NVIDIA Corporation MCP61 IDE (rev a2)
00:07.0 Bridge: NVIDIA Corporation MCP61 Ethernet (rev a2)
00:08.0 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2)
00:08.1 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2)
00:09.0 PCI bridge: NVIDIA Corporation MCP61 PCI Express bridge (rev a2)
00:0b.0 PCI bridge: NVIDIA Corporation MCP61 PCI Express bridge (rev a2)
00:0c.0 PCI bridge: NVIDIA Corporation MCP61 PCI Express bridge (rev a2)
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:05.0 FireWire (IEEE 1394): LSI Corporation FW322/323 [TrueFire] 1394a Controller (rev 70)
02:00.0 VGA compatible controller: NVIDIA Corporation GF119 [GeForce GT 610] (rev a1)
02:00.1 Audio device: NVIDIA Corporation GF119 HDMI Audio Controller (rev a1)
How can I change default resolution to Full HD? LG's specs in Internet mention possibility of 1920x1980.
Yours
Kimmo
Last edited by kkoistinen; 02-09-2021 at 01:54 PM.
|
|
|
02-09-2021, 02:28 PM
|
#2
|
LQ Sage
Registered: Nov 2004
Location: Saint Amant, Acadiana
Distribution: Gentoo ~amd64
Posts: 7,675
Rep: 
|
You need to load correct driver for it, otherwise it will fall back to a generic driver, this is what is happening right now. Follow your distro Wiki, all distros have articles about Xorg configuration.
|
|
|
02-10-2021, 02:30 AM
|
#3
|
LQ Guru
Registered: Aug 2016
Location: SE USA
Distribution: openSUSE 24/7; Debian, Knoppix, Mageia, Fedora, OS/2, others
Posts: 6,522
|
Far more often than not, in any mainstream distro from the past decade, X will automagically configure on the fly. When X fails, Xorg.0.log in /var/log/ should be inspected for errors that constitute clues to what is wrong. If Xorg.0.log is absent in /var/log/, look for /var/log/Xorg.1.log, and for Xorg.0.log in ~/.local/share/xorg/, if you find them all, the one with the most recent timestamp should be inspected. If you need help understanding what it contains, upload it to http://paste.debian.net/ this way:
Code:
pastebinit /var/log/Xorg.0.log
Provide the resulting URL and someone here should be able to interpret it. Of course, only upload the appropriate instance if you found more than one.
The following should roughly match your PC's X, once things are working as they should:
Code:
# inxi -SGIay
System:
Host: big41 Kernel: 5.10.0-2-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1...
Desktop: Trinity R14.0.10 tk: Qt 3.5.0 info: kicker wm: Twin 3.0 dm: TDM
Distro: Debian GNU/Linux bullseye/sid
Graphics:
Device-1: NVIDIA GF108 [GeForce GT 630] vendor: Gigabyte driver: nouveau
v: kernel bus ID: 01:00.0 chip ID: 10de:0f00 class ID: 0300
Display: x11 server: X.Org 1.20.10 driver: loaded: modesetting
unloaded: fbdev,vesa display ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1200 s-dpi: 108 s-size: 451x282mm (17.8x11.1")
s-diag: 532mm (20.9")
Monitor-1: HDMI-1 res: 1920x1200 hz: 60 dpi: 94 size: 519x324mm (20.4x12.8")
diag: 612mm (24.1")
OpenGL: renderer: NVC1 v: 4.3 Mesa 20.3.3 direct render: Yes
Info:,,,Shell: Bash v: 5.1.4 running in: konsole inxi: 3.3.01
# xrandr | head -n12
Screen 0: minimum 320 x 200, current 1920 x 1200, maximum 16384 x 16384
DVI-I-1 disconnected primary (normal left inverted right x axis y axis)
HDMI-1 connected 1920x1200+0+0 (normal left inverted right x axis y axis) 519mm x 324mm
1920x1200 59.95*+
1920x1080 59.96 60.00 59.94 59.93
1600x1200 60.00
1680x1050 59.95 59.88
1600x1024 60.17
1400x1050 59.98 59.95
1600x900 59.95 59.82
1280x1024 60.02
1440x900 59.89 59.90
# lsmod | egrep 'veau|drm' | sort
button 24576 1 nouveau
cec 61440 1 drm_kms_helper
drm 618496 5 drm_kms_helper,ttm,nouveau
drm_kms_helper 274432 1 nouveau
i2c_algo_bit 16384 1 nouveau
mxm_wmi 16384 1 nouveau
nouveau 2326528 2
ttm 114688 1 nouveau
video 53248 1 nouveau
wmi 36864 2 mxm_wmi,nouveau
Note there are two drivers listed in inxi output. The first is the kernel's device driver, in this case named nouveau, specific to NVidia GPUs. Kernel device drivers are provided with each specific kernel.
The second driver listed is the Xorg DDX driver, named Modesetting. All the competent FOSS Xorg DDX drivers depend on Kernel Mode-Setting from the kernel driver. The Modesetting DDX is the upstream default DDX for all non-ancient AMD/ATI, Intel and NVidia GPUs. An optional/alternate DDX for your 610 is named Nouveau, an older, and reverse-engineered technology. If anything prevents the kernel's Nouveau driver, as in the lsmod output above, from loading, no competent DDX driver will load, and one of two crude fallback drivers, FBDEV or VESA, will usually be employed, with a common result being what you're experiencing, resolution limited to 1024x768. Xorg.0.log will report which DDX is in use.
Another alternate Xorg driver for your 610 would be a legacy version of proprietary NVidia drivers. Special instructions for their installation and use are normally provided with them.
Yours is a somewhat unusual situation. It's common for motherboards with MCP61 chipsets to produce trouble with graphics device selection, unlike most others that automatically prefer the add-in GPU to the onboard IGP (GPU). You may need to change a BIOS setting to engage the 610 GPU instead of the onboard. You might also need to update the motherboard BIOS to make the 610 preferred.
So, check your BIOS, then let us have a look at Xorg.0.log, and inxi and lsmod output. The latter two should be copied and pasted here surrounding them with code tags.
|
|
1 members found this post helpful.
|
02-10-2021, 12:32 PM
|
#4
|
Member
Registered: Jul 2012
Posts: 66
Original Poster
Rep: 
|
Hi,
and thank you all for helping me out with this one. For starters some information about my computer. It is an old HP Pavillion with default/recommended screen resolution of 1600x1020. When I start Linux (my distro is Arch) with old monitor it switches nicely to 1600x1020. Anyway here is link to Xorg.0.log:
https://paste.debian.net/1184946/
I couldn't get inxi running (command not found). However lsmod is as follows
Code:
Module Size Used by
ccm 20480 3
rtl8xxxu 143360 0
rtl8192cu 94208 0
rtl_usb 24576 1 rtl8192cu
rtl8192c_common 69632 1 rtl8192cu
snd_hda_codec_realtek 143360 1
rtlwifi 131072 3 rtl8192c_common,rtl_usb,rtl8192cu
snd_hda_codec_generic 98304 1 snd_hda_codec_realtek
mac80211 1110016 4 rtl_usb,rtl8192cu,rtlwifi,rtl8xxxu
ledtrig_audio 16384 1 snd_hda_codec_generic
snd_hda_codec_hdmi 73728 1
snd_hda_intel 57344 3
snd_intel_dspcfg 24576 1 snd_hda_intel
powernow_k8 36864 0
soundwire_intel 45056 1 snd_intel_dspcfg
cfg80211 987136 3 rtlwifi,mac80211,rtl8xxxu
soundwire_generic_allocation 16384 1 soundwire_intel
edac_mce_amd 32768 0
soundwire_cadence 36864 1 soundwire_intel
snd_hda_codec 172032 4 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek
rfkill 28672 4 cfg80211
libarc4 16384 1 mac80211
snd_hda_core 106496 5 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek
ccp 118784 0
snd_hwdep 16384 1 snd_hda_codec
rng_core 16384 1 ccp
soundwire_bus 90112 3 soundwire_intel,soundwire_generic_allocation,soundwire_cadence
kvm 933888 0
drm_kms_helper 274432 0
snd_soc_core 323584 1 soundwire_intel
mousedev 24576 0
snd_compress 32768 1 snd_soc_core
irqbypass 16384 1 kvm
cec 69632 1 drm_kms_helper
ac97_bus 16384 1 snd_soc_core
syscopyarea 16384 1 drm_kms_helper
sysfillrect 16384 1 drm_kms_helper
sysimgblt 16384 1 drm_kms_helper
mac_hid 16384 0
forcedeth 81920 0
snd_pcm_dmaengine 16384 1 snd_soc_core
fb_sys_fops 16384 1 drm_kms_helper
pcspkr 16384 0
snd_pcm 147456 8 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,soundwire_intel,snd_compress,snd_soc_core,snd_hda_core,snd_pcm_dmaengine
snd_timer 45056 1 snd_pcm
snd 114688 16 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_compress,snd_soc_core,snd_pcm
soundcore 16384 1 snd
i2c_nforce2 20480 0
k8temp 16384 0
sg 40960 0
crypto_user 20480 0
drm 569344 1 drm_kms_helper
fuse 163840 5
agpgart 53248 1 drm
bpf_preload 16384 0
ip_tables 32768 0
x_tables 53248 1 ip_tables
ext4 933888 1
crc32c_generic 16384 2
crc16 16384 1 ext4
mbcache 16384 1 ext4
jbd2 151552 1 ext4
uas 32768 0
usb_storage 81920 1 uas
sr_mod 28672 0
cdrom 77824 1 sr_mod
hid_chicony 16384 0
usbhid 65536 0
firewire_ohci 45056 0
firewire_core 81920 1 firewire_ohci
ata_generic 16384 0
pata_acpi 16384 0
crc_itu_t 16384 1 firewire_core
pata_amd 24576 0
sata_nv 32768 1
My guess is that this new monitor doesn't recognize HP's recommended screen resolution and therefore it changes to lower. This recommended resolution pops up once I turn computer on.
I will post more information if required. BIOS isn't configured to onboard and is as PCI with options for PCI-16 and PCI-1. I tried all options but nothing helped with this problem.
Yours
Kimmo
Last edited by kkoistinen; 02-10-2021 at 12:57 PM.
|
|
|
02-11-2021, 06:05 AM
|
#5
|
LQ Guru
Registered: Jan 2006
Location: Ireland
Distribution: Slackware, Slarm64 & Android
Posts: 17,605
|
Quote:
Originally Posted by kkoistinen
screen resolution of 1600x1020
|
That's hardly correct. Screen resolutions are 16:9 (e.g. 1600x900) or in older stuff, 4:3 as in 1600x1200.
So X will hardly have a mode for 1600x1020. Try 1600x900. Let us know how it looks. I don't think 4:3 monitors went as high res as 1600x1200. The biggest they went was 1280x960, iirc.
|
|
|
02-11-2021, 07:34 AM
|
#6
|
LQ Sage
Registered: Nov 2004
Location: Saint Amant, Acadiana
Distribution: Gentoo ~amd64
Posts: 7,675
Rep: 
|
Log shows what I suspected, Xorg is falling back to VESA.
Code:
(EE) open /dev/dri/card0: No such file or directory
And this is the reason, kernel driver for your graphics card is not loaded and as a result Xorg cannot use correct driver, using generic VESA instead.
|
|
|
02-11-2021, 10:22 AM
|
#7
|
LQ Guru
Registered: Aug 2016
Location: SE USA
Distribution: openSUSE 24/7; Debian, Knoppix, Mageia, Fedora, OS/2, others
Posts: 6,522
|
Quote:
Originally Posted by business_kid
I don't think 4:3 monitors went as high res as 1600x1200. The biggest they went was 1280x960, iirc.
|
From Xorg.0.log on one of several I owned that supported up to 2048x1536:
Code:
[ 9513.566] (II) intel(0): EDID for output VGA1
[ 9513.566] (II) intel(0): Manufacturer: SNY Model: 7b0 Serial#: 8047359
[ 9513.566] (II) intel(0): Year: 2002 Week: 31
[ 9513.566] (II) intel(0): EDID Version: 1.3
[ 9513.566] (II) intel(0): Analog Display Input, Input Voltage Level: 0.700/0.300 V
[ 9513.566] (II) intel(0): Sync: Separate Composite SyncOnGreen
[ 9513.566] (II) intel(0): Max Image Size [cm]: horiz.: 40 vert.: 30
[ 9513.566] (II) intel(0): Gamma: 2.50
[ 9513.566] (II) intel(0): DPMS capabilities: Off; RGB/Color Display
[ 9513.566] (II) intel(0): First detailed timing is preferred mode
[ 9513.566] (II) intel(0): GTF timings supported
[ 9513.566] (II) intel(0): redX: 0.625 redY: 0.340 greenX: 0.280 greenY: 0.605
[ 9513.566] (II) intel(0): blueX: 0.155 blueY: 0.070 whiteX: 0.283 whiteY: 0.298
[ 9513.566] (II) intel(0): Supported established timings:
[ 9513.566] (II) intel(0): 720x400@70Hz
[ 9513.566] (II) intel(0): 720x400@88Hz
[ 9513.566] (II) intel(0): 640x480@60Hz
[ 9513.566] (II) intel(0): 640x480@67Hz
[ 9513.566] (II) intel(0): 640x480@72Hz
[ 9513.566] (II) intel(0): 640x480@75Hz
[ 9513.566] (II) intel(0): 800x600@56Hz
[ 9513.566] (II) intel(0): 800x600@60Hz
[ 9513.566] (II) intel(0): 800x600@72Hz
[ 9513.566] (II) intel(0): 800x600@75Hz
[ 9513.566] (II) intel(0): 832x624@75Hz
[ 9513.566] (II) intel(0): 1024x768@87Hz (interlaced)
[ 9513.566] (II) intel(0): 1024x768@60Hz
[ 9513.566] (II) intel(0): 1024x768@70Hz
[ 9513.566] (II) intel(0): 1024x768@75Hz
[ 9513.566] (II) intel(0): 1280x1024@75Hz
[ 9513.566] (II) intel(0): 1152x864@75Hz
[ 9513.566] (II) intel(0): Manufacturer's mask: 0
[ 9513.566] (II) intel(0): Supported standard timings:
[ 9513.566] (II) intel(0): #0: hsize: 2048 vsize 1536 refresh: 75 vid: 20449
[ 9513.566] (II) intel(0): #1: hsize: 1920 vsize 1440 refresh: 85 vid: 22993
[ 9513.566] (II) intel(0): #2: hsize: 1600 vsize 1200 refresh: 85 vid: 22953
[ 9513.566] (II) intel(0): #3: hsize: 1280 vsize 1024 refresh: 85 vid: 39297
[ 9513.566] (II) intel(0): #4: hsize: 1152 vsize 864 refresh: 85 vid: 22897
[ 9513.566] (II) intel(0): #5: hsize: 1024 vsize 768 refresh: 85 vid: 22881
[ 9513.566] (II) intel(0): #6: hsize: 800 vsize 600 refresh: 85 vid: 22853
[ 9513.566] (II) intel(0): #7: hsize: 1280 vsize 960 refresh: 75 vid: 20353
Other resolutions I recall using include1856x1392, 1800x1350 and 1792x1344.
|
|
|
02-11-2021, 10:26 AM
|
#8
|
LQ Guru
Registered: Aug 2016
Location: SE USA
Distribution: openSUSE 24/7; Debian, Knoppix, Mageia, Fedora, OS/2, others
Posts: 6,522
|
Quote:
Originally Posted by kkoistinen
My guess is that this new monitor doesn't recognize HP's recommended screen resolution and therefore it changes to lower. This recommended resolution pops up once I turn computer on.
|
Most distros provide inxi by default. You can get it here.
The error message in Xorg.0.log (EE) open /dev/dri/card0: No such file or directory is fatal to competent FOSS Xorg DDX driver operation. The modesetting DDX driver loads, but cannot be used. Thus, Xorg falls back on the VESA driver, which does not support your display's native resolution.
Did you build your own kernel? lsmod output shows the nouveau kernel driver did not load. This will cause absence of /dev/dri/card0. If you build your own kernel, you must make sure nouveau is either built-in or built as a loadable module.
The nouveau kernel driver also may not load because it has been blacklisted, an occurrence typical of an installation of one of NVidia's proprietary graphics drivers. It can remain so even after uninstallation if uninstallation instructions are not followed to the letter.
|
|
|
02-12-2021, 04:20 AM
|
#9
|
LQ Guru
Registered: Jan 2006
Location: Ireland
Distribution: Slackware, Slarm64 & Android
Posts: 17,605
|
Quote:
Originally Posted by mrmazda
From Xorg.0.log on one of several I owned that supported up to 2048x1536:
Code:
[ 9513.566] (II) intel(0): EDID for output VGA1
[ 9513.566] (II) intel(0): Manufacturer: SNY Model: 7b0 Serial#: 8047359
[ 9513.566] (II) intel(0): Year: 2002 Week: 31
[ 9513.566] (II) intel(0): EDID Version: 1.3
[ 9513.566] (II) intel(0): Analog Display Input, Input Voltage Level: 0.700/0.300 V
[ 9513.566] (II) intel(0): Sync: Separate Composite SyncOnGreen
[ 9513.566] (II) intel(0): Max Image Size [cm]: horiz.: 40 vert.: 30
[ 9513.566] (II) intel(0): Gamma: 2.50
[ 9513.566] (II) intel(0): DPMS capabilities: Off; RGB/Color Display
[ 9513.566] (II) intel(0): First detailed timing is preferred mode
[ 9513.566] (II) intel(0): GTF timings supported
[ 9513.566] (II) intel(0): redX: 0.625 redY: 0.340 greenX: 0.280 greenY: 0.605
[ 9513.566] (II) intel(0): blueX: 0.155 blueY: 0.070 whiteX: 0.283 whiteY: 0.298
[ 9513.566] (II) intel(0): Supported established timings:
[ 9513.566] (II) intel(0): 720x400@70Hz
[ 9513.566] (II) intel(0): 720x400@88Hz
[ 9513.566] (II) intel(0): 640x480@60Hz
[ 9513.566] (II) intel(0): 640x480@67Hz
[ 9513.566] (II) intel(0): 640x480@72Hz
[ 9513.566] (II) intel(0): 640x480@75Hz
[ 9513.566] (II) intel(0): 800x600@56Hz
[ 9513.566] (II) intel(0): 800x600@60Hz
[ 9513.566] (II) intel(0): 800x600@72Hz
[ 9513.566] (II) intel(0): 800x600@75Hz
[ 9513.566] (II) intel(0): 832x624@75Hz
[ 9513.566] (II) intel(0): 1024x768@87Hz (interlaced)
[ 9513.566] (II) intel(0): 1024x768@60Hz
[ 9513.566] (II) intel(0): 1024x768@70Hz
[ 9513.566] (II) intel(0): 1024x768@75Hz
[ 9513.566] (II) intel(0): 1280x1024@75Hz
[ 9513.566] (II) intel(0): 1152x864@75Hz
[ 9513.566] (II) intel(0): Manufacturer's mask: 0
[ 9513.566] (II) intel(0): Supported standard timings:
[ 9513.566] (II) intel(0): #0: hsize: 2048 vsize 1536 refresh: 75 vid: 20449
[ 9513.566] (II) intel(0): #1: hsize: 1920 vsize 1440 refresh: 85 vid: 22993
[ 9513.566] (II) intel(0): #2: hsize: 1600 vsize 1200 refresh: 85 vid: 22953
[ 9513.566] (II) intel(0): #3: hsize: 1280 vsize 1024 refresh: 85 vid: 39297
[ 9513.566] (II) intel(0): #4: hsize: 1152 vsize 864 refresh: 85 vid: 22897
[ 9513.566] (II) intel(0): #5: hsize: 1024 vsize 768 refresh: 85 vid: 22881
[ 9513.566] (II) intel(0): #6: hsize: 800 vsize 600 refresh: 85 vid: 22853
[ 9513.566] (II) intel(0): #7: hsize: 1280 vsize 960 refresh: 75 vid: 20353
Other resolutions I recall using include1856x1392, 1800x1350 and 1792x1344.
|
I see. I don't claim Ireland was at the cutting edge here. We're pretty well there now. In any case, he was using a 1600x1020 resolution that was neither 4:3 or 16:9, and as you pointed out, using a (4:3)vesa driver.
|
|
|
02-12-2021, 06:02 AM
|
#10
|
Member
Registered: Jul 2012
Posts: 66
Original Poster
Rep: 
|
Quote:
The error message in Xorg.0.log (EE) open /dev/dri/card0: No such file or directory is fatal to competent FOSS Xorg DDX driver operation. The modesetting DDX driver loads, but cannot be used. Thus, Xorg falls back on the VESA driver, which does not support your display's native resolution.
|
Thank you for helping me out with this one. So what should I do? I have tried pacman -S nvidia but that doesn't change things.
Yours
Kimmo
|
|
|
02-12-2021, 06:38 AM
|
#11
|
LQ Sage
Registered: Nov 2004
Location: Saint Amant, Acadiana
Distribution: Gentoo ~amd64
Posts: 7,675
Rep: 
|
Check out why kernel driver is defunct and fix it, of course.
|
|
|
02-12-2021, 06:54 AM
|
#12
|
Member
Registered: Jul 2012
Posts: 66
Original Poster
Rep: 
|
Quote:
Originally Posted by Emerson
Check out why kernel driver is defunct and fix it, of course.
|
Ok I'll see what I can do. Apparently nVidia driver is corrupted.
Last edited by kkoistinen; 02-12-2021 at 07:08 AM.
|
|
|
02-12-2021, 07:14 AM
|
#13
|
LQ Sage
Registered: Nov 2004
Location: Saint Amant, Acadiana
Distribution: Gentoo ~amd64
Posts: 7,675
Rep: 
|
Well, the Xorg log has expired in pastebin by now, I do not recall seeing any nvidia driver load attempt there, but I may not remember correctly. You are very different person, for me it is a matter of minutes, check Xorg log, see the problem, check dmesg, see the problem, fix it. You seem to have all the time in the world, it has been days now.
|
|
|
02-17-2021, 01:10 PM
|
#14
|
Member
Registered: Jul 2012
Posts: 66
Original Poster
Rep: 
|
Hello,
I reinstalled Arch and now monitor is working. Thank you for help.
Yours
Kimmo
|
|
|
All times are GMT -5. The time now is 09:50 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|