https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037005 contained
commit 69ea4c9d02b7 ("ALSA: hda/realtek - remove 3k pull low
procedure"), and
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039110 contained
commit 46cdff2369cb ("ALSA: hda/realtek - Remodified 3k pull low
procedure").
All autopkgtests for the newly accepted linux-restricted-modules
(5.15.0-94.104) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.2 (armhf)
Please visit the excuses page listed
This pulls following commits as well due to dependency:
$ git show d1dc30480fef478b06827a428970ef5d763ed76e
commit d1dc30480fef478b06827a428970ef5d763ed76e
Author: Kalle Valo
Date: Wed Apr 5 15:56:21 2023 +0300
ath11k: WCN6855 hw2.0: update board-2.bin
Signed-off-by: Kalle Valo
Public bug reported:
Due to a known silicon limitation, the following sequence is needed
while initialing the PCIE device on a certain devices with ASMedia
chipset involved:
1. 'hot reset' assert
2. 2nd PCIe reset' assert
3. Asmedia 'hot reset' deassert
4. PT21 GPIO13 2nd PCIe reset' deassert.
Public bug reported:
When running an SVA case, the following soft lockup is triggered:
watchdog: BUG: soft lockup - CPU#244 stuck for 26s!
pstate: 8349 (Nzcv daif +PAN -UAO +TCO +DIT -SSBS BTYPE=--)
pc :
This bug is awaiting verification that the linux/5.15.0-94.104 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-jammy-linux' to 'verification-done-jammy-linux'. If
the problem still
This bug is awaiting verification that the linux/5.15.0-94.104 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-jammy-linux' to 'verification-done-jammy-linux'. If
the problem still
This bug is awaiting verification that the linux/5.15.0-94.104 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-jammy-linux' to 'verification-done-jammy-linux'. If
the problem still
This bug is awaiting verification that the linux/5.15.0-94.104 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-jammy-linux' to 'verification-done-jammy-linux'. If
the problem still
This bug is awaiting verification that the linux/5.15.0-94.104 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-jammy-linux' to 'verification-done-jammy-linux'. If
the problem still
All autopkgtests for the newly accepted linux-meta (5.15.0.93.90) for jammy
have finished running.
The following regressions have been reported in tests triggered by the package:
diffoscope/205 (armhf)
nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.2 (armhf)
Please visit the excuses page
Additionally: my understanding is that the corruption fix is minimally
invasive and should be easy to backport. Should we quickly do such a
minimal backport to get that fix out quickly, and then have less
pressure to handle the hardware enablement kernel quickly?
--
You received this bug
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Sounds like it was fixed in kernels 6.6 and 6.5.4
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/2048827
Title:
[amdgpu] Mouse cursor theme is grey instead of black
Status in
See also:
https://gitlab.freedesktop.org/drm/amd/-/issues/2803
https://gitlab.freedesktop.org/drm/amd/-/issues/1513
** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #2803
https://gitlab.freedesktop.org/drm/amd/-/issues/2803
** Bug watch added:
Zooming in on the cursor images in GIMP I find they do contain gradients
- both Yaru and DMZ-Black. Therefore some greyness is correct.
I think the remaining bug here is that either the kernel (amdgpu) or
mutter is under-saturating the cursor plane with an alpha component
below 1.0. That's why I
You have been subscribed to a public bug:
- this is a fresh install of the latest Ubuntu 24.04
- I have fully updated the debs and snaps
- my mouse cursor is grey when it should be black
- the strange thing is the cursor looks normal when I boot off the USB
and then looks grey on first boot
-
> Force pushing my local commits over, sorry not sorry. :)
Yeah it's fine this time. :)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2047780
Title:
BlueZ release 5.71
Status in
I was able to find one single line that syslog server was able to catch:
[ 353.589347] BUG: kernel NULL pointer dereference, address: 0008
I guess it doesn't give a lot of information...
--
You received this bug notification because you are a member of Kernel
Packages, which is
> Simon, ell already has a recent approved MIR LP: #1971738
Er, the binary packages in question don't.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2047780
Title:
BlueZ release 5.71
> Please also remember to commit proposed changes to
https://git.launchpad.net/~bluetooth/bluez
Force pushing my local commits over, sorry not sorry. :)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
I'm pretty shocked, I ran a local sbuild with this and yet it still
FTBFS. Doing an ubuntu2 upload as a fixup.
I would think that because we use the published tarball and not the
upstream source like Debian does, that would affect our ability to ship
the -test package.
Something's up with my
BTW, having the previous Ubuntu version 5.71-0ubuntu3 on line 415 of the
changelog doesn't feel ideal for people wanting to read the Ubuntu
release history.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
Ideally please open a new bug for the merge. This bug should remain Fix
Released because we're already past the point in time when it was
released to Noble.
Please also remember to commit proposed changes to
https://git.launchpad.net/~bluetooth/bluez
** Changed in: bluez (Ubuntu)
Status:
Simon, ell already has a recent approved MIR LP: #1971738
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2047780
Title:
BlueZ release 5.71 and merge from Debian
Status in bluez package
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.5/+bug/2048951/+attachment/5738249/+files/dmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-hwe-6.5 in Ubuntu.
** Attachment added: "lsb_release.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.5/+bug/2048951/+attachment/5738250/+files/lsb_release.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-hwe-6.5 in Ubuntu.
At first I was just going to say, ell-dev isn't built on i386 and it's
not arch:all, of course it will need an i386 allowlist entry! However,
this is the output I'm getting:
```
$ check-mir
Checking support status of build dependencies...
* debhelper-compat does not exist (pure virtual?)
*
** Attachment added: "dmidecode.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.5/+bug/2048951/+attachment/5738246/+files/dmidecode.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-hwe-6.5 in Ubuntu.
** Attachment added: "lspci.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.5/+bug/2048951/+attachment/5738247/+files/lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-hwe-6.5 in Ubuntu.
** Attachment added: "lsusb.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.5/+bug/2048951/+attachment/5738248/+files/lsusb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-hwe-6.5 in Ubuntu.
Public bug reported:
Today one of my NUCs got new kernel 6.5.0-14 and the host started to hang few
minutes after the boot.
I can't find anything in the journal for the previous boot it just ends without
any error. Remote syslog server does not receive any error log from this host.
I've tried
Launchpad has imported 11 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=217914.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/2048945/+attachment/5738224/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.5 in Ubuntu.
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/2048945/+attachment/5738228/+files/acpidump.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.5 in Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/2048945/+attachment/5738227/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.5 in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/2048945/+attachment/5738226/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.5 in Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/2048945/+attachment/5738219/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.5 in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/2048945/+attachment/5738222/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.5 in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2048945/+attachment/5738223/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.5 in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/2048945/+attachment/5738225/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.5 in Ubuntu.
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/2048945/+attachment/5738221/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.5 in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/2048945/+attachment/5738220/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.5 in Ubuntu.
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2048945/+attachment/5738218/+files/ProcCpuinfoMinimal.txt
** Description changed:
Possibly related to https://lkml.kernel.org/linux-
scsi/7611d95d0aada3814a5b140661b3b5188b8b86bb.ca...@redhat.com/T/
** Also affects: linux-aws-6.5 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-hwe-6.5 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-meta-hwe-6.5 (Ubuntu)
Importance: Undecided
Status: New
** Tags added: apport-collected
Public bug reported:
Possibly related to https://lkml.kernel.org/linux-
scsi/7611d95d0aada3814a5b140661b3b5188b8b86bb.ca...@redhat.com/T/
Getting alerts from monitoring tools about high average CPU usage.
Machine reporting the following:
root@server:~# uptime
17:04:34 up 14 days, 6:33, 2
Few hours after posting I got the 6.5.0-14-generic update.
So I'll test it out for a while and see if the issue persists or if it's fixed.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe in Ubuntu.
Public bug reported:
Linux kernel commit ebddb1404900 ("net: move the nat function to
nf_nat_ovs for ovs and tc") introduced a regression into the kernel
openvswitch datapath which prevented the match key from being updated
when nat was undone for packets in the related conntrack state. This
Public bug reported:
After upgrading from the previous HWE kernel 6.2.0-39-generic to the new
HWE kernel 6.5.0-14-generic, the right speaker no longer works. When
booting back into the old HWE kernel, the right speaker functions again.
The left speaker works in both cases.
Hardware info:
Dell
3 years is a long time not to fix a basic sleep problem...
--
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/1909005
Title:
[Dell Inspiron 3593] Ubuntu does not resume (wake up) from
** Changed in: bluez (Ubuntu)
Status: Fix Released => In Progress
** Summary changed:
- BlueZ release 5.71
+ BlueZ release 5.71 and merge from Debian
** Changed in: bluez (Ubuntu)
Assignee: Daniel van Vugt (vanvugt) => Simon Quigley (tsimonq2)
--
You received this bug notification
Public bug reported:
driver bug while update
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: nvidia-dkms-390 390.157-0ubuntu0.22.04.2
ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
AptOrdering:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu)
Status: New => 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/2048915
This issue persists on 5.15.0-91
--
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/2016388
Title:
Kernel Panic on shutdown / reboot on NUC8I3BEH
Status in linux package in Ubuntu:
two patches are now with Debian bugs
Opened #1060393 in bluez 5.67-1 by Gianfranco Costamagna (locutusofborg)
«please update patch
work-around-Logitech-diNovo-Edge-keyboard-firmware-i.patch».
https://bugs.debian.org/1060393
Opened #1060395 in bluez by Gianfranco Costamagna (locutusofborg)
and ell-dev needs a i386 whitelist, not sure
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2047780
Title:
BlueZ release 5.71
Status in bluez package in Ubuntu:
Fix Released
Bug
** Information type changed from Private Security to Public
--
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/2048504
Title:
package linux-headers-6.2.0-39-generic 6.2.0-39.40 failed to
Public bug reported:
---Problem Description---
Regression: uvdevice at /dev/uv not compiled into kernel
Machine Type = IBM z15, IBM z16
Contact Information = steffen.ei...@ibm.com
---uname output---
Linux 6.5.0-14-generic #14-Ubuntu SMP Tue Nov 14 14:16:58 UTC 2023 s390x s390x
s390x
You have been subscribed to a public bug:
---Problem Description---
Regression: uvdevice at /dev/uv not compiled into kernel
Machine Type = IBM z15, IBM z16
Contact Information = steffen.ei...@ibm.com
---uname output---
Linux 6.5.0-14-generic #14-Ubuntu SMP Tue Nov 14 14:16:58 UTC 2023
Hello, I did the merge from Debian, now the packaging is really simpler,
please have a look and upload if possible.
** Attachment added: "bluez_5.71-1ubuntu1.debian.tar.xz"
Yikes.
With old linux-modules:
-rw-r--r-- 1 root root 29622096 Oct 11 22:55 initrd.img-6.5.0-1005-raspi
With new linux-modules:
-rw-r--r-- 1 root root 61907522 Jan 10 16:54 initrd.img-6.5.0-1008-raspi
--
You received this bug notification because you are a member of Kernel
Packages, which is
Public bug reported:
With the modules-extra package removed, a ton of additional modules are
installed and lots of them end up in the initrd, blowing it up in size.
We need to shrink it.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Noble)
Can you remove 'quiet' and 'splash' from the kernel commandline and
reboot into the broken kernel? That should give some console messages.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is
uploaded, thanks
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2041800
Title:
[needs-packaging] usbio-drivers
Status in Ubuntu:
In Progress
Status in linux-oem-6.5 package
Testing looks good from our side. When we have fixes how should we
request they are integrated? A new launchpad bug with a list of
upstream fixes that should be backported?
** Tags removed: verification-needed-mantic-linux
** Tags added: verification-done-mantic-linux
--
You received this bug
** No longer affects: nvidia-graphics-drivers-535 (Ubuntu Focal)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu.
https://bugs.launchpad.net/bugs/2042426
Title:
Introduce the new NVIDIA 545 driver
Public bug reported:
it crashes after kernel update
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: nvidia-dkms-535 535.129.03-0ubuntu0.22.04.1
ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
** Changed in: nvidia-graphics-drivers-535-server (Ubuntu)
Status: Triaged => Invalid
** Changed in: nvidia-graphics-drivers-535-server (Ubuntu Focal)
Status: New => Invalid
** Changed in: nvidia-graphics-drivers-535-server (Ubuntu Jammy)
Status: New => Invalid
** Changed
** Attachment added: "make.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2048796/+attachment/5738071/+files/make.log
--
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/2048796
The previous kernel version was 6.5.0-14-generic. The full output, after
I remove all the mentioned packages and try to reinstall them, is
attached in updateoutput. I do have a dkms module installed, dkms status
outputs evdi/1.14.1, 6.5.0-14-generic, x86_64. The output from apt also
says to check
*** This bug is a duplicate of bug 2036135 ***
https://bugs.launchpad.net/bugs/2036135
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #2036135, so is being marked as such.
I'm on 6.2.0-39-generic (Ubuntu 22.04) and have started to get touchpad
problems(I believe around September 2023).
Touchpad often stops responding after having the laptop(Lenovo Yoga slim
14ARE05) on for a while.
A full shutdown + waiting for a while and starting the laptop again
makes the
Hey @Christian,
1a) No need, AQ 0x000A returns NVM capabilities regardless of configuration
applied (it's done during driver init)
1b) That's the point, I noticed you upgraded to 4.3 which I currently don't
have access to and I wanted to verify capabilities on 4.3. NVM caps should be
similar on
Hi Dimitri, I just tried it here. The same problem is happening with
kernel 6.7 and the same workaround (disabling ASLR) works.
Example of failure:
clang++-$VERSION -O1 -g -fsanitize=address -fno-omit-frame-pointer foo.cpp
ASAN_OPTIONS=verbosity=1 ./a.out &> foo.log || true
we area bout to move to v6.7 kernel as v6.6 is sort of dead to us
already.
Are you able to test with linux-generic-wip (linux-unstable source) from
this ppa https://launchpad.net/~canonical-kernel-
team/+archive/ubuntu/unstable?field.series_filter=noble ?
** Also affects: linux (Ubuntu)
** Description changed:
+ [ Workaround ]
+
+ 1. Set ClassicBondedOnly=false in /etc/bluetooth/input.conf
+ 2. Run: systemctl restart bluetooth # or reboot
+
+ [ Original Description ]
+
Once my Ubuntu updated bluez package to 5.64-0ubuntu1.1 I was not able
to connect my PS3 Sixasis
Public bug reported:
Kernel modules are zstd-compressed nowadays so there's no real reason
anymore to split the modules package. In fact that used to cause issues
and required frequent moving of modules from one package to the other.
** Affects: linux-raspi (Ubuntu)
Importance: Undecided
Public bug reported:
Noble and newer doesn't support armhf for Pi anymore.
** Affects: linux-raspi (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux-raspi (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: linux-raspi (Ubuntu Noble)
Public bug reported:
dwc_otg is really only used for armv6 Pis, which Ubuntu doesn't support,
so make dwc2 the default.
** Affects: linux-raspi (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux-raspi (Ubuntu Noble)
Importance: Undecided
Status: New
**
Test B PC device withlinux/5.15.0-93.103 kernel on several displays, display
fine.
** Tags removed: verification-needed-jammy-linux
** Tags added: verification-done-jammy-linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
** Also affects: linux-firmware (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: linux-oem-6.5 (Ubuntu Noble)
Importance: Undecided
Status: Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Commit 318c64abf touches PNVM as well:
$ git log --oneline --stat 318c64abf
318c64abf (tag: iwlwifi-fw-2023-12-21, korg-iwlwifi/for-upstream) iwlwifi:
update gl FW for core80-165 release
WHENCE | 2 +-
iwlwifi-gl-c0-fm-c0-83.ucode | Bin 1799504 -> 1797996 bytes
Public bug reported:
Within stress reboot tests, iwlwifi may fail to load firmware and
triggers retry, and finally makes wifi operative.
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: Loaded firmware version:
83.d24e06ed.0 gl-c0-fm-c0-83.ucode
Oct 12 00:16:21 32090 kernel: iwlwifi
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: Ubuntu Jammy
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
Both Lunar (6.2.0-41.42) and Mantic (6.5.0-16.16) successfully verified by the
test plan.
root@ubuntu:~# dmesg -wT
[Wed Jan 10 08:28:27 2024] pci :08:00.0: [1af4:1042] type 00 class 0x01
[Wed Jan 10 08:28:27 2024] pci :08:00.0: reg 0x14: [mem
0x-0x0fff]
[Wed Jan 10
Pushed new revision of usbio-drivers source package to
https://launchpad.net/~vicamo/+archive/ubuntu/ppa-2041800. It's based on
a new upstream release version and therefore source tarball & everything
else needed are in the PPA.
Changes since previous attempt:
* New upstream WW50'23-USBIO-PV
** Changed in: Ubuntu Noble
Status: Fix Committed => In Progress
** Description changed:
Description: USBIO Bridge drivers for Intel MeteoLake platform with Lattice
AIC
- This package provides kernel drivers for MIPI cameras through the Intel IPU6
- on Intel MeteoLake platform with
87 matches
Mail list logo
