backports.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Liu, Kainan (GE Healthcare)" <Kainan.Liu@ge.com>
To: "backports@vger.kernel.org" <backports@vger.kernel.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Issue about Deploying ath11k on SLES 15 SP4
Date: Wed, 16 Nov 2022 10:53:01 +0000	[thread overview]
Message-ID: <DM5P101MB0237E3ED4786464058E592E6EB079@DM5P101MB0237.NAMP101.PROD.OUTLOOK.COM> (raw)

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

Hi Backports Project Team,

Thank you for providing the project. Me and my team are trying to use Backports to install ath11k on our system but we have met some problems.

We have successfully built the Backports Project and installed modules on our system. When I boot up the system, it reports some issues like:

[    3.815040] ath11k_pci 0000:06:00.0: BAR 0: assigned [mem 0xb3200000-0xb33fffff 64bit]
[    3.815094] ath11k_pci 0000:06:00.0: enabling device (0000 -> 0002)
[    3.815314] ath11k_pci 0000:06:00.0: qcn9074 hw1.0
[    3.815316] ath11k_pci 0000:06:00.0: failed to register to mhi bus, err = -22
[    3.815352] ath11k_pci 0000:06:00.0: failed to register mhi: -22
[    3.815459] ath11k_pci: probe of 0000:06:00.0 failed with error -22

I have checked the code, and found it was because the driver could not get Length of the MHI MMIO region. 

So I checked the version of those modules, and I found packages like mhi.ko having a version of 5.15, which was built from backports, like pic 1 in the attachment.

And for packages like ath.ko and ns.ko, they have a version of the kernel version, like pic 2 in the attachment.

We are using SLES 15 SP4 with kernel version of 5.14.21-150400.22-default, and backports-5.15.58-1. 

If you need more information, please contact me and I will reply the email as soon as possible.

Thank you!

Best,
Liu, Kainan(he/him)
Software Engineer
Surgery Engineering, China
GE Healthcare

T +86 15611095678


[-- Attachment #2: 1.PNG --]
[-- Type: image/png, Size: 12425 bytes --]

[-- Attachment #3: 2.PNG --]
[-- Type: image/png, Size: 13436 bytes --]

                 reply	other threads:[~2022-11-16 11:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=DM5P101MB0237E3ED4786464058E592E6EB079@DM5P101MB0237.NAMP101.PROD.OUTLOOK.COM \
    --to=kainan.liu@ge.com \
    --cc=backports@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.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).