i2c fun stuff (Previous message: [XCSSA] cases with chassis intrusion sensor)

[xcssa@xcssa.org]

------=_Part_62255_10208484.1154388366208
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hummm...... read the 'cases with chassis intrusion sensor' and got to
thinking if i2c stuff and some other software (open source ?) could be used
to do a harddrive analysis on the fly.  Useful for when one is at computer
shows to see what you're getting before getting the harddrive.
Not shure on the software, but the hardware side would include a combination
of  usb 2.0 to ide/sata <
http://www.scythe-usa.com/product/acc/013/scupc1000.html >; some type of
either wireless connection to a remote home box (pda/phone via unix
pipe/netcat/ssh && remote xwindows) or non-geeky pda/handheld w/ appropriate
HD analysis software installed.
Comments?

Craig

.......

As far as the alarm.. to detect it you need to load up your kernel modules
> (if
> not already there) for lmsensor/i2c signal I/O. First whack.. just try
> running the command "sensors -f" first, to see if your system is already
> lmsensor/i2c aware. In the old days, we had to watch for alarm status
> change
> on the mobo (when the case was opened) by monitoring the /proc variable:
> /proc/sys/dev/sensors/w83781d-isa-0290/alarms
>
> For example. Much easier now though.
>
> Not sure what i2c chipset you have... or what it might map to in /proc
> or /sys. But using the sensors command, or a desktop app such as gkrellm
> or
> such is much easier (and nicer). I think that there's also a daemon that
> you
> can use to watch the system.. but I have not played with any of that.
>
........

------=_Part_62255_10208484.1154388366208
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<div><br>
Hummm...... read the 'cases with chassis intrusion sensor' and got to
thinking if i2c stuff and some other software (open source ?) could be
used to do a harddrive analysis on the fly.&nbsp; Useful for when one
is at computer shows to see what you're getting before getting the
harddrive.<br>
Not shure on the software, but the hardware side would include a
combination of&nbsp; usb 2.0 to ide/sata &lt;
<a href="http://www.scythe-usa.com/product/acc/013/scupc1000.html">http://www.scythe-usa.com/product/acc/013/scupc1000.html</a> &gt;; some
type of either wireless connection to a remote home box (pda/phone via
unix pipe/netcat/ssh &amp;&amp; remote xwindows) or non-geeky
pda/handheld w/ appropriate HD analysis software installed.<br>
Comments?<br>
<br>
Craig<br>
<br>
....... <br>
</div><br>
<blockquote style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;" class="gmail_quote">As far as the alarm.. to detect it you need to load up your kernel modules (if <br>
not already there) for lmsensor/i2c signal I/O.  First whack.. just try <br>
running the command &quot;sensors -f&quot; first, to see if your system is already <br>
lmsensor/i2c aware.  In the old days, we had to watch for alarm status change <br>
on the mobo (when the case was opened) by monitoring  the /proc variable:<br>
	/proc/sys/dev/sensors/w83781d-isa-0290/alarms<br>
  <br>
For example.  Much easier now though.<br>
  <br>
Not sure what i2c chipset you have... or what it might map to in /proc <br>
or /sys.  But using the sensors command, or a desktop app such as gkrellm or <br>
such is much easier (and nicer).  I think that there's also a daemon that you <br>
can use to watch the system.. but I have not played with any of that.<br>
</blockquote>
<pre>........<br></pre>

------=_Part_62255_10208484.1154388366208--