not at the moment… I’ve disabled the modprobe blacklist because I think it’s kinda required for the AE-7 to work. I’m trying to see what is conflicting with it to see if I can disable it or change something there. I’ll continue tomorrow.
1 Like
I’m going to compile 6.4rc1 and try it. If this does not fix it I’ll open a bug report on the kernel bugzilla site. At this point i don’t know what else to try.
2 Likes
Have you tried changing from pipewire to pulse audio or try using OSS?
I think I tried pulse audio yesterday. Didn’t work. I’ll try it again later meanwhile compiling the kernel takes a while at this point in time.
I’m beginning to suspect something’s wrong with the kernel a bug of some sort.
Quick Google told me - make sure you have unplugged headphones (or other jacks probably). Advice coming from Windows, sounds idiot, but who knows… If you already boot without anything connected to the card - please ignore.
Also I would try with kernel 5.10 - first one with support for AE-7 - you would have proof, nothing broke in between then and 6.x
Good job on booting it up anyway. Did you try to load blacklisted modules AFTER you booted up? Make sure you log this, I would expect crash, but maybe you would get more useful info.
As always those issues are fascinating, I will eat popcorn and observe your struggles, good luck!
I actually tried 5.15 but I’ll also try 5.10 after I tried 6.4rc1. Interesting for the jacks. I’ll also try that. I didn’t actually try to load the module after booting as I don’t actually know how to at this point but a quick google search sent me on my way with modprobe. I also expect a crash but we never know maybe I’ll be lucky. It just takes forever to compile the kernel. If i’m lucky enough I can pinpoint which module is causing the issue and report it to the maintainer. it’s most likely snd_hda_intel or xhci_hcd from the errors visible in my pictures. I’m digging deeper into the linux kernel that I have ever been. I’m used to linux just working fine. Never really debugged that far.
1 Like
Well loading the module does not really crash the OS but actually kills the USB controller and after that I can’t control any usb device that means keyboard et mouse are bye bye. I’ll try the other kernel another day. You can guess from my answer that 6.4rc1 does not help either.
1 Like
This is 2 years ago. Maybe somehow can touch base with the user through reddit?
maybe a long shot, but have you disabled Fastboot in BIOS? It caused some very random issues on some systems already, and it does not hurt when it is disabled. With fastboot enabled, some system devices aren’t correctly initialized during boot in some cases.
Yeah I’ve already tried fast startup in Windows and Fast boot in the bios. I never actually enable fast boot. I`ve also tried xhci hand-off and disabling the SATA controller at some point. If there is a bios option that solves that it must be kinda obscure. AMD bioses have so much options which are not that well documented that it’s kinda hard to find anything related.
@Hyrules
In my opinion i think it’s using the wrong bus ID maybe? There was a patch put in for the AE7.
SND_PCI_QUIRK(0x1102, 0x0081, "Sound Blaster *AE-7*", QUIRK_AE7)
I might try to change it inside the local code for the kernel to see if this fix it and recompile. I’ll try it tomorrow.
well nothing new on that front. I tried compiling the 5.10 kernel but it gives me an error (error: ‘GSI_CONTINUE_LINKING’ was not declared in this scope) so it seems I won’t be able to try it. I can blacklist the snd_hda_intel and boot but as soon as I force the module to load with modprobe the computer freezes and the only way to get back is to force power off and restart.
Do you have the latest kernel and also alsa updates?
Yes I updated it a little earlier. I’m starting to believe that you are right about the SND_PCI_QUIRK(0x1102, 0x0081, "Sound Blaster *AE-7*", QUIRK_AE7)
Because it doesn’t match this :
67:00.0 Audio device [0403]: Creative Labs Device [1102:0010] (rev 01)
1102 is good but 0010 is not the same as the 0x0081
I’m just guessing because i don’t know for sure but it seems like a hardware conflict. I wonder if you can use jack retask to change the pins? Or somehow assign a different ID number?
ok i’m going to try to change the value and compile my own kernel. If this fixes the issues, I’ll most likely submit a bug report to the upstream kernel. Worst case scenario it won’t work.
Well changing the value didn’t help when compiling the kernel. It still froze at boot so at this point the only thing I can do is hope someone upstream fixes it or that a bios update eventually fixes it. Not much I can do unless someone has more ideas ?
I think from all the information I have read on this that it is either the wrong pin or ID or combination of also firmware. Here is another bit of info from the original poster who helped with creating a patch.
Edit: Maybe this info about patch on google drive helps?
https://bbs.archlinux.org/viewtopic.php?id=236364
Edit2:
https://lore.kernel.org/lkml/20210315135547.783481944@linuxfoundation.org/