@Karen Chaltikian
Good news! Although I've tried this on my UX391UA, but without success.
Can you describe your procedure step-by-step?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.laun
Can somebody confirm that the above mentioned procedure also works with
an UX391UA.
It does NOT work on my UX391UA.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/178448
I have a ASUS UX391UA and finally want to get the sound working.
Is it theoretically possible to apply the above mentioned fix using the
Kernel Update Utility for Ubuntu (https://github.com/teejee2008/ukuu)?
What's the proper way to apply the following patches afterwards?
https://lkml.org/lkml/2
@Greg (buchovagabond)
Without adding those 3 patches and the SND_PCI_QUIRK(0x1043, 0x10a1,
"ASUS UX391UA", ALC294_FIXUP_ASUS_SPK) tweak to to
/sound/pci/hda/patch_realtek.c ?
So only updating with UKUU will work?
--
You received this bug notification because you are a member of Ubuntu
Touch see
Installed 4.20.0-rc7 kernel through UKUU, but still no sound on ASUS
UX391U :/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1784485
Title:
[ZenBook S UX391UA, Realte
@Ben
patch_realtek.c is missing under
/lib/modules/4.20.0-042000rc7-generic/kernel/sound/pci/hda/ after
installing 4.20.0-rc7 kernel.
Can't find it elsewhere either.
How do you properly applied those 3 patches?
And the proper command is: SND_PCI_QUIRK(0x1043, 0x10a1, "ASUS UX391UA",
ALC294_FIXU
@Ben
Thanks!
Patching and compiling the kernel is out of my league. I prefer the
user-friendly and "foolproof" way through the Kernel Update Utility for
Ubuntu (UKUU), mentioned above. Afaik, I can't edit the patch_realtek.c
file when doing so with UKUU.
Do you know if it's already planned to me
@Santiago Londoño
Or you could have used UKUU: https://github.com/teejee2008/ukuu
Too bad that the 4.20 kernel doesn't contain the fix for the UX391UA :/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
@VanVan
That's strange!
To be on the safe side, I even did a fresh Ubuntu 18.10 installation and
updated to the 4.20 kernel with UKUU, but I still don't have sound.
Neither from the internal, nor the external speakers. I've played around
with alsamixer in the terminal – without success.
Can some
Some additional sysinfo with inxi:
System:Host: mir Kernel: 4.20.0-042000-generic x86_64 bits: 64 Desktop:
Gnome 3.30.1
Distro: Ubuntu 18.10 (Cosmic Cuttlefish)
Machine: Type: Laptop System: ASUSTeK product: ZenBook S UX391UA v: 1.0
serial:
Mobo: ASUSTeK model: UX
Thanks Pawel!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1784485
Title:
[ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
Status in alsa-driver p
Why is this another bug?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1698083
Title:
Middle-click titlebar actions (like maximizing vertically) don't work
in Wayland s
Please change it to "confirmed". That's still a relevant issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1698083
Title:
Middle-click titlebar actions (like maximizin
I'm using Ubuntu 17.10 and this bug is still present with Xorg AND
Wayland.
Apps with a "normal" GTK titlebar (the narrow one), like Firefox, are
working according to the settings in Gnome Tweak. So a double- or
middle-click on the titlebar maximizes the window f.i. vertically. But
when an app has
09 20:32:18 mir bluetoothd[865]: bt_uhid_send: Invalid argument (22)
Aug 09 20:32:18 mir kernel: hid-generic 0005:046D:B01B.0002: input,hidraw1:
BLUETOOTH HID v0.07 Keyboard [M585/M590] on 2C:6F:C9:44:57:E0
Aug 09 20:35:34 mir sudo[8461]: sojusnik : TTY=pts/0 ; PWD=/home/sojusnik ;
USER=roo
t (22)
Aug 09 20:32:18 mir bluetoothd[865]: bt_uhid_send: Invalid argument (22)
Aug 09 20:32:18 mir kernel: hid-generic 0005:046D:B01B.0002: input,hidraw1:
BLUETOOTH HID v0.07 Keyboard [M585/M590] on 2C:6F:C9:44:57:E0
Aug 09 20:35:34 mir sudo[8461]: sojusnik : TTY=pts/0 ; PWD=/hom
This also happens on Manjaro, see https://forum.manjaro.org/t/alc294
-analog-audio-card-detected-but-no-sound-internaly-or-
headphones/54089/16
Did somebody already find a solution or knows how to debug this
properly?
--
You received this bug notification because you are a member of Ubuntu
Touch
oothd[865]: bt_uhid_send: Invalid argument (22)
Aug 09 20:32:18 mir bluetoothd[865]: bt_uhid_send: Invalid argument (22)
Aug 09 20:32:18 mir bluetoothd[865]: bt_uhid_send: Invalid argument (22)
Aug 09 20:32:18 mir bluetoothd[865]: bt_uhid_send: Invalid argument (22)
Aug 09 20:32:18 mir kernel: hid-generic 00
lid argument (22)
Aug 09 20:32:18 mir kernel: hid-generic 0005:046D:B01B.0002: input,hidraw1:
BLUETOOTH HID v0.07 Keyboard [M585/M590] on 2C:6F:C9:44:57:E0
Aug 09 20:35:34 mir sudo[8461]: sojusnik : TTY=pts/0 ; PWD=/home/sojusnik ;
USER=root ; COMMAND=/usr/sbin/service bluetooth restart
Aug
I even installed Windows on an external drive, because the author of
this thread (https://askubuntu.com/questions/986140/no-sound-output-
ubuntu-17-10-asus-zenbook-13) assumed that a proper shutdown of Windows
could solve this issue for Linux users, but it didn't help either.
--
You received this
BTW, can somebody confirm that this ZenBook S UX391UA on Ubuntu 18.04
runs quite hot, even while doing normal "office stuff"?
At some point the preinstalled thermald daemon even forcefully shuts
down Ubuntu, preventing it from overheating. "Package temperature above
threshold, cpu clock throttled"
Still no sound, even on Ubuntu 18.10.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1784485
Title:
[ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
I've opened another issue regarding this notebook. It's about
overheating. Would be very helpful, if you could share your experience
here: https://askubuntu.com/questions/1087672/unusually-hot-asus-ux391ua
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packa
23 matches
Mail list logo
