OS doesn't see my soundCard and SDCard reader.

[Vladislav]

Laptop - Asus E200Ha
On windows 10 everything work fine.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-101-generic 4.4.0-101.124 [modified: boot/vmlinuz-4.4.0-101-generic]
ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95
Uname: Linux 4.4.0-101-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.13
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: LXDE
Date: Wed Dec 20 21:10:49 2017
HibernationDevice: RESUME=UUID=b6b6290a-930f-4164-a472-ca736eeac13e
InstallationDate: Installed on 2017-12-20 (0 days ago)
InstallationMedia: LXLE 16.04 - Release amd64
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 13d3:3496 IMC Networks
 Bus 001 Device 002: ID 0bda:57ed Realtek Semiconductor Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. E200HA
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-101-generic.efi.signed root=UUID=4f349419-658e-4480-970b-881d7837bcb6 ro quiet splash pciehp.pciehp_force=1
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-101-generic N/A
 linux-backports-modules-4.4.0-101-generic N/A
 linux-firmware 1.157.13
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/21/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E200HA.303
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: E200HA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE200HA.303:bd12/21/2016:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: E200HA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

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.15 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc4

[Vladislav (vampik33)]

Thank you, everything now work fine!
I download the latest mainline kernel v4.15-rc4.