When connecting headphone jack to the laptop, it doesn’t get detected, instead it keeps playing audio through speakers. Any help would be greatly appreciated
aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 0: ALC294 Analog [ALC294 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0
inxi -Fxz
System: Kernel: 5.8.0-2-MANJARO x86_64 bits: 64 compiler: N/A Desktop: KDE Plasma 5.19.4 Distro: Manjaro Linux
Machine: Type: Laptop System: ASUSTeK product: Zephyrus M GU502GW_GU502GW v: 1.0 serial: <filter>
Mobo: ASUSTeK model: GU502GW v: 1.0 serial: <filter> UEFI: American Megatrends v: GU502GW.309 date: 04/24/2020
Battery: ID-1: BAT0 charge: 69.0 Wh condition: 72.4/76.0 Wh (95%) model: ASUSTeK ASUS Battery status: Not charging
CPU: Topology: 6-Core model: Intel Core i7-9750H bits: 64 type: MT MCP arch: Kaby Lake rev: A L2 cache: 12.0 MiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 62431
Speed: 800 MHz min/max: 800/4500 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800
9: 800 10: 800 11: 800 12: 800
Graphics: Device-1: Intel UHD Graphics 630 vendor: ASUSTeK driver: i915 v: kernel bus ID: 00:02.0
Device-2: NVIDIA TU106M [GeForce RTX 2070 Mobile] vendor: ASUSTeK driver: nvidia v: 440.100 bus ID: 01:00.0
Display: x11 server: X.Org 1.20.8 driver: modesetting,nvidia resolution: 1: 1920x1080~60Hz 2: 1920x1080~240Hz
OpenGL: renderer: GeForce RTX 2070 with Max-Q Design/PCIe/SSE2 v: 4.6.0 NVIDIA 440.100 direct render: Yes
Audio: Device-1: Intel Cannon Lake PCH cAVS vendor: ASUSTeK driver: snd_hda_intel v: kernel bus ID: 00:1f.3
Sound Server: ALSA v: k5.8.0-2-MANJARO
Network: Device-1: Intel Wireless-AC 9560 [Jefferson Peak] driver: iwlwifi v: kernel port: 5000 bus ID: 00:14.3
IF: wlo1 state: up mac: <filter>
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK driver: r8169 v: kernel port: 3000
bus ID: 03:00.0
IF: eno2 state: down mac: <filter>
Drives: Local Storage: total: 968.41 GiB used: 34.83 GiB (3.6%)
ID-1: /dev/nvme0n1 vendor: Intel model: SSDPEKNW010T8 size: 953.87 GiB
ID-2: /dev/sda type: USB vendor: Kingston model: DataTraveler 2.0 size: 14.54 GiB
Partition: ID-1: / size: 97.93 GiB used: 34.81 GiB (35.5%) fs: ext4 dev: /dev/nvme0n1p4
Swap: Alert: No Swap data was found.
Sensors: System Temperatures: cpu: 58.0 C mobo: N/A gpu: nvidia temp: 50 C
Fan Speeds (RPM): cpu: 2400
Info: Processes: 386 Uptime: 2h 43m Memory: 15.49 GiB used: 6.90 GiB (44.5%) Init: systemd Compilers: gcc: 10.1.0
Packages: 1278 Shell: Zsh v: 5.8 inxi: 3.1.05
Fabby
19 August 2020 15:23
2
That sounds like a hardware problem:
Has it ever worked?
Does the same headphone work on another OS (E.G. Windows)
If no access to Windows, did you try another headphone (preferably from another brand, like your phone’s earbuds)?
When trying the other headphone, wat does the relevant KDE Plasma audio section show?
I have a similar laptop, the Gu502GV and I’ve reported this issue multiple times across multiple forums. So far no fix yet. Please join me in posting your issue on https://bugzilla.kernel.org/show_bug.cgi?id=208005#c6 and https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1877640 . The more visibility and more people reporting this issue, the higher chance a developer can help us with this issue.
2 Likes
It works perfectly on windows. So Hardware problem is discarded.
There is another discussion about some other Asus laptops with similar problems that may relate to this
but it is an ALC295 not ALC294@ZeroAnarchy can clone your Bugzilla report to get their issues reported upstream)
you have 2 links on Bugzilla to the old Manjaro forum that has recently been archived
https://archived.forum.manjaro.org/t/headphones-not-detected-kde/145544 https://archived.forum.manjaro.org/t/headphone-analog-not-working/145882
I see @lestarion has already commented on Bugzillaalsa-info.sh, so it may help to add sudo dmesg | grep snd when supplying more data
2 Likes
nikgnomic:
There is another discussion about some other Asus laptops with similar problems that may relate to this
but it is an ALC295 not ALC294@ZeroAnarchy can clone your Bugzilla report to get their issues reported upstream)
The issue on Zephyrus models appeared before changes were made that broke the sound on non-Zephyrus models; Moreover, for Zephyrus models, connected headphones are not detected at all, and other models are detected, but without sound. These are different problems.
I did not send any reports (I do not have an account on Bugzilla), and the one on Bugzilla does not contain information about the source of the problem that I found, so it will take an extremely long time to fix, if at all.
What other information about the problem should I include the in the bug report so that the chances that someone will work on the fix increases?
If this was a question for me, then I meant this report, your reports concern another problem that I am not aware of.
So, something like this
❯ sudo dmesg | grep snd
[sudo] password for lestairon:
[ 2.580406] snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
[ 2.694509] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC294: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker
[ 2.694511] snd_hda_codec_realtek hdaudioC0D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[ 2.694512] snd_hda_codec_realtek hdaudioC0D0: hp_outs=0 (0x0/0x0/0x0/0x0/0x0)
[ 2.694513] snd_hda_codec_realtek hdaudioC0D0: mono: mono_out=0x0
[ 2.694514] snd_hda_codec_realtek hdaudioC0D0: inputs:
[ 2.694515] snd_hda_codec_realtek hdaudioC0D0: Mic=0x12
[ 216.616262] snd_hda_intel 0000:00:1f.3: Unstable LPIB (352468 >= 176400); disabling LPIB delay counting
❯ pulseaudio --dump-conf
### Read from configuration file: /etc/pulse/daemon.conf ###
daemonize = no
fail = yes
high-priority = yes
nice-level = -11
realtime-scheduling = yes
realtime-priority = 5
allow-module-loading = yes
allow-exit = yes
use-pid-file = yes
system-instance = no
local-server-type = user
cpu-limit = no
enable-shm = yes
flat-volumes = no
lock-memory = no
exit-idle-time = 20
scache-idle-time = 20
dl-search-path = /usr/lib/pulse-13.0/modules
default-script-file = /etc/pulse/default.pa
load-default-script-file = yes
log-target =
log-level = notice
resample-method = auto
avoid-resampling = no
enable-remixing = yes
remixing-use-all-sink-channels = yes
enable-lfe-remixing = no
lfe-crossover-freq = 0
default-sample-format = s16le
default-sample-rate = 44100
alternate-sample-rate = 48000
default-sample-channels = 2
default-channel-map = front-left,front-right
default-fragments = 4
default-fragment-size-msec = 25
enable-deferred-volume = yes
deferred-volume-safety-margin-usec = 8000
deferred-volume-extra-delay-usec = 0
shm-size-bytes = 0
log-meta = no
log-time = no
log-backtrace = 0
rlimit-fsize = -1
rlimit-data = -1
rlimit-stack = -1
rlimit-core = -1
rlimit-rss = -1
rlimit-as = -1
rlimit-nproc = -1
rlimit-nofile = 256
rlimit-memlock = -1
rlimit-locks = -1
rlimit-sigpending = -1
rlimit-msgqueue = -1
rlimit-nice = 31
rlimit-rtprio = 9
rlimit-rttime = 200000
should be useful?
Fabby
31 August 2020 08:44
10
Yes.
And if you have a BugZilla account, you should add that here and if you don’t, you should get one so the kernel team knows more than one person is affected…
1 Like
The dmesg data is good. It shows there is no headphone output - hp_outs=0
You should also run this command
alsa-info.sh --no-upload
That will create a text file of ALSA data you can upload to Bugzilla
the Pulseaudio data isn’t needed for Bugzilla
@iancmx I do not see there is any more data you can add to your bug report as you have done a thorough job on that already. but getting some extra users in the discussion with the same hardware problem will keep it visible
2 Likes
