Hi, a friend of mine has an Intel NUC 12 Enthusiast Kit (NUC12SNKi72) with an Intel Arc 770 graphic card installed on it. By default fedora 39 anaconda freezes (black screen after skipping verify media and selecting install option). It seems the same scenario as described here for fedora 37: https://kevinquillen.com/getting-intel-arc-770m-work-fedora-37 Before going through all the same steps I would like to test something shorter, especially without disabling ACPI and PCIe Power mgmt in the bios, if possible in latest Fedora. Suggestions for anaconda boot parameters? Eg 1) using nomodeset option at installation phase. Could it work oob? 2) any way to specify an option for a kernel module during install? WHat syntax? I mean the equivalent of using the options i915 force_probe=5690 in /etc/modprobe.d/i915.conf for an already installed system
BTW: I have still to understand if the system will use both graphics cards (which one is primary in this case?) or if the onboard one will be disabled if using a discrete card on the Nuc. Thanks in advance, Gianluca
On Tue, 2023-11-21 at 10:08 +0100, Gianluca Cecchi wrote:
BTW: I have still to understand if the system will use both graphics cards (which one is primary in this case?) or if the onboard one will be disabled if using a discrete card on the Nuc.
I've no idea what will happen with a NUC, but in my experience Fedora will use the discrete card in preference to the IGP, unless it's blacklisted in the boot line.
There's a package called switcheroo-control which allows you to select which GPU to use for specific apps, though personally I haven't had much luck with it.
poc
No sure this is what you're looking for, but:
you can edit the kernel parameters in the boot entry. Select a boot entry from a list and press 'e' to edit. Then 'ctrl+x' to execute. That way, you can have a custom kernel option set while running the Fedora installation ISO.
If that would help with the freezing during Anaconda installation, you should be halfway there.
Then after installation is finished, on the new system, edit `/etc/default/grub`, which is used when a new boot entry is added, which is usually done by some Post scriptlet of the kernel, when you (re-)install / update the kernel. I did this in the past to solve different issues requiring edit of kernel parameters. e.g: echo "GRUB_CMDLINE_LINUX="intel_idle.max_cstate=2 i915.enable_psr=0 i915.enable_fbc=0"" >> /etc/default/grub
For example the settings in the /etc/default/grub I use, are: GRUB_TIMEOUT=1 GRUB_DISABLE_UUID=true GRUB_ENABLE_BLSCFG=true
Hope this helps.
Michal
--
Michal Schorm Software Engineer Core Services - Databases Team Red Hat
--
On Tue, Nov 21, 2023 at 12:13 PM Patrick O'Callaghan pocallaghan@gmail.com wrote:
On Tue, 2023-11-21 at 10:08 +0100, Gianluca Cecchi wrote:
BTW: I have still to understand if the system will use both graphics cards (which one is primary in this case?) or if the onboard one will be disabled if using a discrete card on the Nuc.
I've no idea what will happen with a NUC, but in my experience Fedora will use the discrete card in preference to the IGP, unless it's blacklisted in the boot line.
There's a package called switcheroo-control which allows you to select which GPU to use for specific apps, though personally I haven't had much luck with it.
poc
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@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