Just try to dig in the root cause and explain the difference between
alsa-hda-realtek-patched-dkms v1.0 and v1.1.
Looks like the new kernel changes some code in snd-hda, so that makes the
kernel module produced by the dkms package becomes doesn't match with other
snd-hda modules come with
Public bug reported:
In some of Dell laptops, they support a touchpad LED to indicate the
enablement/disablement of the touchpad.
And kernel(after 3.2) supports an interface to turn on/off the LED, user space
app should take the responsibility to handle this,
and I think gnome-settings-daemon
Hi,
I'm trying to build a patch for this issue, but I encountered some
problems.
1. The permission of the file in sysfs is 0644, so gsd(gnome-settings-daemon)
should have root privilege to access the file.
-rw-r--r-- 1 root root 4096 Jan 13 17:04
I fixed the problem to persist the LED status after S3 in the driver, but I
still have no idea how to let user space application access the sysfs without
root privilege.
And I don't think it's suitable to change the file mode to 0666, for I can't
find any file with that mode in sysfs.
--
You
Yes, I'll submit SRU to the kernel team to cherry pick those patches.
But, we still don't have a good way in userspace to cooperate with the kernel
driver.
It just comes to my mind, maybe ubuntu kernel team will accept the way turning
on/off touchpad LED in the driver until we have a better way
Hi,
In Precise kernel, it already provided an interface to turn on/off the
tourchpad LED
/sys/class/leds/dell-laptop::touchpad/brightness
Other patches are just quirks to add more machines to have this
interface, so I don't think it's so urgent.
The problem is that there is no userspace app
I submitted the 2 patches mentioned in #6 to stable kernel,
so they will go into precise kernel at next merge.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/914348
Public bug reported:
For all ASUS machines, it will only notify the userspace app by udev event
while the brightness value is changed, instead of keyevent.
The procedure in the asus-wmi kernel module is as described below
1. receive the keyevent from WMI
2. if the brightness event is not handled
I also filed a bug on upstream.
https://bugzilla.gnome.org/show_bug.cgi?id=672380
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/959106
Title:
brightness changing
Hi, I'm wondering if this issue still happened while using Precise(12.04)
kernel.
From what I heard, this issue might result from that kernel didn't send out
the drm ready event.
So, it's possible that this issue is fixed by the newer kernel.
--
You received this bug notification because you
Great, I just cherry-picked some patches and built a new kernel
Could you guys try to see if those patches fix the issue?
Thanks
http://people.canonical.com/~acelan/bugs/lp873495/
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/838543
Title:
False battery warning
** Also affects: unity-settings-daemon (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/838543
Title:
False battery
Hi all,
I encountered this issue, too, and I would like to know if this patch help.
You can download the kernel packages from this link, this kernel will retry to
get the battery inform after wakeup from S3.
Thanks.
http://people.canonical.com/~acelan/bugs/lp838543
--
You received this bug
** Package changed: unity-settings-daemon (Ubuntu) = linux (Ubuntu)
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = AceLan Kao (acelankao)
** Changed in: linux (Ubuntu)
Status: New = In Progress
--
You received this bug notification because you are a member of Desktop
I re-upload the kernel today, it works well for me, so I think it should
fix your issue as well.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/838543
Title:
False
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = AceLan Kao (acelankao)
** Changed in: linux (Ubuntu)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https
Hi,
I just built a asus-wmi dkms package, I think it should work for you.
Try installing it and reboot the system to see if it works.
sudo dpkg -i asus-wmi-dkms_1.0_all.deb
If not, I need some other logs hope you can attach them to me.
1. the result of rfkill list command, and then press the
For the unknown reason, the dkms package I built may not be able to install,
so I attached the source code here as well.
Following commands to use it
1. tar -zxvf asus-wmi-1.0.tgz
2. sudo cp -a asus-wmi-1.0 /usr/src
3. sudo apt-get install dkms
4. sudo dkms add -m asus-wmi -v 1.0
5. sudo dkms
Correct.
BTW, blacklist asus-nb-wmi will make hotkeys stop working, such as brightness
adjustment.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1172151
Title:
ASUS F75A
Cool, good to hear the dkms works for you.
And the fix is too late to enter the 13.04 release.
Anyway, I'll submit the fix to mainstream kernel, so that the next ubuntu
release will have the fix.
Thanks for your report and test.
--
You received this bug notification because you are a member of
** Changed in: linux (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1172151
Title:
ASUS F75A wi-fi disabled by hardware
After installed those package from proposed repository, it can enable
the chip and run on unity 3D.
linux-image-3.5.0-36-generic libgl1-mesa-glx-lts-quantal libglapi-mesa-
lts-quantal libgl1-mesa-dri-lts-quantal libdrm2 xserver-xorg-video-
intel-lts-quantal
** Tags removed: verification-needed
After installed those package from proposed repository, it can enable
the chip and run on unity 3D.
linux-image-3.5.0-36-generic libgl1-mesa-glx-lts-quantal libglapi-mesa-
lts-quantal libgl1-mesa-dri-lts-quantal libdrm2 xserver-xorg-video-
intel-lts-quantal
--
You received this bug notification
** Tags added: blocks-hwcert-enablement
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs.launchpad.net/bugs/1180881
Title:
Touchscreen only works after suspend/resume on Lenovo ideapad
More finding, if suspend/resume doesn't work for you, try the following steps
cd /sys/devices/pci:00
find -name control | xargs -I '{}' sudo sh -c echo on '{}'
sudo pm-suspend
It will turn on the power for all devices, more precisely you can just turn on
the usb host chip's power
It's confirmed that it's a Synaptics firmware bug, and the new firmware can fix
it.
It works for my device, the usb id is 06CB:0AF8
I'm not sure if it'll work or damage other devices, so use it at your own risk.
** Attachment added: PR1507220.zip
The above test result is wrong, the touchscreen function is not always
working.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs.launchpad.net/bugs/1180881
Title:
Touchscreen only works
add the following lines in /etc/rc.local could wake up the touch screen, it
works every time after booting up.
Or, you can run it manually to check if the commands work.
sudo rmmod hid_multitouch ; sudo modprobe hid-multitouch ; find
/sys/bus/usb/devices/2-3 -name control | xargs -I '{}' sudo
** Changed in: xserver-xorg-input-evdev (Ubuntu)
Status: Confirmed = In Progress
** Changed in: xserver-xorg-input-evdev (Ubuntu)
Assignee: (unassigned) = AceLan Kao (acelankao)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
Using wireshark to monitor the usb traffic, we'll find the touchscreen becomes
abnormal after systems sends the IDLE command to it.
But the touchscreen could revive after sending some other commands, such as
GET_DESCRIPTOR.
I'll build a test driver soon, but I need to build a list for the
Hi unix25, thanks a lot.
But, looks like your touchscreen chip is not Synaptics, I don't know if the
solution apply to SiS' chip.
I got a new way to test.
# cat /etc/modprobe.d/usbhid.conf
options usbhid quirks=0x06cb:0x0af8:0x2000
# sudo update-initramfs -u
# sudo reboot
unix25,
Good to know that.
I'll build a patch for your device, so that linux kernel can support the SiS
touchscreen.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu.
Those 2 patches had submitted
** Patch added: 0002-HID-usbhid-quirk-for-SiS-Touchscreen.patch
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1180881/+attachment/3856404/+files/0002-HID-usbhid-quirk-for-SiS-Touchscreen.patch
** Changed in: xserver-xorg-input-evdev
** Patch added: 0001-HID-usbhid-quirk-for-Synaptics-Large-Touchccreen.patch
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1180881/+attachment/3856403/+files/0001-HID-usbhid-quirk-for-Synaptics-Large-Touchccreen.patch
--
You received this bug notification because you
** Tags removed: verification-needed-saucy
** Tags added: verification-done-saucy
** Changed in: hwe-next/saucy
Status: Confirmed = Fix Committed
** Changed in: hwe-next/trusty
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of
Hi, I tested it on Dell OptiPlex 9030 AIO with 64-bit Ubuntu 14.04, but it
doesn't work.
The touchscreen remaps to the whole extended screen.
I tried to re-login, reboot the system, and re-plug the hdmi cable, the symptom
is the same.
ii unity-settings-daemon
14.04.0+14.04.20140414-0ubuntu1.1
Here comes the logs
** Attachment added: logs_optiplex_9093.tgz
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1287341/+attachment/4121989/+files/logs_optiplex_9093.tgz
--
You received this bug notification because you are a member of Desktop
Packages, which is
** Attachment added: mylog.log
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1287341/+attachment/4121993/+files/mylog.log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-settings-daemon in Ubuntu.
** Attachment added: xrandr.log
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1287341/+attachment/4121995/+files/xrandr.log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-settings-daemon in Ubuntu.
Tested on Dell Inspiron 20 Model 3048, it works well.
** Attachment added: inspiron_20_model_3048.tgz
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1287341/+attachment/4122493/+files/inspiron_20_model_3048.tgz
--
You received this bug notification because you are a
Here comes the Inspiron 2350 AIO log
** Attachment added: inspiron-2350.tgz
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1287341/+attachment/4122771/+files/inspiron-2350.tgz
--
You received this bug notification because you are a member of Desktop
Packages, which is
** Attachment added: xrandr_optiplex_9030.log
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1287341/+attachment/4122776/+files/xrandr_optiplex_9030.log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
** Attachment added: usd_optiplex_9030.log
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1287341/+attachment/4124537/+files/usd_optiplex_9030.log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
** Attachment added: usd_inspiron_2350.log
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1287341/+attachment/4124570/+files/usd_inspiron_2350.log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
The latest unity-settings-daemon fix this issue on Dell OptiPlex 9030.
The touchscreen works well when connects an external monitor and it still works
well after rotate the screen.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
It works on Dell OptiPlex 9030 AIO
** Attachment added: usd_optiplex_9030.2.log
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1287341/+attachment/4125177/+files/usd_optiplex_9030.2.log
--
You received this bug notification because you are a member of Desktop
Packages,
** Attachment added: usd_optiplex_9030.3.log
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1287341/+attachment/4125215/+files/usd_optiplex_9030.3.log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
** Changed in: linux (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/838543
Title:
False battery warning +suspend
It's pretty like a hardware issue to me, I'll try to find the hardware
to verify it next week.
** Changed in: alsa-driver (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in
** Changed in: linux (Ubuntu Vivid)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1646537
Title:
Backlight sometimes fails to resume from
Found another machine and restored the factory image, but still can't
reproduce this issue.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1646537
Title:
Backlight sometimes fails to
For Dell XPS, try remove pinctrl_sunrisepoint driver, it should work.
sudo rmmod pinctrl_sunrisepoint
There is a discussion and a patch for this issue here
https://bugzilla.kernel.org/show_bug.cgi?id=176361
** Bug watch added: Linux Kernel Bug Tracker #176361
I got the same machine and restored the system to factory image.
After doing some check and write some intel reg value for testing, then I can't
reproduce this issue any more, even do a cold boot or restore the image again.
BTW, the patched kernel on #4 seems doesn't help.
--
You received this
The 2 i915 patches can't be backported to 3.19 kernel, so I use another way to
archive the same function.
The test kernel could be found here, I'll try to see if we could find a machine
here to verify it.
http://people.canonical.com/~acelan/bugs/lp1646537/
** Changed in: linux (Ubuntu Vivid)
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1821863
Title:
Need to add Intel CML related pci-id's
** Changed in: linux-oem (Ubuntu Bionic)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1882248
Title:
plug headset won't proper reconfig ouput
Confirmed with fresh installed Jammy release(5.15.0-23). After the
screen dim, the backlight power is off,
"/sys/class/backlight/intel_backlight/bl_power", and can't echo 0 to it
to light up.
Switch vt(ctrl+alt+F1) works, and then I can turn off and turn on the backlight
by
echo 4 | sudo tee
Can't reproduce this issue with KDE.
And can't boot up the machine with mainline kernel. So, it's hard to bisect if
it's a kernel issue.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
Thanks Timo, this series of patches seems fix this issue
https://www.spinics.net/lists/intel-gfx/msg284609.html
Here is the test kernel, I can't reproduce the issue with this kernel.
https://people.canonical.com/~acelan/bugs/lp1967274/
I'll submit SRU soon.
--
You received this bug
** Also affects: linux (Ubuntu Jammy)
Importance: High
Status: In Progress
** Also affects: mutter (Ubuntu Jammy)
Importance: High
Assignee: Daniel van Vugt (vanvugt)
Status: Fix Committed
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => AceLan
** Description changed:
Screen can't turn back on by clicking keyboard after screen off by meta + l
key.
Try to do VT switch can make the screen back, some error poped when I try to
wake up screen.
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
SRU sent
https://lists.ubuntu.com/archives/kernel-team/2022-April/129627.html
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1967274
Title:
Screen sometimes can't update on Intel
I can reproduce this issue, too.
When plug in the dock(with HDMI 4k monitor), the screen freeze and
keyboard/touchpad won't work, but I still can ssh into the machine.
Un-plug the dock, everything works again.
BTW, I found gnome-shell runs in 100% while the issue happened, and un-
plug the dock
** Changed in: linux (Ubuntu)
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1967274
Title:
Screen sometimes can't update on Intel Alder Lake
*** This bug is a duplicate of bug 1999008 ***
https://bugs.launchpad.net/bugs/1999008
Right, I updated the check, will verify it again, thanks.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
*** This bug is a duplicate of bug 1999008 ***
https://bugs.launchpad.net/bugs/1999008
Hi Markus,
Thanks for reporting the preferred issue, I'll submit new MR soon.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in
Adopt the fix by Markus on bug 1999852
Verified it on my laptop, it works, and will verify more sku and the target
2.5k panel with 90Hz machines later.
** Patch added: "0001-hw-xfree86-re-calculate-the-clock-and-refresh-rate.patch"
Add back the check for xf86ModeVRefresh() returns 0, the patch works on my
laptop and the target 2.5k 90Hz panel.
Will submit another MR soon.
** Patch added: "0001-hw-xfree86-re-calculate-the-clock-and-refresh-rate.patch"
https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/993
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1999008
Title:
Xorg crashed with SIGABRT in xf86ModeVRefresh()
Upgraded Jammy to xserver-xorg-core 2:21.1.3-2ubuntu2.4, switching to
different resolutions work well.
Upgrade Kinetic to xserver-xorg-core 2:21.1.4-2ubuntu1.2, switching to
different resolutions also work well.
** Tags removed: verification-needed-jammy verification-needed-kinetic
** Tags
Updated xserver-xorg-core to 21.1.4-2ubuntu1.4(kinetic) with the same
test on comment #14, toggle display works
ii xserver-xorg-core 2:21.1.4-2ubuntu1.4
amd64Xorg X server - core server
** Tags removed: verification-needed verification-needed-kinetic
** Tags
xserver-xorg-core 21.1.3-2ubuntu2.5
1. power off the machine
2. connect DP monitor on the dock
3. plug the dock type-c cable to the machine
4. waiting the machine auto bootup, and no output on the DP monitor
5. no external monitor found in display menu
updated xserver-xorg-core to
ulate-the-clock-and-refresh-rate.patch"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1996490/+attachment/5630714/+files/0001-hw-xfree86-re-calculate-the-clock-and-refresh-rate.patch
** Changed in: xorg-server (Ubuntu Jammy)
Assignee: (unassigned) => AceLan K
** Affects: xorg-server (Ubuntu)
Importance: Undecided
Assignee: AceLan Kao (acelankao)
Status: In Progress
** Affects: xorg-server (Ubuntu Jammy)
Importance: Undecided
Assignee: AceLan Kao (acelankao)
Status: In Progress
** Affects: xorg-server (Ubuntu Kinetic
76 matches
Mail list logo
