unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: "Erik Giorgis" <egiorgis@egiorg.is>
To: Kaelyn <kaelyn.alexi@protonmail.com>,
	"Felix Lechner" <felix.lechner@lease-up.com>
Cc: help-guix@gnu.org, "Dr. Arne Babenhauserheide" <arne_bab@web.de>
Subject: Re: Intel 13700k iGPU not recognised
Date: Fri, 24 Mar 2023 17:43:53 +0100	[thread overview]
Message-ID: <be1cb673-3765-4517-8832-838a8277f8bd@app.fastmail.com> (raw)
In-Reply-To: <ru-Rf0bpadeBIQvI_NysqtqaDlKY_UNNN5RIdoFJQc-gkgxF_UXyTvQNpRSyIgP8zak9OwnLXTJBb6tHHziqxA_bmOh_lYLK5Kep2x6m6BY=@protonmail.com>

Hi Felix and Kaelyn

Thank you for the prompt and detailed reply! 

I get mesa being too old for my CPU, and I also tried installing a newer mesa version (that I found packaged in the wild, could also be that it wasn't perfectly packaged but it built fine). 

What confuses me more is the output of lspci, I just booted a new Guix installation  iso and dropped into a terminal, and this is the output from lspci:

00:00.0 Host bridge: Intel Corporation Device a703 (rev 01)
00:02.0 VGA compatible controller: Intel Corporation Device a780 (rev 04)
00:08.0 System peripheral: Intel Corporation Device a74f (rev 01)
00:0a.0 Signal processing controller: Intel Corporation Device a77d (rev 01)
00:14.0 USB controller: Intel Corporation Device 7ae0 (rev 11)
00:14.2 RAM memory: Intel Corporation Device 7aa7 (rev 11)
00:16.0 Communication controller: Intel Corporation Device 7ae8 (rev 11)
00:17.0 SATA controller: Intel Corporation Device 7ae2 (rev 11)
00:1c.0 PCI bridge: Intel Corporation Device 7ab8 (rev 11)
00:1c.1 PCI bridge: Intel Corporation Device 7ab9 (rev 11)
00:1c.3 PCI bridge: Intel Corporation Device 7abb (rev 11)
00:1f.0 ISA bridge: Intel Corporation Device 7a86 (rev 11)
00:1f.3 Audio device: Intel Corporation Device 7ad0 (rev 11)
00:1f.4 SMBus: Intel Corporation Device 7aa3 (rev 11)
00:1f.5 Serial bus controller [0c80]: Intel Corporation Device 7aa4 (rev 11)
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05)
03:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02)

Just for reference, the kernel version: (but I had the same problem with the 6.2.7 kernel)
Linux gnu 6.0.10-gnu #1 SMP PREEMPT_DYNAMIC 1 x86_64 GNU/Linux

Before mesa, shouldn't the kernel take care of these devices? When on a different distro I get:

00:00.0 Host bridge: Intel Corporation Device a703 (rev 01)
00:02.0 VGA compatible controller: Intel Corporation Raptor Lake-S UHD Graphics (rev 04)
00:08.0 System peripheral: Intel Corporation Device a74f (rev 01)
00:0a.0 Signal processing controller: Intel Corporation Device a77d (rev 01)
00:14.0 USB controller: Intel Corporation Alder Lake-S PCH USB 3.2 Gen 2x2 XHCI Controller (rev 11)
00:14.2 RAM memory: Intel Corporation Alder Lake-S PCH Shared SRAM (rev 11)
00:16.0 Communication controller: Intel Corporation Alder Lake-S PCH HECI Controller #1 (rev 11)
00:17.0 SATA controller: Intel Corporation Alder Lake-S PCH SATA Controller [AHCI Mode] (rev 11)
00:1c.0 PCI bridge: Intel Corporation Alder Lake-S PCH PCI Express Root Port #1 (rev 11)
00:1c.1 PCI bridge: Intel Corporation Alder Lake-S PCH PCI Express Root Port #2 (rev 11)
00:1c.3 PCI bridge: Intel Corporation Device 7abb (rev 11)
00:1f.0 ISA bridge: Intel Corporation Device 7a86 (rev 11)
00:1f.3 Audio device: Intel Corporation Alder Lake-S HD Audio Controller (rev 11)
00:1f.4 SMBus: Intel Corporation Alder Lake-S PCH SMBus Controller (rev 11)
00:1f.5 Serial bus controller: Intel Corporation Alder Lake-S PCH SPI Controller (rev 11)
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05)
03:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02)

So might be that the problem is elsewhere, besides mesa?

Thank you and best regards,
Erik

On Tue, Mar 21, 2023, at 02:13, Kaelyn wrote:
> Hi Erik and Felix,
> 
> ------- Original Message -------
> On Tuesday, March 21st, 2023 at 12:26 AM, Felix Lechner <felix.lechner@lease-up.com> wrote:
> 
> 
> > 
> > 
> > Hi Erik,
> > 
> > On Mon, Mar 20, 2023 at 4:12 PM Erik Giorgis egiorgis@egiorg.is wrote:
> > 
> > > Hi
> > > 
> > > I installed guix on a new system, and would like to use Hyprland with it. I already have Hyprland working on an older laptop.
> > > However, on this new system I get an error that the iGPU is not supported by mesa.
> > 
> > 
> > It looks like Mesa3d support for your Raptor Lake GPU with PCI id
> > 0xa780 was merged on January 25, 2022. [1]
> > 
> > Guix presently ships version 21.3.8 of the Mesa library. [2] As I
> > understand, it contains merely bug fixes for Mesa 21.3.0, which was
> > released on November 17, 2021. [3] The version in Guix currently
> > therefore appears insufficient for your advanced—and I am sure, very
> > exciting—equipment.
> > 
> > Fortunately, an update of Mesa3d to version 22.2.1 is pending in our
> > 'core-updates' branch. [4] The merge process for that branch was
> > delayed a bit this time, but the updates should become available to
> > the general public soon. I think we are talking about a few weeks.
> > Please hang in there!
> > 
> > Among Guix contributors, Kaelyn Takata is probably better positioned
> > than I to validate or correct any information above. I copied Kaelyn.
> 
> Technically 'core-updates' has mesa 22.2.4 as of commit e5af53c51d, but otherwise that should be correct. Mesa 22.2.0 was released in Sept 2022, so should support your Raptor Lake GPU.
> 
> Cheers,
> Kaelyn
> 
> > 
> > As a side note, I also saw another potentially helpful patch by Dr.
> > Arne Babenhauser [5] but I am not sure how it fits into the pending
> > merge of "core-updates". Arne was likewise copied.
> > 
> > Sorry if the news is not as good as what you were hoping for. We are
> > working hard on your behalf. Thank you for using Guix!
> > 
> > Kind regards
> > Felix
> > 
> > [1] https://gitlab.freedesktop.org/mesa/mesa/-/commit/4e0eca7dc34942759638ab00eb006ba40284a7c5
> > [2] https://packages.guix.gnu.org/search/?query=mesa
> > [3] https://docs.mesa3d.org/relnotes/21.3.0.html
> > [4] https://issues.guix.gnu.org/58566
> > [5] https://issues.guix.gnu.org/62176
> 
> 

  reply	other threads:[~2023-03-24 16:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-20 23:11 Intel 13700k iGPU not recognised Erik Giorgis
2023-03-21  0:26 ` Felix Lechner via
2023-03-21  1:13   ` Kaelyn
2023-03-24 16:43     ` Erik Giorgis [this message]
2023-03-24 16:49       ` Felix Lechner via
2023-03-24 17:06         ` Erik Giorgis
2023-03-24 17:11           ` Felix Lechner via
2023-03-24 17:18             ` Erik Giorgis
2023-03-24 17:49               ` Felix Lechner via
2023-03-24 15:54 ` Samuel Schmidt
2023-03-24 16:04   ` Erik Giorgis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=be1cb673-3765-4517-8832-838a8277f8bd@app.fastmail.com \
    --to=egiorgis@egiorg.is \
    --cc=arne_bab@web.de \
    --cc=felix.lechner@lease-up.com \
    --cc=help-guix@gnu.org \
    --cc=kaelyn.alexi@protonmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).