Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 02 Apr 2024 00:42:23 -0700
From:      Chris <bsd-lists@bsdforge.com>
To:        Kevin Oberman <rkoberman@gmail.com>
Cc:        freebsd-current <freebsd-current@freebsd.org>
Subject:   Re: Multi cons support has disappeared (on Alder Lake) was: Alt+Fn isn't functional. Has this been removed?
Message-ID:  <ec5c8adb26d30f12c15b15fb41fd3119@bsdforge.com>
In-Reply-To: <CAN6yY1vLtr03SvMc=db-1XA0Lg1CrgbQDkK5vgn8bwj3tca3sA@mail.gmail.com>
References:  <a9773da25105973b6eaf687f0a816125@bsdforge.com> <CAN6yY1vLtr03SvMc=db-1XA0Lg1CrgbQDkK5vgn8bwj3tca3sA@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 2024-04-01 22:51, Kevin Oberman wrote:
> On Mon, Apr 1, 2024 at 3:05 PM 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 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! :)



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ec5c8adb26d30f12c15b15fb41fd3119>