I can get sound to work with a 5.4 kernel - but it's still not great...
I haven't found a UCM file that let's it just work yet. What does work
is using the alsactl -f downloaded/asound.state.txt bit and then VLC is
able to play sound with Audio device set to chtmax98090, Direct hardware
device
I've updated my cyan (Acer Chromebook R11) to kernel 5.4rc7 from
Ubuntu's mainline PPA, but the audio is still not working (no audio
device visible according to pulseaudio).
Are you aware of something else that still needs upstreaming beside the
mentioned
thanks for the feedback
On Thu, Sep 26, 2019, 09:55 daniel primo stuart <1609...@bugs.launchpad.net>
wrote:
> Kernel needs this patch for maxim98090 to work on cyan and some baytrail
> chromebooks:
>
> https://github.com/torvalds/linux/commit/d5e120422db8808e1c8b1507900ca393a877c58f
>
> As it
Kernel needs this patch for maxim98090 to work on cyan and some baytrail
chromebooks:
https://github.com/torvalds/linux/commit/d5e120422db8808e1c8b1507900ca393a877c58f
As it didn't make to 5.3 on time, would be nice if it were backported by
ubuntu devs
--
You received this bug notification
** Tags added: cscc
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1609750
Title:
Audio not working on Acer Chromebook R11
Status in linux:
Confirmed
Status in linux package in
http://mailman.alsa-project.org/pipermail/alsa-
devel/2018-October/141340.html
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
Looks like that upstream commit might fix it,
https://patchwork.kernel.org/patch/10667953/
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1609750
Title:
Audio not working on Acer
Launchpad has imported 31 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=151521.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
A fix might be coming in some months' time to the upstream kernel.
** Changed in: pulseaudio (Ubuntu)
Status: Incomplete => Invalid
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages,
Thank you for reporting this bug to Ubuntu.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
It has never worked and I'm already using the latest upstream mainline
kernel.
The bug has the tag kernel-bug-exists-upstream already.
See upstream bug report for more details.
Thank you!
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.8
** Bug watch added: Linux Kernel Bug Tracker #151521
http://bugzilla.kernel.org/show_bug.cgi?id=151521
** Also affects: pulseaudio via
http://bugzilla.kernel.org/show_bug.cgi?id=151521
Importance: Unknown
Status: Unknown
** Project changed: pulseaudio => kernel
--
You received
Thanks, I was meaning to do that next. No change with audio on 4.7
kernel (1 of 3 hw support bugs problems did get fixed with 4.7 though).
It is likely this is not pulseaudio problem, as if pulseaudio does not
detect any sound hardware the problem is likely at a lower level.
** Tags added:
There is updated information available from the coreboot/Chromebook
community:
Baytrail/Braswell devices seem to have audio issues when booting via
RW_LEGACY, because depthcharge (the ChromeOS payload) is still doing
some initialization to the audio codec
--
You received this bug notification
** Tags removed: apport-collected
** Tags added: r11
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1609750
Title:
Audio not working on Acer Chromebook R11
Status in linux
16 matches
Mail list logo
