W związku z uruchomieniem już jakieś 4mc temu pomiaru temperatur oparty na czujnikach na magistrali 1-Wire, postanowiłem uruchomić dla Gnieźnian domenę temperatura.gniezno.pl
Póki co domena wykupiona została na rok, panel dotacji istnieje na dole strony. Mam nadzieje że będzie sporo wejść, a to będzie mnie motywowało do kolejnych prac, dołożeniu czujników itp.
Zapraszam:
LM-Sensors jest to pogram wyświetlając temperatury, obroty wentylatorów czy napięcie na naszej płycie głównej.
Płyta główna Asrock AD2550B-ITX jest dość nowym wynalazkiem i do działania LM-Sensors trzeba wykonać małe zabiegi:)
Pobranie lm-sensors:
apt-get update; apt-get install lm-sensors i2c-tools nano /etc/init.d/lm-sesors start
Po czym szukamy czujników:
sensors-detect
Wynikiem komendy będzie:
root@debian:~# sensors-detect # sensors-detect revision 6170 (2013-05-20 21:25:22 +0200) # Board: ASRock AD2550B-ITX 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): yes Module cpuid loaded successfully. 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 AMD Family 12h and 14h thermal sensors... No AMD Family 15h thermal sensors... No AMD Family 15h power sensors... No AMD Family 16h power sensors... No Intel digital 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): yes Probing for Super-I/O at 0x2e/0x2f Trying family `National Semiconductor/ITE'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... Yes Found `Nuvoton NCT5577D/NCT6776F Super IO Sensors' Success! (address 0x290, driver `nct6775') Probing for Super-I/O at 0x4e/0x4f Trying family `National Semiconductor/ITE'... 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): yes 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): yes 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): yes Using driver `i2c-i801' for device 0000:00:1f.3: Intel 82801G ICH7 Module i2c-dev loaded successfully. Next adapter: SMBus I801 adapter at f000 (i2c-0) Do you want to scan it? (yes/NO/selectively): yes Client found at address 0x50 Probing for `Analog Devices ADM1033'... No Probing for `Analog Devices ADM1034'... No Probing for `SPD EEPROM'... Yes (confidence 8, not a hardware monitoring chip) 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'... Yes (confidence 8, not a hardware monitoring chip) Next adapter: ITE 9135 Generic (i2c-1) Do you want to scan it? (YES/no/selectively): no Next adapter: intel drm CRTDDC_A (i2c-2) Do you want to scan it? (yes/NO/selectively): yes Next adapter: intel drm LVDSBLC_B (i2c-3) Do you want to scan it? (yes/NO/selectively): yes Next adapter: intel drm LVDSDDC_C (i2c-4) Do you want to scan it? (yes/NO/selectively): yes Now follows a summary of the probes I have just done. Just press ENTER to continue: Driver `nct6775': * ISA bus, address 0x290 Chip `Nuvoton NCT5577D/NCT6776F Super IO Sensors' (confidence: 9) Driver `coretemp': * Chip `Intel digital thermal sensor' (confidence: 9) To load everything that is needed, add this to /etc/modules: #----cut here---- # Chip drivers coretemp nct6775 #----cut here---- If you have some drivers built into your kernel, the list above will contain too many modules. Skip the appropriate ones! Do you want to add these lines automatically to /etc/modules? (yes/NO)yes Successful! Monitoring programs won't work until the needed modules are loaded. You may want to run '/etc/init.d/kmod start' to load them. Unloading i2c-dev... OK Unloading cpuid... OK
W prezentowanym modelu płyty wykryte zastaną sensory ale stany temperatur będą alarmować stany nieznane.
Naprawić to mozna tak:
/etc/init.d/lm-sensors stop /etc/init.d/kmod stop rm /etc/sensors3.conf wget http://pliki.gru.one.pl/01-2014/sensors3.conf -o /etc/sensors3.conf /etc/init.d/kmod start /etc/init.d/lm-sensors start
Teraz można przetestować działanie:
root@debian:# sensors coretemp-isa-0000 Adapter: ISA adapter Core 0: +57.0 C (crit = +100.0 C) Core 1: +58.0 C (crit = +100.0 C) nct6776-isa-0290 Adapter: ISA adapter Vcore: +1.21 V (min = +0.00 V, max = +1.74 V) in1: +1.85 V (min = +1.62 V, max = +1.98 V) AVCC: +3.34 V (min = +2.98 V, max = +3.63 V) +3.3V: +3.33 V (min = +2.98 V, max = +3.63 V) in4: +0.88 V (min = +0.81 V, max = +0.99 V) in5: +1.73 V (min = +1.53 V, max = +1.87 V) in6: +0.84 V (min = +0.72 V, max = +0.88 V) 3VSB: +3.46 V (min = +2.98 V, max = +3.63 V) Vbat: +3.28 V (min = +2.70 V, max = +3.63 V) fan1: 0 RPM (min = 0 RPM) fan2: 0 RPM (min = 0 RPM) fan3: 0 RPM (min = 0 RPM) fan4: 0 RPM (min = 0 RPM) fan5: 0 RPM (min = 0 RPM) VR temp: +41.0 C (high = +90.0 C, hyst = +75.0 C) sensor = thermistor CPUTIN: +53.0 C (high = +80.0 C, hyst = +75.0 C) sensor = thermistor AUXTIN: +40.5 C (high = +80.0 C, hyst = +75.0 C) sensor = thermistor PCH_CHIP_TEMP: +0.0 C PCH_CPU_TEMP: +0.0 C PCH_MCH_TEMP: +0.0 C intrusion1: OK
Po aktualizacji systemu Debian Testing (jessie) występował u mnie problem:
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-3.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8402-1.fw for module r8169
Rozwiązanie jest łatwe:
apt-get update; apt-get install git git clone git://git.kernel.org/pub/scm/linux/kernel/git/dwmw2/linux-firmware.git cp -r linux-firmware/rtl_nic/ /lib/firmware/ update-initramfs -u
I problem znika;)
Google Cloud Print to nowa technologia łącząca drukarki z internetem. Za jej pomocą możesz z dowolnego miejsca drukować na drukarkach w domu i w pracy, a także udostępniać je wybranym osobom. Google Cloud Print działa na telefonach, tabletach, Chromebookach, komputerach i dowolnych innych urządzeniach połączonych z siecią, z których chcesz coś wydrukować.
Instalacja w systemie Linuks wymaga skonfigurowania wcześniej drukarki w programie CUPS,
Drukarka musi być skonfigurowana w programie CUPS jako tryb PPD (sterownik) a nie RAW (przejście).
Drukowanie w chmurze przydać sie może w telefonach z systemem Android (Menu -> Ustawienia Android 4.4), lub po pobraniu aplikajcji ze Sklepu Play.
Instalacja sprowadza się do instalacji skryptu
apt-get update; apt-get install git python nano git clone https://github.com/armooo/cloudprint.git
Opcjonalnie można zainstalować screen aby uruchamiać skrypt w tle
apt-get install screen
Skrypt już jest, uruchomienie:
cd /cloudprint/cloudprint python cloudprint.py
I ustawiamy dane do naszego konta Google.
Aby zautomatyzować uruchamianie Cloudprinta można zrobić prosty skrypt i dodać go do crona:
nano cloudprint.sh
i wkleić zawartość:
#!/bin/sh cd /root/cloudprint/cloudprint ## sciezka do twojego katalogu z cloudprintem screen -dmS google-cloud-printer python cloudprint.py
Po czym dodać wpis do crontab -e
##oczywiście podac tutaj należy dokładne miejsce gdzie mamy skrypt @reboot sh /scripts/cloudprint.sh >> /dev/null 2>&1