Why isn't there a driver attached to this device?
rkoberman at gmail.com
Sun Feb 21 05:48:40 UTC 2021
Very odd. Oddly, I didn't find any source files and the module was in
/boot/kernel.old. I'm simply baffled as to how it got there. It is dated
02-Feb, so it's from my last build. Best guess is that it was pulled for
some reason. With SVN, I'd look at the sources as of 2/2/21, but I'm just
starting on git. Perhaps you might have some idea for tracking it down.
Perhaps I botched a pull and got main branch instead of stable/13. I'm
certainly running the correct version today.
Sorry for the confusion.
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkoberman at gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
On Fri, Feb 19, 2021 at 10:36 PM Yuri Pankov <yuripv at yuripv.dev> wrote:
> Kevin Oberman wrote:
> > On Fri, Feb 19, 2021 at 2:54 AM Yuri Pankov <yuripv at yuripv.dev> wrote:
> >> Steven Friedrich wrote:
> >>> I am surprised this device has no driver attached. I do include
> >> coretemp in
> >>> my kernel.
> >>> This is from pciconf -lv
> >>> none0 at pci0:0:18:0: class=0x118000 card=0x843f103c chip=0xa3798086
> >>> rev=0x10 hdr=0x00
> >>> vendor = 'Intel Corporation'
> >>> device = 'Cannon Lake PCH Thermal Controller'
> >>> class = dasp
> >> That's different from coretemp(4), and should be driven by pchtherm(4),
> >> but it seems to be only in 13 and not backported to stable/12:
> >> _______________________________________________
> > I see the kernel module on my 12-STABLE system, so I would expect it in
> > 12.3.
> Interesting, checking out stable/12 branch, I don't see any files named
> \*pchtherm\*, nor does grep find any matching contents.
More information about the freebsd-questions