You are not logged in.
Here is the link to my probe :
linux-hardware.org/?probe=7b7eb437c6
Offline
What is the result of "inxi -Axxx" and "lsmod | grep snd" (read manual for lsmod)
In BunsenLabs and/or Boron ?
Offline
aplay -l
aplay: device_list:274: no soundcards found...
sudo systemctl status alsa-restore.service
alsa-restore.service - Save/Restore Sound Card State
Loaded: loaded (/lib/systemd/system/alsa-restore.service; static)
Active: inactive (dead)
Docs: man:alsactl(1)
and when I start it, it says
alsa-restore.service - Save/Restore Sound Card State
Loaded: loaded (/lib/systemd/system/alsa-restore.service; static)
Active: inactive (dead)
Docs: man:alsactl(1)
sept. 12 17:06:25 bunsenlabs systemd[1]: Condition check resulted in Save/Restore Sound Card State being skipped.
sudo dmesg | grep -i snd
[ 12.068322] snd_hda_intel 0000:00:0e.0: DSP detected with PCI class/subclass/prog-if info 0x040100
[ 12.275359] snd_soc_skl 0000:00:0e.0: DSP detected with PCI class/subclass/prog-if info 0x040100
and in BL Boron:
sudo systemctl --user status pipewire
I'll do that just after, I don't try it now because I need to restart my computer so lose what I'm typing.
Can you se your card if you start alsamixer (in terminal]?
There is only one card named Master so I think the answer is no.
Is sound an important issue on the machine?
Until (if ever) the sound is fixed, you can use an external usb soundcard. There is many usb-headsets, that work well with linux. Or, do you have an empty cardslot? Or, you can go back to ZorinOs.
That's what I'm doing rn, using an external Bluetooth device for sound and I would like to use BunsenLabs or Boron, they are lightweight and cool !
Your title for your help request is misleading. "no soundcard detected" when inxi says it is detected...
What should I change it to ?
That is the old driver name, in old oldstable debian. How can you have that driver in BL beryllium and after manual installation from of ver 1.7 from https://github.com/thesofproject/sof-bin? It does not make any sense.
I don't know
Last edited by ric21000 (2023-09-12 15:18:09)
Offline
So, now you know what pc you own. Good.
No, bios is not "payload", if you mean "the actual information or message in transmitted data, as opposed to automatically generated metadata."
BIOS, is an acronym, stands for "Basic Input/Output System". "...is firmware used to provide runtime services for operating systems and programs and to perform hardware initialization during the booting process (power-on startup)"
https://en.wikipedia.org/wiki/BIOS
Often it is better to have newer kernel/firmware. So, update your coreboot. Check bios settings. Boot to boron. Investigate if audio driver loads and your audio hardware is detected and works.
If it were my computer, I would install boron, instead of work in boron live.
If you can't get any audio working in BL boron, you can test boot Debian testing; Debian 13, Trixie live. for example: https://cdimage.debian.org/cdimage/week … 4-lxqt.iso
I think, I would change subject line to: "Acer Chrome book, No audio".
// Regards rbh
Please read before requesting help: "Guide to getting help", "Introduction to the Bunsenlabs Lithium Desktop" and other help topics under "Help & Resources" on the BunsenLabs menu
Offline
No, bios is not "payload", if you mean "the actual information or message in transmitted data, as opposed to automatically generated metadata."
BIOS, is an acronym, stands for "Basic Input/Output System". "...is firmware used to provide runtime services for operating systems and programs and to perform hardware initialization during the booting process (power-on startup)"
https://en.wikipedia.org/wiki/BIOS
Yes, I'm not talking about BIOS in general, but I think this BIOS acts like a payload.
Like here :
mrchromebox.tech/#firmware
The firmware used by ChromeOS devices is built around serveral open-source projects, and consists (mainly) of a hardware init component (coreboot) and one or more payloads (depthcharge for Verified Boot and ChromeOS, SeaBIOS for Legacy Boot Mode) which are subsequently executed.
Often it is better to have newer kernel/firmware. So, update your coreboot. Check bios settings. Boot to boron. Investigate if audio driver loads and your audio hardware is detected and works.
Ok thanks I'll do that
If it were my computer, I would install boron, instead of work in boron live.
Should I install it instead of BunsenLabs (after having save all my important files obviously) ? Or is it a bad idea because it's in beta ?
If you can't get any audio working in BL boron, you can test boot Debian testing; Debian 13, Trixie live. for example: https://cdimage.debian.org/cdimage/week … 4-lxqt.iso
Ok thanks
I think, I would change subject line to: "Acer Chrome book, No audio".
Ok good idea !
Offline
/tmp/flashrom: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /tmp/flashrom)
/tmp/flashrom: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /tmp/flashrom)
I get this error while launching the script, do you know how I can install the correct version of Glibc ?
Offline
I think I found how
Offline
/tmp/flashrom: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /tmp/flashrom) /tmp/flashrom: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /tmp/flashrom)
I get this error while launching the script, do you know how I can install the correct version of Glibc ?
I guess you are doing this from your BL Beryllium (Debian bullseye) installation. Then command
apt policy glibc*
will return (among others)
glibc-source:
Installed: (none)
Candidate: 2.31-13+deb11u6
In BL boron, the response will be:
glibc-source:
Installed: (none)
Candidate: 2.36-9+deb12u1
2.36-9, is higher than 2.34, requirement met. If I guess right...
Requirements met if you install (or upgrade to, but i think install is better in this case) BL boron. Even if the amd64-iso is in alpha, i have not noticed any serious problem, only minor glitches.
Or, you can boot boron live session and run the mrchromebox firmware script.
// Regards rbh
Please read before requesting help: "Guide to getting help", "Introduction to the Bunsenlabs Lithium Desktop" and other help topics under "Help & Resources" on the BunsenLabs menu
Offline
apt policy glibc*
It says
N: Unable to locate package glibc-2.33
N: Couldn't find any package by glob 'glibc-2.33'
N: Unable to locate package glibc-2.34
N: Couldn't find any package by glob 'glibc-2.34'
I think that's because I tried to compile them manually, with the prefix /usr/local/glibc-2.33 and /usr/local/glibc-2.34 to not make the system unusable.
2.36-9, is higher than 2.34, requirement met. If I guess right...
Requirements met if you install (or upgrade to, but i think install is better in this case) BL boron. Even if the amd64-iso is in alpha, i have not noticed any serious problem, only minor glitches.Or, you can boot boron live session and run the mrchromebox firmware script.
Ok cool, I will install it
Offline
I updated the BIOS
Offline
Unfortunately the sound still doesn't work in live Boron (I didn't installed it yet) nor BL
Offline
*on BL Boron
Offline