WeirdTreeThing
Audio not working on botenflex
Describe the bug Currently I can't get audio to work on my IdeaPad Flex 3, no matter what distro I try.
Boardname Botenflex
Logs debug-logs-Botenflex-2025-02-08_08h32m.tar.gz
I've run the script again, running Archlinux using the 6.13.5-1-cachyos kernel. Device is shown, though when testing no audio output is being produced.
I wonder if the old downstream jsl topologies are still needed. You can try to replace /lib/firmware/intel/sof-tplg/sof-jsl-rt5682-rt1015.tplg with https://github.com/WeirdTreeThing/chromebook-linux-audio/raw/ae2f8cf30a26806376cc8591af4a66d33a763ef4/conf/sof/tplg/sof-jsl-rt5682-rt1015.tplg. And make sure you compress the new one with the same type of firmware compression you already have.
I wonder if the old downstream jsl topologies are still needed. You can try to replace
/lib/firmware/intel/sof-tplg/sof-jsl-rt5682-rt1015.tplgwith https://github.com/WeirdTreeThing/chromebook-linux-audio/raw/ae2f8cf30a26806376cc8591af4a66d33a763ef4/conf/sof/tplg/sof-jsl-rt5682-rt1015.tplg. And make sure you compress the new one with the same type of firmware compression you already have.
It didn't work, do I have to rerun the script ?
I wonder if the old downstream jsl topologies are still needed. You can try to replace
/lib/firmware/intel/sof-tplg/sof-jsl-rt5682-rt1015.tplgwith https://github.com/WeirdTreeThing/chromebook-linux-audio/raw/ae2f8cf30a26806376cc8591af4a66d33a763ef4/conf/sof/tplg/sof-jsl-rt5682-rt1015.tplg. And make sure you compress the new one with the same type of firmware compression you already have.
debug-logs-Boten-2025-03-30_22h18m.tar.gz
here are logs after the change i made
Bro, didn't you open your own issues, related to this issue? =D I still have not had the opportunity to try this solution in my issue xD
Bro, didn't you open your own issues, related to this issue? =D I still have not had the opportunity to try this solution in my issue xD
i was told to continue my issue here so it all remains in one place
You're absolutely right, my bad... 😅 Didn't read his @WeirdTreeThing answer in your issue.
As for the issue, I will take a closer look at the mainboard of my Chromebook later to be sure that it is not a hardware error (such as cold solder joints, something got destroyed while disabling hardware write protection yadayadayada). I'll keep you guys updated.
Unrelated I may or may not have lost my stock firmware backup... Any ideas how to (if I decide to someday) revert back to stock chrome os, or at least get a stock firmware image? Thx in advance
-bobby
You're absolutely right, my bad... 😅 Didn't read his @WeirdTreeThing answer in your issue.
As for the issue, I will take a closer look at the mainboard of my Chromebook later to be sure that it is not a hardware error (such as cold solder joints, something got destroyed while disabling hardware write protection yadayadayada). I'll keep you guys updated.
Unrelated I may or may not have lost my stock firmware backup... Any ideas how to (if I decide to someday) revert back to stock chrome os, or at least get a stock firmware image? Thx in advance
-bobby
If you figure it out tell me
So I thoroughly checked the mainboard, looked at nearly every transistor, capacitor, chip... Nothing that would indicate a hardware issue. Which means that I will try to figure out how everything works on a software level (any useful tips @WeirdTreeThing ?), study the logs, look where the issue could be and try to contribute to this project 😁
So I thoroughly checked the mainboard, looked at nearly every transistor, capacitor, chip... Nothing that would indicate a hardware issue. Which means that I will try to figure out how everything works on a software level (any useful tips @WeirdTreeThing ?), study the logs, look where the issue could be and try to contribute to this project 😁
Awesome, I hope this gets fixed
lowercase L. you could just copy and paste.
hwdriver@fedora:~$ aplay -l **** List of PLAYBACK Hardware Devices **** card 0: sofrt5682 [sof-rt5682], device 0: Speakers () [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofrt5682 [sof-rt5682], device 1: Headset () [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofrt5682 [sof-rt5682], device 2: HDMI1 () [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofrt5682 [sof-rt5682], device 3: HDMI2 () [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofrt5682 [sof-rt5682], device 4: HDMI3 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0
Well that does look like the fixed topology. Maybe try aplay -D plughw:0,0 /usr/share/sounds/alsa/Front_Center.wav. Just a warning that if sound does work it will be quite loud. Ctrl + C to cancel early.
Well that does look like the fixed topology. Maybe try
aplay -D plughw:0,0 /usr/share/sounds/alsa/Front_Center.wav. Just a warning that if sound does work it will be quite loud. Ctrl + C to cancel early.
What about the headphone jack sounding like the souls of the damned?
Well that does look like the fixed topology. Maybe try
aplay -D plughw:0,0 /usr/share/sounds/alsa/Front_Center.wav. Just a warning that if sound does work it will be quite loud. Ctrl + C to cancel early.
no sound
hwdriver@fedora:~$ systemctl --user status pipewire ● pipewire.service - PipeWire Multimedia Service Loaded: loaded (/usr/lib/systemd/user/pipewire.service; disabled; preset: disabled) Drop-In: /usr/lib/systemd/user/pipewire.service.d └─00-uresourced.conf /usr/lib/systemd/user/service.d └─10-timeout-abort.conf Active: active (running) since Wed 2025-04-02 15:56:56 +03; 4min 35s ago Invocation: f1cc1f02da414cd39fab2bb13f0db84f TriggeredBy: ● pipewire.socket Main PID: 1507 (pipewire) Tasks: 3 (limit: 4371) Memory: 3.3M (peak: 7.7M swap: 5M swap peak: 6.9M) CPU: 148ms CGroup: /user.slice/user-1000.slice/[email protected]/session.slice/pipewire.service └─1507 /usr/bin/pipewire
Apr 02 15:56:56 fedora systemd[1231]: Started pipewire.service - PipeWire Multimedia Service.
maybe this is why
hwdriver@fedora:~$ systemctl --user enable --now pipewire pipewire-pulse Created symlink '/home/hwdriver/.config/systemd/user/default.target.wants/pipewire.service' → '/usr/lib/systemd/user/pipewire.service'. Created symlink '/home/hwdriver/.config/systemd/user/sockets.target.wants/pipewire.socket' → '/usr/lib/systemd/user/pipewire.socket'. Created symlink '/home/hwdriver/.config/systemd/user/default.target.wants/pipewire-pulse.service' → '/usr/lib/systemd/user/pipewire-pulse.service'. Created symlink '/home/hwdriver/.config/systemd/user/sockets.target.wants/pipewire-pulse.socket' → '/usr/lib/systemd/user/pipewire-pulse.socket'. hwdriver@fedora:~$ systemctl --user status pipewire ● pipewire.service - PipeWire Multimedia Service Loaded: loaded (/usr/lib/systemd/user/pipewire.service; enabled; preset: disabled) Drop-In: /usr/lib/systemd/user/pipewire.service.d └─00-uresourced.conf /usr/lib/systemd/user/service.d └─10-timeout-abort.conf Active: active (running) since Wed 2025-04-02 15:56:56 +03; 6min ago Invocation: f1cc1f02da414cd39fab2bb13f0db84f TriggeredBy: ● pipewire.socket Main PID: 1507 (pipewire) Tasks: 3 (limit: 4371) Memory: 2.7M (peak: 7.7M swap: 5M swap peak: 6.9M) CPU: 201ms CGroup: /user.slice/user-1000.slice/[email protected]/session.slice/pipewire.service └─1507 /usr/bin/pipewire
Apr 02 15:56:56 fedora systemd[1231]: Started pipewire.service - PipeWire Multimedia Service.
i ran this
still no sound
What about the headphone jack sounding like the souls of the damned?
Well maybe the topology really is broken.
What about the headphone jack sounding like the souls of the damned?
Well maybe the topology really is broken.
headphone jack output
i knew this wasn't going to be easy because I was having the problem. this always happens lol
hwdriver@fedora:~$ aplay -D plughw:0,0 /usr/share/sounds/alsa/Front_Center.wav aplay: main:850: audio open error: Device or resource busy hwdriver@fedora:~$ aplay -D plughw:0,0 /usr/share/sounds/alsa/Front_Center.wav aplay: main:850: audio open error: Device or resource busy hwdriver@fedora:~$
new development
Probably just because your audio server is controlling it.
what now? whats the next step in fixing this?