public_git
/
pikvm
mirror of https://github.com/pikvm/pikvm.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

fixed wrong spelled words (#152)

This commit is contained in:
freddii 2021-01-14 17:26:56 +01:00 committed by GitHub
parent c4a2a0cc6e
commit 24cc103f43
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
6 changed files with 11 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
pages/api.md
View File

@ -24,7 +24,7 @@ There are two options here:
< Set-Cookie: auth_token=796cb83b11de4fcb749bc1bad14a91fb06dede84672b2f847fef1e988e6900de; Path=/
...
```
On success the cookie `auth_token` will be recieved with `200 OK`. On invalid user or password you will get `403 Forbidden`.
On success the cookie `auth_token` will be received with `200 OK`. On invalid user or password you will get `403 Forbidden`.
2. The handle `GET /api/auth/check` can be used for check the auth status. If the user is logged in, you will see `200 OK`.
If the token or any of the single-request auth methods are missing, `401 Unauthorized` will be returned.
On incorrect credentials or token, `403 Forbidden` will be returned.

4
pages/arduino_hid.md
View File

@ -28,7 +28,7 @@ Using the PS/2 firmware currently has the following limitations:
Both of these problems will be solved in the nearest future and the two different firmware versions will be combined into one universal one.
To select the PS/2 firmware, you need to follow the instructions for USB, but with one exception. Befor `make` you need to edit file `platformio.ini`. Open it and find these lines:
To select the PS/2 firmware, you need to follow the instructions for USB, but with one exception. Before `make` you need to edit file `platformio.ini`. Open it and find these lines:
```ini
[_common]
build_flags =
@ -55,7 +55,7 @@ build_flags =
# -DHID_SET_USB_MOUSE_REL
```
By default, the firmware works with USB HID and supports dynamic mode switching. You can choose one of the other modes by commenting some lines and uncomenting others. This example to use a USB mouse and PS/2 keyboard:
By default, the firmware works with USB HID and supports dynamic mode switching. You can choose one of the other modes by commenting some lines and uncommenting others. This example to use a USB mouse and PS/2 keyboard:
```ini
...
# ----- The default config with dynamic switching -----

6
pages/cookbook.md
View File

@ -96,7 +96,7 @@ How to enable extra drives:
enabled: true # Set it to true to enable
count: 1 # +1 drive, default value
default: # Default configuration for the all extra drives
cdrom: false # Defaut value (false for the generic flash drive)
cdrom: false # Default value (false for the generic flash drive)
rw: false # Read-only by default
```
If you specify `count: N`, you will create `N` additional drives configured the same way, as described in the `default` section.
@ -147,12 +147,12 @@ This procedure will create a disk image of a USB stick. This is mostly required
You can create a bootable USB stick with the normal Microsoft tools, e.g. Media Creation Tool.
Creating a bootable USB stick can also be made from an ISO file with other tools like Rufus.
Without resizing, the full size of the USB stick will be used, so keep the stick as small as possible (e.g. 4GB or 8GB) but still large enough for all Windows files. The Media Creation tool will tell you what the minum size is.
Without resizing, the full size of the USB stick will be used, so keep the stick as small as possible (e.g. 4GB or 8GB) but still large enough for all Windows files. The Media Creation tool will tell you what the minimum size is.
Before creating the image file, you can use a tool like "EaseUS Partition Master Free" or "GParted" to resize the main FAT32 partition on the USB stick. This will save space on PiKVM.
You can also perform these steps on a separate unix machine and transfer the image over to pikvm with e.g. SCP.
Or, on Windows you could use a program like PassMark ImageUSB (only for full USB size images) or 'dd' for Windows to create the image. Then use WinSCP to tranfer the image over to PiKVM.
Or, on Windows you could use a program like PassMark ImageUSB (only for full USB size images) or 'dd' for Windows to create the image. Then use WinSCP to transfer the image over to PiKVM.
Once you have the desired USB stick perform the following on the RPi to create the image directly to the PiKVM image storage folder.

4
pages/gpio.md
View File

@ -30,7 +30,7 @@ The first part of the configuration refers to the hardware layer, which defines
Each hardware input/output requires a individual driver configuration entry. Each driver has a type (which refers to the plugin that handles the communication between Pi-KVM and the hardware) and a unique name. This allows you to either can add multiple drivers of the same type with different settings or connect multiple USB HID relays.
:exclamation: Each driver requires a unique name. Names surrounded by doube underscore are system reserved and should not be used.
:exclamation: Each driver requires a unique name. Names surrounded by double underscore are system reserved and should not be used.
The only exception to this is the default GPIO driver with the name `__gpio__`, representing the physical GPIO interface of the Raspberry Pi. The configuration section for `__gpio__` is only required in your `/etc/kvmd/override.yaml` if you want to change the default settings. It can be omitted if you are fine with the defaults.
@ -39,7 +39,7 @@ kvmd:
gpio:
drivers:
# This example shows how the default __gpio__ driver settings can be changed. It can be omitted if you are fine with the defaults.
__gpio__: # Names surrounded by doube underscore are system reserved
__gpio__: # Names surrounded by double underscore are system reserved
type: gpio # Refers to the plugin name handling the communication
# You can define another gpio driver for some reason

4
pages/troubleshooting.md
View File

@ -12,7 +12,7 @@ As a first step we recommend carefully reading our documentation on [GitHub](htt
### Pi-KVM does not show any image from the connected computer
- Double check if you connected the HDMI-CSI-2 bridge cable correctly. [Check the documentation for details](/README.md#for-the-hdmi-csi-bridge) A red LED will light up on the bridge if it is connected properly.
- Some laptops do not output any signal until you switched the ouput (usually via the FN + and an F5 key on the keyboard).
- Some laptops do not output any signal until you switched the output (usually via the FN + and an F5 key on the keyboard).
### BIOS/UEFI does not recognize Pi-KVM USB
- If you are using a USB hub or USB PCI controller, this may not be handled by your BIOS. Try using motherboard's USB ports.
@ -65,7 +65,7 @@ Details [here](https://github.com/pikvm/pikvm/issues/6). The reason is that the
- The clipboard only works from the client to the server not vice versa. There is currently no way to do it.
### Chrome Certificate Issue
- The latest versions of Chrome do not allow access to the page with a self signed certificat, so if you see the following screen when loading the pi-kvm website:
- The latest versions of Chrome do not allow access to the page with a self signed certificate, so if you see the following screen when loading the pi-kvm website:
<img src="../img/chrome.png" alt="Chrome Blocking" width="400"/>
- You can proceed by typing ```thisisunsafe``` and Chrome will then load the page.

2
pages/wifi_config.md
View File

@ -3,7 +3,7 @@ The following describes how to setup a WiFi connection on the default pikvm buil
I'd recommend to do this while having a display and keyboard connected directly to the Raspberry Pi as you will loose network connectivity once you connect to a WiFi.
Alternatively you can connect to the pikvm via ssh. The build-in Terminal (available through the browser) should also work.
**Note:** I'm ommiting any sudo prefix for commands as the default installation runs as root anyway. If your installation does not run as root you'll have to add `sudo` in front of each command.
**Note:** I'm omitting any sudo prefix for commands as the default installation runs as root anyway. If your installation does not run as root you'll have to add `sudo` in front of each command.
## Make filesystem writeable
By default the pikvm filesystem is read-only. In order to make changes you'll need to switch to read-write mode. Do this by typing `rw` in the console.