Re: monitor/display problem.
home user composed on 2022-11-03 21:42 (UTC-0600): > What I have is > -rw---. 1 root root 33824169 Oct 20 09:47 > initramfs-5.19.16-100.fc35.x86_64.img > -rw---. 1 root root 35051075 Oct 20 11:19 > initramfs-5.19.16-200.fc36.x86_64.img > -rw---. 1 root root 35452743 Nov 3 13:02 > initramfs-6.0.5-200.fc36.x86_64.img > I'm a little puzzled that there are 2 initrd files for that date. It > might be important that Oct. 20 is the day I first did a weekly "dnf > upgrade", and then upgraded from f35 to f36. Is the 11:19 the one I > should back up, or should I back up both Oct. 20 files? initramfs-5.19.16-100.fc35.x86_64.img was either installed or updated when you did your customary periodic updates to F35. initramfs-5.19.16-200.fc36.x86_64.img was created later when you did your system-upgrade to F36. As long as 200.fc36 belongs to a *working* kernel, it's the important one to have backed up. It couldn't hurt to backup both though. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: monitor/display problem.
On 11/3/22 8:48 PM, Felix Miata wrote: home user composed on 2022-11-03 20:29 (UTC-0600): Felix Miata wrote: home user composed on 2022-11-03 19:02 (UTC-0600): ... 1-Backup the initrd for 5.19. According to the man page for initrd, it should be in "/dev" and/or "/". But using "ls -a", I don't see initrd in either place. The "whereis" command only find a compressed man page. Where is "initrd"? /boot/initramfs-5.19.17-200.fc36.x86_64.img ... What I have is -rw---. 1 root root 33824169 Oct 20 09:47 initramfs-5.19.16-100.fc35.x86_64.img -rw---. 1 root root 35051075 Oct 20 11:19 initramfs-5.19.16-200.fc36.x86_64.img -rw---. 1 root root 35452743 Nov 3 13:02 initramfs-6.0.5-200.fc36.x86_64.img I'm a little puzzled that there are 2 initrd files for that date. It might be important that Oct. 20 is the day I first did a weekly "dnf upgrade", and then upgraded from f35 to f36. Is the 11:19 the one I should back up, or should I back up both Oct. 20 files? I'm now shutting down for the night. I'll try booting up with the 5.19 kernel (as you suggested) in the morning when I power up the workstation. thanks, Bill. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: monitor/display problem.
home user composed on 2022-11-03 20:29 (UTC-0600): > Felix Miata wrote: >> home user composed on 2022-11-03 19:02 (UTC-0600): > ... >> 1-Backup the initrd for 5.19. > According to the man page for initrd, it should be in "/dev" and/or "/". > But using "ls -a", I don't see initrd in either place. The "whereis" > command only find a compressed man page. Where is "initrd"? /boot/initramfs-5.19.17-200.fc36.x86_64.img Initrd is the traditional term for initial RAM disk (initrd), which after many moons use had the term initial RAM filesystem (initramfs) ascribed to the file serving the same purpose and basic structure. It was never a literal disk, just a filesystem, like floppies, HDD partitions and logical volumes support. On most installations, either lsinitrd or lsinitramfs will list either's contents. https://en.wikipedia.org/wiki/Initial_ramdisk -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: monitor/display problem.
On 11/03/2022 04:59 PM, home user wrote: How do I determine which kernel I'm using now? uname -r ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: monitor/display problem.
On 11/3/22 7:20 PM, Felix Miata wrote: home user composed on 2022-11-03 19:02 (UTC-0600): ... 1-Backup the initrd for 5.19. According to the man page for initrd, it should be in "/dev" and/or "/". But using "ls -a", I don't see initrd in either place. The "whereis" command only find a compressed man page. Where is "initrd"? Bill. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: monitor/display problem.
home user composed on 2022-11-03 19:02 (UTC-0600): > What specifically do I need to install? > "dnf install [what?]" and re-boot. > Is there anything else I need to do? It still boots the 5.19 kernel OK, right? 1-Backup the initrd for 5.19. 2-Boot only the 5.19 kernel until such time as updated NVidia 470 drivers reach rpmfusion-nonfree-updates so you can upgrade them. Alternatively, switch to those currently in rpmfusion-nonfree-updates-testing. 3-(optional but desirable) find a way to paste only plain text into your email, leaving out the confusing ANSI strings such as "[K[ [0;31m*[0;1;31m*[0m]". -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: monitor/display problem.
On 11/3/22 3:51 PM, home user wrote: (f36) ... A few have asked about kernel and driver versions. I've been trying to grope through logs to get answers. The logs are being split in strange ways, ways not matching the dates on which the dnf commands were run, making this both difficult and tedious. But here's what I find (some extra lines included for context)... == (dnf.log) 2022-11-03T12:57:56-0600 DEBUG --> Starting dependency resolution 2022-11-03T12:57:57-0600 DEBUG ---> Package kernel.x86_64 6.0.5-200.fc36 will be installed 2022-11-03T12:57:58-0600 DEBUG ---> Package kernel-core.x86_64 6.0.5-200.fc36 will be installed 2022-11-03T12:57:58-0600 DEBUG ---> Package kernel-devel.x86_64 6.0.5-200.fc36 will be installed 2022-11-03T12:57:58-0600 DEBUG ---> Package kernel-modules.x86_64 6.0.5-200.fc36 will be installed 2022-11-03T12:57:59-0600 DEBUG ---> Package kernel-devel-matched.x86_64 5.19.16-200.fc36 will be upgraded 2022-11-03T12:57:59-0600 DEBUG ---> Package kernel-devel-matched.x86_64 6.0.5-200.fc36 will be an upgrade 2022-11-03T12:57:59-0600 DEBUG ---> Package kernel-headers.x86_64 5.19.4-200.fc36 will be upgraded 2022-11-03T12:57:59-0600 DEBUG ---> Package kernel-headers.x86_64 6.0.5-200.fc36 will be an upgrade 2022-11-03T12:57:59-0600 DEBUG ---> Package kernel-tools.x86_64 5.19.4-200.fc36 will be upgraded 2022-11-03T12:57:59-0600 DEBUG ---> Package kernel-tools.x86_64 6.0.5-200.fc36 will be an upgrade 2022-11-03T12:57:59-0600 DEBUG ---> Package kernel-tools-libs.x86_64 5.19.4-200.fc36 will be upgraded 2022-11-03T12:57:59-0600 DEBUG ---> Package kernel-tools-libs.x86_64 6.0.5-200.fc36 will be an upgrade 2022-11-03T12:58:00-0600 DEBUG ---> Package kernel.x86_64 5.19.14-100.fc35 will be erased 2022-11-03T12:58:00-0600 DEBUG ---> Package kernel-core.x86_64 5.19.14-100.fc35 will be erased 2022-11-03T12:58:00-0600 DEBUG ---> Package kernel-devel.x86_64 5.19.14-100.fc35 will be erased 2022-11-03T12:58:00-0600 DEBUG ---> Package kernel-modules.x86_64 5.19.14-100.fc35 will be erased 2022-11-03T12:58:00-0600 DEBUG ---> Package kmod-nvidia-470xx-5.19.14-100.fc35.x86_64.x86_64 3:470.141.03-1.fc35 will be erased 2022-11-03T12:58:00-0600 DEBUG --> Finished dependency resolution [1m[32mkernel(B[m x86_64 6.0.5-200.fc36 updates 113 k [1m[32mkernel-core (B[m x86_64 6.0.5-200.fc36 updates 52 M [1m[32mkernel-devel (B[m x86_64 6.0.5-200.fc36 updates 16 M [1m[32mkernel-modules(B[m x86_64 6.0.5-200.fc36 updates 62 M [1m[32mkernel-devel-matched (B[m x86_64 6.0.5-200.fc36 updates 113 k [1m[32mkernel-headers(B[m x86_64 6.0.5-200.fc36 updates 1.3 M [1m[32mkernel-tools (B[m x86_64 6.0.5-200.fc36 updates 259 k [1m[32mkernel-tools-libs (B[m x86_64 6.0.5-200.fc36 updates 21 k Removing: [31mkernel(B[m x86_64 5.19.14-100.fc35@updates 0 [31mkernel-core (B[m x86_64 5.19.14-100.fc35@updates 92 M [31mkernel-devel (B[m x86_64 5.19.14-100.fc35@updates 64 M [31mkernel-modules(B[m x86_64 5.19.14-100.fc35@updates 58 M Removing dependent packages: [31mkmod-nvidia-470xx-5.19.14-100.fc35.x86_64 (B[m x86_64 3:470.141.03-1.fc35 @@commandline 44 M 2022-11-03T13:03:03-0600 DEBUG Upgraded: kernel-devel-matched-6.0.5-200.fc36.x86_64 2022-11-03T13:03:03-0600 DEBUG Upgraded: kernel-headers-6.0.5-200.fc36.x86_64 2022-11-03T13:03:03-0600 DEBUG Upgraded: kernel-tools-6.0.5-200.fc36.x86_64 2022-11-03T13:03:03-0600 DEBUG Upgraded: kernel-tools-libs-6.0.5-200.fc36.x86_64 2022-11-03T13:03:03-0600 DEBUG Installed: kernel-6.0.5-200.fc36.x86_64 2022-11-03T13:03:03-0600 DEBUG Installed: kernel-core-6.0.5-200.fc36.x86_64 2022-11-03T13:03:03-0600 DEBUG Installed: kernel-devel-6.0.5-200.fc36.x86_64 2022-11-03T13:03:03-0600 DEBUG Installed: kernel-modules-6.0.5-200.fc36.x86_64 2022-11-03T13:03:03-0600 DEBUG Rem
Re: monitor/display problem.
On 11/3/22 4:58 PM, Jerry James wrote: On Thu, Nov 3, 2022 at 4:45 PM home user wrote: I do not see any such logs in the gnome "logview" tool (which is where I see the boot and dnf logs). Where are the akmod logs? /var/cache/akmods/nvidia Nothing there... - bash.3[nvidia]: ls -a . .. bash.4[nvidia]: pwd /var/cache/akmods/nvidia bash.5[nvidia]: - Bill. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: monitor/display problem.
On 11/3/22 15:59, home user wrote:
On 11/3/22 4:25 PM, Felix Miata wrote:
home user composed on 2022-11-03 15:51 (UTC-0600):
...
Were you previously using a 5.19 kernel and the new kernel is a 6.0?
The problem
is NVidia's proprietary driver isn't working, and the fallback driver
is too crude
to support more than one display or more than 1024x768 mode or
possibly 1280x1024,
either of which stretch screen objects horizontally, and usually
provide a much
lower screen resolution than the displays' optimums. Try reinstalling
the NVidia
drivers to fix it.
How do I determine which kernel I'm using now?
uname -a
Before this afternoon's patching, I was using whichever kernel would
have been patched/installed by the previous weekly patch ("dnf upgrade",
run on October 27). I was not using the nVidia proprietary driver, but
the free one (kmod?).
That is merely the result of compiling the proprietary driver. It's not
a free one.
When doing weekly patches, usually after the "dnf upgrade" completes, a
CPU-intensive compile "akmod"? runs for a few minutes. I see that in
"kSysGuard". This afternoon, I saw no such process in kSysGuard" after
the "dnf upgrade" completed.
akmod is the process that compiles the source into the kmod package that
you see installed. You can try running the akmod process manually to
see what's going wrong, but others have already said the driver version
you have is not compatible with the latest kernel and needs updating.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
Re: monitor/display problem.
On 03/11/2022 21:51, home user wrote: (f36) Good afternoon, A short while ago, I did my weekly patches (dnf upgrade), and then re-booted. Just before that, the workstation display (dual monitor) was fine. After the reboot, only one display works. If I switch the monitor cables, I still get a one-monitor display, but on the other monitor. This leads me to think that the problem is not with the monitors. The display in the one monitor looks a little fuzzy and stretched out horizontally. I also notice at the end of the boot log the following lines: - M [K[ [0;31m*[0;1;31m*[0m] (2 of 3) Job plymouth-quit-wait.ser…tart running (1min 17s / no limit) M [K[ [0;31m*[0;1;31m*[0m[0;31m*[0m] (2 of 3) Job plymouth-quit-wait.ser…tart running (1min 17s / no limit) M [K[ [0;31m*[0;1;31m*[0m[0;31m* [0m] (3 of 3) Job akmods.service/start running (1min 18s / no limit) M [K[ [0;31m*[0;1;31m*[0m[0;31m* [0m] (3 of 3) Job akmods.service/start running (1min 18s / no limit) M [K[[0;32m OK [0m] Finished [0;1;39makmods.service[0…all new kmods from akmod packages. [K Starting [0;1;39mnvidia-fallback.s… nouveau as nvidia did not load... [[0;32m OK [0m] Finished [0;1;39mnvidia-fallback.s…to nouveau as nvidia did not load. Starting [0;1;39mgdm.service[0m - GNOME Display Manager... [[0;32m OK [0m] Started [0;1;39mgdm.service[0m - GNOME Display Manager. - (first and last lines are for context only) I can't memorize fast enough, but I did notice during the last boot lines very much like (or identical to?) the lines above that mentioned "nvidia". What is the problem? More important, how do I fix it? thanks, Bill. Your post doesn't show which versions of kernel and nvidia driver you were running before the problem, but others have had difficulty with the kernel 6 and the rpmfusion 390xx and 470xx drivers. There are new versions of both of these in the rpmfusion nonfree updates testing repo. The 470xx testing version works for me. John P ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: monitor/display problem.
On 11/3/22 4:25 PM, Felix Miata wrote:
home user composed on 2022-11-03 15:51 (UTC-0600):
...
Were you previously using a 5.19 kernel and the new kernel is a 6.0? The problem
is NVidia's proprietary driver isn't working, and the fallback driver is too
crude
to support more than one display or more than 1024x768 mode or possibly
1280x1024,
either of which stretch screen objects horizontally, and usually provide a much
lower screen resolution than the displays' optimums. Try reinstalling the NVidia
drivers to fix it.
How do I determine which kernel I'm using now?
Before this afternoon's patching, I was using whichever kernel would
have been patched/installed by the previous weekly patch ("dnf upgrade",
run on October 27). I was not using the nVidia proprietary driver, but
the free one (kmod?).
When doing weekly patches, usually after the "dnf upgrade" completes, a
CPU-intensive compile "akmod"? runs for a few minutes. I see that in
"kSysGuard". This afternoon, I saw no such process in kSysGuard" after
the "dnf upgrade" completed.
Bill.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
Re: monitor/display problem.
On Thu, Nov 3, 2022 at 4:45 PM home user wrote: > I do not see any such logs in the gnome "logview" tool (which is where I > see the boot and dnf logs). Where are the akmod logs? /var/cache/akmods/nvidia -- Jerry James http://www.jamezone.org/ ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: monitor/display problem.
On 11/3/22 3:59 PM, Barry wrote: On 3 Nov 2022, at 21:53, home user wrote: [... snip ...] [K[ [0;31m*[0;1;31m*[0m[0;31m* [0m] (3 of 3) Job akmods.service/start running (1min 18s / no limit) M [K[ [0;31m*[0;1;31m*[0m[0;31m* [0m] (3 of 3) Job akmods.service/start running (1min 18s / no limit) M [K[[0;32m OK [0m] Finished [0;1;39makmods.service[0…all new kmods from akmod packages. [K Starting [0;1;39mnvidia-fallback.s… nouveau as nvidia did not load... [[0;32m OK [0m] Finished [0;1;39mnvidia-fallback.s…to nouveau as nvidia did not load. Seems that you want to use the nvidia driver but it is not compiled and so the fallback nouveau is used. Guess nouveau does not support 2 monitors. Find the akmod logs for the nvidia build and see if there is a clue about what went wrong. I do not see any such logs in the gnome "logview" tool (which is where I see the boot and dnf logs). Where are the akmod logs? [... snip ...] Bill. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: monitor/display problem.
home user composed on 2022-11-03 15:51 (UTC-0600): ... > This leads me to think that the problem is not with the monitors. The > display in the one monitor looks a little fuzzy and stretched out > horizontally. I also notice at the end of the boot log the following lines: ... > What is the problem? > More important, how do I fix it? Were you previously using a 5.19 kernel and the new kernel is a 6.0? The problem is NVidia's proprietary driver isn't working, and the fallback driver is too crude to support more than one display or more than 1024x768 mode or possibly 1280x1024, either of which stretch screen objects horizontally, and usually provide a much lower screen resolution than the displays' optimums. Try reinstalling the NVidia drivers to fix it. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: monitor/display problem.
Barry composed on 2022-11-03 21:59 (UTC): > Seems that you want to use the nvidia driver but it is not compiled and so > the fallback nouveau is used. > Guess nouveau does not support 2 monitors. Nouveau supports 2 monitors, but not when NVidia drivers interfere by blacklisting nouveau, which prevents fallback to FOSS: # xdriinfo Screen 0: nouveau # pinxi -GSaz --zl --hostname System: Host: gb970 Kernel: 5.19.17-200.fc36.x86_64 arch: x86_64 bits: 64 compiler: gcc v: 2.37-36.fc36 parameters: ro root=LABEL= audit=0 ipv6.disable=1 net.ifnames=0 audit=0 plymouth.enable=0 noresume mitigations=auto consoleblank=0 selinux=0 Desktop: Trinity v: R14.0.12 tk: Qt v: 3.5.0 info: kicker wm: Twin v: 3.0 vt: 7 dm: 1: TDM 2: XDM Distro: Fedora release 36 (Thirty Six) Graphics: Device-1: NVIDIA GF108 [GeForce GT 630] vendor: Gigabyte driver: nouveau v: kernel non-free: series: 390.xx+ status: legacy-active (EOL~late 2022) arch: Fermi code: GF1xx process: 40/28nm built: 2010-16 pcie: gen: 1 speed: 2.5 GT/s lanes: 16 ports: active: DVI-I-1,HDMI-A-1 empty: VGA-1 bus-ID: 01:00.0 chip-ID: 10de:0f00 class-ID: 0300 temp: 49.0 C Display: x11 server: X.Org v: 1.20.14 driver: X: loaded: modesetting unloaded: fbdev,vesa dri: nouveau gpu: nouveau display-ID: :0 screens: 1 Screen-1: 0 s-res: 3600x1200 s-dpi: 120 s-size: 761x253mm (29.96x9.96") s-diag: 802mm (31.57") Monitor-1: DVI-I-1 pos: primary,left model: NEC EA243WM serial: built: 2011 res: 1920x1200 hz: 60 dpi: 94 gamma: 1.2 size: 519x324mm (20.43x12.76") diag: 612mm (24.1") ratio: 16:10 modes: max: 1920x1200 min: 640x480 Monitor-2: HDMI-A-1 mapped: HDMI-1 pos: right model: Dell P2213 serial: built: 2012 res: 1680x1050 hz: 60 dpi: 90 gamma: 1.2 size: 473x296mm (18.62x11.65") diag: 558mm (22") ratio: 16:10 modes: max: 1680x1050 min: 720x400 API: OpenGL v: 4.3 Mesa 22.1.7 renderer: NVC1 direct render: Yes Installation of NVidia's proprietary drivers block use of any of the /several/ existing nouveau FOSS driver types: kernel DDX # optional, in place of above "modesetting" DIX display default dri Mesa -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: monitor/display problem.
> On 3 Nov 2022, at 21:53, home user wrote: > > (f36) > > Good afternoon, > > A short while ago, I did my weekly patches (dnf upgrade), and then re-booted. > Just before that, the workstation display (dual monitor) was fine. After > the reboot, only one display works. If I switch the monitor cables, I still > get a one-monitor display, but on the other monitor. This leads me to think > that the problem is not with the monitors. The display in the one monitor > looks a little fuzzy and stretched out horizontally. I also notice at the > end of the boot log the following lines: > - > M > [K[[0;31m*[0;1;31m*[0m] (2 of 3) Job plymouth-quit-wait.ser…tart > running (1min 17s / no limit) > M > [K[ [0;31m*[0;1;31m*[0m[0;31m*[0m] (2 of 3) Job > plymouth-quit-wait.ser…tart running (1min 17s / no limit) > M > [K[ [0;31m*[0;1;31m*[0m[0;31m* [0m] (3 of 3) Job akmods.service/start > running (1min 18s / no limit) > M > [K[ [0;31m*[0;1;31m*[0m[0;31m* [0m] (3 of 3) Job akmods.service/start > running (1min 18s / no limit) > M > [K[[0;32m OK [0m] Finished [0;1;39makmods.service[0…all new kmods from > akmod packages. > [K Starting [0;1;39mnvidia-fallback.s… nouveau as nvidia did not > load... > [[0;32m OK [0m] Finished [0;1;39mnvidia-fallback.s…to nouveau as nvidia > did not load. Seems that you want to use the nvidia driver but it is not compiled and so the fallback nouveau is used. Guess nouveau does not support 2 monitors. Find the akmod logs for the nvidia build and see if there is a clue about what went wrong. Barry > Starting [0;1;39mgdm.service[0m - GNOME Display Manager... > [[0;32m OK [0m] Started [0;1;39mgdm.service[0m - GNOME Display Manager. > - > (first and last lines are for context only) > I can't memorize fast enough, but I did notice during the last boot lines > very much like (or identical to?) the lines above that mentioned "nvidia". > > What is the problem? > More important, how do I fix it? > > thanks, > Bill. > ___ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
monitor/display problem.
(f36) Good afternoon, A short while ago, I did my weekly patches (dnf upgrade), and then re-booted. Just before that, the workstation display (dual monitor) was fine. After the reboot, only one display works. If I switch the monitor cables, I still get a one-monitor display, but on the other monitor. This leads me to think that the problem is not with the monitors. The display in the one monitor looks a little fuzzy and stretched out horizontally. I also notice at the end of the boot log the following lines: - M [K[ [0;31m*[0;1;31m*[0m] (2 of 3) Job plymouth-quit-wait.ser…tart running (1min 17s / no limit) M [K[ [0;31m*[0;1;31m*[0m[0;31m*[0m] (2 of 3) Job plymouth-quit-wait.ser…tart running (1min 17s / no limit) M [K[ [0;31m*[0;1;31m*[0m[0;31m* [0m] (3 of 3) Job akmods.service/start running (1min 18s / no limit) M [K[ [0;31m*[0;1;31m*[0m[0;31m* [0m] (3 of 3) Job akmods.service/start running (1min 18s / no limit) M [K[[0;32m OK [0m] Finished [0;1;39makmods.service[0…all new kmods from akmod packages. [K Starting [0;1;39mnvidia-fallback.s… nouveau as nvidia did not load... [[0;32m OK [0m] Finished [0;1;39mnvidia-fallback.s…to nouveau as nvidia did not load. Starting [0;1;39mgdm.service[0m - GNOME Display Manager... [[0;32m OK [0m] Started [0;1;39mgdm.service[0m - GNOME Display Manager. - (first and last lines are for context only) I can't memorize fast enough, but I did notice during the last boot lines very much like (or identical to?) the lines above that mentioned "nvidia". What is the problem? More important, how do I fix it? thanks, Bill. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
