Seems as if my Fuel is also beginning to suffer from dying battery syndrome. It's not yet got to the level of losing its MAC like jaan-jap's blue Fuel did last year, however its timekeeping is becoming ever more erratic, and yesterday it also lost the env monitoring setting as well.
For now, I've noted down the MAC so that I can set it back to what it was in the event of disaster, and the clock issue has been worked around for now with a startup script to set the clock from another system on my network. However, the env monitoring issue it has developed is more annoying as the setting keeps turning itself back on, meaning I've currently got to remove the case, hook up the L1 to my laptop and switch it off to prevent the system powering down after 30 seconds (slower replacement fans).
As a short term fix, does anyone know if I can use either of the external serial ports to control the L1? I did try them, but without any joy (unless I'm doing something wrong). Alternatively, has anyone ever used the RJ11 socket on the back labelled L1? Just trying to find a short term workaround which doesn't involve me having to pull the side off my Fuel every time I want to power it up.
Of course, longer term I'm going to have to look at replacing the battery (or batteries as it may be). I think the replacement one for the clock is the ST Micro M4T28-BR12SH1. However, I'm not sure if this has anything to do with the env monitoring setting changing itself. Hope the battery in the Dallas chip isn't also failing, although I wouldn't be surprised.
For now, I've noted down the MAC so that I can set it back to what it was in the event of disaster, and the clock issue has been worked around for now with a startup script to set the clock from another system on my network. However, the env monitoring issue it has developed is more annoying as the setting keeps turning itself back on, meaning I've currently got to remove the case, hook up the L1 to my laptop and switch it off to prevent the system powering down after 30 seconds (slower replacement fans).
As a short term fix, does anyone know if I can use either of the external serial ports to control the L1? I did try them, but without any joy (unless I'm doing something wrong). Alternatively, has anyone ever used the RJ11 socket on the back labelled L1? Just trying to find a short term workaround which doesn't involve me having to pull the side off my Fuel every time I want to power it up.
Of course, longer term I'm going to have to look at replacing the battery (or batteries as it may be). I think the replacement one for the clock is the ST Micro M4T28-BR12SH1. However, I'm not sure if this has anything to do with the env monitoring setting changing itself. Hope the battery in the Dallas chip isn't also failing, although I wouldn't be surprised.
Systems in use:
- Nitrogen : R10000 195MHz CPU, 384MB RAM, SolidIMPACT Graphics, 36GB 15k HDD & 300GB 10k HDD, 100Mb/s NIC, New/quiet fans, IRIX 6.5.22
- Lithium : R14000 600MHz CPU, 4GB RAM, V10 Graphics, 36GB 15k HDD & 300GB 10k HDD, 1Gb/s NIC, New/quiet fans, IRIX 6.5.30
Other system in storage: R5000 200MHz, 224MB RAM, 72GB 15k HDD, PSU fan mod, IRIX 6.5.30
- Nitrogen : R10000 195MHz CPU, 384MB RAM, SolidIMPACT Graphics, 36GB 15k HDD & 300GB 10k HDD, 100Mb/s NIC, New/quiet fans, IRIX 6.5.22
- Lithium : R14000 600MHz CPU, 4GB RAM, V10 Graphics, 36GB 15k HDD & 300GB 10k HDD, 1Gb/s NIC, New/quiet fans, IRIX 6.5.30
Other system in storage: R5000 200MHz, 224MB RAM, 72GB 15k HDD, PSU fan mod, IRIX 6.5.30