[05:47] <Bashing-om> !info automake yakkety
[05:53] <Bashing-om> That's all Folks - for me; G nite
[07:11] <ducasse> morning
[13:08] <BluesKaj> Hey folks
[18:23] <Bashing-om> A rained out Tuesday; and thanks - I have IRC to keep me company :)
[18:26] <OerHeks> fiber-love -D
[18:26] <OerHeks> cat6-friends
[18:40] <Bashing-om> Never ever going back to non internet - nor to a Dial up connection !
[18:41] <OerHeks> i would drop TV over internet too
[18:48] <Bashing-om> 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] <Bashing-om> 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] <OerHeks> as of lm-sensors 3.4.0  there are fixes https://github.com/groeck/lm-sensors/blob/master/CHANGES#L12
[19:00] <OerHeks> so i guess the driver is included?
[19:03] <Bashing-om> OerHeks: Thanks , back to homework :) - ii  lm-sensors     1:3.4.0-2 - .
[19:03] <OerHeks> that was 2015
[19:03] <OerHeks> modprobe w83627ehf ?
[19:07] <Bashing-om> that is the source of my inquiry -> " modprobe: ERROR: could not insert 'w83627ehf': Device or resource busy " .
[20:42] <Bashing-om> Smoke break - smokers draw one .
[20:46] <daftykins> device must be claimed by another module already?
[20:48] <Bashing-om> 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] <daftykins> share? you can't have two active drivers :D you gotta unload the other / blacklist it
[20:52] <Bashing-om> 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] <Bashing-om> daftykins: I looking at ACPI issues here so I am some kind of careful .
[20:55] <daftykins> BIOS locking it o0 that doesn't make much sense
[21:12] <Bashing-om> 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] <daftykins> device ID?
[21:32] <Bashing-om> daftykins: Old docs " modprobe w83627ehf force_id=0x8860 " . And old docs do not relate now to verifying " 8860 " in systemd .
[21:33] <daftykins> hrmm
[21:36] <Bashing-om> daftykins: Old docs - prior to the fan control split from lm-sensors .. file locations and addressing no longer apply .