Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #230493 > unrolled thread
| Started by | Dennis Wicks <wix@mgssub.com> |
|---|---|
| First post | 2021-01-09 22:10 +0100 |
| Last post | 2021-01-10 17:20 +0100 |
| Articles | 15 — 5 participants |
Back to article view | Back to linux.debian.user
Monitor resolution wrong Dennis Wicks <wix@mgssub.com> - 2021-01-09 22:10 +0100
Re: Monitor resolution wrong Felix Miata <mrmazda@earthlink.net> - 2021-01-09 22:40 +0100
Re: Monitor resolution wrong Dennis Wicks <wix@mgssub.com> - 2021-01-10 00:20 +0100
Re: Monitor resolution wrong "Alexander V. Makartsev" <avbetev@gmail.com> - 2021-01-10 01:30 +0100
Re: Monitor resolution wrong Dennis Wicks <wix@mgssub.com> - 2021-01-10 02:40 +0100
Re: Monitor resolution wrong Felix Miata <mrmazda@earthlink.net> - 2021-01-10 02:30 +0100
Re: Monitor resolution wrong "Alexander V. Makartsev" <avbetev@gmail.com> - 2021-01-10 10:40 +0100
Re: Monitor resolution wrong Felix Miata <mrmazda@earthlink.net> - 2021-01-10 11:50 +0100
Re: Monitor resolution wrong "Alexander V. Makartsev" <avbetev@gmail.com> - 2021-01-10 15:10 +0100
Re: Monitor resolution wrong Felix Miata <mrmazda@earthlink.net> - 2021-01-10 18:20 +0100
Re: Monitor resolution wrong "Alexander V. Makartsev" <avbetev@gmail.com> - 2021-01-11 00:40 +0100
Re: Monitor resolution wrong Felix Miata <mrmazda@earthlink.net> - 2021-01-11 01:30 +0100
Re: Monitor resolution wrong Felix Miata <mrmazda@earthlink.net> - 2021-01-11 01:40 +0100
Re: Monitor resolution wrong The Wanderer <wanderer@fastmail.fm> - 2021-01-11 01:50 +0100
Re: Monitor resolution wrong Andrei POPESCU <andreimpopescu@gmail.com> - 2021-01-10 17:20 +0100
| From | Dennis Wicks <wix@mgssub.com> |
|---|---|
| Date | 2021-01-09 22:10 +0100 |
| Subject | Monitor resolution wrong |
| Message-ID | <BvtEJ-4gx-13@gated-at.bofh.it> |
Greetings; When I boot kernel 4.19.0-13-amd64 my monitor res is 1024x768. It should be 1680x1050 which I get when I boot into kernel 4.19.0-12-amd64. Also, when I look at the xfce display settings when I have -13 booted it has some generic display listed and only the 1024x768 res. When I am booted in -12 the display is listed as an LG 23", which it is, and a bunch of different resolutions that could be used. I have tried rebuilding the kernel and initrd to no avail. It looks to me like the kernel is not recognizing the monitor for some reason but beyond that I haven't the slightest idea as to where to look! Any ideas?? Many TIA!! Dennis
[toc] | [next] | [standalone]
| From | Felix Miata <mrmazda@earthlink.net> |
|---|---|
| Date | 2021-01-09 22:40 +0100 |
| Message-ID | <Bvu7M-4q6-21@gated-at.bofh.it> |
| In reply to | #230493 |
Dennis Wicks composed on 2021-01-09 15:00 (UTC-0600): > When I boot kernel 4.19.0-13-amd64 my monitor res is > 1024x768. It should be 1680x1050 which I get when I boot > into kernel 4.19.0-12-amd64. Also, when I look at the xfce > display settings when I have -13 booted it has some generic > display listed and only the 1024x768 res. When I am booted > in -12 the display is listed as an LG 23", which it is, and > a bunch of different resolutions that could be used. > I have tried rebuilding the kernel and initrd to no avail. > It looks to me like the kernel is not recognizing the > monitor for some reason but beyond that I haven't the > slightest idea as to where to look! This situation is often a case of missing firmware, but it's unusual that it happens simply due to a minor kernel upgrade. Please upload /var/log/Xorg.0.log from a -13 boot to http://pastebin.com/ or equivalent, and provide here the resulting URL, so that we may try to determine what is happening. Also please paste here output from: 'inxi -GSa', for similar reason. -- Evolution as taught in public schools, like religion, is based on faith, not on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
[toc] | [prev] | [next] | [standalone]
| From | Dennis Wicks <wix@mgssub.com> |
|---|---|
| Date | 2021-01-10 00:20 +0100 |
| Message-ID | <BvvGx-5ue-1@gated-at.bofh.it> |
| In reply to | #230495 |
[Multipart message — attachments visible in raw view] — view raw
Felix Miata wrote on 1/9/21 3:33 PM:
> Dennis Wicks composed on 2021-01-09 15:00 (UTC-0600):
>
>> When I boot kernel 4.19.0-13-amd64 my monitor res is
>> 1024x768. It should be 1680x1050 which I get when I boot
>> into kernel 4.19.0-12-amd64. Also, when I look at the xfce
>> display settings when I have -13 booted it has some generic
>> display listed and only the 1024x768 res. When I am booted
>> in -12 the display is listed as an LG 23", which it is, and
>> a bunch of different resolutions that could be used.
>
>> I have tried rebuilding the kernel and initrd to no avail.
>> It looks to me like the kernel is not recognizing the
>> monitor for some reason but beyond that I haven't the
>> slightest idea as to where to look!
>
> This situation is often a case of missing firmware, but it's unusual that it
> happens simply due to a minor kernel upgrade. Please upload /var/log/Xorg.0.log
> from a -13 boot to http://pastebin.com/ or equivalent, and provide here the
> resulting URL, so that we may try to determine what is happening. Also please
> paste here output from: 'inxi -GSa', for similar reason.
>
The log file is in pastebin at
wix-Xorg.0.log
The output from inxi is attached,and pasted below, for both
-12 and -13. There is a difference between them!
System: Host: ichiban Kernel: 4.19.0-12-amd64 x86_64
bits: 64 Desktop: Xfce 4.12.4 Distro: Debian GNU/Linux 10
(buster)
Graphics: Device-1: NVIDIA GK208 [GeForce GT 710B] driver:
nouveau v: kernel
Display: x11 server: X.Org 1.20.4 driver:
modesetting unloaded: fbdev,vesa resolution: 1680x1050~60Hz
OpenGL: renderer: NV106 v: 4.3 Mesa 18.3.6
System: Host: ichiban Kernel: 4.19.0-13-amd64 x86_64
bits: 64 Desktop: Xfce 4.12.4 Distro: Debian GNU/Linux 10
(buster)
Graphics: Device-1: NVIDIA GK208 [GeForce GT 710B] driver:
nvidia v: 418.152.00
Display: x11 server: X.Org 1.20.4 driver:
nouveau unloaded: fbdev,modesetting,vesa resolution:
1024x768~76Hz
OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits)
v: 3.3 Mesa 18.3.6
Many TIA, again!
Dennis
[toc] | [prev] | [next] | [standalone]
| From | "Alexander V. Makartsev" <avbetev@gmail.com> |
|---|---|
| Date | 2021-01-10 01:30 +0100 |
| Message-ID | <BvwMh-6q2-9@gated-at.bofh.it> |
| In reply to | #230503 |
[Multipart message — attachments visible in raw view] — view raw
On 10.01.2021 04:08, Dennis Wicks wrote: > Felix Miata wrote on 1/9/21 3:33 PM: >> Dennis Wicks composed on 2021-01-09 15:00 (UTC-0600): >> >>> When I boot kernel 4.19.0-13-amd64 my monitor res is >>> 1024x768. It should be 1680x1050 which I get when I boot >>> into kernel 4.19.0-12-amd64. Also, when I look at the xfce >>> display settings when I have -13 booted it has some generic >>> display listed and only the 1024x768 res. When I am booted >>> in -12 the display is listed as an LG 23", which it is, and >>> a bunch of different resolutions that could be used. >> >>> I have tried rebuilding the kernel and initrd to no avail. >>> It looks to me like the kernel is not recognizing the >>> monitor for some reason but beyond that I haven't the >>> slightest idea as to where to look! >> >> This situation is often a case of missing firmware, but it's unusual >> that it >> happens simply due to a minor kernel upgrade. Please upload >> /var/log/Xorg.0.log >> from a -13 boot to http://pastebin.com/ or equivalent, and provide >> here the >> resulting URL, so that we may try to determine what is happening. >> Also please >> paste here output from: 'inxi -GSa', for similar reason. >> > > The log file is in pastebin at > wix-Xorg.0.log > > The output from inxi is attached,and pasted below, for both -12 and > -13. There is a difference between them! > > System: Host: ichiban Kernel: 4.19.0-12-amd64 x86_64 bits: 64 > Desktop: Xfce 4.12.4 Distro: Debian GNU/Linux 10 (buster) > Graphics: Device-1: NVIDIA GK208 [GeForce GT 710B] driver: nouveau v: > kernel > Display: x11 server: X.Org 1.20.4 driver: modesetting > unloaded: fbdev,vesa resolution: 1680x1050~60Hz > OpenGL: renderer: NV106 v: 4.3 Mesa 18.3.6 > > > System: Host: ichiban Kernel: 4.19.0-13-amd64 x86_64 bits: 64 > Desktop: Xfce 4.12.4 Distro: Debian GNU/Linux 10 (buster) > Graphics: Device-1: NVIDIA GK208 [GeForce GT 710B] driver: nvidia v: > 418.152.00 > Display: x11 server: X.Org 1.20.4 driver: nouveau unloaded: > fbdev,modesetting,vesa resolution: 1024x768~76Hz > OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.3 Mesa > 18.3.6 > > Many TIA, again! > Dennis You have installed unsupported nvidia driver version for your VGA. Last version that supports your adapter is 390, so you need to install "nvidia-legacy-390xx-driver". You will need to remove 418 driver after installation, or switch to 390 version by typing: # update-glx --config nvidia to make sure your system will use it. You can use "glxinfo" utility from "mesa-utils" package to see what driver is currently in use. $ glxinfo | grep -e 'OpenGL' -e 'glx' -- With kindest regards, Alexander. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org ⠈⠳⣄⠀⠀⠀⠀
[toc] | [prev] | [next] | [standalone]
| From | Dennis Wicks <wix@mgssub.com> |
|---|---|
| Date | 2021-01-10 02:40 +0100 |
| Message-ID | <BvxS1-71v-3@gated-at.bofh.it> |
| In reply to | #230506 |
Alexander V. Makartsev wrote on 1/9/21 6:22 PM: > On 10.01.2021 04:08, Dennis Wicks wrote: >> Felix Miata wrote on 1/9/21 3:33 PM: >>> Dennis Wicks composed on 2021-01-09 15:00 (UTC-0600): >>> >>>> When I boot kernel 4.19.0-13-amd64 my monitor res is >>>> 1024x768. It should be 1680x1050 which I get when I boot >>>> into kernel 4.19.0-12-amd64. Also, when I look at the xfce >>>> display settings when I have -13 booted it has some generic >>>> display listed and only the 1024x768 res. When I am booted >>>> in -12 the display is listed as an LG 23", which it is, and >>>> a bunch of different resolutions that could be used. >>> >>>> I have tried rebuilding the kernel and initrd to no avail. >>>> It looks to me like the kernel is not recognizing the >>>> monitor for some reason but beyond that I haven't the >>>> slightest idea as to where to look! >>> >>> This situation is often a case of missing firmware, but >>> it's unusual that it >>> happens simply due to a minor kernel upgrade. Please >>> upload /var/log/Xorg.0.log >>> from a -13 boot to http://pastebin.com/ or equivalent, >>> and provide here the >>> resulting URL, so that we may try to determine what is >>> happening. Also please >>> paste here output from: 'inxi -GSa', for similar reason. >>> >> >> The log file is in pastebin at >> wix-Xorg.0.log >> >> The output from inxi is attached,and pasted below, for >> both -12 and -13. There is a difference between them! >> >> System: Host: ichiban Kernel: 4.19.0-12-amd64 x86_64 >> bits: 64 Desktop: Xfce 4.12.4 Distro: Debian GNU/Linux 10 >> (buster) >> Graphics: Device-1: NVIDIA GK208 [GeForce GT 710B] >> driver: nouveau v: kernel >> Display: x11 server: X.Org 1.20.4 driver: >> modesetting unloaded: fbdev,vesa resolution: 1680x1050~60Hz >> OpenGL: renderer: NV106 v: 4.3 Mesa 18.3.6 >> >> >> System: Host: ichiban Kernel: 4.19.0-13-amd64 x86_64 >> bits: 64 Desktop: Xfce 4.12.4 Distro: Debian GNU/Linux 10 >> (buster) >> Graphics: Device-1: NVIDIA GK208 [GeForce GT 710B] >> driver: nvidia v: 418.152.00 >> Display: x11 server: X.Org 1.20.4 driver: >> nouveau unloaded: fbdev,modesetting,vesa resolution: >> 1024x768~76Hz >> OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) >> v: 3.3 Mesa 18.3.6 >> >> Many TIA, again! >> Dennis > You have installed unsupported nvidia driver version for > your VGA. Last version that supports your adapter is 390, so > you need to install "nvidia-legacy-390xx-driver". > You will need to remove 418 driver after installation, or > switch to 390 version by typing: > # update-glx --config nvidia > to make sure your system will use it. You can use "glxinfo" > utility from "mesa-utils" package to see what driver is > currently in use. > $ glxinfo | grep -e 'OpenGL' -e 'glx' > > > > -- > With kindest regards, Alexander. > > ⢀⣴⠾⠻⢶⣦⠀ > ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system > ⢿⡄⠘⠷⠚⠋⠀https://www.debian.org > ⠈⠳⣄⠀⠀⠀⠀ > Alexander; My most fervent and heartfelt thank you! That solved the problem completely. The system crashed on the first try while it was updating the initrd but after I rebooted it worked fine and the remainder of your procedure went smoothly. Again, Thank You! Dennis
[toc] | [prev] | [next] | [standalone]
| From | Felix Miata <mrmazda@earthlink.net> |
|---|---|
| Date | 2021-01-10 02:30 +0100 |
| Message-ID | <BvxIm-6Yz-1@gated-at.bofh.it> |
| In reply to | #230503 |
Dennis Wicks composed on 2021-01-09 17:08 (UTC-0600): > Felix Miata wrote: >> This situation is often a case of missing firmware, but it's unusual that it >> happens simply due to a minor kernel upgrade. Please upload /var/log/Xorg.0.log >> from a -13 boot to http://pastebin.com/ or equivalent, and provide here the >> resulting URL, so that we may try to determine what is happening. Also please >> paste here output from: 'inxi -GSa', for similar reason. > The log file is in pastebin at > wix-Xorg.0.log Not anywhere I could find absent a complete URL. :( > The output from inxi is attached,and pasted below, for both > -12 and -13. There is a difference between them! > System: Host: ichiban Kernel: 4.19.0-12-amd64 x86_64 > bits: 64 Desktop: Xfce 4.12.4 Distro: Debian GNU/Linux 10 > (buster) > Graphics: Device-1: NVIDIA GK208 [GeForce GT 710B] driver: > nouveau v: kernel > Display: x11 server: X.Org 1.20.4 driver: > modesetting unloaded: fbdev,vesa resolution: 1680x1050~60Hz > OpenGL: renderer: NV106 v: 4.3 Mesa 18.3.6 > System: Host: ichiban Kernel: 4.19.0-13-amd64 x86_64 > bits: 64 Desktop: Xfce 4.12.4 Distro: Debian GNU/Linux 10 > (buster) > Graphics: Device-1: NVIDIA GK208 [GeForce GT 710B] driver: > nvidia v: 418.152.00 > Display: x11 server: X.Org 1.20.4 driver: > nouveau unloaded: fbdev,modesetting,vesa resolution: > 1024x768~76Hz > OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) > v: 3.3 Mesa 18.3.6 You are apparently using the ancient inxi provided by Buster. The current version, a mere script, can be had from upstream at: https://smxi.org/docs/inxi-installation.htm#inxi-manual-install What follows is an example of whatall I was hoping for (note the different switches). I don't have full recollection of the many improvements and bug fixes missing from Buster's antique. # xrandr | egrep 'onnect|creen|\*' | grep -v disconn | sort -r Screen 0: minimum 320 x 200, current 2560 x 2280, maximum 16384 x 16384 HDMI-1 connected 2560x1080+0+0 (normal left inverted right x axis y axis) 673mm x 284mm DVI-I-1 connected primary 1920x1200+0+1080 (normal left inverted right x axis y axis) 598mm x 336mm 2560x1080 60.00*+ 1920x1200 59.88* 59.95 # inxi -GISay System: Host: big41 Kernel: 4.19.0-12-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 parameters:...noresume mitigations=auto consoleblank=0 plymouth.enable=0 Desktop: Trinity R14.0.9 tk: Qt 3.5.0 info: kicker wm: Twin 3.0 dm: TDM Distro: Debian GNU/Linux 10 (buster) Graphics: Device-1: NVIDIA GF108 [GeForce GT 630] vendor: Gigabyte driver: nouveau v: kernel bus ID: 01:00.0 chip ID: 10de:0f00 Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa display ID: :0 screens: 1 Screen-1: 0 s-res: 2560x2280 s-dpi: 120 s-size: 541x482mm (21.3x19.0") s-diag: 725mm (28.5") Monitor-1: DVI-I-1 res: 1920x1200 hz: 60 dpi: 82 size: 598x336mm (23.5x13.2") diag: 686mm (27") Monitor-2: HDMI-1 res: 2560x1080 hz: 60 dpi: 97 size: 673x284mm (26.5x11.2") diag: 730mm (28.8") OpenGL: renderer: NVC1 v: 4.3 Mesa 18.3.6 direct render: Yes Info:...Shell: Bash v: 5.0.3 running in: konsole inxi: 3.2.01 # xrandr | egrep 'onnect|creen|\*' | grep -v disconn | sort -r Screen 0: minimum 320 x 200, current 2560 x 2520, maximum 16384 x 16384 HDMI-1 connected 2560x1080+0+0 (normal left inverted right x axis y axis) 673mm x 284mm DVI-I-1 connected primary 2560x1440+0+1080 (normal left inverted right x axis y axis) 598mm x 336mm 2560x1440 59.95*+ 2560x1080 60.00*+ # inxi -GISay System: Host: big41 Kernel: 4.19.0-13-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 parameters:...noresume mitigations=auto consoleblank=0 plymouth.enable=0 Desktop: Trinity R14.0.9 tk: Qt 3.5.0 info: kicker wm: Twin 3.0 dm: TDM Distro: Debian GNU/Linux 10 (buster) Graphics: Device-1: NVIDIA GF108 [GeForce GT 630] vendor: Gigabyte driver: nouveau v: kernel bus ID: 01:00.0 chip ID: 10de:0f00 Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa display ID: :0 screens: 1 Screen-1: 0 s-res: 2560x2520 s-dpi: 120 s-size: 541x532mm (21.3x20.9") s-diag: 759mm (29.9") Monitor-1: DVI-I-1 res: 2560x1440 hz: 60 dpi: 109 size: 598x336mm (23.5x13.2") diag: 686mm (27") Monitor-2: HDMI-1 res: 2560x1080 hz: 60 dpi: 97 size: 673x284mm (26.5x11.2") diag: 730mm (28.8") OpenGL: renderer: NVC1 v: 4.3 Mesa 18.3.6 direct render: Yes Info:...Shell: Bash v: 5.0.3 running in: konsole inxi: 3.2.01 # xrandr | egrep 'onnect|creen|\*' | grep -v disconn | sort -r Screen 0: minimum 320 x 200, current 2560 x 2520, maximum 16384 x 16384 DP-2 connected 2560x1080+0+0 (normal left inverted right x axis y axis) 673mm x 284mm DP-1 connected primary 2560x1440+0+1080 (normal left inverted right x axis y axis) 598mm x 336mm 2560x1440 59.95*+ 2560x1080 60.00*+ # inxi -GISay System: Host: p5bse Kernel: 5.9.0-4-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.0 parameters:...mitigations=auto consoleblank=0 plymouth.enable=0 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 GF119 [NVS 310] vendor: Hewlett-Packard driver: nouveau v: kernel bus ID: 01:00.0 chip ID: 10de:107d Display: x11 server: X.Org 1.20.10 driver: modesetting unloaded: fbdev,vesa display ID: :0 screens: 1 Screen-1: 0 s-res: 2560x2520 s-dpi: 120 s-size: 541x533mm (21.3x21.0") s-diag: 759mm (29.9") Monitor-1: DP-1 res: 2560x1440 hz: 60 dpi: 109 size: 598x336mm (23.5x13.2") diag: 686mm (27") Monitor-2: DP-2 res: 2560x1080 hz: 60 dpi: 97 size: 673x284mm (26.5x11.2") diag: 730mm (28.8") OpenGL: renderer: NVD9 v: 4.3 Mesa 20.2.6 direct render: Yes Info:...Shell: Bash v: 5.1.0 running in: konsole inxi: 3.2.01 Alexander V. Makartsev composed on 2021-01-10 05:22 (UTC+0500): > ...so you need to install "nvidia-legacy-390xx-driver"... Most likely that's false. As you should be able to see above, old NVidia cards don't require tainting software to run X on modern widescreen displays at their native resolutions. Almost certainly all OP /needs/ to do is eradicate the tainting software, and its configuration files, and if applicable, any library modifications its installation created. -- Evolution as taught in public schools, like religion, is based on faith, not on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
[toc] | [prev] | [next] | [standalone]
| From | "Alexander V. Makartsev" <avbetev@gmail.com> |
|---|---|
| Date | 2021-01-10 10:40 +0100 |
| Message-ID | <BvFmx-36m-11@gated-at.bofh.it> |
| In reply to | #230511 |
[Multipart message — attachments visible in raw view] — view raw
On 10.01.2021 06:27, Felix Miata wrote: > Alexander V. Makartsev composed on 2021-01-10 05:22 (UTC+0500): > >> ...so you need to install "nvidia-legacy-390xx-driver"... > Most likely that's false. As you should be able to see above, old > NVidia cards don't require tainting software to run X on modern > widescreen displays at their native resolutions. Almost certainly > all OP /needs/ to do is eradicate the tainting software, and its > configuration files, and if applicable, any library modifications > its installation created. I suggested to install right version of nvidia driver simply because OP is already opted in for nvidia driver and installed 418 version. So I've assumed that was his ultimate goal, to install and use a proprietary driver, that is indeed taints the kernel. It's possible that I couldn't express myself clearly, as you could have noticed, English is not my primary language. Personally, I can't imagine any real reason to use "nouveau", because it is trapped in development hell for years now and to this day doesn't allow to use nvidia graphics cards to their full potential, both performance-wise and feature-wise. If the reason to use "nouveau" is to "eradicate tainting software", then what about myriads of other proprietary blobs in your system? BIOS\UEFI firmware, disk drive firmware, network interface controllers, even CPUs, MIOs and ICHs are programmable and contain proprietary closed-source code. Even ICs themselves are proprietary and there is nothing you could do about it. (Unless you are Ben Eater and also have a personal silicon foundry in your backyard. :) ) Anyway, the choice to use an opensource "nouveau" or proprietary "nvidia" driver is still exist, both are supported by Debian and it is up to end user to decide what to use. -- With kindest regards, Alexander. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org ⠈⠳⣄⠀⠀⠀⠀
[toc] | [prev] | [next] | [standalone]
| From | Felix Miata <mrmazda@earthlink.net> |
|---|---|
| Date | 2021-01-10 11:50 +0100 |
| Message-ID | <BvGsh-3Ij-1@gated-at.bofh.it> |
| In reply to | #230522 |
Alexander V. Makartsev composed on 2021-01-10 14:34 (UTC+0500): > Felix Miata wrote: ... > Personally, I can't imagine any real reason to use "nouveau", because it > is trapped in development hell for years now ... > Anyway, the choice to use an opensource "nouveau" or proprietary > "nvidia" driver is still exist, both are supported by Debian and it is > up to end user to decide what to use. I included my reply to you in the same post as my reply to OP because it could be noted there (three times) that the choice is not between Nouveau and NVidia, but rather it's between those two AND the upstream default (aka preferred; since server 1.17.x about six years ago) DDX driver: Modesetting. Here is where in parts of my post you did not quote where it could be seen three times: ... Display: x11 server: X.Org 1.20.4 driver: modesetting ... Display: x11 server: X.Org 1.20.4 driver: modesetting ... Display: x11 server: X.Org 1.20.10 driver: modesetting ... Notice the absence of "nouveau". You may better understand this choice among three rather than two by reading here: <https://www.linuxquestions.org/questions/blog/mrmazda-1035595/amd-intel-and-nvidia-x-graphics-driver-primer-38306/> -- Evolution as taught in public schools, like religion, is based on faith, not on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
[toc] | [prev] | [next] | [standalone]
| From | "Alexander V. Makartsev" <avbetev@gmail.com> |
|---|---|
| Date | 2021-01-10 15:10 +0100 |
| Message-ID | <BvJzP-5PV-1@gated-at.bofh.it> |
| In reply to | #230525 |
[Multipart message — attachments visible in raw view] — view raw
On 10.01.2021 15:49, Felix Miata wrote: > Alexander V. Makartsev composed on 2021-01-10 14:34 (UTC+0500): > >> Felix Miata wrote: > ... >> Personally, I can't imagine any real reason to use "nouveau", because it >> is trapped in development hell for years now > ... >> Anyway, the choice to use an opensource "nouveau" or proprietary >> "nvidia" driver is still exist, both are supported by Debian and it is >> up to end user to decide what to use. > I included my reply to you in the same post as my reply to OP because it could be > noted there (three times) that the choice is not between Nouveau and NVidia, but > rather it's between those two AND the upstream default (aka preferred; since > server 1.17.x about six years ago) DDX driver: Modesetting. Here is where in parts > of my post you did not quote where it could be seen three times: > > ... > Display: x11 server: X.Org 1.20.4 driver: modesetting > ... > Display: x11 server: X.Org 1.20.4 driver: modesetting > ... > Display: x11 server: X.Org 1.20.10 driver: modesetting > ... > > Notice the absence of "nouveau". You may better understand this choice among three > rather than two by reading here: > <https://www.linuxquestions.org/questions/blog/mrmazda-1035595/amd-intel-and-nvidia-x-graphics-driver-primer-38306/> URL you provided is gated behind account registration. That is enough reason for me to ignore it. I still don't understand why you recommend to use generic [1] "modesetting" DDX module instead of vendor supplied and supported one for your hardware. Every xorg DDX module [2] is still depend on DRM KMS kernel driver [3] supplied by hardware vendor (nvidia or nouveau, intel, amd, etc) to function. So "absence of nouveau" in those lines doesn't really tell anything, because you still run "nouveau" driver in your system. [1] https://dri.freedesktop.org/wiki/DDX/ [2] $ apt-file find "_drv.so" | egrep 'modesetting|nvidia|intel|nouveau|amd|radeon' [3] $ man 4 modesetting -- With kindest regards, Alexander. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org ⠈⠳⣄⠀⠀⠀⠀
[toc] | [prev] | [next] | [standalone]
| From | Felix Miata <mrmazda@earthlink.net> |
|---|---|
| Date | 2021-01-10 18:20 +0100 |
| Message-ID | <BvMxI-7A3-13@gated-at.bofh.it> |
| In reply to | #230529 |
Alexander V. Makartsev composed on 2021-01-10 19:01 (UTC+0500): > Felix Miata wrote: >> Notice the absence of "nouveau". You may better understand this choice among three >> rather than two by reading here: >> <https://www.linuxquestions.org/questions/blog/mrmazda-1035595/amd-intel-and-nvidia-x-graphics-driver-primer-38306/> > URL you provided is gated behind account registration. That is enough > reason for me to ignore it. I wasn't aware of that limitation. Here's an older version of essentially the same thing: <https://forums.opensuse.org/showthread.php/541438-AMD-Intel-amp-NVidia-X-graphics-driver-primer> > I still don't understand why you recommend to use generic [1] > "modesetting" DDX module instead of vendor supplied and supported one > for your hardware. 1: The Modesetting DDX is newer technology. It's good enough that AMD stopped providing its fglrx driver for recent distro releases, and the Intel-specific DDX went into maintenance mode (no major version upgrade) 7 years ago: <https://cgit.freedesktop.org/xorg/driver/xf86-video-intel/> 2: AMD and Intel contribute to FOSS openly, while NVidia still does not. > So "absence of nouveau" in those lines doesn't really tell anything, > because you still run "nouveau" driver in your system. Again, this was addressed by the inxi outputs I provided. Here one is again with less editing, where nouveau is present only as the kernel driver/module for the NVidia hardware device, while modesetting does X-specific duty: # inxi -GISay ... Graphics: Device-1: NVIDIA GF119 [NVS 310] vendor: Hewlett-Packard driver: nouveau v: kernel bus ID: 01:00.0 chip ID: 10de:107d Display: x11 server: X.Org 1.20.10 driver: modesetting unloaded: fbdev,vesa ... Info:...Shell: Bash v: 5.1.0 running in: konsole inxi: 3.2.01 and for Intel (current devel inxi version for its improved presentation): # pinxi -GIay Graphics: Device-1: Intel 4th Generation Core Processor Family Integrated Graphics vendor: Micro-Star MSI driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:041e Display: server: X.Org 1.20.3 driver: loaded: modesetting unloaded: fbdev,vesa alternate: intel display ID: :0 screens: 1 ... Info:...Shell: Bash v: 4.4.23 running in: konsole pinxi: 3.2.01-12 And for AMD: # pinxi -GIay Graphics: Device-1: AMD Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] vendor: Dell driver: radeon v: kernel bus ID: 01:00.0 chip ID: 1002:6779 Display: x11 server: X.Org 1.20.10 driver: loaded: modesetting alternate: ati,fbdev,vesa display ID: :0 screens: 1 ... Info:...533 Shell: Bash v: 5.1.4 running in: konsole pinxi: 3.2.01-12 Thus, for most installations (non-ancient, non-bleeding edge), competent X operation is possible without having any proprietary Xorg driver or GPU-specific DDX installed. NVidia's own software is thus needed only by those who need some specific feature only it provides. -- Evolution as taught in public schools, like religion, is based on faith, not on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
[toc] | [prev] | [next] | [standalone]
| From | "Alexander V. Makartsev" <avbetev@gmail.com> |
|---|---|
| Date | 2021-01-11 00:40 +0100 |
| Message-ID | <BvStr-2DX-5@gated-at.bofh.it> |
| In reply to | #230537 |
[Multipart message — attachments visible in raw view] — view raw
On 10.01.2021 22:18, Felix Miata wrote: > I wasn't aware of that limitation. Here's an older version of essentially the > same thing: > <https://forums.opensuse.org/showthread.php/541438-AMD-Intel-amp-NVidia-X-graphics-driver-primer> I've skimmed through that thread and pretty much agree with a summary [1] from another user. > Thus, for most installations (non-ancient, non-bleeding edge), competent > X operation is possible without having any proprietary Xorg driver or > GPU-specific DDX installed. My take away is "modesetting" module could be used as an alternative, if there is a problem with vendor supplied one. Otherwise it would be recommended to use by nouveau project developers. [2] > NVidia's own software is thus needed only > by those who need some specific feature only it provides. I still won't be suggesting to use "nouveau", at least not to users who struggle to get their system to work, and not before pointing out its limitations. [1] https://forums.opensuse.org/showthread.php/541438-AMD-Intel-amp-NVidia-X-graphics-driver-primer?p=2950669#post2950669 [2] https://nouveau.freedesktop.org/InstallNouveau.html#configuringthexserver -- With kindest regards, Alexander. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org ⠈⠳⣄⠀⠀⠀⠀
[toc] | [prev] | [next] | [standalone]
| From | Felix Miata <mrmazda@earthlink.net> |
|---|---|
| Date | 2021-01-11 01:30 +0100 |
| Message-ID | <BvTfR-39S-5@gated-at.bofh.it> |
| In reply to | #230550 |
Alexander V. Makartsev composed on 2021-01-11 04:35 (UTC+0500): > Otherwise it would be recommended to use by nouveau project developers. [2] Producers of products aren't normally given to recommending use of competing products. > [2] > https://nouveau.freedesktop.org/InstallNouveau.html#configuringthexserver "When using Nouveau, the X-Server doesn't need configuration, the Nouveau driver should be loaded automatically. " This is clearly not the case for the use of a pure upstream basic/minimal configuration, where xf86-video-nouveau, like its cohorts xf86-video-amdgpu, xf86-video-ati and xf86-video-intel, are not included. It really is a carryover or relic from before xf86-video-modesetting was eliminated six years ago, and the driver it contained was moved into xorg-x11-server, ensuring its availability always. Something roughly equivalent to it probably does remain there needed, because modesetting does not support the antique GPUs that nouveau does. If it wasn't for this lack of support by modesetting for antiques, xf86-video-nouveau probably would be candidate for deprecation and eventual discontinuance. -- Evolution as taught in public schools, like religion, is based on faith, not on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
[toc] | [prev] | [next] | [standalone]
| From | Felix Miata <mrmazda@earthlink.net> |
|---|---|
| Date | 2021-01-11 01:40 +0100 |
| Message-ID | <BvTpx-3cX-19@gated-at.bofh.it> |
| In reply to | #230550 |
Leandro neto composed on 2021-01-10 23:42 (UTC): > I am trying to report this since October 2019 Trying to report exactly what (in detail)? > all my emails are blocked fell free to remove access my machine and see by yourself See what by self? Remove what access to your machine? -- Evolution as taught in public schools, like religion, is based on faith, not on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
[toc] | [prev] | [next] | [standalone]
| From | The Wanderer <wanderer@fastmail.fm> |
|---|---|
| Date | 2021-01-11 01:50 +0100 |
| Message-ID | <BvTzb-3g1-1@gated-at.bofh.it> |
| In reply to | #230553 |
[Multipart message — attachments visible in raw view] — view raw
On 2021-01-10 at 19:32, Felix Miata wrote: > Leandro neto composed on 2021-01-10 23:42 (UTC): > >> I am trying to report this since October 2019 > > Trying to report exactly what (in detail)? > >> all my emails are blocked fell free to remove access my machine and >> see by yourself > > See what by self? > > Remove what access to your machine? I think this was a typo for "remote" - i.e., "please feel free to remote in to my machine and see for yourself that all my E-mails are being blocked". Where those E-mails are supposed to be showing up, and what other surrounding details there may be, I have no more idea than you do. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw
[toc] | [prev] | [next] | [standalone]
| From | Andrei POPESCU <andreimpopescu@gmail.com> |
|---|---|
| Date | 2021-01-10 17:20 +0100 |
| Message-ID | <BvLBD-6ZS-1@gated-at.bofh.it> |
| In reply to | #230522 |
[Multipart message — attachments visible in raw view] — view raw
On Du, 10 ian 21, 14:34:42, Alexander V. Makartsev wrote: > > If the reason to use "nouveau" is to "eradicate tainting software", > then what about myriads of other proprietary blobs in your system? One step at a time ;) Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.user
csiph-web