トップ «前の日記(2019-10-06(Sun)) 最新 次の日記(2019-10-21(Mon))» 編集

屑俺日記

僕の備忘録(PC、UN*X、ネットワーク関連が中心)なんです。
自分の書いたところは適当(な時とか)に書き換えますので御了承を。


2019-10-08(Tue) 天気予報の通り、雨が

capslock/brightness

/sys/devices$ find . -type f -name brightness
./platform/i8042/serio0/input/input0/input0::scrolllock/brightness
./platform/i8042/serio0/input/input0/input0::capslock/brightness
./platform/i8042/serio0/input/input0/input0::numlock/brightness
./pci0000:00/0000:00:02.0/drm/card0/card0-eDP-1/intel_backlight/brightness
./pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/rtsx_usb_sdmmc.1.auto/leds/mmc0::/brightness
/sys/devices/platform/i8042/serio0/input/input0/input0::capslock$ sudo \
> sh -c "echo 1 > brightness"

すると、CapsLockキーのLEDが点灯した。
しかし、CapsLock機能は有効にならなかった。

とりあえずは、これだけ。

なんか好いみたい

購入後3日目で我慢できず、Win10を消すと、UEFIを何も変えなくとも busterがあっさり入った。
sidにあげてしばらく遊ぶことにする。

$ lspci
00:00.0 Host bridge: Intel Corporation Device 3e34 (rev 0b)
00:02.0 VGA compatible controller: Intel Corporation
 UHD Graphics 620 (Whiskey Lake)
00:12.0 Signal processing controller: Intel Corporation
 Cannon Point-LP Thermal Controller (rev 30)
00:14.0 USB controller: Intel Corporation
 Cannon Point-LP USB 3.1 xHCI Controller (rev 30)
00:14.2 RAM memory: Intel Corporation
 Cannon Point-LP Shared SRAM (rev 30)
00:14.3 Network controller: Intel Corporation
 Cannon Point-LP CNVi [Wireless-AC] (rev 30)
00:16.0 Communication controller: Intel Corporation
 Cannon Point-LP MEI Controller #1 (rev 30)
00:1d.0 PCI bridge: Intel Corporation
 Cannon Point-LP PCI Express Root Port #9 (rev f0)
00:1d.4 PCI bridge: Intel Corporation
 Cannon Point-LP PCI Express Root Port #13 (rev f0)
00:1f.0 ISA bridge: Intel Corporation
 Cannon Point-LP LPC Controller (rev 30)
00:1f.3 Audio device: Intel Corporation
 Cannon Point-LP High Definition Audio Controller (rev 30)
00:1f.4 SMBus: Intel Corporation
 Cannon Point-LP SMBus Controller (rev 30)
00:1f.5 Serial bus controller [0c80]: Intel Corporation
 Cannon Point-LP SPI Controller (rev 30)
01:00.0 3D controller: NVIDIA Corporation GP108M [GeForce MX250] (rev a1)
02:00.0 Non-Volatile memory controller: Sandisk Corp WD Black 2018/PC SN520 NVMe SSD (rev 01)

i7z

温度上昇を防ぐには、というあたりを少し読んで、thermaidを入れた。その次に あったi7z(1)を実行してみた。

$ sudo i7z
i7z DEBUG: i7z version: svn-r93-(27-MAY-2013)
i7z DEBUG: Found Intel Processor
i7z DEBUG:    Stepping b
i7z DEBUG:    Model e
i7z DEBUG:    Family 6
i7z DEBUG:    Processor Type 0
i7z DEBUG:    Extended Model 8
i7z DEBUG: msr = Model Specific Register
i7z DEBUG: Unknown processor, not exactly based on Nehalem,
 Sandy bridge or Ivy Bridge
i7z DEBUG: msr device files exist /dev/cpu/*/msr
i7z DEBUG: You have write permissions to msr device files
 
------------------------------
--[core id]--- Other information
-------------------------------------
--[0] Processor number 0
--[0] Socket number/Hyperthreaded Sibling number  0,4
--[0] Core id number 0
--[0] Display core in i7z Tool: Yes
 
// 略
 
--[7] Processor number 7
--[7] Socket number/Hyperthreaded Sibling number  0,3
--[7] Core id number 3
--[7] Display core in i7z Tool: No
 
Socket-0 [num of cpus 4 physical 4 logical 8] 3,
Socket-1 [num of cpus 0 physical 0 logical 0] 
GUI has been Turned ON
i7z DEBUG: Single Socket Detected
 
i7z DEBUG: In i7z Single_Socket()
 
i7z DEBUG: guessing Nehalem
WAIT ....
 
 
True Frequency (without accounting Turbo) 1991 MHz
wrmsr:pwrite: Operation not permitted
 
Quitting i7z

cpupwer(1)

これも適当にやって、次はいつになるか。

$ sudo cpupower -c 1 frequency-info 
analyzing CPU 1:
  driver: intel_pstate
  CPUs which run at the same hardware frequency: 1
  CPUs which need to have their frequency coordinated by software: 1
  maximum transition latency:  Cannot determine or is not supported.
  hardware limits: 400 MHz - 4.60 GHz
  available cpufreq governors: performance powersave
  current policy: frequency should be within 400 MHz and 4.60 GHz.
                  The governor "powersave" may decide which speed to use
                  within this range.
  current CPU frequency: Unable to call hardware
  current CPU frequency: 2.44 GHz (asserted by call to kernel)
  boost state support:
    Supported: yes
    Active: yes

waifu2x

bionicで動くなら、busterでも動くだろうとやってみた。
インストールは問題なくできた。 nvidiaのドライバはnon-free(nvidia謹製と思われた)だったが、

$ waifu2x-converter-cpp -l
   0: Intel(R) Core(TM) i7-8565U CPU @ 1.80GHz     (FMA       ): num_core=8

だけ。
以前のページ 貼った写真を4倍に拡大してみる。

$ time waifu2x-converter-cpp --scale-ratio 4 \
> -m scale -p 1 -i 20140529_01.png -o 4x.png
CPU: Intel(R) Core(TM) i7-8565U CPU @ 1.80GHz
Processing file [1/1] "$DIR/20140529_01.png":
Scaling image from 256x144 to 1024x576
 
Step 01/02: 2x Scaling
Proccessing [1/1] slices
2x Scaling:
Processing block, column (01/02), row (01/01) ...
total : 0.478[sec], 0187.78[GFLOPS]
Processing block, column (02/02), row (01/01) ...
total : 0.037[sec], 0134.33[GFLOPS]
 
Step 02/02: 2x Scaling
Proccessing [1/1] slices
2x Scaling:
Processing block, column (01/03), row (01/02) ...
total : 0.797[sec], 0190.73[GFLOPS]
Processing block, column (02/03), row (01/02) ...
total : 0.795[sec], 0191.18[GFLOPS]
Processing block, column (03/03), row (01/02) ...
total : 0.073[sec], 0170.97[GFLOPS]
Processing block, column (01/03), row (02/02) ...
total : 0.151[sec], 0180.48[GFLOPS]
Processing block, column (02/03), row (02/02) ...
total : 0.150[sec], 0181.88[GFLOPS]
Processing block, column (03/03), row (02/02) ...
total : 0.019[sec], 0116.66[GFLOPS]
Writing image to file...
 
Done, took: 0s total, file: 2.698s avg: 6.525s
Finished processing 1 files
Took: 6.525secs total, filter: 2.500secs; 0 files skipped,
 0 files errored. [GFLOPS:   71.73, GFLOPS-Filter:  187.20]
 
real    0m6.613s
user    0m22.492s
sys     0m0.356s

6秒余りかけて waifu2x-converterで拡大した写真と、 ほとんど瞬時にできた、 imagemagickで拡大した写真


リンクはご自由にどうぞ。でもURLや内容が変った場合はあしからず。

index.htmlは ここから。