[05:47] !info automake yakkety [05:47] automake (source: automake-1.15): Tool for generating GNU Standards-compliant Makefiles. In component main, is optional. Version 1:1.15-4ubuntu1 (yakkety), package size 497 kB, installed size 1493 kB [05:53] That's all Folks - for me; G nite [07:11] morning [13:08] Hey folks === EriC^ is now known as EriC^^ [18:23] A rained out Tuesday; and thanks - I have IRC to keep me company :) [18:26] fiber-love -D [18:26] cat6-friends [18:40] Never ever going back to non internet - nor to a Dial up connection ! [18:41] i would drop TV over internet too [18:48] I "might" watch a movie - IF the commercials are not too heavy - maybe ; OR if the other half request that quality time to share a movie event . Otherwise. NO ! [18:53] OerHeks: Can I get into your smart bucket ? lm-sensors -> w83627ehf driver -> id=0x8860 (??) . How can I confirm this chip ID in release 16.04 ? Old docs are driving me nuts . [19:00] as of lm-sensors 3.4.0 there are fixes https://github.com/groeck/lm-sensors/blob/master/CHANGES#L12 [19:00] so i guess the driver is included? [19:03] OerHeks: Thanks , back to homework :) - ii lm-sensors 1:3.4.0-2 - . [19:03] that was 2015 [19:03] modprobe w83627ehf ? [19:07] that is the source of my inquiry -> " modprobe: ERROR: could not insert 'w83627ehf': Device or resource busy " . [20:42] Smoke break - smokers draw one . [20:46] device must be claimed by another module already? [20:48] daftykins: OH for sure is claimed . now I want to tell the system to share it ... Telling the system to ignore the error scares me ! [20:49] share? you can't have two active drivers :D you gotta unload the other / blacklist it [20:52] Uh HUh . Agreed . but Bios has the claim , I do not want that I defeat what bios has set up But I want my cake too and run lm-sensors :) [20:54] daftykins: I looking at ACPI issues here so I am some kind of careful . [20:55] BIOS locking it o0 that doesn't make much sense [21:12] daftykins: Well, Lots I have to learn yet with this can of worms . but looking at voltage and clocking control from bios that the driver w83627ehf also wants to access . I am aware of a couple of possible things I can do . one of which I am not comforable with, and the other; I want to know the ID of the chip that w83627ehf is accessing . [21:28] device ID? [21:32] daftykins: Old docs " modprobe w83627ehf force_id=0x8860 " . And old docs do not relate now to verifying " 8860 " in systemd . [21:33] hrmm [21:36] daftykins: Old docs - prior to the fan control split from lm-sensors .. file locations and addressing no longer apply .