Github messages for voidlinux
 help / color / mirror / Atom feed
From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: sof-firmware: use provided install script
Date: Tue, 26 Jan 2021 04:12:32 +0100	[thread overview]
Message-ID: <20210126031232.OfKQqTyklJuCqYJHPqK1DoPz066WMLEMfQgj0TlpYAc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27917@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 964 bytes --]

There's a merged pull request on the void-packages repository

sof-firmware: use provided install script
https://github.com/void-linux/void-packages/pull/27917

Description:
**note** this message may be out of date due to commits being squashed. Refer to the latest commit message instad.

After hours of trying to find out why SOF (from repo) didn't like my
hardware, I tried installing the archive directly from
github.com/thesofproject/sof-bin/ instead. To my surprise, it worked!

Taking a closer look at the template, I realized that the firmware files
for my system weren't linked, causing the following errors on boot.

```
[   11.829580] sof-audio-pci 0000:00:1f.3: error: request firmware intel/sof/sof-tgl.ri failed err: -2
[   11.829709] sof-audio-pci 0000:00:1f.3: error: failed to load DSP firmware -2
[   11.830177] sof-audio-pci 0000:00:1f.3: error: sof_probe_work failed err: -2
```

**Note**
I have only tested this on Tiger Lake.

      parent reply	other threads:[~2021-01-26  3:12 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-14  9:26 [PR PATCH] sof-firmware: link firmwares for Jasper Lake and Tiger Lake adriangoransson
2021-01-14 10:26 ` [PR PATCH] [Updated] " adriangoransson
2021-01-16  3:15 ` [PR REVIEW] " cinerea0
2021-01-16  4:24 ` cinerea0
2021-01-16  9:17 ` [PR PATCH] [Updated] " adriangoransson
2021-01-16  9:17 ` [PR REVIEW] " adriangoransson
2021-01-20  0:06 ` sof-firmware: link firmwares for Elkhart " ericonr
2021-01-20  5:50 ` cinerea0
2021-01-20  9:07 ` adriangoransson
2021-01-20 15:27 ` ericonr
2021-01-21  0:29 ` cinerea0
2021-01-21 20:45 ` adriangoransson
2021-01-21 20:45 ` adriangoransson
2021-01-21 22:37 ` cinerea0
2021-01-23 10:51 ` [PR PATCH] [Updated] " adriangoransson
2021-01-23 10:55 ` sof-firmware: use provided install script adriangoransson
2021-01-26  3:12 ` ericonr
2021-01-26  3:12 ` ericonr [this message]

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

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

  git send-email \
    --in-reply-to=20210126031232.OfKQqTyklJuCqYJHPqK1DoPz066WMLEMfQgj0TlpYAc@z \
    --to=ericonr@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /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 NNTP newsgroup(s).