The files being uploaded are the current versions of the files from
argon40. These files are being archived as I want to be able to
reference them from time to time. Also I can compare the files that
were ship with the proto type.
Worked once, will not work again. Build occurs, dkms reports that the
build of ./src/oneUpPower.ko failed. Kernel module is being generated,
but not located anywhere it can be found.
Adding a coniguration file (/etc/sysmon.ini). This will allow users to
no monitor the temperature of speciic drives by ignoring them, as well
as ignoring the performance from specific drives.
For instance on a system running mdraid, you could ignore performance on
all of the drives that make up the raid array, and ignore the
temperature of the raid device.
The default value for shutdown is less than 5% of battery life left.
Once the system hits this value (or the one specified by the user) the
system will shutdown.
The soc_shutdown value can be changed to 0 to disable this feature, just
realise that the system will lose power and unsafely shutdown.
Also added install and remove functionality.
Apparently things start differently with trixie, so modified the system
monitor code to keep trying to allocate the resources it needs (and
adapter and a client to the i2c bus). This mades the code work,
and startup is not affected.
Changes made to the monitor code to remove all warnings from
systemsupport.py. Note there are warnings in oneUpMon, however these do
not appear to be valid, as some of them complain about attributes not
existing, when they clearly do (Qt.AlignBottom for instance)
Overall cleanup, and modificaton to the disk chart. System tracks Byte,
KiB and MiB transfer rates. Can't realld support GiB because I'm no
sure the PCIe bus can handle that.
Modifed the Y-Axis for disks so it displays the data on the closest
power of 2 scale. Seems to be a reasonable way to modify the scale so we
can actually see some of the smaller writes.
Automatically shutdown the system when the battery hits 5% left if the
system is not plugged in. The shutdown does *not* save data, so might
want to look into how to make it save data (or possibly just generate a
warning.
I noticed that Argon40 updated the scripts... they must be getting ready
for release, so I grabbed the older ones off of the original boot device
for my Argon OneUp. Will add anything else here that I find as well.
Need to perform code cleanup, and make sure startup of the driver
contains everything it needs to properly verify the status of the
battery.
Could use code to get the voltage etc, however I don't see that code in
the argon40 python stuff so I'd have to investigate the I2C device.
Jeff Curless