It is extremely unlikely that this would cause problems, it would have to match
exactly another bus command interpreted differently by another device, and we
all have almost the same laptop.
However, here is the same command improved to take into account your remarks,
and thus send the commands
It is normal to see these errors, this command sends the instruction to turn on
the digital pad to all bus number.
However, if this command did not turn on the numpad, it means that none of the
bus number are compatible, you should have the same problem manually.
--
You received this bug
For those who want to test if it works, just enter the following
command:
sudo apt-get install -y i2c-tools;for f in /dev/i2c-*; do sudo
i2ctransfer -f -y ${f:9} w13@0x15 0x05 0x00 0x3d 0x03 0x06 0x00 0x07
0x00 0x0d 0x14 0x03 0x01 0xad; done
--
You received this bug notification because you are
I can confirm that it's working for me by changing the bus number from 0
to 2.
i2ctransfer -f -y 2 w13@0x15 0x05 0x00 0x3d 0x03 0x06 0x00 0x07 0x00
0x0d 0x14 0x03 0x01 0xad
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Maybe it is possible to ask them directly :
http://www.emc.com.tw/emc/en/Product/Solution/TouchpadSolutions
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1810183
Title:
numpad on touchpad doesn't
The bug is back for me with kernel :
Linux version 5.0.0-25-generic (buildd@lgw01-amd64-008) (gcc version 8.3.0
(Ubuntu 8.3.0-6ubuntu1)) #26-Ubuntu SMP Thu Aug 1 12:04:58 UTC 2019
Sounds working for few seconds, and go down, no sound after 5 seconds.
Works again for 5 seconds after some minutes
Asus vivobook s15 s530uf has the same new BIOS 304 released, You need to test
it before posting here
https://www.asus.com/za/Laptops/ASUS-VivoBook-S15-S530UF/HelpDesk_BIOS/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
A new BIOS version (304) was released for the UX433FN that fix the
problem !
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824216
Title:
Linux 5.0 black screen on boot, display flickers (i915
*** This bug is a duplicate of bug 1824216 ***
https://bugs.launchpad.net/bugs/1824216
A new BIOS version (304) was released for the UX433FN that fix the
problem
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The new BIOS version works for me also !
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826065
Title:
Can't boot from usb live system to install disco dingo 19.04
To manage notifications about
No it doesn't change anything.
But by adding acpi=off, we can see some logs, but nothing that help.
Even with Ubuntu 19.04 with updated kernel 5.1.7, the problem is the
same.
linux (5.0.0-12.13) disco; urgency=medium
* linux: 5.0.0-12.13 -proposed tracker (LP: #1824726)
* Linux 5.0 black
Related to this bug :
https://bugs.launchpad.net/ubuntu/disco/+source/linux/+bug/1824216
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826065
Title:
Can't boot from usb live system to install
I still have this problem with Linux 5.1.7 on Ubuntu 19.04 with Asus
UX433FN !
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824216
Title:
Linux 5.0 black screen on boot, display flickers (i915
Same problem for me with Asus UX433FN.
Work fine with Kernel 5.0 on Ubuntu 18.10, but not on Uvuntu 19.04.
Maybe because of Wayland...
(This computer has 2 Graphics cards;
On previous Ubuntu version, I used nouveau.modeset=0)
--
You received this bug notification because you are a member of
@avreon Keep in mind there is two different fixes to the kernel depending on
your hardware :
- Fix for UX333, UX433, UX533 and some others starting from 4.19.10
- Fix for UX391UA and some others starting from kernel 5.0-rc1
--
You received this bug notification because you are a member of
@sojusnik
It should be included for UX391UA, I committed it on 19 December
https://github.com/torvalds/linux/commit/9cf6533e8060d3896b88ea14b27f620e6504b84b
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It's already commited, check here :
http://mailman.alsa-project.org/pipermail/alsa-devel/2018-December/143282.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784485
Title:
[ZenBook S UX391UA,
** Changed in: alsa-driver (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Audio fixes start with Linux 4.20-rc6, not 4.19
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784485
Title:
[ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
To manage
Thanks to craig-jackson if you want to check before compiling your
kernel if you have the same problem that I had, you can check if the
sound can work for a few seconds with the command below :
sudo apt install git
git clone https://github.com/VanVan/check_sound.git
sudo ./check_sound
@z80-ben Yes, you are right, UX931UA is not part of the list, it could have
worked :/
Be sure that you have no configuration error on /etc/modprobe.d/alsa-base.conf
Tested on Asus UX333, UX433, UX533 with ALC294
Support for Asus G751, P5440FF, X430UN, D640SA, UX550GE, X705FD; X430UN,
GL503VM,
It's already done like mohamed badaoui said: http://mailman.alsa-
project.org/pipermail/alsa-devel/2018-December/142572.html
Linux kernel is a big project, it can takes months to accept it.
We use mailing list rather than PR request.
If you don't want to wait, you can compile it by yourself
If you want to compile the kernel with the sound patch, you can use my
github as a ready to use official kernel with patch :
git clone https://github.com/VanVan/linux.git
sudo apt-get install build-essential initramfs-tools fakeroot debconf-utils
dpkg-dev debhelper bin86 kernel-package
You can
It can't work if you install official kernel.
You need to replace the audio part by this one
https://github.com/endlessm/linux/tree/master/sound
So you need to compile it ny yourself.
The correction is not yet on official kernel, it can take time before
someone accept the pull request to the
Yes, I can confirm that bluetooth works well, but I hope we can find a
way to use internal sound, it's a good quality speaker for a small
laptop :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have the same issue on new Asus ZenBook 14 UX433FA (ALC294) on Ubuntu
2018.10 with Realtek ALC294.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784485
Title:
[ZenBook S UX391UA, Realtek ALC294,
** Changed in: initramfs-tools
Assignee: (unassigned) = vanvan (bartel-vanessa)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/798414
Title:
update-initramfs should produce a more helpful error
27 matches
Mail list logo
