New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Internal audio does not work on CYAN #317

Closed
reynhout opened this Issue Jan 18, 2017 · 106 comments

Comments

Projects
None yet
@reynhout
Member

reynhout commented Jan 18, 2017

CYAN is the only Braswell with the Maxim MAX98090 audio chip.

Current kernel builds (4.9.4-galliumos) include drivers for this chip, but they are not loading properly and internal audio is not working.

Temporary workarounds: Bluetooth or USB audio.

@reynhout reynhout referenced this issue Jan 18, 2017

Closed

Braswell Platform Validation #270

15 of 15 tasks complete
@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Jan 21, 2017

What's the priority for this issue looking like?

ghost commented Jan 21, 2017

What's the priority for this issue looking like?

@reynhout

This comment has been minimized.

Show comment
Hide comment
@reynhout

reynhout Feb 9, 2017

Member

kernel.org thread here: https://bugzilla.kernel.org/show_bug.cgi?id=151521

Kernel 4.9.4 with the patch in c14 (but without the @plbossart patch for rt5450) yields some new log messages: https://paste.debian.net/913490

Member

reynhout commented Feb 9, 2017

kernel.org thread here: https://bugzilla.kernel.org/show_bug.cgi?id=151521

Kernel 4.9.4 with the patch in c14 (but without the @plbossart patch for rt5450) yields some new log messages: https://paste.debian.net/913490

@reynhout

This comment has been minimized.

Show comment
Hide comment
@reynhout

reynhout Feb 9, 2017

Member

Init of MAX98090 gets further along with @mildred's patch, but now we hit a null pointer deref in the jack configuration. Perhaps there are more bits to pull in from the ChromiumOS tree?

In case the debian pastebin copy expires:

[    0.000000] Linux version 4.9.4-galliumos-braswell (reynhout@galliumos) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #1 SMP PREEMPT galliumos1+wip3.cyan.2 Thu Feb 9 02:52:48 UTC 201
[    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.9.4-galliumos-braswell root=UUID=7c0f7ebd-5854-4517-a97f-9424ddb76850 ro nosplash noplymouth boot=local acpi_osi=Linux acpi_backlight=vendor add_efi_memmap intel_pstate=enable i915.modeset=1 tpm_tis.force=1 tpm_tis.interrupts=0 nmi_watchdog=panic,lapic elevator=noop noresume gpiolib.acpi_lookup_can_try_crs=1
[    4.731933] snd_hda_intel 0000:00:1b.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
[    4.732357] intel_sst_acpi 808622A8:00: LPE base: 0xd1000000 size:0x200000
[    4.732363] intel_sst_acpi 808622A8:00: IRAM base: 0xd10c0000
[    4.732420] intel_sst_acpi 808622A8:00: DRAM base: 0xd1100000
[    4.732429] intel_sst_acpi 808622A8:00: SHIM base: 0xd1140000
[    4.732436] intel_sst_acpi 808622A8:00: Mailbox base: 0xd1144000
[    4.732441] intel_sst_acpi 808622A8:00: DDR base: 0x20000000
[    4.737903] intel_sst_acpi 808622A8:00: Got drv data max stream 25
[    4.849061] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1b.0/sound/card1/input7
[    4.849214] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:1b.0/sound/card1/input8
[    4.849346] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:1b.0/sound/card1/input9
[    4.918101] SSE version of gcm_enc/dec engaged.
[    5.074758] intel_rapl: Found RAPL domain core
[    5.078629] max98090 i2c-193C9890:00: MAX98090 REVID=0x43
[    5.085279] BUG: unable to handle kernel NULL pointer dereference at 0000000000000028
[    5.087321] IP: [<ffffffffc0463d40>] snd_jack_set_key+0x30/0x80 [snd]
[    5.087324] PGD 0 
[    5.087327] Oops: 0000 [#1] PREEMPT SMP
[    5.087377] Modules linked in: intel_rapl intel_powerclamp coretemp kvm_intel snd_soc_sst_cht_bsw_max98090_ti(+) kvm joydev irqbypass arc4 crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw iwlmvm gf128mul glue_helper ablk_helper mac80211 cryptd snd_hda_codec_hdmi uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 snd_intel_sst_acpi snd_hda_intel videobuf2_core snd_intel_sst_core iwlwifi snd_hda_codec videodev btusb snd_soc_sst_mfld_platform snd_soc_ts3a227e btrtl snd_soc_max98090 snd_soc_sst_match snd_hwdep media snd_soc_core btbcm snd_pcm_oss snd_hda_core btintel snd_compress snd_mixer_oss bluetooth cfg80211 snd_pcm_dmaengine snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer int3403_thermal int3400_thermal snd elan_i2c processor_thermal_device
[    5.087400]  int340x_thermal_zone acpi_thermal_rel chromeos_pstore lpc_ich intel_soc_dts_iosf shpchp soundcore elants_i2c mfd_core 8250_dw acpi_cpufreq mac_hid autofs4 dm_mirror dm_region_hash dm_log mmc_block i915 video i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm sdhci_acpi sdhci
[    5.087404] CPU: 2 PID: 324 Comm: systemd-udevd Not tainted 4.9.4-galliumos-braswell #1
[    5.087406] Hardware name: GOOGLE Cyan, BIOS          08/21/2016
[    5.087408] task: ffff8ab43708d940 task.stack: ffffad80c0cc0000
[    5.087417] RIP: 0010:[<ffffffffc0463d40>]  [<ffffffffc0463d40>] snd_jack_set_key+0x30/0x80 [snd]
[    5.087419] RSP: 0018:ffffad80c0cc3a10  EFLAGS: 00010282
[    5.087421] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 000000000000000e
[    5.087422] RDX: 00000000000000e2 RSI: 0000000000004000 RDI: 0000000000000000
[    5.087423] RBP: ffffad80c0cc3a30 R08: ffff8ab4399ea3f8 R09: 0000000000000000
[    5.087425] R10: 0000000000000022 R11: 000000000001cd10 R12: 0000000000004000
[    5.087426] R13: 0000000000000000 R14: ffff8ab436446a68 R15: ffff8ab4364469f0
[    5.087429] FS:  00007f8aac3568c0(0000) GS:ffff8ab43fd00000(0000) knlGS:0000000000000000
[    5.087430] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[    5.087432] CR2: 0000000000000028 CR3: 0000000177666000 CR4: 00000000001006e0
[    5.087433] Stack:
[    5.087439]  ffff8ab436446ad8 ffff8ab43947b858 ffff8ab439778318 ffff8ab436446ad8
[    5.087442]  ffffad80c0cc3a50 ffffffffc059110d ffff8ab436446a00 ffffffffc08820c0
[    5.087446]  ffffad80c0cc3a60 ffffffffc0880019 ffffad80c0cc3aa0 ffffffffc065fb51
[    5.087447] Call Trace:
[    5.087456]  [<ffffffffc059110d>] ts3a227e_enable_jack_detect+0x2d/0x80 [snd_soc_ts3a227e]
[    5.087463]  [<ffffffffc0880019>] cht_max98090_headset_init+0x19/0x20 [snd_soc_sst_cht_bsw_max98090_ti]
[    5.087491]  [<ffffffffc065fb51>] soc_probe_component+0x281/0x3c0 [snd_soc_core]
[    5.087506]  [<ffffffffc06620f7>] snd_soc_register_card+0x737/0x1020 [snd_soc_core]
[    5.087521]  [<ffffffffc0670281>] devm_snd_soc_register_card+0x41/0x80 [snd_soc_core]
[    5.087530]  [<ffffffffc08802ec>] snd_cht_mc_probe+0x6c/0xc8 [snd_soc_sst_cht_bsw_max98090_ti]
[    5.087539]  [<ffffffff864fd93b>] platform_drv_probe+0x3b/0xa0
[    5.087542]  [<ffffffff864fb794>] driver_probe_device+0x224/0x430
[    5.087546]  [<ffffffff864fba7f>] __driver_attach+0xdf/0xf0
[    5.087549]  [<ffffffff864fb9a0>] ? driver_probe_device+0x430/0x430
[    5.087552]  [<ffffffff864f9444>] bus_for_each_dev+0x64/0xa0
[    5.087555]  [<ffffffff864faefe>] driver_attach+0x1e/0x20
[    5.087557]  [<ffffffff864fa9fd>] bus_add_driver+0x1fd/0x270
[    5.087560]  [<ffffffffc01da000>] ? 0xffffffffc01da000
[    5.087563]  [<ffffffff864fc400>] driver_register+0x60/0xe0
[    5.087566]  [<ffffffff864fd8b6>] __platform_driver_register+0x36/0x40
[    5.087570]  [<ffffffffc01da017>] snd_cht_mc_driver_init+0x17/0x1000 [snd_soc_sst_cht_bsw_max98090_ti]
[    5.087575]  [<ffffffff86002190>] do_one_initcall+0x50/0x180
[    5.087582]  [<ffffffff86195950>] do_init_module+0x5f/0x1f6
[    5.087587]  [<ffffffff8610ced7>] load_module+0x2647/0x2a20
[    5.087590]  [<ffffffff86109620>] ? __symbol_put+0x70/0x70
[    5.087598]  [<ffffffff8610d4cc>] SYSC_finit_module+0xbc/0xf0
[    5.087603]  [<ffffffff8610d51e>] SyS_finit_module+0xe/0x10
[    5.087608]  [<ffffffff867629fb>] entry_SYSCALL_64_fastpath+0x1e/0xad
[    5.087656] Code: 55 b9 ff ff ff ff 89 c8 48 89 e5 41 55 41 54 53 41 89 f4 be 00 40 00 00 41 0f bd cc 0f bd c6 29 c8 48 83 ec 08 48 89 fb 41 89 c5 <8b> 47 28 85 c0 75 25 85 d2 74 3a 41 83 fd 05 77 34 49 63 c5 44 
[    5.087663] RIP  [<ffffffffc0463d40>] snd_jack_set_key+0x30/0x80 [snd]
[    5.087665]  RSP <ffffad80c0cc3a10>
[    5.087666] CR2: 0000000000000028
[    5.087868] ---[ end trace c107d479510d8b9c ]---
Member

reynhout commented Feb 9, 2017

Init of MAX98090 gets further along with @mildred's patch, but now we hit a null pointer deref in the jack configuration. Perhaps there are more bits to pull in from the ChromiumOS tree?

In case the debian pastebin copy expires:

[    0.000000] Linux version 4.9.4-galliumos-braswell (reynhout@galliumos) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #1 SMP PREEMPT galliumos1+wip3.cyan.2 Thu Feb 9 02:52:48 UTC 201
[    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.9.4-galliumos-braswell root=UUID=7c0f7ebd-5854-4517-a97f-9424ddb76850 ro nosplash noplymouth boot=local acpi_osi=Linux acpi_backlight=vendor add_efi_memmap intel_pstate=enable i915.modeset=1 tpm_tis.force=1 tpm_tis.interrupts=0 nmi_watchdog=panic,lapic elevator=noop noresume gpiolib.acpi_lookup_can_try_crs=1
[    4.731933] snd_hda_intel 0000:00:1b.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
[    4.732357] intel_sst_acpi 808622A8:00: LPE base: 0xd1000000 size:0x200000
[    4.732363] intel_sst_acpi 808622A8:00: IRAM base: 0xd10c0000
[    4.732420] intel_sst_acpi 808622A8:00: DRAM base: 0xd1100000
[    4.732429] intel_sst_acpi 808622A8:00: SHIM base: 0xd1140000
[    4.732436] intel_sst_acpi 808622A8:00: Mailbox base: 0xd1144000
[    4.732441] intel_sst_acpi 808622A8:00: DDR base: 0x20000000
[    4.737903] intel_sst_acpi 808622A8:00: Got drv data max stream 25
[    4.849061] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1b.0/sound/card1/input7
[    4.849214] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:1b.0/sound/card1/input8
[    4.849346] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:1b.0/sound/card1/input9
[    4.918101] SSE version of gcm_enc/dec engaged.
[    5.074758] intel_rapl: Found RAPL domain core
[    5.078629] max98090 i2c-193C9890:00: MAX98090 REVID=0x43
[    5.085279] BUG: unable to handle kernel NULL pointer dereference at 0000000000000028
[    5.087321] IP: [<ffffffffc0463d40>] snd_jack_set_key+0x30/0x80 [snd]
[    5.087324] PGD 0 
[    5.087327] Oops: 0000 [#1] PREEMPT SMP
[    5.087377] Modules linked in: intel_rapl intel_powerclamp coretemp kvm_intel snd_soc_sst_cht_bsw_max98090_ti(+) kvm joydev irqbypass arc4 crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw iwlmvm gf128mul glue_helper ablk_helper mac80211 cryptd snd_hda_codec_hdmi uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 snd_intel_sst_acpi snd_hda_intel videobuf2_core snd_intel_sst_core iwlwifi snd_hda_codec videodev btusb snd_soc_sst_mfld_platform snd_soc_ts3a227e btrtl snd_soc_max98090 snd_soc_sst_match snd_hwdep media snd_soc_core btbcm snd_pcm_oss snd_hda_core btintel snd_compress snd_mixer_oss bluetooth cfg80211 snd_pcm_dmaengine snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer int3403_thermal int3400_thermal snd elan_i2c processor_thermal_device
[    5.087400]  int340x_thermal_zone acpi_thermal_rel chromeos_pstore lpc_ich intel_soc_dts_iosf shpchp soundcore elants_i2c mfd_core 8250_dw acpi_cpufreq mac_hid autofs4 dm_mirror dm_region_hash dm_log mmc_block i915 video i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm sdhci_acpi sdhci
[    5.087404] CPU: 2 PID: 324 Comm: systemd-udevd Not tainted 4.9.4-galliumos-braswell #1
[    5.087406] Hardware name: GOOGLE Cyan, BIOS          08/21/2016
[    5.087408] task: ffff8ab43708d940 task.stack: ffffad80c0cc0000
[    5.087417] RIP: 0010:[<ffffffffc0463d40>]  [<ffffffffc0463d40>] snd_jack_set_key+0x30/0x80 [snd]
[    5.087419] RSP: 0018:ffffad80c0cc3a10  EFLAGS: 00010282
[    5.087421] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 000000000000000e
[    5.087422] RDX: 00000000000000e2 RSI: 0000000000004000 RDI: 0000000000000000
[    5.087423] RBP: ffffad80c0cc3a30 R08: ffff8ab4399ea3f8 R09: 0000000000000000
[    5.087425] R10: 0000000000000022 R11: 000000000001cd10 R12: 0000000000004000
[    5.087426] R13: 0000000000000000 R14: ffff8ab436446a68 R15: ffff8ab4364469f0
[    5.087429] FS:  00007f8aac3568c0(0000) GS:ffff8ab43fd00000(0000) knlGS:0000000000000000
[    5.087430] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[    5.087432] CR2: 0000000000000028 CR3: 0000000177666000 CR4: 00000000001006e0
[    5.087433] Stack:
[    5.087439]  ffff8ab436446ad8 ffff8ab43947b858 ffff8ab439778318 ffff8ab436446ad8
[    5.087442]  ffffad80c0cc3a50 ffffffffc059110d ffff8ab436446a00 ffffffffc08820c0
[    5.087446]  ffffad80c0cc3a60 ffffffffc0880019 ffffad80c0cc3aa0 ffffffffc065fb51
[    5.087447] Call Trace:
[    5.087456]  [<ffffffffc059110d>] ts3a227e_enable_jack_detect+0x2d/0x80 [snd_soc_ts3a227e]
[    5.087463]  [<ffffffffc0880019>] cht_max98090_headset_init+0x19/0x20 [snd_soc_sst_cht_bsw_max98090_ti]
[    5.087491]  [<ffffffffc065fb51>] soc_probe_component+0x281/0x3c0 [snd_soc_core]
[    5.087506]  [<ffffffffc06620f7>] snd_soc_register_card+0x737/0x1020 [snd_soc_core]
[    5.087521]  [<ffffffffc0670281>] devm_snd_soc_register_card+0x41/0x80 [snd_soc_core]
[    5.087530]  [<ffffffffc08802ec>] snd_cht_mc_probe+0x6c/0xc8 [snd_soc_sst_cht_bsw_max98090_ti]
[    5.087539]  [<ffffffff864fd93b>] platform_drv_probe+0x3b/0xa0
[    5.087542]  [<ffffffff864fb794>] driver_probe_device+0x224/0x430
[    5.087546]  [<ffffffff864fba7f>] __driver_attach+0xdf/0xf0
[    5.087549]  [<ffffffff864fb9a0>] ? driver_probe_device+0x430/0x430
[    5.087552]  [<ffffffff864f9444>] bus_for_each_dev+0x64/0xa0
[    5.087555]  [<ffffffff864faefe>] driver_attach+0x1e/0x20
[    5.087557]  [<ffffffff864fa9fd>] bus_add_driver+0x1fd/0x270
[    5.087560]  [<ffffffffc01da000>] ? 0xffffffffc01da000
[    5.087563]  [<ffffffff864fc400>] driver_register+0x60/0xe0
[    5.087566]  [<ffffffff864fd8b6>] __platform_driver_register+0x36/0x40
[    5.087570]  [<ffffffffc01da017>] snd_cht_mc_driver_init+0x17/0x1000 [snd_soc_sst_cht_bsw_max98090_ti]
[    5.087575]  [<ffffffff86002190>] do_one_initcall+0x50/0x180
[    5.087582]  [<ffffffff86195950>] do_init_module+0x5f/0x1f6
[    5.087587]  [<ffffffff8610ced7>] load_module+0x2647/0x2a20
[    5.087590]  [<ffffffff86109620>] ? __symbol_put+0x70/0x70
[    5.087598]  [<ffffffff8610d4cc>] SYSC_finit_module+0xbc/0xf0
[    5.087603]  [<ffffffff8610d51e>] SyS_finit_module+0xe/0x10
[    5.087608]  [<ffffffff867629fb>] entry_SYSCALL_64_fastpath+0x1e/0xad
[    5.087656] Code: 55 b9 ff ff ff ff 89 c8 48 89 e5 41 55 41 54 53 41 89 f4 be 00 40 00 00 41 0f bd cc 0f bd c6 29 c8 48 83 ec 08 48 89 fb 41 89 c5 <8b> 47 28 85 c0 75 25 85 d2 74 3a 41 83 fd 05 77 34 49 63 c5 44 
[    5.087663] RIP  [<ffffffffc0463d40>] snd_jack_set_key+0x30/0x80 [snd]
[    5.087665]  RSP <ffffad80c0cc3a10>
[    5.087666] CR2: 0000000000000028
[    5.087868] ---[ end trace c107d479510d8b9c ]---
@reynhout

This comment has been minimized.

Show comment
Hide comment
@reynhout

reynhout Feb 9, 2017

Member

Data sheet for the TS3A227E (Autonomous Audio Accessory Detection and Configuration Switch):

http://www.ti.com/lit/ds/symlink/ts3a227e.pdf

Member

reynhout commented Feb 9, 2017

Data sheet for the TS3A227E (Autonomous Audio Accessory Detection and Configuration Switch):

http://www.ti.com/lit/ds/symlink/ts3a227e.pdf

@anorom

This comment has been minimized.

Show comment
Hide comment
@anorom

anorom commented Feb 23, 2017

Are the new patches on https://bugzilla.kernel.org/show_bug.cgi?id=151521 helpful? Thanks

@reynhout

This comment has been minimized.

Show comment
Hide comment
@reynhout

reynhout Feb 23, 2017

Member

@anorom No, they're not working yet. I haven't had a chance to see if I can push things any further, but the patches as-is do not resolve the issue.

Member

reynhout commented Feb 23, 2017

@anorom No, they're not working yet. I haven't had a chance to see if I can push things any further, but the patches as-is do not resolve the issue.

@anorom

This comment has been minimized.

Show comment
Hide comment
@anorom

anorom Feb 24, 2017

It looked like the patches would not fix the issue but your testing and feedback seems to keep things moving. Appreciate your help.

anorom commented Feb 24, 2017

It looked like the patches would not fix the issue but your testing and feedback seems to keep things moving. Appreciate your help.

@chuckhacker

This comment has been minimized.

Show comment
Hide comment
@chuckhacker

chuckhacker Mar 29, 2017

Any updates?

chuckhacker commented Mar 29, 2017

Any updates?

@nkalupahana

This comment has been minimized.

Show comment
Hide comment
@nkalupahana

nkalupahana commented Apr 3, 2017

Anything?

@reynhout

This comment has been minimized.

Show comment
Hide comment
@reynhout

reynhout Apr 3, 2017

Member

@chuckhacker @nkalupahana When there is news, it will be posted here. You can subscribe to this ticket for email updates.

Member

reynhout commented Apr 3, 2017

@chuckhacker @nkalupahana When there is news, it will be posted here. You can subscribe to this ticket for email updates.

@gordonthegopher

This comment has been minimized.

Show comment
Hide comment
@gordonthegopher

gordonthegopher Apr 17, 2017

@reynhout Is this of any use?

https://aur.archlinux.org/packages/linux-max98090/

Apologies if not, I was just browsing the Arch AUR. I have no technical knowledge to help out and you may well know all this already.

Other sources:

https://bugs.archlinux.org/task/48936

https://wiki.archlinux.org/index.php/Chrome_OS_devices (Specifically Post Installation Configuration>Fixing audio>Baytrail based models)

gordonthegopher commented Apr 17, 2017

@reynhout Is this of any use?

https://aur.archlinux.org/packages/linux-max98090/

Apologies if not, I was just browsing the Arch AUR. I have no technical knowledge to help out and you may well know all this already.

Other sources:

https://bugs.archlinux.org/task/48936

https://wiki.archlinux.org/index.php/Chrome_OS_devices (Specifically Post Installation Configuration>Fixing audio>Baytrail based models)

@chuckhacker

This comment has been minimized.

Show comment
Hide comment
@chuckhacker

chuckhacker Apr 28, 2017

@reynhout Sounds good. Feel free to ping me so we can work out some sort of compensation agreement, if you're interested.

chuckhacker commented Apr 28, 2017

@reynhout Sounds good. Feel free to ping me so we can work out some sort of compensation agreement, if you're interested.

@wommy

This comment has been minimized.

Show comment
Hide comment
@wommy

wommy Jun 6, 2017

i would love to help with this in anyway i can

fixed gordonthegopher's link from above: https://wiki.archlinux.org/index.php/Chrome_OS_devices#Haswell_based_models

wommy commented Jun 6, 2017

i would love to help with this in anyway i can

fixed gordonthegopher's link from above: https://wiki.archlinux.org/index.php/Chrome_OS_devices#Haswell_based_models

@gluaxspeed

This comment has been minimized.

Show comment
Hide comment
@gluaxspeed

gluaxspeed Jul 26, 2017

Is there any update for this issue?

gluaxspeed commented Jul 26, 2017

Is there any update for this issue?

@electricduck

This comment has been minimized.

Show comment
Hide comment
@electricduck

electricduck Jul 31, 2017

@gluaxspeed This is a high priority issue, so if there's an update, we will know about it. Posting things like this isn't constructive: keep GitHub Issues clean :)

electricduck commented Jul 31, 2017

@gluaxspeed This is a high priority issue, so if there's an update, we will know about it. Posting things like this isn't constructive: keep GitHub Issues clean :)

@wommy

This comment has been minimized.

Show comment
Hide comment
@wommy

wommy Jul 31, 2017

would love to help in anyway I can

wommy commented Jul 31, 2017

would love to help in anyway I can

@Magnus445

This comment has been minimized.

Show comment
Hide comment
@Magnus445

Magnus445 Aug 4, 2017

How's it going so far?

Magnus445 commented Aug 4, 2017

How's it going so far?

@jeffkub

This comment has been minimized.

Show comment
Hide comment
@jeffkub

jeffkub Aug 8, 2017

I've been digging into the audio issue on CYAN, and becoming convinced its due to missing initialization code that chromeos does in the depthcharge payload.

https://plus.google.com/u/0/+TimoJyrinki/posts/R1AqYCSPru8

Here is the board setup function in depthcharge

https://chromium.googlesource.com/chromiumos/platform/depthcharge/+/firmware-cyan-7287.57.B/src/board/cyan/board.c

I'm narrowing down specifically on the I2S interface (SSP2). The Linux driver doesn't seem to ioremap or touch these control registers.

https://chromium.googlesource.com/chromiumos/platform/depthcharge/+/firmware-cyan-7287.57.B/src/drivers/bus/i2s/braswell/braswell.c

My theory is that for the MAX98090 codec on Braswell, the SSP2 interface needs to be initialized. I'll try to modify the driver to do the initialization... My experience is with ARM platforms, not Intel, so I'll see how far I can get.

jeffkub commented Aug 8, 2017

I've been digging into the audio issue on CYAN, and becoming convinced its due to missing initialization code that chromeos does in the depthcharge payload.

https://plus.google.com/u/0/+TimoJyrinki/posts/R1AqYCSPru8

Here is the board setup function in depthcharge

https://chromium.googlesource.com/chromiumos/platform/depthcharge/+/firmware-cyan-7287.57.B/src/board/cyan/board.c

I'm narrowing down specifically on the I2S interface (SSP2). The Linux driver doesn't seem to ioremap or touch these control registers.

https://chromium.googlesource.com/chromiumos/platform/depthcharge/+/firmware-cyan-7287.57.B/src/drivers/bus/i2s/braswell/braswell.c

My theory is that for the MAX98090 codec on Braswell, the SSP2 interface needs to be initialized. I'll try to modify the driver to do the initialization... My experience is with ARM platforms, not Intel, so I'll see how far I can get.

@plbossart

This comment has been minimized.

Show comment
Hide comment
@plbossart

plbossart Aug 8, 2017

The ACPI-related code does all the initialization of I2C (and the interaction with the maxim codec works fine), the SSP is configured by the audio firmware. I suggest you don't waste too much time on this. The only assumption which was made is that the clock is managed by the BIOS/Coreboot, if this was not correct then this would explain why there is no sound.
Ideally we'd need to figure out how to enable a loopback inside of the maxim codec to see if the SSP connection works. I haven't had time to look into this but that's how we debugged other platforms.

  1. prove that the digital audio transfers work across the SSP link with a loopback
  2. do an analog loopback from mic to speakers to prove than the audio subsystem is not blown
  3. try digital to analog.

plbossart commented Aug 8, 2017

The ACPI-related code does all the initialization of I2C (and the interaction with the maxim codec works fine), the SSP is configured by the audio firmware. I suggest you don't waste too much time on this. The only assumption which was made is that the clock is managed by the BIOS/Coreboot, if this was not correct then this would explain why there is no sound.
Ideally we'd need to figure out how to enable a loopback inside of the maxim codec to see if the SSP connection works. I haven't had time to look into this but that's how we debugged other platforms.

  1. prove that the digital audio transfers work across the SSP link with a loopback
  2. do an analog loopback from mic to speakers to prove than the audio subsystem is not blown
  3. try digital to analog.
@jeffkub

This comment has been minimized.

Show comment
Hide comment
@jeffkub

jeffkub Aug 9, 2017

The MAX98090 driver appears to have the loopback bit LBEN already supported. My understanding of the driver and ALSA subsystem is that I can set this bit with the following commands.

amixer -c2 set 'LBENL Mux' 'Loopback'
amixer -c2 set 'LBENR Mux' 'Loopback'

However, when I play some audio, I'm seeing activity in pulse audio on the output channel but not the input channel. If the loopback was working, I was expecting to see activity on the input channel. I may be missing something...

I also added some code to print the SSP2 registers in the intel-sst-acpi driver

[   10.309277] intel_sst_acpi 808622A8:00: LPE base: 0xd1000000 size:0x200000
[   10.309279] intel_sst_acpi 808622A8:00: IRAM base: 0xd10c0000
[   10.309299] intel_sst_acpi 808622A8:00: DRAM base: 0xd1100000
[   10.309305] intel_sst_acpi 808622A8:00: SSP2 base: 0xd10a2000
[   10.309311] intel_sst_acpi 808622A8:00: SSCR1: 0x43000000
[   10.309314] intel_sst_acpi 808622A8:00: SSCR2: 0x800
[   10.309318] intel_sst_acpi 808622A8:00: SSCR3: 0x2c604
[   10.309321] intel_sst_acpi 808622A8:00: SSCR4: 0x0
[   10.309324] intel_sst_acpi 808622A8:00: SSCR5: 0x0
[   10.309328] intel_sst_acpi 808622A8:00: SSPSP: 0x0
[   10.309331] intel_sst_acpi 808622A8:00: SSTSA: 0x0
[   10.309334] intel_sst_acpi 808622A8:00: SSRSA: 0x0
[   10.309337] intel_sst_acpi 808622A8:00: SSSR: 0xf004
[   10.309341] intel_sst_acpi 808622A8:00: SSCR0: 0x0
[   10.309344] intel_sst_acpi 808622A8:00: SSTO: 0x0
[   10.309345] intel_sst_acpi 808622A8:00: SHIM base: 0xd1140000
[   10.309350] intel_sst_acpi 808622A8:00: Mailbox base: 0xd1144000
[   10.309355] intel_sst_acpi 808622A8:00: DDR base: 0x20000000

I can't find any documentation on the LPE or the SSP peripherals on the Braswell chip. However, from looking at the depthcharge code, bit 7 of the SSCR0 register is the SSP enable bit, which is read as 0. Though, it may be that this is early in the driver init before the audio firmware sets up the SSP2...

Update: After receiving the firmware init message, I'm seeing the regs change. It looks like the audio firmware is setting up the SSP2

[   55.291762] intel_sst_acpi 808622A8:00: SSCR1: 0x41000003
[   55.291768] intel_sst_acpi 808622A8:00: SSCR2: 0x2801
[   55.291772] intel_sst_acpi 808622A8:00: SSCR3: 0x3c61f
[   55.291776] intel_sst_acpi 808622A8:00: SSCR4: 0x1400
[   55.291779] intel_sst_acpi 808622A8:00: SSCR5: 0x26
[   55.291783] intel_sst_acpi 808622A8:00: SSPSP: 0x140084
[   55.291787] intel_sst_acpi 808622A8:00: SSTSA: 0x0
[   55.291790] intel_sst_acpi 808622A8:00: SSRSA: 0x0
[   55.291794] intel_sst_acpi 808622A8:00: SSSR: 0xf004
[   55.291797] intel_sst_acpi 808622A8:00: SSCR0: 0xc0093f
[   55.291801] intel_sst_acpi 808622A8:00: SSTO: 0x0

jeffkub commented Aug 9, 2017

The MAX98090 driver appears to have the loopback bit LBEN already supported. My understanding of the driver and ALSA subsystem is that I can set this bit with the following commands.

amixer -c2 set 'LBENL Mux' 'Loopback'
amixer -c2 set 'LBENR Mux' 'Loopback'

However, when I play some audio, I'm seeing activity in pulse audio on the output channel but not the input channel. If the loopback was working, I was expecting to see activity on the input channel. I may be missing something...

I also added some code to print the SSP2 registers in the intel-sst-acpi driver

[   10.309277] intel_sst_acpi 808622A8:00: LPE base: 0xd1000000 size:0x200000
[   10.309279] intel_sst_acpi 808622A8:00: IRAM base: 0xd10c0000
[   10.309299] intel_sst_acpi 808622A8:00: DRAM base: 0xd1100000
[   10.309305] intel_sst_acpi 808622A8:00: SSP2 base: 0xd10a2000
[   10.309311] intel_sst_acpi 808622A8:00: SSCR1: 0x43000000
[   10.309314] intel_sst_acpi 808622A8:00: SSCR2: 0x800
[   10.309318] intel_sst_acpi 808622A8:00: SSCR3: 0x2c604
[   10.309321] intel_sst_acpi 808622A8:00: SSCR4: 0x0
[   10.309324] intel_sst_acpi 808622A8:00: SSCR5: 0x0
[   10.309328] intel_sst_acpi 808622A8:00: SSPSP: 0x0
[   10.309331] intel_sst_acpi 808622A8:00: SSTSA: 0x0
[   10.309334] intel_sst_acpi 808622A8:00: SSRSA: 0x0
[   10.309337] intel_sst_acpi 808622A8:00: SSSR: 0xf004
[   10.309341] intel_sst_acpi 808622A8:00: SSCR0: 0x0
[   10.309344] intel_sst_acpi 808622A8:00: SSTO: 0x0
[   10.309345] intel_sst_acpi 808622A8:00: SHIM base: 0xd1140000
[   10.309350] intel_sst_acpi 808622A8:00: Mailbox base: 0xd1144000
[   10.309355] intel_sst_acpi 808622A8:00: DDR base: 0x20000000

I can't find any documentation on the LPE or the SSP peripherals on the Braswell chip. However, from looking at the depthcharge code, bit 7 of the SSCR0 register is the SSP enable bit, which is read as 0. Though, it may be that this is early in the driver init before the audio firmware sets up the SSP2...

Update: After receiving the firmware init message, I'm seeing the regs change. It looks like the audio firmware is setting up the SSP2

[   55.291762] intel_sst_acpi 808622A8:00: SSCR1: 0x41000003
[   55.291768] intel_sst_acpi 808622A8:00: SSCR2: 0x2801
[   55.291772] intel_sst_acpi 808622A8:00: SSCR3: 0x3c61f
[   55.291776] intel_sst_acpi 808622A8:00: SSCR4: 0x1400
[   55.291779] intel_sst_acpi 808622A8:00: SSCR5: 0x26
[   55.291783] intel_sst_acpi 808622A8:00: SSPSP: 0x140084
[   55.291787] intel_sst_acpi 808622A8:00: SSTSA: 0x0
[   55.291790] intel_sst_acpi 808622A8:00: SSRSA: 0x0
[   55.291794] intel_sst_acpi 808622A8:00: SSSR: 0xf004
[   55.291797] intel_sst_acpi 808622A8:00: SSCR0: 0xc0093f
[   55.291801] intel_sst_acpi 808622A8:00: SSTO: 0x0
@plbossart

This comment has been minimized.

Show comment
Hide comment
@plbossart

plbossart Aug 9, 2017

It could also be a recent bug that was discussed recently where settings up the clocks mucks with what the Coreboot firmware did. See https://www.spinics.net/lists/linux-clk/msg18650.html

plbossart commented Aug 9, 2017

It could also be a recent bug that was discussed recently where settings up the clocks mucks with what the Coreboot firmware did. See https://www.spinics.net/lists/linux-clk/msg18650.html

@jeffkub

This comment has been minimized.

Show comment
Hide comment
@jeffkub

jeffkub Aug 15, 2017

Great news! I was able to get audio output through the speakers by mucking around with the alsamixer settings. It appears to have been a configuration issue.

I'll try to figure out what settings I changed and update here.

jeffkub commented Aug 15, 2017

Great news! I was able to get audio output through the speakers by mucking around with the alsamixer settings. It appears to have been a configuration issue.

I'll try to figure out what settings I changed and update here.

@jeffkub

This comment has been minimized.

Show comment
Hide comment
@jeffkub

jeffkub Aug 16, 2017

I have the speakers, headphone jack output, and built-in microphone working. The only bit not working yet is the headphone jack mic.

I modified the galliumos 4.12.0 kernel with the following patch, based on the findings here https://bugzilla.kernel.org/show_bug.cgi?id=151521

cyan-audio-driver-fix.patch.txt

I also used the ucm configuration files from the chromeos repo

https://chromium.googlesource.com/chromiumos/third_party/adhd/+/master/ucm-config/cyan/chtmax98090

with some modifications, as shown in this patch

ucm-mod-to-enable-audio.patch.txt

and placed the files at /usr/share/alsa/ucm/chtmax98090/. I can then reboot my computer and the settings persist.

Glad to finally have working audio on my chromebook 😄

jeffkub commented Aug 16, 2017

I have the speakers, headphone jack output, and built-in microphone working. The only bit not working yet is the headphone jack mic.

I modified the galliumos 4.12.0 kernel with the following patch, based on the findings here https://bugzilla.kernel.org/show_bug.cgi?id=151521

cyan-audio-driver-fix.patch.txt

I also used the ucm configuration files from the chromeos repo

https://chromium.googlesource.com/chromiumos/third_party/adhd/+/master/ucm-config/cyan/chtmax98090

with some modifications, as shown in this patch

ucm-mod-to-enable-audio.patch.txt

and placed the files at /usr/share/alsa/ucm/chtmax98090/. I can then reboot my computer and the settings persist.

Glad to finally have working audio on my chromebook 😄

@ryanpcmcquen

This comment has been minimized.

Show comment
Hide comment
@ryanpcmcquen

ryanpcmcquen Aug 16, 2017

@jeffkub, does that mean audio will soon work with GalliumOS on CYAN?

ryanpcmcquen commented Aug 16, 2017

@jeffkub, does that mean audio will soon work with GalliumOS on CYAN?

@jeffkub

This comment has been minimized.

Show comment
Hide comment
@jeffkub

jeffkub Aug 16, 2017

@ryanpcmcquen I'm not an active developer on the GalliumOS project, so I can't say if and when these changes will make it to release. That will be up to the distro maintainers.

jeffkub commented Aug 16, 2017

@ryanpcmcquen I'm not an active developer on the GalliumOS project, so I can't say if and when these changes will make it to release. That will be up to the distro maintainers.

@ryanpcmcquen

This comment has been minimized.

Show comment
Hide comment
@ryanpcmcquen

ryanpcmcquen Oct 8, 2017

@reynhout have the new patches landed in Testing?

ryanpcmcquen commented Oct 8, 2017

@reynhout have the new patches landed in Testing?

@mildred

This comment has been minimized.

Show comment
Hide comment
@mildred

mildred Oct 11, 2017

I am using bluetooth audio on CYAN without problem since a long time, but for the rest I had a small USB sound card.

@superloach see my comment above on how to make it work, and you have to create the /usr/share/alsa/ucm/chtmax98090 directory and put chromium files to it. So yes, we are reusing part of the chromiumos audio setup. The only thing we can't reuse is the kernel patch. chromiumos is stuck to kernel 4.4 and on newer kernels, the audio driver does not work anymore. hence the kernel patch.

mildred commented Oct 11, 2017

I am using bluetooth audio on CYAN without problem since a long time, but for the rest I had a small USB sound card.

@superloach see my comment above on how to make it work, and you have to create the /usr/share/alsa/ucm/chtmax98090 directory and put chromium files to it. So yes, we are reusing part of the chromiumos audio setup. The only thing we can't reuse is the kernel patch. chromiumos is stuck to kernel 4.4 and on newer kernels, the audio driver does not work anymore. hence the kernel patch.

@superloach

This comment has been minimized.

Show comment
Hide comment
@superloach

superloach Oct 25, 2017

Okay, I'll see if I can do it.

superloach commented Oct 25, 2017

Okay, I'll see if I can do it.

@ryanpcmcquen

This comment has been minimized.

Show comment
Hide comment
@ryanpcmcquen

ryanpcmcquen Nov 5, 2017

This issue had some good momentum ... what happened?

ryanpcmcquen commented Nov 5, 2017

This issue had some good momentum ... what happened?

@superloach

This comment has been minimized.

Show comment
Hide comment
@superloach

superloach Nov 10, 2017

superloach commented Nov 10, 2017

@ryanpcmcquen

This comment has been minimized.

Show comment
Hide comment
@ryanpcmcquen

ryanpcmcquen Nov 10, 2017

I know the testing repo is good ... I was hoping it would be rolled into stable.

ryanpcmcquen commented Nov 10, 2017

I know the testing repo is good ... I was hoping it would be rolled into stable.

@BinxJinder

This comment has been minimized.

Show comment
Hide comment
@BinxJinder

BinxJinder Nov 12, 2017

So audio works now on the testing repo? Or must something else be done in order to get it to work?

BinxJinder commented Nov 12, 2017

So audio works now on the testing repo? Or must something else be done in order to get it to work?

@ryanpcmcquen

This comment has been minimized.

Show comment
Hide comment
@ryanpcmcquen

ryanpcmcquen Nov 12, 2017

@BinxJinder it worked for me. Hopefully it gets rolled into the stable repo soon.

ryanpcmcquen commented Nov 12, 2017

@BinxJinder it worked for me. Hopefully it gets rolled into the stable repo soon.

@BinxJinder

This comment has been minimized.

Show comment
Hide comment
@BinxJinder

BinxJinder Nov 12, 2017

@ryanpcmcquen thanks, I'll try it later tonight :)

BinxJinder commented Nov 12, 2017

@ryanpcmcquen thanks, I'll try it later tonight :)

@BinxJinder

This comment has been minimized.

Show comment
Hide comment
@BinxJinder

BinxJinder Nov 24, 2017

How log will this take to be rolled out to stable?

BinxJinder commented Nov 24, 2017

How log will this take to be rolled out to stable?

@superloach

This comment has been minimized.

Show comment
Hide comment
@superloach

superloach Dec 12, 2017

superloach commented Dec 12, 2017

@anorom

This comment has been minimized.

Show comment
Hide comment
@anorom

anorom Jan 9, 2018

Updated to the 4.14.12 kernel from the testing repo on CYAN. The speakers are still working but very quiet compared to what they were with 4.12. Are others seeing this same thing?

anorom commented Jan 9, 2018

Updated to the 4.14.12 kernel from the testing repo on CYAN. The speakers are still working but very quiet compared to what they were with 4.12. Are others seeing this same thing?

@mayjs

This comment has been minimized.

Show comment
Hide comment
@mayjs

mayjs Jan 10, 2018

@anorom I just found out I have the same issue since the last update on CYAN. The problem occurs on both internal audio and builtin headphone jack, but USB-Audio seems to work fine.

mayjs commented Jan 10, 2018

@anorom I just found out I have the same issue since the last update on CYAN. The problem occurs on both internal audio and builtin headphone jack, but USB-Audio seems to work fine.

@anorom

This comment has been minimized.

Show comment
Hide comment
@anorom

anorom Jan 10, 2018

Thanks for the feedback! I was able to increase the internal speaker volume in alsamixer. Initially alsamixer was giving the error 'no such file or directory', but after using alsamixer -c 2 was able to increase the volume. Used the command alsactl store to save the setting but it is not staying after a restart of galliumos.

anorom commented Jan 10, 2018

Thanks for the feedback! I was able to increase the internal speaker volume in alsamixer. Initially alsamixer was giving the error 'no such file or directory', but after using alsamixer -c 2 was able to increase the volume. Used the command alsactl store to save the setting but it is not staying after a restart of galliumos.

@mayjs

This comment has been minimized.

Show comment
Hide comment
@mayjs

mayjs Jan 17, 2018

@anorom Thanks for your tip, the workaround does it for me as well.
I think some application (pulseaudio maybe?) is resetting the volume on boot/login.
I've just added sh -c "sleep 5; amixer -c 2 set Speaker 100%" to my XFCE-autostart scripts and this seems to fix it on boot. If I omit the sleep 5, it won't work.

mayjs commented Jan 17, 2018

@anorom Thanks for your tip, the workaround does it for me as well.
I think some application (pulseaudio maybe?) is resetting the volume on boot/login.
I've just added sh -c "sleep 5; amixer -c 2 set Speaker 100%" to my XFCE-autostart scripts and this seems to fix it on boot. If I omit the sleep 5, it won't work.

@BinxJinder

This comment has been minimized.

Show comment
Hide comment
@BinxJinder

BinxJinder Mar 5, 2018

Hey, sorry to resurrect this thread but how's the current state of internal audio on CYAN? Has it been fixed?

BinxJinder commented Mar 5, 2018

Hey, sorry to resurrect this thread but how's the current state of internal audio on CYAN? Has it been fixed?

@superloach

This comment has been minimized.

Show comment
Hide comment
@superloach

superloach Mar 5, 2018

superloach commented Mar 5, 2018

@reynhout

This comment has been minimized.

Show comment
Hide comment
@reynhout

reynhout Mar 5, 2018

Member

@BinxJinder Yes, CYAN internal audio (playback) works well. Required kernel is in the testing repository, for reasons that do not affect CYAN (or any other Braswells).

sudo galliumos-repodist --enable testing
galliumos-update
reboot

And it should be all sorted.

Member

reynhout commented Mar 5, 2018

@BinxJinder Yes, CYAN internal audio (playback) works well. Required kernel is in the testing repository, for reasons that do not affect CYAN (or any other Braswells).

sudo galliumos-repodist --enable testing
galliumos-update
reboot

And it should be all sorted.

@Alderny

This comment has been minimized.

Show comment
Hide comment
@Alderny

Alderny Mar 10, 2018

Hello @BinxJinder, I'm new to this but have an Acer R11 Chromebook (CYAN) running Gallium OS and have the 'no sound' problem. If I run those 3 lines in a terminal, will it fix the problem ahead of the new kernel release? Thanks.

Alderny commented Mar 10, 2018

Hello @BinxJinder, I'm new to this but have an Acer R11 Chromebook (CYAN) running Gallium OS and have the 'no sound' problem. If I run those 3 lines in a terminal, will it fix the problem ahead of the new kernel release? Thanks.

@reynhout

This comment has been minimized.

Show comment
Hide comment
@reynhout

reynhout Mar 10, 2018

Member

@Alderny Yes. Those three lines install the appropriate kernel package.

Member

reynhout commented Mar 10, 2018

@Alderny Yes. Those three lines install the appropriate kernel package.

@Alderny

This comment has been minimized.

Show comment
Hide comment
@Alderny

Alderny Mar 10, 2018

@BinxJinder Thank you - fantastic service and quick reply! Sound now working.

Alderny commented Mar 10, 2018

@BinxJinder Thank you - fantastic service and quick reply! Sound now working.

@dayschmer

This comment has been minimized.

Show comment
Hide comment
@dayschmer

dayschmer Mar 19, 2018

I used the above-suggested lines

sudo galliumos-repodist --enable testing
galliumos-update
reboot

in order to get audio working on my CYAN, but after reboot Virtualbox (5.0.40, installed via Synaptic) nolonger worked, saying that I need to install virtualbox-dkms. I already had it, so I tried to reinstall it. Reinstall didn't work correctly, so I did "sudo dpkg-reconfigure virtualbox-dkms" This is what came:

`------------------------------

Deleting module version: 5.0.40
completely from the DKMS tree.


Done.
Loading new virtualbox-5.0.40 DKMS files...
Building only for 4.14.14-galliumos
Building initial module for 4.14.14-galliumos
Error! Bad return status for module build on kernel: 4.14.14-galliumos (x86_64)
Consult /var/lib/dkms/virtualbox/5.0.40/build/make.log for more information.
Job for virtualbox.service failed because the control process exited with error code. See "systemctl status virtualbox.service" and "journalctl -xe" for details.
invoke-rc.d: initscript virtualbox, action "restart" failed.
● virtualbox.service - LSB: VirtualBox Linux kernel module
Loaded: loaded (/etc/init.d/virtualbox; bad; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2018-03-19 17:23:30 CET; 15ms ago
Docs: man:systemd-sysv-generator(8)
Process: 5685 ExecStart=/etc/init.d/virtualbox start (code=exited, status=1/FAILURE)

Mar 19 17:23:30 chrx systemd[1]: Starting LSB: VirtualBox Linux kernel module...
Mar 19 17:23:30 chrx virtualbox[5685]: * Loading VirtualBox kernel modules...
Mar 19 17:23:30 chrx virtualbox[5685]: * No suitable module for running ke...nd
Mar 19 17:23:30 chrx virtualbox[5685]: ...fail!
Mar 19 17:23:30 chrx systemd[1]: virtualbox.service: Control process exited...=1
Mar 19 17:23:30 chrx systemd[1]: Failed to start LSB: VirtualBox Linux kern...e.
Mar 19 17:23:30 chrx systemd[1]: virtualbox.service: Unit entered failed state.
Mar 19 17:23:30 chrx systemd[1]: virtualbox.service: Failed with result 'ex...'.
Hint: Some lines were ellipsized, use -l to show in full.


This was in /var/lib/dkms/virtualbox/5.0.40/build/make.log
DKMS make.log for virtualbox-5.0.40 for kernel 4.14.14-galliumos (x86_64)
Mon 19 Mar 17:23:27 CET 2018
make: Entering directory '/usr/src/linux-headers-4.14.14-galliumos'
Makefile:942: *** "Cannot generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel". Stop.
make: Leaving directory '/usr/src/linux-headers-4.14.14-galliumos'

`

----------------

Afterward, I then disabled testing, hoping that it would revert to the old kernel, but it didn't.

Is there any easy way to undo all of this? One of the main reasons I switched from Crouton to Gallium was to be able to run VirtualBox easily.

dayschmer commented Mar 19, 2018

I used the above-suggested lines

sudo galliumos-repodist --enable testing
galliumos-update
reboot

in order to get audio working on my CYAN, but after reboot Virtualbox (5.0.40, installed via Synaptic) nolonger worked, saying that I need to install virtualbox-dkms. I already had it, so I tried to reinstall it. Reinstall didn't work correctly, so I did "sudo dpkg-reconfigure virtualbox-dkms" This is what came:

`------------------------------

Deleting module version: 5.0.40
completely from the DKMS tree.


Done.
Loading new virtualbox-5.0.40 DKMS files...
Building only for 4.14.14-galliumos
Building initial module for 4.14.14-galliumos
Error! Bad return status for module build on kernel: 4.14.14-galliumos (x86_64)
Consult /var/lib/dkms/virtualbox/5.0.40/build/make.log for more information.
Job for virtualbox.service failed because the control process exited with error code. See "systemctl status virtualbox.service" and "journalctl -xe" for details.
invoke-rc.d: initscript virtualbox, action "restart" failed.
● virtualbox.service - LSB: VirtualBox Linux kernel module
Loaded: loaded (/etc/init.d/virtualbox; bad; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2018-03-19 17:23:30 CET; 15ms ago
Docs: man:systemd-sysv-generator(8)
Process: 5685 ExecStart=/etc/init.d/virtualbox start (code=exited, status=1/FAILURE)

Mar 19 17:23:30 chrx systemd[1]: Starting LSB: VirtualBox Linux kernel module...
Mar 19 17:23:30 chrx virtualbox[5685]: * Loading VirtualBox kernel modules...
Mar 19 17:23:30 chrx virtualbox[5685]: * No suitable module for running ke...nd
Mar 19 17:23:30 chrx virtualbox[5685]: ...fail!
Mar 19 17:23:30 chrx systemd[1]: virtualbox.service: Control process exited...=1
Mar 19 17:23:30 chrx systemd[1]: Failed to start LSB: VirtualBox Linux kern...e.
Mar 19 17:23:30 chrx systemd[1]: virtualbox.service: Unit entered failed state.
Mar 19 17:23:30 chrx systemd[1]: virtualbox.service: Failed with result 'ex...'.
Hint: Some lines were ellipsized, use -l to show in full.


This was in /var/lib/dkms/virtualbox/5.0.40/build/make.log
DKMS make.log for virtualbox-5.0.40 for kernel 4.14.14-galliumos (x86_64)
Mon 19 Mar 17:23:27 CET 2018
make: Entering directory '/usr/src/linux-headers-4.14.14-galliumos'
Makefile:942: *** "Cannot generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel". Stop.
make: Leaving directory '/usr/src/linux-headers-4.14.14-galliumos'

`

----------------

Afterward, I then disabled testing, hoping that it would revert to the old kernel, but it didn't.

Is there any easy way to undo all of this? One of the main reasons I switched from Crouton to Gallium was to be able to run VirtualBox easily.

@Magnus445

This comment has been minimized.

Show comment
Hide comment
@Magnus445

Magnus445 Mar 19, 2018

Magnus445 commented Mar 19, 2018

@reynhout

This comment has been minimized.

Show comment
Hide comment
@reynhout

reynhout Mar 19, 2018

Member

@dayschmer Select your kernel version at boot time (hit Esc at the right time to get the GRUB menu, or configure GRUB to prefer a kernel version).

@Magnus445 Try installing ACPID: sudo apt install acpid. Headphones should already work, but jack detection does not, so you'd need to switch the output (audio "sink") manually in the audio applet. We have scripts for ACPID which should handle the jack detection. Tested on CYAN and TERRA. but hopefully functional on all Braswells. acpid should be included in the default install, but currently is not.

Member

reynhout commented Mar 19, 2018

@dayschmer Select your kernel version at boot time (hit Esc at the right time to get the GRUB menu, or configure GRUB to prefer a kernel version).

@Magnus445 Try installing ACPID: sudo apt install acpid. Headphones should already work, but jack detection does not, so you'd need to switch the output (audio "sink") manually in the audio applet. We have scripts for ACPID which should handle the jack detection. Tested on CYAN and TERRA. but hopefully functional on all Braswells. acpid should be included in the default install, but currently is not.

@wly5

This comment has been minimized.

Show comment
Hide comment
@wly5

wly5 Mar 21, 2018

How do you install apcid? I try to use the command: sudo apt install apcid, and it didn't work.

wly5 commented Mar 21, 2018

How do you install apcid? I try to use the command: sudo apt install apcid, and it didn't work.

@wly5

This comment has been minimized.

Show comment
Hide comment
@wly5

wly5 Mar 21, 2018

@reynhout the error message that I got was Unable to locate package apcid.

wly5 commented Mar 21, 2018

@reynhout the error message that I got was Unable to locate package apcid.

@reynhout

This comment has been minimized.

Show comment
Hide comment
@reynhout

reynhout Mar 21, 2018

Member

@wly5 Ugh, sorry. sudo apt install acpid. Corrected above, also.

Member

reynhout commented Mar 21, 2018

@wly5 Ugh, sorry. sudo apt install acpid. Corrected above, also.

@darethehair

This comment has been minimized.

Show comment
Hide comment
@darethehair

darethehair Mar 29, 2018

Note to anyone reading this looking for a fix to this issue, but with a different distro than 'GalliumOS'. I have added my own entry (just now) to the bugzilla case mentioned at the top of this thread -- indicating that I (mostly) got sound working under Linux Mint Debian Edition (thanks to other recent posts in that thread). Everything perfect? Not quite, but at least I have speaker sound now! :)

darethehair commented Mar 29, 2018

Note to anyone reading this looking for a fix to this issue, but with a different distro than 'GalliumOS'. I have added my own entry (just now) to the bugzilla case mentioned at the top of this thread -- indicating that I (mostly) got sound working under Linux Mint Debian Edition (thanks to other recent posts in that thread). Everything perfect? Not quite, but at least I have speaker sound now! :)

@reynhout

This comment has been minimized.

Show comment
Hide comment
@reynhout

reynhout Jun 7, 2018

Member

Closing: largely resolved, many months ago! Jack detection via acpid is included in nightly and 3.0 ISOs.

Member

reynhout commented Jun 7, 2018

Closing: largely resolved, many months ago! Jack detection via acpid is included in nightly and 3.0 ISOs.

@reynhout reynhout closed this Jun 7, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment