Bug 189261
| Summary: | Chuwi hi10/hi12 (Cherry Trail tablet) soundcard not recognised - rt5640 | ||
|---|---|---|---|
| Product: | Drivers | Reporter: | Wojciech Kalinowski (sq2kal) |
| Component: | Sound(ALSA) | Assignee: | Jaroslav Kysela (perex) |
| Status: | NEW --- | ||
| Severity: | normal | CC: | 2281979437, andref.rodrigues92, daniel.otero, drake, greywarl0ck, ignatiev, joehuan, kernins, koelnconcert, m.ksy, m.novosyolov, mpdas108, ndussourd, pierre-louis.bossart, russianneuromancer, sergei.a.trusov, silvan.calarco, tagore.chandan, tiwai, vinod.koul, yangxiaohua, youling257, zhbmath |
| Priority: | P1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Kernel Version: | 4.8 | Subsystem: | |
| Regression: | No | Bisected commit-id: | |
| Attachments: |
dmesg log
Kernel Configuration ALSA-info DSDT Chuwi hi10 @ 4.9 rc7 dmesg 4.9rc7 alsa-info 4.9rc7 Kernel config 4.9rc7 INF File "connected" to Intel soundcard Another file "connected" to Intel soundcard ALSA-info after change in BIOS to PCI dmesg after change in BIOS to PCI DSDT after change lspci -vvv after change asound.state from Irbis NB41 asound.state from Irbis NB41 amixer contents from Irbis NB41 attachment-24355-0.html patch to fix HID information |
||
Created attachment 246031 [details]
Kernel Configuration
Created attachment 246041 [details]
ALSA-info
it looks like a BIOS issue again, not sure why two modules would be loaded: snd_soc_rt5640 snd_soc_rt5670 Can you give us the output of cat /sys/bus/acpi/devices/10EC*/status and provide the DSDT in attachment as well. Created attachment 246271 [details]
DSDT Chuwi hi10 @ 4.9 rc7
I've decided to try and update kernel to 4.9 rc7 but nothing really changed. Also: output of cat /sys/bus/acpi/devices/10EC*/status 0 0 It seems that the codec being actually RT5670 (or similar) and ACPI gives the wrong ID as primary. The very same issue as I have for a Dell machine. I have hackish patches, but it's based on DMI match, and certainly we won't do it in that way. Created attachment 246281 [details]
dmesg 4.9rc7
Created attachment 246291 [details]
alsa-info 4.9rc7
Created attachment 246301 [details]
Kernel config 4.9rc7
Wow, that's not good. If neither of those device entries report _STA > 0 then no driver will be loaded. it looks similar to bug 156191 I also have Windows installed on this tablet. Is there anything that I can show you to help with working on this? Or maybe there's some kind of setting that I can look for in BIOS? Chuwi community got WIFI on this tablet working by changing SCC SDIO Support = ACPI to PCI so maybe this issue is also somehow fixable by something like that. Unfortunately I'm not an expert but maybe something can be done. yes, if you have sound on Windows you can look with Device Manager and give us the details on which driver is used and which HID it uses (should start with 10EC for realtek) Those are only information that I could gather with my knowledge: Windows shows 2 sound cards: Intel SST Audio Device (WDM) HID: ACPI\VEN_8086&DEV_22A8 ACPI\808622A8 *808622A8 Connected files: oem0.inf, ks.inf, wdmaudio.inf "Equivalent elements": PCI\VEN_8086&DEV_2280&SUBSYS_72708086&REV_22\3&11583659&0&00 PCI\VEN_8086&DEV_22B0&SUBSYS_72708086&REV_22\3&11583659&0&10 PCI\VEN_8086&DEV_22B8&SUBSYS_72708086&REV_22\3&11583659&0&18 PCI\VEN_8086&DEV_2294&SUBSYS_72708086&REV_22\3&11583659&0&80 PCI\VEN_8086&DEV_2295&SUBSYS_72708086&REV_22\3&11583659&0&88 PCI\VEN_8086&DEV_2296&SUBSYS_72708086&REV_22\3&11583659&0&90 PCI\VEN_8086&DEV_22B5&SUBSYS_72708086&REV_22\3&11583659&0&A0 PCI\VEN_8086&DEV_2298&SUBSYS_72708086&REV_22\3&11583659&0&D0 PCI\VEN_8086&DEV_229C&SUBSYS_72708086&REV_22\3&11583659&0&F8 ACPI\INT33A4\1 ACPI\INTL9C60\1 ACPI\INTL9C60\2 ACPI\8086228A\1 ACPI\8086228A\2 ACPI\8086228E\1 ACPI\8086228E\2 ACPI\8086228E\3 ACPI\808622C1\1 ACPI\808622C1\2 ACPI\808622C1\3 ACPI\808622C1\4 ACPI\808622C1\5 ACPI\808622C1\6 ACPI\808622C1\7 ACPI\PNP0C02\3 ACPI\INT33D5\3&11583659&0 ACPI\PNP0C02\1 BIOS Name: \_SB.PCI0.LPEA ES8316AudCodec Device HID: ACPI\VEN_ESSX&DEV_8316 ACPI\ESSX8316 *ESSX8316 Connected files: oem28.inf, BIOS Name: \_SB.PCI0.I2C2.ESSX I will attach ks.inf and wdmaudio.inf. Unfortunately I couldn't find those oem files... but there's more! I've found something called "LPE Audio Support" in BIOS and after changing that from ACPI to PCI... here's the result of inxi -Fxz: Audio:Card Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Low Power Engine Audio bus-ID: 00:15.0 Sound: ALSA v: k4.9.0-040900rc7-generic I guess that changes a lot. I will also attach alsa-info,dmesg and dsdt after change in BIOS. If I can give you anything more, please tell me. Created attachment 246411 [details]
INF File "connected" to Intel soundcard
Created attachment 246421 [details]
Another file "connected" to Intel soundcard
Created attachment 246431 [details]
ALSA-info after change in BIOS to PCI
Created attachment 246441 [details]
dmesg after change in BIOS to PCI
Created attachment 246451 [details]
DSDT after change
Created attachment 246461 [details]
lspci -vvv after change
You need the ACPI mode to configure things like interrupts and memories for the LPE audio engine (LPEA in DSDT)
What worries me is that you have a codec that is not supported by Linux:
Scope (I2C2)
{
Device (ESSX)
{
Name (_ADR, Zero) // _ADR: Address
Name (_HID, "ESSX8316") // _HID: Hardware ID
Name (_CID, "ESSX8316") // _CID: Compatible ID
Name (_DDN, "ES8316") // _DDN: DOS Device Name
Name (_UID, One) // _UID: Unique ID
Name (_PR0, Package (0x01) // _PR0: Power Resources for D0
{
CLK3
})
Name (_DEP, Package (0x01) // _DEP: Dependencies
{
PEPD
})
Name (CHAN, Package (0x02)
{
One,
0x017D7840
})
This is an Everest Audio codec and we don't have source code for it. There may be some sources in Android trees from China-based ecosystem but i am not optimistic that you can get audio on this device anytime soon unfortunately. This is not an Intel issue btw.
to confirm my theory can you run this: cat /sys/bus/acpi/devices/ESSX8316*/status cat /sys/bus/acpi/devices/10EC*/status And a bit of Googling shows this driver on github https://github.com/mq002/miqi-kernel/blob/stable-3.10-rk3288-fused/sound/soc/codecs/es8316.c I've tried those commands on PCI mode and ACPI. In both cases first one returned "15" and second "0 0". There's also a Chuwi hi10 "dual boot" version with android preinstalled. AFAIK it has same specs as single boot so maybe we can get something from it? I'm sorry for my lack of knowledge but how can I try these drivers from github? I've tried something like "git clone <path to codecs folder on github>" but it didn't work. Then I manually downloaded whole kernel from github and extracted just "codecs" folder and then tried to "make" and "sudo make install" but it didn't work too. You may want to contact the manufacturer or the authors of the ES8316 driver to ask for their latest codec and machine drivers. Chances are it's on an ancient kernel such as 3.10 or 3.14. If you get your hands on more recent code I can try to help but keep in mind this is not my day job at Intel, just trying to help Takashi with bug triaging and I am only doing this during my 'free' time. Is this fixed bug related to our chuwi problem? https://bugzilla.kernel.org/show_bug.cgi?id=98001 no, this is different. We don't have a driver for this codec yet. David Yang <yangxiaohua@everest-semi.com> tells me last year that he are working on "ES8316 linux driver for ubuntu 16.04". I not sure what this mean and I don't know if they plan to upstream it or at least publish it. For ES8316 codec driver and cherrytrail machine driver, please visit https://github.com/yangxiaohua1977/sound.git I have uploaded es8316.c, es8316.h and cht_bsw_es8316.c, and updated sst_acpi.c, Makefile and Kconfig for es8316. you can find this files in my github. /sound/soc/codecs/es8316.c /sound/soc/codecs/es8316.h /sound/soc/codecs/Makefile /sound/soc/codecs/Kconfig /sound/soc/intel/Kconfig /sound/soc/intel/boards/cht_bsw_es8316.c /sound/soc/intel/boards/Makefile /sound/soc/intel/sst/atom/sst_acpi.c Hello, David! Do you have plans to upstream driver? https://kernel.org/doc/html/latest/process/submitting-patches.html yes, you need to add your signoff to all patches, otherwise we can't touch them. For the Intel part, the code is mostly ok. You'd need to remove the printks and play a bit with indentation. run scripts/checkpatch.pl --no-tree on all your patches. Also the machine driver needs to be added first, then the Kconfig+makefile, and last the inclusion in sst_acpi. There are some mistakes that are easy to fix in the machine driver: - the codec name cannot be "es8316.1-0011", it needs to be i2c-ESSX8316:00 - all the ACPI probe is not needed upstream, see how other drivers work inthe same directory - there is no test on devm_clk_get, it should bail on -NOENT, again see other drivers. - there should be no .pm_ops since it gets in the way of suspend. this was corrected a couple of weeks ago. Also make sure you follow Mark Brown's for-next branch, this is where ASoC development is done. But hey, thanks for contributing this, you are very close to the goal so those patches are good news. Hi RussianNeuroMancer, Thank you very much. I'm not familiar,really,with how to upstream driver. but I'm sure I have that plan. Hi Pierre Bossart, Thank you for your information and help. for the codec name issue, in my EVK, the codec driver can not be probe if codec name in machine driver is i2c-ESSX8316:00. I don't know the cause of this problem. anyway, I will change codec name to i2c-ESSX8316:00. The string needs to match what you used in your codec driver can you provide the result of ls -d /sys/bus/acpi/devices/ESS* cat /sys/bus/acpi/devices/ESS*/status Your codec driver also needs an update btw to clearly separate out CONFIG_OF and CONFIG_ACPI, see e.g. rt5640 to see what they do. Hi Pierre Bossart, please see the following info. yxh@yxh-desktop:/lib64$ ls -d /sys/bus/acpi/devices/ESSX* /sys/bus/acpi/devices/ESSX8316:00 yxh@yxh-desktop:/lib64$ cat /sys/bus/acpi/devices/ESSX*/status 15 yxh@yxh-desktop:/lib64$ I will separate out CONFIG_OF and CONFIG_ACPI in codec driver as rt5640.c. When I debugged this driver, I deleted these two MACRO commands. I have another question about intel_sst_acpi 808622a8 firware. There always be an error when this firware is loading. The error information always shows 'intel_sst_acpi 808622A8:00: Direct firmware load for intel/fw_sst_22a8.bin failed with error -2'. I don't know how to fix it. I have search this error message in patchwork, it seems to be fixed by intel. following is the dmesg info. Enter into driver_register!!!!!!!! [ 2.376760] Enter into bus_add_driver!!!!!!! [ 2.376762] bus: 'platform': add driver snd-soc-dummy [ 2.376767] Enter Into bus_for_each_dev [ 2.376769] Enter Into bus_for_each_dev -----1 [ 2.376796] Enter Into bus_for_each_dev, error = 0 [ 2.376803] Exit bus_add_driver!!!!!!!!!!!Exit driver_register!!!!!!! [ 2.376810] Enter into driver_register!!!!!!!! [ 2.376812] Enter into bus_add_driver!!!!!!! [ 2.376814] bus: 'platform': add driver soc-audio [ 2.376819] Enter Into bus_for_each_dev [ 2.376821] Enter Into bus_for_each_dev -----1 [ 2.376828] Enter Into bus_for_each_dev, error = 0 [ 2.376834] Exit bus_add_driver!!!!!!!!!!!Exit driver_register!!!!!!! [ 2.376841] --es8316_init--start-- [ 2.378123] Enter into driver_register!!!!!!!! [ 2.378140] Enter into bus_add_driver!!!!!!! [ 2.378150] bus: 'i2c': add driver es8316 [ 2.378176] Enter Into bus_for_each_dev [ 2.378184] Enter Into bus_for_each_dev -----1 [ 2.378231] ---es8316_i2c_probe---probe start [ 2.378242] ---es8316_i2c_probe---probe start--------------------- [ 2.378403] Exit es8316_i2c_probe!!!!!!!!, ok [ 2.378438] Enter Into bus_for_each_dev, error = 0 [ 2.378491] Exit bus_add_driver!!!!!!!!!!!Exit driver_register!!!!!!! [ 2.378519] Enter Into bus_for_each_dev [ 2.378528] Enter Into bus_for_each_dev -----1 [ 2.378542] Enter Into bus_for_each_dev, error = 0 [ 2.378551] -----es8316_init---------, ret = 0 [ 2.378571] Enter into driver_register!!!!!!!! [ 2.378583] Enter into bus_add_driver!!!!!!! [ 2.378591] bus: 'platform': add driver sst-acpi [ 2.378612] Enter Into bus_for_each_dev [ 2.378620] Enter Into bus_for_each_dev -----1 [ 2.378679] Enter Into bus_for_each_dev, error = 0 [ 2.378704] Exit bus_add_driver!!!!!!!!!!!Exit driver_register!!!!!!! [ 2.378737] Enter into driver_register!!!!!!!! [ 2.378749] Enter into bus_add_driver!!!!!!! [ 2.378757] bus: 'platform': add driver sst-mfld-platform [ 2.378777] Enter Into bus_for_each_dev [ 2.378785] Enter Into bus_for_each_dev -----1 [ 2.378814] Enter Into bus_for_each_dev, error = 0 [ 2.378836] Exit bus_add_driver!!!!!!!!!!!Exit driver_register!!!!!!! [ 2.378867] Enter into driver_register!!!!!!!! [ 2.378879] Enter into bus_add_driver!!!!!!! [ 2.378887] bus: 'platform': add driver intel_sst_acpi [ 2.378905] Enter Into bus_for_each_dev [ 2.378914] Enter Into bus_for_each_dev -----1 [ 2.379054] Entern int sst_acpi_probe, id->id = -2116865984 [ 2.396032] ACPI device id: 0x808622a8 [ 2.396262] Enter into sst_platform_get_resources [ 2.396278] intel_sst_acpi 808622A8:00: LPE base: 0x91000000 size:0x200000 [ 2.396286] intel_sst_acpi 808622A8:00: IRAM base: 0x910c0000 [ 2.396329] intel_sst_acpi 808622A8:00: DRAM base: 0x91100000 [ 2.396356] intel_sst_acpi 808622A8:00: SHIM base: 0x91140000 [ 2.396384] intel_sst_acpi 808622A8:00: Mailbox base: 0x91144000 [ 2.396402] intel_sst_acpi 808622A8:00: DDR base: 0x20000000 [ 2.396426] Exit sst_platform_get_resources OK [ 2.398273] intel_sst_acpi 808622A8:00: Got drv data max stream 25 [ 2.399286] intel_sst_acpi 808622A8:00: Direct firmware load for intel/fw_sst_22a8.bin failed with error -2 [ 2.399308] intel_sst_acpi 808622A8:00: request fw failed [ 2.399561] success for sst_acpi_probeEnter Into bus_for_each_dev, error = 0 [ 2.399949] Exit bus_add_driver!!!!!!!!!!!Exit driver_register!!!!!!! [ 2.400059] Enter into driver_register!!!!!!!! [ 2.400076] Enter into bus_add_driver!!!!!!! [ 2.400083] bus: 'platform': add driver cht-bsw-es8316 [ 2.400110] Enter Into bus_for_each_dev [ 2.400117] Enter Into bus_for_each_dev -----1 [ 2.411356] !!!!!!!!!!!!!!!!!!!!!!!Enter Into snd_byt_es8316_mc_probe [ 2.411380] snd_byt_es8316_mc_probe, dai_index = 3 [ 2.411389] snd_byt_es8316_mc_probe, dai_num = 4 [ 2.411396] snd_byt_es8316_mc_probe, start to fix index of dai [ 2.413660] snd_byt_es8316_mc_probe, i2c_name = ESSX8316:00 [ 2.418229] ---es8316_probe--start-- [ 2.513309] mmc0: MAN_BKOPS_EN bit is not set [ 2.543711] mmc0: new HS200 MMC card at address 0001 [ 2.545480] mmcblk0: mmc0:0001 032G34 29.1 GiB [ 2.547067] mmcblk0boot0: mmc0:0001 032G34 partition 1 4.00 MiB [ 2.549237] mmcblk0boot1: mmc0:0001 032G34 partition 2 4.00 MiB [ 2.550583] mmcblk0rpmb: mmc0:0001 032G34 partition 3 4.00 MiB [ 2.557375] mmcblk0: p1 p2 p3 [ 2.562881] cht-bsw-es8316 cht-bsw-es8316: snd-soc-dummy-dai <-> media-cpu-dai mapping ok [ 2.563136] cht-bsw-es8316 cht-bsw-es8316: snd-soc-dummy-dai <-> deepbuffer-cpu-dai mapping ok [ 2.563257] compress asoc: snd-soc-dummy-dai <-> compress-cpu-dai mapping ok [ 2.563269] !!!!!!!!!!!!!!!!!!!!!!!Enter Into byt_es8316_init [ 2.563454] clk_prepare_enable, ret = 0 [ 2.563466] Exit byt_es8316_init [ 2.563477] es8316_set_dai_fmt----663, fmt[4001] [ 2.567776] es8316 in slave mode [ 2.569755] cht-bsw-es8316 cht-bsw-es8316: ES8316 HiFi <-> ssp2-port mapping ok [ 2.576714] Exit snd_byt_es8316_mc_probe [ 2.576772] Enter Into bus_for_each_dev, error = 0 [ 2.576846] Exit bus_add_driver!!!!!!!!!!!Exit driver_register!!!!!!! [ 2.576907] oprofile: using NMI interrupt. [ 2.577137] u32 classifier [ 2.577148] Actions configured [ 2.578548] NET: Registered protocol family 10 [ 2.580692] sit: IPv6 over IPv4 tunneling driver [ 2.581637] NET: Registered protocol family 17 [ 2.582050] NET: Registered protocol family 36 [ 2.582155] Key type dns_resolver registered [ 2.584156] microcode: CPU0 sig=0x406c4, pf=0x1, revision=0x406 [ 2.584211] usb 1-1: new low-speed USB device number 2 using xhci_hcd [ 2.584525] microcode: CPU1 sig=0x406c4, pf=0x1, revision=0x406 [ 2.584789] microcode: CPU2 sig=0x406c4, pf=0x1, revision=0x406 [ 2.584830] microcode: CPU3 sig=0x406c4, pf=0x1, revision=0x406 [ 2.585727] microcode: Microcode Update Driver: v2.01 <tigran@aivazian.fsnet.co.uk>, Peter Oruba [ 2.585855] SSE version of gcm_enc/dec engaged. [ 2.599485] Btrfs loaded [ 2.601177] Magic number: 5:179:824 [ 2.601505] tty ptyt4: hash matches [ 2.601839] console [netcon0] enabled [ 2.601850] netconsole: network logging started [ 2.602154] rtc_cmos 00:04: setting system clock to 2017-02-09 07:49:29 UTC (1486626569) [ 2.603878] had: Vidya: Enter alsa_card_intelhad_init [ 2.604159] had: ******** HAD DRIVER loading..*** Ver: 0.01.003 [ 2.604343] Enter into driver_register!!!!!!!! [ 2.604362] Enter into bus_add_driver!!!!!!! [ 2.604371] bus: 'platform': add driver hdmi-audio [ 2.604394] Enter Into bus_for_each_dev [ 2.604402] Enter Into bus_for_each_dev -----1 [ 2.605691] [drm] mid_hdmi_audio_register: Scheduling HDMI audio work queue [ 2.605775] Enter Into bus_for_each_dev, error = 0 [ 2.605844] Exit bus_add_driver!!!!!!!!!!!Exit driver_register!!!!!!! [ 2.605960] PM: Hibernation image not present or could not be loaded. [ 2.606086] ALSA device list: [ 2.606096] #0: cht-es8316 [ 2.606104] #1: [ 2.611429] Freeing unused kernel memory: 1348K (ffffffff82345000 - ffffffff82496000) [ 2.611440] Write protecting the kernel read-only data: 18432k [ 2.613962] Freeing unused kernel memory: 852K (ffff88000252b000 - ffff880002600000) [ 2.626202] Freeing unused kernel memory: 1500K (ffff880002a89000 - ffff880002c00000) [ 2.713316] random: systemd-udevd urandom read with 14 bits of entropy available [ 2.761721] input: PixArt Lenovo USB Optical Mouse as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/0003:17EF:6019.0001/input/input3 [ 2.762334] hid-generic 0003:17EF:6019.0001: input: USB HID v1.11 Mouse [PixArt Lenovo USB Optical Mouse] on usb-0000:00:14.0-1/input0 [ 2.809569] clocksource: Switched to clocksource tsc [ 2.915422] usb 1-3: new low-speed USB device number 3 using xhci_hcd [ 2.995001] r8169 0000:01:00.0 enp1s0: renamed from eth0 [ 3.088443] input: DELL Dell USB Entry Keyboard as /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.0/0003:413C:2107.0002/input/input4 [ 3.139249] hid-generic 0003:413C:2107.0002: input: USB HID v1.10 Keyboard [DELL Dell USB Entry Keyboard] on usb-0000:00:14.0-3/input0 [ 3.397315] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null) [ 3.620738] systemd[1]: systemd 229 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN) the codec_name in the dailink should definitively be i2c-ESSX8316:00 Vinod, can you help with the firmware download question? (In reply to yangxiaohua@everest-semi.com from comment #35) > I have another question about intel_sst_acpi 808622a8 firware. There always > be an error when this firware is loading. The error information always shows > 'intel_sst_acpi 808622A8:00: Direct firmware load for intel/fw_sst_22a8.bin > failed with error -2'. I don't know how to fix it. I have search this error > message in patchwork, it seems to be fixed by intel. The FW file is missing, can you please take the linux-firmware repository from git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git and install on your system. Also ensure CONFIG_FW_LOADER=y Hi Pierre Bossart, for your suggestion about devm_clk_get, - there is no test on devm_clk_get, it should bail on -NOENT, again see other drivers. How can I get clock source safely? if I delete the command about devm_clk_get, there are not 19.2MHZ for codec. On 02/13/2017 02:35 AM, bugzilla-daemon@bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=189261 > > --- Comment #38 from yangxiaohua@everest-semi.com > (yangxiaohua@everest-semi.com) --- > Hi Pierre Bossart, > for your suggestion about devm_clk_get, > > - there is no test on devm_clk_get, it should bail on -NOENT, again see other > drivers. > > How can I get clock source safely? if I delete the command about > devm_clk_get, > there are not 19.2MHZ for codec. you need to stop if you depend on the MCLK or fall back to BCLK use (if applicable for your codec) https://github.com/plbossart/sound/blob/experimental/codecs/sound/soc/intel/boards/bytcr_rt5640.c#L837 Note that most CHT platforms don't need any MCLK management, this is already handled by the BIOS usually. > Hi David, thanks for working on this.
I'm trying to get ES8316 sound working on Weibu F3C cherrytrail miniPC. I have now confirmed it is using SSP2 for the codec, matching the platform you are working with.
I'd be happy to collaborate and get this upstream.
But first, can you make sure you have pushed the code you are working with? And can you confirm it is working?
It doesn't compile here. First few compiler messages are:
sound/soc/codecs/es8316.c:1035:2: error: unknown field ‘controls’ specified in initializer
.controls = es8316_snd_controls,
^
sound/soc/codecs/es8316.c:1035:14: warning: initialization makes integer from pointer without a cast [-Wint-conversion]
.controls = es8316_snd_controls,
^~~~~~~~~~~~~~~~~~~
sound/soc/codecs/es8316.c:1035:14: note: (near initialization for ‘soc_codec_dev_es8316.reg_cache_step’)
sound/soc/codecs/es8316.c:1035:14: error: initializer element is not computable at load time
sound/soc/codecs/es8316.c:1035:14: note: (near initialization for ‘soc_codec_dev_es8316.reg_cache_step’)
sound/soc/codecs/es8316.c:1036:2: error: unknown field ‘num_controls’ specified in initializer
.num_controls = ARRAY_SIZE(es8316_snd_controls),
^
sound/soc/codecs/es8316.c:1037:2: error: unknown field ‘dapm_widgets’ specified in initializer
.dapm_widgets = es8316_dapm_widgets,
(In reply to Daniel Drake from comment #40) .controls, .num_controls, .dapm_widgets, .num_dapm_widgets, .dapm_routes, .num_dapm_routes are all now part of .component_driver. So, change .controls = es8316_snd_controls, .num_controls = ARRAY_SIZE(es8316_snd_controls), .dapm_widgets = es8316_dapm_widgets, .num_dapm_widgets = ARRAY_SIZE(es8316_dapm_widgets), .dapm_routes = es8316_dapm_routes, .num_dapm_routes = ARRAY_SIZE(es8316_dapm_routes), to .component_driver = { .controls = es8316_snd_controls, .num_controls = ARRAY_SIZE(es8316_snd_controls), .dapm_widgets = es8316_dapm_widgets, .num_dapm_widgets = ARRAY_SIZE(es8316_dapm_widgets), .dapm_routes = es8316_dapm_routes, .num_dapm_routes = ARRAY_SIZE(es8316_dapm_routes), }, Thanks tagoreddy. I have already solved this compile error and all the other ones that I didn't paste. But my concern is more, is this the actual code that David is testing? I would like to collaborate but we should at least be working off the same source base. David, are you definitely using this 4.10-rc kernel that your git tree is based on? Or are you using a different kernel to build and test this driver and then pushing the commits to the above git tree without testing? (In reply to Daniel Drake from comment #42) I've checked David's tree. It looks like 4.10-rc5. But my concern is, lot of code in es8316.c/.h is outdated even for 4.4 kernel. This code needs to be trimmed for new ALSA changes. Also, there are few logical changes that need to be incorporated in es8316.c to make it compatible with realtek. I'm waiting for David to make atleast one successful compilation to see what logical changes are to be incorporated. Hello frends.
I got the following error when compiling:
sound/soc/codecs/es8316.c:1049:25: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]
.volatile_reg = es8316_volatile,
^~~~~~~~~~~~~~~
sound/soc/codecs/es8316.c:1049:25: note: (near initialization for 'es8316_regmap.volatile_reg')
sound/soc/codecs/es8316.c:1050:25: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]
.readable_reg = es8316_readable,
^~~~~~~~~~~~~~~
sound/soc/codecs/es8316.c:1050:25: note: (near initialization for 'es8316_regmap.readable_reg')
I've taken David's commits and applied fixes on top: https://github.com/dsd/linux/commits/es8316 Direct links to the current driver files: https://github.com/dsd/linux/blob/es8316/sound/soc/codecs/es8316.c https://github.com/dsd/linux/blob/es8316/sound/soc/intel/boards/cht_es8316.c Now I can run alsamixer, enable the audio route to the codec, and play a sound with speaker-test. Unfortunately the output is completely silent. I've addressed most of the review comments so far. I'm aware there is a fair amount more to clean up, and I'll try to any address any further comments there, but we should probably first focus on items that might solve the key issue that nothing can be heard through the speakers. I created an audio loop within the codec itself, by enabling MIC1 as an input to the Left HP Mux, enabling the LLIN Switch, and enabling Left HP Mux as an input to Left Hp Mixer. Now when I make noise in the microphone, I can hear it on the headphone. This verifies that most of the audio path through the codec is working fine, and also that it is clocked. I used asoc debugfs to trace the path through the DAI, platform and codec DAPM graphs. Everything is On and active as expected. I confirmed that it is basically the same as another Cherry Trail platform I have here (except for the codec which is rt5645 on the other platform), including mixer levels. I also dumped the codec registers over I2C from Windows and set them to the exact same values on Linux - no change. Tomorrow I'll double check Pierre's feedback about I2S format and slots. I'm not a domain expert, so learning as I go. Hi All, I only teseted this driver in linux kernel 4.5.7. you can download it from below link, https://github.com/yangxiaohua1977/sound-linux-4.5.7.git I am only getting silence with the v4.10 code I posted above. However as mentioned, I can enable a mic-to-headphone loop in the codec itself and I hear the mic input on the headphone output, so this confirms that much of the codec is configured correctly for the output path.
I suspect something is wrong with the way the SoC is configured to send digital data to the codec, or with the way the codec's DAC is configured to process such data.
Here are my notes as I've studied this topic with an eye on how this is handled by the current code. Feedback or ideas very welcome.
snd_soc_dai_link backend has:
.dai_fmt = SND_SOC_DAIFMT_I2S | SND_SOC_DAIFMT_NB_NF
| SND_SOC_DAIFMT_CBS_CFS,
DAIFMT_I2S: the codec supports several formats including I2S. Windows is using I2S as can be seen by codec reg 0x0b bits 0 and 1 unset. Same on Linux.
I2S protocol is basically:
1. BCLK (aka SCK, SCLK) = sample rate * bit width * channels. 1 bit of audio data is transferred on each cycle.
2. LRCLK (aka WS, Fs) = indicates which channel the current sample corresponds to. So I2S specifically has a concept of 2 channel audio. This clock runs at the sample rate of the audio.
3. One data line for SoC-to-codec audio data
4. One data line for codec-to-SoC audio data
5. A master clock from SoC to codec (we know this is 19.2MHz BIOS managed in this case)
DAIFMT_NB_NF: This is the most common format and means:
- signal is available at rising edge of BCLK
- frame consists of left then right channel data. Left channel starts with falling FSYNC edge, right channel starts with rising FSYNC edge.
The datasheet says DAC data is sampled on the rising edge and also shows that the frame is left then right, so this seems correct.
SND_SOC_DAIFMT_CBS_CFS: the codec is the slave for BCLK and LRCLK. This looks correct. We know that MCLK is 19.2MHz and the datasheet suggests that the codec is not able to derive BCLK/LRCLK from a MCLK of that rate, so slave mode makes sense. Under Windows, codec reg 0x09 bit 7 is unset which means the codec is running in slave mode (same on Linux).
In cht_es8316_codec_fixup():
params_set_format(params, SNDRV_PCM_FORMAT_S24_LE);
This doesn't seem to be used by the SST driver, perhaps it is for the codec driver? Either way this seems the correct format for I2S and the datasheet explicitly mentions that the sample format for I2S is max 24 bit. Codec reg 0xa bits 2:4 are value 000 on both Windows and Linux which means 24 bit format.
/*
* Default mode for SSP configuration is TDM 4 slot, override config
* with explicit setting to I2S 2ch 24-bit. The word length is set with
* dai_set_tdm_slot() since there is no other API exposed
*/
ret = snd_soc_dai_set_fmt(rtd->cpu_dai,
SND_SOC_DAIFMT_I2S |
SND_SOC_DAIFMT_NB_IF |
SND_SOC_DAIFMT_CBS_CFS
);
ret = snd_soc_dai_set_tdm_slot(rtd->cpu_dai, 0x3, 0x3, 2, 24);
This seems to come as a copy-paste from bytcr_rt5651.c and I don't really understand it. Why does it set NB_IF when also in bytcr_rt5651.c the snd_soc_dai_link backend has NB_NF?
As far as I can see TDM relates to situations where you have more than 2 audio channels on a single data line (http://www.analog.com/media/en/technical-documentation/technical-articles/MS-2275.pdf?doc=an-1327.pdf) so we do not want to use that here. Most of the files in this directory that use DAIFMT_I2S do not call set_tdm_slot.
Here the comment says that it's the only way to enforce 24 bit width for I2S data but as far as I can see that's the default in sst_ssp_configs.
sst_ssp_configs does have default slots=4 but I'm not sure if it's really necessary to fix that up when we're using I2S which is 2 channel by definition?
Anyway I deleted this suspicious code but still no audio output, and I think I've covered all the configuration of the DAI link here. Further ideas very welcome...
The NB_IF was corrected recently, see "ASoC: Intel: atom: fix frame polarity" but it's not in 4.10. see my topic/v4.10-fixes branch on github. On 02/23/2017 11:19 AM, bugzilla-daemon@bugzilla.kernel.org wrote: > In cht_es8316_codec_fixup(): > > params_set_format(params, SNDRV_PCM_FORMAT_S24_LE); > > This doesn't seem to be used by the SST driver, perhaps it is for the codec > driver? Either way this seems the correct format for I2S and the datasheet > explicitly mentions that the sample format for I2S is max 24 bit. Codec reg > 0xa > bits 2:4 are value 000 on both Windows and Linux which means 24 bit format. > > /* > * Default mode for SSP configuration is TDM 4 slot, override config > * with explicit setting to I2S 2ch 24-bit. The word length is set > with > * dai_set_tdm_slot() since there is no other API exposed > */ > ret = snd_soc_dai_set_fmt(rtd->cpu_dai, > SND_SOC_DAIFMT_I2S | > SND_SOC_DAIFMT_NB_IF | > SND_SOC_DAIFMT_CBS_CFS > ); > ret = snd_soc_dai_set_tdm_slot(rtd->cpu_dai, 0x3, 0x3, 2, 24); > > This seems to come as a copy-paste from bytcr_rt5651.c and I don't really > understand it. Why does it set NB_IF when also in bytcr_rt5651.c the > snd_soc_dai_link backend has NB_NF? Thanks. Applied that to my kernel, changed the format to NB_NF in my machine driver, still no audible output. Also silent when removing the call to snd_soc_dai_set_fmt and snd_soc_dai_set_tdm_slot. Is there a reason why byt_rt5651_codec_fixup calls snd_soc_dai_set_fmt and snd_soc_dai_set_tdm_slot to set what is just the default and also specified in byt_rt5651_dais backend? Compared to e.g. byt-rt5640.c which is presumably also working with I2S 2channel 24 bit streams but doesnt have any specific fixup? We measured the codec inputs using the oscilliscope and the results are: MCLK = 19.2Mhz SCLK = 2.4Mhz DSDIN = None DLRCK = None Compared to windows: MCLK = 19.2Mhz SCLK = 2.4Mhz DSDIN = Input data from SOC DLRCK = 48 Khz Pierre, any ideas why we would be getting no i2s data and no lrck here? According to the schematic the corresponding SoC outputs are GP_SSP_2_TXD and I2S_1_FS. Humm, not sure what is going on here. comment #1: the configuration for rt5640 and rt5651 is identical, you need all three steps of configuring the params to 24 bits, setting the slots to 2ch and setting the I2S mode. The minor difference is that for rt5640 when SSP0 is used the firmware requires the use of 16 bits instead of 24 bits. comment #2: the bit clock of 2400 kHz is a good sign, this is what the firmware will use with 50 bits per stereo frame. I don't know why there is no LR clk, that sounds weird, and I don't know why the bit clock would toggle if the LR clock is not active. Something is wrong. If you want to debug and have access to the connector or the I2S pins, you *could* try the 'nocodec' patches we typically use to remove the issues with codec configuration and just look at the SOC output. I have some patches on https://github.com/plbossart/sound/tree/topic/da7212, look for the 'nocodec' subject, however they are a refresh of old patches and are compile-tested only with no MCLK supported (but this shouldn't matter since this is CHT and the MCLK is handled by the BIOS). This is just a hint to help you check if the right pins are driven by the firmware, take it with a grain of salt. the last time I actually tested those patches was in November 2015 and I haven't had time to check myself if they still work... Note that the initial patches were not contributed with a signed-off and that is a show-stopper for me, I can look at them but will not provide any changes or follow-up patches until there is clarity on their license/copyright status from yangxiaohua@everest-semi.com David, could you please confirm that it is OK to consider the code you have posted as Signed-off-by: David Yang <yangxiaohua@everest-semi.com> This will indicate your acceptance of the Developer's Certificate of Origin 1.1 which I paste here: By making a contribution to this project, I certify that: (a) The contribution was created in whole or in part by me and I have the right to submit it under the open source license indicated in the file; or (b) The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same open source license (unless I am permitted to submit under a different license), as indicated in the file; or (c) The contribution was provided directly to me by some other person who certified (a), (b) or (c) and I have not modified it. (d) I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistent with this project or the open source license(s) involved. Thanks Pierre. I have now made my fixup function resemble the one in byt_rt5651. Still no audible output but I'll get new scope results from that just in case something changes. I'll also get scope results from the nocodec setup. I had to make this change to get it built and activated: - select SND_SST_ATOM_HIFI2_PLATFORM + select SND_SST_MFLD_PLATFORM In the mean time, I am wondering if there are any registers that I can dump from the CPU to check on the I2S port configuration. Does the firmware set some specific registers that configure the SCLK and LRCK? If there are such registers and you provide the physical address I can dump them from the Linux side and also from Windows. Unfortunately there is no real way to lookup or modify the I2S settings. Not my choice, it's just what it is and observing the signals on the scope is your best bet. I checked the code over the week-end and the BCLK, FS, SDO work fine, the signals look ok with my logic8 analyzer. I really appreciate your efforts here. Can you clarify which exact codebase you checked? On CHT or BYT? Baytrail but it's the same driver/firmware for CHT I agree. My github commits posted above are all Signed-off-by: David Yang <yangxiaohua@everest-semi.com> (In reply to Daniel Drake from comment #52) > David, could you please confirm that it is OK to consider the code you have > posted as Signed-off-by: David Yang <yangxiaohua@everest-semi.com> > > This will indicate your acceptance of the Developer's Certificate of Origin > 1.1 > which I paste here: > > > By making a contribution to this project, I certify that: > > (a) The contribution was created in whole or in part by me and I > have the right to submit it under the open source license > indicated in the file; or > > (b) The contribution is based upon previous work that, to the best > of my knowledge, is covered under an appropriate open source > license and I have the right under that license to submit that > work with modifications, whether created in whole or in part > by me, under the same open source license (unless I am > permitted to submit under a different license), as indicated > in the file; or > > (c) The contribution was provided directly to me by some other > person who certified (a), (b) or (c) and I have not modified > it. > > (d) I understand and agree that this project and the contribution > are public and that a record of the contribution (including all > personal information I submit with it, including my sign-off) is > maintained indefinitely and may be redistributed consistent with > this project or the open source license(s) involved. Thanks David, this will help us with code review and upstreaming. Pierre, are you sure the firmware is the same? If I am reading sst-acpi.c right, Baytrail uses fw_sst_0f28.bin and Cherrytrail uses fw_sst_22a8.bin. the firmware structure is the same, there may be minor differences but that don't affect the results. Still waiting for nocodec probe results. Some more experiments in the mean time: I tried modifying sst_acpi.c so that it would use fw_sst_0f28.bin and fw_sst_0f28.bin-48kHz_i2s_master. No change in results, still silent. Verified pin config for pins AC19 (SSP_2_FS) and V18 (SSP_2_TXD) under Windows and Linux using physical registers fed85c30, fed85c34, fed5c38, fed5c3c, values are the same under both OS. (These are the registers manipulated by chv_pinmux_set_mux) While playing a sound in Windows, set bit 15 in reg fed85c30 to change SSP_2_FS to GPIO mode. Sound went silent. Unset that bit, sound came back, then set bit 15 in fed85c34 to set SSP_2_TXD to GPIO mode - sound went silent. This confirms that we're indeed working with the right pins. Booting Linux from a USB disk, I tested it on a CHT laptop with working RT5640 using DSP_B format. Working fine. Then I applied the following patch to use that same machine driver with ES8316. https://gist.github.com/dsd/cf2bb8d3a559ec9571a2c43674781e73 The format would be wrong here (DSP_B output but codec expecting I2S) but I was hoping I'd hear something bad - but still silence. Then I modified the codec regs to configure it for DSP_B input (set value 0x23 to regs 0xa and 0xb), still silent. Speculation, but I imagine the problem is the same in all these experiments, i.e. there is no SoC output from those 2 pins. I wonder if there is some other way that the BIOS is disabling these 2 pins, and then Windows is then enabling them? On the working CHT RT5640 laptop, /proc/cpuinfo lists: cpu family : 6 model : 76 model name : Intel(R) Atom(TM) x5-Z8300 CPU @ 1.44GHz stepping : 3 microcode : 0x363 On the silent CHT ES8316 MiniPC it lists: cpu family : 6 model : 76 model name : Intel(R) Atom(TM) x5-Z8300 CPU @ 1.44GHz stepping : 3 microcode : 0x359 i.e. the same except for different microcode version. I checked and there does not seem to be a microcode update published for this CPU, the CPUID in both cases is 0x000406c3. Hello Drake,
Are you using Hans_De_Goede's I2C patches in conjunction with the mainline kernel?
I've a x5-z8300 machine with ESSX8316. With Hans's help, I2C bus is now fully operational. Should you need, I would be glad to test your code.
Thanks,
Tagore
there are too many hypotheses here, and you are mixing rt5640 and rt5645 who use different settings/slots. Please check with the nocodec option if the pins are functional in I2S mode then we can work on why the codec remains silent. Probe results from nocodec kernel: MCLK = 19.2Mhz SCLK = 2.4Mhz DSDIN = None DLRCK = 48Khz One step closer since we don't have DLRCK running in my own driver, any ideas why that might be? Still no data though... so the hardware works as planned. Please share your branch so that we can figure out what the difference is. We were playing sound while probing, so I think we might still have an issue with the DSDIN pin (SSP2_TXD) which remains silent? Either way the first step is indeed figuring out the LRCK difference. Code is at git@github.com:dsd/linux.git branch es8316 Commit web view: https://github.com/dsd/linux/commits/es8316 Direct links to codec and board drivers: https://github.com/dsd/linux/blob/es8316/sound/soc/codecs/es8316.c https://github.com/dsd/linux/blob/es8316/sound/soc/intel/boards/cht_es8316.c tagoreddy, if you want to try it: Kernel config: https://gist.github.com/dsd/e360075738dbc52a198f2b1b512a3fbd You must apply mixer settings to create an audio route before you can play audio: https://gist.github.com/dsd/00e3ec5c3de2b2769f683645a566c877 I think the codec mixer settings should be good for sound playback, but if you don't hear anything, force set the values I dumped from Windows *after you start playing a sound*: https://gist.github.com/dsd/1a6ed85792f4f8a70265e87fe1b8404b If you have a mic you can create a loop on the codec side and check that you hear the mic input being output on the left channel: amixer sset "Left Hp mixer LLIN" unmute looks to me like the sysclk is not setup correctly. The code from ES8316 says: /* * Note that this should be called from init rather than from hw_params. */ static int es8316_set_dai_sysclk(struct snd_soc_dai *codec_dai, int clk_id, unsigned int freq, int dir) and in the machine driver you call it from hw_params... I also disagree with your comment that the setting the clock does nothing, 19.2 is actually a requirement if you want to support 48kHz so you really want to set this and not 24.576 which we typically use for other codecs. What I meant by the comment is that everything that is done by es8316_set_dai_sysclk() has absolutely zero effect on the hardware. It doesn't lead to any register writes or anything like that. And looking at the datasheet, I don't think the codec needs to be told what rate the master clock input is running at when running in slave mode. It states that the device can autodetect MCLK/LRCK ratio as a slave, although it doesn't list the ratio being used here (400) as supported I assume that is just a datasheet omission. The "should be called from init" comment comes copied from wm8988.c. I had recently adapted the driver do the sysclk constraints similar to the approach in es8328.c but I can move it back to wm8988's approach if preferred. And I don't think any of this could affect a lack of LRCK (SSP2_FS) output from the SoC, right? setting the sysclk indirectly selects the PLL coefficients and results in register writes. I don't understand the question on lack of LRCK, it's seen with the nocodec option and the code is identical and it's been working on all other devices. It makes no sense to me unless your hardware is broken or the measurement is wrong. You mean the PLL stuff inside es8316_pcm_hw_params()? All those nice calculations like "coeff" end up being used for ... nothing! Sorry for the codec driver mess, I am planning to gut it, but I was hoping to at least be able to hear something (and hence be able to test changes) before potentially introducing more problems. The LRCK difference is indeed puzzling. We'll double check everything. yeah, well, the codec driver doesn't seem quite ready if it has dead code. Hi, Daniel, Pierre and David! I got batch of Z3735F-based laptops with ES8316 (Irbis NB41, very similar to 4Good AM500). Daniel, I wonder if your recommendations from Comment 65 is still actual? Or I need to wait before some changes recommended by Pierre will be applied to driver? Interesting, a Bay Trail laptop with this codec, I guess I need to rename the board driver back again. Pierre's comments are valid but I don't believe they have any impact on the larger issue at hand which is that the SoC is not sending I2S data nor providing the I2S FS clock. So if you want to test the instructions above are still valid. I'm expecting to receive an oscilliscope this week so that I can continue debugging the cherry trail problem directly without requiring the round-trip to our hardware engineer. Unfortunately on Irbis NB41 there is no image on the screen with kernels before 4.11rc3 (4.4, 4.8 and 4.10 was tested; some people with similar issue on other devices even need drm-tip). Daniel, I wonder if it's ok to apply commits from your repo (https://github.com/dsd/linux/commits/es8316 since Feb 15 till the end) on top of 4.11rc3 - is it ok? I mean, If driver supposed to work with Linux 4.11? Good news, with help from Intel we found the problem. I had been copying the audio route from a working CHT/RT5645 platform that we have, but that one uses DSP_B and not I2S. The final section of the path being pcm0_in -> codec_out1 -> ssp2 Tx. For I2S, it seems like there is a firmware bug or undocumented limitation where codec_out1 can't be used, the SSP_2_TXD pin output is totally silent. Modifying the routing here (ES8316) to use pcm0_in -> codec_out0 -> ssp2 Tx, all is working. I'll now move to cleaning up the code and resyncing to 4.11. *** Bug 156191 has been marked as a duplicate of this bug. *** (In reply to Daniel Drake from comment #74) > Good news, with help from Intel we found the problem. I had been copying the > audio route from a working CHT/RT5645 platform that we have, but that one > uses DSP_B and not I2S. The final section of the path being pcm0_in -> > codec_out1 -> ssp2 Tx. > > For I2S, it seems like there is a firmware bug or undocumented limitation > where codec_out1 can't be used, the SSP_2_TXD pin output is totally silent. > > Modifying the routing here (ES8316) to use pcm0_in -> codec_out0 -> ssp2 Tx, > all is working. Codec_out0 and codec_out1 are multiplexed on the same SSP2. there is a control that defines what goes on what slot, you should double check that the route setup is aligned with your mixer setups. Your fix probably relies on the default mixer value. If you wanted codec_out1 you'd need to explicitly set the mixer to map codec_out1 to slot 0 and slot1. Thanks for the info! I guess you mean these controls: Simple mixer control 'codec_in rx deinterleaver codec_in0_0',0 Capabilities: enum Items: 'none' 'slot 0' 'slot 1' 'slot 2' 'slot 3' Item0: 'slot 0' Simple mixer control 'codec_in rx deinterleaver codec_in0_1',0 Capabilities: enum Items: 'none' 'slot 0' 'slot 1' 'slot 2' 'slot 3' Item0: 'slot 1' Simple mixer control 'codec_in rx deinterleaver codec_in1_0',0 Capabilities: enum Items: 'none' 'slot 0' 'slot 1' 'slot 2' 'slot 3' Item0: 'slot 2' Simple mixer control 'codec_in rx deinterleaver codec_in1_1',0 Capabilities: enum Items: 'none' 'slot 0' 'slot 1' 'slot 2' 'slot 3' Item0: 'slot 3' Simple mixer control 'codec_out tx interleaver slot 0',0 Capabilities: enum Items: 'none' 'codec_out0_0' 'codec_out0_1' 'codec_out1_0' 'codec_out1_1' Item0: 'codec_out0_0' Simple mixer control 'codec_out tx interleaver slot 1',0 Capabilities: enum Items: 'none' 'codec_out0_0' 'codec_out0_1' 'codec_out1_0' 'codec_out1_1' Item0: 'codec_out0_1' Simple mixer control 'codec_out tx interleaver slot 2',0 Capabilities: enum Items: 'none' 'codec_out0_0' 'codec_out0_1' 'codec_out1_0' 'codec_out1_1' Item0: 'codec_out1_0' Simple mixer control 'codec_out tx interleaver slot 3',0 Capabilities: enum Items: 'none' 'codec_out0_0' 'codec_out0_1' 'codec_out1_0' 'codec_out1_1' Item0: 'codec_out1_1' The values are identical (as shown above) on both devices - the CHT/RT5645/DSP_B setup which is using codec_out1 just fine, and also the CHT/ES8316/I2S device which is only able to use codec_out0. Apologies that I haven't been able to finish the upstreaming as soon as I had hoped. Posted my current work in progress here: https://github.com/dsd/linux/commits/es8316 It's based on a recent linux-next. Preliminary testing/review is welcome but don't look at the codec driver, haven't cleaned that up yet. The board driver is done though. Hopefully I'll finish it next week and send out some patches for proper review. On my platform the following commands set up audio routes for headphone output and mic input: amixer cset name='media1_in Gain 0 Switch' on amixer cset name='media1_in Gain 0 Volume' 0 amixer cset name='media0_out mix 0 media1_in Switch' on amixer cset name='pcm0_in Gain 0 Switch' on amixer cset name='pcm0_in Gain 0 Volume' 0 amixer cset name='codec_out0 mix 0 pcm0_in Switch' on amixer cset name='codec_out0 Gain 0 Switch' on amixer cset name='codec_out0 Gain 0 Volume' 0 amixer cset name='codec_in0 Gain 0 Switch' on amixer cset name='codec_in0 Gain 0 Volume' 0 amixer cset name='pcm1_out mix 0 media_loop2_in Switch' on amixer cset name='media_loop2_out mix 0 codec_in0 Switch' on amixer cset name='media_loop2_out Gain 0 Switch' on amixer cset name='media_loop2_out Gain 0 Volume' 0 amixer cset name='pcm1_out Gain 0 Switch' on amixer cset name='pcm1_out Gain 0 Volume' 0dB amixer cset name='DAC Playback Volume' 100% Started the upstreaming process with these patches: [PATCH 1/2] ASoC: add es8316 codec driver [PATCH 2/2] ASoC: Intel: add machine driver for BYT/CHT + ES8316 Many thanks to Pierre and the others at Intel who have helped up to this point! Hello Daniel, Thank you for you contributions, I have successfully applied your patches to 4.11, and I have sound through the headphone jack. My Chuwi 10 has internal speakers as well, I would like if those could be used, is there a way to have the output routed to the speakers? Thanks. > Posted my current work in progress here:
> https://github.com/dsd/linux/commits/es8316
I build kernel from this sources with
CONFIG_SND_SOC_ES8316=m
CONFIG_SND_SOC_INTEL_BYT_CHT_ES8316_MACH=m
but seems like driver does not start on Irbis NB41 - nothing in dmesg. Manual modprobe also does not produce any output in dmesg. Maybe driver could not detect ES8316 on BayTrail for some reason?
Matthew, thanks for testing! The ES8316 codec only has a single stereo output, so there must be something product-specific done to support multiple audio outputs. I think you will have to look for other info (e.g. android source dumps?) in order to figure out how to work with the speakers.
RussianNeuroMancer, good point, please edit sound/soc/intel/atom/sst/sst_acpi.c and add this entry in sst_acpi_bytcr
{"ESSX8316", "bytcht_es8316", "intel/fw_sst_0f28.bin", "cht-bsw", NULL,
&byt_rvp_platform_data },
> I think you will have to look for other info (e.g. android source dumps?) in > order to figure out how to work with the speakers. What if there is no Android for particular device? Like laptop in my case. Or you mean Android version of this driver in general? https://github.com/rockchip-linux/kernel/blob/release-4.4/sound/soc/codecs/es8316.c > RussianNeuroMancer, good point, please edit > sound/soc/intel/atom/sst/sst_acpi.c and add this entry in sst_acpi_bytcr Thanks for this advice! I will try to test it in next couple of days. Created attachment 256721 [details] asound.state from Irbis NB41 Hi, Daniel! Driver loads now, however after applying settings from Comment 78 (with "-c 1" switch, because first audio adapter is HDMI output) there is no audio from headphones output. In headphones I can hear when output is on/off in the beginning and end of playback (just standard audio test in System Settings) but nothing besides that. asound.state is attached. Created attachment 256833 [details] asound.state from Irbis NB41 Just in case, there is confirmation that driver is actually loads: ~$ cat /proc/asound/cards 0 [Audio ]: HdmiLpeAudio - Intel HDMI/DP LPE Audio Intel HDMI/DP LPE Audio 1 [bytchtes8316 ]: bytcht-es8316 - bytcht-es8316 bytcht-es8316 [ 8.681833] bytcht_es8316 bytcht_es8316: snd-soc-dummy-dai <-> media-cpu-dai mapping ok [ 8.682013] bytcht_es8316 bytcht_es8316: snd-soc-dummy-dai <-> deepbuffer-cpu-dai mapping ok [ 8.682069] es8316_set_dai_fmt----502, fmt[4001] [ 8.682073] es8316 in slave mode [ 8.682450] bytcht_es8316 bytcht_es8316: ES8316 HiFi <-> ssp2-port mapping ok [ 129.452480] Enter::es8316_pcm_startup----593 es8316->sysclk=19200000 [ 136.630644] Enter::es8316_pcm_startup----593 es8316->sysclk=19200000 [ 907.125841] Enter::es8316_pcm_startup----593 es8316->sysclk=19200000 Also previously I uploaded wrong asound.state file, here is the right one - with settings from Comment 78 applied. Also I uploaded amixer contents outout for es8316 audio adapter. Created attachment 256835 [details]
amixer contents from Irbis NB41
https://patchwork.kernel.org/patch/9729633/ > Only SSP2 has been tested here, so BYT-CR platforms that require SSP0 will > not work. I see. David, Daniel, Pierre, is there solution for this? Are you sure your platform is BYT-CR? You can test by searching and replacing ssp2 and SSP2 in bytcht_es8316.c, replace with ssp0 / SSP0 there are two telltale signs of BYT-CR 1. the auto detection tells you it is BYT-CR 2. the interrupt index matches BYT-CR (which may happen even when the auto detection fails) You'll need to keep in mind that SSP0 only works with 16-bit I2S mode, and you'll have to look at the bytcr-rt5640.c code to see the configs. Again only if you have evidence it's truly a byt-cr platform. Thanks for looking into this! > Are you sure your platform is BYT-CR? Judging by https://www.intel.com/content/www/us/en/design/mobile-devices/platforms/bay-trail-cr/overview.html I guess it is. I mentioned in Comment 71 that SoC is Z3735F, which is BYT-CR, right? > 1. the auto detection tells you it is BYT-CR > 2. the interrupt index matches BYT-CR Where I can check this? > You'll need to keep in mind that SSP0 only works with 16-bit I2S mode Does it mean that driver need some other changes besides mentioned in Comment 88? > and you'll have to look at the bytcr-rt5640.c code to see the configs. Does it mean that configuration suggested by Daniel in Comment 78 is expected to not work in case of BYT-CR with ES8316 even with changes from Comment 88? no, unfortunately the same chip is used in Byt and byt-cr, the only difference is the package which isn't clearly identifiable. I know it's crazy but it is what it is. I can't answer to all of your questions, there is a point where you have to roll-up your sleeves and test yourself if you want a fix for a platform no one else has. On Chuwi Hi12 sound is lost after system suspend & resume until I manually reload both machine & codec drivers (rmmod & modprobe). I can hear slight pops as device gets opened/closed, so analog part definitely gets powered. Does anyone else has the same issue? Let me know if you need some specific info On latest kernels Irbis NB41 platform is correctly detected: > [ 8.431831] intel_sst_acpi 80860F28:00: Detected Baytrail-CR platform I modified sound/soc/intel/atom/sst/sst_acpi.c as was suggested in Comment 82: > { > .id = "ESSX8316", > .drv_name = "bytcht_es8316", > .fw_filename = "intel/fw_sst_0f28.bin", > .board = "cht-bsw", > .pdata = &byt_rvp_platform_data > }, was added to sst_acpi_bytcr. There is relevant part of dmesg: > [ 8.338555] bytcht_es8316 bytcht_es8316: snd-soc-dummy-dai <-> > media-cpu-dai mapping ok > [ 8.338626] bytcht_es8316 bytcht_es8316: snd-soc-dummy-dai <-> > deepbuffer-cpu-dai mapping ok > [ 8.344885] bytcht_es8316 bytcht_es8316: ES8316 HiFi <-> ssp0-port mapping > ok There is aplay -l output: > **** List of PLAYBACK Hardware Devices **** > card 0: Audio [Intel HDMI/DP LPE Audio], device 0: HdmiLpeAudio [Intel > HDMI/DP LPE Audio] > Subdevices: 1/1 > Subdevice #0: subdevice #0 > card 0: Audio [Intel HDMI/DP LPE Audio], device 1: HdmiLpeAudio [Intel > HDMI/DP LPE Audio] > Subdevices: 1/1 > Subdevice #0: subdevice #0 > card 1: bytchtes8316 [bytcht-es8316], device 0: 3 [] > Subdevices: 1/1 > Subdevice #0: subdevice #0 > card 1: bytchtes8316 [bytcht-es8316], device 1: Deep-Buffer Audio (*) [] > Subdevices: 1/1 > Subdevice #0: subdevice #0 Unfortunately, playback of 16 bit le 48kHz sample to -Dhw:1,0 or -Dhw:1,1 produce nothing but silence. Is there anything else to try? Hello everyone, I have Chuwi Hi12 and sound does not work with either 4.13 or 4.14 rc3 as well. Here is information on its hardware components and system logs: https://linux-hardware.org/index.php?probe=432a39d713 (by the way, the Goodix touch screen stopped working in Linux 4.13, I wrote about it here: https://bugzilla.kernel.org/show_bug.cgi?id=156511#c59 , maybe someone will be interested). I installed audio configs from https://github.com/kernins/linux-chwhi12/tree/master/configs/audio but they do not help Here is the output of alsa-info.sh : http://www.alsa-project.org/db/?f=31497d9928c1a51c0bb47ca09dee9d7c51162341 Installing the Linux kernel with many patches applied https://abf.io/trs/kernel-tablet-4.13 , the sound also does not work in both PCI and ACPI bios modes. ----------------------------------------------- Many thanks to everyone involved in this! Created attachment 258709 [details]
attachment-24355-0.html
Thanks for your email
I am on vacation till Oct 7th
Please expect delayed response.
Regards
--
~Vinod
Oh, the sound DOES WORK on 4.13 and 4.14, if ACPI audio mode in chosen in BIOS. Sometimes it's necessary lo manually locad the kernel module $ sudo modprobe snd_soc_es8316 No additional UCMs and asound.conf are not needed, Pulseaudio does work. But the sound can be outputed only via headphones and cannot be routed to the internel speakers, as I've read here, ES8316 has only one hadrware audio connection; has anyone managed to make the internal speakers work? Sorry for misinforming, UCM configs from https://github.com/kernins/linux-chwhi12 are needed for the sound to work. I have built 4.13 with https://github.com/kernins/linux-chwhi12 applied on top of its source, and now in Chuwi Hi12, both SPEAKERS and HEADPHONES work! speakers do NOT work on the upstream 4.14 kernel. Can you please make upstream changes basing on that code? > in Chuwi Hi12, both SPEAKERS and HEADPHONES work! I think that because of https://github.com/kernins/linux-chwhi12/commit/9ba2e5bcba5ab19bd3b3732c5ddbd87b8945c9aa#diff-33903aae39f3538405aba78c2b3974bd >I think that because of Nope, it just exports relevant gpios to tinker with from usr space. Next commit is what actually makes it work based on HW HP-detection - https://github.com/kernins/linux-chwhi12/commit/60749066b499daa375baec866ce302701ca73e1f However, it is still quick-n-dirty grade, just to get it working [ 11.263173] bytcht_es8316 bytcht_es8316: ASoC: CODEC DAI ES8316 HiFi not registered [ 11.263186] bytcht_es8316 bytcht_es8316: snd_soc_register_card failed -517 Fedora 26, kernel 4.13.5-200.fc26.x86_64. command "aplay -l" doesn't show any sound devices. I don't know, may by this is a bug of Fedora developers... (In reply to Ivan Ivanov from comment #100) > [ 11.263173] bytcht_es8316 bytcht_es8316: ASoC: CODEC DAI ES8316 HiFi not > registered > [ 11.263186] bytcht_es8316 bytcht_es8316: snd_soc_register_card failed -517 > > Fedora 26, kernel 4.13.5-200.fc26.x86_64. > > command "aplay -l" doesn't show any sound devices. > > I don't know, may by this is a bug of Fedora developers... as usual, please attach the dmesg and alas-info.sh logs put this folder into /usr/share/alsa/ucm/, otherwise your sound will not work, because this UCM is currently not mainlined in ALSA (In reply to Pierre Bossart from comment #101) > as usual, please attach the dmesg and alas-info.sh logs Have the same issues nn same hardware. you can see dmesg https://linux-hardware.org/index.php?probe=ae417f2e2c&log=dmesg it looks like the codec driver is not loaded, and we'd need to check what ACPI ID is used so please send the alas-info.sh log (make sure it does provide ACPI-related info) Here is alsa-info output http://www.alsa-project.org/db/?f=6825eeac9f7480168139c6cf035ef775386b65b6 Looks like a BIOS issue, can you try the fix below. if it works then we need to use the usual HID update, the extension for the i2c device seems to be rather random.
diff --git a/sound/soc/intel/boards/bytcht_es8316.c b/sound/soc/intel/boards/bytcht_es8316.c
index 8088396717e3..905f429bd13b 100644
--- a/sound/soc/intel/boards/bytcht_es8316.c
+++ b/sound/soc/intel/boards/bytcht_es8316.c
@@ -205,7 +205,7 @@ static struct snd_soc_dai_link byt_cht_es8316_dais[] = {
.platform_name = "sst-mfld-platform",
.no_pcm = 1,
.codec_dai_name = "ES8316 HiFi",
- .codec_name = "i2c-ESSX8316:00",
+ .codec_name = "i2c-ESSX8316:01",
.dai_fmt = SND_SOC_DAIFMT_I2S | SND_SOC_DAIFMT_NB_NF
| SND_SOC_DAIFMT_CBS_CFS,
.be_hw_params_fixup = byt_cht_es8316_codec_fixup,
After changing codec_name from i2c-ESSX8316:00 to i2c-ESSX8316:01 I got nearly a hundred error messages in dmesg: [ 76.680909] Audio Port: ASoC: no backend DAIs enabled for Audio Port [ 76.681544] Audio Port: ASoC: no backend DAIs enabled for Audio Port [ 76.681905] Audio Port: ASoC: no backend DAIs enabled for Audio Port [ 76.685521] Audio Port: ASoC: no backend DAIs enabled for Audio Port [ 76.685966] Audio Port: ASoC: no backend DAIs enabled for Audio Port [ 76.686146] Audio Port: ASoC: no backend DAIs enabled for Audio Port alsa-info: http://www.alsa-project.org/db/?f=9f02a40031a10b4d8c8bb6b663522cc5ca68f533 Anyway, I'll try again mb I made mistakes. no, it's all good, this means the codec DAI was found and the card created. you are only missing a UCM file to set the missing mixers. The patch does solve the issue that the ACPI does not use the :00 extension for the i2C device, so we'll have to fix this with the standard recipe. Great. Now I understand the case. Here is fresh alsa-info after copying umc files into /usr/share/alsa/ucm/bytcht-es8316/ http://www.alsa-project.org/db/?f=6ebd1331ba5f4f3754a9376ed9514d02d0079177 dmesg has no errors, however there is no sound output device. I'm sorry for the long answer... alsa-info.sh: http://www.alsa-project.org/db/?f=bc480e21f4d4121e7ce98e16db94b08173443ca3 dmesg: https://yadi.sk/d/nHTPgU2z3NtDHf I think that I have same problems as Sergey... I have to say that I forgot to uncomment HeadPhones section in HiFi. After enabling this section if I connect headphones they are working. Speaker section does not. If your talking about ucm from chuwi-hi12 repo posted above, then hp section in its current state is actually irrelevant, and so is speakers one.
They both are basically empty, all the necessary cmds are in verb's main enableSeq.
The codec itself has only one analog out, so spk is controlled by external (to codec ic) analog switch, which in turn is controlled by soc gpio line. Additional code is required to make it work.
You may try my test version from the abovementioned repo, if you want. It should work if your device has a similar implementation, and especially matching gpio order in acpi dt. Something like this
Device (ESSX)
{
...snip...
Name (_HID, "ESSX8316") // _HID: Hardware ID
Name (_CID, "ESSX8316") // _CID: Compatible ID
...snip...
Method (_CRS, 0, NotSerialized) // _CRS: Current Resource Settings
{
Name (SBUF, ResourceTemplate ()
{
I2cSerialBusV2 (0x0011, ControllerInitiated, 0x00061A80,
AddressingMode7Bit, "\\_SB.PCI0.I2C2",
0x00, ResourceConsumer, , Exclusive,
)
IO-OUT FIRST--> GpioIo (Exclusive, PullDefault, 0x0000, 0x0000, IoRestrictionOutputOnly,
"\\_SB.GPO1", 0x00, ResourceConsumer, ,
)
{ // Pin list
0x001B
}
THEN INTERRUPT--> GpioInt (Edge, ActiveHigh, ExclusiveAndWake, PullNone, 0x0000,
"\\_SB.GPO3", 0x00, ResourceConsumer, ,
)
{ // Pin list
0x004F
}
})
You may check this thread https://bugzilla.kernel.org/show_bug.cgi?id=156511 for instructions of how to dump your tables, should you need them.
Also note that your device may have non-reference hp-detection circuit which can result to effectively inverted hp status as seen by the codec ic.
This will result in speakers being enabled when hp is inserted, and disabled otherwise (easily fixable once confirmed).
Watch for "Status: %u / HPIns %u / GMShrt %u" messages in dmesg
>- .codec_name = "i2c-ESSX8316:00",
>+ .codec_name = "i2c-ESSX8316:01",
it helped me with my problem.
i've the next question,
is it possible to do something to make that the soundcard work with the standard kernel from the repository?
(In reply to Ivan Ivanov from comment #113) > >- .codec_name = "i2c-ESSX8316:00", > >+ .codec_name = "i2c-ESSX8316:01", > > it helped me with my problem. > i've the next question, > is it possible to do something to make that the soundcard work with the > standard kernel from the repository? So now that we have evidence that audio works, it's pretty easy to fix this ACPI issue with a dynamic update of the codec_name, I've done it for other machine drivers. The gpio stuff is not something I can help with, I don't have hardware so it's something that requires work from people with access to codec documentation, schematics and hardware. It's usually at this level that quirks come into play, board designers never select the same routing... Pierre, many thanks for you help... Finally, my device can play sound through the built-in soundcard. I waited and hoped for this a year and a half :) Remains only strange problems with the firmware for wireless chip(or with driver for it). Created attachment 260295 [details]
patch to fix HID information
if folks can test this patch before it goes upstream it'd be appreciated.
(In reply to Pierre Bossart from comment #116) > Created attachment 260295 [details] > patch to fix HID information > > if folks can test this patch before it goes upstream it'd be appreciated. Works like a charm, approving. To conclude, I have working headphones with Ubuntu kernell 4.13.0-15.16. I didn't add HiFi file from chuwi-hi12 repo, but added only asound.conf file. Also applied this great fix for codec_name. Thanks to all the participants. Hi10-Plus user here. I can help as you guys instruct me how. Hello. Just tested this great codec_name fix on Jumper ezpad 6 and work as expected(kernel 4.14). I now have headphones working ( tested speakers changing ucm files and got sound through speakers and headphones at same time but hp need to be connected). Thanks Guys! (In reply to Dmitry from comment #112) > Also note that your device may have non-reference hp-detection circuit which > can result to effectively inverted hp status as seen by the codec ic. > This will result in speakers being enabled when hp is inserted, and disabled > otherwise (easily fixable once confirmed). > Watch for "Status: %u / HPIns %u / GMShrt %u" messages in dmesg Just tried this and confirmed the speakers being enabled when hp is inserted. [ 18.341070] es8316 i2c-ESSX8316:01: Status: 38 / HPIns 1 / GMShrt 1 / OUT: 0 [ 23.699997] es8316 i2c-ESSX8316:01: Status: 36 / HPIns 1 / GMShrt 0 / OUT: 0 [ 51.820258] es8316 i2c-ESSX8316:01: Status: 32 / HPIns 0 / GMShrt 0 / OUT: 1 [ 62.741768] es8316 i2c-ESSX8316:01: Status: 34 / HPIns 0 / GMShrt 1 / OUT: 1 [ 68.193849] es8316 i2c-ESSX8316:01: Status: 32 / HPIns 0 / GMShrt 0 / OUT: 1 [ 68.196243] es8316 i2c-ESSX8316:01: Status: 32 / HPIns 0 / GMShrt 0 / OUT: 1 How should i fix this ? Thanks. (In reply to André Rodrigues from comment #120) > (In reply to Dmitry from comment #112) > How should i fix this ? > > Thanks. Try adding dmi matching rules for your hardware to hpdet_inverted_flag[] (line 653). You may find your board_vendor & board_name in dmidecode output chuwi hi10 pro，alc5651，many chinese CHT tablet alc5651/es8316 how to make them sound work? new project SOF audio，i don't know how to make FW and topology files for 5651/5672/5640/5645/es8316. https://github.com/plbossart/sound/tree/topic/sof-v4-14-rebase https://github.com/plbossart/UCM/tree/master/bytcr_rt5651 + .sof_fw_filename = "intel/reef-cht.ri", + .sof_tplg_filename = "intel/reef-cht-rt5651.tplg", + .asoc_plat_name = "sst-mfld-platform", (In reply to André Rodrigues from comment #119) > Hello. > > Just tested this great codec_name fix on Jumper ezpad 6 and work as > expected(kernel 4.14). > > I now have headphones working ( tested speakers changing ucm files and got > sound through speakers and headphones at same time but hp need to be > connected). > > Thanks Guys! my Cherry trail ezpad 6 M4，headphone and speaker both no sound，can you help me ? i need your ucm files and asound.state Hello Jumping in just after trying to compile a freshly downloaded 4.18 with ES8316 options activated. sounds like all needed drivers and codec are well presents in the kernel tree ( so has been upstreamed) but seems not to compiled properly Anyone succeeded in compiling it on 4.18 ? Any restictions that I may have missed ? Many thanks Regards Noel (In reply to youling257 from comment #125) > (In reply to André Rodrigues from comment #119) > > Hello. > > > > Just tested this great codec_name fix on Jumper ezpad 6 and work as > > expected(kernel 4.14). > > > > I now have headphones working ( tested speakers changing ucm files and got > > sound through speakers and headphones at same time but hp need to be > > connected). > > > > Thanks Guys! > > my Cherry trail ezpad 6 M4，headphone and speaker both no sound，can you help > me ? > > i need your ucm files and asound.state I also have EZPAD6 M4, and my headphnoe work with this config https://github.com/kernins/linux-chwhi12/tree/master/configs/audio, but the speaker not work (In reply to 2281979437 from comment #127) > (In reply to youling257 from comment #125) > > (In reply to André Rodrigues from comment #119) > > > Hello. > > > > > > Just tested this great codec_name fix on Jumper ezpad 6 and work as > > > expected(kernel 4.14). > > > > > > I now have headphones working ( tested speakers changing ucm files and > got > > > sound through speakers and headphones at same time but hp need to be > > > connected). > > > > > > Thanks Guys! > > > > my Cherry trail ezpad 6 M4，headphone and speaker both no sound，can you help > > me ? > > > > i need your ucm files and asound.state > > I also have EZPAD6 M4, and my headphnoe work with this config > https://github.com/kernins/linux-chwhi12/tree/master/configs/audio, but the > speaker not work cat /sys/kernel/debug/gpio can you see speaker-amp (In reply to youling257 from comment #128) > (In reply to 2281979437 from comment #127) > > (In reply to youling257 from comment #125) > > > (In reply to André Rodrigues from comment #119) > > > > Hello. > > > > > > > > Just tested this great codec_name fix on Jumper ezpad 6 and work as > > > > expected(kernel 4.14). > > > > > > > > I now have headphones working ( tested speakers changing ucm files and > > got > > > > sound through speakers and headphones at same time but hp need to be > > > > connected). > > > > > > > > Thanks Guys! > > > > > > my Cherry trail ezpad 6 M4，headphone and speaker both no sound，can you > help > > > me ? > > > > > > i need your ucm files and asound.state > > > > I also have EZPAD6 M4, and my headphnoe work with this config > > https://github.com/kernins/linux-chwhi12/tree/master/configs/audio, but the > > speaker not work > > cat /sys/kernel/debug/gpio > > can you see speaker-amp no, here is my output: gpiochip4: GPIOs 225-227, parent: platform/INT0002:00, INT0002 Virtual GPIO: gpio-227 ( |ACPI:Event ) in lo IRQ gpiochip3: GPIOs 228-313, parent: platform/INT33FF:03, INT33FF:03: gpio-274 ( |ACPI:OpRegion ) out lo gpio-309 ( |80860F14:03 ) in hi IRQ gpiochip2: GPIOs 314-340, parent: platform/INT33FF:02, INT33FF:02: gpio-322 ( |power ) in hi IRQ gpio-330 ( |ACPI:OpRegion ) out hi gpio-338 ( |ACPI:Event ) in hi IRQ gpiochip1: GPIOs 341-413, parent: platform/INT33FF:01, INT33FF:01: gpio-344 ( |ACPI:Event ) in hi IRQ gpio-364 ( |ACPI:OpRegion ) out hi gpio-366 ( |ACPI:OpRegion ) out hi gpio-407 ( |ACPI:OpRegion ) out lo gpiochip0: GPIOs 414-511, parent: platform/INT33FF:00, INT33FF:00: gpio-492 ( |volume_up ) in hi IRQ gpio-494 ( |volume_down ) in hi IRQ > > cat /sys/kernel/debug/gpio
> >
> > can you see speaker-amp
> no, here is my output:
>
> gpiochip4: GPIOs 225-227, parent: platform/INT0002:00, INT0002 Virtual GPIO:
> gpio-227 ( |ACPI:Event ) in lo IRQ
>
> gpiochip3: GPIOs 228-313, parent: platform/INT33FF:03, INT33FF:03:
> gpio-274 ( |ACPI:OpRegion ) out lo
> gpio-309 ( |80860F14:03 ) in hi IRQ
>
> gpiochip2: GPIOs 314-340, parent: platform/INT33FF:02, INT33FF:02:
> gpio-322 ( |power ) in hi IRQ
> gpio-330 ( |ACPI:OpRegion ) out hi
> gpio-338 ( |ACPI:Event ) in hi IRQ
>
> gpiochip1: GPIOs 341-413, parent: platform/INT33FF:01, INT33FF:01:
> gpio-344 ( |ACPI:Event ) in hi IRQ
> gpio-364 ( |ACPI:OpRegion ) out hi
> gpio-366 ( |ACPI:OpRegion ) out hi
> gpio-407 ( |ACPI:OpRegion ) out lo
>
> gpiochip0: GPIOs 414-511, parent: platform/INT33FF:00, INT33FF:00:
> gpio-492 ( |volume_up ) in hi IRQ
> gpio-494 ( |volume_down ) in hi IRQ
if you can found which gpio for speak，you can
echo xxx > /sys/class/gpio/export
echo 1 >/sys/class/gpio/gpioxxx/value
Hello All! I have a mini-ps Wintel CX-W9 Pro. Inside the sound chip is ESSX8316. When loading the kernel, it gives an error: [18.699167] intel_sst_acpi 808622A8: 00: LPE base: 0x91000000 size: 0x200000 [18.699172] intel_sst_acpi 808622A8: 00: IRAM base: 0x910c0000 [18.699205] intel_sst_acpi 808622A8: 00: DRAM base: 0x91100000 [18.699215] intel_sst_acpi 808622A8: 00: SHIM base: 0x91140000 [18.699224] intel_sst_acpi 808622A8: 00: Mailbox base: 0x91144000 [18.699230] intel_sst_acpi 808622A8: 00: DDR base: 0x20000000 [18.700833] intel_sst_acpi 808622A8: 00: Got drv data max stream 25 [18.784814] bytcht_es8316 bytcht_es8316: ASoC: CODEC DAI ES8316 HiFi not registered [18.784833] bytcht_es8316 bytcht_es8316: snd_soc_register_card failed -517 [19.137102] bytcht_es8316 bytcht_es8316: ASoC: CODEC DAI ES8316 HiFi not registered [19.137113] bytcht_es8316 bytcht_es8316: snd_soc_register_card failed -517 The sound device does not work (( $ aplay -l aplay: device_list:267: no soundcards found... $ Linux Kernel 4.19.2, at 4.14.81 the same problem. Help me please! How to fix it? (In reply to Alexey Ignatev from comment #131) > Hello All! > > > I have a mini-ps Wintel CX-W9 Pro. Inside the sound chip is ESSX8316. > > When loading the kernel, it gives an error: > > [18.699167] intel_sst_acpi 808622A8: 00: LPE base: 0x91000000 size: 0x200000 > [18.699172] intel_sst_acpi 808622A8: 00: IRAM base: 0x910c0000 > [18.699205] intel_sst_acpi 808622A8: 00: DRAM base: 0x91100000 > [18.699215] intel_sst_acpi 808622A8: 00: SHIM base: 0x91140000 > [18.699224] intel_sst_acpi 808622A8: 00: Mailbox base: 0x91144000 > [18.699230] intel_sst_acpi 808622A8: 00: DDR base: 0x20000000 > [18.700833] intel_sst_acpi 808622A8: 00: Got drv data max stream 25 > [18.784814] bytcht_es8316 bytcht_es8316: ASoC: CODEC DAI ES8316 HiFi not > registered > [18.784833] bytcht_es8316 bytcht_es8316: snd_soc_register_card failed -517 > [19.137102] bytcht_es8316 bytcht_es8316: ASoC: CODEC DAI ES8316 HiFi not > registered > [19.137113] bytcht_es8316 bytcht_es8316: snd_soc_register_card failed -517 > > The sound device does not work (( > > $ aplay -l > aplay: device_list:267: no soundcards found... > $ > > Linux Kernel 4.19.2, at 4.14.81 the same problem. > > Help me please! How to fix it? Please share the full dmesg and alsa-info.sh logs (in attachment). The errors show that most likely the codec driver did not probe successfully and did not register the DAIs needed by the machine driver. (In reply to Pierre Bossart from comment #132) > (In reply to Alexey Ignatev from comment #131) > > Hello All! > > > > > > I have a mini-ps Wintel CX-W9 Pro. Inside the sound chip is ESSX8316. > > > > When loading the kernel, it gives an error: > > > > [18.699167] intel_sst_acpi 808622A8: 00: LPE base: 0x91000000 size: > 0x200000 > > [18.699172] intel_sst_acpi 808622A8: 00: IRAM base: 0x910c0000 > > [18.699205] intel_sst_acpi 808622A8: 00: DRAM base: 0x91100000 > > [18.699215] intel_sst_acpi 808622A8: 00: SHIM base: 0x91140000 > > [18.699224] intel_sst_acpi 808622A8: 00: Mailbox base: 0x91144000 > > [18.699230] intel_sst_acpi 808622A8: 00: DDR base: 0x20000000 > > [18.700833] intel_sst_acpi 808622A8: 00: Got drv data max stream 25 > > [18.784814] bytcht_es8316 bytcht_es8316: ASoC: CODEC DAI ES8316 HiFi not > > registered > > [18.784833] bytcht_es8316 bytcht_es8316: snd_soc_register_card failed -517 > > [19.137102] bytcht_es8316 bytcht_es8316: ASoC: CODEC DAI ES8316 HiFi not > > registered > > [19.137113] bytcht_es8316 bytcht_es8316: snd_soc_register_card failed -517 > > > > The sound device does not work (( > > > > $ aplay -l > > aplay: device_list:267: no soundcards found... > > $ > > > > Linux Kernel 4.19.2, at 4.14.81 the same problem. > > > > Help me please! How to fix it? > > Please share the full dmesg and alsa-info.sh logs (in attachment). The > errors show that most likely the codec driver did not probe successfully and > did not register the DAIs needed by the machine driver. Hi Pierre! Thanks for the quick response! https://dropmefiles.com/GyFSq I`m getting logs from FastSYS embedded linux (small linux for self-service kiosks), inside minimal alsa and this system is very light (based on busybox). I ask to help start the kernel modules, for up the soundcard. Thanks!!!
>
> https://dropmefiles.com/GyFSq
Please add the files as attachments in this bugzilla.
What I was asking is information on ACPI devices. It seems like you don't have /sys/bus/acpi/devices on your system, which makes it impossible to debug. You should have something like this in the log of alsa-info.sh
!!ACPI Device Status Information
!!---------------
/sys/bus/acpi/devices/ACPI000C:00/status 15
/sys/bus/acpi/devices/INT33A1:00/status 15
/sys/bus/acpi/devices/INT340E:00/status 15
/sys/bus/acpi/devices/INT3F0D:00/status 15
/sys/bus/acpi/devices/LNXPOWER:00/status 1
/sys/bus/acpi/devices/LNXPOWER:01/status 1
/sys/bus/acpi/devices/LNXPOWER:02/status 1
/sys/bus/acpi/devices/LNXPOWER:03/status 1
/sys/bus/acpi/devices/LNXPOWER:04/status 1
/sys/bus/acpi/devices/LNXPOWER:05/status 1
/sys/bus/acpi/devices/LNXPOWER:06/status 1
/sys/bus/acpi/devices/LNXPOWER:07/status 1
/sys/bus/acpi/devices/LNXPOWER:08/status 1
/sys/bus/acpi/devices/LNXPOWER:09/status 1
/sys/bus/acpi/devices/LNXPOWER:0a/status 1
(In reply to Pierre Bossart from comment #134) > > > > https://dropmefiles.com/GyFSq > > Please add the files as attachments in this bugzilla. > > What I was asking is information on ACPI devices. It seems like you don't > have /sys/bus/acpi/devices on your system, which makes it impossible to > debug. You should have something like this in the log of alsa-info.sh > > > !!ACPI Device Status Information > !!--------------- > > /sys/bus/acpi/devices/ACPI000C:00/status 15 > /sys/bus/acpi/devices/INT33A1:00/status 15 > /sys/bus/acpi/devices/INT340E:00/status 15 > /sys/bus/acpi/devices/INT3F0D:00/status 15 > /sys/bus/acpi/devices/LNXPOWER:00/status 1 > /sys/bus/acpi/devices/LNXPOWER:01/status 1 > /sys/bus/acpi/devices/LNXPOWER:02/status 1 > /sys/bus/acpi/devices/LNXPOWER:03/status 1 > /sys/bus/acpi/devices/LNXPOWER:04/status 1 > /sys/bus/acpi/devices/LNXPOWER:05/status 1 > /sys/bus/acpi/devices/LNXPOWER:06/status 1 > /sys/bus/acpi/devices/LNXPOWER:07/status 1 > /sys/bus/acpi/devices/LNXPOWER:08/status 1 > /sys/bus/acpi/devices/LNXPOWER:09/status 1 > /sys/bus/acpi/devices/LNXPOWER:0a/status 1 Hi Pierre! I`m sorry, my script alsa-info.sh not contain getting information about ACPI ( I received the necessary data manually: $ for i in /sys/bus/acpi/devices/*; do > if [ -f "$i/status" ]; then > echo "$i `cat $i/status`" > fi > done /sys/bus/acpi/devices/10EC5640:00 0 /sys/bus/acpi/devices/10EC5645:00 0 /sys/bus/acpi/devices/80860F14:00 15 /sys/bus/acpi/devices/80860F14:01 15 /sys/bus/acpi/devices/80860F14:02 15 /sys/bus/acpi/devices/80862286:00 0 /sys/bus/acpi/devices/80862288:00 0 /sys/bus/acpi/devices/80862289:00 0 /sys/bus/acpi/devices/8086228A:00 15 /sys/bus/acpi/devices/8086228A:01 15 /sys/bus/acpi/devices/8086228E:00 15 /sys/bus/acpi/devices/8086228E:01 15 /sys/bus/acpi/devices/8086228E:02 15 /sys/bus/acpi/devices/8086229C:00 0 /sys/bus/acpi/devices/808622A8:00 15 /sys/bus/acpi/devices/808622C0:00 0 /sys/bus/acpi/devices/808622C1:00 15 /sys/bus/acpi/devices/808622C1:01 15 /sys/bus/acpi/devices/808622C1:02 15 /sys/bus/acpi/devices/808622C1:03 15 /sys/bus/acpi/devices/808622C1:04 15 /sys/bus/acpi/devices/808622C1:05 15 /sys/bus/acpi/devices/808622C1:06 15 /sys/bus/acpi/devices/808622D8:00 0 /sys/bus/acpi/devices/ACPI0003:00 15 /sys/bus/acpi/devices/ACPI0011:00 15 /sys/bus/acpi/devices/ADMA22A8:00 0 /sys/bus/acpi/devices/AK009911:00 0 /sys/bus/acpi/devices/AMCR22A8:00 0 /sys/bus/acpi/devices/AUTH2750:00 0 /sys/bus/acpi/devices/BCM2E3A:00 0 /sys/bus/acpi/devices/BCM2E64:00 0 /sys/bus/acpi/devices/BCM2E7B:00 0 /sys/bus/acpi/devices/BCM43241:00 0 /sys/bus/acpi/devices/BCM4356:00 0 /sys/bus/acpi/devices/BCM47521:00 0 /sys/bus/acpi/devices/BCM4752:00 0 /sys/bus/acpi/devices/BMG0160:00 0 /sys/bus/acpi/devices/DMY0001:00 0 /sys/bus/acpi/devices/ESSX8316:00 15 /sys/bus/acpi/devices/FUSB0300:00 0 /sys/bus/acpi/devices/GPTC0001:00 0 /sys/bus/acpi/devices/GSL1680:00 0 /sys/bus/acpi/devices/HAD022A8:00 0 /sys/bus/acpi/devices/HIMX5040:00 0 /sys/bus/acpi/devices/IMPJ0003:00 0 /sys/bus/acpi/devices/IMPJ0003:01 0 /sys/bus/acpi/devices/INT0002:00 0 /sys/bus/acpi/devices/INT0310:00 0 /sys/bus/acpi/devices/INT339A:00 0 /sys/bus/acpi/devices/INT33A2:00 0 /sys/bus/acpi/devices/INT33A4:00 15 /sys/bus/acpi/devices/INT33BB:00 0 /sys/bus/acpi/devices/INT33BE:00 0 /sys/bus/acpi/devices/INT33CF:00 0 /sys/bus/acpi/devices/INT33D5:00 15 /sys/bus/acpi/devices/INT33F4:00 15 /sys/bus/acpi/devices/INT33F5:00 0 /sys/bus/acpi/devices/INT33FB:00 0 /sys/bus/acpi/devices/INT33FD:00 0 /sys/bus/acpi/devices/INT33FE:00 0 /sys/bus/acpi/devices/INT33FE:01 0 /sys/bus/acpi/devices/INT33FE:02 0 /sys/bus/acpi/devices/INT33FF:00 15 /sys/bus/acpi/devices/INT33FF:01 15 /sys/bus/acpi/devices/INT33FF:02 15 /sys/bus/acpi/devices/INT33FF:03 15 /sys/bus/acpi/devices/INT33FF:04 15 /sys/bus/acpi/devices/INT3400:00 15 /sys/bus/acpi/devices/INT3403:00 15 /sys/bus/acpi/devices/INT3403:01 0 /sys/bus/acpi/devices/INT3403:02 0 /sys/bus/acpi/devices/INT3403:03 0 /sys/bus/acpi/devices/INT3403:04 15 /sys/bus/acpi/devices/INT3406:00 15 /sys/bus/acpi/devices/INT3407:00 0 /sys/bus/acpi/devices/INT3408:00 0 /sys/bus/acpi/devices/INT3409:00 0 /sys/bus/acpi/devices/INT3409:01 0 /sys/bus/acpi/devices/INT3477:00 0 /sys/bus/acpi/devices/INT3477:01 0 /sys/bus/acpi/devices/INT3496:00 0 /sys/bus/acpi/devices/INT34D0:00 0 /sys/bus/acpi/devices/INT34D3:00 0 /sys/bus/acpi/devices/INT8260:00 0 /sys/bus/acpi/devices/INTA4321:00 0 /sys/bus/acpi/devices/INTA4322:00 0 /sys/bus/acpi/devices/INTCF1C:00 0 /sys/bus/acpi/devices/INTCFD9:00 0 /sys/bus/acpi/devices/INTL9C60:00 15 /sys/bus/acpi/devices/INTL9C60:01 15 /sys/bus/acpi/devices/KXTJ1009:00 0 /sys/bus/acpi/devices/LNXPOWER:00 0 /sys/bus/acpi/devices/LNXPOWER:01 0 /sys/bus/acpi/devices/LNXPOWER:02 15 /sys/bus/acpi/devices/LNXPOWER:03 0 /sys/bus/acpi/devices/LNXPOWER:04 0 /sys/bus/acpi/devices/LNXPOWER:05 0 /sys/bus/acpi/devices/LNXPOWER:06 0 /sys/bus/acpi/devices/LNXPOWER:07 0 /sys/bus/acpi/devices/LNXPOWER:08 0 /sys/bus/acpi/devices/LNXPOWER:09 2 /sys/bus/acpi/devices/LNXPOWER:0a 2 /sys/bus/acpi/devices/LNXPOWER:0b 0 /sys/bus/acpi/devices/LNXPOWER:0c 0 /sys/bus/acpi/devices/LNXPOWER:0d 0 /sys/bus/acpi/devices/LNXPOWER:0e 0 /sys/bus/acpi/devices/LNXPOWER:0f 2 /sys/bus/acpi/devices/LNXPOWER:10 2 /sys/bus/acpi/devices/LNXPOWER:11 2 /sys/bus/acpi/devices/LNXPOWER:12 2 /sys/bus/acpi/devices/LNXPOWER:13 2 /sys/bus/acpi/devices/LNXPOWER:14 2 /sys/bus/acpi/devices/LNXPOWER:15 2 /sys/bus/acpi/devices/LNXPOWER:16 0 /sys/bus/acpi/devices/LNXPOWER:17 0 /sys/bus/acpi/devices/LNXPOWER:18 0 /sys/bus/acpi/devices/LNXPOWER:19 0 /sys/bus/acpi/devices/LNXPOWER:1a 0 /sys/bus/acpi/devices/LNXPOWER:1b 0 /sys/bus/acpi/devices/LNXPOWER:1c 0 /sys/bus/acpi/devices/LNXPOWER:1d 0 /sys/bus/acpi/devices/LNXPOWER:1e 0 /sys/bus/acpi/devices/LNXPOWER:1f 0 /sys/bus/acpi/devices/LNXPOWER:20 0 /sys/bus/acpi/devices/LNXPOWER:21 0 /sys/bus/acpi/devices/LNXPOWER:22 0 /sys/bus/acpi/devices/LNXPOWER:23 0 /sys/bus/acpi/devices/LNXPOWER:24 0 /sys/bus/acpi/devices/LNXPOWER:25 0 /sys/bus/acpi/devices/LNXPOWER:26 0 /sys/bus/acpi/devices/LNXPOWER:27 0 /sys/bus/acpi/devices/LNXPOWER:28 0 /sys/bus/acpi/devices/LNXPOWER:29 0 /sys/bus/acpi/devices/LNXPOWER:2a 0 /sys/bus/acpi/devices/LTER0303:00 0 /sys/bus/acpi/devices/MAX17047:00 0 /sys/bus/acpi/devices/MCD0001:00 0 /sys/bus/acpi/devices/MCD0001:01 0 /sys/bus/acpi/devices/MCD0001:02 0 /sys/bus/acpi/devices/MCD0001:03 0 /sys/bus/acpi/devices/MCD0001:04 0 /sys/bus/acpi/devices/MCD0001:05 0 /sys/bus/acpi/devices/MSSL1680:00 0 /sys/bus/acpi/devices/OBDA8723:00 15 /sys/bus/acpi/devices/OVTI2680:00 0 /sys/bus/acpi/devices/PI330532:00 0 /sys/bus/acpi/devices/PNP0103:00 15 /sys/bus/acpi/devices/PNP0501:00 15 /sys/bus/acpi/devices/PNP0C0A:00 0 /sys/bus/acpi/devices/PNP0C0A:01 0 /sys/bus/acpi/devices/PNP0C0F:00 9 /sys/bus/acpi/devices/PNP0C0F:01 9 /sys/bus/acpi/devices/PNP0C0F:02 9 /sys/bus/acpi/devices/PNP0C0F:03 9 /sys/bus/acpi/devices/PNP0C0F:04 9 /sys/bus/acpi/devices/PNP0C0F:05 9 /sys/bus/acpi/devices/PNP0C0F:06 9 /sys/bus/acpi/devices/PNP0C0F:07 9 /sys/bus/acpi/devices/PNP0C31:00 0 /sys/bus/acpi/devices/SMB0349:00 0 /sys/bus/acpi/devices/TBQ24296:00 0 /sys/bus/acpi/devices/TIMC22A8:00 0 /sys/bus/acpi/devices/TXN24292:00 0 /sys/bus/acpi/devices/TXN27501:00 0 /sys/bus/acpi/devices/USBC000:00 0 /sys/bus/acpi/devices/VIBR22A8:00 0 /sys/bus/acpi/devices/device:09 0 /sys/bus/acpi/devices/device:0c 15 /sys/bus/acpi/devices/device:1d 15 /sys/bus/acpi/devices/device:23 0 /sys/bus/acpi/devices/device:24 0 /sys/bus/acpi/devices/device:26 0 /sys/bus/acpi/devices/device:2c 0 /sys/bus/acpi/devices/device:2e 0 /sys/bus/acpi/devices/device:30 0 /sys/bus/acpi/devices/device:32 0 /sys/bus/acpi/devices/device:48 15 /sys/bus/acpi/devices/device:4a 0 /sys/bus/acpi/devices/device:4c 0 /sys/bus/acpi/devices/device:4d 0 /sys/bus/acpi/devices/device:4e 15 /sys/bus/acpi/devices/device:4f 15 /sys/bus/acpi/devices/device:50 15 Also publish previous data: upload=true&script=true&cardinfo= !!################################ !!ALSA Information Script v 0.4.64 !!################################ !!Script ran on: Sat Nov 17 17:21:42 UTC 2018 !!Linux Distribution !!------------------ !!DMI Information !!--------------- Manufacturer: OEM Product Name: OEM Product Version: Default string Firmware Version: 5.11 !!Kernel Information !!------------------ Kernel release: 4.19.2-fastsys Operating System: GNU/Linux Architecture: x86_64 Processor: unknown SMP Enabled: YES !!ALSA Version !!------------ Driver version: k4.19.2-fastsys Library version: Utilities version: 1.0.26.4.g7b14c !!Loaded ALSA modules !!------------------- !!Sound Servers on this system !!---------------------------- Pulseaudio: Installed - Yes () Running - No ESound Daemon: Installed - Yes () Running - No aRts: Installed - Yes () Running - No Jack: Installed - Yes () Running - No RoarAudio: Installed - Yes () Running - No No sound servers found. !!Soundcards recognised by ALSA !!----------------------------- --- no soundcards --- !!PCI Soundcards installed in the system !!-------------------------------------- !!Advanced information - PCI Vendor/Device/Subsystem ID's !!------------------------------------------------------- !!Loaded sound module options !!--------------------------- !!ALSA Device nodes !!----------------- crw------- 1 root root 116, 33 Nov 17 19:45 /dev/snd/timer !!Aplay/Arecord output !!-------------------- APLAY aplay: device_list:267: no soundcards found... ARECORD arecord: device_list:267: no soundcards found... !!Amixer output !!------------- !!Alsactl output !!-------------- --startcollapse-- --endcollapse-- !!All Loaded Modules !!------------------ snd_soc_sst_byt_cht_es8316 snd_soc_es8316 snd_intel_sst_acpi snd_soc_acpi_intel_match snd_soc_acpi snd_intel_sst_core snd_soc_sst_atom_hifi2_platform snd_soc_core ac97_bus snd_compress snd_pcm_dmaengine snd_pcm snd_timer snd r8723bs r8152 mii usbtouchscreen hid_generic intelfb i915 i2c_algo_bit intel_gtt drm_kms_helper sysimgblt sysfillrect syscopyarea fb_sys_fops drm agpgart !!ALSA/HDA dmesg !!-------------- [ 0.098676] ACPI: Added _OSI(Linux-Dell-Video) [ 0.098676] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio) [ 0.146139] ACPI: 8 ACPI AML tables successfully acquired and loaded -- [ 17.543203] intel_sst_acpi 808622A8:00: Got drv data max stream 25 [ 17.579608] bytcht_es8316 bytcht_es8316: ASoC: CODEC DAI snd-soc-dummy-dai not registered [ 17.579618] bytcht_es8316 bytcht_es8316: snd_soc_register_card failed -517 [ 17.943530] random: sqlite3: uninitialized urandom read (256 bytes read) [ 0.000000] Linux version 4.19.2-fastsys (root@hash-virtual-machine_x64) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.10)) #41 SMP Sat Nov 17 19:22:25 +04 2018 [ 0.000000] Command line: BOOT_IMAGE=/bzImage video=efifb:1024x768-32,mtrr:3,ywrap quiet console=off [ 0.000000] KERNEL supported cpus: [ 0.000000] Intel GenuineIntel [ 0.000000] AMD AuthenticAMD [ 0.000000] Centaur CentaurHauls [ 0.000000] x86/fpu: x87 FPU will use FXSAVE [ 0.000000] BIOS-provided physical RAM map: [ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000008efff] usable [ 0.000000] BIOS-e820: [mem 0x000000000008f000-0x000000000008ffff] ACPI NVS [ 0.000000] BIOS-e820: [mem 0x0000000000090000-0x000000000009dfff] usable [ 0.000000] BIOS-e820: [mem 0x000000000009e000-0x000000000009ffff] reserved [ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000001fffffff] usable [ 0.000000] BIOS-e820: [mem 0x0000000020000000-0x00000000201fffff] reserved [ 0.000000] BIOS-e820: [mem 0x0000000020200000-0x000000007b121fff] usable [ 0.000000] BIOS-e820: [mem 0x000000007b122000-0x000000007b151fff] reserved [ 0.000000] BIOS-e820: [mem 0x000000007b152000-0x000000007b270fff] usable [ 0.000000] BIOS-e820: [mem 0x000000007b271000-0x000000007b757fff] ACPI NVS [ 0.000000] BIOS-e820: [mem 0x000000007b758000-0x000000007ba13fff] reserved [ 0.000000] BIOS-e820: [mem 0x000000007ba14000-0x000000007ba6dfff] type 20 [ 0.000000] BIOS-e820: [mem 0x000000007ba6e000-0x000000007bffffff] usable [ 0.000000] BIOS-e820: [mem 0x00000000e0000000-0x00000000e3ffffff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000fea00000-0x00000000feafffff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000fed01000-0x00000000fed01fff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000fed03000-0x00000000fed03fff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000fed06000-0x00000000fed06fff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000fed08000-0x00000000fed09fff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1cfff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000fed80000-0x00000000fedbffff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000ffc00000-0x00000000ffffffff] reserved [ 0.000000] NX (Execute Disable) protection: active [ 0.000000] efi: EFI v2.40 by American Megatrends [ 0.000000] efi: ESRT=0x7b150000 ACPI=0x7b2b5000 ACPI 2.0=0x7b2b5000 SMBIOS=0x7b914000 SMBIOS 3.0=0x7b913000 [ 0.000000] SMBIOS 3.0.0 present. [ 0.000000] DMI: OEM OEM/OEM, BIOS 5.11 01/09/2017 [ 0.000000] tsc: Detected 1440.000 MHz processor [ 0.000052] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved [ 0.000060] e820: remove [mem 0x000a0000-0x000fffff] usable [ 0.000084] last_pfn = 0x7c000 max_arch_pfn = 0x400000000 [ 0.000089] MTRR default type: uncachable [ 0.000090] MTRR fixed ranges enabled: [ 0.000093] 00000-9FFFF write-back [ 0.000096] A0000-FFFFF write-protect [ 0.000097] MTRR variable ranges enabled: [ 0.000102] 0 base 000000000 mask F80000000 write-back [ 0.000104] 1 base 07E000000 mask FFE000000 uncachable [ 0.000107] 2 base 07D000000 mask FFF000000 uncachable [ 0.000109] 3 base 07C800000 mask FFF800000 uncachable [ 0.000111] 4 base 07C400000 mask FFFC00000 uncachable [ 0.000113] 5 disabled [ 0.000114] 6 disabled [ 0.000115] 7 disabled [ 0.000415] x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT [ 0.008479] esrt: ESRT header is not in the memory map. [ 0.008506] Scanning 1 areas for low memory corruption [ 0.008514] Base memory trampoline at [(____ptrval____)] 98000 size 24576 [ 0.008524] BRK [0x1ee01000, 0x1ee01fff] PGTABLE [ 0.008530] BRK [0x1ee02000, 0x1ee02fff] PGTABLE [ 0.008532] BRK [0x1ee03000, 0x1ee03fff] PGTABLE [ 0.008639] BRK [0x1ee04000, 0x1ee04fff] PGTABLE [ 0.008648] BRK [0x1ee05000, 0x1ee05fff] PGTABLE [ 0.009079] BRK [0x1ee06000, 0x1ee06fff] PGTABLE [ 0.009171] BRK [0x1ee07000, 0x1ee07fff] PGTABLE [ 0.009342] BRK [0x1ee08000, 0x1ee08fff] PGTABLE [ 0.009449] Secure boot could not be determined [ 0.009458] ACPI: Early table checksum verification disabled [ 0.009465] ACPI: RSDP 0x000000007B2B5000 000024 (v02 ALASKA) [ 0.009474] ACPI: XSDT 0x000000007B2B50A0 0000BC (v01 ALASKA A M I 01072009 AMI 00010013) [ 0.009488] ACPI: FACP 0x000000007B2D3AF0 00010C (v05 ALASKA A M I 01072009 AMI 00010013) [ 0.009502] ACPI: DSDT 0x000000007B2B51F0 01E8FE (v02 ALASKA A M I 01072009 INTL 20120913) [ 0.009511] ACPI: FACS 0x000000007B757F80 000040 [ 0.009518] ACPI: APIC 0x000000007B2D3C00 000084 (v03 ALASKA A M I 01072009 AMI 00010013) [ 0.009525] ACPI: FPDT 0x000000007B2D3C88 000044 (v01 ALASKA A M I 01072009 AMI 00010013) [ 0.009533] ACPI: FIDT 0x000000007B2D3CD0 00009C (v01 ALASKA A M I 01072009 AMI 00010013) [ 0.009541] ACPI: MCFG 0x000000007B2D3D70 00003C (v01 ALASKA A M I 01072009 MSFT 00000097) [ 0.009548] ACPI: SSDT 0x000000007B2D3DB0 004174 (v01 DptfTb DptfTab 00001000 INTL 20120913) [ 0.009556] ACPI: SSDT 0x000000007B2D7F28 000654 (v01 CpuDpf CpuDptf 00001000 INTL 20120913) [ 0.009564] ACPI: SSDT 0x000000007B2D8580 000058 (v01 LowPM LowPwrM 00001000 INTL 20120913) [ 0.009572] ACPI: UEFI 0x000000007B2D85D8 000042 (v01 ALASKA A M I 00000000 00000000) [ 0.009580] ACPI: SSDT 0x000000007B2D8620 000269 (v01 UsbCTb UsbCTab 00001000 INTL 20120913) [ 0.009588] ACPI: HPET 0x000000007B2D8890 000038 (v01 ALASKA A M I 01072009 AMI. 00000005) [ 0.009595] ACPI: SSDT 0x000000007B2D88C8 000763 (v01 PmRef CpuPm 00003000 INTL 20120913) [ 0.009604] ACPI: SSDT 0x000000007B2D9030 000290 (v01 PmRef Cpu0Tst 00003000 INTL 20120913) [ 0.009612] ACPI: SSDT 0x000000007B2D92C0 00017A (v01 PmRef ApTst 00003000 INTL 20120913) [ 0.009620] ACPI: LPIT 0x000000007B2D9440 000104 (v01 ALASKA A M I 00000005 MSFT 0100000D) [ 0.009627] ACPI: BCFG 0x000000007B2D9548 000139 (v01 INTEL BATTCONF 00000001 ACPI 00000000) [ 0.009635] ACPI: PRAM 0x000000007B2D9688 000030 (v01 00000001 00000000) [ 0.009643] ACPI: CSRT 0x000000007B2D96B8 00014C (v00 INTEL LANFORDC 00000005 MSFT 0100000D) [ 0.009650] ACPI: WDAT 0x000000007B2D9808 000104 (v01 00000000 00000000) [ 0.009667] ACPI: Local APIC address 0xfee00000 [ 0.009708] Zone ranges: [ 0.009711] DMA [mem 0x0000000000001000-0x0000000000ffffff] [ 0.009714] DMA32 [mem 0x0000000001000000-0x000000007bffffff] [ 0.009717] Normal empty [ 0.009721] Movable zone start for each node [ 0.009722] Early memory node ranges [ 0.009724] node 0: [mem 0x0000000000001000-0x000000000008efff] [ 0.009726] node 0: [mem 0x0000000000090000-0x000000000009dfff] [ 0.009728] node 0: [mem 0x0000000000100000-0x000000001fffffff] [ 0.009730] node 0: [mem 0x0000000020200000-0x000000007b121fff] [ 0.009732] node 0: [mem 0x000000007b152000-0x000000007b270fff] [ 0.009734] node 0: [mem 0x000000007ba6e000-0x000000007bffffff] [ 0.010820] Reserved but unavailable: 19089 pages [ 0.010825] Initmem setup node 0 [mem 0x0000000000001000-0x000000007bffffff] [ 0.010829] On node 0 totalpages: 505199 [ 0.010832] DMA zone: 64 pages used for memmap [ 0.010833] DMA zone: 22 pages reserved [ 0.010835] DMA zone: 3996 pages, LIFO batch:0 [ 0.011086] DMA32 zone: 7872 pages used for memmap [ 0.011088] DMA32 zone: 501203 pages, LIFO batch:63 [ 0.041586] Reserving Intel graphics memory at [mem 0x7ce00000-0x7edfffff] [ 0.041677] ACPI: PM-Timer IO Port: 0x408 [ 0.041682] ACPI: Local APIC address 0xfee00000 [ 0.041696] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) [ 0.041698] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1]) [ 0.041700] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1]) [ 0.041701] ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1]) [ 0.041721] IOAPIC[0]: apic_id 1, version 32, address 0xfec00000, GSI 0-114 [ 0.041726] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [ 0.041729] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) [ 0.041732] ACPI: IRQ0 used by override. [ 0.041736] ACPI: IRQ9 used by override. [ 0.041742] Using ACPI (MADT) for SMP configuration information [ 0.041746] ACPI: HPET id: 0x8086a201 base: 0xfed00000 [ 0.041757] smpboot: Allowing 4 CPUs, 0 hotplug CPUs [ 0.041825] PM: Registered nosave memory: [mem 0x00000000-0x00000fff] [ 0.041830] PM: Registered nosave memory: [mem 0x0008f000-0x0008ffff] [ 0.041835] PM: Registered nosave memory: [mem 0x0009e000-0x0009ffff] [ 0.041838] PM: Registered nosave memory: [mem 0x000a0000-0x000fffff] [ 0.041843] PM: Registered nosave memory: [mem 0x20000000-0x201fffff] [ 0.041848] PM: Registered nosave memory: [mem 0x7b122000-0x7b151fff] [ 0.041853] PM: Registered nosave memory: [mem 0x7b271000-0x7b757fff] [ 0.041854] PM: Registered nosave memory: [mem 0x7b758000-0x7ba13fff] [ 0.041856] PM: Registered nosave memory: [mem 0x7ba14000-0x7ba6dfff] [ 0.041860] [mem 0x7ee00000-0xdfffffff] available for PCI devices [ 0.041868] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1910969940391419 ns [ 0.041890] random: get_random_bytes called from start_kernel+0x90/0x4d4 with crng_init=0 [ 0.041909] setup_percpu: NR_CPUS:8192 nr_cpumask_bits:4 nr_cpu_ids:4 nr_node_ids:1 [ 0.042906] percpu: Embedded 43 pages/cpu @(____ptrval____) s137432 r8192 d30504 u524288 [ 0.042931] pcpu-alloc: s137432 r8192 d30504 u524288 alloc=1*2097152 [ 0.042934] pcpu-alloc: [0] 0 1 2 3 [ 0.043023] Built 1 zonelists, mobility grouping on. Total pages: 497241 [ 0.043028] Kernel command line: BOOT_IMAGE=/bzImage video=efifb:1024x768-32,mtrr:3,ywrap quiet console=off [ 0.043881] Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes) [ 0.044263] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes) [ 0.044346] Calgary: detecting Calgary via BIOS EBDA area [ 0.044349] Calgary: Unable to locate Rio Grande table in EBDA - bailing! [ 0.069831] Memory: 1907660K/2020796K available (10252K kernel code, 1933K rwdata, 3188K rodata, 16932K init, 1500K bss, 113136K reserved, 0K cma-reserved) [ 0.070155] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [ 0.070167] Kernel/User page tables isolation: enabled [ 0.070617] rcu: Hierarchical RCU implementation. [ 0.070619] rcu: RCU event tracing is enabled. [ 0.070622] rcu: RCU restricting CPUs from NR_CPUS=8192 to nr_cpu_ids=4. [ 0.070625] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4 [ 0.071078] NR_IRQS: 524544, nr_irqs: 1024, preallocated irqs: 16 [ 0.071533] Console: colour dummy device 80x25 [ 0.071546] ACPI: Core revision 20180810 [ 0.072232] clocksource: hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 133484882848 ns [ 0.072257] hpet clockevent registered [ 0.072266] APIC: Switch to symmetric I/O mode setup [ 0.074088] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=0 pin2=0 [ 0.078268] clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x14c1baf3789, max_idle_ns: 440795266465 ns [ 0.078294] Calibrating delay loop (skipped), value calculated using timer frequency.. 2880.00 BogoMIPS (lpj=1440000) [ 0.078301] pid_max: default: 32768 minimum: 301 [ 0.079088] Security Framework initialized [ 0.079146] Mount-cache hash table entries: 4096 (order: 3, 32768 bytes) [ 0.079160] Mountpoint-cache hash table entries: 4096 (order: 3, 32768 bytes) [ 0.079653] ENERGY_PERF_BIAS: Set to 'normal', was 'performance' [ 0.079655] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8) [ 0.079671] mce: CPU supports 6 MCE banks [ 0.079682] CPU0: Thermal monitoring enabled (TM1) [ 0.079689] process: using mwait in idle threads [ 0.079695] Last level iTLB entries: 4KB 48, 2MB 0, 4MB 0 [ 0.079697] Last level dTLB entries: 4KB 256, 2MB 16, 4MB 16, 1GB 0 [ 0.079701] Spectre V2 : Mitigation: Full generic retpoline [ 0.079702] Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on context switch [ 0.080083] Freeing SMP alternatives memory: 28K [ 0.083936] TSC deadline timer enabled [ 0.083944] smpboot: CPU0: Intel(R) Atom(TM) x5-Z8350 CPU @ 1.44GHz (family: 0x6, model: 0x4c, stepping: 0x4) [ 0.084272] Performance Events: PEBS fmt2+, 8-deep LBR, Silvermont events, 8-deep LBR, full-width counters, Intel PMU driver. [ 0.084272] ... version: 3 [ 0.084272] ... bit width: 40 [ 0.084272] ... generic registers: 2 [ 0.084272] ... value mask: 000000ffffffffff [ 0.084272] ... max period: 0000007fffffffff [ 0.084272] ... fixed-purpose events: 3 [ 0.084272] ... event mask: 0000000700000003 [ 0.084272] rcu: Hierarchical SRCU implementation. [ 0.084272] smp: Bringing up secondary CPUs ... [ 0.084529] x86: Booting SMP configuration: [ 0.084532] .... node #0, CPUs: #1 #2 #3 [ 0.085694] smp: Brought up 1 node, 4 CPUs [ 0.085694] smpboot: Max logical packages: 1 [ 0.085694] smpboot: Total of 4 processors activated (11520.00 BogoMIPS) [ 0.086584] devtmpfs: initialized [ 0.086683] PM: Registering ACPI NVS region [mem 0x0008f000-0x0008ffff] (4096 bytes) [ 0.087284] PM: Registering ACPI NVS region [mem 0x7b271000-0x7b757fff] (5140480 bytes) [ 0.087651] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1911260446275000 ns [ 0.087660] futex hash table entries: 1024 (order: 4, 65536 bytes) [ 0.087798] pinctrl core: initialized pinctrl subsystem [ 0.087731] kworker/u8:0 (32) used greatest stack depth: 14568 bytes left [ 0.087857] kworker/u8:0 (33) used greatest stack depth: 14016 bytes left [ 0.088372] NET: Registered protocol family 16 [ 0.089099] cpuidle: using governor menu [ 0.089213] ACPI: bus type PCI registered [ 0.089397] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000) [ 0.089405] PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in E820 [ 0.089410] PCI: MMCONFIG for 0000 [bus00-3f] at [mem 0xe0000000-0xe3ffffff] (base 0xe0000000) (size reduced!) [ 0.089432] PCI: Using configuration type 1 for base access [ 0.097723] kworker/u8:3 (95) used greatest stack depth: 13840 bytes left [ 0.098676] ACPI: Added _OSI(Module Device) [ 0.098676] ACPI: Added _OSI(Processor Device) [ 0.098676] ACPI: Added _OSI(3.0 _SCP Extensions) [ 0.098676] ACPI: Added _OSI(Processor Aggregator Device) [ 0.098676] ACPI: Added _OSI(Linux-Dell-Video) [ 0.098676] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio) [ 0.146139] ACPI: 8 ACPI AML tables successfully acquired and loaded [ 0.165399] ACPI: Dynamic OEM Table Load: [ 0.165418] ACPI: SSDT 0xFFFF985FFA5B5800 00059C (v01 PmRef Cpu0Ist 00003000 INTL 20120913) [ 0.166611] ACPI: Dynamic OEM Table Load: [ 0.166625] ACPI: SSDT 0xFFFF985FF672A800 0003A5 (v01 PmRef Cpu0Cst 00003001 INTL 20120913) [ 0.167987] ACPI: Dynamic OEM Table Load: [ 0.168000] ACPI: SSDT 0xFFFF985FFA619200 00015F (v01 PmRef ApIst 00003000 INTL 20120913) [ 0.168752] ACPI: Dynamic OEM Table Load: [ 0.168764] ACPI: SSDT 0xFFFF985FFA0E10C0 00008D (v01 PmRef ApCst 00003000 INTL 20120913) [ 0.173749] ACPI: Interpreter enabled [ 0.173800] ACPI: (supports S0 S4 S5) [ 0.173803] ACPI: Using IOAPIC for interrupt routing [ 0.173896] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug [ 0.177304] ACPI: Power Resource [P06X] (off) [ 0.179458] ACPI: Power Resource [ID3C] (off) [ 0.182502] ACPI: Power Resource [USBC] (on) [ 0.183631] ACPI: Power Resource [WWPR] (off) [ 0.184343] ACPI: Power Resource [WWPR] (off) [ 0.185503] ACPI: Power Resource [WWPR] (off) [ 0.186192] ACPI: Power Resource [WWPR] (off) [ 0.186899] ACPI: Power Resource [WWPR] (off) [ 0.187668] ACPI: Power Resource [WWPR] (off) [ 0.200554] ACPI: Power Resource [CLK2] (on) [ 0.200677] ACPI: Power Resource [CLK4] (on) [ 0.200792] ACPI: Power Resource [P28P] (off) [ 0.200908] ACPI: Power Resource [P18P] (off) [ 0.201022] ACPI: Power Resource [P12P] (off) [ 0.201150] ACPI: Power Resource [P16P] (off) [ 0.204820] ACPI: Power Resource [CLK3] (on) [ 0.204939] ACPI: Power Resource [CLK4] (on) [ 0.213171] ACPI: Power Resource [CLK2] (on) [ 0.213300] ACPI: Power Resource [CLK1] (on) [ 0.215635] ACPI: Power Resource [CLK0] (on) [ 0.215759] ACPI: Power Resource [CLK1] (on) [ 0.217382] ACPI: Power Resource [CLK5] (off) [ 0.218167] ACPI: Power Resource [P33P] (off) [ 0.218287] ACPI: Power Resource [P65P] (off) [ 0.232831] ACPI: Power Resource [P28X] (off) [ 0.232957] ACPI: Power Resource [P18X] (off) [ 0.233070] ACPI: Power Resource [P12X] (off) [ 0.233189] ACPI: Power Resource [P28P] (off) [ 0.233317] ACPI: Power Resource [P18P] (off) [ 0.233433] ACPI: Power Resource [P12P] (off) [ 0.233546] ACPI: Power Resource [P19X] (off) [ 0.233680] ACPI: Power Resource [P12A] (off) [ 0.233798] ACPI: Power Resource [P28T] (off) [ 0.233917] ACPI: Power Resource [P18D] (off) [ 0.234029] ACPI: Power Resource [P18T] (off) [ 0.234147] ACPI: Power Resource [P3P3] (off) [ 0.234261] ACPI: Power Resource [P12T] (off) [ 0.234385] ACPI: Power Resource [P28W] (off) [ 0.234500] ACPI: Power Resource [P18W] (off) [ 0.234617] ACPI: Power Resource [P12W] (off) [ 0.234737] ACPI: Power Resource [P33W] (off) [ 0.234855] ACPI: Power Resource [P33X] (off) [ 0.234971] ACPI: Power Resource [P4BW] (off) [ 0.242817] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff]) [ 0.242831] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] [ 0.243420] acpi PNP0A08:00: _OSC: OS now controls [PME AER PCIeCapability LTR] [ 0.243430] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-3f] only partially covers this bridge [ 0.243911] PCI host bridge to bus 0000:00 [ 0.243918] pci_bus 0000:00: root bus resource [io 0x0070-0x0077] [ 0.243923] pci_bus 0000:00: root bus resource [io 0x0000-0x006f window] [ 0.243926] pci_bus 0000:00: root bus resource [io 0x0078-0x0cf7 window] [ 0.243930] pci_bus 0000:00: root bus resource [io 0x0d00-0xffff window] [ 0.243934] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window] [ 0.243937] pci_bus 0000:00: root bus resource [mem 0x000c0000-0x000dffff window] [ 0.243941] pci_bus 0000:00: root bus resource [mem 0x000e0000-0x000fffff window] [ 0.243945] pci_bus 0000:00: root bus resource [mem 0x20000000-0x201fffff window] [ 0.243948] pci_bus 0000:00: root bus resource [mem 0x7ce00001-0x7ee00000 window] [ 0.243952] pci_bus 0000:00: root bus resource [mem 0x80000000-0xdfffffff window] [ 0.243956] pci_bus 0000:00: root bus resource [bus 00-ff] [ 0.243974] pci 0000:00:00.0: [8086:2280] type 00 class 0x060000 [ 0.244662] pci 0000:00:02.0: [8086:22b0] type 00 class 0x030000 [ 0.244694] pci 0000:00:02.0: reg 0x10: [mem 0x90000000-0x90ffffff 64bit] [ 0.244710] pci 0000:00:02.0: reg 0x18: [mem 0x80000000-0x8fffffff 64bit pref] [ 0.244721] pci 0000:00:02.0: reg 0x20: [io 0xf000-0xf03f] [ 0.244756] pci 0000:00:02.0: BAR 2: assigned to efifb [ 0.245121] pci 0000:00:0b.0: [8086:22dc] type 00 class 0x118000 [ 0.245152] pci 0000:00:0b.0: reg 0x10: [mem 0x9143b000-0x9143bfff 64bit] [ 0.245599] pci 0000:00:14.0: [8086:22b5] type 00 class 0x0c0330 [ 0.245641] pci 0000:00:14.0: reg 0x10: [mem 0x91400000-0x9140ffff 64bit] [ 0.245752] pci 0000:00:14.0: PME# supported from D3hot D3cold [ 0.246139] pci 0000:00:1a.0: [8086:2298] type 00 class 0x108000 [ 0.246171] pci 0000:00:1a.0: reg 0x10: [mem 0x91300000-0x913fffff] [ 0.246185] pci 0000:00:1a.0: reg 0x14: [mem 0x91200000-0x912fffff] [ 0.246289] pci 0000:00:1a.0: PME# supported from D0 D3hot [ 0.246696] pci 0000:00:1f.0: [8086:229c] type 00 class 0x060100 [ 0.247142] pci_bus 0000:00: on NUMA node 0 [ 0.259462] platform 80860F14:02: Linked as a consumer to 808622C1:06 [ 0.261227] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 10 11 12 14 15) *0, disabled. [ 0.261414] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 10 11 12 14 15) *0, disabled. [ 0.261597] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 10 11 12 14 15) *0, disabled. [ 0.261776] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 11 12 14 15) *0, disabled. [ 0.261957] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 10 11 12 14 15) *0, disabled. [ 0.262136] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 10 11 12 14 15) *0, disabled. [ 0.262322] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 10 11 12 14 15) *0, disabled. [ 0.262504] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 10 11 12 14 15) *0, disabled. [ 0.266797] pci 0000:00:02.0: vgaarb: setting as boot VGA device [ 0.266797] pci 0000:00:02.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none [ 0.266797] pci 0000:00:02.0: vgaarb: bridge control possible [ 0.266797] vgaarb: loaded [ 0.266797] SCSI subsystem initialized [ 0.267378] libata version 3.00 loaded. [ 0.267585] ACPI: bus type USB registered [ 0.267672] usbcore: registered new interface driver usbfs [ 0.267703] usbcore: registered new interface driver hub [ 0.267764] usbcore: registered new device driver usb [ 0.267819] videodev: Linux video capture interface: v2.00 [ 0.267845] pps_core: LinuxPPS API ver. 1 registered [ 0.267847] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it> [ 0.267858] PTP clock support registered [ 0.267986] Registered efivars operations [ 0.271442] PCI: Using ACPI for IRQ routing [ 0.274813] PCI: pci_cache_line_size set to 64 bytes [ 0.274857] Expanded resource Reserved due to conflict with PCI Bus 0000:00 [ 0.274864] e820: reserve RAM buffer [mem 0x0008f000-0x0008ffff] [ 0.274869] e820: reserve RAM buffer [mem 0x0009e000-0x0009ffff] [ 0.274871] e820: reserve RAM buffer [mem 0x7b122000-0x7bffffff] [ 0.274874] e820: reserve RAM buffer [mem 0x7b271000-0x7bffffff] [ 0.275392] clocksource: Switched to clocksource tsc-early [ 0.299988] pnp: PnP ACPI init [ 0.300317] system 00:00: [io 0x0680-0x069f] has been reserved [ 0.300323] system 00:00: [io 0x0400-0x047f] has been reserved [ 0.300327] system 00:00: [io 0x0500-0x05fe] has been reserved [ 0.300353] system 00:00: Plug and Play ACPI device, IDs PNP0c02 (active) [ 0.300573] pnp 00:01: Plug and Play ACPI device, IDs PNP0501 (active) [ 0.307533] system 00:02: [mem 0x91439000-0x91439fff] has been reserved [ 0.307539] system 00:02: [mem 0x91437000-0x91437fff] has been reserved [ 0.307543] system 00:02: [mem 0x91435000-0x91435fff] has been reserved [ 0.307547] system 00:02: [mem 0x91424000-0x91424fff] has been reserved [ 0.307555] system 00:02: [mem 0x91422000-0x91422fff] has been reserved [ 0.307559] system 00:02: [mem 0x91420000-0x91420fff] has been reserved [ 0.307564] system 00:02: [mem 0x9141e000-0x9141efff] has been reserved [ 0.307568] system 00:02: [mem 0x9141c000-0x9141cfff] has been reserved [ 0.307572] system 00:02: [mem 0x9141a000-0x9141afff] has been reserved [ 0.307576] system 00:02: [mem 0x91418000-0x91418fff] has been reserved [ 0.307580] system 00:02: [mem 0x91433000-0x91433fff] has been reserved [ 0.307585] system 00:02: [mem 0x91431000-0x91431fff] has been reserved [ 0.307589] system 00:02: [mem 0x9142f000-0x9142ffff] has been reserved [ 0.307594] system 00:02: [mem 0x9142d000-0x9142dfff] has been reserved [ 0.307598] system 00:02: [mem 0x9142b000-0x9142bfff] has been reserved [ 0.307602] system 00:02: [mem 0x91429000-0x91429fff] has been reserved [ 0.307607] system 00:02: [mem 0x91427000-0x91427fff] has been reserved [ 0.307611] system 00:02: [mem 0x91425000-0x91425fff] has been reserved [ 0.307633] system 00:02: Plug and Play ACPI device, IDs PNP0c02 (active) [ 0.307832] system 00:03: [mem 0xe0000000-0xefffffff] could not be reserved [ 0.307838] system 00:03: [mem 0xfea00000-0xfeafffff] has been reserved [ 0.307842] system 00:03: [mem 0xfed01000-0xfed01fff] has been reserved [ 0.307846] system 00:03: [mem 0xfed03000-0xfed03fff] has been reserved [ 0.307850] system 00:03: [mem 0xfed06000-0xfed06fff] has been reserved [ 0.307855] system 00:03: [mem 0xfed08000-0xfed09fff] has been reserved [ 0.307859] system 00:03: [mem 0xfed80000-0xfedbffff] could not be reserved [ 0.307864] system 00:03: [mem 0xfed1c000-0xfed1cfff] has been reserved [ 0.307868] system 00:03: [mem 0xfee00000-0xfeefffff] could not be reserved [ 0.307888] system 00:03: Plug and Play ACPI device, IDs PNP0c02 (active) [ 0.308326] pnp 00:04: Plug and Play ACPI device, IDs PNP0b00 (active) [ 0.309998] pnp: PnP ACPI: found 5 devices [ 0.319588] clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns [ 0.319612] pci_bus 0000:00: resource 4 [io 0x0070-0x0077] [ 0.319617] pci_bus 0000:00: resource 5 [io 0x0000-0x006f window] [ 0.319621] pci_bus 0000:00: resource 6 [io 0x0078-0x0cf7 window] [ 0.319625] pci_bus 0000:00: resource 7 [io 0x0d00-0xffff window] [ 0.319630] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff window] [ 0.319634] pci_bus 0000:00: resource 9 [mem 0x000c0000-0x000dffff window] [ 0.319639] pci_bus 0000:00: resource 10 [mem 0x000e0000-0x000fffff window] [ 0.319643] pci_bus 0000:00: resource 11 [mem 0x20000000-0x201fffff window] [ 0.319647] pci_bus 0000:00: resource 12 [mem 0x7ce00001-0x7ee00000 window] [ 0.319651] pci_bus 0000:00: resource 13 [mem 0x80000000-0xdfffffff window] [ 0.320169] NET: Registered protocol family 2 [ 0.320525] tcp_listen_portaddr_hash hash table entries: 1024 (order: 2, 16384 bytes) [ 0.320544] TCP established hash table entries: 16384 (order: 5, 131072 bytes) [ 0.320610] TCP bind hash table entries: 16384 (order: 6, 262144 bytes) [ 0.320717] TCP: Hash tables configured (established 16384 bind 16384) [ 0.320798] UDP hash table entries: 1024 (order: 3, 32768 bytes) [ 0.320823] UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes) [ 0.320927] NET: Registered protocol family 1 [ 0.321252] pci 0000:00:02.0: Video device with shadowed ROM at [mem 0x000c0000-0x000dffff] [ 0.321802] PCI: CLS 64 bytes, default 64 [ 3.208039] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x14c1baf3789, max_idle_ns: 440795266465 ns [ 3.208073] clocksource: Switched to clocksource tsc [ 3.209643] Scanning for low memory corruption every 60 seconds [ 3.211261] Initialise system trusted keyrings [ 3.212320] workingset: timestamp_bits=46 max_order=19 bucket_order=0 [ 3.215237] mdev (820) used greatest stack depth: 13752 bytes left [ 3.221185] squashfs: version 4.0 (2009/01/31) Phillip Lougher [ 3.221298] ntfs: driver 2.1.32 [Flags: R/W]. [ 3.222180] fuse init (API version 7.27) [ 3.234561] Key type asymmetric registered [ 3.234565] Asymmetric key parser 'x509' registered [ 3.234610] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251) [ 3.234613] io scheduler noop registered [ 3.234616] io scheduler deadline registered [ 3.234711] io scheduler cfq registered (default) [ 3.234714] io scheduler mq-deadline registered [ 3.234716] io scheduler kyber registered [ 3.238553] uvesafb: Getting VBE info block failed (eax=0x4f00, err=0) [ 3.238561] uvesafb: vbe_init() failed with -22 [ 3.238581] uvesafb: probe of uvesafb.0 failed with error -22 [ 3.238702] efifb: probing for efifb [ 3.238739] efifb: framebuffer at 0x80000000, using 8128k, total 8128k [ 3.238742] efifb: mode is 1920x1080x32, linelength=7680, pages=1 [ 3.238743] efifb: scrolling: redraw [ 3.238747] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0 [ 3.257037] Console: switching to colour frame buffer device 240x67 [ 3.265830] fb0: EFI VGA frame buffer device [ 3.265979] intel_idle: MWAIT substates: 0x33000020 [ 3.265981] intel_idle: v0.4.1 model 0x4C [ 3.266525] intel_idle: lapic_timer_reliable_states 0xffffffff [ 3.266640] ACPI: AC: found native INT33F4 PMIC, not loading [ 3.266853] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0 [ 3.266877] ACPI: Power Button [PWRB] [ 3.267015] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1 [ 3.267205] ACPI: Power Button [PWRF] [ 3.276958] thermal LNXTHERM:00: registered as thermal_zone0 [ 3.276962] ACPI: Thermal Zone [TZ00] (0 C) [ 3.277542] battery: ACPI: Battery: found native INT33F4 PMIC, not loading [ 3.284455] loop: module loaded [ 3.284782] MM: desc_per_page = 128 [ 3.284784] mtip32xx Version 1.3.1 [ 3.284899] Silicon Labs C2 port support v. 0.51.0 - (C) 2007 Rodolfo Giometti [ 3.353146] usbcore: registered new interface driver rtsx_usb [ 3.362848] libphy: Fixed MDIO Bus: probed [ 3.363034] PPP generic driver version 2.4.2 [ 3.364463] PPP BSD Compression module registered [ 3.364466] PPP Deflate Compression module registered [ 3.364469] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 3.364471] ehci-pci: EHCI PCI platform driver [ 3.364548] ehci-platform: EHCI generic platform driver [ 3.364654] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 3.364673] ohci-pci: OHCI PCI platform driver [ 3.364705] ohci-platform: OHCI generic platform driver [ 3.364741] uhci_hcd: USB Universal Host Controller Interface driver [ 3.365193] xhci_hcd 0000:00:14.0: xHCI Host Controller [ 3.365210] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 1 [ 3.366494] xhci_hcd 0000:00:14.0: hcc params 0x200077c1 hci version 0x100 quirks 0x0000000081509810 [ 3.366511] xhci_hcd 0000:00:14.0: cache line size of 64 is not supported [ 3.366920] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19 [ 3.366924] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 3.366928] usb usb1: Product: xHCI Host Controller [ 3.366931] usb usb1: Manufacturer: Linux 4.19.2-fastsys xhci-hcd [ 3.366934] usb usb1: SerialNumber: 0000:00:14.0 [ 3.367263] hub 1-0:1.0: USB hub found [ 3.367314] hub 1-0:1.0: 7 ports detected [ 3.368788] xhci_hcd 0000:00:14.0: xHCI Host Controller [ 3.368801] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 2 [ 3.368811] xhci_hcd 0000:00:14.0: Host supports USB 3.0 SuperSpeed [ 3.368926] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 4.19 [ 3.368930] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 3.368934] usb usb2: Product: xHCI Host Controller [ 3.368937] usb usb2: Manufacturer: Linux 4.19.2-fastsys xhci-hcd [ 3.368940] usb usb2: SerialNumber: 0000:00:14.0 [ 3.369247] hub 2-0:1.0: USB hub found [ 3.369302] hub 2-0:1.0: 6 ports detected [ 3.370787] usbcore: registered new interface driver uas [ 3.370836] usbcore: registered new interface driver usb-storage [ 3.370859] usbcore: registered new interface driver ums-alauda [ 3.370879] usbcore: registered new interface driver ums-cypress [ 3.370902] usbcore: registered new interface driver ums-datafab [ 3.370922] usbcore: registered new interface driver ums_eneub6250 [ 3.370941] usbcore: registered new interface driver ums-freecom [ 3.370960] usbcore: registered new interface driver ums-isd200 [ 3.370979] usbcore: registered new interface driver ums-jumpshot [ 3.370998] usbcore: registered new interface driver ums-karma [ 3.371020] usbcore: registered new interface driver ums-onetouch [ 3.371049] usbcore: registered new interface driver ums-realtek [ 3.371069] usbcore: registered new interface driver ums-sddr09 [ 3.371088] usbcore: registered new interface driver ums-sddr55 [ 3.371108] usbcore: registered new interface driver ums-usbat [ 3.371179] i8042: PNP: No PS/2 controller found. [ 3.371416] mousedev: PS/2 mouse device common for all mice [ 3.371973] rtc_cmos 00:04: registered as rtc0 [ 3.372023] rtc_cmos 00:04: alarms up to one month, y3k, 242 bytes nvram [ 3.372331] device-mapper: ioctl: 4.39.0-ioctl (2018-04-03) initialised: dm-devel@redhat.com [ 3.372344] intel_pstate: Intel P-state driver initializing [ 3.372995] sdhci: Secure Digital Host Controller Interface driver [ 3.373001] sdhci: Copyright(c) Pierre Ossman [ 3.407613] mmc0: SDHCI controller on ACPI [80860F14:00] using ADMA [ 3.421974] mmc1: SDHCI controller on ACPI [80860F14:01] using ADMA [ 3.422093] wbsd: Winbond W83L51xD SD/MMC card interface driver [ 3.422095] wbsd: Copyright(c) Pierre Ossman [ 3.422204] usbcore: registered new interface driver ushc [ 3.422269] sdhci-pltfm: SDHCI platform and OF driver helper [ 3.422744] EFI Variables Facility v0.08 2004-May-17 [ 3.430122] hidraw: raw HID events driver (C) Jiri Kosina [ 3.430190] usbcore: registered new interface driver usbhid [ 3.430191] usbhid: USB HID core driver [ 3.430656] Initializing XFRM netlink socket [ 3.430666] NET: Registered protocol family 17 [ 3.430690] Key type dns_resolver registered [ 3.431318] microcode: sig=0x406c4, pf=0x1, revision=0x40c [ 3.431434] microcode: Microcode Update Driver: v2.2. [ 3.431458] sched_clock: Marking stable (3429477191, 1803700)->(3433822737, -2541846) [ 3.431829] registered taskstats version 1 [ 3.431831] Loading compiled-in X.509 certificates [ 3.435214] rtc_cmos 00:04: setting system clock to 2018-11-17 19:44:54 UTC (1542483894) [ 3.435372] cfg80211: Loading compiled-in X.509 certificates for regulatory database [ 3.443956] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [ 3.444038] Warning: unable to open an initial console. [ 3.453912] Freeing unused kernel image memory: 16932K [ 3.454000] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 [ 3.454004] cfg80211: failed to load regulatory.db [ 3.459729] Write protecting the kernel read-only data: 16384k [ 3.462198] Freeing unused kernel image memory: 2012K [ 3.463418] Freeing unused kernel image memory: 908K [ 3.463969] Run /init as init process [ 3.476425] mdev (1290) used greatest stack depth: 13648 bytes left [ 3.479476] mmc1: new high speed SDIO card at address 0001 [ 3.514386] mmc0: new HS200 MMC card at address 0001 [ 3.515347] mmcblk0: mmc0:0001 NCard 28.9 GiB [ 3.516053] mmcblk0boot0: mmc0:0001 NCard partition 1 4.00 MiB [ 3.516960] mmcblk0boot1: mmc0:0001 NCard partition 2 4.00 MiB [ 3.517699] mmcblk0rpmb: mmc0:0001 NCard partition 3 4.00 MiB, chardev (248:0) [ 3.522501] mdev (1304) used greatest stack depth: 13608 bytes left [ 3.692847] usb 1-2: new high-speed USB device number 2 using xhci_hcd [ 3.822825] usb 1-2: New USB device found, idVendor=1a40, idProduct=0101, bcdDevice= 1.11 [ 3.822839] usb 1-2: New USB device strings: Mfr=0, Product=1, SerialNumber=0 [ 3.822849] usb 1-2: Product: USB 2.0 Hub [ 3.825350] hub 1-2:1.0: USB hub found [ 3.825439] hub 1-2:1.0: 4 ports detected [ 3.997430] usb 2-1: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd [ 4.139455] usb 2-1: New USB device found, idVendor=2109, idProduct=0813, bcdDevice= 2.21 [ 4.139470] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 4.139481] usb 2-1: Product: USB3.0 Hub [ 4.139491] usb 2-1: Manufacturer: VIA Labs, Inc. [ 4.146350] hub 2-1:1.0: USB hub found [ 4.146827] hub 2-1:1.0: 4 ports detected [ 4.248843] usb 1-3: new high-speed USB device number 3 using xhci_hcd [ 4.379357] usb 1-3: New USB device found, idVendor=0bda, idProduct=8152, bcdDevice=20.00 [ 4.379372] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 4.379383] usb 1-3: Product: USB 10/100 LAN [ 4.379394] usb 1-3: Manufacturer: Realtek [ 4.379403] usb 1-3: SerialNumber: 20180E107251 [ 4.454017] usb 1-2.1: new high-speed USB device number 4 using xhci_hcd [ 4.517997] random: fast init done [ 4.553993] usb 1-2.1: New USB device found, idVendor=090c, idProduct=1000, bcdDevice=11.00 [ 4.554008] usb 1-2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 4.554018] usb 1-2.1: Product: USB DISK [ 4.554028] usb 1-2.1: Manufacturer: SMI Corporation [ 4.558869] usb-storage 1-2.1:1.0: USB Mass Storage device detected [ 4.559469] scsi host0: usb-storage 1-2.1:1.0 [ 4.662844] usb 1-4: new high-speed USB device number 5 using xhci_hcd [ 4.800388] usb 1-4: New USB device found, idVendor=2109, idProduct=2813, bcdDevice= 2.21 [ 4.800402] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 4.800414] usb 1-4: Product: USB2.0 Hub [ 4.800424] usb 1-4: Manufacturer: VIA Labs, Inc. [ 4.804226] hub 1-4:1.0: USB hub found [ 4.804901] hub 1-4:1.0: 4 ports detected [ 5.125860] usb 1-4.1: new high-speed USB device number 6 using xhci_hcd [ 5.222755] usb 1-4.1: New USB device found, idVendor=1a40, idProduct=0201, bcdDevice= 1.00 [ 5.222771] usb 1-4.1: New USB device strings: Mfr=0, Product=1, SerialNumber=0 [ 5.222781] usb 1-4.1: Product: USB 2.0 Hub [MTT] [ 5.225410] hub 1-4.1:1.0: USB hub found [ 5.225638] hub 1-4.1:1.0: 7 ports detected [ 5.512874] usb 1-4.1.2: new low-speed USB device number 7 using xhci_hcd [ 5.612881] usb 1-4.1.2: New USB device found, idVendor=046d, idProduct=c05a, bcdDevice=63.00 [ 5.612896] usb 1-4.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 5.612906] usb 1-4.1.2: Product: USB Optical Mouse [ 5.612915] usb 1-4.1.2: Manufacturer: Logitech [ 5.701889] usb 1-4.1.4: new low-speed USB device number 8 using xhci_hcd [ 5.801045] usb 1-4.1.4: New USB device found, idVendor=0566, idProduct=3002, bcdDevice= 1.00 [ 5.801060] usb 1-4.1.4: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 6.097147] scsi 0:0:0:0: Direct-Access SMI USB DISK 1100 PQ: 0 ANSI: 0 CCS [ 6.098135] sd 0:0:0:0: Attached scsi generic sg0 type 0 [ 6.098877] sd 0:0:0:0: [sda] 7802880 512-byte logical blocks: (4.00 GB/3.72 GiB) [ 6.099610] sd 0:0:0:0: [sda] Write Protect is off [ 6.099615] sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00 [ 6.100362] sd 0:0:0:0: [sda] No Caching mode page found [ 6.100371] sd 0:0:0:0: [sda] Assuming drive cache: write through [ 6.104115] sda: sda1 sda2 [ 6.106702] sd 0:0:0:0: [sda] Attached SCSI removable disk [ 6.675994] findfs (1367) used greatest stack depth: 13288 bytes left [ 6.863108] FAT-fs (sda1): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive! [ 6.873121] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. [ 7.025683] random: encfs: uninitialized urandom read (32 bytes read) [ 7.857349] encfs (1516) used greatest stack depth: 13032 bytes left [ 8.855910] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null) [ 9.078500] Linux agpgart interface v0.103 [ 9.199662] checking generic (80000000 7f0000) vs hw (80000000 10000000) [ 9.199666] fb: switching to inteldrmfb from EFI VGA [ 9.199723] Console: switching to colour dummy device 80x25 [ 9.199936] [drm] Replacing VGA console driver [ 9.200129] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 9.200132] [drm] Driver supports precise vblank timestamp query. [ 9.202674] i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [ 9.207459] [drm] Initialized i915 1.6.0 20180719 for 0000:00:02.0 on minor 0 [ 9.209096] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) [ 9.211185] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input2 [ 9.211594] [drm] HDaudio controller not detected, using LPE audio instead [ 9.469553] fbcon: inteldrmfb (fb0) is primary device [ 9.491750] Console: switching to colour frame buffer device 240x67 [ 9.529448] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device [ 9.538586] modprobe (1929) used greatest stack depth: 12824 bytes left [ 9.558624] intelfb: Framebuffer driver for Intel(R) 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/945GME/965G/965GM chipsets [ 9.558629] intelfb: Version 0.9.6 [ 9.573862] input: Logitech USB Optical Mouse as /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.1/1-4.1.2/1-4.1.2:1.0/0003:046D:C05A.0001/input/input3 [ 9.574883] hid-generic 0003:046D:C05A.0001: input,hidraw0: USB HID v1.11 Mouse [Logitech USB Optical Mouse] on usb-0000:00:14.0-4.1.2/input0 [ 9.575544] input: HID 0566:3002 as /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.1/1-4.1.4/1-4.1.4:1.0/0003:0566:3002.0002/input/input4 [ 9.628875] hid-generic 0003:0566:3002.0002: input,hidraw1: USB HID v1.10 Keyboard [HID 0566:3002] on usb-0000:00:14.0-4.1.4/input0 [ 9.629731] input: HID 0566:3002 System Control as /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.1/1-4.1.4/1-4.1.4:1.1/0003:0566:3002.0003/input/input5 [ 9.682161] input: HID 0566:3002 as /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.1/1-4.1.4/1-4.1.4:1.1/0003:0566:3002.0003/input/input6 [ 9.683069] hid-generic 0003:0566:3002.0003: input,hiddev96,hidraw2: USB HID v1.10 Device [HID 0566:3002] on usb-0000:00:14.0-4.1.4/input1 [ 9.707872] usbcore: registered new interface driver usbtouchscreen [ 15.290009] random: sqlite3: uninitialized urandom read (256 bytes read) [ 17.089930] usbcore: registered new interface driver r8152 [ 17.127749] r8723bs: module is from the staging directory, the quality is unknown, you have been warned. [ 17.132161] RTL8723BS: module init start [ 17.132165] RTL8723BS: rtl8723bs v4.3.5.5_12290.20140916_BTCOEX20140507-4E40 [ 17.132166] RTL8723BS: rtl8723bs BT-Coex version = BTCOEX20140507-4E40 [ 17.208095] usb 1-3: reset high-speed USB device number 3 using xhci_hcd [ 17.215626] pnetdev = 00000000106e46c4 [ 17.398766] r8152 1-3:1.0 eth0: v1.09.9 [ 17.468145] RTL8723BS: rtw_ndev_init(wlan0) [ 17.468692] RTL8723BS: module init ret =0 [ 17.542998] intel_sst_acpi 808622A8:00: LPE base: 0x91000000 size:0x200000 [ 17.543003] intel_sst_acpi 808622A8:00: IRAM base: 0x910c0000 [ 17.543039] intel_sst_acpi 808622A8:00: DRAM base: 0x91100000 [ 17.543048] intel_sst_acpi 808622A8:00: SHIM base: 0x91140000 [ 17.543056] intel_sst_acpi 808622A8:00: Mailbox base: 0x91144000 [ 17.543066] intel_sst_acpi 808622A8:00: DDR base: 0x20000000 [ 17.543203] intel_sst_acpi 808622A8:00: Got drv data max stream 25 [ 17.579608] bytcht_es8316 bytcht_es8316: ASoC: CODEC DAI snd-soc-dummy-dai not registered [ 17.579618] bytcht_es8316 bytcht_es8316: snd_soc_register_card failed -517 [ 17.943530] random: sqlite3: uninitialized urandom read (256 bytes read) [ 18.963493] random: sqlite3: uninitialized urandom read (256 bytes read) [ 19.175877] r8152 1-3:1.0 eth0: carrier on [ 23.167863] random: crng init done 00:00.0 Host bridge: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series SoC Transaction Register (rev 36) 00:02.0 VGA compatible controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers (rev 36) 00:0b.0 Signal processing controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Power Management Controller (rev 36) 00:14.0 USB controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series USB xHCI Controller (rev 36) 00:1a.0 Encryption controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Trusted Execution Engine (rev 36) 00:1f.0 ISA bridge: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCU (rev 36) snd_soc_sst_byt_cht_es8316 16384 0 - Live 0xffffffffc03bf000 snd_soc_es8316 40960 0 - Live 0xffffffffc03e5000 snd_intel_sst_acpi 16384 1 - Live 0xffffffffc03e0000 snd_soc_acpi_intel_match 24576 1 snd_intel_sst_acpi, Live 0xffffffffc0362000 snd_soc_acpi 16384 2 snd_intel_sst_acpi,snd_soc_acpi_intel_match, Live 0xffffffffc03db000 snd_intel_sst_core 32768 1 snd_intel_sst_acpi, Live 0xffffffffc03b6000 snd_soc_sst_atom_hifi2_platform 86016 1 snd_intel_sst_core, Live 0xffffffffc03c5000 snd_soc_core 200704 3 snd_soc_sst_byt_cht_es8316,snd_soc_es8316,snd_soc_sst_atom_hifi2_platform, Live 0xffffffffc0384000 ac97_bus 16384 1 snd_soc_core, Live 0xffffffffc0353000 snd_compress 20480 1 snd_soc_core, Live 0xffffffffc035c000 snd_pcm_dmaengine 16384 1 snd_soc_core, Live 0xffffffffc02aa000 snd_pcm 94208 5 snd_soc_sst_byt_cht_es8316,snd_soc_es8316,snd_soc_sst_atom_hifi2_platform,snd_soc_core,snd_pcm_dmaengine, Live 0xffffffffc036c000 snd_timer 32768 1 snd_pcm, Live 0xffffffffc034a000 snd 73728 5 snd_soc_sst_atom_hifi2_platform,snd_soc_core,snd_compress,snd_pcm,snd_timer, Live 0xffffffffc0297000 r8723bs 581632 0 - Live 0xffffffffc02bb000 (C) r8152 57344 0 - Live 0xffffffffc0288000 mii 16384 1 r8152, Live 0xffffffffc0283000 usbtouchscreen 20480 0 - Live 0xffffffffc0279000 hid_generic 16384 0 - Live 0xffffffffc0271000 intelfb 45056 0 - Live 0xffffffffc02af000 i915 1421312 2 - Live 0xffffffffc0115000 i2c_algo_bit 16384 2 intelfb,i915, Live 0xffffffffc00e0000 intel_gtt 20480 1 i915, Live 0xffffffffc00d7000 drm_kms_helper 159744 1 i915, Live 0xffffffffc00ed000 sysimgblt 16384 1 drm_kms_helper, Live 0xffffffffc00d2000 sysfillrect 16384 1 drm_kms_helper, Live 0xffffffffc00cb000 syscopyarea 16384 1 drm_kms_helper, Live 0xffffffffc00e8000 fb_sys_fops 16384 1 drm_kms_helper, Live 0xffffffffc0059000 drm 442368 3 i915,drm_kms_helper, Live 0xffffffffc005e000 agpgart 45056 3 intelfb,intel_gtt,drm, Live 0xffffffffc004d000 (In reply to Pierre Bossart from comment #134) > > > > https://dropmefiles.com/GyFSq > > Please add the files as attachments in this bugzilla. > > What I was asking is information on ACPI devices. It seems like you don't > have /sys/bus/acpi/devices on your system, which makes it impossible to > debug. You should have something like this in the log of alsa-info.sh > > > !!ACPI Device Status Information > !!--------------- > > /sys/bus/acpi/devices/ACPI000C:00/status 15 > /sys/bus/acpi/devices/INT33A1:00/status 15 > /sys/bus/acpi/devices/INT340E:00/status 15 > /sys/bus/acpi/devices/INT3F0D:00/status 15 > /sys/bus/acpi/devices/LNXPOWER:00/status 1 > /sys/bus/acpi/devices/LNXPOWER:01/status 1 > /sys/bus/acpi/devices/LNXPOWER:02/status 1 > /sys/bus/acpi/devices/LNXPOWER:03/status 1 > /sys/bus/acpi/devices/LNXPOWER:04/status 1 > /sys/bus/acpi/devices/LNXPOWER:05/status 1 > /sys/bus/acpi/devices/LNXPOWER:06/status 1 > /sys/bus/acpi/devices/LNXPOWER:07/status 1 > /sys/bus/acpi/devices/LNXPOWER:08/status 1 > /sys/bus/acpi/devices/LNXPOWER:09/status 1 > /sys/bus/acpi/devices/LNXPOWER:0a/status 1 Maybe this data will be needed: $ pwd /sys/bus/acpi/devices/ESSX8316:00 $ cat ./adr ./hid modalias path power_state real_power_state status uevent uid 0x00000000 ESSX8316 acpi:ESSX8316:ESSX8316: \_SB_.PCI0.I2C2.ESSX D0 D3hot 15 MODALIAS=acpi:ESSX8316:ESSX8316: 1 $ please use attachments instead of copy-pasting... I don't know what is going on with your platform, it has everything needed for ACPI probe but now the error is different [ 17.579608] bytcht_es8316 bytcht_es8316: ASoC: CODEC DAI snd-soc-dummy-dai not registered That doesn't have any hardware dependencies, I suspect a case of bad configuration since it looks like you are using a very specific distro. (In reply to Pierre Bossart from comment #137) > please use attachments instead of copy-pasting... I apologize, did not see that they are attached at the top ... ( > > I don't know what is going on with your platform, it has everything needed > for ACPI probe but now the error is different These errors have always been: [ 15.870282] intel_sst_acpi 808622A8:00: LPE base: 0x91000000 size:0x200000 [ 15.870286] intel_sst_acpi 808622A8:00: IRAM base: 0x910c0000 [ 15.870315] intel_sst_acpi 808622A8:00: DRAM base: 0x91100000 [ 15.870325] intel_sst_acpi 808622A8:00: SHIM base: 0x91140000 [ 15.870333] intel_sst_acpi 808622A8:00: Mailbox base: 0x91144000 [ 15.870341] intel_sst_acpi 808622A8:00: DDR base: 0x20000000 [ 15.871985] intel_sst_acpi 808622A8:00: Got drv data max stream 25 [ 15.904954] bytcht_es8316 bytcht_es8316: ASoC: CODEC DAI snd-soc-dummy-dai not registered [ 15.904966] bytcht_es8316 bytcht_es8316: snd_soc_register_card failed -517 [ 15.933183] bytcht_es8316 bytcht_es8316: ASoC: CODEC DAI snd-soc-dummy-dai not registered [ 15.933193] bytcht_es8316 bytcht_es8316: snd_soc_register_card failed -517 Maybe I missed the block with these errors last time ... > > [ 17.579608] bytcht_es8316 bytcht_es8316: ASoC: CODEC DAI > snd-soc-dummy-dai not registered > > That doesn't have any hardware dependencies, I suspect a case of bad > configuration since it looks like you are using a very specific distro. Distribution is our own development, but now the problem is that the kernel module does not see the sound card, this problem not depend on the distribution. I ask to help only with the problem of the kernel module. > Distribution is our own development, but now the problem is that the kernel
> module does not see the sound card, this problem not depend on the
> distribution. I ask to help only with the problem of the kernel module.
the kernel detects the right machine driver, but somehow your kernel
configuration is problematic or something is just not right in the codec
probe. You will have to add more traces yourself and debug the flows. No
one can help you if you don't look further in the details, sorry.
(In reply to Pierre Bossart from comment #139) > > Distribution is our own development, but now the problem is that the kernel > > module does not see the sound card, this problem not depend on the > > distribution. I ask to help only with the problem of the kernel module. > the kernel detects the right machine driver, but somehow your kernel > configuration is problematic or something is just not right in the codec > probe. You will have to add more traces yourself and debug the flows. No > one can help you if you don't look further in the details, sorry. You will help me a lot if you give a .config file of the kernel in which the sound card is normal working! Thank you very much! > You will help me a lot if you give a .config file of the kernel in which the > sound card is normal working! https://github.com/kernins/linux-chwhi12/blob/master/configs/kernel/dotconfig (In reply to Vinod Koul from comment #95) > Created attachment 258709 [details] > attachment-24355-0.html > > Thanks for your email > > I am on vacation till Oct 7th > Please expect delayed response. > > Regards > -- > ~Vinod dmesg | grep 5645 [ 5.490811] rt5645 i2c-10EC5645:00: Detected MINIX Z83-4 platform [ 5.490827] rt5645 i2c-10EC5645:00: i2c-10EC5645:00 supply avdd not found, using dummy regulator [ 5.490862] rt5645 i2c-10EC5645:00: Linked as a consumer to regulator.0 [ 5.490866] rt5645 i2c-10EC5645:00: i2c-10EC5645:00 supply cpvdd not found, using dummy regulator [ 5.988133] cht-bsw-rt5645 cht-bsw-rt5645: snd-soc-dummy-dai <-> media-cpu-dai mapping ok [ 5.988200] cht-bsw-rt5645 cht-bsw-rt5645: snd-soc-dummy-dai <-> deepbuffer-cpu-dai mapping ok [ 5.988515] cht-bsw-rt5645 cht-bsw-rt5645: rt5645-aif1 <-> ssp2-port mapping ok [ 6.052041] input: chtrt5645 Headset as /devices/pci0000:00/808622A8:00/cht-bsw-rt5645/sound/card1/input16 aplay -l **** List of PLAYBACK Hardware Devices **** card 0: Audio [Intel HDMI/DP LPE Audio], device 0: HdmiLpeAudio [Intel HDMI/DP LPE Audi] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: Audio [Intel HDMI/DP LPE Audio], device 1: HdmiLpeAudio [Intel HDMI/DP LPE Audi] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: Audio [Intel HDMI/DP LPE Audio], device 2: HdmiLpeAudio [Intel HDMI/DP LPE Audi] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: chtrt5645 [chtrt5645], device 0: Audio (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: chtrt5645 [chtrt5645], device 1: Deep-Buffer Audio (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 aplay -l **** List of PLAYBACK Hardware Devices **** card 0: Audio [Intel HDMI/DP LPE Audio], device 0: HdmiLpeAudio [Intel HDMI/DP LPE Audi] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: Audio [Intel HDMI/DP LPE Audio], device 1: HdmiLpeAudio [Intel HDMI/DP LPE Audi] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: Audio [Intel HDMI/DP LPE Audio], device 2: HdmiLpeAudio [Intel HDMI/DP LPE Audi] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: chtrt5645 [chtrt5645], device 0: Audio (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: chtrt5645 [chtrt5645], device 1: Deep-Buffer Audio (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 chtrt5645 does not work ! |
Created attachment 246021 [details] dmesg log I've heard about Surface 3 tablet getting audio working which seems to have the same soundcard as those tablets. On those tablets it only works through HDMI, speakers and headphone jack don't work. On those tablets it only works through HDMI, speakers and headphone jack don't work. intel_sst_acpi 808622A8:00: No matching machine driver found