Robert: Wow - thank you! I'll give it a shot.
Regards, David Stein On Sunday, December 10, 2017 at 7:29:50 PM UTC-5, RobertCNelson wrote: > > On Sun, Dec 10, 2017 at 5:50 PM, David Stein <[email protected] > <javascript:>> wrote: > > I'm working with an X15, and the fan is driving me crazy. > > > > I'm using the recommended heatsink and fan from Digi-Key (the 5V F251R: > > https://www.digikey.com/products/en?keywords=X15FANKIT-ND ). The fan > works, > > but it constantly turns on and off on what seems to be a completely > random > > basis. Has no relationship with actual CPU load, either. > > > > I'm delving into Debian's fan control package, lm-sensors, and I've > found > > this: > > > > sensors > > > > > > ...which outputs this: > > > > gpio_fan-isa-0000 > > Adapter: ISA adapter > > fan1: 0 RPM (min = 0 RPM, max = 13000 RPM) > > > > tmp102-i2c-0-48 > > Adapter: OMAP I2C adapter > > temp1: +41.4°C (high = +160.0°C, hyst = +150.0°C) > > > > > > That's certainly informative, but those set points are insane: I don't > want > > it getting anywhere near 160°C, or even 150°C for that matter. I presume > > that someone was aiming for Fahrenheit values. These settings also > indicate > > a problem: if tmp102-i2c-0-48 were actually controlling the fan, it > would > > never turn on - it would probably be fried long before it hit either of > > those values. > > > > The settings command allows me to query both devices for settable > > properties: > > > > gpio_fan-isa-0000 > > Adapter: ISA adapter > > fan1: > > fan1_input: 13000.000 > > fan1_min: 0.000 > > fan1_max: 13000.000 > > > > tmp102-i2c-0-48 > > Adapter: OMAP I2C adapter > > temp1: > > temp1_input: 42.375 > > temp1_max: 160.000 > > temp1_max_hyst: 150.000 > > > > > > And I can also change them by creating /etc/sensors.d/x15-config with > the > > following: > > > > chip "tmp102*" > > set temp1_max 41 > > set temp1_max_hyst 39 > > > > > > After either running "sensors -s" to reload settings or just rebooting, > the > > sensors -u command shows that tmp102-i2c has accepted the override > values. > > Unfortunately, it doesn't affect the annoying fan behavior one bit. > Reported > > CPU temperature is over 41, so it should run constantly until it's under > > 39... no dice. Same behavior. > > > > At this point, I can't figure out what is actually controlling the fan, > > especially not in this manner. I'm ready to chalk it up to either a > flaky > > fan or a faulty GPIO or... something. > > > > Anyone have any ideas? > > So here's the patch: > > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/arch/arm/boot/dts/am57xx-beagle-x15.dts?h=v4.15-rc2&id=d723cfeafc7b4c73e89ed3d4b1a4d747e990872c > > > You'll need to patch the dtb to play* around with different C values > for cpu_trips/thermal_zones.. The values originally used where just a > best guess. (the am5728 is rated for -40 <-> 105 C) > > You can use dtb-rebuilder for this: > > https://github.com/RobertCNelson/dtb-rebuilder > > Use either the 4.4-ti, 4.9-ti, or 4.14-ti branches matching your > booting kernel.. > > Regards, > > -- > Robert Nelson > https://rcn-ee.com/ > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/80f5ac6f-e4eb-4d7f-9d2f-4dbdc9a1d19f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
