An update on this. There have been a number of ipu6 driver
improvements and the web cam on my Lenovo X1 Gen 11 works some fraction
of the time. There *does* seem to be a timing problem with the hardware
and/or driver.
https://github.com/intel/ipu6-drivers/issues/187 proposes kernel patches
whic
Sorry, just trying to help by providing reports an following the rules.
I'll refrain from posting moving forward.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2061747
Title:
obsol
Thanks, I tried the NVidia kernel 6.8.0-1005.5+1 from noble-proposed;
still no detection. Could be that this predates that patch series? Not
sure.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchp
** Tags removed: verification-needed-noble
** Tags added: verification-failed-noble
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2061747
Title:
obsolete out-of-tree ivsc dkms in f
I did the followings steps:
- Added the noble-proposed repo
- Installed the driver(s) using: `sudo apt install
intel-ipu6-dkms/noble-proposed`
- Confirmed that the correct package was installed:
```
$ apt policy intel-ipu6-dkms
intel-ipu6-dkms:
Installed: 0~git202404110253.97c94720-0ubuntu1
C
I moved the driver file up a directory from /lib/firmware/intel/ipu to
/lib/firmware/intel and now the firmware appears to be loaded. But
something else is still wrong here:
[ 19.220279] intel-ipu6 :00:05.0: Device 0xa75d (rev: 0x0)
[ 19.220291] intel-ipu6 :00:05.0: physical base addr
Public bug reported:
I followed the suggestions here for handling the Intel MIPI camera
replacing 22.04 for 24.04: https://wiki.ubuntu.com/Lenovo
Perhaps I should have installed 22.04? Anyway, this is a new laptop so
I went with the new release.
I tried both the generic and oem kernel. Same.
This seems to be the same problem reported here:
https://bugzilla.redhat.com/show_bug.cgi?id=1506339
** Bug watch added: Red Hat Bugzilla #1506339
https://bugzilla.redhat.com/show_bug.cgi?id=1506339
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Attachment added: "kern.log containing a dead hang"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884546/+attachment/5387972/+files/kern.log.1
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.lau
** Attachment added: "syslog surrounding the dead hang"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884546/+attachment/5387971/+files/syslog.1
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.laun
I ran it until it happened again. I'm attaching the syslog and
kern.log from the time of the crash, which was Jun 28 at about 15:30.
Doesn't seem to be a lot to go on here . . .
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ub
This kernel also shows continuous rendering artifact on the native LCD
screen, such as the windows underneath the current active window appear
as flickering ghosts. No problems on the previous released kernel.
--
You received this bug notification because you are a member of Kernel
Packages, wh
Public bug reported:
This issue has been a persistent but infrequent problem for many years
with the T440s. It only occurs when the laptop is docked. I have
reported this bug several times. However, with the current kernel
release, 5.4.0-37, this occurs at least once a day. The kern.log lines
Some good and bad news: I have been testing this in a running Gnome 3
environment. I decided to start testing on console. On console, all
kernels seem to fail using crypt swap. This suggests to me that failure
must depend on current memory usage, dirty ratio, or some such runtime
condition.
How
In response to #7, I don't think this is the same issue. The cryptswap
initiates with no difficulties, timeouts, etc. on boot. When I first
installed Bionic, ubiquity did not correctly install the swap, and I
filed #1759253 on that issue.
--
You received this bug notification because you are a
BTW, I _do_ realize that you want a starting point for bisection; I'm
sorry this is turning out so messy.
On 04/11/2018 05:51 PM, Martin Weinberg wrote:
> The first kernel on that list that exhibits the bug is the first one:
> 4.14 Final. Recall: the bug results in a full up hang. The disk stop
The first kernel on that list that exhibits the bug is the first one:
4.14 Final. Recall: the bug results in a full up hang. The disk stops
swapping (it's audible). I can reboot with sysctl SUB however.
I then tested 4.13.0-36 from the Ubuntu 17.10 respoitory, followed by
4.11.12-041112-generi
Yes, the problem does occur in mainline 4.16 and I have added the
requested tag.
If anything, 4.16.1 seems slower than 4.15 release kernel even for no
cryptswap. It could be that my disk is too slow for cryptswap, but it
did work in 17.10.
The obvious work around is not to use cryptswap, of cour
It seems that cryptswap is working correctly on 17.10 with the kernel
4.13.0-36-generic on a different machine using the same test as
described above. I tried the same kernel (4.13.0-36) on 18.04 (machine
used in original post) and it still fails. Of course, I checked that
the swap appears in /pr
The code that I used to force failure, memtest.c, is attached to the bug
report.
--
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/1762468
Title:
Cryptoswap not working in Bionic
Status in
Public bug reported:
I have cryptoswap set up both with the 2 GB default swap file and an 8
GB swap partition with 8 GB of ram. However, the system does not use
this swap when it should. For example, if I run a little test code
which attempts to allocate 10 GB of memory in 1 GB chuncks, the syst
I am happy to report that linux-image-4.4.0-63-generic from xenial-
proposed _is_ working correctly with the T440s on and off the dock. So
the bug is gone from the -proposed kernel package.
Thanks for that!
If we could only get the DP audio to work on the dock, sigh. It hasn't
worked since Kern
Another thought: I'm using the modesetting driver, not the intel driver.
--
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/1662381
Title:
linux-image-4.4.0-62-generic breaks Lenovo T440s on
Also, and not sure if this is related, Plymouth does not correctly
render the splashscreen on boot up. Part way through, the screen blanks
and only the "dot icons" are visible. Again, this does not occur for
earlier kernels.
--
You received this bug notification because you are a member of Kern
Public bug reported:
When using with dock, attached monitor is not detected, laptop monitor
remains blank. Requires a reboot
4.4.0-59 works fine. I'm guessing this is due to the i915 patches for
DP.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-62-generic 4.4.0-62.83
That is correct. The default raring kernel will be very disappointing
for people that are experiencing the problems outlined in this thread.
It seems that only >3.9.7 has a usable kernel for affected Sandybridge
users (I am using a Lenovo X220). Even then, the bug remains at some
level but it mo
26 matches
Mail list logo
