Tiny Core Linux
Tiny Core Base => TCB Talk => Topic started by: emilandreseniii on February 07, 2014, 11:20:06 AM
-
Greetings All,
I've installed watchdog-3.8.10-tinycore.tcz and I see the drivers under /usr/local/lib/modules/3.8.10-tinycore/kernel/drivers/watchdog, but when I execute "find / | grep watchdog" I don't see any files for a watchdog daemon. I'm working on getting the hardware watchdog on an Intel Atom (DN2800 CedarTrail) running, which uses I believe uses iTCO driver.
Question: Has anybody got a hardware watchdog up and running in TinyCore and if so do you have any tips? I'm wondering
* Is there a watchdog daemon implementation available in the tcz TinyCore repo? (I'm guessing I need to compile one)
* Do I pass nmi_watchdog=1 on the grub boot line? (Was necessary to get it working with Fedora and this should work the same way for the TC kernel yes?)
* I see "iTCO_wdt.ko.gz" and "iTCO_vendor_support.ko.gz" in the watchdog driver list, i'm guessing I need to load both modules?
Thanks,
Emil
-
"find / | grep watchdog"
Redundant "grep", use
find / -name "*watchdog*"
* Do I pass nmi_watchdog=1 on the grub boot line? (Was necessary to get it working with Fedora and this should work the same way for the TC kernel yes?)
According to
https://www.kernel.org/doc/Documentation/kernel-parameters.txt
"1" does not look like a valid parameter.
* I see "iTCO_wdt.ko.gz" and "iTCO_vendor_support.ko.gz" in the watchdog driver list, i'm guessing I need to load both modules?
In general, you can use "modinfo foo" to get info for modules, incl. dependencies and parameters.
Documentation for watchdog is available here:
https://www.kernel.org/doc/Documentation/watchdog/
-
Hi tinypoodle,
Yeah, "find / | grep .." bad habit :-)
I found the nmi_watchdog param info here: http://www.cs.fsu.edu/~baker/devices/lxr/http/source/linux/Documentation/nmi_watchdog.txt On Fedora the watchdog doesn't seem to fire without that param when I tested it.
When I run "modinfo iTCO_wdt" I just get "filename: iTCO_wdt", but I haven't installed it yet so i'll try that next.
I'm guessing the standard linux system watchdog hasn't been ported to TC yet so I was going building that:
http://linux.die.net/man/8/watchdog
http://ibiblio.org/pub/linux/system/daemons/watchdog/
-
Hi emilandreseniii
When I run "modinfo iTCO_wdt" I just get "filename: iTCO_wdt",
It seems modinfo just echos back whatever you typed rather than displaying a not found message.
-
I found the nmi_watchdog param info here: http://www.cs.fsu.edu/~baker/devices/lxr/http/source/linux/Documentation/nmi_watchdog.txt
Then likely one of the doc sources is inaccurate or outdated.
When I run "modinfo iTCO_wdt" I just get "filename: iTCO_wdt", but I haven't installed it yet so i'll try that next.
No sense of running a command on an inexistent file... ::)
-
Hi emilandreseniii
When I run "modinfo iTCO_wdt" I just get "filename: iTCO_wdt",
It seems modinfo just echos back whatever you typed rather than displaying a not found message.
If exists, expected value for filename would be its path.
-
Thanks tinypoodle! I don't often work with kernel modules :-) Looks like it does depend on iTCO_vendor_support which loads automatically with iTCO_wdt.
root@box:/usr/local/lib/modules/3.8.13-tinycore/kernel/drivers/watchdog# modinfo iTCO_wdt.ko.gz
filename: iTCO_wdt.ko.gz
description: Intel TCO WatchDog Timer Driver
author: Wim Van Sebroeck <wim@iguana.be>
license: GPL
vermagic: 3.8.13-tinycore SMP mod_unload 486
parm: turn_SMI_watchdog_clear_off:Turn off SMI clearing watchdog (depends on TCO-version)(default=1)
parm: nowayout:Watchdog cannot be stopped once started (default=0)
parm: heartbeat:Watchdog timeout in seconds. 5..76 (TCO v1) or 3..614 (TCO v2), default=30)
depends: iTCO_vendor_support
root@box:/usr/local/lib/modules/3.8.13-tinycore/kernel/drivers/watchdog# modprobe -a iTCO_wdt.ko.gz
root@box:/usr/local/lib/modules/3.8.13-tinycore/kernel/drivers/watchdog# lsmod
Module Size Used by Not tainted
iTCO_wdt 12288 0
iTCO_vendor_support 12288 1 iTCO_wdt
mperf 12288 0
cpufreq_stats 12288 0
cpufreq_powersave 12288 0
cpufreq_userspace 12288 0
cpufreq_conservative 12288 0
ppdev 12288 0
parport_pc 24576 0
parport 24576 2 ppdev,parport_pc
squashfs 24576 110
ac 12288 0
battery 16384 0
loop 20480 220
pcspkr 12288 0
microcode 12288 0
pcnet32 24576 0