Welcome to fdisk (util-linux 2.33.1). Changes will remain in memory only, until you decide to write them. Be careful before using the write command.
Command (m forhelp): p #查询现有分区# Disk /dev/sda: 223.6 GiB, 240057409536 bytes, 468862128 sectors Disk model: KINGSTON SUV500M Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0xf196b74b
Device Boot Start End Sectors Size Id Type /dev/sda1 2048 468862127 468860080 223.6G 83 Linux
Command (m forhelp): d #删除已有的分区# Selected partition 1 Partition 1 has been deleted.
Command (m forhelp): n #创建新分区# Partition type p primary (0 primary, 0 extended, 4 free) e extended (container for logical partitions) Select (default p): p #创建主分区# Partition number (1-4, default 1): #默认# First sector (2048-468862127, default 2048): #默认# Last sector, +/-sectors or +/-size{K,M,G,T,P} (2048-468862127, default 468862127):
Created a new partition 1 of type'Linux' and of size 223.6 GiB. Partition #1 contains a ext4 signature.
Do you want to remove the signature? [Y]es/[N]o: y #删除已有的标记#
The signature will be removed by a write command.
Command (m forhelp): w #执行分区操作,写入分区表# The partition table has been altered. Calling ioctl() to re-read partition table. Syncing disks.
$ sudo pwmconfig # pwmconfig revision $Revision$ ($Date$) This program will search your sensors for pulse width modulation (pwm) controls, and test each one to see if it controls a fan on your motherboard. Note that many motherboards do not have pwm circuitry installed, even if your sensor chip supports pwm.
We will attempt to briefly stop each fan using the pwm controls. The program will attempt to restore each fan to full speed after testing. However, it is ** very important ** that you physically verify that the fans have been to full speed after the program has completed.
Found the following devices: hwmon0 is coretemp hwmon1 is nct6779 hwmon2 is soc_dts0 hwmon3 is soc_dts1
Found the following PWM controls: hwmon1/pwm1 current value: 251 hwmon1/pwm2 current value: 74 hwmon1/pwm2 is currently setup for automatic speed control. In general, automatic mode is preferred over manual mode, as it is more efficient and it reacts faster. Are you sure that you want to setup this output for manual control? (n) y hwmon1/pwm3 current value: 253 hwmon1/pwm4 current value: 254 hwmon1/pwm5 current value: 255
Giving the fans some time to reach full speed... Found the following fan sensors: hwmon1/fan1_input current speed: 0 ... skipping! hwmon1/fan2_input current speed: 1341 RPM hwmon1/fan3_input current speed: 0 ... skipping! hwmon1/fan4_input current speed: 0 ... skipping! hwmon1/fan5_input current speed: 0 ... skipping!
Warning!!! This program will stop your fans, one at a time, for approximately 5 seconds each!!! This may cause your processor temperature to rise!!! If you do not want to do this hit control-C now!!! Hit return to continue:
Testing pwm control hwmon1/pwm1 ... hwmon1/fan2_input ... speed was 1341 now 1340 no correlation
No correlations were detected. There is either no fan connected to the output of hwmon1/pwm1, or the connected fan has no rpm-signal connected to one of the tested fan sensors. (Note: not all motherboards have the pwm outputs connected to the fan connectors, check out the hardware database on http://www.almico.com/forumindex.php)
Did you see/hear a fan stopping during the above test (n)?y
$ sudo sensors-detect # sensors-detect revision $Revision$ # Board: AMI Corporation Aptio CRB # Kernel: 4.19.0-6-amd64 x86_64 # Processor: Intel(R) Celeron(R) CPU J1900 @ 1.99GHz (6/55/9) 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): 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 16h thermal sensors... No AMD Family 17h 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 Intel 5500/5520/X58 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): y 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 NCT5532D/NCT6779D Super IO Sensors' Success! (address 0xa20, 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): y 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): y 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): y Using driver `i2c-i801' for device 0000:00:1f.3: BayTrail (SOC) Module i2c-dev loaded successfully. Next adapter: SMBus I801 adapter at f000 (i2c-0) Do you want to scan it? (yes/NO/selectively): y 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 Next adapter: i915 gmbus ssc (i2c-1) Do you want to scan it? (yes/NO/selectively): y Next adapter: i915 gmbus vga (i2c-2) Do you want to scan it? (yes/NO/selectively): y Next adapter: i915 gmbus panel (i2c-3) Do you want to scan it? (yes/NO/selectively): y Next adapter: i915 gmbus dpc (i2c-4) Do you want to scan it? (yes/NO/selectively): y Next adapter: i915 gmbus dpb (i2c-5) Do you want to scan it? (yes/NO/selectively): y Next adapter: i915 gmbus dpd (i2c-6) Do you want to scan it? (yes/NO/selectively): y Next adapter: DPDDC-B (i2c-7) Do you want to scan it? (yes/NO/selectively): y Next adapter: DPDDC-C (i2c-8) Do you want to scan it? (yes/NO/selectively): y Now follows a summary of the probes I have just done. Just press ENTER to continue: Driver `nct6775': * ISA bus, address 0xa20 Chip `Nuvoton NCT5532D/NCT6779D 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)y 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
更新设置
1 2 3 4 5
sudo service module-init-tools restart
cat /sys/class/hwmon/hwmon3/pwm1
ls -ahl /sys/class/hwmon/hwmon3/pwm?
硬盘休眠
1 2 3 4 5 6 7 8 9 10 11
$ sudo hdparm -C /dev/sdd /dev/sdd: drive state is: active/idle