Solved boot hangs after loading i915kms

BaronBS · Nov 29, 2024

Hello forum.

So, since I moved from 14.1-RELEASE to 14-STABLE i915kms stopped working.
The OS freeze after loading the module, both manually or during boot.
Here it is what I see (sorry for the pic, but it is a tty):

After that just a hard reset to get the system running again.
What should I do/look for?

tOsYZYny · Nov 29, 2024

I'm not an expert, but I would try:

Do the logs report anything, /var/log/messages? What about dmesg (both the cmd and /var/log/dmesg.today)?

Does it truly freeze or just the video dies? Do you have another system that you can ssh into this both with? If so, see if you can SSH in, that will let you know that the system is still running, but the video is hung. Alternatively, you could try pinging it to see that it still responds to pings. If it were truly dead, then it wouldn't respond at all.

Also, if you were lucky and made a Boot Environment prior to the upgrade, you could simply reboot into the older working configuration and set that as your active BE until this issue is sorted out. If not, you might still be able to select the older kernel during boot.

BaronBS · Nov 29, 2024

tOsYZYny said:
Do the logs report anything, /var/log/messages?

Last boot entry that I tried to load the module:

Code:

Nov 29 21:48:00 BattleStar-Hydra kernel: ---<<BOOT>>---
Nov 29 21:48:00 BattleStar-Hydra kernel: Copyright (c) 1992-2023 The FreeBSD Project.
Nov 29 21:48:00 BattleStar-Hydra kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
Nov 29 21:48:00 BattleStar-Hydra kernel:     The Regents of the University of California. All rights reserved.
Nov 29 21:48:00 BattleStar-Hydra kernel: FreeBSD is a registered trademark of The FreeBSD Foundation.
Nov 29 21:48:00 BattleStar-Hydra kernel: FreeBSD 14.2-STABLE stable/14-n269706-0dd21407bd39 GENERIC amd64
Nov 29 21:48:00 BattleStar-Hydra kernel: FreeBSD clang version 18.1.6 (https://github.com/llvm/llvm-project.git llvmorg-18.1.6-0-g1118c2e05e67)
Nov 29 21:48:00 BattleStar-Hydra kernel: VT(efifb): resolution 1920x1080
Nov 29 21:48:00 BattleStar-Hydra kernel: CPU: Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz (3292.47-MHz K8-class CPU)
Nov 29 21:48:00 BattleStar-Hydra kernel:   Origin="GenuineIntel"  Id=0x306c3  Family=0x6  Model=0x3c  Stepping=3
Nov 29 21:48:00 BattleStar-Hydra kernel:   Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
Nov 29 21:48:00 BattleStar-Hydra kernel:   Features2=0x7ffafbff<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND>
Nov 29 21:48:00 BattleStar-Hydra kernel:   AMD Features=0x2c100800<SYSCALL,NX,Page1GB,RDTSCP,LM>
Nov 29 21:48:00 BattleStar-Hydra kernel:   AMD Features2=0x21<LAHF,ABM>
Nov 29 21:48:00 BattleStar-Hydra kernel:   Structured Extended Features=0x27ab<FSGSBASE,TSCADJ,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,NFPUSG>
Nov 29 21:48:00 BattleStar-Hydra kernel:   XSAVE Features=0x1<XSAVEOPT>
Nov 29 21:48:00 BattleStar-Hydra kernel:   VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID
Nov 29 21:48:00 BattleStar-Hydra kernel:   TSC: P-state invariant, performance statistics
Nov 29 21:48:00 BattleStar-Hydra kernel: real memory  = 34359738368 (32768 MB)
Nov 29 21:48:00 BattleStar-Hydra kernel: avail memory = 33265737728 (31724 MB)
Nov 29 21:48:00 BattleStar-Hydra kernel: Event timer "LAPIC" quality 600
Nov 29 21:48:00 BattleStar-Hydra kernel: ACPI APIC Table: <DELL   CBX3   >
Nov 29 21:48:00 BattleStar-Hydra kernel: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
Nov 29 21:48:00 BattleStar-Hydra kernel: FreeBSD/SMP: 1 package(s) x 4 core(s)
Nov 29 21:48:00 BattleStar-Hydra kernel: random: registering fast source Intel Secure Key RNG
Nov 29 21:48:00 BattleStar-Hydra kernel: random: fast provider: "Intel Secure Key RNG"
Nov 29 21:48:00 BattleStar-Hydra kernel: random: unblocking device.
Nov 29 21:48:00 BattleStar-Hydra kernel: ioapic0 <Version 2.0> irqs 0-23
Nov 29 21:48:00 BattleStar-Hydra kernel: Launching APs: 2 3 1
Nov 29 21:48:00 BattleStar-Hydra kernel: random: entropy device external interface
Nov 29 21:48:00 BattleStar-Hydra kernel: kbd1 at kbdmux0
Nov 29 21:48:00 BattleStar-Hydra kernel: efirtc0: <EFI Realtime Clock>
Nov 29 21:48:00 BattleStar-Hydra kernel: efirtc0: registered as a time-of-day clock, resolution 1.000000s
Nov 29 21:48:00 BattleStar-Hydra kernel: smbios0: <System Management BIOS> at iomem 0xf0000-0xf001e
Nov 29 21:48:00 BattleStar-Hydra kernel: smbios0: Version: 2.7, BCD Revision: 2.7
Nov 29 21:48:00 BattleStar-Hydra kernel: aesni0: <AES-CBC,AES-CCM,AES-GCM,AES-ICM,AES-XTS>
Nov 29 21:48:00 BattleStar-Hydra kernel: acpi0: <DELL CBX3   >
Nov 29 21:48:00 BattleStar-Hydra kernel: acpi0: Power Button (fixed)
Nov 29 21:48:00 BattleStar-Hydra kernel: cpu0: <ACPI CPU> on acpi0
Nov 29 21:48:00 BattleStar-Hydra kernel: hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
Nov 29 21:48:00 BattleStar-Hydra kernel: Timecounter "HPET" frequency 14318180 Hz quality 950
Nov 29 21:48:00 BattleStar-Hydra kernel: Event timer "HPET" frequency 14318180 Hz quality 550
Nov 29 21:48:00 BattleStar-Hydra kernel: Event timer "HPET1" frequency 14318180 Hz quality 440
Nov 29 21:48:00 BattleStar-Hydra kernel: Event timer "HPET2" frequency 14318180 Hz quality 440
Nov 29 21:48:00 BattleStar-Hydra kernel: Event timer "HPET3" frequency 14318180 Hz quality 440
Nov 29 21:48:00 BattleStar-Hydra kernel: Event timer "HPET4" frequency 14318180 Hz quality 440
Nov 29 21:48:00 BattleStar-Hydra kernel: atrtc0: <AT realtime clock> port 0x70-0x77 irq 8 on acpi0
Nov 29 21:48:00 BattleStar-Hydra kernel: atrtc0: Warning: Couldn't map I/O.
Nov 29 21:48:00 BattleStar-Hydra kernel: atrtc0: registered as a time-of-day clock, resolution 1.000000s
Nov 29 21:48:00 BattleStar-Hydra kernel: Event timer "RTC" frequency 32768 Hz quality 0
Nov 29 21:48:00 BattleStar-Hydra kernel: attimer0: <AT timer> port 0x40-0x43,0x50-0x53 irq 0 on acpi0
Nov 29 21:48:00 BattleStar-Hydra kernel: Timecounter "i8254" frequency 1193182 Hz quality 0
Nov 29 21:48:00 BattleStar-Hydra kernel: Event timer "i8254" frequency 1193182 Hz quality 100
Nov 29 21:48:00 BattleStar-Hydra kernel: Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
Nov 29 21:48:00 BattleStar-Hydra kernel: acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1808-0x180b on acpi0
Nov 29 21:48:00 BattleStar-Hydra kernel: pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
Nov 29 21:48:00 BattleStar-Hydra kernel: pci0: <ACPI PCI bus> on pcib0
Nov 29 21:48:00 BattleStar-Hydra kernel: vgapci0: <VGA-compatible display> port 0xf000-0xf03f mem 0xf7800000-0xf7bfffff,0xe0000000-0xefffffff at device 2.0 on pci0
Nov 29 21:48:00 BattleStar-Hydra kernel: vgapci0: Boot video device
Nov 29 21:48:00 BattleStar-Hydra kernel: hdac0: <Intel Haswell HDA Controller> mem 0xf7c34000-0xf7c37fff at device 3.0 on pci0
Nov 29 21:48:00 BattleStar-Hydra kernel: xhci0: <Intel Lynx Point USB 3.0 controller> mem 0xf7c20000-0xf7c2ffff at device 20.0 on pci0
Nov 29 21:48:00 BattleStar-Hydra kernel: xhci0: 32 bytes context size, 64-bit DMA
Nov 29 21:48:00 BattleStar-Hydra kernel: usbus0: waiting for BIOS to give up control
Nov 29 21:48:00 BattleStar-Hydra kernel: xhci0: Port routing mask set to 0xffffffff
Nov 29 21:48:00 BattleStar-Hydra kernel: usbus0 on xhci0
Nov 29 21:48:00 BattleStar-Hydra kernel: usbus0: 5.0Gbps Super Speed USB v3.0
Nov 29 21:48:00 BattleStar-Hydra kernel: pci0: <simple comms> at device 22.0 (no driver attached)
Nov 29 21:48:00 BattleStar-Hydra kernel: em0: <Intel(R) I217-LM LPT> port 0xf080-0xf09f mem 0xf7c00000-0xf7c1ffff,0xf7c3d000-0xf7c3dfff at device 25.0 on pci0
Nov 29 21:48:00 BattleStar-Hydra kernel: em0: EEPROM V0.13-4
Nov 29 21:48:00 BattleStar-Hydra kernel: em0: Using 1024 TX descriptors and 1024 RX descriptors
Nov 29 21:48:00 BattleStar-Hydra kernel: em0: Using an MSI interrupt
Nov 29 21:48:00 BattleStar-Hydra kernel: em0: Ethernet address: 98:90:96:b6:e8:d7
Nov 29 21:48:00 BattleStar-Hydra kernel: em0: netmap queues/slots: TX 1/1024, RX 1/1024
Nov 29 21:48:00 BattleStar-Hydra kernel: ehci0: <Intel Lynx Point USB 2.0 controller USB-B> mem 0xf7c3c000-0xf7c3c3ff at device 26.0 on pci0
Nov 29 21:48:00 BattleStar-Hydra kernel: usbus1: EHCI version 1.0
Nov 29 21:48:00 BattleStar-Hydra kernel: usbus1 on ehci0
Nov 29 21:48:00 BattleStar-Hydra kernel: usbus1: 480Mbps High Speed USB v2.0
Nov 29 21:48:00 BattleStar-Hydra kernel: hdac1: <Intel Lynx Point HDA Controller> mem 0xf7c30000-0xf7c33fff at device 27.0 on pci0
Nov 29 21:48:00 BattleStar-Hydra kernel: ehci1: <Intel Lynx Point USB 2.0 controller USB-A> mem 0xf7c3b000-0xf7c3b3ff at device 29.0 on pci0
Nov 29 21:48:00 BattleStar-Hydra kernel: usbus2: EHCI version 1.0
Nov 29 21:48:00 BattleStar-Hydra kernel: usbus2 on ehci1
Nov 29 21:48:00 BattleStar-Hydra kernel: usbus2: 480Mbps High Speed USB v2.0
Nov 29 21:48:00 BattleStar-Hydra kernel: isab0: <PCI-ISA bridge> at device 31.0 on pci0
Nov 29 21:48:00 BattleStar-Hydra kernel: isa0: <ISA bus> on isab0
Nov 29 21:48:00 BattleStar-Hydra kernel: ahci0: <Intel Lynx Point AHCI SATA controller> port 0xf0d0-0xf0d7,0xf0c0-0xf0c3,0xf0b0-0xf0b7,0xf0a0-0xf0a3,0xf060-0xf07f mem 0xf7c3a000-0xf7c3a7ff at device 31.2 on pci0
Nov 29 21:48:00 BattleStar-Hydra kernel: ahci0: AHCI v1.30 with 6 6Gbps ports, Port Multiplier not supported
Nov 29 21:48:00 BattleStar-Hydra kernel: ahcich0: <AHCI channel> at channel 0 on ahci0
Nov 29 21:48:00 BattleStar-Hydra kernel: ahcich1: <AHCI channel> at channel 1 on ahci0
Nov 29 21:48:00 BattleStar-Hydra kernel: ahcich2: <AHCI channel> at channel 2 on ahci0
Nov 29 21:48:00 BattleStar-Hydra kernel: ahciem0: <AHCI enclosure management bridge> on ahci0
Nov 29 21:48:00 BattleStar-Hydra kernel: acpi_button0: <Power Button> on acpi0
Nov 29 21:48:00 BattleStar-Hydra kernel: acpi_tz0: <Thermal Zone> on acpi0
Nov 29 21:48:00 BattleStar-Hydra kernel: acpi_tz1: <Thermal Zone> on acpi0
Nov 29 21:48:00 BattleStar-Hydra kernel: uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
Nov 29 21:48:00 BattleStar-Hydra kernel: atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
Nov 29 21:48:00 BattleStar-Hydra kernel: atkbd0: <AT Keyboard> irq 1 on atkbdc0
Nov 29 21:48:00 BattleStar-Hydra kernel: kbd0 at atkbd0
Nov 29 21:48:00 BattleStar-Hydra kernel: atkbd0: [GIANT-LOCKED]
Nov 29 21:48:00 BattleStar-Hydra kernel: atkbdc0: non-PNP ISA device will be removed from GENERIC in FreeBSD 15.
Nov 29 21:48:00 BattleStar-Hydra kernel: est0: <Enhanced SpeedStep Frequency Control> on cpu0
Nov 29 21:48:00 BattleStar-Hydra kernel: Timecounter "TSC-low" frequency 1646189477 Hz quality 1000
Nov 29 21:48:00 BattleStar-Hydra kernel: Timecounters tick every 1.000 msec
Nov 29 21:48:00 BattleStar-Hydra kernel: ugen1.1: <Intel EHCI root HUB> at usbus1
Nov 29 21:48:00 BattleStar-Hydra kernel: ugen2.1: <Intel EHCI root HUB> at usbus2
Nov 29 21:48:00 BattleStar-Hydra kernel: ugen0.1: <Intel XHCI root HUB> at usbus0
Nov 29 21:48:00 BattleStar-Hydra kernel: uhub0 on usbus1
Nov 29 21:48:00 BattleStar-Hydra kernel: uhub0: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus1
Nov 29 21:48:00 BattleStar-Hydra kernel: uhub1 on usbus2
Nov 29 21:48:00 BattleStar-Hydra kernel: uhub1: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus2
Nov 29 21:48:00 BattleStar-Hydra kernel: uhub2 on usbus0
Nov 29 21:48:00 BattleStar-Hydra kernel: uhub2: <Intel XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0
Nov 29 21:48:00 BattleStar-Hydra kernel: ZFS filesystem version: 5
Nov 29 21:48:00 BattleStar-Hydra kernel: ZFS storage pool version: features support (5000)
Nov 29 21:48:00 BattleStar-Hydra kernel: hdacc0: <Intel Haswell HDA CODEC> at cad 0 on hdac0
Nov 29 21:48:00 BattleStar-Hydra kernel: hdaa0: <Intel Haswell Audio Function Group> at nid 1 on hdacc0
Nov 29 21:48:00 BattleStar-Hydra kernel: hdacc1: <Realtek ALC280 HDA CODEC> at cad 0 on hdac1
Nov 29 21:48:00 BattleStar-Hydra kernel: hdaa1: <Realtek ALC280 Audio Function Group> at nid 1 on hdacc1
Nov 29 21:48:00 BattleStar-Hydra kernel: pcm0: <Realtek ALC280 (Analog 2.0+HP/2.0)> at nid 20,21 and 26 on hdaa1
Nov 29 21:48:00 BattleStar-Hydra kernel: pcm1: <Realtek ALC280 (Rear Analog)> at nid 27 and 24 on hdaa1
Nov 29 21:48:00 BattleStar-Hydra kernel: Trying to mount root from zfs:zroot/ROOT/default-stable []...
Nov 29 21:48:00 BattleStar-Hydra kernel: ada0 at ahcich0 bus 0 scbus0 target 0 lun 0
Nov 29 21:48:00 BattleStar-Hydra kernel: ada0: <Crucial CT275MX300SSD1 M0CR031> ACS-3 ATA SATA 3.x device
Nov 29 21:48:00 BattleStar-Hydra kernel: ada0: Serial Number 164614AF08D0
Nov 29 21:48:00 BattleStar-Hydra kernel: ada0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes)
Nov 29 21:48:00 BattleStar-Hydra kernel: ada0: Command Queueing enabled
Nov 29 21:48:00 BattleStar-Hydra kernel: ada0: 262321MB (537234768 512 byte sectors)
Nov 29 21:48:00 BattleStar-Hydra kernel: ada1 at ahcich1 bus 0 scbus1 target 0 lun 0
Nov 29 21:48:00 BattleStar-Hydra kernel: ada1: <ST500LM000-1EJ162 DEM9> ACS-2 ATA SATA 3.x device
Nov 29 21:48:00 BattleStar-Hydra kernel: ada1: Serial Number W76343VQ
Nov 29 21:48:00 BattleStar-Hydra kernel: ada1: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes)
Nov 29 21:48:00 BattleStar-Hydra kernel: ada1: Command Queueing enabled
Nov 29 21:48:00 BattleStar-Hydra kernel: ada1: 476940MB (976773168 512 byte sectors)
Nov 29 21:48:00 BattleStar-Hydra kernel: ada2 at ahcich2 bus 0 scbus2 target 0 lun 0
Nov 29 21:48:00 BattleStar-Hydra kernel: ada2: <ST9500423AS 0002DEM1> ATA8-ACS SATA 2.x device
Nov 29 21:48:00 BattleStar-Hydra kernel: ada2: Serial Number 5WS2JFEG
Nov 29 21:48:00 BattleStar-Hydra kernel: ada2: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
Nov 29 21:48:00 BattleStar-Hydra kernel: ada2: Command Queueing enabled
Nov 29 21:48:00 BattleStar-Hydra kernel: ada2: 476940MB (976773168 512 byte sectors)
Nov 29 21:48:00 BattleStar-Hydra kernel: ada2: quirks=0x1<4K>
Nov 29 21:48:00 BattleStar-Hydra kernel: ses0 at ahciem0 bus 0 scbus3 target 0 lun 0
Nov 29 21:48:00 BattleStar-Hydra kernel: ses0: <AHCI SGPIO Enclosure 2.00 0001> SEMB S-E-S 2.00 device
Nov 29 21:48:00 BattleStar-Hydra kernel: ses0: SEMB SES Device
Nov 29 21:48:00 BattleStar-Hydra kernel: ses0: ada0,pass0 in 'Slot 00', SATA Slot: scbus0 target 0
Nov 29 21:48:00 BattleStar-Hydra kernel: ses0: ada1,pass1 in 'Slot 01', SATA Slot: scbus1 target 0
Nov 29 21:48:00 BattleStar-Hydra kernel: ses0: ada2,pass2 in 'Slot 02', SATA Slot: scbus2 target 0
Nov 29 21:48:00 BattleStar-Hydra kernel: GEOM_ELI: Device ada0p3.eli created.
Nov 29 21:48:00 BattleStar-Hydra kernel: GEOM_ELI: Encryption: AES-XTS 256
Nov 29 21:48:00 BattleStar-Hydra kernel: GEOM_ELI:     Crypto: accelerated software
Nov 29 21:48:00 BattleStar-Hydra kernel: uhub1: 2 ports with 2 removable, self powered
Nov 29 21:48:00 BattleStar-Hydra kernel: uhub0: 2 ports with 2 removable, self powered
Nov 29 21:48:00 BattleStar-Hydra kernel: uhub2: 21 ports with 21 removable, self powered
Nov 29 21:48:00 BattleStar-Hydra kernel: Root mount waiting for: usbus1 usbus2
Nov 29 21:48:00 BattleStar-Hydra kernel: ugen2.2: <vendor 0x8087 product 0x8000> at usbus2
Nov 29 21:48:00 BattleStar-Hydra kernel: uhub3 on uhub1
Nov 29 21:48:00 BattleStar-Hydra kernel: uhub3: <vendor 0x8087 product 0x8000, class 9/0, rev 2.00/0.04, addr 2> on usbus2
Nov 29 21:48:00 BattleStar-Hydra kernel: ugen1.2: <vendor 0x8087 product 0x8008> at usbus1
Nov 29 21:48:00 BattleStar-Hydra kernel: uhub4 on uhub0
Nov 29 21:48:00 BattleStar-Hydra kernel: uhub4: <vendor 0x8087 product 0x8008, class 9/0, rev 2.00/0.04, addr 2> on usbus1
Nov 29 21:48:00 BattleStar-Hydra kernel: uhub4: 6 ports with 6 removable, self powered
Nov 29 21:48:00 BattleStar-Hydra kernel: uhub3: 8 ports with 8 removable, self powered
Nov 29 21:48:00 BattleStar-Hydra kernel: Root mount waiting for: usbus1 usbus2
Nov 29 21:48:00 BattleStar-Hydra kernel: ugen1.3: <vendor 0x413c Dell KB216 Wired Keyboard> at usbus1
Nov 29 21:48:00 BattleStar-Hydra kernel: ukbd0 on uhub4
Nov 29 21:48:00 BattleStar-Hydra kernel: ukbd0: <vendor 0x413c Dell KB216 Wired Keyboard, class 0/0, rev 2.00/33.08, addr 3> on usbus1
Nov 29 21:48:00 BattleStar-Hydra kernel: kbd2 at ukbd0
Nov 29 21:48:00 BattleStar-Hydra kernel: Root mount waiting for: usbus2
Nov 29 21:48:00 BattleStar-Hydra kernel: usb_msc_auto_quirk: UQ_MSC_NO_GETMAXLUN set for USB mass storage device asmediag ASMT1051 (0x174c:0x55aa)
Nov 29 21:48:00 BattleStar-Hydra kernel: ugen2.3: <asmediag ASMT1051> at usbus2
Nov 29 21:48:00 BattleStar-Hydra kernel: umass0 on uhub3
Nov 29 21:48:00 BattleStar-Hydra kernel: umass0: <asmediag ASMT1051, class 0/0, rev 2.10/1.00, addr 3> on usbus2
Nov 29 21:48:00 BattleStar-Hydra kernel: umass0:  SCSI over Bulk-Only; quirks = 0x0100
Nov 29 21:48:00 BattleStar-Hydra kernel: umass0:4:0: Attached to scbus4
Nov 29 21:48:00 BattleStar-Hydra kernel: da0 at umass-sim0 bus 0 scbus4 target 0 lun 0
Nov 29 21:48:00 BattleStar-Hydra kernel: da0: <ASMT 2115 0> Fixed Direct Access SPC-4 SCSI device
Nov 29 21:48:00 BattleStar-Hydra kernel: da0: Serial Number 1234567890B8
Nov 29 21:48:00 BattleStar-Hydra kernel: da0: 40.000MB/s transfers
Nov 29 21:48:00 BattleStar-Hydra kernel: da0: 953869MB (1953525168 512 byte sectors)
Nov 29 21:48:00 BattleStar-Hydra kernel: da0: quirks=0x2<NO_6_BYTE>
Nov 29 21:48:00 BattleStar-Hydra kernel: GEOM_ELI: Device ada0p2.eli created.
Nov 29 21:48:00 BattleStar-Hydra kernel: GEOM_ELI: Encryption: AES-XTS 128
Nov 29 21:48:00 BattleStar-Hydra kernel: GEOM_ELI:     Crypto: accelerated software
Nov 29 21:48:00 BattleStar-Hydra kernel: ichsmb0: <Intel Lynx Point SMBus controller> port 0xf040-0xf05f mem 0xf7c39000-0xf7c390ff at device 31.3 on pci0
Nov 29 21:48:00 BattleStar-Hydra kernel: smbus0: <System Management Bus> on ichsmb0
Nov 29 21:48:00 BattleStar-Hydra kernel: em0: link state changed to UP
Nov 29 21:48:00 BattleStar-Hydra kernel: lo0: link state changed to UP
Nov 29 21:48:00 BattleStar-Hydra kernel: em0: link state changed to DOWN
Nov 29 21:48:00 BattleStar-Hydra kernel: em0: link state changed to UP
Nov 29 21:48:00 BattleStar-Hydra kernel: uhid0 on uhub4
Nov 29 21:48:00 BattleStar-Hydra kernel: uhid0: <vendor 0x413c Dell KB216 Wired Keyboard, class 0/0, rev 2.00/33.08, addr 3> on usbus1
Nov 29 21:48:00 BattleStar-Hydra kernel: tun0: link state changed to UP
Nov 29 21:48:00 BattleStar-Hydra kernel: tun0: changing name to 'tailscale0'
Nov 29 21:48:00 BattleStar-Hydra kernel: Security policy loaded: MAC/ntpd (mac_ntpd)
Nov 29 21:48:00 BattleStar-Hydra ntpd[72866]: ntpd 4.2.8p18-a (1): Starting
Nov 29 21:48:00 BattleStar-Hydra ntpd[72866]: Command line: /usr/sbin/ntpd -p /var/db/ntp/ntpd.pid -c /etc/ntp.conf -f /var/db/ntp/ntpd.drift
Nov 29 21:48:00 BattleStar-Hydra ntpd[72866]: ----------------------------------------------------
Nov 29 21:48:00 BattleStar-Hydra ntpd[72866]: ntp-4 is maintained by Network Time Foundation,
Nov 29 21:48:00 BattleStar-Hydra ntpd[72866]: Inc. (NTF), a non-profit 501(c)(3) public-benefit
Nov 29 21:48:00 BattleStar-Hydra ntpd[72866]: corporation.  Support and training for ntp-4 are
Nov 29 21:48:00 BattleStar-Hydra ntpd[72866]: available at https://www.nwtime.org/support
Nov 29 21:48:00 BattleStar-Hydra ntpd[72866]: ----------------------------------------------------
Nov 29 21:48:00 BattleStar-Hydra ntpd[73202]: leapsecond file ('/var/db/ntpd.leap-seconds.list'): good hash signature
Nov 29 21:48:00 BattleStar-Hydra ntpd[73202]: leapsecond file ('/var/db/ntpd.leap-seconds.list'): loaded, expire=2025-06-28T00:00:00Z last=2017-01-01T00:00:00Z ofs=37
Nov 29 21:48:00 BattleStar-Hydra mountd[92550]: Warning: exporting /media/Share exports entire / file system
Nov 29 21:48:00 BattleStar-Hydra mountd[92550]: can't change attributes for /media/Backup: netcred already exists for given addr/mask
Nov 29 21:48:00 BattleStar-Hydra mountd[92550]: bad exports list line '/media/Backup BattleStar-Lat54 BattleStar-Void418 BattleStar-T430'
Nov 29 21:49:04 BattleStar-Hydra kernel: [drm] Got Intel graphics stolen memory base 0xdd200000, size 0x2000000
Nov 29 21:49:04 BattleStar-Hydra kernel: drmn0: <drmn> on vgapci0
Nov 29 21:49:04 BattleStar-Hydra kernel: vgapci0: child drmn0 requested pci_enable_io
Nov 29 21:49:04 BattleStar-Hydra syslogd: last message repeated 1 times
Nov 29 21:49:04 BattleStar-Hydra kernel: lkpi_iic0: <LinuxKPI I2C> on drmn0
Nov 29 21:49:04 BattleStar-Hydra kernel: iicbus0: <Philips I2C bus> on lkpi_iic0
Nov 29 21:49:04 BattleStar-Hydra kernel: iic0: <I2C generic I/O>
Nov 29 21:49:04 BattleStar-Hydra kernel:  on iicbus0
Nov 29 21:49:04 BattleStar-Hydra kernel: lkpi_iic1: <LinuxKPI I2C> on drmn0
Nov 29 21:49:04 BattleStar-Hydra kernel: iicbus1: <Philips I2C bus> on lkpi_iic1
Nov 29 21:49:04 BattleStar-Hydra kernel: iic1: <I2C generic I/O> on iicbus1
Nov 29 21:49:04 BattleStar-Hydra kernel: lkpi_iic2: <LinuxKPI I2C> on drmn0
Nov 29 21:49:04 BattleStar-Hydra kernel: iicbus2: <Philips I2C bus> on lkpi_iic2
Nov 29 21:49:04 BattleStar-Hydra kernel: iic2: <I2C generic I/O> on iicbus2
Nov 29 21:49:04 BattleStar-Hydra kernel: lkpi_iic3: <LinuxKPI I2C> on drmn0
Nov 29 21:49:04 BattleStar-Hydra kernel: iicbus3: <Philips I2C bus> on lkpi_iic3
Nov 29 21:49:04 BattleStar-Hydra kernel: iic3: <I2C generic I/O> on iicbus3
Nov 29 21:49:04 BattleStar-Hydra kernel: lkpi_iic4: <LinuxKPI I2C> on drmn0
Nov 29 21:49:04 BattleStar-Hydra kernel: iicbus4: <Philips I2C bus> on lkpi_iic4
Nov 29 21:49:04 BattleStar-Hydra kernel: iic4: <I2C generic I/O> on iicbus4
Nov 29 21:49:04 BattleStar-Hydra kernel: lkpi_iic5: <LinuxKPI I2C> on drmn0
Nov 29 21:49:04 BattleStar-Hydra kernel: iicbus5: <Philips I2C bus> on lkpi_iic5
Nov 29 21:49:04 BattleStar-Hydra kernel: iic5: <I2C generic I/O> on iicbus5
Nov 29 21:49:05 BattleStar-Hydra kernel: sysctl_warn_reuse: can't re-use a leaf (hw.dri.debug)!
Nov 29 21:49:05 BattleStar-Hydra kernel: lkpi_iic6: <LinuxKPI I2C> on drm2
Nov 29 21:49:05 BattleStar-Hydra kernel: iicbus6: <Philips I2C bus> on lkpi_iic6
Nov 29 21:49:05 BattleStar-Hydra kernel: iic6: <I2C generic I/O> on iicbus6
Nov 29 21:49:05 BattleStar-Hydra kernel: lkpi_iic7: <LinuxKPI I2C> on drm4
Nov 29 21:49:05 BattleStar-Hydra kernel: iicbus7: <Philips I2C bus> on lkpi_iic7
Nov 29 21:49:05 BattleStar-Hydra kernel: iic7: <I2C generic I/O> on iicbus7
Nov 29 21:49:05 BattleStar-Hydra kernel: [drm] Initialized i915 1.6.0 20201103 for drmn0 on minor 0
Nov 29 21:49:05 BattleStar-Hydra kernel: VT: Driver priority 0 too low. Current 101
Nov 29 21:49:05 BattleStar-Hydra kernel:  fbd0: not attached to vt(4) console; another device has precedence (err=17)
Nov 29 21:50:41 BattleStar-Hydra kernel: .
Nov 29 21:50:42 BattleStar-Hydra kernel: , 9846.
Nov 29 21:50:42 BattleStar-Hydra kernel: .
Nov 29 21:50:42 BattleStar-Hydra ntpd[73202]: ntpd exiting on signal 15 (Terminated)
Nov 29 21:50:42 BattleStar-Hydra kernel: .
Nov 29 21:50:42 BattleStar-Hydra kernel:
Nov 29 21:50:42 BattleStar-Hydra kernel: tailscale0: link state changed to DOWN
Nov 29 21:50:42 BattleStar-Hydra devd[55534]: notify_clients: send() failed; dropping unresponsive client
Nov 29 21:50:42 BattleStar-Hydra syslogd: exiting on signal 15
Nov 29 21:52:21 BattleStar-Hydra syslogd: kernel boot file is /boot/kernel/kernel
..

Apparently it is just the video. I loaded the module manually in the server with another system connected via ssh, the session is alive and running, so it should be just the video, right?

Oh, almost forgot. dmesg output after I loaded the module:

Code:

tun0: link state changed to UP
tun0: changing name to 'tailscale0'
Security policy loaded: MAC/ntpd (mac_ntpd)
[drm] Got Intel graphics stolen memory base 0xdd200000, size 0x2000000
drmn0: <drmn> on vgapci0
vgapci0: child drmn0 requested pci_enable_io
vgapci0: child drmn0 requested pci_enable_io
lkpi_iic0: <LinuxKPI I2C> on drmn0
iicbus0: <Philips I2C bus> on lkpi_iic0
iic0: <I2C generic I/O> on iicbus0
lkpi_iic1: <LinuxKPI I2C> on drmn0
iicbus1: <Philips I2C bus> on lkpi_iic1
iic1: <I2C generic I/O> on iicbus1
lkpi_iic2: <LinuxKPI I2C> on drmn0
iicbus2: <Philips I2C bus> on lkpi_iic2
iic2: <I2C generic I/O> on iicbus2
lkpi_iic3: <LinuxKPI I2C> on drmn0
iicbus3: <Philips I2C bus> on lkpi_iic3
iic3: <I2C generic I/O> on iicbus3
lkpi_iic4: <LinuxKPI I2C> on drmn0
iicbus4: <Philips I2C bus> on lkpi_iic4
iic4: <I2C generic I/O> on iicbus4
lkpi_iic5: <LinuxKPI I2C> on drmn0
iicbus5: <Philips I2C bus> on lkpi_iic5
iic5: <I2C generic I/O> on iicbus5
sysctl_warn_reuse: can't re-use a leaf (hw.dri.debug)!
lkpi_iic6: <LinuxKPI I2C> on drm2
iicbus6: <Philips I2C bus> on lkpi_iic6
iic6: <I2C generic I/O> on iicbus6
lkpi_iic7: <LinuxKPI I2C> on drm4
iicbus7: <Philips I2C bus> on lkpi_iic7
iic7: <I2C generic I/O> on iicbus7
[drm] Initialized i915 1.6.0 20201103 for drmn0 on minor 0
VT: Driver priority 0 too low. Current 101
 fbd0: not attached to vt(4) console; another device has precedence (err=17)

T-Aoki · Nov 29, 2024

Some questions for prerequisites:

Is it installed via official pkg repo using pkg? Or via built from ports locally?
Which version of graphics/drm-*-kmod are you using?

If you installed it using official pkg, does replacing it by locally built (using ports) one help?

If it does not help and you're using graphics/drm-61-kmod (preferred by graphics/drm-kmod metaport), does forcibly switching to graphics/drm-515-kmod (if no luck,graphics/drm-510-kmod) help?

And more, do you have graphics/gpu-firmware-intel-kmod installed? (Possibly you did it via /usr/sbin/fwget(8)instead of pkg, thogh.)

Espionage724 · Nov 30, 2024

Running into this now with 14.2, i915kms mentions something about dmc firmware not found, then loaded later. UHD 630

Edit: It was drm-61-kmod causing the issue for me (worked 14.1 though). Replacing with drm-515-kmod works on 14.2 so far to startx Xfce!

BaronBS · Nov 30, 2024

T-Aoki said:
Is it installed via official pkg repo using pkg? Or via built from ports locally?

binary via pkg

T-Aoki said:
Which version of graphics/drm-*-kmod are you using?

Code:

beastie@BattleStar-Hydra --> ~
Ψ pkg prime-origins | grep kmod                                                                                            < 0:45 >  < 11,724-11-30 >  < 0 > 
graphics/drm-kmod
sysutils/sysctlbyname-improved-kmod
sysutils/sysctlinfo-kmod

T-Aoki said:
does replacing it by locally built (using ports) one help?

Yes.
dmesg:

Code:

Security policy loaded: MAC/ntpd (mac_ntpd)
[drm] Got Intel graphics stolen memory base 0xdd200000, size 0x2000000
drmn0: <drmn> on vgapci0
vgapci0: child drmn0 requested pci_enable_io
vgapci0: child drmn0 requested pci_enable_io
lkpi_iic0: <LinuxKPI I2C> on drmn0
iicbus0: <Philips I2C bus> on lkpi_iic0
iic0: <I2C generic I/O> on iicbus0
lkpi_iic1: <LinuxKPI I2C> on drmn0
iicbus1: <Philips I2C bus> on lkpi_iic1
iic1: <I2C generic I/O> on iicbus1
lkpi_iic2: <LinuxKPI I2C> on drmn0
iicbus2: <Philips I2C bus> on lkpi_iic2
iic2: <I2C generic I/O> on iicbus2
lkpi_iic3: <LinuxKPI I2C> on drmn0
iicbus3: <Philips I2C bus> on lkpi_iic3
iic3: <I2C generic I/O> on iicbus3
lkpi_iic4: <LinuxKPI I2C> on drmn0
iicbus4: <Philips I2C bus> on lkpi_iic4
iic4: <I2C generic I/O> on iicbus4
lkpi_iic5: <LinuxKPI I2C> on drmn0
iicbus5: <Philips I2C bus> on lkpi_iic5
iic5: <I2C generic I/O> on iicbus5
sysctl_warn_reuse: can't re-use a leaf (hw.dri.debug)!
lkpi_iic6: <LinuxKPI I2C> on drm2
iicbus6: <Philips I2C bus> on lkpi_iic6
iic6: <I2C generic I/O> on iicbus6
lkpi_iic7: <LinuxKPI I2C> on drm4
iicbus7: <Philips I2C bus> on lkpi_iic7
iic7: <I2C generic I/O> on iicbus7
[drm] Initialized i915 1.6.0 20201103 for drmn0 on minor 0
VT: Replacing driver "efifb" with new "drmfb".
start FB_INFO:
height=1080 width=1920 depth=32
pbase=0xe0000000 vbase=0xfffff800e0000000
name=drmn0 id=i915drmfb flags=0x0 stride=7680
end FB_INFO

I have no clue why it worked btf.

T-Aoki said:
If it does not help and you're using graphics/drm-61-kmod (preferred by graphics/drm-kmod metaport), does forcibly switching to graphics/drm-515-kmod (if no luck,graphics/drm-510-kmod) help?

How do I know which one it's being used?

T-Aoki said:
And more, do you have graphics/gpu-firmware-intel-kmod installed?

Yes, it probably came with graphics/drm-kmod.

T-Aoki said:
(Possibly you did it via /usr/sbin/fwget(8)instead of pkg, thogh.)

Nope, didn't even know this tool.

Espionage724 · Nov 30, 2024

BaronBS said:
How do I know which one it's being used?

I could only have one or the other installed; I'd try pkg install -f drm-515-kmod

T-Aoki · Nov 30, 2024

Espionage724 said:
Running into this now with 14.2, i915kms mentions something about dmc firmware not found, then loaded later. UHD 630

Edit: It was drm-61-kmod causing the issue for me (worked 14.1 though). Replacing with drm-515-kmod works on 14.2 so far to startx Xfce!

Usually the newer version (510:5.10 < 515:5.15 < 61:6.1) is better.
But unfortunately, human makes mistakes and developers (including upstream) are humans. Sometimes newer version breaks something other than the developer is targeting/testing. So going backward downto the version that the running hardware is supported could be a good try.

T-Aoki · Nov 30, 2024

BaronBS said:
I have no clue why it worked btf.

Because drm-*-kmod ports strongly depends on the version (at a level of specific commit) of the kernel (precisely, linuxkpi module) on which it was built. So the mis-match happenes relatively often, as linuxkpi is actively developed to support newer hardwares.
Many of kernel modules in ports tree loosely depends on kernel versions, so those can run on latest stable/14 even if it is built on 14.0-Release, but some cannot, and drm related ports are clearly the latter, thus, local builds are almost mandatory for each time you update base.

BaronBS said:
How do I know which one it's being used?

Simply running pkg version -o -v | grep drm would show you all installed ports origin (in category/port form) having "drm" somewhere.
My example below. I have nvidia GPU and graphics/nvidia-drm-kmod chose graphics/nvidia-drm-61-kmod for me. And graphics/nvidia-drm-61-kmod pulles in corresponding graphics/drm-61-kmod as a dependency.

Code:

% pkg version -o -v | grep drm
graphics/drm-61-kmod               =   up-to-date with index
graphics/libdrm                    =   up-to-date with index
graphics/linux-c7-libdrm           =   up-to-date with index
graphics/nvidia-drm-61-kmod        =   up-to-date with index
graphics/nvidia-drm-kmod           >   succeeds index (index has 550.127.05)

graphics/drm-kmod port checks the version and architecture (amd64 etc.) of the base, automatically chooses newest actual port and then installs it if not yet installed.

BaronBS · Nov 30, 2024

T-Aoki said:
Because drm-*-kmod ports strongly depends on the version (at a level of specific commit) of the kernel (precisely, linuxkpi module) on which it was built. So the mis-match happenes relatively often, as linuxkpi is actively developed to support newer hardwares.
Many of kernel modules in ports tree loosely depends on kernel versions, so those can run on latest stable/14 even if it is built on 14.0-Release, but some cannot, and drm related ports are clearly the latter, thus, local builds are almost mandatory for each time you update base.

Simply running pkg version -o -v | grep drm would show you all installed ports origin (in category/port form) having "drm" somewhere.
My example below. I have nvidia GPU and graphics/nvidia-drm-kmod chose graphics/nvidia-drm-61-kmod for me. And graphics/nvidia-drm-61-kmod pulles in corresponding graphics/drm-61-kmod as a dependency.

Code:

% pkg version -o -v | grep drm graphics/drm-61-kmod = up-to-date with index graphics/libdrm = up-to-date with index graphics/linux-c7-libdrm = up-to-date with index graphics/nvidia-drm-61-kmod = up-to-date with index graphics/nvidia-drm-kmod > succeeds index (index has 550.127.05)

graphics/drm-kmod port checks the version and architecture (amd64 etc.) of the base, automatically chooses newest actual port and then installs it if not yet installed.

Yup, it makes sense, thank you for your explanation. I'm creating my build server with poudriere right now.

squidbones · Nov 30, 2024

another data point for TigerLake i5-1135G7 and i915. I was on drm-61-kmod and switching to drm-515-kmod fixed the issue just using standard pkg binaries.

Code:

Nov 30 17:34:08 sophos kernel: [drm] Got Intel graphics stolen memory base 0x4b800000, size 0x4000000
Nov 30 17:34:08 sophos kernel: drmn0: <drmn> on vgapci0
Nov 30 17:34:08 sophos kernel: vgapci0: child drmn0 requested pci_enable_io
Nov 30 17:34:08 sophos syslogd: last message repeated 1 times
Nov 30 17:34:08 sophos kernel: tgl_dmc_ver2_12.bin: could not load binary firmware /boot/firmware/tgl_dmc_ver2_12.bin either
Nov 30 17:34:08 sophos kernel: i915/tgl_dmc_ver2_12.bin: could not load binary firmware /boot/firmware/i915/tgl_dmc_ver2_12.bin either
Nov 30 17:34:08 sophos kernel: i915_tgl_dmc_ver2_12.bin: could not load binary firmware /boot/firmware/i915_tgl_dmc_ver2_12.bin either
Nov 30 17:34:08 sophos kernel: lkpi_iic0: <LinuxKPI I2C> on drmn0
Nov 30 17:34:08 sophos kernel: iicbus0: <Philips I2C bus> on lkpi_iic0
Nov 30 17:34:08 sophos kernel: iic0: <I2C generic I/O> on iicbus0
Nov 30 17:34:08 sophos kernel: lkpi_iic1: <LinuxKPI I2C> on drmn0
Nov 30 17:34:08 sophos kernel: iicbus1: <Philips I2C bus> on lkpi_iic1
Nov 30 17:34:08 sophos kernel: iic1: <I2C generic I/O> on iicbus1
Nov 30 17:34:08 sophos kernel: lkpi_iic2: <LinuxKPI I2C> on drmn0
Nov 30 17:34:08 sophos kernel: iicbus2: <Philips I2C bus> on lkpi_iic2
Nov 30 17:34:08 sophos kernel: iic2: <I2C generic I/O> on iicbus2
Nov 30 17:34:08 sophos kernel: lkpi_iic3: <LinuxKPI I2C> on drmn0
Nov 30 17:34:08 sophos kernel: iicbus3: <Philips I2C bus> on lkpi_iic3
Nov 30 17:34:08 sophos kernel: iic3: <I2C generic I/O> on iicbus3
Nov 30 17:34:08 sophos kernel: lkpi_iic4: <LinuxKPI I2C> on drmn0
Nov 30 17:34:08 sophos kernel: iicbus4: <Philips I2C bus> on lkpi_iic4
Nov 30 17:34:08 sophos kernel: iic4: <I2C generic I/O> on iicbus4
Nov 30 17:34:08 sophos kernel: lkpi_iic5: <LinuxKPI I2C> on drmn0
Nov 30 17:34:08 sophos kernel: iicbus5: <Philips I2C bus> on lkpi_iic5
Nov 30 17:34:08 sophos kernel: iic5: <I2C generic I/O> on iicbus5
Nov 30 17:34:08 sophos kernel: lkpi_iic6: <LinuxKPI I2C> on drmn0
Nov 30 17:34:08 sophos kernel: iicbus6: <Philips I2C bus> on lkpi_iic6
Nov 30 17:34:08 sophos kernel: iic6: <I2C generic I/O> on iicbus6
Nov 30 17:34:08 sophos kernel: lkpi_iic7: <LinuxKPI I2C> on drmn0
Nov 30 17:34:08 sophos kernel: iicbus7: <Philips I2C bus> on lkpi_iic7
Nov 30 17:34:08 sophos kernel: iic7: <I2C generic I/O> on iicbus7
Nov 30 17:34:08 sophos kernel: lkpi_iic8: <LinuxKPI I2C> on drmn0
Nov 30 17:34:08 sophos kernel: iicbus8: <Philips I2C bus> on lkpi_iic8
Nov 30 17:34:08 sophos kernel: iic8: <I2C generic I/O> on iicbus8
Nov 30 17:34:08 sophos kernel: drmn0: successfully loaded firmware image 'i915/tgl_dmc_ver2_12.bin'
Nov 30 17:34:08 sophos kernel: drmn0: [drm] Finished loading DMC firmware i915/tgl_dmc_ver2_12.bin (v2.12)
Nov 30 17:34:08 sophos kernel: sysctl_warn_reuse: can't re-use a leaf (hw.dri.debug)!
Nov 30 17:34:08 sophos kernel: lkpi_iic9: <LinuxKPI I2C> on drm3
Nov 30 17:34:08 sophos kernel: iicbus9: <Philips I2C bus> on lkpi_iic9
Nov 30 17:34:08 sophos kernel: iic9: <I2C generic I/O> on iicbus9
Nov 30 17:34:08 sophos kernel: [drm] Initialized i915 1.6.0 20201103 for drmn0 on minor 0
Nov 30 17:34:08 sophos kernel: VT: Driver priority 0 too low. Current 101
Nov 30 17:34:08 sophos kernel:  fbd0: not attached to vt(4) console; another device has precedence (err=17

T-Aoki · Nov 30, 2024

squidbones said:

another data point for TigerLake i5-1135G7 and i915. I was on drm-61-kmod and switching to drm-515-kmod fixed the issue just using standard pkg binaries.

Code:

Nov 30 17:34:08 sophos kernel: [drm] Got Intel graphics stolen memory base 0x4b800000, size 0x4000000
Nov 30 17:34:08 sophos kernel: drmn0: <drmn> on vgapci0
Nov 30 17:34:08 sophos kernel: vgapci0: child drmn0 requested pci_enable_io
Nov 30 17:34:08 sophos syslogd: last message repeated 1 times
Nov 30 17:34:08 sophos kernel: tgl_dmc_ver2_12.bin: could not load binary firmware /boot/firmware/tgl_dmc_ver2_12.bin either
Nov 30 17:34:08 sophos kernel: i915/tgl_dmc_ver2_12.bin: could not load binary firmware /boot/firmware/i915/tgl_dmc_ver2_12.bin either
Nov 30 17:34:08 sophos kernel: i915_tgl_dmc_ver2_12.bin: could not load binary firmware /boot/firmware/i915_tgl_dmc_ver2_12.bin either
Nov 30 17:34:08 sophos kernel: lkpi_iic0: <LinuxKPI I2C> on drmn0
Nov 30 17:34:08 sophos kernel: iicbus0: <Philips I2C bus> on lkpi_iic0
Nov 30 17:34:08 sophos kernel: iic0: <I2C generic I/O> on iicbus0
Nov 30 17:34:08 sophos kernel: lkpi_iic1: <LinuxKPI I2C> on drmn0
Nov 30 17:34:08 sophos kernel: iicbus1: <Philips I2C bus> on lkpi_iic1
Nov 30 17:34:08 sophos kernel: iic1: <I2C generic I/O> on iicbus1
Nov 30 17:34:08 sophos kernel: lkpi_iic2: <LinuxKPI I2C> on drmn0
Nov 30 17:34:08 sophos kernel: iicbus2: <Philips I2C bus> on lkpi_iic2
Nov 30 17:34:08 sophos kernel: iic2: <I2C generic I/O> on iicbus2
Nov 30 17:34:08 sophos kernel: lkpi_iic3: <LinuxKPI I2C> on drmn0
Nov 30 17:34:08 sophos kernel: iicbus3: <Philips I2C bus> on lkpi_iic3
Nov 30 17:34:08 sophos kernel: iic3: <I2C generic I/O> on iicbus3
Nov 30 17:34:08 sophos kernel: lkpi_iic4: <LinuxKPI I2C> on drmn0
Nov 30 17:34:08 sophos kernel: iicbus4: <Philips I2C bus> on lkpi_iic4
Nov 30 17:34:08 sophos kernel: iic4: <I2C generic I/O> on iicbus4
Nov 30 17:34:08 sophos kernel: lkpi_iic5: <LinuxKPI I2C> on drmn0
Nov 30 17:34:08 sophos kernel: iicbus5: <Philips I2C bus> on lkpi_iic5
Nov 30 17:34:08 sophos kernel: iic5: <I2C generic I/O> on iicbus5
Nov 30 17:34:08 sophos kernel: lkpi_iic6: <LinuxKPI I2C> on drmn0
Nov 30 17:34:08 sophos kernel: iicbus6: <Philips I2C bus> on lkpi_iic6
Nov 30 17:34:08 sophos kernel: iic6: <I2C generic I/O> on iicbus6
Nov 30 17:34:08 sophos kernel: lkpi_iic7: <LinuxKPI I2C> on drmn0
Nov 30 17:34:08 sophos kernel: iicbus7: <Philips I2C bus> on lkpi_iic7
Nov 30 17:34:08 sophos kernel: iic7: <I2C generic I/O> on iicbus7
Nov 30 17:34:08 sophos kernel: lkpi_iic8: <LinuxKPI I2C> on drmn0
Nov 30 17:34:08 sophos kernel: iicbus8: <Philips I2C bus> on lkpi_iic8
Nov 30 17:34:08 sophos kernel: iic8: <I2C generic I/O> on iicbus8
Nov 30 17:34:08 sophos kernel: drmn0: successfully loaded firmware image 'i915/tgl_dmc_ver2_12.bin'
Nov 30 17:34:08 sophos kernel: drmn0: [drm] Finished loading DMC firmware i915/tgl_dmc_ver2_12.bin (v2.12)
Nov 30 17:34:08 sophos kernel: sysctl_warn_reuse: can't re-use a leaf (hw.dri.debug)!
Nov 30 17:34:08 sophos kernel: lkpi_iic9: <LinuxKPI I2C> on drm3
Nov 30 17:34:08 sophos kernel: iicbus9: <Philips I2C bus> on lkpi_iic9
Nov 30 17:34:08 sophos kernel: iic9: <I2C generic I/O> on iicbus9
Nov 30 17:34:08 sophos kernel: [drm] Initialized i915 1.6.0 20201103 for drmn0 on minor 0
Nov 30 17:34:08 sophos kernel: VT: Driver priority 0 too low. Current 101
Nov 30 17:34:08 sophos kernel:  fbd0: not attached to vt(4) console; another device has precedence (err=17

Are you on 14.1-Release or 13.3 Release? If so, official pkg for there would work.
Because official pkgs are built on oldest supported release of the branch (not 100% sure, but would be the latest patch level [i.e., 14.1-Release-p1] for security). So if you are running the exact version, mis-matching shouldn't happen.

squidbones · Nov 30, 2024

T-Aoki said:
Are you on 14.1-Release or 13.3 Release? If so, official pkg for there would work.

Oh sorry, I just upgraded from 14.1p5 to 14.2-RELEASE when the kmod stopped working for me. The computer started life as 13.2-BETA3 so it started with drm-61-kmod from that release.

Also, I upgrade FreeBSD versions with buildworld for the OS but use the latest pkg to stay up-to-date with browsers and all their dependencies.

anh0516 · Dec 3, 2024

I just did a fresh install of 14.2-RELEASE and installed the binary drm-61-kmod package from latest. For me, it doesn't just freeze, but I get a black screen. The terminal is still responsive underneath though.

Code:

[drm] Got Intel graphics stolen memory base 0x0, size 0x0
drmn0: <drmn> on vgapci0
vgapci0: child drmn0 requested pci_enable_io
vgapci0: child drmn0 requested pci_enable_io
kbl_dmc_ver1_04.bin: could not load binary firmware /boot/firmware/kbl_dmc_ver1_04.bin either
i915/kbl_dmc_ver1_04.bin: could not load binary firmware /boot/firmware/i915/kbl_dmc_ver1_04.bin either
i915_kbl_dmc_ver1_04.bin: could not load binary firmware /boot/firmware/i915_kbl_dmc_ver1_04.bin either
drmn0: successfully loaded firmware image 'i915/kbl_dmc_ver1_04.bin'
drmn0: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4)
lkpi_iic0: <LinuxKPI I2C> on drmn0
iicbus1: <Philips I2C bus> on lkpi_iic0
iic1: <I2C generic I/O> on iicbus1
lkpi_iic1: <LinuxKPI I2C> on drmn0
iicbus2: <Philips I2C bus> on lkpi_iic1
iic2: <I2C generic I/O> on iicbus2
lkpi_iic2: <LinuxKPI I2C> on drmn0
iicbus3: <Philips I2C bus> on lkpi_iic2
iic3: <I2C generic I/O> on iicbus3
lkpi_iic3: <LinuxKPI I2C> on drmn0
iicbus4: <Philips I2C bus> on lkpi_iic3
iic4: <I2C generic I/O> on iicbus4
sysctl_warn_reuse: can't re-use a leaf (hw.dri.debug)!
lkpi_iic4: <LinuxKPI I2C> on drm1
iicbus5: <Philips I2C bus> on lkpi_iic4
iic5: <I2C generic I/O> on iicbus5
lkpi_iic5: <LinuxKPI I2C> on drm2
iicbus6: <Philips I2C bus> on lkpi_iic5
iic6: <I2C generic I/O> on iicbus6
lkpi_iic6: <LinuxKPI I2C> on drm4
iicbus7: <Philips I2C bus> on lkpi_iic6
iic7: <I2C generic I/O> on iicbus7
[drm] Initialized i915 1.6.0 20201103 for drmn0 on minor 0
VT: Driver priority 0 too low. Current 101
fbd0: not attached to vt(4) console; another device has precedence (err=17)

Exactly the same problem.

Also solved by installing drm-515-kmod instead.

T-Aoki · Dec 3, 2024

anh0516 said:
I just did a fresh install of 14.2-RELEASE and installed the binary drm-61-kmod package from latest. For me, it doesn't just freeze, but I get a black screen. The terminal is still responsive underneath though.

Official pre-built pkgs are built on oldest supported release of the branch, for 14.*, currently 14.1-Release.
And pre-built pkgs which depends on linuxkpi.ko like graphics/drm-*-kmod are quite fragile on version mis-match between themselves and linuxkpi.ko.
Sometime hesitates to load complaining version mis-match, sometime mis-behaves without any messages like black screen.
To be 100% sure that both linuxkpi.ko and graphics/drm-*-kmod matches, building/installing from ports is strongly (almost mandatorily) suggested.

psmet · Dec 4, 2024

I've got a similar problem, and building from ports didn't solve it, as it usually does. Still a black screen after reboot.

But loading the newly built module *AFTER* boot, using kldload works fine for some reason.
So I removed i915kms from kldlist in rc.conf and added
/sbin/kldload i915kms
In rc.local

And ...it works. Still don't understand why :/

qapsl0ck · Dec 4, 2024

After upgrading to 14-2 had simular problem. Solved it with:
pkg install drm-515-kmod

This removed:
drm-61-kmod: 6.1.92
drm-kmod: 20220907_3

After this, kldload i915kms works without hanging.
I added the line 'kld_list="i915kms"' back again in /etc/rc.conf, and the reboot went without any problems.

gnath · Dec 5, 2024

qapsl0ck said:
pkg install drm-515-kmod

Considering the above best possible solution for my working systems for now, I shall go ahead for 14.2-RELEASE.

jiten · Dec 5, 2024

Is problem related to this ?

FreeBSD 14.2-RELEASE Errata

FreeBSD is an operating system used to power modern servers, desktops, and embedded platforms.

www.freebsd.org

drm-kmod packages compiled on FreeBSD 14.1 resultin the text console being inoperative when the kernel module isloaded. Recompiling the package from the ports tree will restorethe lost functionality. This issue will also resolve itself after the FreeBSD 14.1 EoL, when packages for 14-STABLE will start beingbuilt on FreeBSD 14.2-RELEASE.

yjqg6666 · Friday at 1:29 AM

How about always building the drm-kmod related pkg binaries(pkg.freebsd.org) using the latest release?

chrbr · Friday at 4:15 AM

yjqg6666 said:
How about always building the drm-kmod related pkg binaries(pkg.freebsd.org) using the latest release?

I am sure that there are users who have reasons to stick with FreeBSD 14.1-RELEASE. If drm-kmod would be build for the latest release but fail with FreeBSD 14.1-RELEASE the issue would not have been solved but just affect others.