Batteries
in [Mandrake]
|
From: Moe Trin on 1 Oct 2007 21:18 On Mon, 01 Oct 2007, in the Usenet newsgroup alt.os.linux.mandrake, in article <nb_Li.3281$Hb2.118(a)trndny07>, Adam wrote: >Moe Trin wrote: >>>> Where might the air be coming in? Gaps around the drive[s]? >>> I'd guess from the vent holes in the right side of the case. This >>> is a vertical tower, ATX form factor. >> >> That doesn't sound like the ideal solution. > >It doesn't? Exhaust fan on left side of case pulls air in through right >side of case and over HDs. The description above didn't read that way. >> What's this??? Another 5 kilo bag of salt??? > >Sorry, that one went right over my head. Some people talk about taking things with a grain of salt. Some userland applications require more than that - and I'm on a reduced sodium diet. >System temperatures now seems to be pretty steady at: > >M/B Temp: +40�C (low = +15�C, high = +40�C) sensor = thermistor >CPU Temp: +28�C (low = +15�C, high = +45�C) sensor = diode >/dev/hda: SAMSUNG SP0411N: 25�C What is room temperature like? 25C = 77F (28C = 82F) sounds a bit low for operating components. >/dev/hdb: MAXTOR 6L020J1: 41�C That's more what I would expect >Maxtor HD's spec for operating temperature is 5-55C. Those are supposed to be ambient, rather than internal. >After a LOT of work, I found it. It's by the top of the CPU heatsink, >half under it. IT87??F (partially covered by plastic frame that CPU >fan/heatsink attaches to), probably an ITE 8705F, which is a Super I/O >chip. (And yes, I put thermal compound on the CPU before reattaching >the heatsink.) Looks like everything's now in spec except maybe the >motherboard is occasionally one degree over according to 'sensor'. A quick google turns up rather conflicting data, as if the chip is using an internal or (up to) two external sensors (which sound like thermistors). I can't find a manufacturer's data sheet. >BTW this printer (HP Color LaserJet 5 if anyone's forgotten) seems to be >drawing power even when it's switched off, What indication? >but the manual doesn't say how much. I'm tempted to go out to the >electric meter to see just how much. Is it worth unplugging the thing >when (a) system is on but not using printer, (b) system powered down, >and/or (c) when system will be off for several days? I can't think off hand why it would have some power draw, unless the whole thing is on standby (as opposed to really/truly off). Copiers (there really is the printing side of a copier in there) usually have a warm-up delay, but I don't think it would be that critical. >This is where I'm stuck. NIC card is recognized as eth10 How recognized? Is this what the kernel is assigning it in the boot messages (/var/log/messages probably)? >and I used ifconfig to give it the address 192.0.0.192 which I'm told >is the default for JetDirect. 192.0.0.0/24 is an unassigned block (see RFC3330), but my recolection is that they were using a 192.168.x.x address - vaguely 192.168.1.*9. >[root(a)ozymandias ~]# ifconfig eth10 >eth10 Link encap:Ethernet HWaddr 00:03:47:42:12:A1 [compton ~]$ etherwhois 00:03:47 00-03-47 (hex) Intel Corporation 000347 (base 16) Intel Corporation MS: LF3-420 2111 N.E. 25th Avenue Hillsboro OR 97124 UNITED STATES [compton ~]$ but I don't recognize it as being a specific model. > inet addr:192.0.0.192 Bcast:192.0.0.255 Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:76 errors:0 dropped:0 overruns:0 frame:0 > TX packets:166 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 OK - that looks good. You can talk to it, something can talk to you, and there are no errors. >DEVICE=eth10 >BOOTPROTO=dhcp You are depending on the printer having a DHCP server. Now if that is what assigned the 192.0.0.192 address, we can live with it. >NEEDHOSTNAME=yes >PEERDNS=yes Those two should probably be "no" >PEERYP=yes If that's Yellow Pages (NIS), that also should be "no" >When I try to use MCC to change the printer's connection type to >"network printer," I gave it 192.0.0.192, and it accepts it, but won't >print a test page. I think that's not the right address, but I have no >idea how to find out what's correct. That's yourself, rather than the printer. I'd try running a packet sniffer on eth10 (/usr/sbin/tcpdump -i eth10 -n) and see what if any traffic exists. Another option is to try pinging the addresses in the range 192.0.0.1 - 192.0.0.254 (a broadcast ping of 192.0.0.255 probably would be ignored). Look in the arp cache (/sbin/arp -a) and see what shows up with a MAC address - possibly 00:60:B0, or 08:00:09 >> Your power never goes out? > >Maybe once every two or three years. Not often enough to be a big >worry. A UPS would be nice, but I don't think it's a priority for me. I've lost track how many power outages I've had this year - probably in the 5 or 6 range. Most have been momentary (several seconds max) which sets off alarms all over the place. The longest outage was an hour. >Only real problem over the years has been two dialup modems that had >their hook relays frozen in "off hook" presumably by power surge on >phone line. Your surge protector may or may not help. Big deal is the difference in voltages between "ground" and what-ever else is around. If the whole building suddenly jumped up to 1000 Volts above ground for a second, it's _probably_ going to be OK as long as the building entrance grounds are tied together. Problem occurs when the grounds are in physically different locations. Old guy
From: Adam on 3 Oct 2007 17:21 Moe Trin wrote: > What is room temperature like? 25C = 77F (28C = 82F) sounds a bit low > for operating components. Cheap analog thermometer/hygrometer ($4 at Wal-Mart) was left on top of system unit overnight. In morning, showed 86F/30C (didn't feel like it, though) and 53% relative humidity. When left directly in exhaust fan output (outside left side of case) for several hours, 90F/32C, 50%. Current system temperatures: M/B Temp: +41�C (low = +15�C, high = +40�C) sensor = thermistor CPU Temp: +29�C (low = +15�C, high = +45�C) sensor = diode /dev/hda: SAMSUNG SP0411N: 27�C /dev/hdb: MAXTOR 6L020J1: 41�C I put a small script in /etc/cron.hourly to record these, and since Sunday (9/30) @ 1700 hours, recorded 61 measurements, all Celsius: M/B temp: min 36, max 49, mean 42.3, mode 47.5, median 41 CPU temp: min 25, max 42, mean 34.2, mode 29 (2ary mode 40), median 30 /dev/hda: min 21, max 29, mean 25, mode 25, median 24 /dev/hdb: min 28, max 47, mean 43.6, mode 43, median 34 I don't like the M/B temp, and hda (all Linux except swap) seems too low, but CPU and hdb sound plausible. [/dev/hdb] >> Maxtor HD's spec for operating temperature is 5-55C. > Those are supposed to be ambient, rather than internal. You're right. However, if it's 47C inside the drive, I'm sure ambient temp is no higher. [motherboard temperature sensor] >> It's by the top of the CPU heatsink, >> half under it. IT87??F (partially covered by plastic frame that CPU >> fan/heatsink attaches to), probably an ITE 8705F, which is a Super I/O >> chip. > > A quick google turns up rather conflicting data, as if the chip is > using an internal or (up to) two external sensors (which sound like > thermistors). I can't find a manufacturer's data sheet. I'll look into that. I just wanted to get this out before I headed off to tonight's LUG meeting (topic is "Security and Privacy"). >> BTW this printer (HP Color LaserJet 5 if anyone's forgotten) seems to be >> drawing power even when it's switched off, > > What indication? When I plug it in with power switch off, sound of fan starting up and air blowing out of slot that printed pages come out of. When unplugged, these stop. > I can't think off hand why it would have some power draw, unless the > whole thing is on standby (as opposed to really/truly off). Went outside and timed stator of watthour meter with printer unplugged (1:23, 1:14, 1:16) and plugged in but switched off (1:49, 1:52, 1:56) -- that's a minute and some seconds for the stator to make one revolution. Apparently I use /less/ power with it plugged in! Not sure whether further investigation would be needed or would be pointless. >> This is where I'm stuck. NIC card is recognized as eth10 > > How recognized? Is this what the kernel is assigning it in the boot > messages (/var/log/messages probably)? Apparently. [root(a)ozymandias ~]# cat /var/log/messages [snip] Oct 3 16:11:50 ozymandias kernel: ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11 Oct 3 16:11:50 ozymandias kernel: ACPI: PCI Interrupt 0000:00:0f.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11 Oct 3 16:11:50 ozymandias kernel: eth1: 0000:00:0f.0, 00:03:47:42:12:A1, IRQ 11. Oct 3 16:11:50 ozymandias kernel: Board assembly 729757-007, Physical connectors present: RJ45 Oct 3 16:11:50 ozymandias kernel: Primary interface chip i82555 PHY #1. Oct 3 16:11:50 ozymandias kernel: General self-test: passed. Oct 3 16:11:50 ozymandias kernel: Serial sub-system self-test: passed. Oct 3 16:11:50 ozymandias kernel: Internal registers self-test: passed. Oct 3 16:11:50 ozymandias kernel: ROM checksum self-test: passed (0x04f4518b). Oct 3 16:11:50 ozymandias ifplugd(eth10)[3217]: ifplugd 0.28 initializing. Oct 3 16:11:50 ozymandias ifplugd(eth10)[3217]: Using interface eth10/00:03:47:42:12:A1 with driver <eepro100> (version: eepro100.c:v1.09j-t 9/29/99 Don) Oct 3 16:11:50 ozymandias ifplugd(eth10)[3217]: Using detection mode: SIOCETHTOOL Oct 3 16:11:50 ozymandias ifplugd(eth10)[3217]: Initialization complete, link beat not detected. [snip] However, it doesn't have any network address until I use ifconfig to give it one. After reboot: [root(a)ozymandias ~]# ifconfig eth10 eth10 Link encap:Ethernet HWaddr 00:03:47:42:12:A1 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Interrupt:11 [root(a)ozymandias ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth10 DEVICE=eth10 BOOTPROTO=dhcp ONBOOT=yes METRIC=10 MII_NOT_SUPPORTED=no USERCTL=no RESOLV_MODS=no IPV6INIT=no IPV6TO4INIT=no DHCP_CLIENT=dhclient NEEDHOSTNAME=no PEERDNS=no PEERYP=no PEERNTPD=no > [compton ~]$ etherwhois 00:03:47 > 00-03-47 (hex) Intel Corporation [snip] > but I don't recognize it as being a specific model. MCC says it's an Intel(R) PRO/100+ Server Adaptor (PILA8470B). > I'd try running a packet > sniffer on eth10 (/usr/sbin/tcpdump -i eth10 -n) and see what if any > traffic exists. excerpt: 21:23:29.095840 (NOV-ETHII) IPX 00000000.00:60:b0:38:69:6c.4000 > 00000000.ff:ff:ff:ff:ff:ff.0452: ipx-sap-req 0004 21:23:29.097166 00:60:b0:38:69:6c > ff:ff:ff:ff:ff:ff OSI Information, send seq0, rcv seq 17, Flags [Command, Poll], length 46 21:23:32.788175 AT 255.1.4.159 > 0.0.2: nbp-lkup 1: "HP Color LaserJet 5M:=@*" but setting printer connection to: TCP/IP Host "255.4.1.159", port 9100 results in: [adam(a)ozymandias ~]$ lpq -a Rank Owner Job File(s) Total Size active root 1646 testprint.ps 987136 bytes which just stays like that, printer does nothing and its "data" LED never even flickers. Still works okay, albeit slowly, via parallel port. > Look in the arp cache (/sbin/arp -a) and see what > shows up with a MAC address - possibly 00:60:B0, or 08:00:09 Is this getting complicated enough to deserve a new thread in a.o.l.mandriva ? >> Only real problem over the years has been two dialup modems that had >> their hook relays frozen in "off hook" presumably by power surge on >> phone line. > > Your surge protector may or may not help. Big deal is the difference > in voltages between "ground" and what-ever else is around. If the > whole building suddenly jumped up to 1000 Volts above ground for a > second, it's _probably_ going to be OK as long as the building entrance > grounds are tied together. Problem occurs when the grounds are in > physically different locations. What would you recommend to protect against both power and phone line surges? >>> What's this??? Another 5 kilo bag of salt??? >> Sorry, that one went right over my head. > > Some people talk about taking things with a grain of salt. Some > userland applications require more than that - and I'm on a > reduced sodium diet. Largest I've seen (and carried!) were 80 lb. bags for the water softener. BTW I'm on "mild sodium restriction" (2-4 g/day) and really only miss it on potatoes and pasta. I've found a lot of interesting seasonings, including many that don't explicitly say "salt free" but are. Details on request. Adam
From: Unruh on 3 Oct 2007 17:54 Adam <look(a)bottom.for.address> writes: >Moe Trin wrote: >> What is room temperature like? 25C = 77F (28C = 82F) sounds a bit low >> for operating components. >Cheap analog thermometer/hygrometer ($4 at Wal-Mart) was left on top of >system unit overnight. In morning, showed 86F/30C (didn't feel like it, >though) and 53% relative humidity. When left directly in exhaust fan >output (outside left side of case) for several hours, 90F/32C, 50%. >Current system temperatures: >M/B Temp: +41�C (low = +15�C, high = +40�C) sensor = thermistor >CPU Temp: +29�C (low = +15�C, high = +45�C) sensor = diode >/dev/hda: SAMSUNG SP0411N: 27�C >/dev/hdb: MAXTOR 6L020J1: 41�C Since the cpu is main heat source for the motherboard, I simply do not believe these temperatures of the cpu. I think that there is either some problem with the sensor or there is some problem with the calibration of the sensor. >I put a small script in /etc/cron.hourly to record these, and since >Sunday (9/30) @ 1700 hours, recorded 61 measurements, all Celsius: >M/B temp: min 36, max 49, mean 42.3, mode 47.5, median 41 >CPU temp: min 25, max 42, mean 34.2, mode 29 (2ary mode 40), median 30 >/dev/hda: min 21, max 29, mean 25, mode 25, median 24 >/dev/hdb: min 28, max 47, mean 43.6, mode 43, median 34 >I don't like the M/B temp, and hda (all Linux except swap) seems too >low, but CPU and hdb sound plausible. No. cpu is ALWAYS higher than the MB. Heat flows from the cpu to the motherboard, not vice versa. >[/dev/hdb] >>> Maxtor HD's spec for operating temperature is 5-55C. >> Those are supposed to be ambient, rather than internal. >You're right. However, if it's 47C inside the drive, I'm sure ambient >temp is no higher. >[motherboard temperature sensor] >>> It's by the top of the CPU heatsink, >>> half under it. IT87??F (partially covered by plastic frame that CPU >>> fan/heatsink attaches to), probably an ITE 8705F, which is a Super I/O >>> chip. >> >> A quick google turns up rather conflicting data, as if the chip is >> using an internal or (up to) two external sensors (which sound like >> thermistors). I can't find a manufacturer's data sheet. >I'll look into that. I just wanted to get this out before I headed off >to tonight's LUG meeting (topic is "Security and Privacy"). >>> BTW this printer (HP Color LaserJet 5 if anyone's forgotten) seems to be >>> drawing power even when it's switched off, >> >> What indication? >When I plug it in with power switch off, sound of fan starting up and >air blowing out of slot that printed pages come out of. When unplugged, >these stop. >> I can't think off hand why it would have some power draw, unless the >> whole thing is on standby (as opposed to really/truly off). >Went outside and timed stator of watthour meter with printer >unplugged (1:23, 1:14, 1:16) and plugged in but switched off (1:49, >1:52, 1:56) -- that's a minute and some seconds for the stator to make >one revolution. Apparently I use /less/ power with it plugged in! Not >sure whether further investigation would be needed or would be pointless. >>> This is where I'm stuck. NIC card is recognized as eth10 >> >> How recognized? Is this what the kernel is assigning it in the boot >> messages (/var/log/messages probably)? >Apparently. >[root(a)ozymandias ~]# cat /var/log/messages >[snip] >Oct 3 16:11:50 ozymandias kernel: ACPI: PCI Interrupt Link [LNKA] >enabled at IRQ 11 >Oct 3 16:11:50 ozymandias kernel: ACPI: PCI Interrupt 0000:00:0f.0[A] >-> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11 >Oct 3 16:11:50 ozymandias kernel: eth1: 0000:00:0f.0, >00:03:47:42:12:A1, IRQ 11. >Oct 3 16:11:50 ozymandias kernel: Board assembly 729757-007, Physical >connectors present: RJ45 >Oct 3 16:11:50 ozymandias kernel: Primary interface chip i82555 PHY #1. >Oct 3 16:11:50 ozymandias kernel: General self-test: passed. >Oct 3 16:11:50 ozymandias kernel: Serial sub-system self-test: passed. >Oct 3 16:11:50 ozymandias kernel: Internal registers self-test: passed. >Oct 3 16:11:50 ozymandias kernel: ROM checksum self-test: passed >(0x04f4518b). >Oct 3 16:11:50 ozymandias ifplugd(eth10)[3217]: ifplugd 0.28 initializing. >Oct 3 16:11:50 ozymandias ifplugd(eth10)[3217]: Using interface >eth10/00:03:47:42:12:A1 with driver <eepro100> (version: >eepro100.c:v1.09j-t 9/29/99 Don) >Oct 3 16:11:50 ozymandias ifplugd(eth10)[3217]: Using detection mode: >SIOCETHTOOL >Oct 3 16:11:50 ozymandias ifplugd(eth10)[3217]: Initialization >complete, link beat not detected. >[snip] >However, it doesn't have any network address until I use ifconfig to >give it one. After reboot: >[root(a)ozymandias ~]# ifconfig eth10 >eth10 Link encap:Ethernet HWaddr 00:03:47:42:12:A1 > UP BROADCAST MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > Interrupt:11 >[root(a)ozymandias ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth10 >DEVICE=eth10 >BOOTPROTO=dhcp >ONBOOT=yes >METRIC=10 >MII_NOT_SUPPORTED=no >USERCTL=no >RESOLV_MODS=no >IPV6INIT=no >IPV6TO4INIT=no >DHCP_CLIENT=dhclient >NEEDHOSTNAME=no >PEERDNS=no >PEERYP=no >PEERNTPD=no >> [compton ~]$ etherwhois 00:03:47 >> 00-03-47 (hex) Intel Corporation >[snip] >> but I don't recognize it as being a specific model. >MCC says it's an Intel(R) PRO/100+ Server Adaptor (PILA8470B). >> I'd try running a packet >> sniffer on eth10 (/usr/sbin/tcpdump -i eth10 -n) and see what if any >> traffic exists. >excerpt: >21:23:29.095840 (NOV-ETHII) IPX 00000000.00:60:b0:38:69:6c.4000 > >00000000.ff:ff:ff:ff:ff:ff.0452: ipx-sap-req 0004 >21:23:29.097166 00:60:b0:38:69:6c > ff:ff:ff:ff:ff:ff OSI Information, >send seq0, rcv seq 17, Flags [Command, Poll], length 46 >21:23:32.788175 AT 255.1.4.159 > 0.0.2: nbp-lkup 1: "HP Color LaserJet >5M:=@*" >but setting printer connection to: >TCP/IP Host "255.4.1.159", port 9100 >results in: >[adam(a)ozymandias ~]$ lpq -a >Rank Owner Job File(s) Total Size >active root 1646 testprint.ps 987136 bytes >which just stays like that, printer does nothing and its "data" LED >never even flickers. Still works okay, albeit slowly, via parallel port. >> Look in the arp cache (/sbin/arp -a) and see what >> shows up with a MAC address - possibly 00:60:B0, or 08:00:09 >Is this getting complicated enough to deserve a new thread in >a.o.l.mandriva ? >>> Only real problem over the years has been two dialup modems that had >>> their hook relays frozen in "off hook" presumably by power surge on >>> phone line. >> >> Your surge protector may or may not help. Big deal is the difference >> in voltages between "ground" and what-ever else is around. If the >> whole building suddenly jumped up to 1000 Volts above ground for a >> second, it's _probably_ going to be OK as long as the building entrance >> grounds are tied together. Problem occurs when the grounds are in >> physically different locations. >What would you recommend to protect against both power and phone line >surges? >>>> What's this??? Another 5 kilo bag of salt??? >>> Sorry, that one went right over my head. >> >> Some people talk about taking things with a grain of salt. Some >> userland applications require more than that - and I'm on a >> reduced sodium diet. >Largest I've seen (and carried!) were 80 lb. bags for the water >softener. BTW I'm on "mild sodium restriction" (2-4 g/day) and really >only miss it on potatoes and pasta. I've found a lot of interesting >seasonings, including many that don't explicitly say "salt free" but >are. Details on request. >Adam
From: Moe Trin on 4 Oct 2007 22:37 On Wed, 03 Oct 2007, in the Usenet newsgroup alt.os.linux.mandrake, in article <0cUMi.141686$bO6.71079(a)edtnps89>, Unruh wrote: >Adam <look(a)bottom.for.address> writes: [ ~190 lines of quoted material not referenced deleted] >>Current system temperatures: > >>M/B Temp: +41�C (low = +15�C, high = +40�C) sensor = thermistor >>CPU Temp: +29�C (low = +15�C, high = +45�C) sensor = diode >>/dev/hda: SAMSUNG SP0411N: 27�C >>/dev/hdb: MAXTOR 6L020J1: 41�C > >Since the cpu is main heat source for the motherboard, I simply do not >believe these temperatures of the cpu. I think that there is either >some problem with the sensor or there is some problem with the >calibration of the sensor. Intel builds the sensor (a diode on the die) as part of the CPU itself. What you are measuring is the forward voltage drop across the diode under a "known" current. That translates directly into temperature at that spot on the die (which probably isn't the hot spot on the die). See the Intel spec sheets for the CPU for details. The words you are looking for are "Thermal Diode". The problem is measuring that voltage accurately, and converting that digital value into an assumed die temperature. Old guy
From: Unruh on 5 Oct 2007 00:12
ibuprofin(a)painkiller.example.tld (Moe Trin) writes: >On Wed, 03 Oct 2007, in the Usenet newsgroup alt.os.linux.mandrake, in article ><0cUMi.141686$bO6.71079(a)edtnps89>, Unruh wrote: >>Adam <look(a)bottom.for.address> writes: >[ ~190 lines of quoted material not referenced deleted] >>>Current system temperatures: >> >>>M/B Temp: +41�C (low = +15�C, high = +40�C) sensor = thermistor >>>CPU Temp: +29�C (low = +15�C, high = +45�C) sensor = diode >>>/dev/hda: SAMSUNG SP0411N: 27�C >>>/dev/hdb: MAXTOR 6L020J1: 41�C >> >>Since the cpu is main heat source for the motherboard, I simply do not >>believe these temperatures of the cpu. I think that there is either >>some problem with the sensor or there is some problem with the >>calibration of the sensor. >Intel builds the sensor (a diode on the die) as part of the CPU itself. >What you are measuring is the forward voltage drop across the diode >under a "known" current. That translates directly into temperature at >that spot on the die (which probably isn't the hot spot on the die). >See the Intel spec sheets for the CPU for details. The words you are >looking for are "Thermal Diode". The problem is measuring that >voltage accurately, and converting that digital value into an assumed >die temperature. But since I suspect that the transverse conductivity is at least as good as the vertical, I would suspect this temp is close to the mean of the die. If this thing is reporting temperatures out by 20C it is not worth anything. Intel CPUs report their temperatures far more accurately than that. My cpy even not running is at around 38C under low loads. I simply do not believe 27 unless you are pouring liquid N2 over the chip. > Old guy |