Re: Wrong screen resolution (1024x768) after upgrade
Hi, Back home. This morning, I just upgraded my system with dnf upgrade (so I still did not installed the nvidia proprietary driver). I obtained the new kerner 6.0.7. I rebooted and here am I again with my wrong screen resolution... # grep veau /etc/modprobe.d/* returns nothing I rebuilt initrds although the file was already there for 6.0.7: # dracut -f # lsmod | grep veau returns nothing # inxi -GSaz --zl --hostname https://paste.centos.org/view/0496bee0 # inxi -C --vs https://paste.centos.org/view/97d00d79 /var/log/Xorg.0.log: https://paste.centos.org/view/355ead1b I see strange things: [23.494] (EE) Failed to load module "nv" (module does not exist, 0) [23.628] (EE) [drm] Failed to open DRM device for pci::01:00.0: -19 [23.628] (EE) open /dev/dri/card0: No such file or directory [23.628] (WW) Falling back to old probe method for modesetting [23.628] (EE) open /dev/dri/card0: No such file or directory [23.634] (EE) open /dev/fb0: No such file or directory [23.634] (EE) Screen 0 deleted because of no matching config section. [23.634] (II) UnloadModule: "modesetting" [23.634] (EE) Screen 0 deleted because of no matching config section. but also [23.492] (II) LoadModule: "nouveau" [23.492] (II) Loading /usr/lib64/xorg/modules/drivers/nouveau_drv.so which seems to indicate that nouveau is used. Thanks for your help! F ___ 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: Wrong screen resolution (1024x768) after upgrade
On 11/11/2022 11:17, Frédéric wrote: Hi, Back home. This morning, I just upgraded my system with dnf upgrade (so I still did not installed the nvidia proprietary driver). I obtained the new kerner 6.0.7. I rebooted and here am I again with my wrong screen resolution... # grep veau /etc/modprobe.d/* returns nothing I rebuilt initrds although the file was already there for 6.0.7: # dracut -f # lsmod | grep veau returns nothing # inxi -GSaz --zl --hostname https://paste.centos.org/view/0496bee0 # inxi -C --vs https://paste.centos.org/view/97d00d79 /var/log/Xorg.0.log: https://paste.centos.org/view/355ead1b I see strange things: [23.494] (EE) Failed to load module "nv" (module does not exist, 0) [23.628] (EE) [drm] Failed to open DRM device for pci::01:00.0: -19 [23.628] (EE) open /dev/dri/card0: No such file or directory [23.628] (WW) Falling back to old probe method for modesetting [23.628] (EE) open /dev/dri/card0: No such file or directory [23.634] (EE) open /dev/fb0: No such file or directory [23.634] (EE) Screen 0 deleted because of no matching config section. [23.634] (II) UnloadModule: "modesetting" [23.634] (EE) Screen 0 deleted because of no matching config section. but also [23.492] (II) LoadModule: "nouveau" [23.492] (II) Loading /usr/lib64/xorg/modules/drivers/nouveau_drv.so which seems to indicate that nouveau is used. Thanks for your help! F Today's email from rpmfusion does not show any pushes to the nonfree stable repo. I suggest: Boot the 5.16 kernel and install akmod470xx or reinstall nouveau or dnf --enablerepo epmfusion-nonfree-updates-testing install akmod470xx or wait until the push-to-stable happens and update These are ideas, probably not the exact commands. John ___ 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: Wrong screen resolution (1024x768) after upgrade
Frédéric composed on 2022-11-11 12:17 (UTC+0100): > # inxi -GSaz --zl --hostname > https://paste.centos.org/view/0496bee0 from above: rd.driver.blacklist=nouveau modprobe.blacklist=nouveau causes all the following fatal errors: >> # lsmod | grep veau > returns nothing ... > [23.628] (EE) [drm] Failed to open DRM device for pci::01:00.0: -19 > [23.628] (EE) open /dev/dri/card0: No such file or directory > [23.628] (EE) open /dev/dri/card0: No such file or directory > [23.634] (EE) open /dev/fb0: No such file or directory > [23.634] (II) UnloadModule: "modesetting" Those kernel command line options need to be removed from /etc/default/grub and /boot/grub2/grub.cfg regenerated to exclude them. nvidia-drm.modeset=1 Is probably unnecessary. You might be best off removing it too. None of my NVidia GPUs require it. To test, strike the E key at the Grub menu and remove them all before proceeding with boot. -- 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: Wrong screen resolution (1024x768) after upgrade
Hi, > rd.driver.blacklist=nouveau modprobe.blacklist=nouveau > > causes all the following fatal errors: > > Those kernel command line options need to be removed from /etc/default/grub > and /boot/grub2/grub.cfg regenerated to exclude them. You are right: I edited with e and removed those 2 commands and it works. So I edited /etc/default/grub, removed the commands ran grub2-mkconfig -o /boot/grub2/grub.cfg. And it works! > nvidia-drm.modeset=1 > > Is probably unnecessary. You might be best off removing it too. None of my > NVidia GPUs require it. You're right, I also removed it. After that, I was able to reinstall the nvidia proprietary driver (390xx) and again, it works! Thanks a lot! F ___ 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: Moving to a new GPU
On Wed, 2022-11-09 at 22:55 +0100, greg wrote: > In order to disable i915 altogether, I used an option in bios/efi > firmware. > (I have an NVIDIA card and want to use it always/for any > application.) That's what I ended up doing. I tried blacklisting the i915 but it was still be there on booting. Turning it off in the BIOS is what got the result. I'd still like to enable both GPUs for VM PC passthrough, but haven't got that working yet. Thanks to everyone who replied. poc ___ 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: Moving to a new GPU
On Thu, 2022-11-10 at 08:02 -0700, stan via users wrote: > On Wed, 09 Nov 2022 17:09:02 + > Patrick O'Callaghan wrote: > > > Is there some grub magic I need to do? I assumed this would be > > automatic but it seems not. > > When I switched from nvidia to amd, many years ago, it was seamless. > But that was older hardware, I didn't have two graphics cards (a > builtin > and a discrete), and I am using the radeon driver with an amd cpu, > not > an amd card with an intel cpu. Anyway I did a quick search and found > this link that mentions something called prime that seems to do > something like what you want. > > https://www.unixmen.com/using-hybrid-graphic-card-intel-amd-arch-linux/ Thanks. I may get round to that later, though often the Arch package structure is different enough from Fedora to make some decoding necessary. For now I disabled the IGP in the BIOS, which gets me part of the way. poc ___ 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: Font Error Before a Display of the Grub Boot Menu
On 11/11/22 15:43, Doug H. wrote: On Thu, Nov 10, 2022, at 2:04 PM, Stephen Morris wrote: Hi, When I boot my machine I am getting a font error before the Grub Menu is being displayed but is disappearing before I can get a good look at it, which may be because of the Grub Boot Theme I am using, which has not installed its files into /boot/grub2/themes but has stored them in /usr/share/grub, irrespective of the error the grub menus display fine with the theme. The error message seems to be referencing efi/EFI/fedora/unicode.pf2 as a target but I can't be sure, but the theme being used doesn't use that file anyway. Is there anywhere I can look to find the message to understand what is being objected to? Video record the screen while booting? Thankyou, I was able to take a photo of the screen with the message displayed (I hadn't thought about doing that). The message was the grub fshelp component complaining it could find EFI/fedora/fonts/unicode.pf2, I had unicode.pf2 in /boot/efi/EFI/fedora not in the fonts subdirectory which didn't exist. This was probably an issue I created when trying to clean up fingerprints left behind by grub-customizer when I was trying to replicate the grub default menu functionality of displaying the menus at 4K resolution because the GRUB_GFXPAYLOAD_LINUX="3840x2160" parameter in /etc/default/grub seems to be ignored for the theme I am using, but the theme doesn't have any resolution setting in theme.txt. regards, Steve ___ 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
