From nobody Mon Apr 1 20:47:35 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4V7jks5l9bz5GqXj for ; Mon, 1 Apr 2024 20:47:49 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from udns.ultimatedns.net (udns.ultimatedns.net [24.113.41.81]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "ultimatedns.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4V7jks1hdzz449x for ; Mon, 1 Apr 2024 20:47:49 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=ultimatedns.net header.s=mx99 header.b=mEoS5Z6P; spf=none (mx1.freebsd.org: domain of bsd-lists@bsdforge.com has no SPF policy when checking 24.113.41.81) smtp.mailfrom=bsd-lists@bsdforge.com Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.16.1/8.16.1) with ESMTP id 431KlZBK065240 for ; Mon, 1 Apr 2024 13:47:42 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=ultimatedns.net; s=mx99; t=1712004462; x=1712005062; r=y; bh=KePng3SQ8pafQuqMqcMkSfKBM4YCfxR11KkS3E7kn1Q=; h=Date:From:To:Subject; b=mEoS5Z6P8NNyJFhz97I6nymEJjxRYljt9O2rOwkLBBtB99bVsc18Tw5Gol03Yc0OV u2Jdn2m2jhv3eNGIVinKoOrq3N4T8exlufMLLBRKBVeXSjX12+oFEHMPCAVBRID3+U NGYqWdetfzSaf58wlQnzf/EeZYQoLO7jEpoTJt0WA45TS1D79UnRTx+3wt0ddBmAYe da3JEOMcU+vJvbP/hrnYe8b3++8rLr6+vKM3V3Gm8s21SPv3IFvVfwgpNDk+PJ0QMT sgxh+/+Rxm409kTRPYKyKIy0c2hLjIfIRz6M9RTH2Jc1PwFdZ3OLI185chngfvXEvi caVrPFGLDlbXg== List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Date: Mon, 01 Apr 2024 13:47:35 -0700 From: Chris To: freebsd-current Subject: Multi cons support has disappeared (on Alder Lake) was: Alt+Fn isn't functional. Has this been removed? User-Agent: UDNSMS/17.0 Message-ID: X-Sender: bsd-lists@bsdforge.com Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Bar: / X-Rspamd-Pre-Result: action=no action; module=multimap; Matched map: local_wl_ip X-Spamd-Result: default: False [0.80 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; R_DKIM_ALLOW(-0.20)[ultimatedns.net:s=mx99]; ONCE_RECEIVED(0.10)[]; MIME_GOOD(-0.10)[text/plain]; local_wl_ip(0.00)[24.113.41.81]; ASN(0.00)[asn:11404, ipnet:24.113.0.0/16, country:US]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; R_SPF_NA(0.00)[no SPF record]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; MIME_TRACE(0.00)[0:+]; FROM_HAS_DN(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[ultimatedns.net:+] X-Rspamd-Queue-Id: 4V7jks1hdzz449x I experience challenges running FreeBSD on my Alder Lake laptop. With some help on the list and Bugzilla, I was able to get Graphics WiFi at least working. But still wasn't as stable as running on more dated CPU's. As it is; I'm only able to use CURRENT. Beginning of last week, in hopes of getting a more stable experience. I wiped the partition (UFS) and unpacked the version available on the FreeBSD ftp servers at that time. I quickly discovered that multi-cons (Ctrl+ Alt+Fn || Alt+Fn) was no longer available. I posted this discovery to the list. But no solution was discovered. I've since attempted to use 2 more different newer versions. Both of them were also w/o multi-con(s) support. What must I do to fix, or uncover the cause of this? I only load the associated GPU module in rc.conf(5) (no keyboard settings). I'm also unable to get multi-cons booting from any of the boot media produced within the last week. Following are some specifics: CPU: 12th Gen Intel(R) Core(TM) i3-1215U (2496.00-MHz K8-class CPU) IdeaPad 3 17IAU7 WORKS: FreeBSD 15.0-CURRENT #0 main-n267640-7a4d1d1df0b2: Thu Jan 18 04:04:32 UTC 2024 DOESN'T WORK: FreeBSD 15.0-CURRENT #0 main-n269036-6baddb6b1176: Fri Mar 29 10:19:43 UTC 2024 root@releng3.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 FreeBSD 15.0-CURRENT #0 main-n268793-220ee18f1964: Thu Mar 14 02:58:39 UTC 2024 root@releng3.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 hostb0@pci0:0:0:0: class=0x060000 rev=0x04 hdr=0x00 vendor=0x8086 device=0x4609 subvendor=0x17aa subdevice=0x3803 vendor = 'Intel Corporation' class = bridge subclass = HOST-PCI vgapci0@pci0:0:2:0: class=0x030000 rev=0x0c hdr=0x00 vendor=0x8086 device=0x46b3 subvendor=0x17aa subdevice=0x3b3a vendor = 'Intel Corporation' device = 'Alder Lake-UP3 GT1 [UHD Graphics]' class = display subclass = VGA none0@pci0:0:4:0: class=0x118000 rev=0x04 hdr=0x00 vendor=0x8086 device=0x461d subvendor=0x17aa subdevice=0x380c vendor = 'Intel Corporation' device = 'Alder Lake Innovation Platform Framework Processor Participant' class = dasp pcib1@pci0:0:6:0: class=0x060400 rev=0x04 hdr=0x01 vendor=0x8086 device=0x464d subvendor=0x17aa subdevice=0x380e vendor = 'Intel Corporation' device = '12th Gen Core Processor PCI Express x4 Controller' class = bridge subclass = PCI-PCI none1@pci0:0:10:0: class=0x118000 rev=0x01 hdr=0x00 vendor=0x8086 device=0x467d subvendor=0x17aa subdevice=0x3813 vendor = 'Intel Corporation' device = 'Platform Monitoring Technology' class = dasp xhci0@pci0:0:13:0: class=0x0c0330 rev=0x04 hdr=0x00 vendor=0x8086 device=0x461e subvendor=0x17aa subdevice=0x3824 vendor = 'Intel Corporation' device = 'Alder Lake-P Thunderbolt 4 USB Controller' class = serial bus subclass = USB xhci1@pci0:0:20:0: class=0x0c0330 rev=0x01 hdr=0x00 vendor=0x8086 device=0x51ed subvendor=0x17aa subdevice=0x3820 vendor = 'Intel Corporation' device = 'Alder Lake PCH USB 3.2 xHCI Host Controller' class = serial bus subclass = USB none2@pci0:0:20:2: class=0x050000 rev=0x01 hdr=0x00 vendor=0x8086 device=0x51ef subvendor=0x17aa subdevice=0x381e vendor = 'Intel Corporation' device = 'Alder Lake PCH Shared SRAM' class = memory subclass = RAM iwlwifi0@pci0:0:20:3: class=0x028000 rev=0x01 hdr=0x00 vendor=0x8086 device=0x51f0 subvendor=0x8086 subdevice=0x0074 vendor = 'Intel Corporation' device = 'Alder Lake-P PCH CNVi WiFi' class = network ig4iic0@pci0:0:21:0: class=0x0c8000 rev=0x01 hdr=0x00 vendor=0x8086 device=0x51e8 subvendor=0x17aa subdevice=0x3812 vendor = 'Intel Corporation' device = 'Alder Lake PCH Serial IO I2C Controller' class = serial bus ig4iic1@pci0:0:21:1: class=0x0c8000 rev=0x01 hdr=0x00 vendor=0x8086 device=0x51e9 subvendor=0x17aa subdevice=0x3814 vendor = 'Intel Corporation' device = 'Alder Lake PCH Serial IO I2C Controller' class = serial bus none3@pci0:0:22:0: class=0x078000 rev=0x01 hdr=0x00 vendor=0x8086 device=0x51e0 subvendor=0x17aa subdevice=0x3815 vendor = 'Intel Corporation' device = 'Alder Lake PCH HECI Controller' class = simple comms ahci0@pci0:0:23:0: class=0x010601 rev=0x01 hdr=0x00 vendor=0x8086 device=0x51d3 subvendor=0x8086 subdevice=0x7270 vendor = 'Intel Corporation' device = 'Alder Lake-P SATA AHCI Controller' class = mass storage subclass = SATA pcib2@pci0:0:29:0: class=0x060400 rev=0x01 hdr=0x01 vendor=0x8086 device=0x51b1 subvendor=0x17aa subdevice=0x381f vendor = 'Intel Corporation' device = 'Alder Lake PCI Express x1 Root Port' class = bridge subclass = PCI-PCI isab0@pci0:0:31:0: class=0x060100 rev=0x01 hdr=0x00 vendor=0x8086 device=0x5182 subvendor=0x17aa subdevice=0x382b vendor = 'Intel Corporation' device = 'Alder Lake PCH eSPI Controller' class = bridge subclass = PCI-ISA hdac0@pci0:0:31:3: class=0x040380 rev=0x01 hdr=0x00 vendor=0x8086 device=0x51c8 subvendor=0x17aa subdevice=0x3881 vendor = 'Intel Corporation' device = 'Alder Lake PCH-P High Definition Audio Controller' class = multimedia subclass = HDA ichsmb0@pci0:0:31:4: class=0x0c0500 rev=0x01 hdr=0x00 vendor=0x8086 device=0x51a3 subvendor=0x17aa subdevice=0x382f vendor = 'Intel Corporation' device = 'Alder Lake PCH-P SMBus Host Controller' class = serial bus subclass = SMBus none4@pci0:0:31:5: class=0x0c8000 rev=0x01 hdr=0x00 vendor=0x8086 device=0x51a4 subvendor=0x17aa subdevice=0x381c vendor = 'Intel Corporation' device = 'Alder Lake-P PCH SPI Controller' class = serial bus nvme0@pci0:1:0:0: class=0x010802 rev=0x01 hdr=0x00 vendor=0x2646 device=0x5013 subvendor=0x2646 subdevice=0x5013 vendor = 'Kingston Technology Company, Inc.' device = 'KC3000/FURY Renegade NVMe SSD E18' class = mass storage subclass = NVM sdhci_pci0@pci0:2:0:0: class=0x080501 rev=0x01 hdr=0x00 vendor=0x1217 device=0x8621 subvendor=0x17aa subdevice=0x3874 vendor = 'O2 Micro, Inc.' device = 'SD/MMC Card Reader Controller' class = base peripheral subclass = SD host controller Id Refs Address Size Name 1 95 0xffffffff80200000 1d527c0 kernel 2 1 0xffffffff81f54000 287e8 fusefs.ko 3 1 0xffffffff82d8f000 1e3228 i915kms.ko 4 2 0xffffffff82f73000 85090 drm.ko 5 1 0xffffffff82ff9000 22b8 iic.ko 6 2 0xffffffff82ffc000 40e9 linuxkpi_video.ko 7 3 0xffffffff83001000 7358 dmabuf.ko 8 3 0xffffffff83009000 3378 lindebugfs.ko 9 1 0xffffffff8300d000 c338 ttm.ko 10 1 0xffffffff8301a000 5760 cuse.ko 11 1 0xffffffff83020000 3390 acpi_wmi.ko 12 1 0xffffffff83024000 4250 ichsmb.ko 13 1 0xffffffff83029000 2178 smbus.ko 14 1 0xffffffff8302c000 91260 if_iwlwifi.ko 15 1 0xffffffff830be000 5f90 ig4.ko 16 1 0xffffffff830c4000 4d20 ng_ubt.ko 17 3 0xffffffff830c9000 bbb8 netgraph.ko 18 2 0xffffffff830d5000 a250 ng_hci.ko 19 2 0xffffffff830e0000 2670 ng_bluetooth.ko 20 1 0xffffffff830e3000 3218 iichid.ko 21 5 0xffffffff830e7000 3380 hidbus.ko 22 1 0xffffffff830eb000 21e8 hms.ko 23 1 0xffffffff830ee000 40a8 hidmap.ko 24 1 0xffffffff830f3000 3355 hmt.ko 25 1 0xffffffff830f7000 22cc hconf.ko 26 1 0xffffffff830fa000 2260 pflog.ko 27 1 0xffffffff830fd000 56540 pf.ko 28 1 0xffffffff83154000 3560 fdescfs.ko Thanks! --Chris From nobody Mon Apr 1 22:29:51 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4V7m0m3gbJz5FHS6 for ; Mon, 1 Apr 2024 22:30:00 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from udns.ultimatedns.net (udns.ultimatedns.net [24.113.41.81]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "ultimatedns.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4V7m0k589Yz4HpT for ; Mon, 1 Apr 2024 22:29:58 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=ultimatedns.net header.s=mx99 header.b=vG9bdKMB; spf=none (mx1.freebsd.org: domain of bsd-lists@bsdforge.com has no SPF policy when checking 24.113.41.81) smtp.mailfrom=bsd-lists@bsdforge.com Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.16.1/8.16.1) with ESMTP id 431MTq3B000602; Mon, 1 Apr 2024 15:29:58 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=ultimatedns.net; s=mx99; t=1712010598; x=1712011198; r=y; bh=ovXgOVMVUOsvUImzX4xj1Dsp15iSjn8fycNNsq9jgtY=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=vG9bdKMBF0y37K9r4TMh8tsoH/cerh/y/mxXE80pBCMplwWKy86gTEADtsiLkRvIU LEtqS6YnEBiFAno6HB6Ac+NwDPwa6bdMIWuDQUD0AsV1fiwPuQfXkl/ATJYki87hgD dZogQUNYSiPFzoBKAN6GS39VKjkizvWVC7UIHg8Su9kriddvmqu/AWbKLZeIocrteT 6BoSUT2quxJGeOm4WqROcbuaq8F0j3nP7UuyjuGHQI2YybqYgX8zZBtg+H9WrH1pOx ldTw4pbBcxGUuF2vpMMg2UnkfF60IU43XWsRJDCptvIaHKfEIt+1MKFij9siFuRufC +yfvGxU/YKKjQ== List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Date: Mon, 01 Apr 2024 15:29:51 -0700 From: Chris To: Michael Gmelin Cc: freebsd-current Subject: Re: Multi cons support has disappeared (on Alder Lake) was: Alt+Fn isn't functional. Has this been removed? In-Reply-To: <310A6EC4-33F0-4A75-8D3B-AB9417779A31@grem.de> References: <310A6EC4-33F0-4A75-8D3B-AB9417779A31@grem.de> User-Agent: UDNSMS/17.0 Message-ID: X-Sender: bsd-lists@bsdforge.com Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spamd-Bar: / X-Rspamd-Pre-Result: action=no action; module=multimap; Matched map: local_wl_ip X-Spamd-Result: default: False [0.80 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; R_DKIM_ALLOW(-0.20)[ultimatedns.net:s=mx99]; ONCE_RECEIVED(0.10)[]; MIME_GOOD(-0.10)[text/plain]; ASN(0.00)[asn:11404, ipnet:24.113.0.0/16, country:US]; local_wl_ip(0.00)[24.113.41.81]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FROM_HAS_DN(0.00)[]; DKIM_TRACE(0.00)[ultimatedns.net:+] X-Rspamd-Queue-Id: 4V7m0k589Yz4HpT On 2024-04-01 14:57, Michael Gmelin wrote: > You never responded to my (and T’s) message - so I assume the suggestions > made no > difference? Right, and thank you for the reply. I (indirectly) answered it here when I indicated that I had no references to "keyboard settings in my rc.conf(5)". :) Any other thoughts? Thanks again, Michael! --Chris > > -m > >> On 1. Apr 2024, at 22:48, Chris wrote: >> >> I experience challenges running FreeBSD on my Alder Lake laptop. >> With some help on the list and Bugzilla, I was able to get Graphics >> WiFi at least working. But still wasn't as stable as running on >> more dated CPU's. As it is; I'm only able to use CURRENT. Beginning >> of last week, in hopes of getting a more stable experience. I wiped >> the partition (UFS) and unpacked the version available on the FreeBSD >> ftp servers at that time. I quickly discovered that multi-cons (Ctrl+ >> Alt+Fn || Alt+Fn) was no longer available. I posted this discovery to >> the list. But no solution was discovered. I've since attempted to use >> 2 more different newer versions. Both of them were also w/o multi-con(s) >> support. What must I do to fix, or uncover the cause of this? >> I only load the associated GPU module in rc.conf(5) (no keyboard settings). >> I'm also unable to get multi-cons booting from any of the boot media >> produced within the last week. >> >> Following are some specifics: >> >> CPU: 12th Gen Intel(R) Core(TM) i3-1215U (2496.00-MHz K8-class CPU) >> >> IdeaPad 3 17IAU7 >> >> WORKS: >> FreeBSD 15.0-CURRENT #0 main-n267640-7a4d1d1df0b2: >> Thu Jan 18 04:04:32 UTC 2024 >> >> DOESN'T WORK: >> FreeBSD 15.0-CURRENT #0 main-n269036-6baddb6b1176: >> Fri Mar 29 10:19:43 UTC 2024 >> root@releng3.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 >> >> FreeBSD 15.0-CURRENT #0 main-n268793-220ee18f1964: >> Thu Mar 14 02:58:39 UTC 2024 >> root@releng3.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 >> >> hostb0@pci0:0:0:0: class=0x060000 rev=0x04 hdr=0x00 vendor=0x8086 >> device=0x4609 subvendor=0x17aa subdevice=0x3803 >> vendor = 'Intel Corporation' >> class = bridge >> subclass = HOST-PCI >> vgapci0@pci0:0:2:0: class=0x030000 rev=0x0c hdr=0x00 vendor=0x8086 >> device=0x46b3 subvendor=0x17aa subdevice=0x3b3a >> vendor = 'Intel Corporation' >> device = 'Alder Lake-UP3 GT1 [UHD Graphics]' >> class = display >> subclass = VGA >> none0@pci0:0:4:0: class=0x118000 rev=0x04 hdr=0x00 vendor=0x8086 >> device=0x461d subvendor=0x17aa subdevice=0x380c >> vendor = 'Intel Corporation' >> device = 'Alder Lake Innovation Platform Framework Processor >> Participant' >> class = dasp >> pcib1@pci0:0:6:0: class=0x060400 rev=0x04 hdr=0x01 vendor=0x8086 >> device=0x464d subvendor=0x17aa subdevice=0x380e >> vendor = 'Intel Corporation' >> device = '12th Gen Core Processor PCI Express x4 Controller' >> class = bridge >> subclass = PCI-PCI >> none1@pci0:0:10:0: class=0x118000 rev=0x01 hdr=0x00 vendor=0x8086 >> device=0x467d subvendor=0x17aa subdevice=0x3813 >> vendor = 'Intel Corporation' >> device = 'Platform Monitoring Technology' >> class = dasp >> xhci0@pci0:0:13:0: class=0x0c0330 rev=0x04 hdr=0x00 vendor=0x8086 >> device=0x461e subvendor=0x17aa subdevice=0x3824 >> vendor = 'Intel Corporation' >> device = 'Alder Lake-P Thunderbolt 4 USB Controller' >> class = serial bus >> subclass = USB >> xhci1@pci0:0:20:0: class=0x0c0330 rev=0x01 hdr=0x00 vendor=0x8086 >> device=0x51ed subvendor=0x17aa subdevice=0x3820 >> vendor = 'Intel Corporation' >> device = 'Alder Lake PCH USB 3.2 xHCI Host Controller' >> class = serial bus >> subclass = USB >> none2@pci0:0:20:2: class=0x050000 rev=0x01 hdr=0x00 vendor=0x8086 >> device=0x51ef subvendor=0x17aa subdevice=0x381e >> vendor = 'Intel Corporation' >> device = 'Alder Lake PCH Shared SRAM' >> class = memory >> subclass = RAM >> iwlwifi0@pci0:0:20:3: class=0x028000 rev=0x01 hdr=0x00 vendor=0x8086 >> device=0x51f0 subvendor=0x8086 subdevice=0x0074 >> vendor = 'Intel Corporation' >> device = 'Alder Lake-P PCH CNVi WiFi' >> class = network >> ig4iic0@pci0:0:21:0: class=0x0c8000 rev=0x01 hdr=0x00 vendor=0x8086 >> device=0x51e8 subvendor=0x17aa subdevice=0x3812 >> vendor = 'Intel Corporation' >> device = 'Alder Lake PCH Serial IO I2C Controller' >> class = serial bus >> ig4iic1@pci0:0:21:1: class=0x0c8000 rev=0x01 hdr=0x00 vendor=0x8086 >> device=0x51e9 subvendor=0x17aa subdevice=0x3814 >> vendor = 'Intel Corporation' >> device = 'Alder Lake PCH Serial IO I2C Controller' >> class = serial bus >> none3@pci0:0:22:0: class=0x078000 rev=0x01 hdr=0x00 vendor=0x8086 >> device=0x51e0 subvendor=0x17aa subdevice=0x3815 >> vendor = 'Intel Corporation' >> device = 'Alder Lake PCH HECI Controller' >> class = simple comms >> ahci0@pci0:0:23:0: class=0x010601 rev=0x01 hdr=0x00 vendor=0x8086 >> device=0x51d3 subvendor=0x8086 subdevice=0x7270 >> vendor = 'Intel Corporation' >> device = 'Alder Lake-P SATA AHCI Controller' >> class = mass storage >> subclass = SATA >> pcib2@pci0:0:29:0: class=0x060400 rev=0x01 hdr=0x01 vendor=0x8086 >> device=0x51b1 subvendor=0x17aa subdevice=0x381f >> vendor = 'Intel Corporation' >> device = 'Alder Lake PCI Express x1 Root Port' >> class = bridge >> subclass = PCI-PCI >> isab0@pci0:0:31:0: class=0x060100 rev=0x01 hdr=0x00 vendor=0x8086 >> device=0x5182 subvendor=0x17aa subdevice=0x382b >> vendor = 'Intel Corporation' >> device = 'Alder Lake PCH eSPI Controller' >> class = bridge >> subclass = PCI-ISA >> hdac0@pci0:0:31:3: class=0x040380 rev=0x01 hdr=0x00 vendor=0x8086 >> device=0x51c8 subvendor=0x17aa subdevice=0x3881 >> vendor = 'Intel Corporation' >> device = 'Alder Lake PCH-P High Definition Audio Controller' >> class = multimedia >> subclass = HDA >> ichsmb0@pci0:0:31:4: class=0x0c0500 rev=0x01 hdr=0x00 vendor=0x8086 >> device=0x51a3 subvendor=0x17aa subdevice=0x382f >> vendor = 'Intel Corporation' >> device = 'Alder Lake PCH-P SMBus Host Controller' >> class = serial bus >> subclass = SMBus >> none4@pci0:0:31:5: class=0x0c8000 rev=0x01 hdr=0x00 vendor=0x8086 >> device=0x51a4 subvendor=0x17aa subdevice=0x381c >> vendor = 'Intel Corporation' >> device = 'Alder Lake-P PCH SPI Controller' >> class = serial bus >> nvme0@pci0:1:0:0: class=0x010802 rev=0x01 hdr=0x00 vendor=0x2646 >> device=0x5013 subvendor=0x2646 subdevice=0x5013 >> vendor = 'Kingston Technology Company, Inc.' >> device = 'KC3000/FURY Renegade NVMe SSD E18' >> class = mass storage >> subclass = NVM >> sdhci_pci0@pci0:2:0:0: class=0x080501 rev=0x01 hdr=0x00 vendor=0x1217 >> device=0x8621 subvendor=0x17aa subdevice=0x3874 >> vendor = 'O2 Micro, Inc.' >> device = 'SD/MMC Card Reader Controller' >> class = base peripheral >> subclass = SD host controller >> >> Id Refs Address Size Name >> 1 95 0xffffffff80200000 1d527c0 kernel >> 2 1 0xffffffff81f54000 287e8 fusefs.ko >> 3 1 0xffffffff82d8f000 1e3228 i915kms.ko >> 4 2 0xffffffff82f73000 85090 drm.ko >> 5 1 0xffffffff82ff9000 22b8 iic.ko >> 6 2 0xffffffff82ffc000 40e9 linuxkpi_video.ko >> 7 3 0xffffffff83001000 7358 dmabuf.ko >> 8 3 0xffffffff83009000 3378 lindebugfs.ko >> 9 1 0xffffffff8300d000 c338 ttm.ko >> 10 1 0xffffffff8301a000 5760 cuse.ko >> 11 1 0xffffffff83020000 3390 acpi_wmi.ko >> 12 1 0xffffffff83024000 4250 ichsmb.ko >> 13 1 0xffffffff83029000 2178 smbus.ko >> 14 1 0xffffffff8302c000 91260 if_iwlwifi.ko >> 15 1 0xffffffff830be000 5f90 ig4.ko >> 16 1 0xffffffff830c4000 4d20 ng_ubt.ko >> 17 3 0xffffffff830c9000 bbb8 netgraph.ko >> 18 2 0xffffffff830d5000 a250 ng_hci.ko >> 19 2 0xffffffff830e0000 2670 ng_bluetooth.ko >> 20 1 0xffffffff830e3000 3218 iichid.ko >> 21 5 0xffffffff830e7000 3380 hidbus.ko >> 22 1 0xffffffff830eb000 21e8 hms.ko >> 23 1 0xffffffff830ee000 40a8 hidmap.ko >> 24 1 0xffffffff830f3000 3355 hmt.ko >> 25 1 0xffffffff830f7000 22cc hconf.ko >> 26 1 0xffffffff830fa000 2260 pflog.ko >> 27 1 0xffffffff830fd000 56540 pf.ko >> 28 1 0xffffffff83154000 3560 fdescfs.ko >> >> >> Thanks! >> >> --Chris >> From nobody Tue Apr 2 05:51:10 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4V7xp850bmz5G91F for ; Tue, 2 Apr 2024 05:51:28 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-yb1-xb29.google.com (mail-yb1-xb29.google.com [IPv6:2607:f8b0:4864:20::b29]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4V7xp83Fm4z451g for ; Tue, 2 Apr 2024 05:51:28 +0000 (UTC) (envelope-from kob6558@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-yb1-xb29.google.com with SMTP id 3f1490d57ef6-db4364ecd6aso4509352276.2 for ; Mon, 01 Apr 2024 22:51:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1712037087; x=1712641887; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=YCl5eY0wUB/uFpeWoB/CzV3ykEMVmxvHMKxsBSi/qkI=; b=DU/tjkU04imtOBeoS+xzxyxaFKJrbkf07Mwgzgb7yZ7qxFw5s151CqBJdTZ9K1V5qj CcAUq81X2aObGZh9rezBImqDbeLUKE3lwexMnR+cV/5NSF9d6+1yu2Z72TQQ1q6B5huh KUsx6lQy6JokDJ1EkRUodk6JK+J6grjK9oFc6+NF2sOs7/HE4li2W6P3SB20A/IiOowB I+srVTTGMLl79lVbcPSEgfnmjM0cgqLYf6e2WeFf5ELqFKPk9kntoDr2EZAs4ZaCrxSX eYC7Vkitt/aSwAFO/tlHqEWDcaDjevBsN/fEaR2eZ+HMCvo7316GJTr0yBUHTFAMQLto fmLw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1712037087; x=1712641887; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=YCl5eY0wUB/uFpeWoB/CzV3ykEMVmxvHMKxsBSi/qkI=; b=O8+ZYtk2/kphjvaihBHR+pO/Bl0BC2D7OZnGQhTzQrt6oWujrfaNdARYAREeDZMH6l JS0iP1cpMtN89+nqWkzaeYiVK5czET5ZW3s8+kISbwZeUyRJK+Jdt3OUOLK7BdZryv7U WXG6sC8vhz+9j9lSy4gHObo6opwa2v8atDMvaQRNYEyEy2di3/d4uzVweAqONkP521I3 /W2FFTdj38QnBEpacpFVoazr4bFy/cxgtuRnuDme+v2XlrUBrDdLY8dht4npQSdOdTN5 frN4Yc6A6y7fz07DhO/AEXQuXElZeon+U0El0z8AymhV5f4Bh4yFqtxK61x3yg9Ulnf3 JQuw== X-Gm-Message-State: AOJu0YzF+O+YZNiNXEY+DFF0cXvaXozqaIW16ernCIGqEYkmD+eRV+YU iNFKL4Esq2dDxhYsA5/D3/72qXKrM82vxwTm3qg6LPfm44PrGbT2kzdiL+nerNkWvk/laXZLkz/ M+nCTFdyXYY2j+Hp2boklQ39mPleDDogoZBA= X-Google-Smtp-Source: AGHT+IHvZFbSr3FEC/1QB8t6l+yPbn65bsW/mzBLkjP2ViNXCBWagy4TYjvLZLfC1FIB8khb8dokHO/ZJZ/ksqP9X9g= X-Received: by 2002:a25:ab53:0:b0:dcf:f4d3:3a16 with SMTP id u77-20020a25ab53000000b00dcff4d33a16mr9240751ybi.45.1712037086737; Mon, 01 Apr 2024 22:51:26 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Kevin Oberman Date: Mon, 1 Apr 2024 22:51:10 -0700 Message-ID: Subject: Re: Multi cons support has disappeared (on Alder Lake) was: Alt+Fn isn't functional. Has this been removed? To: Chris Cc: freebsd-current Content-Type: multipart/alternative; boundary="00000000000065c0e4061516b2b5" X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4V7xp83Fm4z451g --00000000000065c0e4061516b2b5 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, Apr 1, 2024 at 3:05=E2=80=AFPM Chris wrote= : > I experience challenges running FreeBSD on my Alder Lake laptop. > With some help on the list and Bugzilla, I was able to get Graphics > WiFi at least working. But still wasn't as stable as running on > more dated CPU's. As it is; I'm only able to use CURRENT. Beginning > of last week, in hopes of getting a more stable experience. I wiped > the partition (UFS) and unpacked the version available on the FreeBSD > ftp servers at that time. I quickly discovered that multi-cons (Ctrl+ > Alt+Fn || Alt+Fn) was no longer available. I posted this discovery to > the list. But no solution was discovered. I've since attempted to use > 2 more different newer versions. Both of them were also w/o multi-con(s) > support. What must I do to fix, or uncover the cause of this? > I only load the associated GPU module in rc.conf(5) (no keyboard settings= ). > I'm also unable to get multi-cons booting from any of the boot media > produced within the last week. > > Following are some specifics: > > CPU: 12th Gen Intel(R) Core(TM) i3-1215U (2496.00-MHz K8-class CPU) > > IdeaPad 3 17IAU7 > > WORKS: > FreeBSD 15.0-CURRENT #0 main-n267640-7a4d1d1df0b2: > Thu Jan 18 04:04:32 UTC 2024 > > DOESN'T WORK: > FreeBSD 15.0-CURRENT #0 main-n269036-6baddb6b1176: > Fri Mar 29 10:19:43 UTC 2024 > root@releng3.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC > amd64 > > FreeBSD 15.0-CURRENT #0 main-n268793-220ee18f1964: > Thu Mar 14 02:58:39 UTC 2024 > root@releng3.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC > amd64 > > hostb0@pci0:0:0:0: class=3D0x060000 rev=3D0x04 hdr=3D0x00 vendor=3D0= x8086 > device=3D0x4609 subvendor=3D0x17aa subdevice=3D0x3803 > vendor =3D 'Intel Corporation' > class =3D bridge > subclass =3D HOST-PCI > vgapci0@pci0:0:2:0: class=3D0x030000 rev=3D0x0c hdr=3D0x00 vendor=3D0= x8086 > device=3D0x46b3 subvendor=3D0x17aa subdevice=3D0x3b3a > vendor =3D 'Intel Corporation' > device =3D 'Alder Lake-UP3 GT1 [UHD Graphics]' > class =3D display > subclass =3D VGA > none0@pci0:0:4:0: class=3D0x118000 rev=3D0x04 hdr=3D0x00 vendor=3D0= x8086 > device=3D0x461d subvendor=3D0x17aa subdevice=3D0x380c > vendor =3D 'Intel Corporation' > device =3D 'Alder Lake Innovation Platform Framework Processor > Participant' > class =3D dasp > pcib1@pci0:0:6:0: class=3D0x060400 rev=3D0x04 hdr=3D0x01 vendor=3D0= x8086 > device=3D0x464d subvendor=3D0x17aa subdevice=3D0x380e > vendor =3D 'Intel Corporation' > device =3D '12th Gen Core Processor PCI Express x4 Controller' > class =3D bridge > subclass =3D PCI-PCI > none1@pci0:0:10:0: class=3D0x118000 rev=3D0x01 hdr=3D0x00 vendor=3D0= x8086 > device=3D0x467d subvendor=3D0x17aa subdevice=3D0x3813 > vendor =3D 'Intel Corporation' > device =3D 'Platform Monitoring Technology' > class =3D dasp > xhci0@pci0:0:13:0: class=3D0x0c0330 rev=3D0x04 hdr=3D0x00 vendor=3D0= x8086 > device=3D0x461e subvendor=3D0x17aa subdevice=3D0x3824 > vendor =3D 'Intel Corporation' > device =3D 'Alder Lake-P Thunderbolt 4 USB Controller' > class =3D serial bus > subclass =3D USB > xhci1@pci0:0:20:0: class=3D0x0c0330 rev=3D0x01 hdr=3D0x00 vendor=3D0= x8086 > device=3D0x51ed subvendor=3D0x17aa subdevice=3D0x3820 > vendor =3D 'Intel Corporation' > device =3D 'Alder Lake PCH USB 3.2 xHCI Host Controller' > class =3D serial bus > subclass =3D USB > none2@pci0:0:20:2: class=3D0x050000 rev=3D0x01 hdr=3D0x00 vendor=3D0= x8086 > device=3D0x51ef subvendor=3D0x17aa subdevice=3D0x381e > vendor =3D 'Intel Corporation' > device =3D 'Alder Lake PCH Shared SRAM' > class =3D memory > subclass =3D RAM > iwlwifi0@pci0:0:20:3: class=3D0x028000 rev=3D0x01 hdr=3D0x00 vendor=3D0= x8086 > device=3D0x51f0 subvendor=3D0x8086 subdevice=3D0x0074 > vendor =3D 'Intel Corporation' > device =3D 'Alder Lake-P PCH CNVi WiFi' > class =3D network > ig4iic0@pci0:0:21:0: class=3D0x0c8000 rev=3D0x01 hdr=3D0x00 vendor=3D0= x8086 > device=3D0x51e8 subvendor=3D0x17aa subdevice=3D0x3812 > vendor =3D 'Intel Corporation' > device =3D 'Alder Lake PCH Serial IO I2C Controller' > class =3D serial bus > ig4iic1@pci0:0:21:1: class=3D0x0c8000 rev=3D0x01 hdr=3D0x00 vendor=3D0= x8086 > device=3D0x51e9 subvendor=3D0x17aa subdevice=3D0x3814 > vendor =3D 'Intel Corporation' > device =3D 'Alder Lake PCH Serial IO I2C Controller' > class =3D serial bus > none3@pci0:0:22:0: class=3D0x078000 rev=3D0x01 hdr=3D0x00 vendor=3D0= x8086 > device=3D0x51e0 subvendor=3D0x17aa subdevice=3D0x3815 > vendor =3D 'Intel Corporation' > device =3D 'Alder Lake PCH HECI Controller' > class =3D simple comms > ahci0@pci0:0:23:0: class=3D0x010601 rev=3D0x01 hdr=3D0x00 vendor=3D0= x8086 > device=3D0x51d3 subvendor=3D0x8086 subdevice=3D0x7270 > vendor =3D 'Intel Corporation' > device =3D 'Alder Lake-P SATA AHCI Controller' > class =3D mass storage > subclass =3D SATA > pcib2@pci0:0:29:0: class=3D0x060400 rev=3D0x01 hdr=3D0x01 vendor=3D0= x8086 > device=3D0x51b1 subvendor=3D0x17aa subdevice=3D0x381f > vendor =3D 'Intel Corporation' > device =3D 'Alder Lake PCI Express x1 Root Port' > class =3D bridge > subclass =3D PCI-PCI > isab0@pci0:0:31:0: class=3D0x060100 rev=3D0x01 hdr=3D0x00 vendor=3D0= x8086 > device=3D0x5182 subvendor=3D0x17aa subdevice=3D0x382b > vendor =3D 'Intel Corporation' > device =3D 'Alder Lake PCH eSPI Controller' > class =3D bridge > subclass =3D PCI-ISA > hdac0@pci0:0:31:3: class=3D0x040380 rev=3D0x01 hdr=3D0x00 vendor=3D0= x8086 > device=3D0x51c8 subvendor=3D0x17aa subdevice=3D0x3881 > vendor =3D 'Intel Corporation' > device =3D 'Alder Lake PCH-P High Definition Audio Controller' > class =3D multimedia > subclass =3D HDA > ichsmb0@pci0:0:31:4: class=3D0x0c0500 rev=3D0x01 hdr=3D0x00 vendor=3D0= x8086 > device=3D0x51a3 subvendor=3D0x17aa subdevice=3D0x382f > vendor =3D 'Intel Corporation' > device =3D 'Alder Lake PCH-P SMBus Host Controller' > class =3D serial bus > subclass =3D SMBus > none4@pci0:0:31:5: class=3D0x0c8000 rev=3D0x01 hdr=3D0x00 vendor=3D0= x8086 > device=3D0x51a4 subvendor=3D0x17aa subdevice=3D0x381c > vendor =3D 'Intel Corporation' > device =3D 'Alder Lake-P PCH SPI Controller' > class =3D serial bus > nvme0@pci0:1:0:0: class=3D0x010802 rev=3D0x01 hdr=3D0x00 vendor=3D0= x2646 > device=3D0x5013 subvendor=3D0x2646 subdevice=3D0x5013 > vendor =3D 'Kingston Technology Company, Inc.' > device =3D 'KC3000/FURY Renegade NVMe SSD E18' > class =3D mass storage > subclass =3D NVM > sdhci_pci0@pci0:2:0:0: class=3D0x080501 rev=3D0x01 hdr=3D0x00 vendor=3D0= x1217 > device=3D0x8621 subvendor=3D0x17aa subdevice=3D0x3874 > vendor =3D 'O2 Micro, Inc.' > device =3D 'SD/MMC Card Reader Controller' > class =3D base peripheral > subclass =3D SD host controller > > Id Refs Address Size Name > 1 95 0xffffffff80200000 1d527c0 kernel > 2 1 0xffffffff81f54000 287e8 fusefs.ko > 3 1 0xffffffff82d8f000 1e3228 i915kms.ko > 4 2 0xffffffff82f73000 85090 drm.ko > 5 1 0xffffffff82ff9000 22b8 iic.ko > 6 2 0xffffffff82ffc000 40e9 linuxkpi_video.ko > 7 3 0xffffffff83001000 7358 dmabuf.ko > 8 3 0xffffffff83009000 3378 lindebugfs.ko > 9 1 0xffffffff8300d000 c338 ttm.ko > 10 1 0xffffffff8301a000 5760 cuse.ko > 11 1 0xffffffff83020000 3390 acpi_wmi.ko > 12 1 0xffffffff83024000 4250 ichsmb.ko > 13 1 0xffffffff83029000 2178 smbus.ko > 14 1 0xffffffff8302c000 91260 if_iwlwifi.ko > 15 1 0xffffffff830be000 5f90 ig4.ko > 16 1 0xffffffff830c4000 4d20 ng_ubt.ko > 17 3 0xffffffff830c9000 bbb8 netgraph.ko > 18 2 0xffffffff830d5000 a250 ng_hci.ko > 19 2 0xffffffff830e0000 2670 ng_bluetooth.ko > 20 1 0xffffffff830e3000 3218 iichid.ko > 21 5 0xffffffff830e7000 3380 hidbus.ko > 22 1 0xffffffff830eb000 21e8 hms.ko > 23 1 0xffffffff830ee000 40a8 hidmap.ko > 24 1 0xffffffff830f3000 3355 hmt.ko > 25 1 0xffffffff830f7000 22cc hconf.ko > 26 1 0xffffffff830fa000 2260 pflog.ko > 27 1 0xffffffff830fd000 56540 pf.ko > 28 1 0xffffffff83154000 3560 fdescfs.ko > > > Thanks! > > --Chri I have a T16 and ran into that issue. It may be that BIOS changes have broken things, but I found that, by default, the F keys control volume, screen brightness, and many other things. I can use Fn+F[1-12] to perform traditional function key functions. I found that bios has an option to make the traditional functions the default which is how I am running today and have since shortly after I purchased the computer. One I set that BIOS option, everything worked "properly". I now use Fn+F[1-12] to adjust volume and screen brightness. I hope to get mute to work, but I need to figure out which event is set when Fn+F1 is pressed to write trivial devd support for it. BTW, if you have not found it, Fn+K is screen lock. Most everything on my T16 now works with FreeBSD CURRENT. --=20 Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 --00000000000065c0e4061516b2b5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Mon, Apr 1, 2024 at 3:05=E2= =80=AFPM Chris <bsd-lists@bsdf= orge.com> wrote:
I experience challenges running FreeBS= D on my Alder Lake laptop.
With some help on the list and Bugzilla, I was able to get Graphics
WiFi at least working. But still wasn't as stable as running on
more dated CPU's. As it is; I'm only able to use CURRENT. Beginning=
of last week, in hopes of getting a more stable experience. I wiped
the partition (UFS) and unpacked the version available on the FreeBSD
ftp servers at that time. I quickly discovered that multi-cons (Ctrl+
Alt+Fn || Alt+Fn) was no longer available. I posted this discovery to
the list. But no solution was discovered. I've since attempted to use 2 more different newer versions. Both of them were also w/o multi-con(s) support. What must I do to fix, or uncover the cause of this?
I only load the associated GPU module in rc.conf(5) (no keyboard settings).=
I'm also unable to get multi-cons booting from any of the boot media produced within the last week.

Following are some specifics:

CPU: 12th Gen Intel(R) Core(TM) i3-1215U (2496.00-MHz K8-class CPU)

IdeaPad 3 17IAU7

WORKS:
FreeBSD 15.0-CURRENT #0 main-n267640-7a4d1d1df0b2:
Thu Jan 18 04:04:32 UTC 2024

DOESN'T WORK:
FreeBSD 15.0-CURRENT #0 main-n269036-6baddb6b1176:
Fri Mar 29 10:19:43 UTC 2024
root@releng3.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64=

FreeBSD 15.0-CURRENT #0 main-n268793-220ee18f1964:
Thu Mar 14 02:58:39 UTC 2024
root@releng3.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64=

hostb0@pci0:0:0:0:=C2=A0 =C2=A0 =C2=A0 class=3D0x060000 rev=3D0x04 hdr=3D0x= 00 vendor=3D0x8086
device=3D0x4609 subvendor=3D0x17aa subdevice=3D0x3803
=C2=A0 =C2=A0 =C2=A0vendor=C2=A0 =C2=A0 =C2=A0=3D 'Intel Corporation= 9;
=C2=A0 =C2=A0 =C2=A0class=C2=A0 =C2=A0 =C2=A0 =3D bridge
=C2=A0 =C2=A0 =C2=A0subclass=C2=A0 =C2=A0=3D HOST-PCI
vgapci0@pci0:0:2:0:=C2=A0 =C2=A0 =C2=A0class=3D0x030000 rev=3D0x0c hdr=3D0x= 00 vendor=3D0x8086
device=3D0x46b3 subvendor=3D0x17aa subdevice=3D0x3b3a
=C2=A0 =C2=A0 =C2=A0vendor=C2=A0 =C2=A0 =C2=A0=3D 'Intel Corporation= 9;
=C2=A0 =C2=A0 =C2=A0device=C2=A0 =C2=A0 =C2=A0=3D 'Alder Lake-UP3 GT1 [= UHD Graphics]'
=C2=A0 =C2=A0 =C2=A0class=C2=A0 =C2=A0 =C2=A0 =3D display
=C2=A0 =C2=A0 =C2=A0subclass=C2=A0 =C2=A0=3D VGA
none0@pci0:0:4:0:=C2=A0 =C2=A0 =C2=A0 =C2=A0class=3D0x118000 rev=3D0x04 hdr= =3D0x00 vendor=3D0x8086
device=3D0x461d subvendor=3D0x17aa subdevice=3D0x380c
=C2=A0 =C2=A0 =C2=A0vendor=C2=A0 =C2=A0 =C2=A0=3D 'Intel Corporation= 9;
=C2=A0 =C2=A0 =C2=A0device=C2=A0 =C2=A0 =C2=A0=3D 'Alder Lake Innovatio= n Platform Framework Processor
Participant'
=C2=A0 =C2=A0 =C2=A0class=C2=A0 =C2=A0 =C2=A0 =3D dasp
pcib1@pci0:0:6:0:=C2=A0 =C2=A0 =C2=A0 =C2=A0class=3D0x060400 rev=3D0x04 hdr= =3D0x01 vendor=3D0x8086
device=3D0x464d subvendor=3D0x17aa subdevice=3D0x380e
=C2=A0 =C2=A0 =C2=A0vendor=C2=A0 =C2=A0 =C2=A0=3D 'Intel Corporation= 9;
=C2=A0 =C2=A0 =C2=A0device=C2=A0 =C2=A0 =C2=A0=3D '12th Gen Core Proces= sor PCI Express x4 Controller'
=C2=A0 =C2=A0 =C2=A0class=C2=A0 =C2=A0 =C2=A0 =3D bridge
=C2=A0 =C2=A0 =C2=A0subclass=C2=A0 =C2=A0=3D PCI-PCI
none1@pci0:0:10:0:=C2=A0 =C2=A0 =C2=A0 class=3D0x118000 rev=3D0x01 hdr=3D0x= 00 vendor=3D0x8086
device=3D0x467d subvendor=3D0x17aa subdevice=3D0x3813
=C2=A0 =C2=A0 =C2=A0vendor=C2=A0 =C2=A0 =C2=A0=3D 'Intel Corporation= 9;
=C2=A0 =C2=A0 =C2=A0device=C2=A0 =C2=A0 =C2=A0=3D 'Platform Monitoring = Technology'
=C2=A0 =C2=A0 =C2=A0class=C2=A0 =C2=A0 =C2=A0 =3D dasp
xhci0@pci0:0:13:0:=C2=A0 =C2=A0 =C2=A0 class=3D0x0c0330 rev=3D0x04 hdr=3D0x= 00 vendor=3D0x8086
device=3D0x461e subvendor=3D0x17aa subdevice=3D0x3824
=C2=A0 =C2=A0 =C2=A0vendor=C2=A0 =C2=A0 =C2=A0=3D 'Intel Corporation= 9;
=C2=A0 =C2=A0 =C2=A0device=C2=A0 =C2=A0 =C2=A0=3D 'Alder Lake-P Thunder= bolt 4 USB Controller'
=C2=A0 =C2=A0 =C2=A0class=C2=A0 =C2=A0 =C2=A0 =3D serial bus
=C2=A0 =C2=A0 =C2=A0subclass=C2=A0 =C2=A0=3D USB
xhci1@pci0:0:20:0:=C2=A0 =C2=A0 =C2=A0 class=3D0x0c0330 rev=3D0x01 hdr=3D0x= 00 vendor=3D0x8086
device=3D0x51ed subvendor=3D0x17aa subdevice=3D0x3820
=C2=A0 =C2=A0 =C2=A0vendor=C2=A0 =C2=A0 =C2=A0=3D 'Intel Corporation= 9;
=C2=A0 =C2=A0 =C2=A0device=C2=A0 =C2=A0 =C2=A0=3D 'Alder Lake PCH USB 3= .2 xHCI Host Controller'
=C2=A0 =C2=A0 =C2=A0class=C2=A0 =C2=A0 =C2=A0 =3D serial bus
=C2=A0 =C2=A0 =C2=A0subclass=C2=A0 =C2=A0=3D USB
none2@pci0:0:20:2:=C2=A0 =C2=A0 =C2=A0 class=3D0x050000 rev=3D0x01 hdr=3D0x= 00 vendor=3D0x8086
device=3D0x51ef subvendor=3D0x17aa subdevice=3D0x381e
=C2=A0 =C2=A0 =C2=A0vendor=C2=A0 =C2=A0 =C2=A0=3D 'Intel Corporation= 9;
=C2=A0 =C2=A0 =C2=A0device=C2=A0 =C2=A0 =C2=A0=3D 'Alder Lake PCH Share= d SRAM'
=C2=A0 =C2=A0 =C2=A0class=C2=A0 =C2=A0 =C2=A0 =3D memory
=C2=A0 =C2=A0 =C2=A0subclass=C2=A0 =C2=A0=3D RAM
iwlwifi0@pci0:0:20:3:=C2=A0 =C2=A0class=3D0x028000 rev=3D0x01 hdr=3D0x00 ve= ndor=3D0x8086
device=3D0x51f0 subvendor=3D0x8086 subdevice=3D0x0074
=C2=A0 =C2=A0 =C2=A0vendor=C2=A0 =C2=A0 =C2=A0=3D 'Intel Corporation= 9;
=C2=A0 =C2=A0 =C2=A0device=C2=A0 =C2=A0 =C2=A0=3D 'Alder Lake-P PCH CNV= i WiFi'
=C2=A0 =C2=A0 =C2=A0class=C2=A0 =C2=A0 =C2=A0 =3D network
ig4iic0@pci0:0:21:0:=C2=A0 =C2=A0 class=3D0x0c8000 rev=3D0x01 hdr=3D0x00 ve= ndor=3D0x8086
device=3D0x51e8 subvendor=3D0x17aa subdevice=3D0x3812
=C2=A0 =C2=A0 =C2=A0vendor=C2=A0 =C2=A0 =C2=A0=3D 'Intel Corporation= 9;
=C2=A0 =C2=A0 =C2=A0device=C2=A0 =C2=A0 =C2=A0=3D 'Alder Lake PCH Seria= l IO I2C Controller'
=C2=A0 =C2=A0 =C2=A0class=C2=A0 =C2=A0 =C2=A0 =3D serial bus
ig4iic1@pci0:0:21:1:=C2=A0 =C2=A0 class=3D0x0c8000 rev=3D0x01 hdr=3D0x00 ve= ndor=3D0x8086
device=3D0x51e9 subvendor=3D0x17aa subdevice=3D0x3814
=C2=A0 =C2=A0 =C2=A0vendor=C2=A0 =C2=A0 =C2=A0=3D 'Intel Corporation= 9;
=C2=A0 =C2=A0 =C2=A0device=C2=A0 =C2=A0 =C2=A0=3D 'Alder Lake PCH Seria= l IO I2C Controller'
=C2=A0 =C2=A0 =C2=A0class=C2=A0 =C2=A0 =C2=A0 =3D serial bus
none3@pci0:0:22:0:=C2=A0 =C2=A0 =C2=A0 class=3D0x078000 rev=3D0x01 hdr=3D0x= 00 vendor=3D0x8086
device=3D0x51e0 subvendor=3D0x17aa subdevice=3D0x3815
=C2=A0 =C2=A0 =C2=A0vendor=C2=A0 =C2=A0 =C2=A0=3D 'Intel Corporation= 9;
=C2=A0 =C2=A0 =C2=A0device=C2=A0 =C2=A0 =C2=A0=3D 'Alder Lake PCH HECI = Controller'
=C2=A0 =C2=A0 =C2=A0class=C2=A0 =C2=A0 =C2=A0 =3D simple comms
ahci0@pci0:0:23:0:=C2=A0 =C2=A0 =C2=A0 class=3D0x010601 rev=3D0x01 hdr=3D0x= 00 vendor=3D0x8086
device=3D0x51d3 subvendor=3D0x8086 subdevice=3D0x7270
=C2=A0 =C2=A0 =C2=A0vendor=C2=A0 =C2=A0 =C2=A0=3D 'Intel Corporation= 9;
=C2=A0 =C2=A0 =C2=A0device=C2=A0 =C2=A0 =C2=A0=3D 'Alder Lake-P SATA AH= CI Controller'
=C2=A0 =C2=A0 =C2=A0class=C2=A0 =C2=A0 =C2=A0 =3D mass storage
=C2=A0 =C2=A0 =C2=A0subclass=C2=A0 =C2=A0=3D SATA
pcib2@pci0:0:29:0:=C2=A0 =C2=A0 =C2=A0 class=3D0x060400 rev=3D0x01 hdr=3D0x= 01 vendor=3D0x8086
device=3D0x51b1 subvendor=3D0x17aa subdevice=3D0x381f
=C2=A0 =C2=A0 =C2=A0vendor=C2=A0 =C2=A0 =C2=A0=3D 'Intel Corporation= 9;
=C2=A0 =C2=A0 =C2=A0device=C2=A0 =C2=A0 =C2=A0=3D 'Alder Lake PCI Expre= ss x1 Root Port'
=C2=A0 =C2=A0 =C2=A0class=C2=A0 =C2=A0 =C2=A0 =3D bridge
=C2=A0 =C2=A0 =C2=A0subclass=C2=A0 =C2=A0=3D PCI-PCI
isab0@pci0:0:31:0:=C2=A0 =C2=A0 =C2=A0 class=3D0x060100 rev=3D0x01 hdr=3D0x= 00 vendor=3D0x8086
device=3D0x5182 subvendor=3D0x17aa subdevice=3D0x382b
=C2=A0 =C2=A0 =C2=A0vendor=C2=A0 =C2=A0 =C2=A0=3D 'Intel Corporation= 9;
=C2=A0 =C2=A0 =C2=A0device=C2=A0 =C2=A0 =C2=A0=3D 'Alder Lake PCH eSPI = Controller'
=C2=A0 =C2=A0 =C2=A0class=C2=A0 =C2=A0 =C2=A0 =3D bridge
=C2=A0 =C2=A0 =C2=A0subclass=C2=A0 =C2=A0=3D PCI-ISA
hdac0@pci0:0:31:3:=C2=A0 =C2=A0 =C2=A0 class=3D0x040380 rev=3D0x01 hdr=3D0x= 00 vendor=3D0x8086
device=3D0x51c8 subvendor=3D0x17aa subdevice=3D0x3881
=C2=A0 =C2=A0 =C2=A0vendor=C2=A0 =C2=A0 =C2=A0=3D 'Intel Corporation= 9;
=C2=A0 =C2=A0 =C2=A0device=C2=A0 =C2=A0 =C2=A0=3D 'Alder Lake PCH-P Hig= h Definition Audio Controller'
=C2=A0 =C2=A0 =C2=A0class=C2=A0 =C2=A0 =C2=A0 =3D multimedia
=C2=A0 =C2=A0 =C2=A0subclass=C2=A0 =C2=A0=3D HDA
ichsmb0@pci0:0:31:4:=C2=A0 =C2=A0 class=3D0x0c0500 rev=3D0x01 hdr=3D0x00 ve= ndor=3D0x8086
device=3D0x51a3 subvendor=3D0x17aa subdevice=3D0x382f
=C2=A0 =C2=A0 =C2=A0vendor=C2=A0 =C2=A0 =C2=A0=3D 'Intel Corporation= 9;
=C2=A0 =C2=A0 =C2=A0device=C2=A0 =C2=A0 =C2=A0=3D 'Alder Lake PCH-P SMB= us Host Controller'
=C2=A0 =C2=A0 =C2=A0class=C2=A0 =C2=A0 =C2=A0 =3D serial bus
=C2=A0 =C2=A0 =C2=A0subclass=C2=A0 =C2=A0=3D SMBus
none4@pci0:0:31:5:=C2=A0 =C2=A0 =C2=A0 class=3D0x0c8000 rev=3D0x01 hdr=3D0x= 00 vendor=3D0x8086
device=3D0x51a4 subvendor=3D0x17aa subdevice=3D0x381c
=C2=A0 =C2=A0 =C2=A0vendor=C2=A0 =C2=A0 =C2=A0=3D 'Intel Corporation= 9;
=C2=A0 =C2=A0 =C2=A0device=C2=A0 =C2=A0 =C2=A0=3D 'Alder Lake-P PCH SPI= Controller'
=C2=A0 =C2=A0 =C2=A0class=C2=A0 =C2=A0 =C2=A0 =3D serial bus
nvme0@pci0:1:0:0:=C2=A0 =C2=A0 =C2=A0 =C2=A0class=3D0x010802 rev=3D0x01 hdr= =3D0x00 vendor=3D0x2646
device=3D0x5013 subvendor=3D0x2646 subdevice=3D0x5013
=C2=A0 =C2=A0 =C2=A0vendor=C2=A0 =C2=A0 =C2=A0=3D 'Kingston Technology = Company, Inc.'
=C2=A0 =C2=A0 =C2=A0device=C2=A0 =C2=A0 =C2=A0=3D 'KC3000/FURY Renegade= NVMe SSD E18'
=C2=A0 =C2=A0 =C2=A0class=C2=A0 =C2=A0 =C2=A0 =3D mass storage
=C2=A0 =C2=A0 =C2=A0subclass=C2=A0 =C2=A0=3D NVM
sdhci_pci0@pci0:2:0:0:=C2=A0 class=3D0x080501 rev=3D0x01 hdr=3D0x00 vendor= =3D0x1217
device=3D0x8621 subvendor=3D0x17aa subdevice=3D0x3874
=C2=A0 =C2=A0 =C2=A0vendor=C2=A0 =C2=A0 =C2=A0=3D 'O2 Micro, Inc.'<= br> =C2=A0 =C2=A0 =C2=A0device=C2=A0 =C2=A0 =C2=A0=3D 'SD/MMC Card Reader C= ontroller'
=C2=A0 =C2=A0 =C2=A0class=C2=A0 =C2=A0 =C2=A0 =3D base peripheral
=C2=A0 =C2=A0 =C2=A0subclass=C2=A0 =C2=A0=3D SD host controller

Id Refs Address=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Size= Name
=C2=A0 1=C2=A0 =C2=A095 0xffffffff80200000=C2=A0 1d527c0 kernel
=C2=A0 2=C2=A0 =C2=A0 1 0xffffffff81f54000=C2=A0 =C2=A0 287e8 fusefs.ko
=C2=A0 3=C2=A0 =C2=A0 1 0xffffffff82d8f000=C2=A0 =C2=A01e3228 i915kms.ko =C2=A0 4=C2=A0 =C2=A0 2 0xffffffff82f73000=C2=A0 =C2=A0 85090 drm.ko
=C2=A0 5=C2=A0 =C2=A0 1 0xffffffff82ff9000=C2=A0 =C2=A0 =C2=A022b8 iic.ko =C2=A0 6=C2=A0 =C2=A0 2 0xffffffff82ffc000=C2=A0 =C2=A0 =C2=A040e9 linuxkpi= _video.ko
=C2=A0 7=C2=A0 =C2=A0 3 0xffffffff83001000=C2=A0 =C2=A0 =C2=A07358 dmabuf.k= o
=C2=A0 8=C2=A0 =C2=A0 3 0xffffffff83009000=C2=A0 =C2=A0 =C2=A03378 lindebug= fs.ko
=C2=A0 9=C2=A0 =C2=A0 1 0xffffffff8300d000=C2=A0 =C2=A0 =C2=A0c338 ttm.ko 10=C2=A0 =C2=A0 1 0xffffffff8301a000=C2=A0 =C2=A0 =C2=A05760 cuse.ko
11=C2=A0 =C2=A0 1 0xffffffff83020000=C2=A0 =C2=A0 =C2=A03390 acpi_wmi.ko 12=C2=A0 =C2=A0 1 0xffffffff83024000=C2=A0 =C2=A0 =C2=A04250 ichsmb.ko
13=C2=A0 =C2=A0 1 0xffffffff83029000=C2=A0 =C2=A0 =C2=A02178 smbus.ko
14=C2=A0 =C2=A0 1 0xffffffff8302c000=C2=A0 =C2=A0 91260 if_iwlwifi.ko
15=C2=A0 =C2=A0 1 0xffffffff830be000=C2=A0 =C2=A0 =C2=A05f90 ig4.ko
16=C2=A0 =C2=A0 1 0xffffffff830c4000=C2=A0 =C2=A0 =C2=A04d20 ng_ubt.ko
17=C2=A0 =C2=A0 3 0xffffffff830c9000=C2=A0 =C2=A0 =C2=A0bbb8 netgraph.ko 18=C2=A0 =C2=A0 2 0xffffffff830d5000=C2=A0 =C2=A0 =C2=A0a250 ng_hci.ko
19=C2=A0 =C2=A0 2 0xffffffff830e0000=C2=A0 =C2=A0 =C2=A02670 ng_bluetooth.k= o
20=C2=A0 =C2=A0 1 0xffffffff830e3000=C2=A0 =C2=A0 =C2=A03218 iichid.ko
21=C2=A0 =C2=A0 5 0xffffffff830e7000=C2=A0 =C2=A0 =C2=A03380 hidbus.ko
22=C2=A0 =C2=A0 1 0xffffffff830eb000=C2=A0 =C2=A0 =C2=A021e8 hms.ko
23=C2=A0 =C2=A0 1 0xffffffff830ee000=C2=A0 =C2=A0 =C2=A040a8 hidmap.ko
24=C2=A0 =C2=A0 1 0xffffffff830f3000=C2=A0 =C2=A0 =C2=A03355 hmt.ko
25=C2=A0 =C2=A0 1 0xffffffff830f7000=C2=A0 =C2=A0 =C2=A022cc hconf.ko
26=C2=A0 =C2=A0 1 0xffffffff830fa000=C2=A0 =C2=A0 =C2=A02260 pflog.ko
27=C2=A0 =C2=A0 1 0xffffffff830fd000=C2=A0 =C2=A0 56540 pf.ko
28=C2=A0 =C2=A0 1 0xffffffff83154000=C2=A0 =C2=A0 =C2=A03560 fdescfs.ko


Thanks!

--Chri

I have a T16 and ran into that = issue. It may be that BIOS changes have broken things, but I found that, by= default, the F keys control volume, screen brightness, and many other thin= gs. I can use Fn+F[1-12] to perform traditional function key functions. I f= ound that bios has an option to make the traditional functions the default = which is how I am running today and have since shortly after I purchased th= e computer. One I set that BIOS option, everything worked "properly&qu= ot;. I now use Fn+F[1-12] to adjust volume and screen brightness. I hope to= get mute to work, but I need to figure out which event is set when Fn+F1 i= s pressed to write trivial devd support for it.

BTW, if you have not found it, Fn+K is screen lock. Most everything= on my T16 now works with FreeBSD CURRENT.
--
Kevin Oberman, Part time kid herder and retired Network Enginee= r
E-mail: rkobe= rman@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B31= 8AB39EF1B055683
--00000000000065c0e4061516b2b5-- From nobody Tue Apr 2 07:42:23 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4V80GJ3D3Gz5GMlF for ; Tue, 2 Apr 2024 07:42:32 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from udns.ultimatedns.net (udns.ultimatedns.net [24.113.41.81]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "ultimatedns.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4V80GH41dcz4Jvm for ; Tue, 2 Apr 2024 07:42:31 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Authentication-Results: mx1.freebsd.org; none Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.16.1/8.16.1) with ESMTP id 4327gOno010426; Tue, 2 Apr 2024 00:42:30 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=ultimatedns.net; s=mx99; t=1712043750; x=1712044350; r=y; bh=/fcQrlGEtSubj2rNrAe7V0VupRyAyufGrcg8rv4dm8I=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=GeRqvKfzfyLzjtmnmIQjaZNGTkGNTLYrrhomjLWyrr2mKaB/Nw5vdIwtnPeLyHjsG 3a+uPXo1Ug/7RlCRTLrxvT75ClZ0nXlPnWJKNK9x/fum/UrkacVDZw5dM6YG0hL2rm jSZbcKM4iNr519ShZBmSH+c67W+2EQEZ50XixViHfwdl3iaixDo3peOtnHxuIn6Mw3 BegB7dGEY0lSuMoyU3jBmQ9RgmiTo6D6gd1agNXVwUpsgs/X0LMDUd3wJVhYNKbPzE 8xxJ44HrVKZPLsbym0PL9dhqXcp9sGrdLssBznXW9vlV0mfjK94l8yu2kpCpkfRCKk Ov7oNXcXfbGEQ== List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Date: Tue, 02 Apr 2024 00:42:23 -0700 From: Chris To: Kevin Oberman Cc: freebsd-current Subject: Re: Multi cons support has disappeared (on Alder Lake) was: Alt+Fn isn't functional. Has this been removed? In-Reply-To: References: User-Agent: UDNSMS/17.0 Message-ID: X-Sender: bsd-lists@bsdforge.com Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:11404, ipnet:24.113.0.0/16, country:US] X-Rspamd-Queue-Id: 4V80GH41dcz4Jvm On 2024-04-01 22:51, Kevin Oberman wrote: > On Mon, Apr 1, 2024 at 3:05 PM Chris wrote: > >> I experience challenges running FreeBSD on my Alder Lake laptop. >> With some help on the list and Bugzilla, I was able to get Graphics >> WiFi at least working. But still wasn't as stable as running on >> more dated CPU's. As it is; I'm only able to use CURRENT. Beginning >> of last week, in hopes of getting a more stable experience. I wiped >> the partition (UFS) and unpacked the version available on the FreeBSD >> ftp servers at that time. I quickly discovered that multi-cons (Ctrl+ >> Alt+Fn || Alt+Fn) was no longer available. I posted this discovery to >> the list. But no solution was discovered. I've since attempted to use >> 2 more different newer versions. Both of them were also w/o multi-con(s) >> support. What must I do to fix, or uncover the cause of this? >> I only load the associated GPU module in rc.conf(5) (no keyboard settings). >> I'm also unable to get multi-cons booting from any of the boot media >> produced within the last week. >> >> Following are some specifics: >> >> CPU: 12th Gen Intel(R) Core(TM) i3-1215U (2496.00-MHz K8-class CPU) >> >> IdeaPad 3 17IAU7 >> >> WORKS: >> FreeBSD 15.0-CURRENT #0 main-n267640-7a4d1d1df0b2: >> Thu Jan 18 04:04:32 UTC 2024 >> >> DOESN'T WORK: >> FreeBSD 15.0-CURRENT #0 main-n269036-6baddb6b1176: >> Fri Mar 29 10:19:43 UTC 2024 >> root@releng3.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC >> amd64 >> >> FreeBSD 15.0-CURRENT #0 main-n268793-220ee18f1964: >> Thu Mar 14 02:58:39 UTC 2024 >> root@releng3.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC >> amd64 >> >> hostb0@pci0:0:0:0: class=0x060000 rev=0x04 hdr=0x00 vendor=0x8086 >> device=0x4609 subvendor=0x17aa subdevice=0x3803 >> vendor = 'Intel Corporation' >> class = bridge >> subclass = HOST-PCI >> vgapci0@pci0:0:2:0: class=0x030000 rev=0x0c hdr=0x00 vendor=0x8086 >> device=0x46b3 subvendor=0x17aa subdevice=0x3b3a >> vendor = 'Intel Corporation' >> device = 'Alder Lake-UP3 GT1 [UHD Graphics]' >> class = display >> subclass = VGA >> none0@pci0:0:4:0: class=0x118000 rev=0x04 hdr=0x00 vendor=0x8086 >> device=0x461d subvendor=0x17aa subdevice=0x380c >> vendor = 'Intel Corporation' >> device = 'Alder Lake Innovation Platform Framework Processor >> Participant' >> class = dasp >> pcib1@pci0:0:6:0: class=0x060400 rev=0x04 hdr=0x01 vendor=0x8086 >> device=0x464d subvendor=0x17aa subdevice=0x380e >> vendor = 'Intel Corporation' >> device = '12th Gen Core Processor PCI Express x4 Controller' >> class = bridge >> subclass = PCI-PCI >> none1@pci0:0:10:0: class=0x118000 rev=0x01 hdr=0x00 vendor=0x8086 >> device=0x467d subvendor=0x17aa subdevice=0x3813 >> vendor = 'Intel Corporation' >> device = 'Platform Monitoring Technology' >> class = dasp >> xhci0@pci0:0:13:0: class=0x0c0330 rev=0x04 hdr=0x00 vendor=0x8086 >> device=0x461e subvendor=0x17aa subdevice=0x3824 >> vendor = 'Intel Corporation' >> device = 'Alder Lake-P Thunderbolt 4 USB Controller' >> class = serial bus >> subclass = USB >> xhci1@pci0:0:20:0: class=0x0c0330 rev=0x01 hdr=0x00 vendor=0x8086 >> device=0x51ed subvendor=0x17aa subdevice=0x3820 >> vendor = 'Intel Corporation' >> device = 'Alder Lake PCH USB 3.2 xHCI Host Controller' >> class = serial bus >> subclass = USB >> none2@pci0:0:20:2: class=0x050000 rev=0x01 hdr=0x00 vendor=0x8086 >> device=0x51ef subvendor=0x17aa subdevice=0x381e >> vendor = 'Intel Corporation' >> device = 'Alder Lake PCH Shared SRAM' >> class = memory >> subclass = RAM >> iwlwifi0@pci0:0:20:3: class=0x028000 rev=0x01 hdr=0x00 vendor=0x8086 >> device=0x51f0 subvendor=0x8086 subdevice=0x0074 >> vendor = 'Intel Corporation' >> device = 'Alder Lake-P PCH CNVi WiFi' >> class = network >> ig4iic0@pci0:0:21:0: class=0x0c8000 rev=0x01 hdr=0x00 vendor=0x8086 >> device=0x51e8 subvendor=0x17aa subdevice=0x3812 >> vendor = 'Intel Corporation' >> device = 'Alder Lake PCH Serial IO I2C Controller' >> class = serial bus >> ig4iic1@pci0:0:21:1: class=0x0c8000 rev=0x01 hdr=0x00 vendor=0x8086 >> device=0x51e9 subvendor=0x17aa subdevice=0x3814 >> vendor = 'Intel Corporation' >> device = 'Alder Lake PCH Serial IO I2C Controller' >> class = serial bus >> none3@pci0:0:22:0: class=0x078000 rev=0x01 hdr=0x00 vendor=0x8086 >> device=0x51e0 subvendor=0x17aa subdevice=0x3815 >> vendor = 'Intel Corporation' >> device = 'Alder Lake PCH HECI Controller' >> class = simple comms >> ahci0@pci0:0:23:0: class=0x010601 rev=0x01 hdr=0x00 vendor=0x8086 >> device=0x51d3 subvendor=0x8086 subdevice=0x7270 >> vendor = 'Intel Corporation' >> device = 'Alder Lake-P SATA AHCI Controller' >> class = mass storage >> subclass = SATA >> pcib2@pci0:0:29:0: class=0x060400 rev=0x01 hdr=0x01 vendor=0x8086 >> device=0x51b1 subvendor=0x17aa subdevice=0x381f >> vendor = 'Intel Corporation' >> device = 'Alder Lake PCI Express x1 Root Port' >> class = bridge >> subclass = PCI-PCI >> isab0@pci0:0:31:0: class=0x060100 rev=0x01 hdr=0x00 vendor=0x8086 >> device=0x5182 subvendor=0x17aa subdevice=0x382b >> vendor = 'Intel Corporation' >> device = 'Alder Lake PCH eSPI Controller' >> class = bridge >> subclass = PCI-ISA >> hdac0@pci0:0:31:3: class=0x040380 rev=0x01 hdr=0x00 vendor=0x8086 >> device=0x51c8 subvendor=0x17aa subdevice=0x3881 >> vendor = 'Intel Corporation' >> device = 'Alder Lake PCH-P High Definition Audio Controller' >> class = multimedia >> subclass = HDA >> ichsmb0@pci0:0:31:4: class=0x0c0500 rev=0x01 hdr=0x00 vendor=0x8086 >> device=0x51a3 subvendor=0x17aa subdevice=0x382f >> vendor = 'Intel Corporation' >> device = 'Alder Lake PCH-P SMBus Host Controller' >> class = serial bus >> subclass = SMBus >> none4@pci0:0:31:5: class=0x0c8000 rev=0x01 hdr=0x00 vendor=0x8086 >> device=0x51a4 subvendor=0x17aa subdevice=0x381c >> vendor = 'Intel Corporation' >> device = 'Alder Lake-P PCH SPI Controller' >> class = serial bus >> nvme0@pci0:1:0:0: class=0x010802 rev=0x01 hdr=0x00 vendor=0x2646 >> device=0x5013 subvendor=0x2646 subdevice=0x5013 >> vendor = 'Kingston Technology Company, Inc.' >> device = 'KC3000/FURY Renegade NVMe SSD E18' >> class = mass storage >> subclass = NVM >> sdhci_pci0@pci0:2:0:0: class=0x080501 rev=0x01 hdr=0x00 vendor=0x1217 >> device=0x8621 subvendor=0x17aa subdevice=0x3874 >> vendor = 'O2 Micro, Inc.' >> device = 'SD/MMC Card Reader Controller' >> class = base peripheral >> subclass = SD host controller >> >> Id Refs Address Size Name >> 1 95 0xffffffff80200000 1d527c0 kernel >> 2 1 0xffffffff81f54000 287e8 fusefs.ko >> 3 1 0xffffffff82d8f000 1e3228 i915kms.ko >> 4 2 0xffffffff82f73000 85090 drm.ko >> 5 1 0xffffffff82ff9000 22b8 iic.ko >> 6 2 0xffffffff82ffc000 40e9 linuxkpi_video.ko >> 7 3 0xffffffff83001000 7358 dmabuf.ko >> 8 3 0xffffffff83009000 3378 lindebugfs.ko >> 9 1 0xffffffff8300d000 c338 ttm.ko >> 10 1 0xffffffff8301a000 5760 cuse.ko >> 11 1 0xffffffff83020000 3390 acpi_wmi.ko >> 12 1 0xffffffff83024000 4250 ichsmb.ko >> 13 1 0xffffffff83029000 2178 smbus.ko >> 14 1 0xffffffff8302c000 91260 if_iwlwifi.ko >> 15 1 0xffffffff830be000 5f90 ig4.ko >> 16 1 0xffffffff830c4000 4d20 ng_ubt.ko >> 17 3 0xffffffff830c9000 bbb8 netgraph.ko >> 18 2 0xffffffff830d5000 a250 ng_hci.ko >> 19 2 0xffffffff830e0000 2670 ng_bluetooth.ko >> 20 1 0xffffffff830e3000 3218 iichid.ko >> 21 5 0xffffffff830e7000 3380 hidbus.ko >> 22 1 0xffffffff830eb000 21e8 hms.ko >> 23 1 0xffffffff830ee000 40a8 hidmap.ko >> 24 1 0xffffffff830f3000 3355 hmt.ko >> 25 1 0xffffffff830f7000 22cc hconf.ko >> 26 1 0xffffffff830fa000 2260 pflog.ko >> 27 1 0xffffffff830fd000 56540 pf.ko >> 28 1 0xffffffff83154000 3560 fdescfs.ko >> >> >> Thanks! >> >> --Chri > > > I have a T16 and ran into that issue. It may be that BIOS changes have > broken things, but I found that, by default, the F keys control volume, > screen brightness, and many other things. I can use Fn+F[1-12] to perform > traditional function key functions. I found that bios has an option to make > the traditional functions the default which is how I am running today and > have since shortly after I purchased the computer. One I set that BIOS > option, everything worked "properly". I now use Fn+F[1-12] to adjust volume > and screen brightness. I hope to get mute to work, but I need to figure out > which event is set when Fn+F1 is pressed to write trivial devd support for > it. Well, I can't explain it. I set everything up in the BIOS to work "traditionally" and everything worked fine up until the upgrade. Where everything went "south" in the Fn department. But since you mentioned it. I thought I'd review the settings and sure enough, the Function key settings had changed. I have no explanation. I haven't been to the BIOS settings since initial setup. But only that setting was changed. I can't thank you enough for mentioning this, Kevin. I *really* appreciate your taking the time to reply! > > BTW, if you have not found it, Fn+K is screen lock. Most everything on my > T16 now works with FreeBSD CURRENT. Thanks. That was the first thing I looked for when I got it. I can't live w/o the scrollock. Took me a bit. But I found it too. :) Thanks again! :) From nobody Tue Apr 2 10:33:20 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4V843j1QdMz5GGQ7 for ; Tue, 2 Apr 2024 10:33:37 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from mx.catwhisker.org (mx.catwhisker.org [107.204.234.170]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4V843h41g4z4gKF for ; Tue, 2 Apr 2024 10:33:36 +0000 (UTC) (envelope-from david@catwhisker.org) Authentication-Results: mx1.freebsd.org; none Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.18.1/8.18.1) with ESMTP id 432AXKZG032450; Tue, 2 Apr 2024 10:33:20 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.18.1/8.18.1/Submit) id 432AXK9u032449; Tue, 2 Apr 2024 03:33:20 -0700 (PDT) (envelope-from david) Date: Tue, 2 Apr 2024 03:33:20 -0700 From: David Wolfskill To: Kevin Oberman Cc: Chris , freebsd-current Subject: Re: Multi cons support has disappeared (on Alder Lake) was: Alt+Fn isn't functional. Has this been removed? Message-ID: Reply-To: current@freebsd.org Mail-Followup-To: current@freebsd.org, Kevin Oberman , Chris , freebsd-current References: List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="4Z1gSK+YcJBIzX4z" Content-Disposition: inline In-Reply-To: X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:7018, ipnet:107.192.0.0/12, country:US] X-Rspamd-Queue-Id: 4V843h41g4z4gKF --4Z1gSK+YcJBIzX4z Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Apr 01, 2024 at 10:51:10PM -0700, Kevin Oberman wrote: > .... > I have a T16 and ran into that issue. It may be that BIOS changes have > broken things, but I found that, by default, the F keys control volume, > screen brightness, and many other things. I can use Fn+F[1-12] to perform > traditional function key functions. I found that bios has an option to ma= ke > the traditional functions the default which is how I am running today and > have since shortly after I purchased the computer. One I set that BIOS > option, everything worked "properly". I now use Fn+F[1-12] to adjust volu= me > and screen brightness. I hope to get mute to work, but I need to figure o= ut > which event is set when Fn+F1 is pressed to write trivial devd support for > it. Another approach (for making use of quasi-random keys scattered across a keyboard) is to utilize x11/xbindkeys (at least, within an X11 environment). > .... Peace, david --=20 David H. Wolfskill david@catwhisker.org Alexey Navalny was a courageous man; Putin has made him a martyr. See https://www.catwhisker.org/~david/publickey.gpg for my public key. --4Z1gSK+YcJBIzX4z Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iNUEARYKAH0WIQSTLzOSbomIK53fjFliipiWhXYx5QUCZgve8F8UgAAAAAAuAChp c3N1ZXItZnByQG5vdGF0aW9ucy5vcGVucGdwLmZpZnRoaG9yc2VtYW4ubmV0OTMy RjMzOTI2RTg5ODgyQjlEREY4QzU5NjI4QTk4OTY4NTc2MzFFNQAKCRBiipiWhXYx 5Wp3AQC9tjc8rG6XFsR9rrFnid0Zzw1nhkfqxzZVvxpmOkRASAD/YrbeHvRtQw+H +xvGMtTbCbS6Nj7XclBt0WFMKt5KPwA= =Ssmf -----END PGP SIGNATURE----- --4Z1gSK+YcJBIzX4z-- From nobody Tue Apr 2 11:32:17 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4V85Mw1HnYz5GNNW for ; Tue, 2 Apr 2024 11:32:44 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from www121.sakura.ne.jp (www121.sakura.ne.jp [153.125.133.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4V85Mv3Qfcz4ljr for ; Tue, 2 Apr 2024 11:32:42 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Authentication-Results: mx1.freebsd.org; none Received: from kalamity.joker.local (123-1-21-232.area1b.commufa.jp [123.1.21.232]) (authenticated bits=0) by www121.sakura.ne.jp (8.17.1/8.17.1/[SAKURA-WEB]/20201212) with ESMTPA id 432BWHQQ052978; Tue, 2 Apr 2024 20:32:17 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) Date: Tue, 2 Apr 2024 20:32:17 +0900 From: Tomoaki AOKI To: Chris Cc: Kevin Oberman , freebsd-current Subject: Re: Multi cons support has disappeared (on Alder Lake) was: Alt+Fn isn't functional. Has this been removed? Message-Id: <20240402203217.713707a1cdef4c08905ca4e0@dec.sakura.ne.jp> In-Reply-To: References: Organization: Junchoon corps X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd14.0) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:7684, ipnet:153.125.128.0/18, country:JP] X-Rspamd-Queue-Id: 4V85Mv3Qfcz4ljr On Tue, 02 Apr 2024 00:42:23 -0700 Chris wrote: > On 2024-04-01 22:51, Kevin Oberman wrote: > > On Mon, Apr 1, 2024 at 3:05 PM Chris wrote: > > > >> I experience challenges running FreeBSD on my Alder Lake laptop. > >> With some help on the list and Bugzilla, I was able to get Graphics > >> WiFi at least working. But still wasn't as stable as running on > >> more dated CPU's. As it is; I'm only able to use CURRENT. Beginning > >> of last week, in hopes of getting a more stable experience. I wiped > >> the partition (UFS) and unpacked the version available on the FreeBSD > >> ftp servers at that time. I quickly discovered that multi-cons (Ctrl+ > >> Alt+Fn || Alt+Fn) was no longer available. I posted this discovery to > >> the list. But no solution was discovered. I've since attempted to use > >> 2 more different newer versions. Both of them were also w/o multi-con(s) > >> support. What must I do to fix, or uncover the cause of this? > >> I only load the associated GPU module in rc.conf(5) (no keyboard settings). > >> I'm also unable to get multi-cons booting from any of the boot media > >> produced within the last week. > >> > >> Following are some specifics: > >> > >> CPU: 12th Gen Intel(R) Core(TM) i3-1215U (2496.00-MHz K8-class CPU) > >> > >> IdeaPad 3 17IAU7 > >> > >> WORKS: > >> FreeBSD 15.0-CURRENT #0 main-n267640-7a4d1d1df0b2: > >> Thu Jan 18 04:04:32 UTC 2024 > >> > >> DOESN'T WORK: > >> FreeBSD 15.0-CURRENT #0 main-n269036-6baddb6b1176: > >> Fri Mar 29 10:19:43 UTC 2024 > >> root@releng3.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC > >> amd64 > >> > >> FreeBSD 15.0-CURRENT #0 main-n268793-220ee18f1964: > >> Thu Mar 14 02:58:39 UTC 2024 > >> root@releng3.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC > >> amd64 > >> > >> hostb0@pci0:0:0:0: class=0x060000 rev=0x04 hdr=0x00 vendor=0x8086 > >> device=0x4609 subvendor=0x17aa subdevice=0x3803 > >> vendor = 'Intel Corporation' > >> class = bridge > >> subclass = HOST-PCI > >> vgapci0@pci0:0:2:0: class=0x030000 rev=0x0c hdr=0x00 vendor=0x8086 > >> device=0x46b3 subvendor=0x17aa subdevice=0x3b3a > >> vendor = 'Intel Corporation' > >> device = 'Alder Lake-UP3 GT1 [UHD Graphics]' > >> class = display > >> subclass = VGA > >> none0@pci0:0:4:0: class=0x118000 rev=0x04 hdr=0x00 vendor=0x8086 > >> device=0x461d subvendor=0x17aa subdevice=0x380c > >> vendor = 'Intel Corporation' > >> device = 'Alder Lake Innovation Platform Framework Processor > >> Participant' > >> class = dasp > >> pcib1@pci0:0:6:0: class=0x060400 rev=0x04 hdr=0x01 vendor=0x8086 > >> device=0x464d subvendor=0x17aa subdevice=0x380e > >> vendor = 'Intel Corporation' > >> device = '12th Gen Core Processor PCI Express x4 Controller' > >> class = bridge > >> subclass = PCI-PCI > >> none1@pci0:0:10:0: class=0x118000 rev=0x01 hdr=0x00 vendor=0x8086 > >> device=0x467d subvendor=0x17aa subdevice=0x3813 > >> vendor = 'Intel Corporation' > >> device = 'Platform Monitoring Technology' > >> class = dasp > >> xhci0@pci0:0:13:0: class=0x0c0330 rev=0x04 hdr=0x00 vendor=0x8086 > >> device=0x461e subvendor=0x17aa subdevice=0x3824 > >> vendor = 'Intel Corporation' > >> device = 'Alder Lake-P Thunderbolt 4 USB Controller' > >> class = serial bus > >> subclass = USB > >> xhci1@pci0:0:20:0: class=0x0c0330 rev=0x01 hdr=0x00 vendor=0x8086 > >> device=0x51ed subvendor=0x17aa subdevice=0x3820 > >> vendor = 'Intel Corporation' > >> device = 'Alder Lake PCH USB 3.2 xHCI Host Controller' > >> class = serial bus > >> subclass = USB > >> none2@pci0:0:20:2: class=0x050000 rev=0x01 hdr=0x00 vendor=0x8086 > >> device=0x51ef subvendor=0x17aa subdevice=0x381e > >> vendor = 'Intel Corporation' > >> device = 'Alder Lake PCH Shared SRAM' > >> class = memory > >> subclass = RAM > >> iwlwifi0@pci0:0:20:3: class=0x028000 rev=0x01 hdr=0x00 vendor=0x8086 > >> device=0x51f0 subvendor=0x8086 subdevice=0x0074 > >> vendor = 'Intel Corporation' > >> device = 'Alder Lake-P PCH CNVi WiFi' > >> class = network > >> ig4iic0@pci0:0:21:0: class=0x0c8000 rev=0x01 hdr=0x00 vendor=0x8086 > >> device=0x51e8 subvendor=0x17aa subdevice=0x3812 > >> vendor = 'Intel Corporation' > >> device = 'Alder Lake PCH Serial IO I2C Controller' > >> class = serial bus > >> ig4iic1@pci0:0:21:1: class=0x0c8000 rev=0x01 hdr=0x00 vendor=0x8086 > >> device=0x51e9 subvendor=0x17aa subdevice=0x3814 > >> vendor = 'Intel Corporation' > >> device = 'Alder Lake PCH Serial IO I2C Controller' > >> class = serial bus > >> none3@pci0:0:22:0: class=0x078000 rev=0x01 hdr=0x00 vendor=0x8086 > >> device=0x51e0 subvendor=0x17aa subdevice=0x3815 > >> vendor = 'Intel Corporation' > >> device = 'Alder Lake PCH HECI Controller' > >> class = simple comms > >> ahci0@pci0:0:23:0: class=0x010601 rev=0x01 hdr=0x00 vendor=0x8086 > >> device=0x51d3 subvendor=0x8086 subdevice=0x7270 > >> vendor = 'Intel Corporation' > >> device = 'Alder Lake-P SATA AHCI Controller' > >> class = mass storage > >> subclass = SATA > >> pcib2@pci0:0:29:0: class=0x060400 rev=0x01 hdr=0x01 vendor=0x8086 > >> device=0x51b1 subvendor=0x17aa subdevice=0x381f > >> vendor = 'Intel Corporation' > >> device = 'Alder Lake PCI Express x1 Root Port' > >> class = bridge > >> subclass = PCI-PCI > >> isab0@pci0:0:31:0: class=0x060100 rev=0x01 hdr=0x00 vendor=0x8086 > >> device=0x5182 subvendor=0x17aa subdevice=0x382b > >> vendor = 'Intel Corporation' > >> device = 'Alder Lake PCH eSPI Controller' > >> class = bridge > >> subclass = PCI-ISA > >> hdac0@pci0:0:31:3: class=0x040380 rev=0x01 hdr=0x00 vendor=0x8086 > >> device=0x51c8 subvendor=0x17aa subdevice=0x3881 > >> vendor = 'Intel Corporation' > >> device = 'Alder Lake PCH-P High Definition Audio Controller' > >> class = multimedia > >> subclass = HDA > >> ichsmb0@pci0:0:31:4: class=0x0c0500 rev=0x01 hdr=0x00 vendor=0x8086 > >> device=0x51a3 subvendor=0x17aa subdevice=0x382f > >> vendor = 'Intel Corporation' > >> device = 'Alder Lake PCH-P SMBus Host Controller' > >> class = serial bus > >> subclass = SMBus > >> none4@pci0:0:31:5: class=0x0c8000 rev=0x01 hdr=0x00 vendor=0x8086 > >> device=0x51a4 subvendor=0x17aa subdevice=0x381c > >> vendor = 'Intel Corporation' > >> device = 'Alder Lake-P PCH SPI Controller' > >> class = serial bus > >> nvme0@pci0:1:0:0: class=0x010802 rev=0x01 hdr=0x00 vendor=0x2646 > >> device=0x5013 subvendor=0x2646 subdevice=0x5013 > >> vendor = 'Kingston Technology Company, Inc.' > >> device = 'KC3000/FURY Renegade NVMe SSD E18' > >> class = mass storage > >> subclass = NVM > >> sdhci_pci0@pci0:2:0:0: class=0x080501 rev=0x01 hdr=0x00 vendor=0x1217 > >> device=0x8621 subvendor=0x17aa subdevice=0x3874 > >> vendor = 'O2 Micro, Inc.' > >> device = 'SD/MMC Card Reader Controller' > >> class = base peripheral > >> subclass = SD host controller > >> > >> Id Refs Address Size Name > >> 1 95 0xffffffff80200000 1d527c0 kernel > >> 2 1 0xffffffff81f54000 287e8 fusefs.ko > >> 3 1 0xffffffff82d8f000 1e3228 i915kms.ko > >> 4 2 0xffffffff82f73000 85090 drm.ko > >> 5 1 0xffffffff82ff9000 22b8 iic.ko > >> 6 2 0xffffffff82ffc000 40e9 linuxkpi_video.ko > >> 7 3 0xffffffff83001000 7358 dmabuf.ko > >> 8 3 0xffffffff83009000 3378 lindebugfs.ko > >> 9 1 0xffffffff8300d000 c338 ttm.ko > >> 10 1 0xffffffff8301a000 5760 cuse.ko > >> 11 1 0xffffffff83020000 3390 acpi_wmi.ko > >> 12 1 0xffffffff83024000 4250 ichsmb.ko > >> 13 1 0xffffffff83029000 2178 smbus.ko > >> 14 1 0xffffffff8302c000 91260 if_iwlwifi.ko > >> 15 1 0xffffffff830be000 5f90 ig4.ko > >> 16 1 0xffffffff830c4000 4d20 ng_ubt.ko > >> 17 3 0xffffffff830c9000 bbb8 netgraph.ko > >> 18 2 0xffffffff830d5000 a250 ng_hci.ko > >> 19 2 0xffffffff830e0000 2670 ng_bluetooth.ko > >> 20 1 0xffffffff830e3000 3218 iichid.ko > >> 21 5 0xffffffff830e7000 3380 hidbus.ko > >> 22 1 0xffffffff830eb000 21e8 hms.ko > >> 23 1 0xffffffff830ee000 40a8 hidmap.ko > >> 24 1 0xffffffff830f3000 3355 hmt.ko > >> 25 1 0xffffffff830f7000 22cc hconf.ko > >> 26 1 0xffffffff830fa000 2260 pflog.ko > >> 27 1 0xffffffff830fd000 56540 pf.ko > >> 28 1 0xffffffff83154000 3560 fdescfs.ko > >> > >> > >> Thanks! > >> > >> --Chri > > > > > > I have a T16 and ran into that issue. It may be that BIOS changes have > > broken things, but I found that, by default, the F keys control volume, > > screen brightness, and many other things. I can use Fn+F[1-12] to perform > > traditional function key functions. I found that bios has an option to make > > the traditional functions the default which is how I am running today and > > have since shortly after I purchased the computer. One I set that BIOS > > option, everything worked "properly". I now use Fn+F[1-12] to adjust volume > > and screen brightness. I hope to get mute to work, but I need to figure out > > which event is set when Fn+F1 is pressed to write trivial devd support for > > it. > Well, I can't explain it. I set everything up in the BIOS to work > "traditionally" > and everything worked fine up until the upgrade. Where everything went > "south" > in the Fn department. But since you mentioned it. I thought I'd review the > settings > and sure enough, the Function key settings had changed. I have no > explanation. I > haven't been to the BIOS settings since initial setup. But only that setting > was > changed. I can't thank you enough for mentioning this, Kevin. I *really* > appreciate > your taking the time to reply! So I was correct. ;-) > > BTW, if you have not found it, Fn+K is screen lock. Most everything on my > > T16 now works with FreeBSD CURRENT. > Thanks. That was the first thing I looked for when I got it. I can't live w/o > the scrollock. Took me a bit. But I found it too. :) Another datapoint. Even on Lenovo ThinkPad series, the alternative ScrLk is different. On my ThinkPad P52, Non-existent ScrLk is mapped to Fn+B, not Fn+K. You should better reading provided PDF manual closely before ordering next time. Lenovo provides it relatively early for ThinkPads. > > Thanks again! :) > -- Tomoaki AOKI From nobody Tue Apr 2 15:53:15 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4V8C8m450Xz5Gt50 for ; Tue, 2 Apr 2024 15:53:28 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from udns.ultimatedns.net (udns.ultimatedns.net [24.113.41.81]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "ultimatedns.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4V8C8m04NHz4RVt for ; Tue, 2 Apr 2024 15:53:27 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Authentication-Results: mx1.freebsd.org; none Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.16.1/8.16.1) with ESMTP id 432FrFhh082854; Tue, 2 Apr 2024 08:53:22 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=ultimatedns.net; s=mx99; t=1712073202; x=1712073802; r=y; bh=GlQy4Z7WQH2DUmmCuruexUvAJdHmaD9k64uoechxTys=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=snmcCkNnlcM/vyRdyq1h5RDkcU2eDQSP1GsEYC+A7fbkFqGRWFK1Mg3zJ7bHpMk7S NXYhJZ+vcIUIKw61NR62FKCTxiZh3dlnPyG+AMhBJTZRGic4SGUQDV8cdQYFQrgCkw MC/tXdyg0HCqnyPWcJOcGoBkmyfmW47lRys4VfXCHbMh4YT2G/apEnjIyzFPoyDUnT Yq67gvhKXsp5/OYd5Sdq9EGOp0eRGEWHBe4oR42HZ6rL+U+K1dkANd1zeG+JmsSJAd GD9FH+QZDk74X2U6W50quelz8Fr/nm7o43H+vSxm42JNoUqDJRG8sbHMUcSnCLA7eX nDgrbTThBgkOw== List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Date: Tue, 02 Apr 2024 08:53:15 -0700 From: Chris To: Tomoaki AOKI Cc: Kevin Oberman , freebsd-current Subject: Re: Multi cons support has disappeared (on Alder Lake) was: Alt+Fn isn't functional. Has this been removed? In-Reply-To: <20240402203217.713707a1cdef4c08905ca4e0@dec.sakura.ne.jp> References: <20240402203217.713707a1cdef4c08905ca4e0@dec.sakura.ne.jp> User-Agent: UDNSMS/17.0 Message-ID: X-Sender: bsd-lists@bsdforge.com Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:11404, ipnet:24.113.0.0/16, country:US] X-Rspamd-Queue-Id: 4V8C8m04NHz4RVt On 2024-04-02 04:32, Tomoaki AOKI wrote: > On Tue, 02 Apr 2024 00:42:23 -0700 > Chris wrote: > >> On 2024-04-01 22:51, Kevin Oberman wrote: >> > On Mon, Apr 1, 2024 at 3:05 PM Chris wrote: >> > >> >> I experience challenges running FreeBSD on my Alder Lake laptop. >> >> With some help on the list and Bugzilla, I was able to get Graphics >> >> WiFi at least working. But still wasn't as stable as running on >> >> more dated CPU's. As it is; I'm only able to use CURRENT. Beginning >> >> of last week, in hopes of getting a more stable experience. I wiped >> >> the partition (UFS) and unpacked the version available on the FreeBSD >> >> ftp servers at that time. I quickly discovered that multi-cons (Ctrl+ >> >> Alt+Fn || Alt+Fn) was no longer available. I posted this discovery to >> >> the list. But no solution was discovered. I've since attempted to use >> >> 2 more different newer versions. Both of them were also w/o multi-con(s) >> >> support. What must I do to fix, or uncover the cause of this? >> >> I only load the associated GPU module in rc.conf(5) (no keyboard settings). >> >> I'm also unable to get multi-cons booting from any of the boot media >> >> produced within the last week. >> >> >> >> Following are some specifics: >> >> >> >> CPU: 12th Gen Intel(R) Core(TM) i3-1215U (2496.00-MHz K8-class CPU) >> >> >> >> IdeaPad 3 17IAU7 >> >> >> >> WORKS: >> >> FreeBSD 15.0-CURRENT #0 main-n267640-7a4d1d1df0b2: >> >> Thu Jan 18 04:04:32 UTC 2024 >> >> >> >> DOESN'T WORK: >> >> FreeBSD 15.0-CURRENT #0 main-n269036-6baddb6b1176: >> >> Fri Mar 29 10:19:43 UTC 2024 >> >> root@releng3.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC >> >> amd64 >> >> >> >> FreeBSD 15.0-CURRENT #0 main-n268793-220ee18f1964: >> >> Thu Mar 14 02:58:39 UTC 2024 >> >> root@releng3.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC >> >> amd64 >> >> >> >> hostb0@pci0:0:0:0: class=0x060000 rev=0x04 hdr=0x00 vendor=0x8086 >> >> device=0x4609 subvendor=0x17aa subdevice=0x3803 >> >> vendor = 'Intel Corporation' >> >> class = bridge >> >> subclass = HOST-PCI >> >> vgapci0@pci0:0:2:0: class=0x030000 rev=0x0c hdr=0x00 vendor=0x8086 >> >> device=0x46b3 subvendor=0x17aa subdevice=0x3b3a >> >> vendor = 'Intel Corporation' >> >> device = 'Alder Lake-UP3 GT1 [UHD Graphics]' >> >> class = display >> >> subclass = VGA >> >> none0@pci0:0:4:0: class=0x118000 rev=0x04 hdr=0x00 vendor=0x8086 >> >> device=0x461d subvendor=0x17aa subdevice=0x380c >> >> vendor = 'Intel Corporation' >> >> device = 'Alder Lake Innovation Platform Framework Processor >> >> Participant' >> >> class = dasp >> >> pcib1@pci0:0:6:0: class=0x060400 rev=0x04 hdr=0x01 vendor=0x8086 >> >> device=0x464d subvendor=0x17aa subdevice=0x380e >> >> vendor = 'Intel Corporation' >> >> device = '12th Gen Core Processor PCI Express x4 Controller' >> >> class = bridge >> >> subclass = PCI-PCI >> >> none1@pci0:0:10:0: class=0x118000 rev=0x01 hdr=0x00 vendor=0x8086 >> >> device=0x467d subvendor=0x17aa subdevice=0x3813 >> >> vendor = 'Intel Corporation' >> >> device = 'Platform Monitoring Technology' >> >> class = dasp >> >> xhci0@pci0:0:13:0: class=0x0c0330 rev=0x04 hdr=0x00 vendor=0x8086 >> >> device=0x461e subvendor=0x17aa subdevice=0x3824 >> >> vendor = 'Intel Corporation' >> >> device = 'Alder Lake-P Thunderbolt 4 USB Controller' >> >> class = serial bus >> >> subclass = USB >> >> xhci1@pci0:0:20:0: class=0x0c0330 rev=0x01 hdr=0x00 vendor=0x8086 >> >> device=0x51ed subvendor=0x17aa subdevice=0x3820 >> >> vendor = 'Intel Corporation' >> >> device = 'Alder Lake PCH USB 3.2 xHCI Host Controller' >> >> class = serial bus >> >> subclass = USB >> >> none2@pci0:0:20:2: class=0x050000 rev=0x01 hdr=0x00 vendor=0x8086 >> >> device=0x51ef subvendor=0x17aa subdevice=0x381e >> >> vendor = 'Intel Corporation' >> >> device = 'Alder Lake PCH Shared SRAM' >> >> class = memory >> >> subclass = RAM >> >> iwlwifi0@pci0:0:20:3: class=0x028000 rev=0x01 hdr=0x00 vendor=0x8086 >> >> device=0x51f0 subvendor=0x8086 subdevice=0x0074 >> >> vendor = 'Intel Corporation' >> >> device = 'Alder Lake-P PCH CNVi WiFi' >> >> class = network >> >> ig4iic0@pci0:0:21:0: class=0x0c8000 rev=0x01 hdr=0x00 vendor=0x8086 >> >> device=0x51e8 subvendor=0x17aa subdevice=0x3812 >> >> vendor = 'Intel Corporation' >> >> device = 'Alder Lake PCH Serial IO I2C Controller' >> >> class = serial bus >> >> ig4iic1@pci0:0:21:1: class=0x0c8000 rev=0x01 hdr=0x00 vendor=0x8086 >> >> device=0x51e9 subvendor=0x17aa subdevice=0x3814 >> >> vendor = 'Intel Corporation' >> >> device = 'Alder Lake PCH Serial IO I2C Controller' >> >> class = serial bus >> >> none3@pci0:0:22:0: class=0x078000 rev=0x01 hdr=0x00 vendor=0x8086 >> >> device=0x51e0 subvendor=0x17aa subdevice=0x3815 >> >> vendor = 'Intel Corporation' >> >> device = 'Alder Lake PCH HECI Controller' >> >> class = simple comms >> >> ahci0@pci0:0:23:0: class=0x010601 rev=0x01 hdr=0x00 vendor=0x8086 >> >> device=0x51d3 subvendor=0x8086 subdevice=0x7270 >> >> vendor = 'Intel Corporation' >> >> device = 'Alder Lake-P SATA AHCI Controller' >> >> class = mass storage >> >> subclass = SATA >> >> pcib2@pci0:0:29:0: class=0x060400 rev=0x01 hdr=0x01 vendor=0x8086 >> >> device=0x51b1 subvendor=0x17aa subdevice=0x381f >> >> vendor = 'Intel Corporation' >> >> device = 'Alder Lake PCI Express x1 Root Port' >> >> class = bridge >> >> subclass = PCI-PCI >> >> isab0@pci0:0:31:0: class=0x060100 rev=0x01 hdr=0x00 vendor=0x8086 >> >> device=0x5182 subvendor=0x17aa subdevice=0x382b >> >> vendor = 'Intel Corporation' >> >> device = 'Alder Lake PCH eSPI Controller' >> >> class = bridge >> >> subclass = PCI-ISA >> >> hdac0@pci0:0:31:3: class=0x040380 rev=0x01 hdr=0x00 vendor=0x8086 >> >> device=0x51c8 subvendor=0x17aa subdevice=0x3881 >> >> vendor = 'Intel Corporation' >> >> device = 'Alder Lake PCH-P High Definition Audio Controller' >> >> class = multimedia >> >> subclass = HDA >> >> ichsmb0@pci0:0:31:4: class=0x0c0500 rev=0x01 hdr=0x00 vendor=0x8086 >> >> device=0x51a3 subvendor=0x17aa subdevice=0x382f >> >> vendor = 'Intel Corporation' >> >> device = 'Alder Lake PCH-P SMBus Host Controller' >> >> class = serial bus >> >> subclass = SMBus >> >> none4@pci0:0:31:5: class=0x0c8000 rev=0x01 hdr=0x00 vendor=0x8086 >> >> device=0x51a4 subvendor=0x17aa subdevice=0x381c >> >> vendor = 'Intel Corporation' >> >> device = 'Alder Lake-P PCH SPI Controller' >> >> class = serial bus >> >> nvme0@pci0:1:0:0: class=0x010802 rev=0x01 hdr=0x00 vendor=0x2646 >> >> device=0x5013 subvendor=0x2646 subdevice=0x5013 >> >> vendor = 'Kingston Technology Company, Inc.' >> >> device = 'KC3000/FURY Renegade NVMe SSD E18' >> >> class = mass storage >> >> subclass = NVM >> >> sdhci_pci0@pci0:2:0:0: class=0x080501 rev=0x01 hdr=0x00 vendor=0x1217 >> >> device=0x8621 subvendor=0x17aa subdevice=0x3874 >> >> vendor = 'O2 Micro, Inc.' >> >> device = 'SD/MMC Card Reader Controller' >> >> class = base peripheral >> >> subclass = SD host controller >> >> >> >> Id Refs Address Size Name >> >> 1 95 0xffffffff80200000 1d527c0 kernel >> >> 2 1 0xffffffff81f54000 287e8 fusefs.ko >> >> 3 1 0xffffffff82d8f000 1e3228 i915kms.ko >> >> 4 2 0xffffffff82f73000 85090 drm.ko >> >> 5 1 0xffffffff82ff9000 22b8 iic.ko >> >> 6 2 0xffffffff82ffc000 40e9 linuxkpi_video.ko >> >> 7 3 0xffffffff83001000 7358 dmabuf.ko >> >> 8 3 0xffffffff83009000 3378 lindebugfs.ko >> >> 9 1 0xffffffff8300d000 c338 ttm.ko >> >> 10 1 0xffffffff8301a000 5760 cuse.ko >> >> 11 1 0xffffffff83020000 3390 acpi_wmi.ko >> >> 12 1 0xffffffff83024000 4250 ichsmb.ko >> >> 13 1 0xffffffff83029000 2178 smbus.ko >> >> 14 1 0xffffffff8302c000 91260 if_iwlwifi.ko >> >> 15 1 0xffffffff830be000 5f90 ig4.ko >> >> 16 1 0xffffffff830c4000 4d20 ng_ubt.ko >> >> 17 3 0xffffffff830c9000 bbb8 netgraph.ko >> >> 18 2 0xffffffff830d5000 a250 ng_hci.ko >> >> 19 2 0xffffffff830e0000 2670 ng_bluetooth.ko >> >> 20 1 0xffffffff830e3000 3218 iichid.ko >> >> 21 5 0xffffffff830e7000 3380 hidbus.ko >> >> 22 1 0xffffffff830eb000 21e8 hms.ko >> >> 23 1 0xffffffff830ee000 40a8 hidmap.ko >> >> 24 1 0xffffffff830f3000 3355 hmt.ko >> >> 25 1 0xffffffff830f7000 22cc hconf.ko >> >> 26 1 0xffffffff830fa000 2260 pflog.ko >> >> 27 1 0xffffffff830fd000 56540 pf.ko >> >> 28 1 0xffffffff83154000 3560 fdescfs.ko >> >> >> >> >> >> Thanks! >> >> >> >> --Chri >> > >> > >> > I have a T16 and ran into that issue. It may be that BIOS changes have >> > broken things, but I found that, by default, the F keys control volume, >> > screen brightness, and many other things. I can use Fn+F[1-12] to perform >> > traditional function key functions. I found that bios has an option to make >> > the traditional functions the default which is how I am running today and >> > have since shortly after I purchased the computer. One I set that BIOS >> > option, everything worked "properly". I now use Fn+F[1-12] to adjust volume >> > and screen brightness. I hope to get mute to work, but I need to figure out >> > which event is set when Fn+F1 is pressed to write trivial devd support for >> > it. >> Well, I can't explain it. I set everything up in the BIOS to work >> "traditionally" >> and everything worked fine up until the upgrade. Where everything went >> "south" >> in the Fn department. But since you mentioned it. I thought I'd review the >> settings >> and sure enough, the Function key settings had changed. I have no >> explanation. I >> haven't been to the BIOS settings since initial setup. But only that >> setting >> was >> changed. I can't thank you enough for mentioning this, Kevin. I *really* >> appreciate >> your taking the time to reply! > > So I was correct. ;-) I don't know how in the **** I missed your suggestion. Thank you for figuring it out, (even if I somehow missed it)! How embarrassing. > > >> > BTW, if you have not found it, Fn+K is screen lock. Most everything on my >> > T16 now works with FreeBSD CURRENT. >> Thanks. That was the first thing I looked for when I got it. I can't live >> w/o >> the scrollock. Took me a bit. But I found it too. :) > > Another datapoint. > Even on Lenovo ThinkPad series, the alternative ScrLk is different. > On my ThinkPad P52, Non-existent ScrLk is mapped to Fn+B, not Fn+K. > You should better reading provided PDF manual closely before ordering > next time. Lenovo provides it relatively early for ThinkPads. Understood. My last Thinkpad was that way. I wish they could decide on one way, and just stick with it. :/ Thanks again! > > >> >> Thanks again! :) >> From nobody Tue Apr 2 18:52:38 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4V8H7w1W8zz5FWcq for ; Tue, 2 Apr 2024 18:53:00 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from www121.sakura.ne.jp (www121.sakura.ne.jp [153.125.133.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4V8H7v4JdQz4rWY for ; Tue, 2 Apr 2024 18:52:58 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Authentication-Results: mx1.freebsd.org; none Received: from kalamity.joker.local (123-1-21-232.area1b.commufa.jp [123.1.21.232]) (authenticated bits=0) by www121.sakura.ne.jp (8.17.1/8.17.1/[SAKURA-WEB]/20201212) with ESMTPA id 432IqcmC003436; Wed, 3 Apr 2024 03:52:39 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) Date: Wed, 3 Apr 2024 03:52:38 +0900 From: Tomoaki AOKI To: Chris Cc: Kevin Oberman , freebsd-current Subject: Re: Multi cons support has disappeared (on Alder Lake) was: Alt+Fn isn't functional. Has this been removed? Message-Id: <20240403035238.6fdcdb6f4b6fc3ecdee7f85a@dec.sakura.ne.jp> In-Reply-To: References: <20240402203217.713707a1cdef4c08905ca4e0@dec.sakura.ne.jp> Organization: Junchoon corps X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd14.0) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:7684, ipnet:153.125.128.0/18, country:JP] X-Rspamd-Queue-Id: 4V8H7v4JdQz4rWY On Tue, 02 Apr 2024 08:53:15 -0700 Chris wrote: > On 2024-04-02 04:32, Tomoaki AOKI wrote: > > On Tue, 02 Apr 2024 00:42:23 -0700 > > Chris wrote: > > > >> On 2024-04-01 22:51, Kevin Oberman wrote: > >> > On Mon, Apr 1, 2024 at 3:05 PM Chris wrote: > >> > > >> >> I experience challenges running FreeBSD on my Alder Lake laptop. > >> >> With some help on the list and Bugzilla, I was able to get Graphics > >> >> WiFi at least working. But still wasn't as stable as running on > >> >> more dated CPU's. As it is; I'm only able to use CURRENT. Beginning > >> >> of last week, in hopes of getting a more stable experience. I wiped > >> >> the partition (UFS) and unpacked the version available on the FreeBSD > >> >> ftp servers at that time. I quickly discovered that multi-cons (Ctrl+ > >> >> Alt+Fn || Alt+Fn) was no longer available. I posted this discovery to > >> >> the list. But no solution was discovered. I've since attempted to use > >> >> 2 more different newer versions. Both of them were also w/o multi-con(s) > >> >> support. What must I do to fix, or uncover the cause of this? > >> >> I only load the associated GPU module in rc.conf(5) (no keyboard settings). > >> >> I'm also unable to get multi-cons booting from any of the boot media > >> >> produced within the last week. > >> >> > >> >> Following are some specifics: > >> >> > >> >> CPU: 12th Gen Intel(R) Core(TM) i3-1215U (2496.00-MHz K8-class CPU) > >> >> > >> >> IdeaPad 3 17IAU7 > >> >> > >> >> WORKS: > >> >> FreeBSD 15.0-CURRENT #0 main-n267640-7a4d1d1df0b2: > >> >> Thu Jan 18 04:04:32 UTC 2024 > >> >> > >> >> DOESN'T WORK: > >> >> FreeBSD 15.0-CURRENT #0 main-n269036-6baddb6b1176: > >> >> Fri Mar 29 10:19:43 UTC 2024 > >> >> root@releng3.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC > >> >> amd64 > >> >> > >> >> FreeBSD 15.0-CURRENT #0 main-n268793-220ee18f1964: > >> >> Thu Mar 14 02:58:39 UTC 2024 > >> >> root@releng3.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC > >> >> amd64 > >> >> > >> >> hostb0@pci0:0:0:0: class=0x060000 rev=0x04 hdr=0x00 vendor=0x8086 > >> >> device=0x4609 subvendor=0x17aa subdevice=0x3803 > >> >> vendor = 'Intel Corporation' > >> >> class = bridge > >> >> subclass = HOST-PCI > >> >> vgapci0@pci0:0:2:0: class=0x030000 rev=0x0c hdr=0x00 vendor=0x8086 > >> >> device=0x46b3 subvendor=0x17aa subdevice=0x3b3a > >> >> vendor = 'Intel Corporation' > >> >> device = 'Alder Lake-UP3 GT1 [UHD Graphics]' > >> >> class = display > >> >> subclass = VGA > >> >> none0@pci0:0:4:0: class=0x118000 rev=0x04 hdr=0x00 vendor=0x8086 > >> >> device=0x461d subvendor=0x17aa subdevice=0x380c > >> >> vendor = 'Intel Corporation' > >> >> device = 'Alder Lake Innovation Platform Framework Processor > >> >> Participant' > >> >> class = dasp > >> >> pcib1@pci0:0:6:0: class=0x060400 rev=0x04 hdr=0x01 vendor=0x8086 > >> >> device=0x464d subvendor=0x17aa subdevice=0x380e > >> >> vendor = 'Intel Corporation' > >> >> device = '12th Gen Core Processor PCI Express x4 Controller' > >> >> class = bridge > >> >> subclass = PCI-PCI > >> >> none1@pci0:0:10:0: class=0x118000 rev=0x01 hdr=0x00 vendor=0x8086 > >> >> device=0x467d subvendor=0x17aa subdevice=0x3813 > >> >> vendor = 'Intel Corporation' > >> >> device = 'Platform Monitoring Technology' > >> >> class = dasp > >> >> xhci0@pci0:0:13:0: class=0x0c0330 rev=0x04 hdr=0x00 vendor=0x8086 > >> >> device=0x461e subvendor=0x17aa subdevice=0x3824 > >> >> vendor = 'Intel Corporation' > >> >> device = 'Alder Lake-P Thunderbolt 4 USB Controller' > >> >> class = serial bus > >> >> subclass = USB > >> >> xhci1@pci0:0:20:0: class=0x0c0330 rev=0x01 hdr=0x00 vendor=0x8086 > >> >> device=0x51ed subvendor=0x17aa subdevice=0x3820 > >> >> vendor = 'Intel Corporation' > >> >> device = 'Alder Lake PCH USB 3.2 xHCI Host Controller' > >> >> class = serial bus > >> >> subclass = USB > >> >> none2@pci0:0:20:2: class=0x050000 rev=0x01 hdr=0x00 vendor=0x8086 > >> >> device=0x51ef subvendor=0x17aa subdevice=0x381e > >> >> vendor = 'Intel Corporation' > >> >> device = 'Alder Lake PCH Shared SRAM' > >> >> class = memory > >> >> subclass = RAM > >> >> iwlwifi0@pci0:0:20:3: class=0x028000 rev=0x01 hdr=0x00 vendor=0x8086 > >> >> device=0x51f0 subvendor=0x8086 subdevice=0x0074 > >> >> vendor = 'Intel Corporation' > >> >> device = 'Alder Lake-P PCH CNVi WiFi' > >> >> class = network > >> >> ig4iic0@pci0:0:21:0: class=0x0c8000 rev=0x01 hdr=0x00 vendor=0x8086 > >> >> device=0x51e8 subvendor=0x17aa subdevice=0x3812 > >> >> vendor = 'Intel Corporation' > >> >> device = 'Alder Lake PCH Serial IO I2C Controller' > >> >> class = serial bus > >> >> ig4iic1@pci0:0:21:1: class=0x0c8000 rev=0x01 hdr=0x00 vendor=0x8086 > >> >> device=0x51e9 subvendor=0x17aa subdevice=0x3814 > >> >> vendor = 'Intel Corporation' > >> >> device = 'Alder Lake PCH Serial IO I2C Controller' > >> >> class = serial bus > >> >> none3@pci0:0:22:0: class=0x078000 rev=0x01 hdr=0x00 vendor=0x8086 > >> >> device=0x51e0 subvendor=0x17aa subdevice=0x3815 > >> >> vendor = 'Intel Corporation' > >> >> device = 'Alder Lake PCH HECI Controller' > >> >> class = simple comms > >> >> ahci0@pci0:0:23:0: class=0x010601 rev=0x01 hdr=0x00 vendor=0x8086 > >> >> device=0x51d3 subvendor=0x8086 subdevice=0x7270 > >> >> vendor = 'Intel Corporation' > >> >> device = 'Alder Lake-P SATA AHCI Controller' > >> >> class = mass storage > >> >> subclass = SATA > >> >> pcib2@pci0:0:29:0: class=0x060400 rev=0x01 hdr=0x01 vendor=0x8086 > >> >> device=0x51b1 subvendor=0x17aa subdevice=0x381f > >> >> vendor = 'Intel Corporation' > >> >> device = 'Alder Lake PCI Express x1 Root Port' > >> >> class = bridge > >> >> subclass = PCI-PCI > >> >> isab0@pci0:0:31:0: class=0x060100 rev=0x01 hdr=0x00 vendor=0x8086 > >> >> device=0x5182 subvendor=0x17aa subdevice=0x382b > >> >> vendor = 'Intel Corporation' > >> >> device = 'Alder Lake PCH eSPI Controller' > >> >> class = bridge > >> >> subclass = PCI-ISA > >> >> hdac0@pci0:0:31:3: class=0x040380 rev=0x01 hdr=0x00 vendor=0x8086 > >> >> device=0x51c8 subvendor=0x17aa subdevice=0x3881 > >> >> vendor = 'Intel Corporation' > >> >> device = 'Alder Lake PCH-P High Definition Audio Controller' > >> >> class = multimedia > >> >> subclass = HDA > >> >> ichsmb0@pci0:0:31:4: class=0x0c0500 rev=0x01 hdr=0x00 vendor=0x8086 > >> >> device=0x51a3 subvendor=0x17aa subdevice=0x382f > >> >> vendor = 'Intel Corporation' > >> >> device = 'Alder Lake PCH-P SMBus Host Controller' > >> >> class = serial bus > >> >> subclass = SMBus > >> >> none4@pci0:0:31:5: class=0x0c8000 rev=0x01 hdr=0x00 vendor=0x8086 > >> >> device=0x51a4 subvendor=0x17aa subdevice=0x381c > >> >> vendor = 'Intel Corporation' > >> >> device = 'Alder Lake-P PCH SPI Controller' > >> >> class = serial bus > >> >> nvme0@pci0:1:0:0: class=0x010802 rev=0x01 hdr=0x00 vendor=0x2646 > >> >> device=0x5013 subvendor=0x2646 subdevice=0x5013 > >> >> vendor = 'Kingston Technology Company, Inc.' > >> >> device = 'KC3000/FURY Renegade NVMe SSD E18' > >> >> class = mass storage > >> >> subclass = NVM > >> >> sdhci_pci0@pci0:2:0:0: class=0x080501 rev=0x01 hdr=0x00 vendor=0x1217 > >> >> device=0x8621 subvendor=0x17aa subdevice=0x3874 > >> >> vendor = 'O2 Micro, Inc.' > >> >> device = 'SD/MMC Card Reader Controller' > >> >> class = base peripheral > >> >> subclass = SD host controller > >> >> > >> >> Id Refs Address Size Name > >> >> 1 95 0xffffffff80200000 1d527c0 kernel > >> >> 2 1 0xffffffff81f54000 287e8 fusefs.ko > >> >> 3 1 0xffffffff82d8f000 1e3228 i915kms.ko > >> >> 4 2 0xffffffff82f73000 85090 drm.ko > >> >> 5 1 0xffffffff82ff9000 22b8 iic.ko > >> >> 6 2 0xffffffff82ffc000 40e9 linuxkpi_video.ko > >> >> 7 3 0xffffffff83001000 7358 dmabuf.ko > >> >> 8 3 0xffffffff83009000 3378 lindebugfs.ko > >> >> 9 1 0xffffffff8300d000 c338 ttm.ko > >> >> 10 1 0xffffffff8301a000 5760 cuse.ko > >> >> 11 1 0xffffffff83020000 3390 acpi_wmi.ko > >> >> 12 1 0xffffffff83024000 4250 ichsmb.ko > >> >> 13 1 0xffffffff83029000 2178 smbus.ko > >> >> 14 1 0xffffffff8302c000 91260 if_iwlwifi.ko > >> >> 15 1 0xffffffff830be000 5f90 ig4.ko > >> >> 16 1 0xffffffff830c4000 4d20 ng_ubt.ko > >> >> 17 3 0xffffffff830c9000 bbb8 netgraph.ko > >> >> 18 2 0xffffffff830d5000 a250 ng_hci.ko > >> >> 19 2 0xffffffff830e0000 2670 ng_bluetooth.ko > >> >> 20 1 0xffffffff830e3000 3218 iichid.ko > >> >> 21 5 0xffffffff830e7000 3380 hidbus.ko > >> >> 22 1 0xffffffff830eb000 21e8 hms.ko > >> >> 23 1 0xffffffff830ee000 40a8 hidmap.ko > >> >> 24 1 0xffffffff830f3000 3355 hmt.ko > >> >> 25 1 0xffffffff830f7000 22cc hconf.ko > >> >> 26 1 0xffffffff830fa000 2260 pflog.ko > >> >> 27 1 0xffffffff830fd000 56540 pf.ko > >> >> 28 1 0xffffffff83154000 3560 fdescfs.ko > >> >> > >> >> > >> >> Thanks! > >> >> > >> >> --Chri > >> > > >> > > >> > I have a T16 and ran into that issue. It may be that BIOS changes have > >> > broken things, but I found that, by default, the F keys control volume, > >> > screen brightness, and many other things. I can use Fn+F[1-12] to perform > >> > traditional function key functions. I found that bios has an option to make > >> > the traditional functions the default which is how I am running today and > >> > have since shortly after I purchased the computer. One I set that BIOS > >> > option, everything worked "properly". I now use Fn+F[1-12] to adjust volume > >> > and screen brightness. I hope to get mute to work, but I need to figure out > >> > which event is set when Fn+F1 is pressed to write trivial devd support for > >> > it. > >> Well, I can't explain it. I set everything up in the BIOS to work > >> "traditionally" > >> and everything worked fine up until the upgrade. Where everything went > >> "south" > >> in the Fn department. But since you mentioned it. I thought I'd review the > >> settings > >> and sure enough, the Function key settings had changed. I have no > >> explanation. I > >> haven't been to the BIOS settings since initial setup. But only that > >> setting > >> was > >> changed. I can't thank you enough for mentioning this, Kevin. I *really* > >> appreciate > >> your taking the time to reply! > > > > So I was correct. ;-) > I don't know how in the **** I missed your suggestion. Thank you for figuring > it out, > (even if I somehow missed it)! How embarrassing. Maybe just because my previous post was sent to this ML only, not including your email directly as a recipient. ;-) > >> > BTW, if you have not found it, Fn+K is screen lock. Most everything on my > >> > T16 now works with FreeBSD CURRENT. > >> Thanks. That was the first thing I looked for when I got it. I can't live > >> w/o > >> the scrollock. Took me a bit. But I found it too. :) > > > > Another datapoint. > > Even on Lenovo ThinkPad series, the alternative ScrLk is different. > > On my ThinkPad P52, Non-existent ScrLk is mapped to Fn+B, not Fn+K. > > You should better reading provided PDF manual closely before ordering > > next time. Lenovo provides it relatively early for ThinkPads. > Understood. My last Thinkpad was that way. I wish they could decide on > one way, and just stick with it. :/ > > Thanks again! > > > > > >> > >> Thanks again! :) -- Tomoaki AOKI From nobody Tue Apr 2 23:24:07 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4V8P956Hqtz5FyxH for ; Tue, 2 Apr 2024 23:24:25 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-yb1-xb34.google.com (mail-yb1-xb34.google.com [IPv6:2607:f8b0:4864:20::b34]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4V8P950sX4z45mY for ; Tue, 2 Apr 2024 23:24:25 +0000 (UTC) (envelope-from kob6558@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-yb1-xb34.google.com with SMTP id 3f1490d57ef6-dc6d8bd612dso5833204276.1 for ; Tue, 02 Apr 2024 16:24:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1712100264; x=1712705064; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=byc0HT6BXCJ3AW4IMFsFm/8/+qekMnZG+TBYN+elkpY=; b=Ej30BzL0vAN0lbnqw7GkKHOB688MlAnFiTikEMQT+nYG4KXm7C4Simajv06pDJTAMl mCW1JhsUyXeMu+AdDQEluDi3NLNaCATUorhYCBlqGkA3ousRrM/pXX8dLPIYFnoGaNPB TDis5vzKqcZiivIhvAWSG6mVn9aeCz7MFjiGvTsHw2Ic5xhGCxyxlI/QRTyDBZJ/TpLz fJe8ENW4sNenFR7wM6Gi56xo6/2AXvpPLpzsp7kqYL2DTEprbure4JDf59mMJ6mvFfuH 88RbnR7rRDNrZJbWUBofQksOeEEqQirSXRaaO31IZMwlH4BlZ332Eb9KvfhbumcoOMZv 8A3Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1712100264; x=1712705064; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=byc0HT6BXCJ3AW4IMFsFm/8/+qekMnZG+TBYN+elkpY=; b=FdQX6oUl472iRZIyKcUlFvDEJdeRnyGRwsKOy+2sCsuQM3sFWLnE+80OQ92czU0raE Yvnp9uzv9sEsCpRZx1p+qp3GWrEqfmOOiqxf1B5ZHn/1fDKfwqQD3/3mpayalXvp1Yma 27n4BHnquPu9JiRbb7FYfQ5HegLqh5T7d66BckT/M+RoiyEfUWFksCIbPaU5uBV0HAMM 0o60JdGYRVj9war/1VT3sL2/nLjrG/4DM+ToX11HMXkZFZbntng8eQ2XepPryzzSFu3h PgavQajmbPOOeUy68sRXFTJe9e2WNh3eWUfJEIeX41rcOF8kaW64KlwKpphvpaTbxUv8 pFbA== X-Forwarded-Encrypted: i=1; AJvYcCXqIo3nKZxdJxjAnBGs6S71KnV8XAzRUwtxOD+aXX+B1BkVS5vSlw5VjhdvpCwchfws1DH/AC5dss/9txK4hEo8LQm0hRJXKltPqMk= X-Gm-Message-State: AOJu0Yy87sddk7ZKQFs377/cmUV59TSwJ4dJj5wQqEL65FUj2bUdXGON 3TSarUKa9uTA3ocsDGSSOMx3KFVveoyjseuPOBOqX78XHlz58MbEtF5O44Z9drN2fRBLAOEzXlD McqrUUMvulBKOLowASDcPsAgDZVKImOPwRic= X-Google-Smtp-Source: AGHT+IEhOYJx0lUZ0dy1KAUPjIMYx7tOM0lSBpmUMvWa9wT0uEI/2JeJ4ve9WZaP5XwUA0vG2ZxBLBmTieSpjcMFfAU= X-Received: by 2002:a25:4b82:0:b0:dcf:c389:854c with SMTP id y124-20020a254b82000000b00dcfc389854cmr12080805yba.16.1712100264197; Tue, 02 Apr 2024 16:24:24 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: <20240402203217.713707a1cdef4c08905ca4e0@dec.sakura.ne.jp> <20240403035238.6fdcdb6f4b6fc3ecdee7f85a@dec.sakura.ne.jp> In-Reply-To: <20240403035238.6fdcdb6f4b6fc3ecdee7f85a@dec.sakura.ne.jp> From: Kevin Oberman Date: Tue, 2 Apr 2024 16:24:07 -0700 Message-ID: Subject: Re: Multi cons support has disappeared (on Alder Lake) was: Alt+Fn isn't functional. Has this been removed? To: Tomoaki AOKI Cc: Chris , freebsd-current Content-Type: multipart/alternative; boundary="000000000000114bc90615256802" X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4V8P950sX4z45mY --000000000000114bc90615256802 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, Apr 2, 2024 at 11:53=E2=80=AFAM Tomoaki AOKI wrote: > On Tue, 02 Apr 2024 08:53:15 -0700 > Chris wrote: > > > On 2024-04-02 04:32, Tomoaki AOKI wrote: > > > On Tue, 02 Apr 2024 00:42:23 -0700 > > > Chris wrote: > > > > > >> On 2024-04-01 22:51, Kevin Oberman wrote: > > >> > On Mon, Apr 1, 2024 at 3:05=E2=80=AFPM Chris > wrote: > > >> > > > >> >> I experience challenges running FreeBSD on my Alder Lake laptop. > > >> >> With some help on the list and Bugzilla, I was able to get Graphi= cs > > >> >> WiFi at least working. But still wasn't as stable as running on > > >> >> more dated CPU's. As it is; I'm only able to use CURRENT. Beginni= ng > > >> >> of last week, in hopes of getting a more stable experience. I wip= ed > > >> >> the partition (UFS) and unpacked the version available on the > FreeBSD > > >> >> ftp servers at that time. I quickly discovered that multi-cons > (Ctrl+ > > >> >> Alt+Fn || Alt+Fn) was no longer available. I posted this discover= y > to > > >> >> the list. But no solution was discovered. I've since attempted to > use > > >> >> 2 more different newer versions. Both of them were also w/o > multi-con(s) > > >> >> support. What must I do to fix, or uncover the cause of this? > > >> >> I only load the associated GPU module in rc.conf(5) (no keyboard > settings). > > >> >> I'm also unable to get multi-cons booting from any of the boot > media > > >> >> produced within the last week. > > >> >> > > >> >> Following are some specifics: > > >> >> > > >> >> CPU: 12th Gen Intel(R) Core(TM) i3-1215U (2496.00-MHz K8-class CP= U) > > >> >> > > >> >> IdeaPad 3 17IAU7 > > >> >> > [Lots of details elided]] > > >> > > > >> > I have a T16 and ran into that issue. It may be that BIOS changes > have > > >> > broken things, but I found that, by default, the F keys control > volume, > > >> > screen brightness, and many other things. I can use Fn+F[1-12] to > perform > > >> > traditional function key functions. I found that bios has an optio= n > to make > > >> > the traditional functions the default which is how I am running > today and > > >> > have since shortly after I purchased the computer. One I set that > BIOS > > >> > option, everything worked "properly". I now use Fn+F[1-12] to > adjust volume > > >> > and screen brightness. I hope to get mute to work, but I need to > figure out > > >> > which event is set when Fn+F1 is pressed to write trivial devd > support for > > >> > it. > > >> Well, I can't explain it. I set everything up in the BIOS to work > > >> "traditionally" > > >> and everything worked fine up until the upgrade. Where everything we= nt > > >> "south" > > >> in the Fn department. But since you mentioned it. I thought I'd > review the > > >> settings > > >> and sure enough, the Function key settings had changed. I have no > > >> explanation. I > > >> haven't been to the BIOS settings since initial setup. But only that > > >> setting > > >> was > > >> changed. I can't thank you enough for mentioning this, Kevin. I > *really* > > >> appreciate > > >> your taking the time to reply! > > > > > > So I was correct. ;-) > > I don't know how in the **** I missed your suggestion. Thank you for > figuring > > it out, > > (even if I somehow missed it)! How embarrassing. > > Maybe just because my previous post was sent to this ML only, not > including your email directly as a recipient. ;-) > FWIW, when I sent the message to "All", bsdforge had blocked it (550 5.0.0 REJECT, too much abuse from your host). If this is an indication that my system is misbehaving, please let me know. --=20 Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 --000000000000114bc90615256802 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Tue, Apr 2, 2024 at 11:53=E2= =80=AFAM Tomoaki AOKI <junchoon@dec.sakura.ne.jp> wrote:
On Tue,= 02 Apr 2024 08:53:15 -0700
Chris <bsd-l= ists@bsdforge.com> wrote:

> On 2024-04-02 04:32, Tomoaki AOKI wrote:
> > On Tue, 02 Apr 2024 00:42:23 -0700
> > Chris <bsd-lists@bsdforge.com> wrote:
> >
> >> On 2024-04-01 22:51, Kevin Oberman wrote:
> >> > On Mon, Apr 1, 2024 at 3:05=E2=80=AFPM Chris <bsd-lists@bsdforge.com= > wrote:
> >> >
> >> >> I experience challenges running FreeBSD on my Alder = Lake laptop.
> >> >> With some help on the list and Bugzilla, I was able = to get Graphics
> >> >> WiFi at least working. But still wasn't as stabl= e as running on
> >> >> more dated CPU's. As it is; I'm only able to= use CURRENT. Beginning
> >> >> of last week, in hopes of getting a more stable expe= rience. I wiped
> >> >> the partition (UFS) and unpacked the version availab= le on the FreeBSD
> >> >> ftp servers at that time. I quickly discovered that = multi-cons (Ctrl+
> >> >> Alt+Fn || Alt+Fn) was no longer available. I posted = this discovery to
> >> >> the list. But no solution was discovered. I've s= ince attempted to use
> >> >> 2 more different newer versions. Both of them were a= lso w/o multi-con(s)
> >> >> support. What must I do to fix, or uncover the cause= of this?
> >> >> I only load the associated GPU module in rc.conf(5) = (no keyboard settings).
> >> >> I'm also unable to get multi-cons booting from a= ny of the boot media
> >> >> produced within the last week.
> >> >>
> >> >> Following are some specifics:
> >> >>
> >> >> CPU: 12th Gen Intel(R) Core(TM) i3-1215U (2496.00-MH= z K8-class CPU)
> >> >>
> >> >> IdeaPad 3 17IAU7
> >> >>
[Lots of details eli= ded]]
&g= t; >> >
> >> > I have a T16 and ran into that issue. It may be that BIO= S changes have
> >> > broken things, but I found that, by default, the F keys = control volume,
> >> > screen brightness, and many other things. I can use Fn+F= [1-12] to perform
> >> > traditional function key functions. I found that bios ha= s an option to make
> >> > the traditional functions the default which is how I am = running today and
> >> > have since shortly after I purchased the computer. One I= set that BIOS
> >> > option, everything worked "properly". I now us= e Fn+F[1-12] to adjust volume
> >> > and screen brightness. I hope to get mute to work, but I= need to figure out
> >> > which event is set when Fn+F1 is pressed to write trivia= l devd support for
> >> > it.
> >> Well, I can't explain it. I set everything up in the BIOS= to work
> >> "traditionally"
> >> and everything worked fine up until the upgrade. Where everyt= hing went
> >> "south"
> >> in the Fn department. But since you mentioned it. I thought I= 'd review the
> >> settings
> >> and sure enough, the Function key settings had changed. I hav= e no
> >> explanation. I
> >> haven't been to the BIOS settings since initial setup. Bu= t only that
> >> setting
> >> was
> >> changed. I can't thank you enough for mentioning this, Ke= vin. I *really*
> >> appreciate
> >> your taking the time to reply!
> >
> > So I was correct. ;-)
> I don't know how in the **** I missed your suggestion. Thank you f= or figuring
> it out,
> (even if I somehow missed it)! How embarrassing.

Maybe just because my previous post was sent to this ML only, not
including your email directly as a recipient. ;-)

=
FWIW, when I sent the message to "All",=C2=A0 bsd= forge had blocked it (550 5.0.0 REJECT, too much abuse from your host). If = this is an indication that my system is misbehaving, please let me know.
--
<= div>
Kevin Oberman, Part time kid her= der and retired Network Engineer
E-mail: rkoberman@gmail.com
PGP Fingerp= rint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
--000000000000114bc90615256802-- From nobody Wed Apr 3 18:32:54 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4V8tfT0wZhz5Fb18 for ; Wed, 3 Apr 2024 18:33:05 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mx1.sbone.de (cross.sbone.de [195.201.62.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx1.sbone.de", Issuer "SBone.DE Root Certificate Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4V8tfS316Dz4BP0 for ; Wed, 3 Apr 2024 18:33:04 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of bzeeb-lists@lists.zabbadoz.net designates 195.201.62.131 as permitted sender) smtp.mailfrom=bzeeb-lists@lists.zabbadoz.net Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:1025]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.sbone.de (Postfix) with ESMTPS id 68E8A8D4A177 for ; Wed, 3 Apr 2024 18:32:56 +0000 (UTC) Received: from content-filter.t4-02.sbone.de (content-filter.t4-02.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:2742]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id 17E9C2D029D8 for ; Wed, 3 Apr 2024 18:32:56 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:4902:0:7404:2:1025]) by content-filter.t4-02.sbone.de (content-filter.t4-02.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:2742]) (amavisd-new, port 10024) with ESMTP id cBau8hxEhdVE for ; Wed, 3 Apr 2024 18:32:55 +0000 (UTC) Received: from strong-iwl0.sbone.de (strong-iwl0.sbone.de [IPv6:fde9:577b:c1a9:4902:b66b:fcff:fef3:e3d2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id 309C22D029D2 for ; Wed, 3 Apr 2024 18:32:55 +0000 (UTC) Date: Wed, 3 Apr 2024 18:32:54 +0000 (UTC) From: "Bjoern A. Zeeb" To: freebsd-current@freebsd.org Subject: LOR so_snd_sx / nfs Message-ID: <6nn67272-3osp-26o7-170p-14p1n6476633@yvfgf.mnoonqbm.arg> X-OpenPGP-Key-Id: 0x14003F198FEFA3E77207EE8D2B58B8F83CCF1842 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset=US-ASCII X-Spamd-Bar: - X-Spamd-Result: default: False [-1.80 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_SPAM_SHORT(0.50)[0.497]; R_SPF_ALLOW(-0.20)[+ip4:195.201.62.131]; MIME_GOOD(-0.10)[text/plain]; FROM_HAS_DN(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:24940, ipnet:195.201.0.0/16, country:DE]; R_DKIM_NA(0.00)[]; MISSING_XM_UA(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; RCVD_COUNT_THREE(0.00)[4]; DMARC_NA(0.00)[zabbadoz.net]; TO_DN_NONE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_LAST(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; ARC_NA(0.00)[] X-Rspamd-Queue-Id: 4V8tfS316Dz4BP0 NFS root boot of a Lab machine; calling wpa_cli: Thilock order reversal: 1st 0xffff0001d4e1c800 so_snd_sx (so_snd_sx, sx) @ /usr/src/sys/kern/uipc_socket.c:4020 2nd 0xffffa020cb20e930 nfs (nfs, lockmgr) @ /usr/src/sys/kern/vfs_lookup.c:1083 lock order nfs -> so_snd_sx established at: #0 0xffff000000529588 at witness_checkorder+0x328 #1 0xffff0000004bdf48 at _sx_xlock+0x70 #2 0xffff0000005687e0 at soiolock+0x5c #3 0xffff000000567ff0 at sosend_generic+0x104 #4 0xffff0000005688b8 at sosend+0x48 #5 0xffff00000076b6a0 at clnt_vc_call+0x570 #6 0xffff000000769914 at clnt_reconnect_call+0x1c4 #7 0xffff0000003552ec at newnfs_request+0x7e4 #8 0xffff00000037abf0 at nfsrpc_getattrnovp+0xfc #9 0xffff00000039823c at mountnfs+0x6ec #10 0xffff000000395c64 at nfs_mount+0xe78 #11 0xffff00000059b59c at vfs_mount_sigdefer+0x30 #12 0xffff0000005a44c8 at vfs_domount_first+0x254 #13 0xffff0000005a0884 at vfs_domount+0x2d4 #14 0xffff00000059f1ec at vfs_donmount+0x824 #15 0xffff0000005a3438 at kernel_mount+0x64 #16 0xffff0000005a72b0 at parse_mount+0x494 #17 0xffff0000005a59ac at vfs_mountroot+0x5b8 lock order so_snd_sx -> nfs attempted at: #0 0xffff000000529cd8 at witness_checkorder+0xa78 #1 0xffff00000047edb8 at lockmgr_lock_flags+0x78 #2 0xffff000000390044 at nfs_lock+0x34 #3 0xffff00000059793c at vop_sigdefer+0x38 #4 0xffff0000005c3734 at _vn_lock+0x58 #5 0xffff00000059cb78 at vfs_lookup+0x12c #6 0xffff00000059c01c at namei+0x280 #7 0xffff0000005751f8 at unp_connectat+0x244 #8 0xffff000000576adc at uipc_sosend_dgram+0x3c0 #9 0xffff0000005689c8 at sousrsend+0x80 #10 0xffff00000056ec90 at kern_sendit+0x1e4 #11 0xffff00000056ef78 at sendit+0x1b0 #12 0xffff00000056edb4 at sys_sendto+0x4c #13 0xffff00000086ad40 at do_el0_sync+0x59c #14 0xffff00000084391c at handle_el0_sync+0x48 -- Bjoern A. Zeeb r15:7 From nobody Wed Apr 3 20:07:37 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4V8wln0PC1z5FmJ6 for ; Wed, 3 Apr 2024 20:07:49 +0000 (UTC) (envelope-from rick.macklem@gmail.com) Received: from mail-pg1-x529.google.com (mail-pg1-x529.google.com [IPv6:2607:f8b0:4864:20::529]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4V8wlm5fnnz4PlM for ; Wed, 3 Apr 2024 20:07:48 +0000 (UTC) (envelope-from rick.macklem@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pg1-x529.google.com with SMTP id 41be03b00d2f7-5c229dabbb6so234602a12.0 for ; Wed, 03 Apr 2024 13:07:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1712174867; x=1712779667; darn=freebsd.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=QQf19O/8UxyRQ1CO8FnM4C8IrF1zKd8zRWQT2UO0A6I=; b=HlsflcYSsU7UXtd/LnDBCzXdwCnGGGPIjdDJq6NPA25wavs7FMRL2TesC5okT/yxm1 TTuhatU/I+l/8EVLbD8+sdI3CSGeNUsCE+/xsExBatify8bepwXk4rPRdtANARQ7h2gM vUyP1dj8piOekbRbsdOFN6BMekjBgyRiPhP0TwD3GfEECPwzAhVC2bPko+Dq54NahOtI RiVlTpwW1GUXQTRnSZOdM3tdw38kU1/T8ZlEVAUmksvFBClpKSwhTprMRh5DwCsfi0U0 5NiANaHpP0LxoxYoxddKhnvpiBnBUzGaq3BtbVhDNNnYKzSG5DCDkdrBHgnxn/s8tWbs NjpA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1712174867; x=1712779667; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=QQf19O/8UxyRQ1CO8FnM4C8IrF1zKd8zRWQT2UO0A6I=; b=wzT9QN5d9F/IDLdyZ85khIs0NHV3bv0+sYbJbjJqpIjJQcMuuOmm41fVxkMNuyDW1Y L1qunNjXfyBIjgpv3uVhDJfeTLX5eB/+4NM7eAWymvbL0pIn7l9LHA7ES4RulngaVc7E wZRevDEmZELaM16AdhnrwTkjakLXHXJL8eYUr5bzeE8OWzvfL4CpFPc70AF+VZS1vcpv FLNvwy8GrXcxwdUz3UEVaU9R4fO/R6vutz7dQIwvXk6ylqVugdSwryR2CQrmOJXJ3nIc ZW9OduN5QNLZAZYjVj1EiWknZeMKCYGnSChn0QiRC8w9GlEY871h/WuHMpEVYmuqPuYm Ro7w== X-Gm-Message-State: AOJu0YyV3GlT7R4idLnImW+C4Ne91StdeFm1/uIit2DdXeRSPoiuonW9 mK/xfqpI+49x4FJebbyyz79zA056H+rEu35zNSghV8HIO+mO61YqTC5/7AzWaL1nfzoG4GtmDN1 7b+cE8pGMzSQKzlniuzylzAiDYpzUwAw= X-Google-Smtp-Source: AGHT+IEjn8EYR9lQC8JFfBdoqhglQZJN1sSC5eRvEVapgXqdV7alhqqNDNX12md4YZ+Fa2ZKRZ2VLcUxVLfA0WSdZr0= X-Received: by 2002:a05:6a20:2d2a:b0:1a3:53e7:16da with SMTP id g42-20020a056a202d2a00b001a353e716damr847138pzl.15.1712174867221; Wed, 03 Apr 2024 13:07:47 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: <6nn67272-3osp-26o7-170p-14p1n6476633@yvfgf.mnoonqbm.arg> In-Reply-To: <6nn67272-3osp-26o7-170p-14p1n6476633@yvfgf.mnoonqbm.arg> From: Rick Macklem Date: Wed, 3 Apr 2024 13:07:37 -0700 Message-ID: Subject: Re: LOR so_snd_sx / nfs To: "Bjoern A. Zeeb" Cc: freebsd-current@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; TAGGED_FROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4V8wlm5fnnz4PlM Shouldn't be a problem. The socket used for lookup is AF_UNIX (uses unp_connectat) and the NFS socket will always be UDP or TCP. Different sockets imply different socket locks. At least that's my interpretation, rick On Wed, Apr 3, 2024 at 11:33=E2=80=AFAM Bjoern A. Zeeb wrote: > > > NFS root boot of a Lab machine; calling wpa_cli: > > Thilock order reversal: > 1st 0xffff0001d4e1c800 so_snd_sx (so_snd_sx, sx) @ /usr/src/sys/kern/ui= pc_socket.c:4020 > 2nd 0xffffa020cb20e930 nfs (nfs, lockmgr) @ /usr/src/sys/kern/vfs_looku= p.c:1083 > lock order nfs -> so_snd_sx established at: > #0 0xffff000000529588 at witness_checkorder+0x328 > #1 0xffff0000004bdf48 at _sx_xlock+0x70 > #2 0xffff0000005687e0 at soiolock+0x5c > #3 0xffff000000567ff0 at sosend_generic+0x104 > #4 0xffff0000005688b8 at sosend+0x48 > #5 0xffff00000076b6a0 at clnt_vc_call+0x570 > #6 0xffff000000769914 at clnt_reconnect_call+0x1c4 > #7 0xffff0000003552ec at newnfs_request+0x7e4 > #8 0xffff00000037abf0 at nfsrpc_getattrnovp+0xfc > #9 0xffff00000039823c at mountnfs+0x6ec > #10 0xffff000000395c64 at nfs_mount+0xe78 > #11 0xffff00000059b59c at vfs_mount_sigdefer+0x30 > #12 0xffff0000005a44c8 at vfs_domount_first+0x254 > #13 0xffff0000005a0884 at vfs_domount+0x2d4 > #14 0xffff00000059f1ec at vfs_donmount+0x824 > #15 0xffff0000005a3438 at kernel_mount+0x64 > #16 0xffff0000005a72b0 at parse_mount+0x494 > #17 0xffff0000005a59ac at vfs_mountroot+0x5b8 > lock order so_snd_sx -> nfs attempted at: > #0 0xffff000000529cd8 at witness_checkorder+0xa78 > #1 0xffff00000047edb8 at lockmgr_lock_flags+0x78 > #2 0xffff000000390044 at nfs_lock+0x34 > #3 0xffff00000059793c at vop_sigdefer+0x38 > #4 0xffff0000005c3734 at _vn_lock+0x58 > #5 0xffff00000059cb78 at vfs_lookup+0x12c > #6 0xffff00000059c01c at namei+0x280 > #7 0xffff0000005751f8 at unp_connectat+0x244 > #8 0xffff000000576adc at uipc_sosend_dgram+0x3c0 > #9 0xffff0000005689c8 at sousrsend+0x80 > #10 0xffff00000056ec90 at kern_sendit+0x1e4 > #11 0xffff00000056ef78 at sendit+0x1b0 > #12 0xffff00000056edb4 at sys_sendto+0x4c > #13 0xffff00000086ad40 at do_el0_sync+0x59c > #14 0xffff00000084391c at handle_el0_sync+0x48 > > > -- > Bjoern A. Zeeb r15:7 > From nobody Thu Apr 4 05:49:56 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4V99hC1Y3Nz5GHsX; Thu, 4 Apr 2024 05:50:35 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Received: from smtp6.goneo.de (smtp6.goneo.de [85.220.129.31]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4V99h94FYQz4Kl6; Thu, 4 Apr 2024 05:50:33 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=walstatt-de.de header.s=DKIM001 header.b=QZdzpZjl; dmarc=none; spf=pass (mx1.freebsd.org: domain of freebsd@walstatt-de.de designates 85.220.129.31 as permitted sender) smtp.mailfrom=freebsd@walstatt-de.de Received: from hub1.goneo.de (hub1.goneo.de [IPv6:2001:1640:5::8:52]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by smtp6.goneo.de (Postfix) with ESMTPS id 123C5240124; Thu, 4 Apr 2024 07:50:26 +0200 (CEST) Received: from hub1.goneo.de (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by hub1.goneo.de (Postfix) with ESMTPS id 427ED24012A; Thu, 4 Apr 2024 07:50:24 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=walstatt-de.de; s=DKIM001; t=1712209824; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=rgmiFR5UmzWhC8md1Kqwc8Fd39sXZ9P0SUJ2ZSXJ9D4=; b=QZdzpZjl0bJMAqlp7V9TLtKKHig2JhIqCc/xr3f6/4yCIDRLFdhCyRJApAd6asAqhZbLbP nJ1fUn8AVj/CJH+JT2n4HRLt4aw3DzvNVjWMKqV8XmglTWDj1pqFlWAh7vb0PHALQN/g0l bDFdGAafXzqJ3iBEVaAXrSdZTVZX3+UXkjzSnheNYfvfLhMO5TEUR38E4WDVJZbmsL74r1 DKtslpaA9mu1rAgnetC1tZ+GG4Qb83eesTsPLtyVnqqekPEMiWpwfPXKjaHQjIOrOSl8v9 CxgFbjmo7gkiN/jnaR2kI3qn8nkcvlNVoTWR6gJLQFuZBUi3yfPo2lyH5x1EVg== Received: from thor.intern.walstatt.dynvpn.de (dynamic-089-014-109-072.89.14.pool.telefonica.de [89.14.109.72]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (prime256v1) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by hub1.goneo.de (Postfix) with ESMTPSA id 0DAE6240125; Thu, 4 Apr 2024 07:50:24 +0200 (CEST) Date: Thu, 4 Apr 2024 07:49:56 +0200 From: FreeBSD User To: FreeBSD CURRENT , freebsd-security@freebsd.org Subject: CVE-2024-3094: malicious code in xz 5.6.0 and xz 5.6.1 Message-ID: <20240404075023.3de63e28@thor.intern.walstatt.dynvpn.de> Organization: walstatt-de.de List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-UID: 9b3015 X-Rspamd-UID: 901608 X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.49 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.988]; R_SPF_ALLOW(-0.20)[+ip4:85.220.129.0/25]; R_DKIM_ALLOW(-0.20)[walstatt-de.de:s=DKIM001]; MIME_GOOD(-0.10)[text/plain]; TO_DN_SOME(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; MIME_TRACE(0.00)[0:+]; ARC_NA(0.00)[]; HAS_ORG_HEADER(0.00)[]; ASN(0.00)[asn:25394, ipnet:85.220.128.0/17, country:DE]; RCVD_TLS_ALL(0.00)[]; DMARC_NA(0.00)[walstatt-de.de]; RCPT_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; MISSING_XM_UA(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org,freebsd-security@freebsd.org]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[walstatt-de.de:+] X-Rspamd-Queue-Id: 4V99h94FYQz4Kl6 Hello, I just stumbled over this CVE regarding xz 5.6.0 and 5.6.1: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-3094 FreeBSD starting with 14-STABLE seems to use xz 5.6.0, but my limited skills do not allow me to judge wether the described exploit mechanism also works on FreeBSD. RedHat already sent out a warning, the workaround is to move back towards an older variant. I have to report to my superiors (we're using 14-STABLE and CURRENT and I do so in private), so I would like to welcome any comment on that. Thanks in advance, O. Hartmann -- O. Hartmann From nobody Thu Apr 4 06:03:56 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4V99zk1rbTz5GK2G for ; Thu, 4 Apr 2024 06:04:02 +0000 (UTC) (envelope-from paulf2718@gmail.com) Received: from mail-wm1-x32b.google.com (mail-wm1-x32b.google.com [IPv6:2a00:1450:4864:20::32b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4V99zh5WwSz4Nch for ; Thu, 4 Apr 2024 06:04:00 +0000 (UTC) (envelope-from paulf2718@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b=l2N9UznF; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of paulf2718@gmail.com designates 2a00:1450:4864:20::32b as permitted sender) smtp.mailfrom=paulf2718@gmail.com Received: by mail-wm1-x32b.google.com with SMTP id 5b1f17b1804b1-4162b7f18b6so264945e9.3 for ; Wed, 03 Apr 2024 23:04:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1712210639; x=1712815439; darn=freebsd.org; h=content-transfer-encoding:in-reply-to:from:content-language :references:to:subject:user-agent:mime-version:date:message-id:from :to:cc:subject:date:message-id:reply-to; bh=M0mG1Mb88BrdtQNB29XsbhTGd7sWNPn8QGH45ipGTtk=; b=l2N9UznFTK0x1bhNSobwPwN6M9vr305g2IiNEVbrLcWovqJcntfj6eUDcUk+VWICsl tpSpKEjeHZ4wjrLBI9znjOLoiWIeqvlQcYTq0swkmyiVizkLb4dGcux8D4biUpPsYEJn R1l+Nkn4tKgJd4X8UATUNllut8dIv/10JGuAYMJ5c/asq9oO9w8FBUG2B2AcDMq6bB+s VZLoin7tPsuRgegdLxDu+pyECyE+UJ1X3HEMYFrKAfWtk7NzsJIMUtkx59U7zGQY1Ljc BpuCmrD54sz7N//8eihS+Gvdc4uaIWeMRu/5eSo0HKgzzOAfZ9xCugw9P7nqyY4qD0hX T7+g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1712210639; x=1712815439; h=content-transfer-encoding:in-reply-to:from:content-language :references:to:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=M0mG1Mb88BrdtQNB29XsbhTGd7sWNPn8QGH45ipGTtk=; b=mZEMGGyrs66GlHxpA+/J0C5OfB9CD6f8iiFZJiWXNe5bTcJyxs9CdyGEkl+YsxdgYE +sWlemEaOU4Ee40UrTMjbLP536W8NZHc0YKeGH2E/dYkAQUHBdxr12LoUyl45Loyj0mK 7jZBHACGS+JEzvaAiQ+hFAjAZMOANhjtqpyqfrVguoHUF9ZwHMp4LajB3LDkW1EQWlxK /+VaOFPzmtXveXPIHLm0dKw35VsdQ+e+hoQBhjd/qD9lM3taMtYdVEVfmtTyRUWyZ0LR DgpKIu8jHlNFnGLL7eZq50mQG1hhy4GEjx3FHG6mJPG/o4oXITUWxIMWGBg/8JnBSUIN PZ/A== X-Gm-Message-State: AOJu0YyIYwSOWAHsXoUgYGaD48pDgonWUhyvlvoci0XO190xTCHUA4Bn FOGsqrJRvNzEsbnHlPcLqdimmj3z3zPCiUxiAu/nE1MCJmtj5Th4CBsGm/01 X-Google-Smtp-Source: AGHT+IEEiDqL6Oc9mOWsH90kyiyb2vqnJ4u+4NpNOcWoNP/HkNSBlvgIhT02bom6wd3XgUTH5yckuw== X-Received: by 2002:a5d:51cf:0:b0:343:9fec:eb35 with SMTP id n15-20020a5d51cf000000b003439feceb35mr1019106wrv.24.1712210638906; Wed, 03 Apr 2024 23:03:58 -0700 (PDT) Received: from ?IPV6:2a01:cb15:8010:2f00:1aa9:5ff:fe16:2efb? ([2a01:cb15:8010:2f00:1aa9:5ff:fe16:2efb]) by smtp.gmail.com with ESMTPSA id h9-20020adffa89000000b003435e1c0b78sm6703945wrr.28.2024.04.03.23.03.57 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 03 Apr 2024 23:03:58 -0700 (PDT) Message-ID: <5e546bba-7d06-452b-ad8c-76555e1b1c14@gmail.com> Date: Thu, 4 Apr 2024 06:03:56 +0000 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: CVE-2024-3094: malicious code in xz 5.6.0 and xz 5.6.1 To: freebsd-current@freebsd.org References: <20240404075023.3de63e28@thor.intern.walstatt.dynvpn.de> Content-Language: en-US From: Paul Floyd In-Reply-To: <20240404075023.3de63e28@thor.intern.walstatt.dynvpn.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.73 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.74)[-0.739]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; MIME_GOOD(-0.10)[text/plain]; XM_UA_NO_VERSION(0.01)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; RCPT_COUNT_ONE(0.00)[1]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; TO_DN_NONE(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::32b:from] X-Rspamd-Queue-Id: 4V99zh5WwSz4Nch On 04-04-24 05:49, FreeBSD User wrote: > Hello, > > I just stumbled over this CVE regarding xz 5.6.0 and 5.6.1: > > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-3094 > > FreeBSD starting with 14-STABLE seems to use xz 5.6.0, but my limited skills do not allow me > to judge whether the described exploit mechanism also works on FreeBSD. > RedHat already sent out a warning, the workaround is to move back towards an older variant. > > I have to report to my superiors (we're using 14-STABLE and CURRENT and I do so in private), > so I would like to welcome any comment on that. No it does not affect FreeBSD. The autoconf script checks that it is running in a RedHat or Debian package build environment before trying to proceed. There are also checks for GCC and binutils ld.bfd. And I'm not sure that the payload (a precompiled Linux object file) would work with FreeBSD and /lib/libelf.so.2. See https://gist.github.com/thesamesam/223949d5a074ebc3dce9ee78baad9e27 A+ Paul From nobody Thu Apr 4 06:06:26 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4V9B2d5XhNz5GKYj for ; Thu, 4 Apr 2024 06:06:33 +0000 (UTC) (envelope-from sthaug@nethelp.no) Received: from bizet.nethelp.no (bizet.nethelp.no [195.1.209.4]) by mx1.freebsd.org (Postfix) with ESMTP id 4V9B2c75GRz4PjD for ; Thu, 4 Apr 2024 06:06:32 +0000 (UTC) (envelope-from sthaug@nethelp.no) Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of sthaug@nethelp.no designates 195.1.209.4 as permitted sender) smtp.mailfrom=sthaug@nethelp.no Received: from localhost (bizet.nethelp.no [195.1.209.4]) by bizet.nethelp.no (Postfix) with ESMTP id 619C6646B02 for ; Thu, 4 Apr 2024 08:06:26 +0200 (CEST) Date: Thu, 04 Apr 2024 08:06:26 +0200 (CEST) Message-Id: <20240404.080626.2156450008475679449.sthaug@nethelp.no> To: freebsd-current@freebsd.org Subject: Re: CVE-2024-3094: malicious code in xz 5.6.0 and xz 5.6.1 From: sthaug@nethelp.no In-Reply-To: <5e546bba-7d06-452b-ad8c-76555e1b1c14@gmail.com> References: <20240404075023.3de63e28@thor.intern.walstatt.dynvpn.de> <5e546bba-7d06-452b-ad8c-76555e1b1c14@gmail.com> X-Mailer: Mew version 6.9 on Emacs 29.2 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spamd-Bar: - X-Spamd-Result: default: False [-1.26 / 15.00]; MID_CONTAINS_FROM(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-0.97)[-0.969]; NEURAL_HAM_SHORT(-0.69)[-0.688]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+mx]; RCVD_NO_TLS_LAST(0.10)[]; MIME_GOOD(-0.10)[text/plain]; ONCE_RECEIVED(0.10)[]; RCVD_COUNT_ONE(0.00)[1]; RCPT_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:2116, ipnet:195.1.0.0/16, country:NO]; FROM_NO_DN(0.00)[]; MIME_TRACE(0.00)[0:+]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[nethelp.no]; ARC_NA(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; R_DKIM_NA(0.00)[] X-Rspamd-Queue-Id: 4V9B2c75GRz4PjD >> I have to report to my superiors (we're using 14-STABLE and CURRENT >> and I do so in private), >> so I would like to welcome any comment on that. > > No it does not affect FreeBSD. > > The autoconf script checks that it is running in a RedHat or Debian > package build environment before trying to proceed. There are also > checks for GCC and binutils ld.bfd. And I'm not sure that the payload > (a precompiled Linux object file) would work with FreeBSD and > /lib/libelf.so.2. > > See > > https://gist.github.com/thesamesam/223949d5a074ebc3dce9ee78baad9e27 See also the following message from the FreeBSD security officer: https://lists.freebsd.org/archives/freebsd-security/2024-March/000248.html Steinar Haug, Nethelp consulting, sthaug@nethelp.no From nobody Thu Apr 4 06:13:02 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4V9BBr6BR9z5GLDg for ; Thu, 4 Apr 2024 06:13:40 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Received: from smtp052.goneo.de (smtp5.goneo.de [IPv6:2001:1640:5::8:30]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4V9BBr48jkz4R7J for ; Thu, 4 Apr 2024 06:13:40 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Authentication-Results: mx1.freebsd.org; none Received: from hub1.goneo.de (hub1.goneo.de [85.220.129.52]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by smtp5.goneo.de (Postfix) with ESMTPS id BC3FC2407F8; Thu, 4 Apr 2024 08:13:36 +0200 (CEST) Received: from hub1.goneo.de (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by hub1.goneo.de (Postfix) with ESMTPS id 9A7B9240252; Thu, 4 Apr 2024 08:13:30 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=walstatt-de.de; s=DKIM001; t=1712211210; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=3Ye56w9Mg/Hfwp3hH1ibP2onBvboYMDN7aQT7QEOjHE=; b=LFrdEIjwQ54/GwT0CG5Zyz+iRbjTZ1YUupkcYKgtsXRZNGeouy0FqLZ9QMSv85uIxEOvQC HEJuBaL3Qymu/XMuIYFD9QYclLpxtJUh5HbAQHAADLfL6ejQHRgZN6SlDGFLvR7nqBpQ/8 8kJXlNQ3wgOY7IgiQ4Q7xGUU/600yVEw8R40+FqrhQWYResnOQEB2Ymi3oScTmOA0F2Q3E M+tYTF56/mH7eTEPKICoDJspcYxUZJV0xuhkGJPu+u3A+FscuyS+51vAMEQ29e3rFvSL2Y ZvYWf/TSRkGr+LWGmPEVrcZlgdUd44xRZvUR6oq2HYA+n8+BrzeH1BGlTLmo7w== Received: from thor.intern.walstatt.dynvpn.de (dynamic-089-014-109-072.89.14.pool.telefonica.de [89.14.109.72]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (prime256v1) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by hub1.goneo.de (Postfix) with ESMTPSA id 5CA3C24012F; Thu, 4 Apr 2024 08:13:30 +0200 (CEST) Date: Thu, 4 Apr 2024 08:13:02 +0200 From: FreeBSD User To: sthaug@nethelp.no Cc: freebsd-current@freebsd.org Subject: Re: CVE-2024-3094: malicious code in xz 5.6.0 and xz 5.6.1 Message-ID: <20240404081329.5fa28101@thor.intern.walstatt.dynvpn.de> In-Reply-To: <20240404.080626.2156450008475679449.sthaug@nethelp.no> References: <20240404075023.3de63e28@thor.intern.walstatt.dynvpn.de> <5e546bba-7d06-452b-ad8c-76555e1b1c14@gmail.com> <20240404.080626.2156450008475679449.sthaug@nethelp.no> Organization: walstatt-de.de List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-UID: 3b35b4 X-Rspamd-UID: 8d8e70 X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:25394, ipnet:2001:1640::/32, country:DE] X-Rspamd-Queue-Id: 4V9BBr48jkz4R7J Am Thu, 04 Apr 2024 08:06:26 +0200 (CEST) sthaug@nethelp.no schrieb: > >> I have to report to my superiors (we're using 14-STABLE and CURRENT > >> and I do so in private), > >> so I would like to welcome any comment on that. > > > > No it does not affect FreeBSD. > > > > The autoconf script checks that it is running in a RedHat or Debian > > package build environment before trying to proceed. There are also > > checks for GCC and binutils ld.bfd. And I'm not sure that the payload > > (a precompiled Linux object file) would work with FreeBSD and > > /lib/libelf.so.2. > > > > See > > > > https://gist.github.com/thesamesam/223949d5a074ebc3dce9ee78baad9e27 > > See also the following message from the FreeBSD security officer: > > https://lists.freebsd.org/archives/freebsd-security/2024-March/000248.html > > Steinar Haug, Nethelp consulting, sthaug@nethelp.no > Thank you very much for the quick answer. Kind regards oh -- O. Hartmann From nobody Thu Apr 4 06:14:52 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4V9BDH1f7Lz5GLH2; Thu, 4 Apr 2024 06:14:55 +0000 (UTC) (envelope-from kevans@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4V9BDH1CHpz4SQw; Thu, 4 Apr 2024 06:14:55 +0000 (UTC) (envelope-from kevans@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1712211295; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=vsQas0ZHgZYfVcyZBHrVjnoVivY4PBOeHOQ2tit1fYI=; b=gDKiyW2Q0PLMCTs9wWbya2xObgiCJs2hJoYCMXrRlCIEoJk3L8vTA1VKDAPxw0RlACV0X+ Bm/BYAR9eABABEBjIoWsuGdM1OB5W0zysV+bljQrFayAsgaR7lyo7S7+YC5wy+CxLfUJIs izRV+UGGRSBobSjXJyAzDo4thsVhHUtM+xeTC7nG6YinEp3tXJmST4cM6OGBjHQlVnAfey /b6xeZzfIwiS+HyMfuSxeZ77djb7ivp5ejZBZEc0nHYIrZHhdb/VVWVLDxv7xbKBHw3t90 9HwigcFPW4P/h7cy4tlEINY5L1BoNp/lu0M59+8bjF9v9pE1NObwEeEOWMOA8g== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1712211295; a=rsa-sha256; cv=none; b=NSO8mtsGa4+++ov8VuJudqV5Mm0LQBMr/QHNiupXEpa78ONUYGc7ugKZD9A8xEaCbXjppu PEGcyDvQOt1+V2OrtE+VxrKNLk55WGKZomnspRIiu6MVnq1uPVD19N+dDrmnxvBoF2s2lk 5W6JuV88Wq8FEMHSkIE/pDkr1NA5qEfrt3xCMPDNkKGaADyspOxFFPXAZrZK3G5mngrJDq 2IAQIJ4rMMy6rEd36WRmWhCt+zW5SQ1U5zBZWmxR64QR9G7esUQSqMtafvIV7HY3K8Quyu VHNxre44GTsIueRP7nuBgwycUg1EprAhGSwXVAWpd37aJHizD4+diNpmKYBq6A== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1712211295; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=vsQas0ZHgZYfVcyZBHrVjnoVivY4PBOeHOQ2tit1fYI=; b=mKNd6gBhjjuPXvkUlzDNuHZDlItCIPun6wHYPTH9gxigvFN6Fr7xY+UnjIuMBJO1i0UXDA nvnB6Fu2pnPywgtMIIJoVnkKX7Ge3/ZU8hX5RYQWZcyIJ0fdVA6J3Q3D+qmmxvMCLGPl+d /H7GeDVhLcrW4KE0LQkoqSmHv4wpEt7iJB0GxEJaGQXy+wdXwrNUUj/9d8x+yxCjAdizl0 YAeJXVDecKg16hpOsQYX1q6n765qkh3rpppkOcPO726PmKaSck/WROprk3gxjRLbUF91gp KNxG3/F0waWsJ4pqHTcqqowIMUGo4f4uhrkyx4bdaKtcP3r92ZljAuKD5O8c6A== Received: from [10.9.4.95] (unknown [209.182.120.176]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: kevans/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4V9BDG4SHlzGqf; Thu, 4 Apr 2024 06:14:54 +0000 (UTC) (envelope-from kevans@FreeBSD.org) Message-ID: Date: Thu, 4 Apr 2024 01:14:52 -0500 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: CVE-2024-3094: malicious code in xz 5.6.0 and xz 5.6.1 Content-Language: en-US To: FreeBSD User , FreeBSD CURRENT , freebsd-security@freebsd.org References: <20240404075023.3de63e28@thor.intern.walstatt.dynvpn.de> From: Kyle Evans In-Reply-To: <20240404075023.3de63e28@thor.intern.walstatt.dynvpn.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 4/4/24 00:49, FreeBSD User wrote: > Hello, > > I just stumbled over this CVE regarding xz 5.6.0 and 5.6.1: > > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-3094 > > FreeBSD starting with 14-STABLE seems to use xz 5.6.0, but my limited skills do not allow me > to judge wether the described exploit mechanism also works on FreeBSD. > RedHat already sent out a warning, the workaround is to move back towards an older variant. > > I have to report to my superiors (we're using 14-STABLE and CURRENT and I do so in private), > so I would like to welcome any comment on that. > > Thanks in advance, > > O. Hartmann > > See so@'s answer from a couple days ago: https://lists.freebsd.org/archives/freebsd-security/2024-March/000248.html TL;DR no Thanks, Kyle Evans From nobody Thu Apr 4 06:56:28 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4V9C8D3VFxz5GQ4V; Thu, 4 Apr 2024 06:56:28 +0000 (UTC) (envelope-from dutchdaemon@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4V9C8D0M0Yz4Y6K; Thu, 4 Apr 2024 06:56:28 +0000 (UTC) (envelope-from dutchdaemon@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1712213788; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=88KylaqmFSyh5SHHTng26zPhjOWdw5yzCuqGz2ERNNE=; b=RBSHNxTqbi0W18xt6SLQfr04GRVTJ+Lufw1Cn+MCI0ptVsTu8kJW809O/FEnxYPlZuSyfc RoBPZ/zsbr1WNQVKJq1IXHgm7wEYh6D3rue92IajyFUe4hNZpchwtIo27VOUGiLYyIY4AX hUScfXjx6zw/SLhV3SNBvmOYv7gRZjrrfUDjWoSpiVyVkSyZUmdYDHPslnOjboXwTUTJ0m s5bxgwGik9ZG1wANW3pY2969r0NW/x1NNmzuIuR2B94FsyKPPERi+DGsqlQ3Pj/La12ysE EbjXEOEOqUY8N1qcKee53yrCXhQiLhjMzhnjF024T+iDjnAiC31Cgq8KVE0+Ow== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1712213788; a=rsa-sha256; cv=none; b=uNhReUXDR1ElV7NSLZpHMxxMuMzU6/CIHuR0b8Osb3UuxEQcnHjGnXoGzTaBZSx0xsBMVO iL4VSpiwOFI1gyRil2Eh2Hv1wJ9TYNSJDsXUXhbVSWLOjKiMFkW7RvHHCb8aOEDK60H4Qm 2alN4rLZqElAZWxcx/1nGgW84sHr9y3KUpxx6u8gcFgcqMdf+tRzV+CwFzhb0x1tFXHMRd 2uv+zwie9L0S9Vz/FX5SWvjOL8r2zEMcMIp2c5/7vR+GbZQfXQpn+GjX4NGYa0WhA+tIh8 12IW12LbacyLtCC5vsz7E5GgUtp3LNGUObwwFLQa2jL1Dw7t4AjnB0LANWp5rw== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1712213788; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=88KylaqmFSyh5SHHTng26zPhjOWdw5yzCuqGz2ERNNE=; b=HOzwLOGw3YXCefwpMp90dohdKOFIU+qXNZXcLLcKod7eiPydFH9BprPTPRQyCKrFXE3ZAg KzOTC6YRv9mnDG73aLtyF+HhBSSJXRCMYpfJXDwbJ4/6AdgKPteb6TfNk1MwES1kYWheN5 BrsKQuWoS912w0SfqlF13sB51y/3UU75z9wZZik3OSEs4Ej1BSUnuHm4bdgwRnpELxc5mm eeMVLlnSJHB+hPUtiqnDY0znSfz4L+KgFSZ0CxkDdfQn/YRZuS7q70uoGpLfHN7EF0nYPY 9OxFzJHuL4H/JqkxdC4c/e/01QedNTqHU5WfKTk4snYo/d7yvQ5znY20MfwWyQ== Received: from [192.168.178.229] (unknown [85.148.89.7]) (using TLSv1.2 with cipher ECDHE-RSA-CHACHA20-POLY1305 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: dutchdaemon/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4V9C8C3NWtzHWZ; Thu, 4 Apr 2024 06:56:27 +0000 (UTC) (envelope-from dutchdaemon@freebsd.org) From: "Ben C. O. Grimm" To: FreeBSD User , FreeBSD CURRENT , Date: Thu, 04 Apr 2024 08:56:28 +0200 Message-ID: <18ea7b425a8.2892.b36d34a15fda208b80f54b6ad54d9e04@freebsd.org> In-Reply-To: <20240404075023.3de63e28@thor.intern.walstatt.dynvpn.de> References: <20240404075023.3de63e28@thor.intern.walstatt.dynvpn.de> User-Agent: AquaMail/1.50.0 (build: 105000429) Subject: Re: CVE-2024-3094: malicious code in xz 5.6.0 and xz 5.6.1 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="18ea7e50659271f2892388edc8" This is a multi-part message in MIME format. --18ea7e50659271f2892388edc8 Content-Type: text/plain; format=flowed; charset="us-ascii" Content-Transfer-Encoding: 8bit On April 4, 2024 07:50:55 FreeBSD User wrote: > Hello, > > I just stumbled over this CVE regarding xz 5.6.0 and 5.6.1: > > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-3094 > > FreeBSD starting with 14-STABLE seems to use xz 5.6.0, but my limited > skills do not allow me > to judge wether the described exploit mechanism also works on FreeBSD. > RedHat already sent out a warning, the workaround is to move back towards > an older variant. > > I have to report to my superiors (we're using 14-STABLE and CURRENT and I > do so in private), > so I would like to welcome any comment on that. > > Thanks in advance, > > O. Hartmann > > > -- > O. Hartmann As noted on freebsd-security last Friday: FreeBSD is not affected by the recently announced backdoor included in the 5.6.0 and 5.6.1 xz releases. All supported FreeBSD releases include versions of xz that predate the affected releases. The main, stable/14, and stable/13 branches do include the affected version (5.6.0), but the backdoor components were excluded from the vendor import. Additionally, FreeBSD does not use the upstream's build tooling, which was a required part of the attack. Lastly, the attack specifically targeted x86_64 Linux systems using glibc. --18ea7e50659271f2892388edc8 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

On April 4, 2024 07:50:55 FreeBSD User <freebsd@walsta= tt-de.de> wrote:

Hello,

I just stumbled over this CVE regarding xz 5.6.0 and 5.6.= 1:

https://cve.mitre.org/cgi-bin/cvename.cgi?name=3DCVE-2024= -3094

FreeBSD starting with 14-STABLE seems to use xz 5.6.0, bu= t my limited skills do not allow me
to judge wether the described exploit mechanism also work= s on FreeBSD.
RedHat already sent out a warning, the workaround is to m= ove back towards an older variant.

I have to report to my superiors (we're using 14-STABLE a= nd CURRENT and I do so in private),
so I would like to welcome any comment on that.

Thanks in advance,

O. Hartmann


-- 
O. Hartmann
As noted on freebsd-security last Friday: 

FreeBSD is not affected by = the recently announced backdoor included in the 5.6.0 and 5.6.1 xz releases= .



All supported FreeBSD releases include ve= rsions of xz that predate the affected releases.


The main, stable/14, and stable/13 branches do include the affected v= ersion (5.6.0), but the backdoor components were excluded from the vendor i= mport. Additionally, FreeBSD does not use the upstream's build tooling, whi= ch was a required part of the attack. Lastly, the attack specifically targe= ted x86_64 Linux systems using glibc.
--18ea7e50659271f2892388edc8-- From nobody Sat Apr 6 07:05:00 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4VBRFw6S6hz5FyYy; Sat, 6 Apr 2024 07:05:40 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Received: from smtp6.goneo.de (smtp6.goneo.de [IPv6:2001:1640:5::8:31]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4VBRFv3BBdz4stC; Sat, 6 Apr 2024 07:05:39 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=walstatt-de.de header.s=DKIM001 header.b=e1+qhwd8; dmarc=none; spf=pass (mx1.freebsd.org: domain of freebsd@walstatt-de.de designates 2001:1640:5::8:31 as permitted sender) smtp.mailfrom=freebsd@walstatt-de.de Received: from hub2.goneo.de (hub2.goneo.de [85.220.129.53]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by smtp6.goneo.de (Postfix) with ESMTPS id 56B52240618; Sat, 6 Apr 2024 09:05:30 +0200 (CEST) Received: from hub2.goneo.de (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by hub2.goneo.de (Postfix) with ESMTPS id BC534240308; Sat, 6 Apr 2024 09:05:28 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=walstatt-de.de; s=DKIM001; t=1712387128; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=ej74G6FvrtOt0g+wA7QTymQywdbOnqXuy0Kfy5AznQk=; b=e1+qhwd8gEpz6QHEQERBQpeaJwutTXeSsGfrFGzfWXzf4dof5Z+wfoF8BdCQjTsnOr8aNh G7LXVO1Q3qXBFLalBW8+gyPfk2SjKXP4Ib0+aX36Q0q1KICZBPitmwcZb1igeLWh/IPjs/ yBsJ3GDQik8yxvH/DQ21/7cFbD7xci8krVhBR11qgfRkDlCd4vvnuhG/YFJJIceZoLMltH d67eogA8EOd5KcEj7ZuXenWylo2M8krB+CEROVHhGhU6kRTHZ6firIVfQjkDyTVzlWyGcK FDGX7unqzlzl3WYeWP+rIIxGMakjIzMynmrWo4nG+q2Mg1xhjDcZob3QN/li5A== Received: from thor.intern.walstatt.dynvpn.de (dynamic-078-055-133-175.78.55.pool.telefonica.de [78.55.133.175]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (prime256v1) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by hub2.goneo.de (Postfix) with ESMTPSA id 8E0A124030E; Sat, 6 Apr 2024 09:05:28 +0200 (CEST) Date: Sat, 6 Apr 2024 09:05:00 +0200 From: FreeBSD User To: FreeBSD Ports , FreeBSD CURRENT Subject: pkg-1.21.0: after upgrade 1.20.9_1 -> 1.21.0: pkg core dumps on specific ports Message-ID: <20240406090527.34d84eb9@thor.intern.walstatt.dynvpn.de> Organization: walstatt-de.de List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-UID: 916045 X-Rspamd-UID: a2f6f9 X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.50 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.998]; R_SPF_ALLOW(-0.20)[+ip6:2001:1640:5::8:0/112]; R_DKIM_ALLOW(-0.20)[walstatt-de.de:s=DKIM001]; MIME_GOOD(-0.10)[text/plain]; ASN(0.00)[asn:25394, ipnet:2001:1640::/32, country:DE]; MISSING_XM_UA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; HAS_ORG_HEADER(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org,freebsd-ports@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; DMARC_NA(0.00)[walstatt-de.de]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[walstatt-de.de:+] X-Rspamd-Queue-Id: 4VBRFv3BBdz4stC Hello, after updating (portmaster and make) ports-mgmt/ports from 1.20.9_1 -> 1.21.0 on CURRENT and 14-STABLE, I can't update several ports: www/apache24 databases/redis pkg core dumps while performing installation. apache24 and redis are ports I realized this misbehaviour on ALL 14-STABLE and CURRENT boxes (both OS variants latest builds, i.e. FreeBSD 15.0-CURRENT #32 main-n269135-da2b732288c7: Fri Apr 5 20:30:39 CEST 2024 amd64). After some updates on a poudriere builder (CURRENT base host, 14.0-RELENG jail with poudriere) building packages for 14.0-RELENG, I observed the same behaviour when updating packages on target hosts where pkg is first updated, on those hosts, nextcloud-server and icinga2 host utilizing also databases/redis and www/apache24, pkg fails the same way. I do not dare to update our poudriere hosts since the problem seems to pop up when pkg 1.21.0 is installed, no matter whether I use poudriere built ports (from our own builder hosts) or recent source tree with portmaster/make build process. Looks like a serious bug to me and not a site/user specific problem. Hopefully others do realize the same ... Thanks in advance, oh -- O. Hartmann From nobody Sat Apr 6 07:23:30 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4VBRfj1ytQz5G1tr; Sat, 6 Apr 2024 07:23:41 +0000 (UTC) (envelope-from rhurlin@gwdg.de) Received: from mx-2023-1.gwdg.de (mx-2023-1.gwdg.de [134.76.10.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4VBRfh5Xybz3xRj; Sat, 6 Apr 2024 07:23:40 +0000 (UTC) (envelope-from rhurlin@gwdg.de) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gwdg.de; s=2023-rsa; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:From:CC: References:To:Subject:MIME-Version:Date:Message-ID:Sender:Reply-To:Content-ID :Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To: Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe :List-Post:List-Owner:List-Archive; bh=557QFH0CT6dpH82Xkrw8fqZBhVqGxxFl8gUoS8Uxq98=; b=daLgW+IWVnhB0ivFn0z27u+qWL RqEp/os8xvk86r71qp6i/k1oZ+FtGv6SR7vSLotPhEAPEw53ed7/IBlSeM6DXA3bZJrGIhPV7VNyR Wa/fERIIsYpLVu+E3/mcT62Zakp80ghuxeI2QhfAMNB/gbt4ufC6Wdljto0rdsKUhzuKSqPfRNp+P 3km0bdyCVgbhzUaoRcUCkczHidFKasy64680mbIV6aVkWbCtBtiHJd1eL5CSCq80D8LEQUOujdGVH kbOu1OmyEYc+7iIfPQEpfpB12Z9KdCgD3abBMOyonJcp/hMsm+tG8ORk+aIluR6aB2du+6PgE3m90 botTfqdQ==; Received: from xmailer.gwdg.de ([134.76.10.29]:54668) by mailer.gwdg.de with esmtp (GWDG Mailer) (envelope-from ) id 1rt0Oh-006nGb-2g; Sat, 06 Apr 2024 09:23:31 +0200 Received: from mbx19-gwd-03.um.gwdg.de ([10.108.142.56] helo=email.gwdg.de) by mailer.gwdg.de with esmtps (TLS1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (GWDG Mailer) (envelope-from ) id 1rt0Oh-0006dI-1u; Sat, 06 Apr 2024 09:23:31 +0200 Received: from [192.168.178.23] (10.250.9.199) by MBX19-GWD-03.um.gwdg.de (10.108.142.56) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256) id 15.2.1544.9; Sat, 6 Apr 2024 09:23:31 +0200 Message-ID: Date: Sat, 6 Apr 2024 09:23:30 +0200 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: pkg-1.21.0: after upgrade 1.20.9_1 -> 1.21.0: pkg core dumps on specific ports Content-Language: en-US To: FreeBSD User References: <20240406090527.34d84eb9@thor.intern.walstatt.dynvpn.de> CC: FreeBSD Ports , FreeBSD CURRENT From: Rainer Hurling In-Reply-To: <20240406090527.34d84eb9@thor.intern.walstatt.dynvpn.de> Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [10.250.9.199] X-ClientProxiedBy: EXCMBX-13.um.gwdg.de (134.76.9.222) To MBX19-GWD-03.um.gwdg.de (10.108.142.56) X-Virus-Scanned: (clean) by clamav X-Spam-Level: - X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:207592, ipnet:134.76.0.0/16, country:DE] X-Rspamd-Queue-Id: 4VBRfh5Xybz3xRj Am 06.04.24 um 09:05 schrieb FreeBSD User: > Hello, > > after updating (portmaster and make) ports-mgmt/ports from 1.20.9_1 -> 1.21.0 on CURRENT and > 14-STABLE, I can't update several ports: > > www/apache24 > databases/redis > > pkg core dumps while performing installation. apache24 and redis are ports I realized this > misbehaviour on ALL 14-STABLE and CURRENT boxes (both OS variants latest builds, i.e. FreeBSD > 15.0-CURRENT #32 main-n269135-da2b732288c7: Fri Apr 5 20:30:39 CEST 2024 amd64). > > After some updates on a poudriere builder (CURRENT base host, 14.0-RELENG jail with poudriere) > building packages for 14.0-RELENG, I observed the same behaviour when updating packages on > target hosts where pkg is first updated, on those hosts, nextcloud-server and icinga2 host > utilizing also databases/redis and www/apache24, pkg fails the same way. > > I do not dare to update our poudriere hosts since the problem seems to pop up when pkg 1.21.0 > is installed, no matter whether I use poudriere built ports (from our own builder hosts) or > recent source tree with portmaster/make build process. > > Looks like a serious bug to me and not a site/user specific problem. Hopefully others do > realize the same ... > > Thanks in advance, > > oh Hmm, I just tried to reproduce that. Both ports mentioned, databases/redis and www/apache24, can be built and installed with Portmaster. The box is a 15.0-CURRENT with pkg-1.21.0. Maybe 'pkg check -Bn' or 'portmaster --check-depends --check-port-dbdir' show some inconsistencies? Best wishes, Rainer From nobody Sat Apr 6 07:23:49 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4VBRgW5z10z5G2NP; Sat, 6 Apr 2024 07:24:23 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Received: from smtp052.goneo.de (smtp5.goneo.de [IPv6:2001:1640:5::8:30]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4VBRgV3b2Jz40fH; Sat, 6 Apr 2024 07:24:22 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=walstatt-de.de header.s=DKIM001 header.b=baOgqfYx; dmarc=none; spf=pass (mx1.freebsd.org: domain of freebsd@walstatt-de.de designates 2001:1640:5::8:30 as permitted sender) smtp.mailfrom=freebsd@walstatt-de.de Received: from hub1.goneo.de (hub1.goneo.de [85.220.129.52]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by smtp5.goneo.de (Postfix) with ESMTPS id 6B38F2403CA; Sat, 6 Apr 2024 09:24:19 +0200 (CEST) Received: from hub1.goneo.de (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by hub1.goneo.de (Postfix) with ESMTPS id 82763240030; Sat, 6 Apr 2024 09:24:17 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=walstatt-de.de; s=DKIM001; t=1712388257; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=XmoRyyCxmqbUHDleMS1G8qJdO+xQ5Z3+OcR5zp98Xzs=; b=baOgqfYxLyv7dqvrXjHtOIi+lWUq5SfcPxKWmpRRHwzDDlfpNMa+OGN34DgR5Mp2BuLAEO dMj5u7cJz7LMVVOPT6o4bKuKR7RkYQ2jqKEEwEQW8ENGFnOg5MPruhV3u5KvRDgLQ36nrQ OYOEIy0C5ZHHDL61vK7ZdPrbujzEPUkbB70GrHgRAn43oaYty0YeiRuwbg3uJVe6MY2LIv ihQBFAbZk6UqH9BC6wMMWa8LUBHqVGUZ5MLa/8sRNYhY5kWDXdxG8ZzjxJsKIDt0tUFTl1 TSsvc7BsdRzSxyJ1QHQOpIeP1PLii7sWQvwSTAy0wzjxxwfTBzevSOon4sJRSw== Received: from thor.intern.walstatt.dynvpn.de (dynamic-078-055-133-175.78.55.pool.telefonica.de [78.55.133.175]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (prime256v1) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by hub1.goneo.de (Postfix) with ESMTPSA id 4531A240124; Sat, 6 Apr 2024 09:24:17 +0200 (CEST) Date: Sat, 6 Apr 2024 09:23:49 +0200 From: FreeBSD User To: Kyle Evans Cc: FreeBSD CURRENT , freebsd-security@freebsd.org Subject: Re: CVE-2024-3094: malicious code in xz 5.6.0 and xz 5.6.1 Message-ID: <20240406092416.046598fb@thor.intern.walstatt.dynvpn.de> In-Reply-To: References: <20240404075023.3de63e28@thor.intern.walstatt.dynvpn.de> Organization: walstatt-de.de List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-UID: c693f9 X-Rspamd-UID: d82f0e X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.60 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.997]; R_SPF_ALLOW(-0.20)[+ip6:2001:1640:5::8:0/112]; R_DKIM_ALLOW(-0.20)[walstatt-de.de:s=DKIM001]; RCVD_IN_DNSWL_LOW(-0.10)[2001:1640:5::8:30:from]; MIME_GOOD(-0.10)[text/plain]; ASN(0.00)[asn:25394, ipnet:2001:1640::/32, country:DE]; ARC_NA(0.00)[]; TO_DN_SOME(0.00)[]; HAS_ORG_HEADER(0.00)[]; MISSING_XM_UA(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_TLS_ALL(0.00)[]; DMARC_NA(0.00)[walstatt-de.de]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org,freebsd-security@freebsd.org]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[walstatt-de.de:+] X-Rspamd-Queue-Id: 4VBRgV3b2Jz40fH Am Thu, 4 Apr 2024 01:14:52 -0500 Kyle Evans schrieb: > On 4/4/24 00:49, FreeBSD User wrote: > > Hello, > > > > I just stumbled over this CVE regarding xz 5.6.0 and 5.6.1: > > > > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-3094 > > > > FreeBSD starting with 14-STABLE seems to use xz 5.6.0, but my limited skills do not allow > > me to judge wether the described exploit mechanism also works on FreeBSD. > > RedHat already sent out a warning, the workaround is to move back towards an older variant. > > > > I have to report to my superiors (we're using 14-STABLE and CURRENT and I do so in > > private), so I would like to welcome any comment on that. > > > > Thanks in advance, > > > > O. Hartmann > > > > > > See so@'s answer from a couple days ago: > > https://lists.freebsd.org/archives/freebsd-security/2024-March/000248.html > > TL;DR no > > Thanks, > > Kyle Evans Thank you very much. Kind regards, oh -- O. Hartmann From nobody Sat Apr 6 07:56:25 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4VBSPC4HRYz5G4fw; Sat, 6 Apr 2024 07:57:03 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Received: from smtp052.goneo.de (smtp052.goneo.de [85.220.129.60]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4VBSPC1qsmz44hd; Sat, 6 Apr 2024 07:57:03 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Authentication-Results: mx1.freebsd.org; none Received: from hub1.goneo.de (hub1.goneo.de [85.220.129.52]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by smtp5.goneo.de (Postfix) with ESMTPS id 69613240AD8; Sat, 6 Apr 2024 09:56:55 +0200 (CEST) Received: from hub1.goneo.de (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by hub1.goneo.de (Postfix) with ESMTPS id CC76D2404DE; Sat, 6 Apr 2024 09:56:53 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=walstatt-de.de; s=DKIM001; t=1712390213; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=ciQ48PPyvBECWhfZLu8eIYUQ1ZAWCti6fUFCOufemYA=; b=mDDAGgVVk0l99ZMsuR70b1SdxnrAom/zBTEDhsU7moWp1x1s3h/oCxH8by+30wsZPHD+zj SdoWGeTN6xzlwCwfnR/iYzaaqlZ28k8kXyCiGM+/s9Iv++lUsZjMZcK3Ij4E5vVAt96uiN dEHc9P9pR1VS0Oyi0CnIpm8bS32faE+7hS+AHs6unUx4bUzKOQNKA2r0KSm9Uy8N27eUDx lfrYBiB/V7JFFN6+AUzAcLdDxNDVP52CVUT9esWaPyryrG1wTEx7DXN3mWEHfGWXZ66qMh 0u5ga8xFijLuiIzuyokquzOMu8ua8SiKmLZ0vN5E5OPbpGQEOGTk+xYwP32NmA== Received: from thor.intern.walstatt.dynvpn.de (dynamic-078-055-133-175.78.55.pool.telefonica.de [78.55.133.175]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (prime256v1) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by hub1.goneo.de (Postfix) with ESMTPSA id 96AB4240252; Sat, 6 Apr 2024 09:56:53 +0200 (CEST) Date: Sat, 6 Apr 2024 09:56:25 +0200 From: FreeBSD User To: Rainer Hurling Cc: FreeBSD Ports , FreeBSD CURRENT Subject: Re: pkg-1.21.0: after upgrade 1.20.9_1 -> 1.21.0: pkg core dumps on specific ports Message-ID: <20240406095652.1a5f7acb@thor.intern.walstatt.dynvpn.de> In-Reply-To: References: <20240406090527.34d84eb9@thor.intern.walstatt.dynvpn.de> Organization: walstatt-de.de List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-UID: c460b4 X-Rspamd-UID: 5d670a X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:25394, ipnet:85.220.128.0/17, country:DE] X-Rspamd-Queue-Id: 4VBSPC1qsmz44hd Am Sat, 6 Apr 2024 09:23:30 +0200 Rainer Hurling schrieb: > Am 06.04.24 um 09:05 schrieb FreeBSD User: > > Hello, > > > > after updating (portmaster and make) ports-mgmt/ports from 1.20.9_1 -> 1.21.0 on CURRENT > > and 14-STABLE, I can't update several ports: > > > > www/apache24 > > databases/redis > > > > pkg core dumps while performing installation. apache24 and redis are ports I realized this > > misbehaviour on ALL 14-STABLE and CURRENT boxes (both OS variants latest builds, i.e. > > FreeBSD 15.0-CURRENT #32 main-n269135-da2b732288c7: Fri Apr 5 20:30:39 CEST 2024 amd64). > > > > After some updates on a poudriere builder (CURRENT base host, 14.0-RELENG jail with > > poudriere) building packages for 14.0-RELENG, I observed the same behaviour when updating > > packages on target hosts where pkg is first updated, on those hosts, nextcloud-server and > > icinga2 host utilizing also databases/redis and www/apache24, pkg fails the same way. > > > > I do not dare to update our poudriere hosts since the problem seems to pop up when pkg > > 1.21.0 is installed, no matter whether I use poudriere built ports (from our own builder > > hosts) or recent source tree with portmaster/make build process. > > > > Looks like a serious bug to me and not a site/user specific problem. Hopefully others do > > realize the same ... > > > > Thanks in advance, > > > > oh > > > Hmm, I just tried to reproduce that. Both ports mentioned, > databases/redis and www/apache24, can be built and installed with > Portmaster. The box is a 15.0-CURRENT with pkg-1.21.0. > > Maybe 'pkg check -Bn' or 'portmaster --check-depends --check-port-dbdir' > show some inconsistencies? > > Best wishes, > Rainer > Hello, thanks for the quick response. I checked on the CURRENT systems here at hand and must confess - it is a mess! pkg check -Bn dropped a lot of missing shared objects missing from autotools and missing guile2 :-( Thank you very much, oh -- O. Hartmann From nobody Sun Apr 7 09:15:20 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4VC65q4cm5z5GdJV; Sun, 7 Apr 2024 09:15:59 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Received: from smtp052.goneo.de (smtp052.goneo.de [85.220.129.60]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4VC65p2rGQz4krd; Sun, 7 Apr 2024 09:15:58 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=walstatt-de.de header.s=DKIM001 header.b="Fjq9po/7"; dmarc=none; spf=pass (mx1.freebsd.org: domain of freebsd@walstatt-de.de designates 85.220.129.60 as permitted sender) smtp.mailfrom=freebsd@walstatt-de.de Received: from hub1.goneo.de (hub1.goneo.de [IPv6:2001:1640:5::8:52]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by smtp5.goneo.de (Postfix) with ESMTPS id B77982405E6; Sun, 7 Apr 2024 11:15:50 +0200 (CEST) Received: from hub1.goneo.de (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by hub1.goneo.de (Postfix) with ESMTPS id D5298240124; Sun, 7 Apr 2024 11:15:48 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=walstatt-de.de; s=DKIM001; t=1712481348; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=wi5dxrLVi/mmz1sh0GhhP01WdyFWkzlAu7fLxh2b61Y=; b=Fjq9po/7/c/yG+sVDuAsefP3EadTB72xZFJWnOyb+3TAe+xFhVbfKtvIafw2v4P9Rkdj2s d3S7tGZpuHDlvYOQD3frUu+P7lvpQPkAAu+rxCMzSRQ5kIP2pjR5mjo1KsHSMpbAi75ViE 2VmjMeE/t7sYsXIG0HODuAztEU/snNPSIwXKKm2etIz0CpjBrV5jtMYxDEOZto8LgH96xi RFkIRkPHwVCFM9fNlZQ+aCdkDufqWMgTtihidqDS97ReKeyBKCl+1RGBUeXiv91p59s+ax tVGA4B/qvN4XbOi3eAM5gZLda3P8bGRplhGewzlnC3k0sqBivz5nrY/hAxi7wQ== Received: from thor.intern.walstatt.dynvpn.de (dynamic-077-011-008-227.77.11.pool.telefonica.de [77.11.8.227]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (prime256v1) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by hub1.goneo.de (Postfix) with ESMTPSA id 987D6240030; Sun, 7 Apr 2024 11:15:48 +0200 (CEST) Date: Sun, 7 Apr 2024 11:15:20 +0200 From: FreeBSD User To: FreeBSD Ports , FreeBSD CURRENT Subject: Re: pkg-1.21.0: after upgrade 1.20.9_1 -> 1.21.0: pkg-static core dumps on some ports Message-ID: <20240407111547.2c3ea50b@thor.intern.walstatt.dynvpn.de> In-Reply-To: <20240406090527.34d84eb9@thor.intern.walstatt.dynvpn.de> References: <20240406090527.34d84eb9@thor.intern.walstatt.dynvpn.de> Organization: walstatt-de.de List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-UID: fab6b4 X-Rspamd-UID: c1ef7e X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.42 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.92)[-0.924]; R_SPF_ALLOW(-0.20)[+ip4:85.220.129.0/25]; R_DKIM_ALLOW(-0.20)[walstatt-de.de:s=DKIM001]; MIME_GOOD(-0.10)[text/plain]; ASN(0.00)[asn:25394, ipnet:85.220.128.0/17, country:DE]; MISSING_XM_UA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; HAS_ORG_HEADER(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org,freebsd-ports@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; DMARC_NA(0.00)[walstatt-de.de]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[walstatt-de.de:+] X-Rspamd-Queue-Id: 4VC65p2rGQz4krd Am Sat, 6 Apr 2024 09:05:00 +0200 FreeBSD User schrieb: > Hello, > > after updating (portmaster and make) ports-mgmt/ports from 1.20.9_1 -> 1.21.0 on CURRENT and > 14-STABLE, I can't update several ports: > > www/apache24 > databases/redis > > pkg core dumps while performing installation. apache24 and redis are ports I realized this > misbehaviour on ALL 14-STABLE and CURRENT boxes (both OS variants latest builds, i.e. FreeBSD > 15.0-CURRENT #32 main-n269135-da2b732288c7: Fri Apr 5 20:30:39 CEST 2024 amd64). > > After some updates on a poudriere builder (CURRENT base host, 14.0-RELENG jail with > poudriere) building packages for 14.0-RELENG, I observed the same behaviour when updating > packages on target hosts where pkg is first updated, on those hosts, nextcloud-server and > icinga2 host utilizing also databases/redis and www/apache24, pkg fails the same way. > > I do not dare to update our poudriere hosts since the problem seems to pop up when pkg 1.21.0 > is installed, no matter whether I use poudriere built ports (from our own builder hosts) or > recent source tree with portmaster/make build process. > > Looks like a serious bug to me and not a site/user specific problem. Hopefully others do > realize the same ... > > Thanks in advance, > > oh > > Hello, after following a recommnedation checking dependencies on ports via pkg check -Bn, recompiling pkg via "portmaster -df ports-mgmt/pkg" along with all ports found by the check command as well a sqlite (precaustion), still the pkg-static binary drops core dumps on some ports. Phenomenon: When updating existing ports, like www/apache24 databases/redis net/openldap26-server misc/e2fsprogs-libuuid building the port runs smootly, but pkg-static dies on deleting attempt of the old/to-be-reinstalled port. The problem arises by using portmaster as well as performing "make install/make deinstall" in the specific target port. Last port I hit is misc/e2fsprogs-libuuid. My skills debugging core dumps are rather limited, our boxes do have debugging disabled. Since the problem spreads across several hosts running CURRENT (same IcyBridge CPU generation, but one host most recent CURRENT with LLVM18, the other one running a CURRENT compiled 4 days ago and as of last week the problem arose also on 14-STABLE on a box in the lab when performing the tansition from pkg 1.20.9_1 -> 1.21.0), I'd exclude a hardware/memory issue. Using (a freshly recompiled) gdb 14 from ports gives not much: [...] root@thor:/usr/ports # gdb /usr/local/sbin/pkg-static ./packages/portmaster-backup/pkg-static.core GNU gdb (GDB) 14.1 [GDB v14.1 for FreeBSD] Copyright (C) 2023 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-portbld-freebsd15.0". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/local/sbin/pkg-static... (No debugging symbols found in /usr/local/sbin/pkg-static) [New LWP 101269] Core was generated by `/usr/local/sbin/pkg-static delete -yf e2fsprogs-libuuid-1.47.0'. Program terminated with signal SIGSEGV, Segmentation fault. Address not mapped to object. #0 0x0000000000b3de2b in strlen_baseline () Kind regards, oh -- O. Hartmann From nobody Sun Apr 7 10:49:15 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4VC89V19DRz5GXkM; Sun, 7 Apr 2024 10:49:18 +0000 (UTC) (envelope-from lexi@le-fay.org) Received: from thyme.eden.le-Fay.ORG (THYME.EDEN.LE-FAY.ORG [81.187.47.194]) by mx1.freebsd.org (Postfix) with ESMTP id 4VC89T3Fwvz4ww9; Sun, 7 Apr 2024 10:49:17 +0000 (UTC) (envelope-from lexi@le-fay.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=le-fay.org header.s=thyme header.b=oCjwHpDZ; dmarc=none; spf=pass (mx1.freebsd.org: domain of lexi@le-fay.org designates 81.187.47.194 as permitted sender) smtp.mailfrom=lexi@le-fay.org Received: from iris.eden.le-Fay.ORG (IRIS.EDEN.LE-FAY.ORG [IPv6:2001:8b0:aab5:106:3::6]) by thyme.eden.le-Fay.ORG (Postfix) with ESMTP id E031276; Sun, 07 Apr 2024 11:49:14 +0100 (BST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=le-fay.org; s=thyme; t=1712486954; bh=nMAQ3RiNiKFWwFJXRxJiWp+NcvBUJg7lNnvslUMFBEQ=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=oCjwHpDZpZ8AdRMjw/SdX8G1I9yc0L2+aFVVF2ZTDLPb9oMLPM+xbfmWEYeVNdjVa IZENM4OpSiMF7Kc3Zmg+ANORBkzPz+c2iHU+BBz1Www7eYj+7BI97pcmx9PNHysl/F 75+3UnlDkh/wZgngotDCnNyDqgbPxOcinoZH+XgE= Received: from ilythia.eden.le-fay.org (ILYTHIA.EDEN.LE-FAY.ORG [IPv6:2001:8b0:aab5:106:3::10]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (secp384r1) server-digest SHA384) (No client certificate requested) by iris.eden.le-Fay.ORG (Postfix) with ESMTPSA id 5A2C42C0400; Sun, 07 Apr 2024 11:49:15 +0100 (BST) Date: Sun, 7 Apr 2024 11:49:15 +0100 From: Lexi Winter To: Mark Millard Cc: FreeBSD ARM List , freebsd-current@freebsd.org Subject: Re: 15.0 on RPi4, USB broken: uhub_reattach_port: port 2 reset failed, error=USB_ERR_TIMEOUT Message-ID: Mail-Followup-To: Mark Millard , FreeBSD ARM List , freebsd-current@freebsd.org References: <04AA156F-129B-41C2-AB3D-B762585F8BC0@yahoo.com> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="nOU2GO/wMrSyUgvR" Content-Disposition: inline In-Reply-To: <04AA156F-129B-41C2-AB3D-B762585F8BC0@yahoo.com> X-Spamd-Bar: ----- X-Spamd-Result: default: False [-5.60 / 15.00]; SIGNED_PGP(-2.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.999]; R_DKIM_ALLOW(-0.20)[le-fay.org:s=thyme]; R_SPF_ALLOW(-0.20)[+ip4:81.187.47.194]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; RCVD_NO_TLS_LAST(0.10)[]; RCVD_IN_DNSWL_LOW(-0.10)[81.187.47.194:from]; FREEMAIL_TO(0.00)[yahoo.com]; RCPT_COUNT_THREE(0.00)[3]; DMARC_NA(0.00)[le-fay.org]; DKIM_TRACE(0.00)[le-fay.org:+]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FROM_HAS_DN(0.00)[]; ASN(0.00)[asn:20712, ipnet:81.187.0.0/16, country:GB]; TO_DN_SOME(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; MISSING_XM_UA(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org,freebsd-current@freebsd.org]; MID_RHS_MATCH_FROMTLD(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; DWL_DNSWL_NONE(0.00)[le-fay.org:dkim] X-Rspamd-Queue-Id: 4VC89T3Fwvz4ww9 --nOU2GO/wMrSyUgvR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Mark Millard: > On Mar 30, 2024, at 12:44, Lexi Winter wrote: > > when the problem happens, with USB_DEBUG enabled, the kernel logs: > >=20 > > uhub_reattach_port: port 2 reset failed, error=3DUSB_ERR_TIMEOUT > > uhub_reattach_port: device problem (USB_ERR_TIMEOUT), disabling port 2 >=20 > Here is my config.txt material related to such issues: >=20 > # > # Local addition that avoids USB3 SSD boot failures that look like: > # uhub_reattach_port: port ? reset failed, error=3DUSB_ERR_TIMEOUT > # uhub_reattach_port: device problem (USB_ERR_TIMEOUT), disabling port ? > # WARNING, not sufficient for "boot -s": that needs the full force_turbo= =3D1 > initial_turbo=3D60 =20 thanks -- after setting this in config.txt, the problem seems to be fixed. hopefully this won't cause any overheating issues; none of my RPis have fans, but they have fairly decent passive cooling, and are running powerd on boot. regards, lexi. --nOU2GO/wMrSyUgvR Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGzBAABCAAdFiEEuwt6MaPcv/+Mo+ftDHqbqZ41x5kFAmYSeigACgkQDHqbqZ41 x5kU2QwAoDDkHWfubUcLE5znIqajVHrdk+OFiZhactS2K5VL3kAA8HPBRIUoi1Vp 5d3q0erwXZyRERhe02olynxjFFyxElDCszd1yM3xCsUyupzMnOWfmFR5NAscwZqz XDGdvlo/te6fqIFvm4ASOSo5ZjXKubQ/NpTOOoLx3ktOmbhJE+8Bi36/6cwzWox6 NEATLzZHVvc04eVxmdM4PhyygQL3rCgBuUBQt1+BO7TFlLKGWu884XVmaFUoM8iA aYjcey96FfL7mY+hXYevL+V7kVoFvK4knOjxRz7ck8wfFGbzhl8YnNBhVocRqerR k8J0WWyxqNpsVReAVSVgC+6eql0y83Pu1h/uL0e0XtrEBF9FpE6g8QMQ6eMeNU0f iDsD+I7lB4Tgz3imgEtFSyi1IX+xP0rTDwrYMn5wKPA2cdycwwq9PXdmzK1H4GR9 /G22EZCXSoED7K7AGlsrNIVBH4TodEKeqoO7xibjP7ffT39lc2sQ+i9y/VxW7kXR nlwDsSbS =4NTU -----END PGP SIGNATURE----- --nOU2GO/wMrSyUgvR-- From nobody Sun Apr 7 23:09:46 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4VCSc915mHz5FVkf for ; Sun, 7 Apr 2024 23:10:01 +0000 (UTC) (envelope-from rick.macklem@gmail.com) Received: from mail-pf1-x429.google.com (mail-pf1-x429.google.com [IPv6:2607:f8b0:4864:20::429]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4VCSc818R4z44BM for ; Sun, 7 Apr 2024 23:10:00 +0000 (UTC) (envelope-from rick.macklem@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b=ZfRERfrR; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of rick.macklem@gmail.com designates 2607:f8b0:4864:20::429 as permitted sender) smtp.mailfrom=rick.macklem@gmail.com Received: by mail-pf1-x429.google.com with SMTP id d2e1a72fcca58-6ece8991654so3532208b3a.3 for ; Sun, 07 Apr 2024 16:10:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1712531397; x=1713136197; darn=freebsd.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=u+61znFuCDt/Yq4xuZpPKISCXL62CG2Pf5GgX9JqW9o=; b=ZfRERfrRha0Yx+SRU3/Tf9rTYdxYP7ZlFxdogdN+sxI/u0SWOqd05nT64mAHVIPcmo OVPcpNriBccva4rTjTF/Q+w+ikGTWzHc67qriXJfrZY7nzlexfZfbcvMFuaDq8EcotF5 IaZx6WaL4RJ14LuX8AfuRpujKdamr3wbcCjEHQjlKa1NxUe87eI0zmMtoZELN2/CWEIi 5IgWq/piSjMKzPcn72eYqFypwX9S4nHnbZLKTM64dQR+VjNv/2HGqJhGq41M2c1xaVfx ZzGPBFUGh631yaBQqVh/9CG1mak6+4T9CS2AcZFD7ONqyEhjasa9OfnFMHckQFbHX3IQ GSMg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1712531397; x=1713136197; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=u+61znFuCDt/Yq4xuZpPKISCXL62CG2Pf5GgX9JqW9o=; b=rIEzCNG2iNvu+jEcK0L9wjVMSNsA1egP9QtUV9nXt+Wd+XpNLHmcfYfBnfZUEYoC5s xnNDsHz+6Qgm/Kv3/1DzTwmQ9MBrUG8pHVdeOqBZii2Bw2Vyrg7vBdvJE3laRwSCCJjo Z+JYaDoBl1F7oC9sRJ0SpB+ICUZX5vQN/dShihus9AizHQdhW4FFm8hxS87kdou9c3iT nNzZHDB4HrRxwTApclCqs9IGEVLnVrt2VFOByhb+aVxcrpzzab7fTXK4vxP2eVspLEEh 5nC/BwoswuJV7CTrd3g6cJ7O06gCWLLd5tJRxEDiSC+2gwTGzuHxe9T7vxP5yVFz24h9 7ccg== X-Gm-Message-State: AOJu0YxAC2KhGtXnCS6XKTfo+9wDFlBUe/HrYdgbPC9FEHEYXUrNk31/ iJE7qdsFDspOvODIDFn6O2EvX26rA0r1sSOwr/7Cd3NjRqGD3XkJaANeQH4SKkjtNl7Lt3RwRi+ Wk5ZMqiVfewHm7DqWAPYByEUzy5jZc+Q= X-Google-Smtp-Source: AGHT+IFDqm+XYgCGwZPa1FEeDs25proSFsxPTUeHQDtPshfOs4Z6GYI7sn8IukbH7qAzkgN5FX+stfj7HhP5BngA+tA= X-Received: by 2002:a05:6a21:9201:b0:1a7:3f4c:21d1 with SMTP id tl1-20020a056a21920100b001a73f4c21d1mr10453008pzb.35.1712531397174; Sun, 07 Apr 2024 16:09:57 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 From: Rick Macklem Date: Sun, 7 Apr 2024 16:09:46 -0700 Message-ID: Subject: RFC: Does anyone use the -public/-webnfs NFS exports? To: FreeBSD CURRENT Content-Type: text/plain; charset="UTF-8" X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.93 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-0.999]; NEURAL_HAM_SHORT(-0.93)[-0.931]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36:c]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; FROM_HAS_DN(0.00)[]; MIME_TRACE(0.00)[0:+]; ARC_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; FREEMAIL_FROM(0.00)[gmail.com]; TO_DN_ALL(0.00)[]; MISSING_XM_UA(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; TAGGED_FROM(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::429:from] X-Rspamd-Queue-Id: 4VCSc818R4z44BM Hi, I have a hunch that no one uses the WebNFS stuff, which is done via exports(5) using the -public or -webnfs exports options. I would like to deprecate these exports options, but thought I'd ask in case anyone uses them? rick