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
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:
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:
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:
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:
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:
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1954320
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
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
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
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
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"
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
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
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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878279
Title:
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
@thatanonyg, thank you for the logs
@thatanonyg, and everyone else for who adding "pci=nocrs" to the kernel
commandline helps. I think I've figured out what is going on here and
the patch which I'm attach should help, but it needs to be tested.
If you can build a kernel with this patch added and
Ubuntu devs, if one of you could build a test-kernel with the patch
added for reporters to test, then that would be great.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878279
Title:
MSFT0004:00
@petterip:
> regarding 3/4 where exactly should I add the "pci=nocrs"
You should add this to the kernel commandline, see:
https://wiki.ubuntu.com/Kernel/KernelBootParameters
> regarding 4/4 what should I replace "" in order to run the cat
command?
You should not replace it; on laptop
Since root-cause 1/4 and 2/4 (of the 4 known root causes, see previous
comment) are fixed now I would like to focus on further researching
root-cause 3/4.
If adding "pci=nocrs" as a workaround helps to get your touchpad working
then please do the following:
1. Boot *without* "pci=nocrs" on the
Hi All,
So this is a bit of a mess which I'm trying to sort out ATM, there are
at least 4 different issues with Ideapad touchpads that I'm aware of:
1. There was a Linux ACPI issue where the resource-list (_CRS) for the touchpad
given to Linux was not correct, this has been fixed for a while
I've been debugging a similar issue together with a Fedora user:
https://bugzilla.redhat.com/show_bug.cgi?id=1871793
(note this bug is set to private atm, so you can likely not view this, I've
asked the reporter if it is ok to open it up)
I see some comments here about things no longer working
Sorry for being slow in getting back to you about this.
I believe that this should be fixed by this upstream commit, which will
be in the 5.12 kernel:
https://git.kernel.org/pub/scm/linux/kernel/git/hid/hid.git/commit/?h
=for-next=e037acf0b1aed31cb5f3b09ccb602b4768c133d5
--
You received this
@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
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:
So this seems to be a kernel issue. The hid-logitech-hidpp kernel driver
supports 2 battery reporting modes:
1. Status reporting, here the device basically reports 3 levels low /
normal / high
2. mileage reporting, this is where an actual percentage left gets
reported. I would expect at least
@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:
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
@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
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
@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 Ubuntu
Bugs, 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
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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
@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:
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
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
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
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
>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
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
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
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 Ubuntu
Bugs,
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=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:
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1728244
Title:
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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1728244
Title:
Touchpad stops working
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
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
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
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:
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1173681
Title:
168c:002b
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
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
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
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
@omriasta, no I'm afraid not.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1213239
Title:
Bluetooth subsystem dies after suspend
To manage notifications about this bug go to:
@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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1213239
Title:
Bluetooth subsystem dies after suspend
To manage
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1213239
Title:
Bluetooth subsystem dies after suspend
To manage
** 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 because
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
Patch has been added to the upstream v4l-utils git tree:
http://git.linuxtv.org/v4l-utils.git
And will be in the 0.8.4 release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/774123
Title:
Webcam
Hi all,
Short self intro: I'm a v4l kernel subsystem developer and the author
and maintainer of libv4l. So when it comes to upside down mounted
webcams in laptops there are 3 important points to keep in mind:
1) Video processing in the kernel is wrong, and the kernel patch which
some here have
I'm not an ubuntu contributor (not even a user), so you can best compile
it for yourself, the compile instructions are tested on ubuntu, so they
should work fine.
Note the above link is quite old now, please use:
http://people.fedoraproject.org/~jwrdegoede/libv4l-0.6.4-test.tar.gz
Install
Hi,
I'm the author of libv4l, I've fixed the DMI strings in my tree, you can
download a snapshot here:
http://people.atrpms.net/~hdegoede/libv4l-0.6.2-test.tar.gz
And there are testing instructions for installing from source here:
http://hansdegoede.livejournal.com/7622.html
Please let me know
Hi,
This is certainly not an ekiga bug (it will happen with any application), but
rather a hardware issue. The webcam has been
mounted upside down in the frame, the vendor probably solves this by providing
a custom driver which corrects this in software,
if you would use the default microsoft
I just hit the x86_64 compile problem too, here is a patch (also send
upstream).
** Attachment added: Patch fixing sysprof kernel module not compiling on
x86_64 with 2.6.27
http://launchpadlibrarian.net/19612228/sysprof-1.0.11-2.6.27-x86_64.patch
--
sysprof-module doesn't build
Hi,
I accidentally stumbled over this package request. I'm a Fedora contributer and
the Fedora packager of alex4, perhaps you can use some parts (patches, .desktop
file) from the Fedora package feel free to take what you need:
http://cvs.fedoraproject.org/viewcvs/devel/alex4/
--
package
72 matches
Mail list logo
