minor
This commit is contained in:
parent
3ec8fdd1ca
commit
c366c8aba4
2
edms.md
2
edms.md
@ -2,7 +2,7 @@
|
||||
https://github.com/awesome-selfhosted/awesome-selfhosted#document-management
|
||||
|
||||
mayan
|
||||
paperless-ng
|
||||
paperless-ngx
|
||||
ocrmypdf
|
||||
paperwork
|
||||
Hardware-OCR
|
||||
|
@ -49,7 +49,7 @@ block device -> dm-integrity -> cryptsetup(mdadm/lvm2 (RAID1)) -> btrfs
|
||||
- [ ] complete header backup
|
||||
- [ ] block device sector size
|
||||
- [ ] block device support for SCT/ERC `smartctl -l scterc /dev/sdX`
|
||||
- [ ] Block device support for write-verify `smartctl -r1 /dev/sdX`
|
||||
- [ ] Block device support for write-verify `hdparm -R1 /dev/sdX`
|
||||
- [ ] block device support ``hdparm --dco-identify /dev/sdX`
|
||||
|
||||
Western Digital Time Limited Error Recovery (TLER)
|
||||
@ -96,7 +96,21 @@ The following features can be selectively disabled via DCO:
|
||||
WRITE_UNC_EXT
|
||||
SATA command/feature sets:
|
||||
NCQ interface_power_management SSP
|
||||
|
||||
|
||||
hdparm -R1 /dev/sda
|
||||
|
||||
/dev/sda:
|
||||
setting write-read-verify to 1
|
||||
HDIO_DRIVE_CMD:WRV failed: Input/output error
|
||||
write-read-verify = not supported
|
||||
|
||||
smartctl -l scterc /dev/sda
|
||||
smartctl 7.2 2020-12-30 r5155 [armv7l-linux-5.4.199-odroidxu4] (local build)
|
||||
|
||||
SCT Error Recovery Control:
|
||||
Read: Disabled
|
||||
Write: Disabled
|
||||
|
||||
```
|
||||
Lenovo S440 HDD
|
||||
```
|
||||
@ -234,8 +248,17 @@ Logical Unit WWN Device Identifier: 5000c5007cb8f1cc
|
||||
IEEE OUI : 000c50
|
||||
Unique ID : 07cb8f1cc
|
||||
Checksum: correct
|
||||
|
||||
|
||||
sudo hdparm -R1 /dev/sda
|
||||
Touch HW dongle
|
||||
|
||||
/dev/sda:
|
||||
setting write-read-verify to 1
|
||||
write-read-verify = 2
|
||||
|
||||
```
|
||||
m.s SATA SSD
|
||||
m.2 SATA SSD
|
||||
```
|
||||
ATA device, with non-removable media
|
||||
Model Number: TS256GMTS430S
|
||||
@ -472,6 +495,13 @@ Logical Unit WWN Device Identifier: 5000039af21081db
|
||||
IEEE OUI : 000039
|
||||
Unique ID : af21081db
|
||||
Checksum: correct
|
||||
|
||||
hdparm -R1 /dev/sda
|
||||
|
||||
/dev/sda:
|
||||
setting write-read-verify to 1
|
||||
write-read-verify = 2
|
||||
|
||||
```
|
||||
|
||||
```
|
||||
@ -535,11 +565,24 @@ SCT capabilities: (0x303d) SCT Status supported.
|
||||
SCT Feature Control supported.
|
||||
SCT Data Table supported.
|
||||
|
||||
smartctl -l scterc /dev/sda
|
||||
smartctl 7.2 2020-12-30 r5155 [armv7l-linux-5.10.63-v7+] (local build)
|
||||
|
||||
SCT Error Recovery Control:
|
||||
Read: 85 (8.5 seconds)
|
||||
Write: 85 (8.5 seconds)
|
||||
|
||||
hdparm -R1 /dev/sda
|
||||
|
||||
/dev/sda:
|
||||
setting write-read-verify to 1
|
||||
HDIO_DRIVE_CMD:WRV failed: Input/output error
|
||||
write-read-verify = not supported
|
||||
|
||||
```
|
||||
```
|
||||
root@cubietruck:~# smartctl -l scterc /dev/sda
|
||||
smartctl 7.2 2020-12-30 r5155 [armv7l-linux-5.15.25-sunxi] (local build)
|
||||
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org
|
||||
|
||||
SCT Error Recovery Control:
|
||||
Read: Disabled
|
||||
@ -679,7 +722,14 @@ Logical Unit WWN Device Identifier: 5000c5002e9f2ea1
|
||||
NAA : 5
|
||||
IEEE OUI : 000c50
|
||||
Unique ID : 02e9f2ea1
|
||||
Checksum: correct
|
||||
Checksum: correct
|
||||
|
||||
hdparm -R1 /dev/sda
|
||||
|
||||
/dev/sda:
|
||||
setting write-read-verify to 1
|
||||
write-read-verify = 2
|
||||
|
||||
```
|
||||
ERC settings: `smartctl -l scterc /dev/sda` or setting `smartctl -l scterc,150,150 /dev/sda`
|
||||
|
||||
|
36
windows_10.md
Normal file
36
windows_10.md
Normal file
@ -0,0 +1,36 @@
|
||||
# Window
|
||||
|
||||
### display resolutions
|
||||
windows resets the display resolutions because it has values, which apply to a virtual device, which is used when no device is conncted.
|
||||
```
|
||||
http://answers.microsoft.com/en-us/windows/forum/windows_7-hardware/windows-7-movesresizes-windows-on-monitor-power/1653aafb-848b-464a-8c69-1a68fbd106aa
|
||||
|
||||
_"I have found a work-around._
|
||||
_Using Sysinternals ProcessMonitor I found that Windows was accessing the following Registry path;_
|
||||
_HKEY\_LOCAL\_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\GraphicsDrivers\\Configuration_
|
||||
|
||||
_My system had three entries;_
|
||||
_DELF003YY7707BR0MUL\_30\_07D7_6A^9A3774EB79DEE3E3E38496CC7DF4D936_
|
||||
_QHD32000001\_31\_07D6_D5^63E1ABDD175E7871DCAEB710418A0F75_
|
||||
_SIMULATED\_8086\_2A42\_00000000\_00020000_1010100^CDE365D1B3F0942F0CF38BFB8E127AB4_
|
||||
|
||||
_Under each is a tree called "00" two of the keys are_
|
||||
_PrimSurfSize.cx_
|
||||
_PrimSurfSize.cy_
|
||||
|
||||
_Under "00" was another branch also called "00" two of the keys are;_
|
||||
_ActiveSize.cx_
|
||||
_ActiveSize.cy_
|
||||
|
||||
_The first two of the configs (ie DELF00... & QHD3...) the above keys were 1440x900,_
|
||||
_so they were not involved._
|
||||
|
||||
_The third (SIMULATED...) were set to 1024x768._
|
||||
|
||||
_I changed these to 1600x900 and the problem was solved._
|
||||
|
||||
_Further I changed resolution (via control panel) to 1920x1080, the moving/resize issue returned,_
|
||||
_but the lower right corner was set to 1600x900, ie the SIMULATED... settings."_[](http://answers.microsoft.com/en-us/windows/forum/windows_7-hardware/windows-7-movesresizes-windows-on-monitor-power/1653aafb-848b-464a-8c69-1a68fbd106aa)
|
||||
|
||||
Use MichealAtOz's advice but within all the folders that are labeled "00" or "01", (etc, I had 00 and 01) look for any settings that contain 1024, 768, or I 4096 in the data values at the end in parenthesis. Change the 1024 to the x resolution of your desktop (the first number in resolutions) and the 768 to the y resolution of your desktop. Change the 4096 number of "Stride" to whatever number there already is in a "00" or similar titled folder that <ins>already has (without you changing them)</ins> the desired desktop resolution numbers in primsurfsize.cx and ...y. Right click the name and choose modify, then select binary as the base to enter correct resolution values.
|
||||
```
|
Loading…
Reference in New Issue
Block a user