# Graphics card not available

**URL:** <https://community.frame.work/t/graphics-card-not-available/66269>\
**Category:** Linux\
**Tags:** arch\
**Created:** [March 17, 2025, 5:43pm UTC](https://community.frame.work/t/graphics-card-not-available/66269 "2025-03-17T17:43:12Z")\
**Posts on this page:** 20\
**Page:** 5

<div class="post-metadata">

**Author:** ![knipp30](https://avatars.discourse-cdn.com/v4/letter/k/ed8c4c/32.png) [@knipp30](https://community.frame.work/u/knipp30)\
**Post date:** [April 18, 2025, 4:37pm UTC](https://community.frame.work/t/graphics-card-not-available/66269/81 "2025-04-18T16:37:05Z")

</div>

> [@John\_Obscurant](#):
>
> When booting while running on battery, the dGPU is not available from the start.

I did just confirm that I do have that issue.

Did you build the patched kernel from source?

---

<div class="post-metadata">

**Author:** ![John\_Obscurant](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/john_obscurant/32/22180_2.png) [@John\_Obscurant](https://community.frame.work/u/John_Obscurant)\
**Post date:** [April 18, 2025, 5:35pm UTC](https://community.frame.work/t/graphics-card-not-available/66269/82 "2025-04-18T17:35:01Z")

</div>

Yes, following these instructions:

> **[Building a Custom Kernel](https://docs.fedoraproject.org/en-US/quick-docs/kernel-build-custom/)**
>
> This document provides instructions for advanced users who want to rebuild the kernel from some source. Some common reasons to build a custom kernel are: To apply patches for testing…

---

<div class="post-metadata">

**Author:** ![knipp30](https://avatars.discourse-cdn.com/v4/letter/k/ed8c4c/32.png) [@knipp30](https://community.frame.work/u/knipp30)\
**Post date:** [April 18, 2025, 5:37pm UTC](https://community.frame.work/t/graphics-card-not-available/66269/83 "2025-04-18T17:37:23Z")

</div>

I figured as much 🙂 I did that a while back to test a d3cold issue.

Since mine is only messing up when booting from battery, Ill wait 🙂

Currently installing a single node openshift environment and don’t feel like messing w/the kernel today lol

---

<div class="post-metadata">

**Author:** ![the9thdude](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/the9thdude/32/47111_2.png) [@the9thdude](https://community.frame.work/u/the9thdude)\
**Post date:** [April 18, 2025, 7:09pm UTC](https://community.frame.work/t/graphics-card-not-available/66269/84 "2025-04-18T19:09:45Z")

</div>

Throwing my hat in the ring since this issue literally _just_ happened to me.

**System**

- AMD Ryzen 7 7840HS
- 32GB Crucial DDR5 (from Framework)
- 2TB WD SN770 (from Framework)
- AMD Radeon RX 7700S
- Fedora 42 (kernel 6.14.2-300.fc42.x86\_64)

Strangely, I’ve mostly had this problem when waking from sleep, but this time was different. I was gaming on battery using the 7700S (MangoHud showed it as active) and when I closed the lid after plugging in my monitor, the dGPU disappeared from Mission Center. FastFetch shows the dGPU though.

I’m still fairly new to Linux troubleshooting, so I’d be happy to help if guided.

---

<div class="post-metadata">

**Author:** ![Tealk](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/tealk/32/24794_2.png) [@Tealk](https://community.frame.work/u/Tealk)\
**Post date:** [April 19, 2025, 1:48pm UTC](https://community.frame.work/t/graphics-card-not-available/66269/85 "2025-04-19T13:48:33Z")

</div>

So since the following update the graphics card seems to be active for some time now, I have nvtop open all the time and even after the supsend it is still active.

```auto
fedora:fedora/42/x86_64/silverblue
                  Version: 42.20250417.0 (2025-04-17T17:29:03Z)
               BaseCommit: b6784a601685fd9f89e667f29676f6a6da9c7721becc921b5239a77f4331b196

```

---

<div class="post-metadata">

**Author:** ![TechPriestNhyk](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/techpriestnhyk/32/27853_2.png) [@TechPriestNhyk](https://community.frame.work/u/TechPriestNhyk)\
**Post date:** [April 21, 2025, 12:14pm UTC](https://community.frame.work/t/graphics-card-not-available/66269/86 "2025-04-21T12:14:46Z")

</div>

> [@Tealk](#):
>
> So since the following update the graphics card seems to be active for some time now, I have nvtop open all the time and even after the supsend it is still active.
> 
> ```auto
> 
> ```

nvtop keeps the gpu awake and will prevent it from sleeping

---

<div class="post-metadata">

**Author:** ![Tealk](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/tealk/32/24794_2.png) [@Tealk](https://community.frame.work/u/Tealk)\
**Post date:** [April 21, 2025, 12:16pm UTC](https://community.frame.work/t/graphics-card-not-available/66269/87 "2025-04-21T12:16:34Z")

</div>

Yes, the problem is rather that the graphics card would have to be usable first and I only have that at every hundredth start or even less often 😢

---

<div class="post-metadata">

**Author:** ![TechPriestNhyk](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/techpriestnhyk/32/27853_2.png) [@TechPriestNhyk](https://community.frame.work/u/TechPriestNhyk)\
**Post date:** [April 21, 2025, 12:17pm UTC](https://community.frame.work/t/graphics-card-not-available/66269/88 "2025-04-21T12:17:48Z")

</div>

Ah. Yeah, I haven’t had the courage to update my Fedora yet, which is a real shame.

---

<div class="post-metadata">

**Author:** ![Tealk](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/tealk/32/24794_2.png) [@Tealk](https://community.frame.work/u/Tealk)\
**Post date:** [April 21, 2025, 12:33pm UTC](https://community.frame.work/t/graphics-card-not-available/66269/89 "2025-04-21T12:33:43Z")

</div>

That there is no way to hard wake up the graphics card, but I haven’t found anything yet. A console command would be enough for me.

---

<div class="post-metadata">

**Author:** ![magnificent\_wombat](https://avatars.discourse-cdn.com/v4/letter/m/3ec8ea/32.png) [@magnificent\_wombat](https://community.frame.work/u/magnificent_wombat)\
**Post date:** [April 21, 2025, 3:03pm UTC](https://community.frame.work/t/graphics-card-not-available/66269/90 "2025-04-21T15:03:38Z")

</div>

I had the same problem on Fedora 41/42. Installing Kernel 6.12 from [this COPR](https://copr.fedorainfracloud.org/coprs/kwizart/kernel-longterm-6.12/) solved the problem for me. I had to disable Secure-Boot as well to boot this kernel.

---

<div class="post-metadata">

**Author:** ![Tealk](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/tealk/32/24794_2.png) [@Tealk](https://community.frame.work/u/Tealk)\
**Post date:** [April 21, 2025, 3:05pm UTC](https://community.frame.work/t/graphics-card-not-available/66269/91 "2025-04-21T15:05:45Z")

</div>

Reliable with sleep and multiple reboots?

I have tried all the kernels listed [here](https://koji.fedoraproject.org/koji/search?match=glob&type=build&terms=kernel-6.*.fc42) and none of them could reliably run the graphics card.

---

<div class="post-metadata">

**Author:** ![magnificent\_wombat](https://avatars.discourse-cdn.com/v4/letter/m/3ec8ea/32.png) [@magnificent\_wombat](https://community.frame.work/u/magnificent_wombat)\
**Post date:** [April 21, 2025, 3:07pm UTC](https://community.frame.work/t/graphics-card-not-available/66269/92 "2025-04-21T15:07:29Z")

</div>

Not sure what you mean with multiple reboots, but yes, it wakes up fast and reliable from sleep (so far).

---

<div class="post-metadata">

**Author:** ![Tealk](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/tealk/32/24794_2.png) [@Tealk](https://community.frame.work/u/Tealk)\
**Post date:** [April 21, 2025, 3:18pm UTC](https://community.frame.work/t/graphics-card-not-available/66269/93 "2025-04-21T15:18:08Z")

</div>

That the graphics card is also available every time the notebook is started.

Shortly after a kernel update it often works after 1-4 starts, but then it is always gone for me.

---

<div class="post-metadata">

**Author:** ![magnificent\_wombat](https://avatars.discourse-cdn.com/v4/letter/m/3ec8ea/32.png) [@magnificent\_wombat](https://community.frame.work/u/magnificent_wombat)\
**Post date:** [April 22, 2025, 1:48pm UTC](https://community.frame.work/t/graphics-card-not-available/66269/94 "2025-04-22T13:48:06Z")

</div>

Seems very stable to me. I had no issues after reboots or waking from suspends after installing the LTS Kernel on Fedora 42, even when switching from docked to undocked while asleep.

---

<div class="post-metadata">

**Author:** ![Zaechus](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/zaechus/32/36590_2.png) [@Zaechus](https://community.frame.work/u/Zaechus)\
**Post date:** [May 5, 2025, 6:45am UTC](https://community.frame.work/t/graphics-card-not-available/66269/95 "2025-05-05T06:45:17Z")

</div>

This happened to me recently. I hadn’t updated or even rebooted in a bit, but one day the 7700S no longer appears. Using older or recent versions of linux kernels 6.6, 6.12, and 6.14 make no difference. Checked with a USB drive with Arch LInux and Windows and neither could see the dGPU either.

---

<div class="post-metadata">

**Author:** ![Accalia\_Elementia](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/accalia_elementia/32/24471_2.png) [@Accalia\_Elementia](https://community.frame.work/u/Accalia_Elementia)\
**Post date:** [May 5, 2025, 12:56pm UTC](https://community.frame.work/t/graphics-card-not-available/66269/96 "2025-05-05T12:56:39Z")

</div>

Given the issue in this thread is a driver level issue and two of the kernels and one of the OSes listed do not exhibit the particular driver bug, I’d recommend opening a support ticket. if the dGPU is not appearing in windows device manager nor linux lspci commands, then something different is happening, and the support team would be equipped to help you troubleshoot and to handle warranty replacement of parts should that be necessary and applicable.

This being a community forum the support team does not actively monitor it, so opening a ticket is the correct way to get their attention.

---

<div class="post-metadata">

**Author:** ![TechPriestNhyk](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/techpriestnhyk/32/27853_2.png) [@TechPriestNhyk](https://community.frame.work/u/TechPriestNhyk)\
**Post date:** [May 8, 2025, 1:45pm UTC](https://community.frame.work/t/graphics-card-not-available/66269/97 "2025-05-08T13:45:29Z")

</div>

I finally worked up the courage to update to Fedora 42 last night. I was incredibly surprised, and pleased, to find that my graphics card worked (kernel 6.14.5)! I don’t know if it’s 100% reliable, I only did just a little testing, but it did at least work on that boot 🙂 .

---

<div class="post-metadata">

**Author:** ![Tealk](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/tealk/32/24794_2.png) [@Tealk](https://community.frame.work/u/Tealk)\
**Post date:** [May 8, 2025, 6:43pm UTC](https://community.frame.work/t/graphics-card-not-available/66269/98 "2025-05-08T18:43:51Z")

</div>

i didn’t dare to update anymore, would you like to confirm again when you have tested it for a few days/restarts?

---

<div class="post-metadata">

**Author:** ![TechPriestNhyk](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/techpriestnhyk/32/27853_2.png) [@TechPriestNhyk](https://community.frame.work/u/TechPriestNhyk)\
**Post date:** [May 8, 2025, 6:47pm UTC](https://community.frame.work/t/graphics-card-not-available/66269/99 "2025-05-08T18:47:47Z")

</div>

Yeah, I’ll report back either once I have an issue, or sometime next week if I haven’t had an issue. If I do run into an issue, I see my 6.13.5 kernel is still there, so I should be able to boot using that and still hack my way through.

---

<div class="post-metadata">

**Author:** ![Tealk](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/tealk/32/24794_2.png) [@Tealk](https://community.frame.work/u/Tealk)\
**Post date:** [May 8, 2025, 7:04pm UTC](https://community.frame.work/t/graphics-card-not-available/66269/100 "2025-05-08T19:04:39Z")

</div>

You can pin a deployment so that it never gets cleaned up, that’s what I currently do with a version that works.

```auto
sudo ostree admin pin 0

```

0 is the first to be displayed for the status

```auto
rpm-ostree status

```

The command to pick up the pin is a little strange

```auto
sudo ostree admin pin --unpin 0

```

[Previous page](https://community.frame.work/t/graphics-card-not-available/66269.md?page=4)

[Next page](https://community.frame.work/t/graphics-card-not-available/66269.md?page=6)
