Thanks @Sheila_Flanagan ,
On the MX system let’s try aplay, I believe this uses sound device directly.
Something like:
aplay [a-valid-sound-file.wav] --device plughw: --device plughw:CARD=sofhdadsp,DEV=31
If I composed it right, it would play the valid soundfile on sofhdadsp/dev 31 (analog port).
Do you hear sound from the speaker so?
Thanks, @Daniel_Phillips
I do love EndeavourOS, but I do not look forward to a complete change to the daily working laptop with MX that I have now.
I thought you always had a saved previous kernel to boot into from GRUB, but I must have missed that tick box as I only have the current one when I try to use a different one.
Obviously, the Arch-based Garuda and probably others have no issues with using my internal speakers, but MX did not have an issue before either.
I am making a CZ image of the drive with both right now so in case I want to switch or make any changes here that breaks my systems.
Sheila
Thanks @kovacslt as soon as the Clonezilla image finishes I will test this. I decided I better have a current one since we are making changes.
My issue last night with not being able to connect the ext BT speaker caused me to have to use Timeshift to go back to the previous day and that fixed it. So better to have a complete image to restore while everything else still works.
Should be finished within an hour. I thought it was already completed, but that was just the MX partition that went quickly. I think Garuda, using BTRFS must take longer as it is showing twice the remaining time that MX did.
I will post results then.
Sheila
I get the response:
Playing WAVE 'Alesis-Fusion-Tremolo-Strings-C4.wav' : Signed 16 bit
Little Endian, Rate 44100 Hz, Stereo
But no sound is heard at 150% volume. I checked alsamixer and all are unmuted.
Sheila
Look in /boot, with ls -l
You will get the dates of each kernel file
The easy way to install a newer kernel is tomuse the MX tool for software updates
Warning: Dont try to change from an AHS kernel to a nomal kernel or vice/versa. I tried that and absolutely wrecked my MX package system…forced to reinstall.
Check the kernel versions ( /boot again) and the kernel config … each kernel version has a config file in /boot. … they are large files, hard to check.
Also, if your current MX has more than one kernel installed, you might try booting an older kernel. Normally grub woukd boit the latest one by default. To do this use the Advanced/Repair option in the grub menu… it will list all avsilable kernels and you can choose
root@mx--acer:/boot# ls -l
total 99741
-rw-r--r-- 1 root root 265577 Sep 17 2023 config-6.5.0-1mx-ahs-amd64
drwxrwxr-x 3 root root 512 Dec 31 1969 efi
drwxr-xr-x 7 root root 4096 Feb 1 22:09 grub
-rw-r--r-- 1 root root 84022963 Jan 11 09:24 initrd.img-6.5.0-1mx-ahs-amd64
-rw-r--r-- 1 root root 8126464 Sep 10 14:18 intel-ucode.img
-rw-r--r-- 1 root root 138712 Feb 11 2023 memtest86+ia32.bin
-rw-r--r-- 1 root root 139776 Feb 11 2023 memtest86+ia32.efi
-rw-r--r-- 1 root root 144312 Feb 11 2023 memtest86+x64.bin
-rw-r--r-- 1 root root 145408 Feb 11 2023 memtest86+x64.efi
-rw-r--r-- 1 root root 83 Sep 17 2023 System.map-6.5.0-1mx-ahs-amd64
drwxr-xr-x 2 root root 4096 Mar 27 2024 uefi-mt
-rw-r--r-- 1 root root 9120576 Sep 17 2023 vmlinuz-6.5.0-1mx-ahs-amd64
Unfortunately, it appears I only have the latest kernel. I mentioned that earlier that when I tried, from GRUB, to load an earlier one, there were none listed. I thought it always kept the previous kernel when updating to a newer one.
I do have the AHS (due to Nvidia RTX 3070) and I would def need to keep that, but can I add an older kernel for booting in recovery from GRUB? Not sure how that works.
Thanks,
Sheila
Not sure if things have changed, but an older Ubuntu forum had the same question asked and instructs:
To add a new kernel to grub2:
Move your kernel to /boot/
Run sudo update-grub
update-grub will scan your computer for kernels, and create a listing of available kernels at boot.
In order for you to select which kernel to boot at boot time, you may have to hold the SHIFT button down right after your BIOS does its posting.
You can edit /etc/default/grub to change default boot options and parameters that you may need.
That seems to indicate I could download the MX point releases prior to my current one and move them to /boot and update-grub would find them?
Sheila
Thanks @Gary I was trying to find it in the package manager, but looking at the wrong name. Still not sure about the difference between those though, and if I should use package manager GUI or just download from MX download each point release.
Sheila
Use the MX tool. Search for linux or kernel. Choose another ahs kernel. Tell it to install it . It will probably do the update-grub automatically… if not do it manually when the install finishes.
Note. I am assuming MX is in control of grub.
If Garuda controls grub you have to do an update-grub in garuda.
To see all kernels in the grub menu, you have to choose Advanced
The Package Installer? Do I look for the package by point release name? or as Gary showed?
Which ones do I want?
Thanks,
Sheila
I am installing 6.6 & 6.8 since later point releases show 6.12. Will see if I can boot into one of them once installed and GRUB updates.
Sheila
As Gary showed
Debian***AHS
I think it ran into an issue. Here is the last part after installing 6.8.12:
update-initramfs: Generating /boot/initrd.img-6.8.12-amd64/etc/kernel/postinst.d/zz-update-grub:Found theme: /boot/grub/themes/mx_linux/theme.txtFound linux image: /boot/vmlinuz-6.8.12-amd64Found initrd image: /boot/intel-ucode.img /boot/initrd.img-6.8.12-amd64Found linux image: /boot/vmlinuz-6.6.15-amd64Found initrd image: /boot/intel-ucode.img /boot/initrd.img-6.6.15-amd64Found linux image: /boot/vmlinuz-6.5.0-1mx-ahs-amd64Found initrd image: /boot/intel-ucode.img /boot/initrd.img-6.5.0-1mx-ahs-amd64Found mtest-64.efi image: /boot/uefi-mt/mtest-64.efiFound Garuda Linux Bird of Prey (Soaring) on /dev/nvme0n1p5Adding boot menu entry for EFI firmware configurationdoneSetting up linux-kbuild-6.8.12 (6.8.12-1~mx23ahs) ...Setting up linux-headers-6.8.12-common (6.8.12-1~mx23ahs) ...Setting up linux-headers-6.8.12-amd64 (6.8.12-1~mx23ahs) .../etc/kernel/header_postinst.d/dkms:
dkms: running auto installation service for kernel 6.8.12-amd64./usr/sbin/dkms.mx autoinstall --kernelver 6.8.12-amd64dkms: autoinstall for kernel: 6.8.12-amd64.
But a pop up said something about dpkg being busy or in use, then it went away, so not sure if it worked or not.
Will reboot to see if they are not available from GRUB. BTW, MX controls GRUB.
Sheila
They were all there in Advanced in GRUB. Booted to the oldest 6.6, no sound in VLC nor in terminal with @kovacslt instructions.
I did note that there was now a different output called Pulse Effects one for mic and one for speaker. I tried both the TigerLake speaker as well as that one but no sound.
I hope I don’t have to go farther back, as 6.3 is the oldest. Will boot into 6.8 now.
Sheila
Have now booted into 6.5, 6.6 & 6.8–no sound. All of them added a Pulse Effects and set it as the default sound output, and while the file is playing, bars surge and if I speak, the microphone bar surges with audio input. But no sound is heard.
I will try to add the oldest 6.3 and see what happens.
Sheila
You are close to concluding it is not a kernel problem
Are the kernel boot parameters in Garuda different to those in MX?
cat /proc/cmdline
or look in grub menu with ‘e’
Try adding the boot parameter ‘intel_iommu=false’
I am running out of ideas
In MX (booting 6.5 kernel):
$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-6.5.0-1mx-ahs-amd64 root=UUID=2779c5bc-45ad-4909-bd7c-de1dcd54dafd ro splash init=/lib/systemd/systemd
In Garuda
BOOT_IMAGE=/@/boot/vmlinuz-linux-zen root=UUID=406d8c92-eb3f-4642-8532-fe14c97261cd rw rootflags=subvol=@ quiet loglevel=3 ibt=off
Let me go add the boot parameter to current MX kernel at boot.
Sheila
So added boot parameter to both 6.3 and current MX 23.5 kernel and now in my latest kernel boot, the Pulse Effects app are back for speaker/mic in volume control equalizer. Sound plays, but no sound heard.
I even tried to hook up via audio jack an external line-in speaker, switched to it and it made all static/loud hum except when audio was playing, which was not heard, but obviously stopped the hum because it was?
I have also since tried using the HDMI sound, ensured volume is max on monitor itself, but no sound there either.
So I guess I will just have to use my BT speaker whether traveling or at home.
Thanks @everyone!!
Sheila
I think ‘ibt=off’ is irrelevant.
Sorry, we have failed you this time.