Reading this bug-report the issue seems to be that dell-uart-backlight
is non-functional in the 6.5.y kernels and completely missing in the
24.04 6.8.y kernels. While in Ubuntu 23.04 with its 6.2 kernel dell-
uart-backlight is present and functional.
The problem is that Canonical / Ubuntu wrote th
Note if someone wants to build a kernel with:
https://lore.kernel.org/linux-pci/20220512202511.34197-2-hdego...@redhat.com/
This patch applies on top of the 3 patches from:
https://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git/log/?h=pci/resource
--
You received this bug notification b
Sorry that it is taking so long to fix this. There have been several
attempts at fixing this upstream already, but all of them had to be
reverted/dropped because they were causing issues on other laptop
models.
The latest attempt at fixing this is here:
https://lore.kernel.org/linux-pci/2022051220
Sorry that it is taking so long to fix this. There have been several
attempts at fixing this upstream already, but all of them had to be
reverted/dropped because they were causing issues on other laptop
models.
The latest attempt at fixing this is here:
https://lore.kernel.org/linux-pci/2022051220
Sorry that it is taking so long to fix this. There have been several
attempts at fixing this upstream already, but all of them had to be
reverted/dropped because they were causing issues on other laptop
models.
The latest attempt at fixing this is here:
https://lore.kernel.org/linux-pci/2022051220
Sorry that it is taking so long to fix this. There have been several
attempts at fixing this upstream already, but all of them had to be
reverted/dropped because they were causing issues on other laptop
models.
The latest attempt at fixing this is here:
https://lore.kernel.org/linux-pci/2022051220
Sorry that it is taking so long to fix this. There have been several
attempts at fixing this upstream already, but all of them had to be
reverted/dropped because they were causing issues on other laptop
models.
The latest attempt at fixing this is here:
https://lore.kernel.org/linux-pci/2022051220
** Package changed: linux (Ubuntu) => initramfs-tools (Ubuntu)
** Changed in: initramfs-tools (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs
Note I've also filed a bug against initramfs-tools in Debian for this,
see: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001409
** Bug watch added: Debian Bug tracker #1001409
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001409
--
You received this bug notification because you ar
The component here should be initramfs-tools which I selected at the "Report a
bug" page, but I got at that page from the link at:
https://bugs.launchpad.net/ubuntu/+source/linux/ so I guess launchpad just
decided to ignore my answer to "In what package did you find this bug?",
because I came fr
Public bug reported:
Starting with kernel 5.17 the kernel supports the builtin privacy
screens built into the LCD panel of some new laptop models.
This means that the drm drivers will now return -EPROBE_DEFER from their
probe() method on models with a builtin privacy screen when the privacy
scree
Kai-Heng, thank you for providing the test kernel.
Folks, if you need to add pci=nocrs to your kernel-commandline to get
your touchpad to work, please test this kernel:
https://people.canonical.com/~khfeng/lp1878279/
With pci=no_e820 on the kernel commandline (replacing pci=nocrs). If the
touchp
Please test a kernel build with this patch, combined with adding
"pci=no_e820" added to the kernel commandline. See comment 133 for more
details.
** Patch added: "[PATCH] x86/PCI: Add pci=no_e820 cmdline option to ignore E820
reservations for bridge windows"
https://bugs.launchpad.net/ubunt
This is a follow-up to comment #123
Sorry for the long silence on this bug. I was hoping one of the upstream
pci-subsys devs would help out with this...
Since that did not happen I've been looking into fixing this myself now.
I've come up with a solution which still involves a kernel cmdline
opti
I just typed a long email in reply to someone asking about the keyboard
not working by email. The contents of that email are likely useful for
other people who are still experiencing the keyboard not working too, so
I've copy and pasted my entire reply below.
If you still need help with this pleas
I've been working with a Fedora reporter to try and solve the case where
pci=nocrs helps to get a working touchpad, see:
https://bugzilla.redhat.com/show_bug.cgi?id=1868899
Thanks to the latest set of logs attached there, I now am finally
starting to understand what is going on here.
Your BIOS c
Ratul, the patch which I attached won 't help you. The patch is
basically no good, because the problem is not what I thought it was.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe in Ubuntu.
https://bugs.launchpad.net/bug
Bernhard, no in the mean time I've learned that my patch is no good. I'm
currently debugging this with a Fedora user who also needs pci=nocrs to get the
touchpad to work:
https://bugzilla.redhat.com/show_bug.cgi?id=1868899
But this is going quite slow because the cycle between me providing the
u
@kaihengfeng, can you perhaps build a 5.9.xx kernel with:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d823346876a970522ff9e4d2b323c9b734dcc4de
added for @dacto from comment 25 to test ?
His device gets intel-vbtn SW_TABLET_MODE support enabled based on the
chassi
chassis_type 31 is "Convertible", so we expect the intel-vbtn
SW_TABLET_MODE reporting to work there.
There was one other HP model which had a bit of a weird issue, this was
fixed by:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d823346876a970522ff9e4d2b323c9b734d
@burritojohn, if you are seeing this on an Asus device then you are hit
by a different variant of what is in essence the same bug.
The Asus case is fixed by this upstream commit:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1797d588af15174d4a4e7159dac8c800538e4f8c
This has been fixed in the upstream 5.4.71 stable series release, so as
soon as the Ubuntu kernels pick up the fixes from that release then this
should be resolved.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://b
@tjaalton, note the fix which I originally wrote for this causes
regressions on some devices, a follow up fix is necessary, see:
https://lore.kernel.org/linux-i2c/20201014144158.18036-1-hdego...@redhat.com/
https://lore.kernel.org/linux-i2c/20201014144158.18036-2-hdego...@redhat.com/
--
You rece
I just got an email from gkh that both patches have also been added to
the various stable kernel series, including 5.4.x and 5.8.y, so they
should show up in the next stable series release for those kernels.
Thus if the Ubuntu kernel follows the stable series then this will get
fixed through that.
@handyboy, my fix for this has been merged by Linus for inclusion into
5.9. If one of the Ubuntu devs can add the 2 mentioned fixes to the next
20.04 kernel build then this issue should be resolved/fixed.
--
You received this bug notification because you are a member of Kernel
Packages, which is
For everyone who is seeing this issue with the intel-vbtn driver,
if you do:
cat /sys/class/dmi/id/chassis_type
On your laptop, and the output is NOT "31" or "32" then the
fix, which I linked above, should work for you.
If the output actually is "31" or "32 (which I do not expect),
then please l
This should be fixed by this upstream commit, which landed in Linus'
tree a couple of hours ago:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/platform/x86?id=8169bd3e6e193497cab781acddcff8fde5d0c416
Note for the Ubuntu kernel devs: a similar bug was introduced
Gaurav, did you reboot into the patched kernel?
And what is the output of "uname -r" in a terminal (after rebooting),
does that show that you are running the patched kernel now?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.
@ferenc-szabo, thank you for figuring out the issue with the _STA
method.
@kaihengfeng, it looks like we are both working on the same issue again
:)
I've written a simple, clean kernel patch fixing this, and I just got
confirmation from the reporter of:
https://bugzilla.redhat.com/show_bug.cgi?i
Hi All,
We (upstream kernel devs) are currently working with Realtek to get to
the bottom of this, once we know what the exact settings are which need
to be applied we can then add a quirk to the kernel to do this
automatically.
Realtek is asking for people with an affected laptop model to test t
Well the "[drm:intel_dsi_vbt_gpio_init [i915]] *ERROR* Failed to own
gpio for panel control" error is gone.
I just noticed you describe the problem as "blank screen with a cursor"
, I should have noticed this before. I assume with a cursor you mean a
mouse cursor (and not a Linux text console curs
p.s.
There is another issue with 5.5.y and 5.6 kernels on Cherry Trail
hardware, at least with Fedora I'm seeing regular GPU freezes; and
specifically on the T100HAN also spontaneous reboots. I've seen the GPU
freezes on multiple Cherry Trail devices (these require ssh-ing in and
killing gnome-she
I have a T100HAN in my personal hw collection, so I just booted up a
nightly build of the Fedora 32 workstation livecd on it and that works
fine for me. This nightly build is using a 5.6 kernel.
So the 5.6 kernel can work on this hardware. AFAIK Ubuntu, like Fedora
puts the i915 driver in the init
>From the original report:
"When the device is under load and more than 1 hardrive is acessed, the
USB enclosure frequently restarts."
So this very much sounds like a hardware problem. UAS allows having
multiple outstanding commands (read/write requests) and thus *actually*
accessing multiple dis
Robert,
There are some patches pending upstream to fix the "incomplete report"
errors in the mean time these can be safely ignored.
As for you needing to do a 2-finger-click to get a right click, that
means that libinput is configured for clickfinger behavior rather then
click areas.
To change t
Good news (hopefully) it looks like we finally have found a fix which is
not an ugly hack / does not disable runtime pm for other devices which
will hopefully fix this.
Kai-Heng Feng, can you build a kernel with this patch:
https://patchwork.kernel.org/patch/10597519/
Added for reporters of this
David Perez Millan,
Please run gnome-tweaks and go to: "Keyboard & Mouse" then under "Mouse
Click Emulation" select "Area" that should give you a right click at the
bottom right area of the touchpad.
Regards,
Hans
--
You received this bug notification because you are a member of Kernel
Package
Olivier, thank you excellent work. I've mailed the upstream developers
and the author of the patch of which the older version fixes things.
Kai-Heng, can you perhaps do a test Ubuntu kernel build with the patch
from comment 158, then other users with different (but similar) model
laptops can test
Olivier Fock,
Thanks, so it seems that:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/base?h=v4.14-rc7&id=0cc2b4e5a020fc7f4d1795741c116c983e9467d7
on top of 4.17-rc8 fixes things again, that is very interesting.
You may want to try a recent kernel and then do:
What would also be helpful is an acpidump of your Thomson X6 as well the
output of:
ls -l /sys/bus/i2c/devices
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1728244
Title:
Touchpad sto
Olivier Fock,
Thanks for your work on this, that is some excellent detective work.
Also good to know that the "incomplete report" errors are also happening
in a working setup.
The buttons starting to work after you updating the drivers/hid
directory is expected, I have done several fixes to the h
And a dmesg directly after boot with the non-working 4.14-rc7 + another
one with the working 4.14-rc8 based one would also be good.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1728244
T
Can people with this problem please boot with:
i2c_designware_core.dyndbg=+p i2c-hid.debug=1
Added to their kernel commandline and then directly after boot run:
dmesg > dmesg.log
And attach the generated dmesg.log file here?
--
You received this bug notification because you are a member of Ke
Hi Bart,
In your previous comment you set that linux-
image-4.14.0-997-generic_4.14.0-997.201712022100_amd64.deb is working,
now you say that 4.14.0-041400rc7 is the latest working, and that 4.14
final does not work? linux-
image-4.14.0-997-generic_4.14.0-997.201712022100_amd64.deb sounds like
it
Hi All,
So several people here are reporting that touch is not working for them
at all, starting with 4.15 kernels, where as 4.14 works but does not
have working buttons. The buttons thing is known and fixed (I believe),
but that is of little help if touch no longer works at all.
I've a feeling t
Hi All,
Clicking the 0911:5288 clickpad not sending button events is a known and
fixed issue, this is fixed by the following 3 commits:
"HID: multitouch: Properly deal with Win8 PTP reports with 0 touches"
"HID: multitouch: Only look at non touch fields in first packet of a frame"
"HID: multitouc
Hi Kanwir,
I understand that Fn+F2 does not work at all, that is a known issue with
Asus laptops.
But does the wifi not show as hardblocked, and work as expected with the
"options asus_nb_wmi wapf=4" workaround ? I'm asking because if you
need the wapf=4 workaround then I'll add a quirk for your
André,
Thanks for the info, I've send a patch upstream to get a quirk for this
added to the upstream kernel.
Regards,
Hans
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1173681
Title:
Hi All,
I'm an upstream kernel developer who happened to stumble over this bug.
The proper solution here is to add a dmi based quirk to the asus-nb-wmi
driver to use wapf=4 by default. Note the wapf=4 not wapf=1 which
everyone has been testing with sofar.
I would like to add a proper fix for this
Hi,
Fixing this is non trivial, supporting these new touchpads likely needs
a signicant amount of work (for details see
https://bugzilla.redhat.com/show_bug.cgi?id=1110011 ).
In the mean time, I can provide a workaround which should make the
touchpad work in ps/2 mouse emulation mode (so no 2 fi
Hi,
Fixing this is non trivial, supporting these new touchpads likely needs
a signicant amount of work (for details see
https://bugzilla.redhat.com/show_bug.cgi?id=1110011 ).
In the mean time, I can provide a workaround which should make the
touchpad work in ps/2 mouse emulation mode (so no 2 fi
@omriasta, no I'm afraid not.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1213239
Title:
Bluetooth subsystem dies after suspend
Status in “linux” package in Ubuntu:
Confirmed
Bug
@Joseph,
I'm sorry I was wrong it is not upstream yet. I was on the wrong git branch
when I checked. It has been accepted into bluetooth.git:
http://git.kernel.org/cgit/linux/kernel/git/bluetooth/bluetooth.git
But it has not found its way into Linus' tree yet.
Regards,
Hans
--
You received t
p.s. note that the patch in question has already been merged into
3.12-rc4
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1213239
Title:
Bluetooth subsystem dies after suspend
Status in
As I already mentioned in comment #11 I've a patch fixing this, see
comment #11.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1213239
Title:
Bluetooth subsystem dies after suspend
Sta
Hi all,
I just hit the same problem, and I've managed to fix it for my case
(Dell E6430 laptop with integrated bluetooth).
I've had exactly the same experience as Till, in that 3.11 caused bt to
no longer work after a suspend/resume for me. I'm surprised to hear that
the problem has magically gon
** Patch added: "PATCH: Regression fix revert: "Bluetooth: Add missing
reset_resume dev_pm_ops""
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1213239/+attachment/3847175/+files/0001-Regression-fix-revert-Bluetooth-Add-missing-reset_re.patch
--
You received this bug notification beca
57 matches
Mail list logo
