-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Doesn't work on MateBook D16 2021 (Ryzen 4600H) #8
Comments
Do you still have the issue? |
Hi, my laptop is this Huawei Matebook D16 as well. If i can give you any info or try things i'll gladly do that. Thanks! |
Attach the dmesg output |
Sorry I did not see you answer! Duplicating the WXX9-M1040 entries and replacing them with M1010 fixes the issue. I can open an MR with the change so that you can hopefully push the change along with your upstream request before the release. |
@HexPandaa I will update the upstream driver with your SKU. Does the sound work ok on your laptop? |
Yep the sound works fine 👍 |
I did make the kernel with the config you added. Then i did:
Somewhere in between i used strip to make the initrd size smaller:
aplay -l only shows the hdmi sound. i tried:
with no success. In my /etc/modules everything is commented out. I attached my /etc/modprobe.d/blacklist.conf here: And and my dmseg output: Thanks for your help and the work you put in! |
Hey it works now! Using working-config-huawei-laptops.config as .config. Following HexPandas discovery, the solution was: Look at the first entry of "system information" of dmidecode
Handle 0x0001, DMI type 1, 27 bytes We can see that, not like Hexpandas Version: M1010, the Version here is M1020. Looking for occurences of HVY-WXX9 and copying the lines where M1040 is, in both of these 2 files:
then again compile and add to boot:
Result is working sound! |
Hey ! I also have this issue Looking at I modified the files I have never worked with the kernel or sound stuff before, so I don't even know where to start to troubleshoot this. Could I get some help ? Thanks alsamixer a |
Here are the dmesg logs of a fresh boot: dmesg.txt EDIT: I followed the instructions in codepayne/linux-sound-huawei#26 (comment) and https://github.com/codepayne/linux-sound-huawei/wiki (the last part about alsamixer), now the white noise stopped, and KDE doesn't recognize the sound card anymore (but alsamixer still does) EDIT 2: created another user and KDE now seem to detect the sound card. the sound is sped up, but that seem to be an ongoing problem in the issue I mentioned earlier. I guess it works now, thanks anyway ! |
@HexPandaa I sent the patch that adds support for your laptop: |
Hi, I've been trying to get sound on my MateBook for over a year, so thank you for creating this repo!
I tried your linux-sound-huawei repo but as it didn't seem to work, I'm trying this one.
No mater what I do, I only see the Dummy Output in the settings and
alsamixer
doesn't show any more outputs.Trying to investigate the problem, I found that the
DMI_EXACT_MATCH
for my device was not exactly correct.In acp-config.c, there is an exact math for
M1040
, however my DMI infos showsM1010
.pop-os-linux/sound/soc/amd/acp-config.c
Line 100 in b89f980
I tried changing the value in
acp-config.c
to match mine, but nothing changed.Do you have any idea where I could look for logs explaining why the driver is supposedly not loaded? I found no info in
dmesg
andjournalctl
.For the sake of completeness, I'm running Ubuntu 22.04.
Thanks a lot for your work!
The text was updated successfully, but these errors were encountered: