Rofl really?! well I dont think thats being polled for any info as per the webgui at least.
If it is then I have no idea wtf is going on =P

Is the LM75 the actual temp sensor itself as well? if it is then measuring the temperature on that location of the board is purely a freaking ambient temp - "inside of the cube" temp ROFL! Thats quite useless, thanks KNC.

But if it uses a remote temp line then where that remote temp thingy is... is a mystery, I would think somewhere near the ASIC package.

Whats funny is, if the LM75 itself is the thermometer and the DCDC's temps are just really the DCDC temps then ... we have NO fucking clue what the actual ASIC die temps are =P    ..... engineering at its finest....

Please attempt installing the new released v.99a firmware .bin file here:
https://github.com/GenTarkin/Titan/releases/tag/v.99a

It wont attempt to install wget anymore, should have no problems with this release.
Upgrade should finish in a few mins.

Announcing new firmware v.99a:
Quick, incremental fix for failed installs when hanging on wget installation(apt-get syncing etc...)
No longer relys on wget being installed to download files when using STATUS->upgrade.

https://github.com/GenTarkin/Titan/releases/tag/v.99a

HAHA! Figures, well it must have a remote temp sensor somewhere. Would have to trace the traces... which being a multilayer is impossible.
I bet the sensor is somewhere or in the actual ASIC package.

It would be super retarded if KNC just put that there and the sensor was close but all it did was measure ambient, lol Id wanna burn their farm down then, oh wait I already want to...

Alright, found a way to actually download the file using curl despite the obscure URL which is why I had problems w/ curl previously. I will code up a new upgrade method and package and make a new incrimental release. Will do away w/ the questionable reliability of sync'ng apt and trying to install wget ... yay!

BTW, if more and more people experience issues w/ wget installing, then for the next release Im gonna go ahead and remove the upgarde button option located beneath my firmware version on status page. People will have to upgrade using .bin file method instead.

The pages are already correctly labeled LOL! DCDC = VRM's ... loosely interchanged to refer to the same thing.
The temperature column on the status page grabs those temps directly from a LM75 sensor... I dont know where this sensor is on the board, could u inspect the underside of the board perhaps? maybe there is 1 LM75 sensor mounted beneath the ASIC package. Its reading temps through the board, or maybe somehow the LM75 is integrated within the ASIC package.
But there has to be one LM75 sensor somewhere on these damn boards.
Either way, I suspect its an external sensor for the ASIC package. It functions to readout external package temps which are usually a good 10-30C less than actual die temps.

Out of curiousity how much did your temps change by when u slid the HSF around?
I have 2 theories,
1. when sliding HSF around this could potentially change airflow caused by your hand etc... and therefore the DCDC's were being cooled more or not depending on that airflow aversion.
2. If slid the HSF caused temperatures to skyrocket for a short period the dies may have went into a limp mode to avoid being blown up.

I suspect there is no on die temp sensor, otherwise we would see it being used. We arent.
Hey vegas, w/ ur thermal sensor thing, can you read temps from atop the base of the HSF while its hashing? Actually, if u could aim the laser at the package underneath the heatsink as its hashing, that would be really telling. If its close to the readout of TEMPERATURE on status page then the ASIC is using a single external package temp monitor. (thats already my suspicioun anyways, but it would prove the theory)
What I wish we knew was the TDELTA between the dies & the package temp sensor. If I knew what that DELTA was on average, I could code it into the firmware to reflect the correct average temp of the dies.

Bummer, do you only have 1 titan or more? If more then have you tested it on the others? Also, what method is the Pi hooked up to internet, wifi or eth?

Lets not confuse things, dies = physical seperated pieces of silicon.
cores = logical/functional seperation of logic inside dies.

Well thats odd. Either way, in the source code, the 2 temp fields are derived from reading the DCDC's internal temperature register.
The temperature shown in status page under "Temperature" column is derived from LM75's temperature register. Is LM75 the FPGA?... Im not sure but after seeing this: http://datasheets.maximintegrated.com/en/ds/LM75.pdf
If that is identical to what our LM75 is ... then Im inclined to think the LM75 is some sort of external temp sensor that maybe sits as close as they can to their respective places around the dies?

I dont see anything labeled LM75 on the picture u showed, are there any surface mount pieces on the bottom side of the PCB? Maybe LM75 is integrated into the package somehow, doubt it tho. Im just guessing tho =)

That makes no sense. The board is clearly not laid out that way. It has 4 dies & 2 VRM's per die.
It would be extremely odd if each die had 2 internal temp sensors. It makes more sense that each VRM has a temp sensor.

After looking at the docs for those DCDC's, they do have internal temperature monitors and they are read over pmbus. Im almost certain this is the data thats polled for DCDC temp's we see in webgui.

It should only take a good 5mins or so... Not 2 hrs unless ur inet is shit or your SD card is dead or ur inet is crap to the pi. If its hanging there that means apt-get is failing to sync & download wget. =(
If thats happening to a lot of installs, I may have to rethink the whole upgrade process.
All I can say is hit browser back button and try upgrading w/ the .bin file again.

UPDATE, small error found in previous v.99 upgrade. For anyone that has updated so far, please reapply the .bin found here:
https://github.com/GenTarkin/Titan/releases/tag/v.99

BTW, as of now the enable / disable lighttpd option under SYSTEM tab works =)

ANNOUNCING v.99 firmware:
https://github.com/GenTarkin/Titan/releases/tag/v.99

Release notes:

Changes for v.99:
After a failed original v.99 release, this is the new version with fixes for OTA & .bin upgrades!!

NOTE: If upgrading from v.98 via OTA, it "WILL" say theres an error in red letters and show error: as error result. But, if everything above the red letters doesnt state an error then its safe to reboot - there was no error. If upgrading using .bin file, there should be no issues.

NOTE: if anyone upgraded to v.99 prior to this new release, you will need to upgrade again using the .bin file listed on the page linked above!

Implementation of new graphics. Removal of KNC branding. Rewording of warning message on SYSTEM page.
Implemented auto increase of die clocks which have been underclocked due to DCDC overheat.
Created upgrade packages to allow installing my firmware via SYSTEM -> UPGRADE(knc's firmware upgarde method).
Various code fixes for monitoring script, donations & webgui.
Creating Backup now saves voltages, die clocks & minername. Minername now saved as part of backup filename.
Branding now enabled for all builds.
Groundwork started for enabling / disabling lighttpd access logging(disabled saves SD card life).
NOTES:
.bin file can be used to upgarde from STOCK KNC 2.00 firmware, the process takes a good few minutes.
.img file will be uploaded on request but is no longer needed really due to .bin being able to upgrade stock firmware to my modified firmware.
If upgrading from previous versions of my firmware then using the upgrade button on status page should upgrade to v.99.

Reboot after upgrading!
Note: if upgrade happens to fail repeatedly then redownload full v.98 img and attempt upgrade again.

ANNOUNCING v.99 firmware:
https://github.com/GenTarkin/Titan/releases/tag/v.99

Release notes:
Changes for v.99:
After a failed original v.99 release, this is the new version with fixes for OTA & .bin upgrades!!

NOTE: If upgrading from v.98 via OTA, it "WILL" say theres an error in red letters and show error: as error result. But, if everything above the red letters doesnt state an error then its safe to reboot - there was no error. If upgrading using .bin file, there should be no issues.

NOTE: if anyone upgraded to v.99 prior to this new release, you will need to upgrade again using the .bin file listed on the page linked above!

Implementation of new graphics. Removal of KNC branding. Rewording of warning message on SYSTEM page.
Implemented auto increase of die clocks which have been underclocked due to DCDC overheat.
Created upgrade packages to allow installing my firmware via SYSTEM -> UPGRADE(knc's firmware upgarde method).
Various code fixes for monitoring script, donations & webgui.
Creating Backup now saves voltages, die clocks & minername. Minername now saved as part of backup filename.
Branding now enabled for all builds.
Groundwork started for enabling / disabling lighttpd access logging(disabled saves SD card life).
NOTES:
.bin file can be used to upgarde from STOCK KNC 2.00 firmware, the process takes a good few minutes.
.img file will be uploaded on request but is no longer needed really due to .bin being able to upgrade stock firmware to my modified firmware.
If upgrading from previous versions of my firmware then using the upgrade button on status page should upgrade to v.99.

Reboot after upgrading!
Note: if upgrade happens to fail repeatedly then redownload full v.98 img and attempt upgrade again.

Hrm... have copies of the monitordcdc.log any chance? I really cant think of how its related to my firmware build =/
Sounds like a bfgminer issue..

After some issues encountered w/ my original v.99 build, Im hoping they are resolved and being tested now. If all goes well v.99 will be available soon =)

Yes, I disabled the update. Also, there is a gigantic issue w/ the ugprade button, I didnt realize this but wget was failing to install on my initial upgrade scripts etc.... I will be rereleasing the "upgrade" package for v.98 & v.99 once its fixed. I will then reenable v.99 as well =)
If you flashed my full v.98 img, it should be unaffected.

Sorry for the confusion.

Will post when they are ready to rollout.

Awesome!! Thanks!



opinions? I like =)

Well, the background logo is specified in body tag and I dont see any opacity setting for a background image. Seems in order to do that the image would have to be thrown in a div in all html pages and the addition made in the style.css file. Which I dont have time to do atm. LOL