I’m not sure those syslog entries are particularly telling. I would expect problems with the
snd_hda_intel driver to be listed as such. That said, you may want to provide just the logs relevant with
journalctl -t snd_hda_intel.
So here’s what we know:
- With the device showing in
lspci at all, we can confirm that the kernel sees it, which is to say that there should not be any hardware issues.
From what I can tell,
snd_hda_intel is indeed the right driver for this device. We can see this further confirmed by one of the driver’s aliases if you run
modinfo snd_hda_intel (
pci:v00008086d00002284 translates to vendor ID 8086 and device ID 2284, which is equivalent to the PCI ID of
8086:2284 you see in
So some other basic things we should check:
- List all your output devices with
aplay -l. If there’s nothing there (or if they’re only HDMI outputs or something of the sort), then there’s clearly a problem.
- Check for muting.
pactl list sinks | grep -E 'Description|Mute' should give a relatively friendly description of the output device and its state as far as muting is concerned.
Outside of that, we may have to delve into deeper waters and look at the driver parameters (see
modinfo -p snd_hda_intel).
It turns out there are quite a few.
index:Index value for Intel HD audio interface. (array of int)
id:ID string for Intel HD audio interface. (array of charp)
enable:Enable Intel HD audio interface. (array of bool)
model:Use the given board model. (array of charp)
position_fix:DMA pointer read method.(-1 = system default, 0 = auto, 1 = LPIB, 2 = POSBUF, 3 = VIACOMBO, 4 = COMBO, 5 = SKL+, 6 = FIFO). (array of int)
bdl_pos_adj:BDL position adjustment offset. (array of int)
probe_mask:Bitmask to probe codecs (default = -1). (array of int)
probe_only:Only probing and no codec initialization. (array of int)
jackpoll_ms:Ms between polling for jack events (default = 0, using unsol events only) (array of int)
single_cmd:Use single command to communicate with codecs (for debugging only). (bint)
enable_msi:Enable Message Signaled Interrupt (MSI) (bint)
patch:Patch file for Intel HD audio interface. (array of charp)
beep_mode:Select HDA Beep registration mode (0=off, 1=on) (default=1). (array of bool)
power_save:Automatic power-saving timeout (in second, 0 = disable). (xint)
pm_blacklist:Enable power-management blacklist (bool)
power_save_controller:Reset controller in power save mode. (bool)
align_buffer_size:Force buffer and period sizes to be multiple of 128 bytes. (bint)
snoop:Enable/disable snooping (bint)
Looking at the kernel docs it seems the HD Audio devices are often troublesome (although mine works great) and offers several suggestions, including flipping some of those configuration options. One thing that might be useful is looking for your codec with
grep -R Codec /proc/asound/card*/codec#* and then looking at the models and seeing if there’s something specific listed, otherwise I might take the more generic advice and using
I will say that Chromebooks are notoriously problematic, as evidenced by this AskUbuntu post reporting similar woes.
The good news is that this should be a problem that affects Ubuntu and all of its flavors, Lubuntu included, so you could expand your search for an answer beyond just this forum.