[gentoo-user] grub-install error

2023-10-04 Thread dhk



After setting up a new laptop the grub-install command produces an 
error:  "grub-install: error: disk `lvm/nvme0n1p1' not found."


A few comments about the system . . it is a basic setup except that it 
uses luks2 on each partition; lvm is not used, but the decrypted 
partitions are in /dev/mapper and may be the reason lvm is in the error 
message.  The device.map file does not exist on my other working 
machines so it is not clear if that is even necessary.  Also the 
/dev/mapper/nvme0n1p1 partition is certainly there, it is vfat and 
mounted on /efi. The intent is to use a custom initramfs to do the 
decryption.


The laptop will be rebuilt a couple times to work out some ideas, but 
before starting over it would be helpful to understand this error (it is 
not one of the two errors mentioned in the Debugging GRUB section of the 
Handbook).  Responses to questions will be slow since all my traffic 
goes through the weekly digest.


Thanks in advance.

Below is the output of some commands.

* The grub-install command run twice first without and second with 
--verbose.

(chroot) livecd / # grub-install --target=x86_64-efi --efi-directory=/efi
Installing for x86_64-efi platform.
grub-install: error: disk `lvm/nvme0n1p1' not found.

(chroot) livecd / # grub-install --target=x86_64-efi 
--efi-directory=/efi --verbose

Installing for x86_64-efi platform.
grub-install: info: cannot open `/boot/grub/device.map': No such file or 
directory.

grub-install: info: changing current directory to /dev/mapper.
grub-install: info: /dev/mapper/nvme0n1p1 is not present.
grub-install: info: /dev/mapper/nvme0n1p1 is not present.
grub-install: info: /dev/mapper/nvme0n1p1 is not present.
grub-install: info: Scanning for DISKFILTER devices on disk host.
grub-install: info: Scanning for mdraid1x devices on disk host.
grub-install: info: Scanning for mdraid09_be devices on disk host.
grub-install: info: Scanning for mdraid09 devices on disk host.
grub-install: info: Scanning for dmraid_nv devices on disk host.
grub-install: info: Scanning for ldm devices on disk host.
grub-install: info: scanning host for LDM.
grub-install: info: no LDM signature found.
grub-install: info: Scanning for lvm devices on disk host.
grub-install: info: Scanning for DISKFILTER devices on disk proc.
grub-install: info: Scanning for mdraid1x devices on disk proc.
grub-install: info: Scanning for mdraid09_be devices on disk proc.
grub-install: info: Scanning for mdraid09 devices on disk proc.
grub-install: info: Scanning for dmraid_nv devices on disk proc.
grub-install: info: Scanning for ldm devices on disk proc.
grub-install: info: scanning proc for LDM.
grub-install: info: no LDM signature found.
grub-install: info: Scanning for lvm devices on disk proc.
grub-install: info: drive = -1.
grub-install: error: disk `lvm/nvme0n1p1' not found.

* The /efi partition is vfat.
(chroot) livecd / # fdisk -l /dev/mapper/nvme0n1p1
Disk /dev/mapper/nvme0n1p1: 34 MiB, 35651584 bytes, 69632 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x

* The lsblk command on the drive.
(chroot) livecd /usr/src/linux # lsblk /dev/nvme0n1
NAME  MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINTS
nvme0n1   259:0    0 238.5G  0 disk
├─nvme0n1p1   259:1    0    50M  0 part
│ └─nvme0n1p1 253:0    0    34M  0 crypt /efi
├─nvme0n1p2   259:2    0 2G  0 part
│ └─nvme0n1p2 253:1    0   1.9G  0 crypt /boot
├─nvme0n1p3   259:3    0    16G  0 part
│ └─nvme0n1p3 253:2    0    16G  0 crypt [SWAP]
├─nvme0n1p4   259:4    0    10G  0 part
│ └─nvme0n1p4 253:3    0    10G  0 crypt /
├─nvme0n1p5   259:5    0 2G  0 part
│ └─nvme0n1p5 253:4    0 2G  0 crypt /tmp
├─nvme0n1p6   259:6    0    60G  0 part
│ └─nvme0n1p6 253:5    0    60G  0 crypt /usr
├─nvme0n1p7   259:7    0    25G  0 part
│ └─nvme0n1p7 253:6    0    25G  0 crypt /var
├─nvme0n1p8   259:8    0    20G  0 part
│ └─nvme0n1p8 253:7    0    20G  0 crypt /opt
└─nvme0n1p9   259:9    0 103.5G  0 part
  └─nvme0n1p9 253:8    0 103.5G  0 crypt /home

* The emerge --info
(chroot) livecd / # emerge --info
!!! CONFIG_PROTECT is empty
Portage 3.0.51 (python 3.11.5-final-0, 
default/linux/amd64/17.1/no-multilib, gcc-13, glibc-2.37-r7, 
6.1.28-gentoo-x86_64 x86_64)

=
System uname: 
Linux-6.1.28-gentoo-x86_64-x86_64-11th_Gen_Intel-R-_Core-TM-_i5-1145G7_@_2.60GHz-with-glibc2.37

KiB Mem:    16154684 total,  15575452 free
KiB Swap:   16760828 total,  16760828 free
Timestamp of repository gentoo: Wed, 04 Oct 2023 03:00:01 +
Head commit of repository gentoo: 5194d8a0709d5d13abf436928bd7d6299e404a43
sh bash 5.1_p16-r6
ld GNU ld (Gentoo 2.40 p5) 2.40.0
app-misc/pax-utils:    1.3.5::gentoo
app-shells/bash:   5.1_p16-r6::gentoo
dev-lang/perl: 5.38.0-r1::gentoo
dev-lang/python:   3.11.5::gentoo

Re: [gentoo-user] Soft scrolling on framebuffer consoles - with GPM handling - version of the patch for kernel 6.3 onwards.

2023-10-04 Thread Jorge Almeida
On Wed, Oct 4, 2023 at 7:59 PM Alan Mackenzie  wrote:

>
> On Wed, Oct 04, 2023 at 18:08:20 +0100, Jorge Almeida wrote:
> >    6.3.11-GPM.20231004.diff works fine with 6.5.5 (vanilla from
> >[1]kernel.org)
>
> Thanks for doing this testing.
>

Thank _you_ for making the patch :)


Re: [gentoo-user] Soft scrolling on framebuffer consoles - with GPM handling - version of the patch for kernel 6.3 onwards.

2023-10-04 Thread Alan Mackenzie
Hello, Jorge.

On Wed, Oct 04, 2023 at 18:08:20 +0100, Jorge Almeida wrote:
>6.3.11-GPM.20231004.diff works fine with 6.5.5 (vanilla from
>[1]kernel.org)

Thanks for doing this testing.

> 
> References
> 
>1. http://kernel.org/

-- 
Alan Mackenzie (Nuremberg, Germany).



[gentoo-user] An annoyance in GPM, and a fix for it

2023-10-04 Thread Alan Mackenzie
Hello, Gentoo.

In the GPM mouse utility in a tty, one can use a double click to select
a word (and by holding the button down and moving the mouse, select a
sequence of words).

Similarly, with a triple click, one can select a line, or a sequence of
lines.  This is all very fine, but GPM adds a CR after each line in the
sequnce, INCLUDING THE LAST ONE.  This makes it less useful for, say,
copying a shell script command from and editor onto a command line.
Because typically, you'd want to edit the command before executing it,
but with GPM's mechanism, the CR on the end immediately executes it, not
giving you a chance to edit it.

A solution to this problem is not to append the CR to the last line in a
sequence of lines selected by GPM.  This means patching the kernel.  To
apply the patch, first get the attached patch into the kernel's
directory, and do something like:

# patch -p1 < 6.1.8-TRIPLE.20231004.diff

, then rebuild the kernel.  Install this kernel into your boot manager,
and voilà - the problem is solved.  :-)

The usual disclaimer applies.

-- 
Alan Mackenzie (Nuremberg, Germany).

diff --git a/drivers/tty/vt/selection.c b/drivers/tty/vt/selection.c
index 6ef22f01cc51..e2a07b8759ed 100644
--- a/drivers/tty/vt/selection.c
+++ b/drivers/tty/vt/selection.c
@@ -217,7 +217,8 @@ static int vc_selection_store_chars(struct vc_data *vc, 
bool unicode)
   unless non-space at end of line. */
if (obp != bp) {
bp = obp;
-   *bp++ = '\r';
+   if ((i + 2) < vc_sel.end) /* Don't add \r to 
the last line. */
+   *bp++ = '\r';
}
obp = bp;
}


Re: [gentoo-user] Re: What to do about openssl

2023-10-04 Thread John Covici
On Wed, 04 Oct 2023 13:36:38 -0400,
Steve Wilson wrote:
> 
> [1  ]
> From https://www.php.net/manual/en/openssl.requirements.php
> 
> PHP 7.1-8.0 requires OpenSSL >= 1.0.1, < 3.0.
> PHP >= 8.1 requires OpenSSL >= 1.0.2, < 4.0.
> 
> So it looks like you need to upgrade php to 8.1
> 
> I've a similar problem with my server requiring php 7.2 and
> trying to figure out the upgrade path for all php based
> sites/apps is a pain.
> 
> On 04/10/2023 18:15, John Covici wrote:
> > On Wed, 04 Oct 2023 11:53:46 -0400,
> > Grant Edwards wrote:
The php was the problem, I had upgraded it, but not removed the 7.4
yet.  After doing a depclean on that all is at least compiling now,
including many, many reinstalls.

Thanks all.

> >> On 2023-10-04, John Covici  wrote:
> >>> Hi.  I just did a world update and found that my openssl-1.1.1v is
> >>> masked.  What can I do,
> >> Use one of the stable versions.
> >> 
> >>> I don't have any version that is not masked
> >> Huh?  What architecture are you on? There are three versions of
> >> openssl that are stable and not masked for amd64, x86, and most
> >> others:
> >> 
> >> 3.0.9-r1
> >> 3.0.9-r2
> >> 3.0.10
> >> 
> >> see
> >> 
> >> https://packages.gentoo.org/packages/dev-libs/openssl
> >> 
> >>> and according to the message this version is EOL.
> >> Indeed. OpenSSL 1.1.1 is dead. Support ended a few weeks ago.
> >> 
> >> 
> >> 
> >> 
> >> 
> >> 
> > Upon further investigation, I hadd masked them off myself , if I
> > unmask the 3.x I get the following:
> > Script started on 2023-10-04 13:10:40-04:00 [COMMAND="emerge -1
> > dev-libs/openssl" TERM="linux" TTY="/dev/tty1" COLUMNS="240"
> > LINES="67"]
> > ^M
> > These are the packages that would be merged, in order:^M
> > ^M
> > Calculating dependencies  .  ... done!^M
> > Dependency resolution took 38.07 s.^M
> > ^M
> > [ebuild  r  U  ] dev-libs/openssl-3.1.3:0/3::gentoo
> > [1.1.1v:0/1.1::gentoo] USE="asm -fips% -ktls% -rfc3779 -sctp
> > -static-libs -test -tls-compression -vanilla -verify-sig
> > -weak-ssl-ciphers (-sslv3%) (-tls-heartbeat%)" ABI_X86="(64) -32
> > (-x3\2)" CPU_FLAGS_X86="(sse2)" 15,198 KiB^M
> > [ebuild  rR] sys-apps/coreutils-9.4::gentoo  USE="acl nls openssl
> > (split-usr) xattr -caps -gmp -hostname -kill -multicall (-selinux)
> > -static -test -vanilla -verify-sig" 0 KiB^M
> > [ebuild  rR] net-misc/rsync-3.2.7-r2::gentoo  USE="acl iconv ssl
> > xattr -examples -lz4 -rrsync -stunnel -system-zlib -verify-sig -xxhash
> > -zstd" PYTHON_SINGLE_TARGET="python3_11 -python3_10" 0 KiB^M
> > [ebuild  rR] net-misc/wget-1.21.4::gentoo  USE="ipv6 nls pcre
> > (ssl) zlib -cookie-check -debug -gnutls -idn -metalink -ntlm -static
> > -test -uuid -verify-sig" 0 KiB^M
> > [ebuild  rR] dev-lang/python-3.12.0_rc3_p1:3.12::gentoo
> > USE="ensurepip gdbm ncurses readline sqlite ssl -bluetooth -build
> > -debug -examples -libedit -lto -pgo -test -tk -valgrind -verify-sig" 0
> > KiB^M
> > [ebuild  rR] dev-libs/libtpms-0.9.6::gentoo  0 KiB^M
> > [ebuild  rR] www-client/w3m-0.5.3_p20230121::gentoo  USE="X gpm
> > nls ssl unicode -fbcon -gdk-pixbuf -imlib -lynxkeymap -nntp -xface"
> > L10N="-ja" 0 KiB^M
> > [ebuild  rR] dev-db/mysql-connector-c-8.0.32-r1:0/21::gentoo
> > USE="static-libs -ldap" ABI_X86="(64) -32 (-x32)" 0 KiB^M
> > [ebuild  rR] dev-lang/rust-1.72.0:stable/1.72::gentoo  USE="lto
> > (-big-endian) -clippy -debug -dist -doc (-llvm-libunwind) (-miri)
> > (-nightly) (-parallel-compiler) -profiler -rust-analyzer -rust-src
> > -rustfmt -system-bootstrap -system-llv\m -test -verify-sig -wasm"
> > ABI_X86="(64) -32 (-x32)" CPU_FLAGS_X86="sse2" LLVM_TARGETS="(X86)
> > -AArch64 -AMDGPU -ARM -AVR -BPF -Hexagon -Lanai -LoongArch -MSP430
> > -Mips -NVPTX -PowerPC -RISCV -Sparc -SystemZ -VE -WebAssembly -XCore"
> > 0 KiB^M
> > [ebuild  rR] net-libs/libssh-0.10.5:0/4::gentoo  USE="sftp zlib
> > -debug -doc -examples -gcrypt -gssapi -mbedtls -pcap -server
> > -static-libs -test" ABI_X86="(64) -32 (-x32)" 0 KiB^M
> > [ebuild  rR] dev-db/mariadb-connector-c-3.3.4:0/3::gentoo
> > USE="curl ssl -gnutls -kerberos -static-libs -test" ABI_X86="(64) -32
> > (-x32)" 0 KiB^M
> > [ebuild  rR] app-crypt/swtpm-0.8.1-r2::gentoo  USE="seccomp -fuse
> > -test" 0 KiB^M
> > [ebuild  rR] dev-python/cryptography-41.0.4::gentoo  USE="-debug
> > -test" PYTHON_TARGETS="python3_11 -pypy3 -python3_10 -python3_12" 0
> > KiB^M
> > [ebuild  rR] dev-db/mariadb-10.11.5:10.11/18::gentoo  USE="backup
> > odbc pam perl server systemd xml -bindist -columnstore -cracklib
> > -debug -extraengine -galera -innodb-lz4 -innodb-lzo -innodb-snappy
> > -jdbc -jemalloc -kerberos -latin1 -mr\oonga -numa -oqgraph -profiling
> > -rocksdb -s3 (-selinux) -sphinx -sst-mariabackup -sst-rsync -static
> > -systemtap -tcmalloc -test -yassl" 0 KiB^M
> > [ebuild  rR] dev-db/postgresql-16.0:16::gentoo  USE="icu nls pam
> > readline server ssl systemd xml zlib -debug -doc -kerberos -ldap -llvm
> > -lz4 -perl -python (-selinux) 

Re: [gentoo-user] Re: What to do about openssl

2023-10-04 Thread John Covici
On Wed, 04 Oct 2023 13:23:40 -0400,
Alan McKinnon wrote:
> 
> [1  ]
> That should not happen, and is probably happening because you have masked
> something deep in the dep graph that is required.
> 
> Please post all your package.mask files, and provided if you have any of
> those
> 
> 
> Alan
Here is my package.mask file.

#1.4.1 has some serious problems
>=app-backup/rsnapshot-1.4.1


#i use udev
>=sys-fs/static-dev-0.1





#not yet ready
#mutes everything
>=media-sound/alsa-utils-1.2.5

That is all I have.



> 
> On Wed, Oct 4, 2023 at 7:15 PM John Covici  wrote:
> 
> > On Wed, 04 Oct 2023 11:53:46 -0400,
> > Grant Edwards wrote:
> > >
> > > On 2023-10-04, John Covici  wrote:
> > > > Hi.  I just did a world update and found that my openssl-1.1.1v is
> > > > masked.  What can I do,
> > >
> > > Use one of the stable versions.
> > >
> > > > I don't have any version that is not masked
> > >
> > > Huh?  What architecture are you on? There are three versions of
> > > openssl that are stable and not masked for amd64, x86, and most
> > > others:
> > >
> > > 3.0.9-r1
> > > 3.0.9-r2
> > > 3.0.10
> > >
> > > see
> > >
> > > https://packages.gentoo.org/packages/dev-libs/openssl
> > >
> > > > and according to the message this version is EOL.
> > >
> > > Indeed. OpenSSL 1.1.1 is dead. Support ended a few weeks ago.
> > >
> > >
> > >
> > >
> > >
> > >
> >
> > Upon further investigation, I hadd masked them off myself , if I
> > unmask the 3.x I get the following:
> > Script started on 2023-10-04 13:10:40-04:00 [COMMAND="emerge -1
> > dev-libs/openssl" TERM="linux" TTY="/dev/tty1" COLUMNS="240"
> > LINES="67"]
> > ^M
> > These are the packages that would be merged, in order:^M
> > ^M
> > Calculating dependencies  .  ... done!^M
> > Dependency resolution took 38.07 s.^M
> > ^M
> > [ebuild  r  U  ] dev-libs/openssl-3.1.3:0/3::gentoo
> > [1.1.1v:0/1.1::gentoo] USE="asm -fips% -ktls% -rfc3779 -sctp
> > -static-libs -test -tls-compression -vanilla -verify-sig
> > -weak-ssl-ciphers (-sslv3%) (-tls-heartbeat%)" ABI_X86="(64) -32
> > (-x3\2)" CPU_FLAGS_X86="(sse2)" 15,198 KiB^M
> > [ebuild  rR] sys-apps/coreutils-9.4::gentoo  USE="acl nls openssl
> > (split-usr) xattr -caps -gmp -hostname -kill -multicall (-selinux)
> > -static -test -vanilla -verify-sig" 0 KiB^M
> > [ebuild  rR] net-misc/rsync-3.2.7-r2::gentoo  USE="acl iconv ssl
> > xattr -examples -lz4 -rrsync -stunnel -system-zlib -verify-sig -xxhash
> > -zstd" PYTHON_SINGLE_TARGET="python3_11 -python3_10" 0 KiB^M
> > [ebuild  rR] net-misc/wget-1.21.4::gentoo  USE="ipv6 nls pcre
> > (ssl) zlib -cookie-check -debug -gnutls -idn -metalink -ntlm -static
> > -test -uuid -verify-sig" 0 KiB^M
> > [ebuild  rR] dev-lang/python-3.12.0_rc3_p1:3.12::gentoo
> > USE="ensurepip gdbm ncurses readline sqlite ssl -bluetooth -build
> > -debug -examples -libedit -lto -pgo -test -tk -valgrind -verify-sig" 0
> > KiB^M
> > [ebuild  rR] dev-libs/libtpms-0.9.6::gentoo  0 KiB^M
> > [ebuild  rR] www-client/w3m-0.5.3_p20230121::gentoo  USE="X gpm
> > nls ssl unicode -fbcon -gdk-pixbuf -imlib -lynxkeymap -nntp -xface"
> > L10N="-ja" 0 KiB^M
> > [ebuild  rR] dev-db/mysql-connector-c-8.0.32-r1:0/21::gentoo
> > USE="static-libs -ldap" ABI_X86="(64) -32 (-x32)" 0 KiB^M
> > [ebuild  rR] dev-lang/rust-1.72.0:stable/1.72::gentoo  USE="lto
> > (-big-endian) -clippy -debug -dist -doc (-llvm-libunwind) (-miri)
> > (-nightly) (-parallel-compiler) -profiler -rust-analyzer -rust-src
> > -rustfmt -system-bootstrap -system-llv\m -test -verify-sig -wasm"
> > ABI_X86="(64) -32 (-x32)" CPU_FLAGS_X86="sse2" LLVM_TARGETS="(X86)
> > -AArch64 -AMDGPU -ARM -AVR -BPF -Hexagon -Lanai -LoongArch -MSP430
> > -Mips -NVPTX -PowerPC -RISCV -Sparc -SystemZ -VE -WebAssembly -XCore"
> > 0 KiB^M
> > [ebuild  rR] net-libs/libssh-0.10.5:0/4::gentoo  USE="sftp zlib
> > -debug -doc -examples -gcrypt -gssapi -mbedtls -pcap -server
> > -static-libs -test" ABI_X86="(64) -32 (-x32)" 0 KiB^M
> > [ebuild  rR] dev-db/mariadb-connector-c-3.3.4:0/3::gentoo
> > USE="curl ssl -gnutls -kerberos -static-libs -test" ABI_X86="(64) -32
> > (-x32)" 0 KiB^M
> > [ebuild  rR] app-crypt/swtpm-0.8.1-r2::gentoo  USE="seccomp -fuse
> > -test" 0 KiB^M
> > [ebuild  rR] dev-python/cryptography-41.0.4::gentoo  USE="-debug
> > -test" PYTHON_TARGETS="python3_11 -pypy3 -python3_10 -python3_12" 0
> > KiB^M
> > [ebuild  rR] dev-db/mariadb-10.11.5:10.11/18::gentoo  USE="backup
> > odbc pam perl server systemd xml -bindist -columnstore -cracklib
> > -debug -extraengine -galera -innodb-lz4 -innodb-lzo -innodb-snappy
> > -jdbc -jemalloc -kerberos -latin1 -mr\oonga -numa -oqgraph -profiling
> > -rocksdb -s3 (-selinux) -sphinx -sst-mariabackup -sst-rsync -static
> > -systemtap -tcmalloc -test -yassl" 0 KiB^M
> > [ebuild  rR] dev-db/postgresql-16.0:16::gentoo  USE="icu nls pam
> > readline server ssl systemd xml zlib -debug -doc -kerberos -ldap -llvm
> > -lz4 -perl -python (-selinux) -static-libs -tcl -uuid -zstd"
> 

Re: [gentoo-user] Re: What to do about openssl

2023-10-04 Thread Steve Wilson

From https://www.php.net/manual/en/openssl.requirements.php

PHP 7.1-8.0 requires OpenSSL >= 1.0.1, < 3.0.
PHP >= 8.1 requires OpenSSL >= 1.0.2, < 4.0.

So it looks like you need to upgrade php to 8.1

I've a similar problem with my server requiring php 7.2 and trying to 
figure out the upgrade path for all php based sites/apps is a pain.


On 04/10/2023 18:15, John Covici wrote:

On Wed, 04 Oct 2023 11:53:46 -0400,
Grant Edwards wrote:

On 2023-10-04, John Covici  wrote:

Hi.  I just did a world update and found that my openssl-1.1.1v is
masked.  What can I do,

Use one of the stable versions.


I don't have any version that is not masked

Huh?  What architecture are you on? There are three versions of
openssl that are stable and not masked for amd64, x86, and most
others:

3.0.9-r1
3.0.9-r2
3.0.10

see

https://packages.gentoo.org/packages/dev-libs/openssl


and according to the message this version is EOL.

Indeed. OpenSSL 1.1.1 is dead. Support ended a few weeks ago.







Upon further investigation, I hadd masked them off myself , if I
unmask the 3.x I get the following:
Script started on 2023-10-04 13:10:40-04:00 [COMMAND="emerge -1
dev-libs/openssl" TERM="linux" TTY="/dev/tty1" COLUMNS="240"
LINES="67"]
^M
These are the packages that would be merged, in order:^M
^M
Calculating dependencies  .  ... done!^M
Dependency resolution took 38.07 s.^M
^M
[ebuild  r  U  ] dev-libs/openssl-3.1.3:0/3::gentoo
[1.1.1v:0/1.1::gentoo] USE="asm -fips% -ktls% -rfc3779 -sctp
-static-libs -test -tls-compression -vanilla -verify-sig
-weak-ssl-ciphers (-sslv3%) (-tls-heartbeat%)" ABI_X86="(64) -32
(-x3\2)" CPU_FLAGS_X86="(sse2)" 15,198 KiB^M
[ebuild  rR] sys-apps/coreutils-9.4::gentoo  USE="acl nls openssl
(split-usr) xattr -caps -gmp -hostname -kill -multicall (-selinux)
-static -test -vanilla -verify-sig" 0 KiB^M
[ebuild  rR] net-misc/rsync-3.2.7-r2::gentoo  USE="acl iconv ssl
xattr -examples -lz4 -rrsync -stunnel -system-zlib -verify-sig -xxhash
-zstd" PYTHON_SINGLE_TARGET="python3_11 -python3_10" 0 KiB^M
[ebuild  rR] net-misc/wget-1.21.4::gentoo  USE="ipv6 nls pcre
(ssl) zlib -cookie-check -debug -gnutls -idn -metalink -ntlm -static
-test -uuid -verify-sig" 0 KiB^M
[ebuild  rR] dev-lang/python-3.12.0_rc3_p1:3.12::gentoo
USE="ensurepip gdbm ncurses readline sqlite ssl -bluetooth -build
-debug -examples -libedit -lto -pgo -test -tk -valgrind -verify-sig" 0
KiB^M
[ebuild  rR] dev-libs/libtpms-0.9.6::gentoo  0 KiB^M
[ebuild  rR] www-client/w3m-0.5.3_p20230121::gentoo  USE="X gpm
nls ssl unicode -fbcon -gdk-pixbuf -imlib -lynxkeymap -nntp -xface"
L10N="-ja" 0 KiB^M
[ebuild  rR] dev-db/mysql-connector-c-8.0.32-r1:0/21::gentoo
USE="static-libs -ldap" ABI_X86="(64) -32 (-x32)" 0 KiB^M
[ebuild  rR] dev-lang/rust-1.72.0:stable/1.72::gentoo  USE="lto
(-big-endian) -clippy -debug -dist -doc (-llvm-libunwind) (-miri)
(-nightly) (-parallel-compiler) -profiler -rust-analyzer -rust-src
-rustfmt -system-bootstrap -system-llv\m -test -verify-sig -wasm"
ABI_X86="(64) -32 (-x32)" CPU_FLAGS_X86="sse2" LLVM_TARGETS="(X86)
-AArch64 -AMDGPU -ARM -AVR -BPF -Hexagon -Lanai -LoongArch -MSP430
-Mips -NVPTX -PowerPC -RISCV -Sparc -SystemZ -VE -WebAssembly -XCore"
0 KiB^M
[ebuild  rR] net-libs/libssh-0.10.5:0/4::gentoo  USE="sftp zlib
-debug -doc -examples -gcrypt -gssapi -mbedtls -pcap -server
-static-libs -test" ABI_X86="(64) -32 (-x32)" 0 KiB^M
[ebuild  rR] dev-db/mariadb-connector-c-3.3.4:0/3::gentoo
USE="curl ssl -gnutls -kerberos -static-libs -test" ABI_X86="(64) -32
(-x32)" 0 KiB^M
[ebuild  rR] app-crypt/swtpm-0.8.1-r2::gentoo  USE="seccomp -fuse
-test" 0 KiB^M
[ebuild  rR] dev-python/cryptography-41.0.4::gentoo  USE="-debug
-test" PYTHON_TARGETS="python3_11 -pypy3 -python3_10 -python3_12" 0
KiB^M
[ebuild  rR] dev-db/mariadb-10.11.5:10.11/18::gentoo  USE="backup
odbc pam perl server systemd xml -bindist -columnstore -cracklib
-debug -extraengine -galera -innodb-lz4 -innodb-lzo -innodb-snappy
-jdbc -jemalloc -kerberos -latin1 -mr\oonga -numa -oqgraph -profiling
-rocksdb -s3 (-selinux) -sphinx -sst-mariabackup -sst-rsync -static
-systemtap -tcmalloc -test -yassl" 0 KiB^M
[ebuild  rR] dev-db/postgresql-16.0:16::gentoo  USE="icu nls pam
readline server ssl systemd xml zlib -debug -doc -kerberos -ldap -llvm
-lz4 -perl -python (-selinux) -static-libs -tcl -uuid -zstd"
PYTHON_SINGLE_TARGET="python3_11 -pyth\on3_10 -python3_12" 0 KiB^M
[ebuild  rR] app-admin/syslog-ng-4.4.0::gentoo  USE="systemd -amqp
-caps -dbi -geoip2 -http -json -kafka -mongodb -pacct -python -redis
-smtp -snmp -spoof-source -tcpd -test"
PYTHON_SINGLE_TARGET="python3_11 -python3_10 -python3_12" 0 \KiB^M
[ebuild  rR] dev-db/postgresql-14.9:14::gentoo  USE="icu nls pam
readline server ssl systemd xml zlib -debug -doc -kerberos -ldap -llvm
-lz4 -perl -python (-selinux) -static-libs -tcl -uuid (-threads%)"
PYTHON_SINGLE_TARGET="python3_11\ -python3_10 -python3_12" 0 KiB^M
[ebuild  rR] 

Re: [gentoo-user] Re: What to do about openssl

2023-10-04 Thread Alan McKinnon
That should not happen, and is probably happening because you have masked
something deep in the dep graph that is required.

Please post all your package.mask files, and provided if you have any of
those


Alan

On Wed, Oct 4, 2023 at 7:15 PM John Covici  wrote:

> On Wed, 04 Oct 2023 11:53:46 -0400,
> Grant Edwards wrote:
> >
> > On 2023-10-04, John Covici  wrote:
> > > Hi.  I just did a world update and found that my openssl-1.1.1v is
> > > masked.  What can I do,
> >
> > Use one of the stable versions.
> >
> > > I don't have any version that is not masked
> >
> > Huh?  What architecture are you on? There are three versions of
> > openssl that are stable and not masked for amd64, x86, and most
> > others:
> >
> > 3.0.9-r1
> > 3.0.9-r2
> > 3.0.10
> >
> > see
> >
> > https://packages.gentoo.org/packages/dev-libs/openssl
> >
> > > and according to the message this version is EOL.
> >
> > Indeed. OpenSSL 1.1.1 is dead. Support ended a few weeks ago.
> >
> >
> >
> >
> >
> >
>
> Upon further investigation, I hadd masked them off myself , if I
> unmask the 3.x I get the following:
> Script started on 2023-10-04 13:10:40-04:00 [COMMAND="emerge -1
> dev-libs/openssl" TERM="linux" TTY="/dev/tty1" COLUMNS="240"
> LINES="67"]
> ^M
> These are the packages that would be merged, in order:^M
> ^M
> Calculating dependencies  .  ... done!^M
> Dependency resolution took 38.07 s.^M
> ^M
> [ebuild  r  U  ] dev-libs/openssl-3.1.3:0/3::gentoo
> [1.1.1v:0/1.1::gentoo] USE="asm -fips% -ktls% -rfc3779 -sctp
> -static-libs -test -tls-compression -vanilla -verify-sig
> -weak-ssl-ciphers (-sslv3%) (-tls-heartbeat%)" ABI_X86="(64) -32
> (-x3\2)" CPU_FLAGS_X86="(sse2)" 15,198 KiB^M
> [ebuild  rR] sys-apps/coreutils-9.4::gentoo  USE="acl nls openssl
> (split-usr) xattr -caps -gmp -hostname -kill -multicall (-selinux)
> -static -test -vanilla -verify-sig" 0 KiB^M
> [ebuild  rR] net-misc/rsync-3.2.7-r2::gentoo  USE="acl iconv ssl
> xattr -examples -lz4 -rrsync -stunnel -system-zlib -verify-sig -xxhash
> -zstd" PYTHON_SINGLE_TARGET="python3_11 -python3_10" 0 KiB^M
> [ebuild  rR] net-misc/wget-1.21.4::gentoo  USE="ipv6 nls pcre
> (ssl) zlib -cookie-check -debug -gnutls -idn -metalink -ntlm -static
> -test -uuid -verify-sig" 0 KiB^M
> [ebuild  rR] dev-lang/python-3.12.0_rc3_p1:3.12::gentoo
> USE="ensurepip gdbm ncurses readline sqlite ssl -bluetooth -build
> -debug -examples -libedit -lto -pgo -test -tk -valgrind -verify-sig" 0
> KiB^M
> [ebuild  rR] dev-libs/libtpms-0.9.6::gentoo  0 KiB^M
> [ebuild  rR] www-client/w3m-0.5.3_p20230121::gentoo  USE="X gpm
> nls ssl unicode -fbcon -gdk-pixbuf -imlib -lynxkeymap -nntp -xface"
> L10N="-ja" 0 KiB^M
> [ebuild  rR] dev-db/mysql-connector-c-8.0.32-r1:0/21::gentoo
> USE="static-libs -ldap" ABI_X86="(64) -32 (-x32)" 0 KiB^M
> [ebuild  rR] dev-lang/rust-1.72.0:stable/1.72::gentoo  USE="lto
> (-big-endian) -clippy -debug -dist -doc (-llvm-libunwind) (-miri)
> (-nightly) (-parallel-compiler) -profiler -rust-analyzer -rust-src
> -rustfmt -system-bootstrap -system-llv\m -test -verify-sig -wasm"
> ABI_X86="(64) -32 (-x32)" CPU_FLAGS_X86="sse2" LLVM_TARGETS="(X86)
> -AArch64 -AMDGPU -ARM -AVR -BPF -Hexagon -Lanai -LoongArch -MSP430
> -Mips -NVPTX -PowerPC -RISCV -Sparc -SystemZ -VE -WebAssembly -XCore"
> 0 KiB^M
> [ebuild  rR] net-libs/libssh-0.10.5:0/4::gentoo  USE="sftp zlib
> -debug -doc -examples -gcrypt -gssapi -mbedtls -pcap -server
> -static-libs -test" ABI_X86="(64) -32 (-x32)" 0 KiB^M
> [ebuild  rR] dev-db/mariadb-connector-c-3.3.4:0/3::gentoo
> USE="curl ssl -gnutls -kerberos -static-libs -test" ABI_X86="(64) -32
> (-x32)" 0 KiB^M
> [ebuild  rR] app-crypt/swtpm-0.8.1-r2::gentoo  USE="seccomp -fuse
> -test" 0 KiB^M
> [ebuild  rR] dev-python/cryptography-41.0.4::gentoo  USE="-debug
> -test" PYTHON_TARGETS="python3_11 -pypy3 -python3_10 -python3_12" 0
> KiB^M
> [ebuild  rR] dev-db/mariadb-10.11.5:10.11/18::gentoo  USE="backup
> odbc pam perl server systemd xml -bindist -columnstore -cracklib
> -debug -extraengine -galera -innodb-lz4 -innodb-lzo -innodb-snappy
> -jdbc -jemalloc -kerberos -latin1 -mr\oonga -numa -oqgraph -profiling
> -rocksdb -s3 (-selinux) -sphinx -sst-mariabackup -sst-rsync -static
> -systemtap -tcmalloc -test -yassl" 0 KiB^M
> [ebuild  rR] dev-db/postgresql-16.0:16::gentoo  USE="icu nls pam
> readline server ssl systemd xml zlib -debug -doc -kerberos -ldap -llvm
> -lz4 -perl -python (-selinux) -static-libs -tcl -uuid -zstd"
> PYTHON_SINGLE_TARGET="python3_11 -pyth\on3_10 -python3_12" 0 KiB^M
> [ebuild  rR] app-admin/syslog-ng-4.4.0::gentoo  USE="systemd -amqp
> -caps -dbi -geoip2 -http -json -kafka -mongodb -pacct -python -redis
> -smtp -snmp -spoof-source -tcpd -test"
> PYTHON_SINGLE_TARGET="python3_11 -python3_10 -python3_12" 0 \KiB^M
> [ebuild  rR] dev-db/postgresql-14.9:14::gentoo  USE="icu nls pam
> readline server ssl systemd xml zlib -debug -doc -kerberos -ldap -llvm
> -lz4 -perl -python (-selinux) 

Re: [gentoo-user] Re: What to do about openssl

2023-10-04 Thread John Covici
On Wed, 04 Oct 2023 11:53:46 -0400,
Grant Edwards wrote:
> 
> On 2023-10-04, John Covici  wrote:
> > Hi.  I just did a world update and found that my openssl-1.1.1v is
> > masked.  What can I do,
> 
> Use one of the stable versions.
> 
> > I don't have any version that is not masked
> 
> Huh?  What architecture are you on? There are three versions of
> openssl that are stable and not masked for amd64, x86, and most
> others:
> 
> 3.0.9-r1
> 3.0.9-r2
> 3.0.10
> 
> see
> 
> https://packages.gentoo.org/packages/dev-libs/openssl
> 
> > and according to the message this version is EOL.
> 
> Indeed. OpenSSL 1.1.1 is dead. Support ended a few weeks ago.
> 
> 
> 
> 
> 
> 

Upon further investigation, I hadd masked them off myself , if I
unmask the 3.x I get the following:
Script started on 2023-10-04 13:10:40-04:00 [COMMAND="emerge -1
dev-libs/openssl" TERM="linux" TTY="/dev/tty1" COLUMNS="240"
LINES="67"]
^M
These are the packages that would be merged, in order:^M
^M
Calculating dependencies  .  ... done!^M
Dependency resolution took 38.07 s.^M
^M
[ebuild  r  U  ] dev-libs/openssl-3.1.3:0/3::gentoo
[1.1.1v:0/1.1::gentoo] USE="asm -fips% -ktls% -rfc3779 -sctp
-static-libs -test -tls-compression -vanilla -verify-sig
-weak-ssl-ciphers (-sslv3%) (-tls-heartbeat%)" ABI_X86="(64) -32
(-x3\2)" CPU_FLAGS_X86="(sse2)" 15,198 KiB^M
[ebuild  rR] sys-apps/coreutils-9.4::gentoo  USE="acl nls openssl
(split-usr) xattr -caps -gmp -hostname -kill -multicall (-selinux)
-static -test -vanilla -verify-sig" 0 KiB^M
[ebuild  rR] net-misc/rsync-3.2.7-r2::gentoo  USE="acl iconv ssl
xattr -examples -lz4 -rrsync -stunnel -system-zlib -verify-sig -xxhash
-zstd" PYTHON_SINGLE_TARGET="python3_11 -python3_10" 0 KiB^M
[ebuild  rR] net-misc/wget-1.21.4::gentoo  USE="ipv6 nls pcre
(ssl) zlib -cookie-check -debug -gnutls -idn -metalink -ntlm -static
-test -uuid -verify-sig" 0 KiB^M
[ebuild  rR] dev-lang/python-3.12.0_rc3_p1:3.12::gentoo
USE="ensurepip gdbm ncurses readline sqlite ssl -bluetooth -build
-debug -examples -libedit -lto -pgo -test -tk -valgrind -verify-sig" 0
KiB^M
[ebuild  rR] dev-libs/libtpms-0.9.6::gentoo  0 KiB^M
[ebuild  rR] www-client/w3m-0.5.3_p20230121::gentoo  USE="X gpm
nls ssl unicode -fbcon -gdk-pixbuf -imlib -lynxkeymap -nntp -xface"
L10N="-ja" 0 KiB^M
[ebuild  rR] dev-db/mysql-connector-c-8.0.32-r1:0/21::gentoo
USE="static-libs -ldap" ABI_X86="(64) -32 (-x32)" 0 KiB^M
[ebuild  rR] dev-lang/rust-1.72.0:stable/1.72::gentoo  USE="lto
(-big-endian) -clippy -debug -dist -doc (-llvm-libunwind) (-miri)
(-nightly) (-parallel-compiler) -profiler -rust-analyzer -rust-src
-rustfmt -system-bootstrap -system-llv\m -test -verify-sig -wasm"
ABI_X86="(64) -32 (-x32)" CPU_FLAGS_X86="sse2" LLVM_TARGETS="(X86)
-AArch64 -AMDGPU -ARM -AVR -BPF -Hexagon -Lanai -LoongArch -MSP430
-Mips -NVPTX -PowerPC -RISCV -Sparc -SystemZ -VE -WebAssembly -XCore"
0 KiB^M
[ebuild  rR] net-libs/libssh-0.10.5:0/4::gentoo  USE="sftp zlib
-debug -doc -examples -gcrypt -gssapi -mbedtls -pcap -server
-static-libs -test" ABI_X86="(64) -32 (-x32)" 0 KiB^M
[ebuild  rR] dev-db/mariadb-connector-c-3.3.4:0/3::gentoo
USE="curl ssl -gnutls -kerberos -static-libs -test" ABI_X86="(64) -32
(-x32)" 0 KiB^M
[ebuild  rR] app-crypt/swtpm-0.8.1-r2::gentoo  USE="seccomp -fuse
-test" 0 KiB^M
[ebuild  rR] dev-python/cryptography-41.0.4::gentoo  USE="-debug
-test" PYTHON_TARGETS="python3_11 -pypy3 -python3_10 -python3_12" 0
KiB^M
[ebuild  rR] dev-db/mariadb-10.11.5:10.11/18::gentoo  USE="backup
odbc pam perl server systemd xml -bindist -columnstore -cracklib
-debug -extraengine -galera -innodb-lz4 -innodb-lzo -innodb-snappy
-jdbc -jemalloc -kerberos -latin1 -mr\oonga -numa -oqgraph -profiling
-rocksdb -s3 (-selinux) -sphinx -sst-mariabackup -sst-rsync -static
-systemtap -tcmalloc -test -yassl" 0 KiB^M
[ebuild  rR] dev-db/postgresql-16.0:16::gentoo  USE="icu nls pam
readline server ssl systemd xml zlib -debug -doc -kerberos -ldap -llvm
-lz4 -perl -python (-selinux) -static-libs -tcl -uuid -zstd"
PYTHON_SINGLE_TARGET="python3_11 -pyth\on3_10 -python3_12" 0 KiB^M
[ebuild  rR] app-admin/syslog-ng-4.4.0::gentoo  USE="systemd -amqp
-caps -dbi -geoip2 -http -json -kafka -mongodb -pacct -python -redis
-smtp -snmp -spoof-source -tcpd -test"
PYTHON_SINGLE_TARGET="python3_11 -python3_10 -python3_12" 0 \KiB^M
[ebuild  rR] dev-db/postgresql-14.9:14::gentoo  USE="icu nls pam
readline server ssl systemd xml zlib -debug -doc -kerberos -ldap -llvm
-lz4 -perl -python (-selinux) -static-libs -tcl -uuid (-threads%)"
PYTHON_SINGLE_TARGET="python3_11\ -python3_10 -python3_12" 0 KiB^M
[ebuild  rR] dev-lang/php-8.2.10:8.2::gentoo  USE="acl apache2
bcmath bzip2 cgi cli ctype curl exif fileinfo filter flatfile fpm ftp
gd gdbm iconv imap intl ipv6 jit mhash mysql mysqli nls odbc opcache
pcntl pdo phar posix postgres rea\dline session sharedmem simplexml
sockets spell sqlite ssl sysvipc tokenizer truetype unicode xml
xmlreader xmlwriter 

Re: [gentoo-user] Soft scrolling on framebuffer consoles - with GPM handling - version of the patch for kernel 6.3 onwards.

2023-10-04 Thread Jorge Almeida
6.3.11-GPM.20231004.diff works fine with 6.5.5 (vanilla from kernel.org)

>
>


Re: [gentoo-user] Re: What to do about openssl

2023-10-04 Thread Matt Connell
On Wed, 2023-10-04 at 12:57 -0400, John Covici wrote:
> All those are masked, I am using the ~amd64.

> All of the v3 packages are masked in my repository, just updated a
> couple of days ago.

Something on your local machine is masking these, they are definitely
unmasked for me and many others.  Check /etc/portage/package.mask to
start with, but in general I would grep -r openssl /etc/portage/ to see
what all you've got set (or unset)...



Re: [gentoo-user] Re: What to do about openssl

2023-10-04 Thread John Covici
On Wed, 04 Oct 2023 11:53:46 -0400,
Grant Edwards wrote:
> 
> On 2023-10-04, John Covici  wrote:
> > Hi.  I just did a world update and found that my openssl-1.1.1v is
> > masked.  What can I do,
> 
> Use one of the stable versions.
> 
> > I don't have any version that is not masked
> 
> Huh?  What architecture are you on? There are three versions of
> openssl that are stable and not masked for amd64, x86, and most
> others:
> 
> 3.0.9-r1
> 3.0.9-r2
> 3.0.10
> 
> see
> 
> https://packages.gentoo.org/packages/dev-libs/openssl
> 
> > and according to the message this version is EOL.
> 
> Indeed. OpenSSL 1.1.1 is dead. Support ended a few weeks ago.
> 
> 
> 
> 
All those are masked, I am using the ~amd64.

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

 John Covici wb2una
 cov...@ccs.covici.com



Re: [gentoo-user] What to do about openssl

2023-10-04 Thread John Covici
On Wed, 04 Oct 2023 11:38:04 -0400,
Alan McKinnon wrote:
> 
> [1  ]
> Hi John
> 
> All version 1.x have been masked. They are very very old and have obsolete
> code.
> 
> Upgrade to v3.x - this is what portage is telling you.
> 
> Is there some reason you require v1.1.x? Do you have a local mask for
> openssl?
> 
> Alan
> 
> On Wed, Oct 4, 2023 at 5:34 PM John Covici  wrote:
> 
> > Hi.  I just did a world update and found that my openssl-1.1.1v is
> > masked.  What can I do, I don't have any version that is not masked
> > and according to the message this version is EOL.
> >
> > Thanks in advance for any suggestions.
> >
> >
> > --
> > Your life is like a penny.  You're going to lose it.  The question is:
> > How do
> > you spend it?
> >
> >  John Covici wb2una
> >  cov...@ccs.covici.com
> >
> >
> 
> -- 
> Alan McKinnon
All of the v3 packages are masked in my repository, just updated a
couple of days ago.

Here is what I get
Available versions:  [M]1.0.2u-r1^td [M]1.1.1u(0/1.1)^t{xpak}
[M](~)1.1.1v(0/1.1)^t{xpak} [M](~)1.1.1w(0/1.1)^t [m]3.0.9-r1(0/3)^t
[m]3.0.9-r2(0/3)^t [m]3.0.10(0/3)^t [m](~)3.0.11(0/3)^t
[m](~)3.1.1-r1(0/3)^t [m](~)3.1.1-r2(0/3)^t [m](~)3.1.2(0/3)^t
[m](~)3.1.3(0/3)^t {+asm bindist fips gmp kerberos ktls rfc3779 sctp
sslv2 (+)sslv3 static-libs test tls-compression (+)tls-heartbeat
vanilla verify-sig weak-ssl-ciphers ABI_MIPS="n32 n64 o32"
ABI_S390="32 64" ABI_X86="32 64
x32" CPU_FLAGS_X86="sse2"}


-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

 John Covici wb2una
 cov...@ccs.covici.com



[gentoo-user] Re: What to do about openssl

2023-10-04 Thread Grant Edwards
On 2023-10-04, John Covici  wrote:
> Hi.  I just did a world update and found that my openssl-1.1.1v is
> masked.  What can I do,

Use one of the stable versions.

> I don't have any version that is not masked

Huh?  What architecture are you on? There are three versions of
openssl that are stable and not masked for amd64, x86, and most
others:

3.0.9-r1
3.0.9-r2
3.0.10

see

https://packages.gentoo.org/packages/dev-libs/openssl

> and according to the message this version is EOL.

Indeed. OpenSSL 1.1.1 is dead. Support ended a few weeks ago.








Re: [gentoo-user] What to do about openssl

2023-10-04 Thread Alan McKinnon
Hi John

All version 1.x have been masked. They are very very old and have obsolete
code.

Upgrade to v3.x - this is what portage is telling you.

Is there some reason you require v1.1.x? Do you have a local mask for
openssl?

Alan

On Wed, Oct 4, 2023 at 5:34 PM John Covici  wrote:

> Hi.  I just did a world update and found that my openssl-1.1.1v is
> masked.  What can I do, I don't have any version that is not masked
> and according to the message this version is EOL.
>
> Thanks in advance for any suggestions.
>
>
> --
> Your life is like a penny.  You're going to lose it.  The question is:
> How do
> you spend it?
>
>  John Covici wb2una
>  cov...@ccs.covici.com
>
>

-- 
Alan McKinnon
alan dot mckinnon at gmail dot com


[gentoo-user] What to do about openssl

2023-10-04 Thread John Covici
Hi.  I just did a world update and found that my openssl-1.1.1v is
masked.  What can I do, I don't have any version that is not masked
and according to the message this version is EOL.

Thanks in advance for any suggestions.
 

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

 John Covici wb2una
 cov...@ccs.covici.com



Re: [gentoo-user] Soft scrolling on framebuffer consoles - with GPM handling - version of the patch for kernel 6.3 onwards.

2023-10-04 Thread Peter Humphrey
On Wednesday, 4 October 2023 14:16:44 BST Alan Mackenzie wrote:
> Hello, Gentoo.
> 
> On Fri, Feb 03, 2023 at 18:56:27 +, Alan Mackenzie wrote:
> 
> The topic of this post is my kernel patch which enables soft scrolling
> on Linux tty's with  and , and also enables
> the GPM mouse utility on those scrolled regions.
> 
> Currently, the patch I posted some months ago works on all 6.1.x
> kernels, and very likely works on 6.2.x, too.  In kernel 6.3.1, some
> significant refactoring was done by the kernel people, necessitating a
> new version of the patch, called 6.3.11-GPM.20231004.diff.  I've tested
> this on 6.3.11 and 6.5.5.
> 
> Just a quick reminder of how to use these files for anybody else who
> might be interested:
> (i) cd /usr/src/linux-6.3.11-gentoo, or similar.  (Or ...-6.1.x-gentoo).
> (ii) patch -p1 < 6.3.11-GPM.20231004.diff (or the other one).
> (iii) Configure the kernel as normal.  Additionally, under Device
> drivers/Graphic Support/Console display driver support, enable
> CONFIG_FRAMEBUFFER_CONSOLE_SOFT_SCROLLBACK, set the buffer size to 
taste
> (it's default is 128 kB) and accept the default enablement of
> CONFIG_FRAMEBUFFER_CONSOLE_SOFT_SCROLLBACK_GPM.
> (iv) Build the kernel and install it into your boot manager.
> (v) Reboot and enjoy!  You can now use GPM in scrolled consoles.
> 
> Just a warning: if you copy your kernel .config from a 6.1.x kernel, and
> use make oldconfig to generate a new kernel for 6.3.x etc., you will
> have to enable CONFIG_HID_SUPPORT, otherwise your USB keyboard and 
mouse
> will be dead on bootup.  ;-(
> 
> The usual disclaimers apply, here.  If this patch breaks anything for
> you, you get to join the pieces back together again.  But if this does
> happen, please let me know, so that I can try to fix the bug.  My only
> promise is that there's nothing malicious in the patch.
> 
> As well as 6.3.11-GPM.20231004.diff, I'm reposting
> 6.1.8-GPM.20230203.diff for anybody new here who wants to try it on the
> current Gentoo 6.1.x kernel.

Many thanks again Alan. What a stalwart you are!

-- 
Regards,
Peter.






Re: [gentoo-user] Soft scrolling on framebuffer consoles - with GPM handling - version of the patch for kernel 6.3 onwards.

2023-10-04 Thread Alan Mackenzie
Hello, Gentoo.

On Fri, Feb 03, 2023 at 18:56:27 +, Alan Mackenzie wrote:

The topic of this post is my kernel patch which enables soft scrolling
on Linux tty's with  and , and also enables
the GPM mouse utility on those scrolled regions.

Currently, the patch I posted some months ago works on all 6.1.x
kernels, and very likely works on 6.2.x, too.  In kernel 6.3.1, some
significant refactoring was done by the kernel people, necessitating a
new version of the patch, called 6.3.11-GPM.20231004.diff.  I've tested
this on 6.3.11 and 6.5.5.

Just a quick reminder of how to use these files for anybody else who
might be interested:
(i) cd /usr/src/linux-6.3.11-gentoo, or similar.  (Or ...-6.1.x-gentoo).
(ii) patch -p1 < 6.3.11-GPM.20231004.diff (or the other one).
(iii) Configure the kernel as normal.  Additionally, under Device
drivers/Graphic Support/Console display driver support, enable
CONFIG_FRAMEBUFFER_CONSOLE_SOFT_SCROLLBACK, set the buffer size to taste
(it's default is 128 kB) and accept the default enablement of
CONFIG_FRAMEBUFFER_CONSOLE_SOFT_SCROLLBACK_GPM.
(iv) Build the kernel and install it into your boot manager.
(v) Reboot and enjoy!  You can now use GPM in scrolled consoles.

Just a warning: if you copy your kernel .config from a 6.1.x kernel, and
use make oldconfig to generate a new kernel for 6.3.x etc., you will
have to enable CONFIG_HID_SUPPORT, otherwise your USB keyboard and mouse
will be dead on bootup.  ;-(

The usual disclaimers apply, here.  If this patch breaks anything for
you, you get to join the pieces back together again.  But if this does
happen, please let me know, so that I can try to fix the bug.  My only
promise is that there's nothing malicious in the patch.

As well as 6.3.11-GPM.20231004.diff, I'm reposting
6.1.8-GPM.20230203.diff for anybody new here who wants to try it on the
current Gentoo 6.1.x kernel.

-- 
Alan Mackenzie (Nuremberg, Germany).

diff --git a/drivers/tty/vt/vt.c b/drivers/tty/vt/vt.c
index 3c2ea9c098f7..51a3f0e7ffb5 100644
--- a/drivers/tty/vt/vt.c
+++ b/drivers/tty/vt/vt.c
@@ -134,6 +134,11 @@ const struct consw *conswitchp;
 #define DEFAULT_BELL_DURATION  (HZ/8)
 #define DEFAULT_CURSOR_BLINK_MS200
 
+#ifdef CONFIG_FRAMEBUFFER_CONSOLE_SOFT_SCROLLBACK
+static unsigned int console_soft_scrollback_size =
+   1024 * CONFIG_FRAMEBUFFER_CONSOLE_SOFT_SCROLLBACK_SIZE;
+#endif
+
 struct vc vc_cons [MAX_NR_CONSOLES];
 
 #ifndef VT_SINGLE_DRIVER
@@ -286,8 +291,31 @@ static inline bool con_should_update(const struct vc_data 
*vc)
 static inline unsigned short *screenpos(const struct vc_data *vc, int offset,
bool viewed)
 {
+#ifdef CONFIG_FRAMEBUFFER_CONSOLE_SOFT_SCROLLBACK
+   unsigned long softback_pos, scrolled_expanse;
+
+   if (vc->vc_softback_curr == vc->vc_origin) /* Should never happen! */
+   return (unsigned short *)(vc->vc_origin + offset);
+   else {
+   if (vc->vc_softback_in >= vc->vc_softback_curr)
+   scrolled_expanse = vc->vc_softback_in - 
vc->vc_softback_curr;
+   else
+   scrolled_expanse = vc->vc_softback_in - 
vc->vc_softback_curr
+   + vc->vc_softback_end - vc->vc_softback_buf;
+   if (offset >= scrolled_expanse)
+   return (unsigned short *)(vc->vc_origin
+ + (offset - 
scrolled_expanse));
+   else {
+   softback_pos = vc->vc_softback_curr + offset;
+   if (softback_pos >= vc->vc_softback_end)
+   softback_pos -= vc->vc_softback_end
+   - vc->vc_softback_buf;
+   }
+   }
+   return (unsigned short *)softback_pos;
+#else
unsigned short *p;
-   
+
if (!viewed)
p = (unsigned short *)(vc->vc_origin + offset);
else if (!vc->vc_sw->con_screen_pos)
@@ -295,6 +323,7 @@ static inline unsigned short *screenpos(const struct 
vc_data *vc, int offset,
else
p = vc->vc_sw->con_screen_pos(vc, offset);
return p;
+#endif
 }
 
 /* Called  from the keyboard irq path.. */
@@ -316,107 +345,111 @@ void schedule_console_callback(void)
  * Code to manage unicode-based screen buffers
  */
 
-/*
- * Our screen buffer is preceded by an array of line pointers so that
- * scrolling only implies some pointer shuffling.
- */
+#define vc_uniscr_buf_end(vc) (vc->vc_uniscr_buf + vc->vc_uniscr_char_size)
 
-static u32 **vc_uniscr_alloc(unsigned int cols, unsigned int rows)
+static int vc_uniscr_alloc(struct vc_data *vc, unsigned int cols, unsigned int 
rows)
 {
-   u32 **uni_lines;
-   void *p;
-   unsigned int memsize, i, col_size = cols * sizeof(**uni_lines);
-
-   /* allocate everything in one go */
-   memsize = col_size * rows;

Re: [gentoo-user] 6.1.53-gentoo-r1 kernel not booting

2023-10-04 Thread Peter Böhm
Am Mittwoch, 4. Oktober 2023, 05:42:17 CEST schrieb Valmor F. de Almeida:

> -> cat /proc/cpuinfo
>
> processor   : 0
> vendor_id   : GenuineIntel
> cpu family  : 6
> model   : 158
> model name  : Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
> stepping: 9
> microcode   : 0x84

At the moment this is our actual microcode for Intel CPUs:

sys-firmware/intel-microcode-20230808_p20230804

If you look into:

https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/blob/main/
releasenote.md

You will see that version f4 is actual for your CPU (dec 6-158-9 is hex
6-9e-9) instead your version 84.

KBL-G/H/S/X/E3  B0  06-9e-09/2a 00f200f4
Core
Gen7; Xeon E3 v6

What you can always do:

1. Boot with our GentooMinimalCD (so you have the new/actual microcode active
on your CPU)
2. Chroot into your system (like you do with a new installation)
3. Re-emerge all packages with "emerge -e ..."

After this, if you boot your kernel-6.1.53-r1 you should have no problem.






Re: [gentoo-user] 6.1.53-gentoo-r1 kernel not booting

2023-10-04 Thread Neil Bothwick
On Tue, 3 Oct 2023 23:42:17 -0400, Valmor F. de Almeida wrote:

> There may have been a microcode emerge from dependencies; I don't
> emerge directly. I do agree with you: if I try to recompile the working 
> kernel it will not boot. However I am not willing to try just right now 
> and having to troubleshoot a broken system.

Microcode is usually applied as an initramfs, and I think you said you
are not using any.

If you set LOCALVERSION in the kernel config, your existing kernel will
be installed with a new name, so you'll still have the working kernel to
fall back on.


-- 
Neil Bothwick

Taglines are like cars - You get a good one, then someone nicks it.


pgpxE0Vt3LD_M.pgp
Description: OpenPGP digital signature