On Mon 14 Feb 2022 at 00:40:11 (-0500), Felix Miata wrote: > Felix Miata composed on 2022-02-13 23:53 (UTC-0500): > > David Wright composed on 2022-02-10 09:27 (UTC-0600): > >> On Thu 10 Feb 2022 at 03:39:26 (-0500), Felix Miata wrote: > > >>> ...if you have a bad BIOS, and wish to boot with more than one connected > >>> display. > >>> https://gitlab.freedesktop.org/drm/intel/-/issues/4762 explains the > >>> issue, which > >>> has just been announced fixed. But, it appears the fix may only be > >>> landing in > >>> kernel 5.17rc3. > ... > > # aptitude search linux-image > ... > > p linux-image-5.17.0-rc3-amd64-unsigned - Linux 5.17-rc3 for 64-bit PCs > > Installing this one didn't help: > # uname -a > Linux ab560 5.17.0-rc3-amd64 #1 SMP PREEMPT Debian 5.17~rc3-1~exp1 > (2022-02-11)
I can't help with the underlying problem of kernel patches. > What search will return enough information to know when this has been replaced > with a newer rc3 build or rc4 or newer, like the following does:? > # zypper se -s nel-def | egrep -v 'devel|debug|base|src|586' > Loading repository data... > Reading installed packages... > > S | Name | Type | Version | Arch | Repository > ---+----------------+------------+----------------------+--------+------------------- > il | kernel-default | package | 5.16.7-1.1.g0503f69 | x86_64 | (System > Packages) > il | kernel-default | package | 5.16.3-4.1.gc7377e3 | x86_64 | (System > Packages) > vl | kernel-default | package | 5.16.9-4.1.g704dc30 | x86_64 | > homeTiwaiSimpledrm > vl | kernel-default | package | 5.16.8-1.1 | x86_64 | OSS > # inxi -S > System: > Host: ab560 Kernel: 5.16.7-1.g0503f69-default x86_64 bits: 64 > Console: pty pts/0 Distro: openSUSE Tumbleweed 20220130 > # > The homeTiwaiSimpledrm 5.16.7 kernel includes the fix for the thread subject > problem. > > The apt*/dpkg system generally seems rather resistant to showing uninstalled > package versions, except for the aptitude "extension". Come to think of it, I don't think I can help at all, beyond suggesting that you regularly download the names of the new kernels that appear in the pool itself. Yesterday you posted that: "apt-cache and aptitude don't seem to know that http://ftp.us.debian.org/debian/pool/main/l/linux/linux-image-5.16.0-trunk-amd64-unsigned_5.16.4-1~exp1_amd64.deb exists." I suppose it's an indication of how quickly things change that I get: $ wget http://ftp.us.debian.org/debian/pool/main/l/linux/linux-image-5.16.0-trunk-amd64-unsigned_5.16.4-1~exp1_amd64.deb --2022-02-14 09:10:18-- http://ftp.us.debian.org/debian/pool/main/l/linux/linux-image-5.16.0-trunk-amd64-unsigned_5.16.4-1~exp1_amd64.deb Resolving ftp.us.debian.org (ftp.us.debian.org)... 64.50.236.52, 64.50.233.100, 208.80.154.139, ... Connecting to ftp.us.debian.org (ftp.us.debian.org)|64.50.236.52|:80... connected. HTTP request sent, awaiting response... 404 Not Found 2022-02-14 09:10:18 ERROR 404: Not Found. $ AIUI, your apt* tools can only find what's indexed in dists/ rather than anything that happens to be in the pool, but I'm not familiar with the policy issues (as a non-developer). I don't think dpkg makes that its business at all. BTW the red line (attached) indicates that "trunk" doesn't appear on the page. (It's a term I don't understand.) Cheers, David.
