brunch
brunch copied to clipboard
sebanc
No Working essx8336
Hello. The sound card is defined as snd_hda_intel, the sound does not work, although my sound card is essx8389, how do I fix it?
have you tried disable_intel_hda option from chromeos settings?
When selecting Brunch patches, it is not possible to select "disable_intel_hda", if you manually register "options=$options, disable_intel_hda" or "options=disable_intel_hda" then nothing changes. If you use the 5.10 kernel, then a mixer appears and the driver is now sof-skl.
My processor: 6th gemini lake.
have you tried disable_intel_hda option from chromeos settings?
When selecting Brunch patches, it is not possible to select "disable_intel_hda", if you manually register "options=$options, disable_intel_hda" or "options=disable_intel_hda" then nothing changes. If you use the 5.10 kernel, then a mixer appears and the driver is now sof-skl.
My processor: 6th gemini lake.
In brunch settings, You have to select framework options by 'space' and move to next screen by 'enter'
In brunch settings, You have to select framework options by 'space' and move to next screen by 'enter'
Item "disable_intel_hda" is missing
Hello. Did this ever get resolved?
I have no sound on brunch ChromeOS on a Tactus Geoflex 110. I believe this is the same issue.
Hello. Did this ever get resolved?
I have no sound on brunch ChromeOS on a Tactus Geoflex 110. I believe this is the same issue.
I would not be surprised if the essx8336 issue has been solved in brunch with newer versions of the kernel as kernel 6.3 solved the issue on 2 different devices for me ... I need to check it out when I have time ...
Brunch ships with kernel 6.1, as it only ships lts kernels. Do you know how I can use a kernel newer than 6.1?
I am using manjaro with kernel 6.5 and sound works fine, but brunch still has no sound.
Please advise
https://linux-hardware.org/?view=computers&vendor=Tactus&model=GeoFlex+110
cant get sound working, any help?
I think I have it running ... almost. And very simple.
I own a Tactus Geobook 140, with probably similar hardware. Most of all, essx8336 sound which hasn't been working so far. Just recently, I found this website / repository:
https://github.com/gnickm/sof-essx8336-debian-fix
I used some of the steps to get the sound running under a few linux distros, here's what I found regarding brunch. To do this, I installed the current version (118 rammus based) freshly on my Geobook 140. As Options, I only chose Kernel 6.1 and allow updates / pwa, nothing more. BIOS setting are all set to factory default.
Under Kernel 6.1, all the sof firmware files etc. seem to be already in place. As opposed to kernel 5.15 and below, the sound card now appears as a device in chromeos, but no sound.
Seems that the only missing thing now is the "setup-alsa.sh" to be run in chromeos. To do this, I need to:
- change it to "c 1" twice, because in the Geobook 140 the essx8336 is the second card after the USB webcam
- transfer the script to a partition without "noexec" flag (I use /root)
- run the script with sudo from the shell (ALT+CRTL+F2, login "chronos")
After that, the sound card works, both with speakers and headphones. Here's my version of the script
#!/bin/bash
echo "--- Setting up ALSA output for ESSX8336"
# This may be different for your system, you can check it by running aplay -l
OUTPUT_DEVICE='-c 1'
amixer $OUTPUT_DEVICE cset name='Speaker Switch' on
amixer $OUTPUT_DEVICE cset name='Headphone Playback Volume' 3,3
amixer $OUTPUT_DEVICE cset name='Right Headphone Mixer Right DAC Switch' on
amixer $OUTPUT_DEVICE cset name='Left Headphone Mixer Left DAC Switch' on
amixer $OUTPUT_DEVICE cset name='DAC Playback Volume' 999,999
amixer $OUTPUT_DEVICE cset name='Headphone Mixer Volume' 999,999
amixer $OUTPUT_DEVICE sset Headphone 3
echo "--- Setting up ALSA output for ESSX8336"
# This may be different for your system, you can check it by running arecord -l
INPUT_DEVICE='-c 1'
amixer $INPUT_DEVICE cset name='ADC PGA Gain Volume' 7
amixer $INPUT_DEVICE cset name='ADC Capture Volume' 150
amixer $INPUT_DEVICE cset name='Internal Mic Switch' on
amixer $INPUT_DEVICE cset name='Headset Mic Switch' on
amixer $INPUT_DEVICE cset name='Differential Mux' 'lin2-rin2'
echo "=== Done!"
exit 0
Only snag: I need to run this after every boot.
@sebanc , can this be turned into a permanent feature / patch for the essx8336 sound card? Everything else (sof firmware, kernel > 5.17) seems to be there in the latest brunch OS.
Going to try again this weekend using your guide @agrimpelhuber , The latest brunch should be using a newer kernel, which may work OOB?
Haven't checked any newer kernel than 6.1 on brunch yet (is there a newer one?), but I doubt it: In all cutting-edge Linux Distros with newest kernels all the SOF firmware was complete, so from the fix, the main steps (getting newer firmware, finding a compatible kernel) was OK. But, like with brunch kernel 6.1, the mappings from above script were always missing.
And: The microphone (e.g. in a headset) never worked, buit that might well be due to crappy hardware.
Haven't checked any newer kernel than 6.1 on brunch yet (is there a newer one?),
@agrimpelhuber : kernel chromebook-6.6 added in https://github.com/sebanc/brunch-unstable/releases since Brunch r120 unstable 20240201 ...
@ameeno did you have success on your device ? I think I am going to try on my n4020 Kuu Yobook M ... google chrome working quite well on it on Fedora LXDE but I miss the "top url toolbar autohide" feature of chromeos (yandex browser not working as fast as chrome on this weakish n4020 device ...)
ok , tried with kernel 6.6 on latest brunch unstable but no sound on my device ... I am going to try to write a setup-alsa.sh script like agrimpelhuber did ... ( I ll try to check how Fedora with kernel 6.7 has this working ...)
When I tried with manjaro, a few weeks back, it was working! But it didn't work ootb with brunch!
OK the setup-alsa.sh script given by agrimpelhuber above ( see https://github.com/sebanc/brunch/issues/1692#issuecomment-1828425632 ) works nicely on my Kuu Yobook M if I set : OUTPUT_DEVICE='-c 0' and INPUT_DEVICE='-c 0' in it ...
... still a little pain to have to run it manually after each boot though but I can now enjoy watching and listening to youtube videos on my Yobook M with its great screen !
@pierro78, I just discovered that on teh very latest brunch version (chromeos Version 121.0.6167.212 updated the normal way, and Brunch r121 stable 20240224), there is a fix in the brunch settings (actually 2) to run the script on bootup. One for card 0, one for card 1. Works great on 2 different Geobooks-140. One is permanently connected to HDMI (so the internal sound is card 1), one is standalone (internal sound card 0). Both work fine with the respective script - yeah. Beith with Kernel 6.6, but also might work with 6.1 as before.
I haven't yet tested whether you can run both scripts, in case the internal sound changes from being card 0 to card 1 if HDMI is connected on startup. Will do that right away. But in the meantime, THANKS @sebanc and every one else involved for fixing this.
Edit: Just tested running both scripts on both machines, didn't work.
@pierro78, I just discovered that on teh very latest brunch version (chromeos Version 121.0.6167.212 updated the normal way, and Brunch r121 stable 20240224), there is a fix in the brunch settings (actually 2) to run the script on bootup. One for card 0, one for card 1. Works great on 2 different Geobooks-140. One is permanently connected to HDMI (so the internal sound is card 1), one is standalone (internal sound card 0). Both work fine with the respective script - yeah. Beith with Kernel 6.6, but also might work with 6.1 as before.
I haven't yet tested whether you can run both scripts, in case the internal sound changes from being card 0 to card 1 if HDMI is connected on startup. Will do that right away. But in the meantime, THANKS @sebanc and every one else involved for fixing this.
Edit: Just tested running both scripts on both machines, didn't work.
Hi, Sorry, Dont understand, How do I get the geobook-140 soundcards to work properly with latest brunch r121 stable? please confirm the steps :D
@pierro78, I just discovered that on teh very latest brunch version (chromeos Version 121.0.6167.212 updated the normal way, and Brunch r121 stable 20240224), there is a fix in the brunch settings (actually 2) to run the script on bootup. One for card 0, one for card 1. Works great on 2 different Geobooks-140. One is permanently connected to HDMI (so the internal sound is card 1), one is standalone (internal sound card 0). Both work fine with the respective script - yeah. Beith with Kernel 6.6, but also might work with 6.1 as before.
thanks so much for the tip !! ... just did the upgrade to Brunch r121 stable 20240224 from the pwa, selected essx8336 on card0 in the settings and it s working great on my Kuu Yobook M !!! ... thanks again !! and thanks also for the awesome work by sebanc !
@pierro78, I just discovered that on teh very latest brunch version (chromeos Version 121.0.6167.212 updated the normal way, and Brunch r121 stable 20240224), there is a fix in the brunch settings (actually 2) to run the script on bootup. One for card 0, one for card 1. Works great on 2 different Geobooks-140. One is permanently connected to HDMI (so the internal sound is card 1), one is standalone (internal sound card 0). Both work fine with the respective script - yeah. Beith with Kernel 6.6, but also might work with 6.1 as before. I haven't yet tested whether you can run both scripts, in case the internal sound changes from being card 0 to card 1 if HDMI is connected on startup. Will do that right away. But in the meantime, THANKS @sebanc and every one else involved for fixing this. Edit: Just tested running both scripts on both machines, didn't work.
Hi, Sorry, Dont understand, How do I get the geobook-140 soundcards to work properly with latest brunch r121 stable? please confirm the steps :D
@ameeno : at boot time choose "brunch settings", then in second settings screen choose "essx8336 on card1"
@ameeno, you might also need to select "card 0" instead if card1 does not work. I have 2 Geobooks-140, and they behave differently. Might have something to to with the fact that I broke the screen on one of them, and use it permanently on a HDMI display now.
Important: You need to use a kernel >6. 6.1 should work, but I'm using 6.6.