E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. Reading package lists... Building dependency tree... Reading state information... Reading extended state information... Initializing package states... E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. Reading package lists... Building dependency tree... Reading state information... Reading extended state information... Initializing package states... E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. Reading package lists... Building dependency tree... Reading state information... Reading extended state information... Initializing package states... E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. --2010-07-03 22:18:35-- http://dl.dropbox.com/u/4325533/XCI/Temp-sensors/coretemp.patch Resolving dl.dropbox.com... 75.101.142.97, 75.101.148.191, 174.129.33.139, ... Connecting to dl.dropbox.com|75.101.142.97|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 3441 (3.4K) [text/x-diff] Saving to: `coretemp.patch' 0K ... 100% 14.9K=0.2s 2010-07-03 22:18:36 (14.9 KB/s) - `coretemp.patch' saved [3441/3441] bzip2: Compressed file ends unexpectedly; perhaps it is corrupted? *Possible* reason follows. bzip2: Invalid argument Input file = (stdin), output file = (stdout) It is possible that the compressed file(s) have become corrupted. You can use the -tvv option to test integrity of such files. You can use the `bzip2recover' program to attempt to recover data from undamaged sections of corrupted files. tar: Child returned status 2 tar: Exiting with failure status due to previous errors make: Entering directory `/usr/src/linux-headers-2.6.31-22-generic' scripts/Makefile.build:44: /usr/src/linux-source-2.6.31/drivers/hwmon/Makefile: No such file or directory make[1]: *** No rule to make target `/usr/src/linux-source-2.6.31/drivers/hwmon/Makefile'. Stop. make: *** [_module_/usr/src/linux-source-2.6.31/drivers/hwmon] Error 2 make: Leaving directory `/usr/src/linux-headers-2.6.31-22-generic' cp: cannot stat `/usr/src/linux-source-2.6.31/drivers/hwmon/coretemp.ko': No such file or directory --2010-07-03 22:18:38-- http://dl.dropbox.com/u/4325533/XCI/Temp-sensors/sensors-detect Resolving dl.dropbox.com... 75.101.136.120, 75.101.142.97, 75.101.148.191, ... Connecting to dl.dropbox.com|75.101.136.120|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 171252 (167K) [application/octet-stream] Saving to: `sensors-detect' 0K .......... .......... .......... .......... .......... 29% 55.6K 2s 50K .......... .......... .......... .......... .......... 59% 221K 1s 100K .......... .......... .......... .......... .......... 89% 224K 0s 150K .......... ....... 100% 11.2M=1.4s 2010-07-03 22:18:40 (124 KB/s) - `sensors-detect' saved [171252/171252] --2010-07-03 22:18:40-- http://dl.dropbox.com/u/4325533/XCI/Temp-Sensors/sensors-input Resolving dl.dropbox.com... 75.101.129.115, 75.101.136.120, 75.101.142.97, ... Connecting to dl.dropbox.com|75.101.129.115|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 21 [application/octet-stream] Saving to: `sensors-input' 0K 100% 417K=0s 2010-07-03 22:18:41 (417 KB/s) - `sensors-input' saved [21/21] # sensors-detect revision 5842 (2010-06-19 21:47:45 +0200) # System: To Be Filled By O.E.M. To Be Filled By O.E.M. # Board: ASRock AMCP7A-ION This program will help you determine which kernel modules you need to load to use lm_sensors most effectively. It is generally safe and recommended to accept the default answers to all questions, unless you know what you're doing. Some south bridges, CPUs or memory controllers contain embedded sensors. Do you want to scan for them? This is totally safe. (YES/no): Silicon Integrated Systems SIS5595... No VIA VT82C686 Integrated Sensors... No VIA VT8231 Integrated Sensors... No AMD K8 thermal sensors... No AMD Family 10h thermal sensors... No AMD Family 11h thermal sensors... No Intel Core family thermal sensor... No Intel Atom thermal sensor... Success! (driver `coretemp') Intel AMB FB-DIMM thermal sensor... No VIA C7 thermal sensor... No VIA Nano thermal sensor... No Some Super I/O chips contain embedded sensors. We have to write to standard I/O ports to probe them. This is usually safe. Do you want to scan for Super I/O sensors? (YES/no): Probing for Super-I/O at 0x2e/0x2f Trying family `National Semiconductor'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... No Trying family `ITE'... No Probing for Super-I/O at 0x4e/0x4f Trying family `National Semiconductor'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... No Trying family `ITE'... No Some systems (mainly servers) implement IPMI, a set of common interfaces through which system health data may be retrieved, amongst other things. We first try to get the information from SMBIOS. If we don't find it there, we have to read from arbitrary I/O ports to probe for such interfaces. This is normally safe. Do you want to scan for IPMI interfaces? (YES/no): Probing for `IPMI BMC KCS' at 0xca0... No Probing for `IPMI BMC SMIC' at 0xca8... No Some hardware monitoring chips are accessible through the ISA I/O ports. We have to write to arbitrary I/O ports to probe them. This is usually safe though. Yes, you do have ISA I/O ports even if you do not have any ISA slots! Do you want to scan the ISA I/O ports? (YES/no): Probing for `National Semiconductor LM78' at 0x290... No Probing for `National Semiconductor LM79' at 0x290... No Probing for `Winbond W83781D' at 0x290... No Probing for `Winbond W83782D' at 0x290... No Lastly, we can probe the I2C/SMBus adapters for connected hardware monitoring devices. This is the most risky part, and while it works reasonably well on most systems, it has been reported to cause trouble on some systems. Do you want to probe the I2C/SMBus adapters now? (YES/no): Using driver `i2c-nforce2' for device 0000:00:03.2: nVidia Corporation nForce SMBus (MCP79) Module i2c-dev loaded successfully. Next adapter: SMBus nForce2 adapter at 4d00 (i2c-0) Do you want to scan it? (YES/no/selectively): Client found at address 0x50 Probing for `Analog Devices ADM1033'... No Probing for `Analog Devices ADM1034'... No Probing for `SPD EEPROM'... No Probing for `EDID EEPROM'... No Client found at address 0x51 Probing for `Analog Devices ADM1033'... No Probing for `Analog Devices ADM1034'... No Probing for `SPD EEPROM'... No Client found at address 0x52 Probing for `Analog Devices ADM1033'... No Probing for `Analog Devices ADM1034'... No Probing for `SPD EEPROM'... No Client found at address 0x53 Probing for `Analog Devices ADM1033'... No Probing for `Analog Devices ADM1034'... No Probing for `SPD EEPROM'... No Next adapter: NVIDIA i2c adapter (i2c-1) Do you want to scan it? (YES/no/selectively): Next adapter: NVIDIA i2c adapter (i2c-2) Do you want to scan it? (YES/no/selectively): Next adapter: NVIDIA i2c adapter (i2c-3) Do you want to scan it? (YES/no/selectively): Now follows a summary of the probes I have just done. Just press ENTER to continue: Driver `coretemp': * Chip `Intel Atom thermal sensor' (confidence: 9) Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO): Copy prog/init/lm_sensors.init to /etc/init.d/lm_sensors for initialization at boot time. You should now start the lm_sensors service to load the required kernel modules. Unloading i2c-dev... OK lm-sensors: unrecognized service ./xbmc-installer.sh: line 1316: sensors: command not found E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. Reading package lists... Building dependency tree... Reading state information... Reading extended state information... Initializing package states... E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. ./xbmc-installer.sh: line 1322: cvs: command not found ./xbmc-installer.sh: line 1325: ./configure: No such file or directory make: *** No targets specified and no makefile found. Stop. make: *** No rule to make target `install'. Stop. --2010-07-03 22:18:46-- http://dl.dropbox.com/u/4325533/XCI/Temp-sensors/hddtemp.input Resolving dl.dropbox.com... 174.129.242.127, 184.73.197.198, 184.73.197.205, ... Connecting to dl.dropbox.com|174.129.242.127|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 283 [application/octet-stream] Saving to: `hddtemp.input' 0K 100% 14.1M=0s 2010-07-03 22:18:47 (14.1 MB/s) - `hddtemp.input' saved [283/283] --2010-07-03 22:18:50-- http://dl.dropbox.com/u/4325533/XCI/Temp-sensors/advancedsettings-coretemp Resolving dl.dropbox.com... 174.129.212.16, 174.129.242.127, 184.73.197.198, ... Connecting to dl.dropbox.com|174.129.212.16|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 434 [application/octet-stream] Saving to: `advancedsettings-coretemp' 0K 100% 22.4M=0s 2010-07-03 22:18:51 (22.4 MB/s) - `advancedsettings-coretemp' saved [434/434] stop: Unknown instance: xbmc-live start/running, process 2109