You are not logged in.
At this moment, the sound (output) works on linux-lts (4.1.13), but it fails to produce anything whenever I switch to linux (4.2.5). Which log or prompt should I investigate to uncover the problem?
I'm using Plasma 5 and pulseaudio.
Details:
aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: Intel [HDA Intel], device 0: VT1708S Analog [VT1708S Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: Intel [HDA Intel], device 2: VT1708S Alt Analog [VT1708S Alt Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
Headphone jack is plugged in
pacmd list-sinks
1 sink(s) available.
* index: 0
name: <alsa_output.pci-0000_00_1b.0.analog-stereo>
driver: <module-alsa-card.c>
flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY DYNAMIC_LATENCY
state: SUSPENDED
suspend cause: IDLE
priority: 9959
volume: front-left: 65536 / 100% / 0.00 dB, front-right: 65536 / 100% / 0.00 dB
balance 0.00
base volume: 65536 / 100% / 0.00 dB
volume steps: 65537
muted: no
current latency: 0.00 ms
max request: 0 KiB
max rewind: 0 KiB
monitor source: 0
sample spec: s16le 2ch 44100Hz
channel map: front-left,front-right
Stereo
used by: 0
linked by: 0
configured latency: 0.00 ms; range is 0.50 .. 2000.00 ms
card: 0 <alsa_card.pci-0000_00_1b.0>
module: 6
properties:
alsa.resolution_bits = "16"
device.api = "alsa"
device.class = "sound"
alsa.class = "generic"
alsa.subclass = "generic-mix"
alsa.name = "VT1708S Analog"
alsa.id = "VT1708S Analog"
alsa.subdevice = "0"
alsa.subdevice_name = "subdevice #0"
alsa.device = "0"
alsa.card = "0"
alsa.card_name = "HDA Intel"
alsa.long_card_name = "HDA Intel at 0xfe9f4000 irq 29"
alsa.driver_name = "snd_hda_intel"
device.bus_path = "pci-0000:00:1b.0"
sysfs.path = "/devices/pci0000:00/0000:00:1b.0/sound/card0"
device.bus = "pci"
device.vendor.id = "8086"
device.vendor.name = "Intel Corporation"
device.product.id = "293e"
device.product.name = "82801I (ICH9 Family) HD Audio Controller"
device.form_factor = "internal"
device.string = "front:0"
device.buffering.buffer_size = "352800"
device.buffering.fragment_size = "176400"
device.access_mode = "mmap+timer"
device.profile.name = "analog-stereo"
device.profile.description = "Analog Stereo"
device.description = "Built-in Audio Analog Stereo"
alsa.mixer_name = "VIA VT1708S"
alsa.components = "HDA:11060397,10431111,00100000"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-pci"
ports:
analog-output-speaker: Speakers (priority 10000, latency offset 0 usec, available: no)
properties:
device.icon_name = "audio-speakers"
analog-output-headphones: Headphones (priority 9000, latency offset 0 usec, available: yes)
properties:
device.icon_name = "audio-headphones"
active port: <analog-output-headphones>
Of course, I could stick with lts for now, but I'm afraid when lts eventually adopts 4.2.x, the similar issue will arise; therefore, I would like to know whether it's the kernel or something else that caused the problem.
Thanks.
Update:
I will stick with LTS kernel for now.
Last edited by bowshock (2015-11-30 14:37:14)
Offline
Although I'm not very knowledgeable about sound devices and cannot help you there, I can tell you that usually the lts kernel usually takes about a year before they choose a new version (based on the package's changelog).
Usually someone on the AUR (although the kernel takes a while to build) maintains one of the lts kernels from kernel.org. The packages usually follow a format of linux-ltsXY, where XY is the version (like 318 for 3.18). If sometime next year Arch chooses to change from the 4.1 line to a newer one, you will still be able to use 4.1 (even if that means you have to build the package yourself).
I don't want to work. I want to bang on the drum all day.
Offline
https://www.kernel.org/category/releases.html
Looks like 4.4 will be the next linux-lts version, and 4.1 will be supported until september 2017 .
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
(A works at time B) && (time C > time B ) ≠ (A works at time C)
Offline
You could write a bug report on bugzilla and ensure the issue is resolved by the time lts updates.
Offline
Thank you all for the information. LTS it is.
Last edited by bowshock (2015-11-30 14:36:08)
Offline
bowshock, [CLOSED]is typically used (on archlinux forum) for a thread in which posting is blocked.
Please used [SOLVED] instead.
Last edited by Lone_Wolf (2015-12-01 13:02:00)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
(A works at time B) && (time C > time B ) ≠ (A works at time C)
Offline