search

sebanc / brunch

Boot ChromeOS on x86_64 PC - Supports Intel CPU/GPU from 8th gen or AMD Ryzen
GNU General Public License v3.0
3.71k stars 393 forks source link

Pixelbook (Eve) No sound or brightness control w/either Eve or Rammus base #346

Closed ericksontx closed 3 years ago

ericksontx commented 4 years ago

Have used Brunch wonderfully on other machines but there are two major showstopper issues with Google Pixelbook 2017 / Eve.

These are consistent on multiple Eve machines, using either Rammus or Eve base recovery images, v80-v83 images and matching 80-83 Brunch stable scripts.

  1. no sound. Sound is absent, and volume slider has no effect.

  2. screen brightness control is broken: It is either completely on or completely off, slider and hotkeys have no effect (keyboard mapping for the hotkey controls is also a mismatch, but that is a different, minor issue). Essentially this screen brightness is 100% all the time, when trying to slide to lowest brightness, the screen turns off. Adjusting up from lowest brightness results in the screen being 100% brightness again. Battery life killer.

Thanks

WindowsXP95 commented 4 years ago

You may need to enable some framework options

ericksontx commented 4 years ago

You may need to enable some framework options

Thanks , I am unfamiliar so how would I go about enabling them, and finding the correct ones? Thanks

sebanc commented 4 years ago

Well, let's try to fix brunch issues with pixelbook: 1) Try to download and copy the firmware available below in /lib/firmware. https://github.com/EmbeddedAndroid/linux-eve/tree/master/lib/firmware 2) add "i915.enable_dpcd_backlight=1 module_blacklist=snd_hda_intel" to the kernel command line 3) reboot and see if there is any change for audio and brightness

ericksontx commented 4 years ago

Well, let's try to fix brunch issues with pixelbook:

  1. Try to download and copy the firmware available below in /lib/firmware. https://github.com/EmbeddedAndroid/linux-eve/tree/master/lib/firmware
  2. add "i915.enable_dpcd_backlight=1 module_blacklist=snd_hda_intel" to the kernel command line
  3. reboot and see if there is any change for audio and brightness

Thanks for the tips, however I tried these, currently have that file in my /lib/firmware directory and also added that to the kernel line in grub, and no effect. Still no audio or brightness control unfortunately.

Since I am using Eve and not a generic x86 machine- what if I copied the files from /lib/firmware from the regular Eve install, to the Brunched version's /lib/firmware directory? Technically only the Eve-relevant firmware files need to be in there, I'm guessing?

sebanc commented 4 years ago

Could you attach a dmesg to this issue ? (run "dmesg > ~/Downloads/dmesg.txt" in crosh shell and attach dmesg.txt from you downloads folder)

ericksontx commented 4 years ago

dmesg.txt dmesg.txt

Could you attach a dmesg to this issue ? (run "dmesg > ~/Downloads/dmesg.txt" in crosh shell and attach dmesg.txt from you downloads folder)

sebanc commented 4 years ago

The "i915.enable_dpcd_backlight=1 module_blacklist=snd_hda_intel" are not enabled in the dmesg you sent. Have you added those to your linux dual boot grub config ? Also, did you run "sudo update-grub" afterwards ?

ericksontx commented 4 years ago

Ok sorry I had changed things but wasnt able to isolate instance/ use of grub with all of the dual config experimentation.

So now using cleaned HDD with no windows,and booting only off of Brunch USB, and making edits to that grub. No other chrome installs or other OS's on hard drive.

Attaching new dmesg. Not sure if I'm adding those modifiers to the right place in the kernel command line? But they are now appearing in that line. Also added dfw_sst.bin to bin/firmware/

seems to be no changes in issues with backlight control and audio dmesg.txt

sebanc commented 4 years ago

For sound, it looks better, could you try run the below command in crosh shell and reboot: "sudo ln -s dsp_fw_kbl_v3420.bin /lib/firmware/intel/dsp_fw_kbl.bin"

If sound does not work, could you post a new dmesg ?

For backlight, it did not seem to help, I will try to see what the issue could be.

ericksontx commented 4 years ago

For sound, it looks better, could you try run the below command in crosh shell and reboot: "sudo ln -s dsp_fw_kbl_v3420.bin /lib/firmware/intel/dsp_fw_kbl.bin"

If sound does not work, could you post a new dmesg ?

For backlight, it did not seem to help, I will try to see what the issue could be.

Hi - I ran that in shell, and rebooted. On reboot, when I logged in, I went to check volume, the speaker logo was active and at least for the single volume key I was able to press, I saw the volume slider move - the speaker logo and the volume movement were both improvements over before, where there was neither.

However before I could check if there was actually sound output, there was an immediate reboot. This was only about 8sec after login. Subsequent reboots were the same, even if I did Guest. Whether I messed with volume or not, Chrome would reboot seconds later. I can no longer get to crosh shell fast enough before reboot to save dmesg.

Is there a way to extract it anyway?

sebanc commented 4 years ago

Press CTRL+ALT+F2 when you see the login screen, then login as "root" and type rm /lib/firmware/intel/dsp_fw_kbl.bin.

The firmware we used are probably not the right ones, I will try to new ones from the eve recovery image directly.

ericksontx commented 4 years ago

Ok update. Started with a fresh Brunch drive - with the additions and edits you posted, no crashes or reboot this time, and consistent.

Volume slider works as does mute button, in terms of on screen functionality, but still no sound at all.

Trying to attach but GitHub keeps giving a failure message and won't let me attach. Will post log below.

(edited out)

sebanc commented 4 years ago

Could you try copying the content of the below archive to /lib/firmware ? eve_firmware.zip

sebanc commented 4 years ago

and also copy the content of the below one to /usr/share/alsa/ucm/ eve_ucm.zip

ericksontx commented 4 years ago

and also copy the content of the below one to /usr/share/alsa/ucm/ eve_ucm.zip

Ok I copied the files and directories of the two zips above, into the destination directories.

unfortunately audio went back to original state as regular Rammus base+Eve Brunch boot - speaker logo on volume control is inactive/"not complete", mute function works, volume keys have no effect on slider, and no sound output.

dmesg attached. dmesg.txt

sebanc commented 4 years ago

Thanks, indeed a new firmware appeared in the log, could you copy it to /lib/firmware ? dsp_lib_dsm_core_spt_release.zip

sebanc commented 4 years ago

Alternatively, you can download the latest testing release below (after validating the github email invite): https://github.com/sebanc/brunch-testing/releases

And boot with "options=eve" added to the kernel command line.

ericksontx commented 4 years ago

Thanks, indeed a new firmware appeared in the log, could you copy it to /lib/firmware ? dsp_lib_dsm_core_spt_release.zip

Unfortunately I get reboots after adding this, I cannot even get to login screen, I get kicked to UEFI shell. Is it supposed to be in lib/firmware or a subdir within perhaps?

sebanc commented 4 years ago

Could you try the test build just to confirm if it is the same ?

ericksontx commented 4 years ago

Could you try the test build just to confirm if it is the same ?

Ok tried test build with Rammus 83 on Eve. Initial boot was normal and fine except for backlight control and audio of course. Added the Eve option to kernel command line then rebooted.

Seems same result, reboot shortly after Chrome logo splash screen. Login screen is there for a few seconds and then it reboots. Not enough time to get to Crosh to capture dmesg.

sebanc commented 4 years ago

Ok so copying the original eve firmwares do not work... maybe there are specific kernel patches in eve kernel or it could be because eve kernel is version 4.4 if I am not mistaken.

I will try to find resources on how eve sound works in linux distros.

By any chance, is backlight control working in the new release ?

sebanc commented 4 years ago

Just found out, there is no audio support for kabylake chromebooks in linux even from galliumos. So this one is going to be diificult....

ericksontx commented 4 years ago

Ok so copying the original eve firmwares do not work... maybe there are specific kernel patches in eve kernel or it could be because eve kernel is version 4.4 if I am not mistaken.

I will try to find resources on how eve sound works in linux distros.

By any chance, is backlight control working in the new release ?

No difference in backlight during the brief time I had to try backlight controls before it would reboot.

Also FYI - on the testing release there are definite improvements on DisplayLink compatibility, I tested it with Samus 83 and Stumpy.

Before, connecting a monitor to an attached DisplayLink adapter caused an automatic reboot. Now, works perfectly. Tried with two different model older HP DisplayLink adapters, both work great.

Crescendo-BLYAT commented 4 years ago

offtopic: why would one use brunch on legit supported Chromebook? Eve is still supported officially, right?

Resurrection2981 commented 4 years ago

offtopic: why would one use brunch on legit supported Chromebook? Eve is still supported officially, right?

Dual boot Windows & Chrome OS.

ericksontx commented 3 years ago

Closed.

Brightness control was fixed in regular brunch releases.

Sound still has issues but can be worked around by using legacy kernel as shown in this thread.

https://github.com/sebanc/brunch/issues/779