[bytcr-rt5651 - bytcr-rt5651, playback] Pulseaudio fails to detect card

Bug #1816429 reported by Erkan ÜNLÜTÜRK
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
Unassigned
pulseaudio (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

I'm having a sound problem

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: pulseaudio 1:8.0-0ubuntu3.10
ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-45-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: erkan 2121 F.... pulseaudio
CurrentDesktop: Unity
Date: Mon Feb 18 16:48:58 2019
InstallationDate: Installed on 2019-02-18 (0 days ago)
InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731)
SourcePackage: pulseaudio
Symptom: audio
Symptom_Card: bytcr-rt5651 - bytcr-rt5651
Title: [bytcr-rt5651 - bytcr-rt5651, playback] Pulseaudio fails to detect card
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/06/2017
dmi.bios.version: LC-BI-14-Y116CR210-424-B
dmi.board.asset.tag: Default string
dmi.board.name: Cherry Trail CR
dmi.board.vendor: AMI Corporation
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.version: Default string
dmi.modalias: dmi:bvn:bvrLC-BI-14-Y116CR210-424-B:bd12/06/2017:svnI-LifeDigitalTechnologiesLLC:pnZEDAIRTES:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvn:ct10:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: ZED AIR TES
dmi.product.version: Default string
dmi.sys.vendor: I-Life Digital Technologies LLC
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: XFCE
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-12-08 (2 days ago)
InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp.
 Bus 001 Device 003: ID 1ea7:0066
 Bus 001 Device 002: ID 6080:8060
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: I-Life Digital Technologies LLC ZED AIR TES
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic root=UUID=77349cb5-6380-4667-8fab-ff147aea5a2f ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-5.0.0-37-generic N/A
 linux-backports-modules-5.0.0-37-generic N/A
 linux-firmware 1.173.13
StagingDrivers: r8723bs
Tags: bionic staging
Uname: Linux 5.0.0-37-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 12/06/2017
dmi.bios.version: LC-BI-14-Y116CR210-424-B
dmi.board.asset.tag: Default string
dmi.board.name: Cherry Trail CR
dmi.board.vendor: AMI Corporation
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.version: Default string
dmi.modalias: dmi:bvn:bvrLC-BI-14-Y116CR210-424-B:bd12/06/2017:svnI-LifeDigitalTechnologiesLLC:pnZEDAIRTES:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvn:ct10:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: ZED AIR TES
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: I-Life Digital Technologies LLC

Revision history for this message
Erkan ÜNLÜTÜRK (erkan-unluturk) wrote :
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Can you please explain in more detail what problem you are experiencing?

Headphones? Speakers? Microphone?

What works and what doesn't work?

Changed in pulseaudio (Ubuntu):
status: New → Incomplete
Revision history for this message
Erkan ÜNLÜTÜRK (erkan-unluturk) wrote :

None of them sound, analog output looks(intel hdmi/dp lpe audio).. Including 18.04.2

alsa corrected in new version, here https://www.alsa-project.org/main/index.php/Changes_v1.1.7_v1.1.8

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I vaguely recall sound didn't work on Cherry Trail systems like this until recently. Could you please try live booting some newer versions of Ubuntu and tell us which versions have working sound?

18.04: http://releases.ubuntu.com/18.04/
18.10: http://releases.ubuntu.com/18.10/
19.04: http://cdimages.ubuntu.com/daily-live/current/

Revision history for this message
Erkan ÜNLÜTÜRK (erkan-unluturk) wrote :

Works in 18.10

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thanks. That makes this bug Fix Released (because it is fixed in some release, any release). And I think the fix would have been in the kernel.

If you could try some different kernel versions, you might/should be able to find the version where it started working:

  https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D

Presently it seems that 4.15 is not working. But kernel 4.18 (in Ubuntu 18.10) does work.

affects: pulseaudio (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
status: Incomplete → Fix Released
Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Please find the first good -rc kernel [1] between v4.16-rc1 to v4.18-rc8.

[1] http://kernel.ubuntu.com/~kernel-ppa/mainline/

Revision history for this message
Erkan ÜNLÜTÜRK (erkan-unluturk) wrote :

Why doesn't work in 18.04.2 (kernel 4.18)

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Reopened due to bionic bug 1853439

Changed in linux (Ubuntu):
status: Fix Released → New
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1816429

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Actually that still counts as Fix Released for 18.10, but incomplete for 18.04. Please answer comment #7.

tags: added: bionic
Revision history for this message
Erkan ÜNLÜTÜRK (erkan-unluturk) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected staging
description: updated
Revision history for this message
Erkan ÜNLÜTÜRK (erkan-unluturk) wrote : CRDA.txt

apport information

Revision history for this message
Erkan ÜNLÜTÜRK (erkan-unluturk) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Erkan ÜNLÜTÜRK (erkan-unluturk) wrote : IwConfig.txt

apport information

Revision history for this message
Erkan ÜNLÜTÜRK (erkan-unluturk) wrote : Lspci.txt

apport information

Revision history for this message
Erkan ÜNLÜTÜRK (erkan-unluturk) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Erkan ÜNLÜTÜRK (erkan-unluturk) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Erkan ÜNLÜTÜRK (erkan-unluturk) wrote : ProcEnviron.txt

apport information

Revision history for this message
Erkan ÜNLÜTÜRK (erkan-unluturk) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Erkan ÜNLÜTÜRK (erkan-unluturk) wrote : ProcModules.txt

apport information

Revision history for this message
Erkan ÜNLÜTÜRK (erkan-unluturk) wrote : RfKill.txt

apport information

Revision history for this message
Erkan ÜNLÜTÜRK (erkan-unluturk) wrote : UdevDb.txt

apport information

Revision history for this message
Erkan ÜNLÜTÜRK (erkan-unluturk) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Erkan ÜNLÜTÜRK (erkan-unluturk) wrote :

i don't think it is kernel related, I also don't know how to do it, sorry.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Since you said Ubuntu 18.04 is broken and 18.10 works then we need to identify which kernel version fixed the problem. Per comment #7 we believe this is probably in the range v4.16-rc1 to v4.18-rc8.

I suggest starting around v4.17. Please download:

https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17/linux-headers-4.17.0-041700_4.17.0-041700.201806041953_all.deb
https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17/linux-headers-4.17.0-041700-generic_4.17.0-041700.201806041953_amd64.deb
https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17/linux-image-unsigned-4.17.0-041700-generic_4.17.0-041700.201806041953_amd64.deb
https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17/linux-modules-4.17.0-041700-generic_4.17.0-041700.201806041953_amd64.deb

and then install them:

  sudo dpkg -i *.deb

and reboot.

Now verify the new kernel version is active:

  uname -a

and tell us if that has fixed the bug for Ubuntu 18.04.

Changed in linux (Ubuntu Bionic):
status: New → Incomplete
Changed in linux (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Oh, your latest apport upload was 18.04.3 already.

Changed in linux-hwe (Ubuntu):
status: New → Incomplete
no longer affects: linux-hwe (Ubuntu Bionic)
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Just to confirm where the bug is fixed, please also boot Ubuntu 19.10 and verify the bug is fixed there:

https://ubuntu.com/download/desktop/thank-you?version=19.10&architecture=amd64

Changed in linux (Ubuntu):
status: Fix Released → Incomplete
no longer affects: linux (Ubuntu Bionic)
Changed in pulseaudio (Ubuntu):
status: New → Incomplete
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Also your latest upload from comment #12 shows:

!!Sound Servers on this system
!!----------------------------

Pulseaudio:
      Installed - Yes (/usr/bin/pulseaudio)
      Running - No

So we need to find out why pulseaudio is not running. Please check /var/crash for crash files. If there are any crash files then please follow these instructions:

https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

Otherwise please try editing /etc/pulse/daemon.conf and add a new line:

 realtime-scheduling = no

then reboot.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

To clarify why there's so much confusion here, it appears this started out as a kernel bug in older Ubuntu releases but is now a PulseAudio bug. Two separate issues.

Revision history for this message
Erkan ÜNLÜTÜRK (erkan-unluturk) wrote :

"realtime-scheduling = no" no change

Revision history for this message
Erkan ÜNLÜTÜRK (erkan-unluturk) wrote :

there is sound after 18.10 (19.04, 19.10)

Revision history for this message
Erkan ÜNLÜTÜRK (erkan-unluturk) wrote :

it makes sense to wait for the next LTS version

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

OK then. We can say the bug was fixed in some Ubuntu versions but this might turn out to be one of those bugs where we don't know exactly where so can't backport the fix to older releases.

Changed in linux (Ubuntu):
status: Incomplete → Fix Released
Changed in pulseaudio (Ubuntu):
status: Incomplete → Fix Released
no longer affects: linux-hwe (Ubuntu)
Revision history for this message
Fábio Trentino Souza (fabiotrentino) wrote :

In KDE Neon 5.17.5 this bug exist as well...

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.