From 0dacd4f9bc15f2209c492f4f97ce27b9e96b4d6f Mon Sep 17 00:00:00 2001 From: Devaev Maxim Date: Sun, 2 Aug 2020 01:28:54 +0300 Subject: [PATCH] move --- README.md | 20 +++++++++---------- bios_glitch.png => img/bios_glitch.png | Bin no_relays.png => img/no_relays.png | Bin screen1.png => img/screen1.png | Bin v0.png => img/v0.png | Bin v0_usbcap.png => img/v0_usbcap.png | Bin v2.png => img/v2.png | Bin v2_splitter.png => img/v2_splitter.png | Bin v2_usbcap_rpi2.png => img/v2_usbcap_rpi2.png | Bin v2_usbcap_rpi4.png => img/v2_usbcap_rpi4.png | Bin v3_board.png => img/v3_board.png | Bin building_os.md => pages/building_os.md | 0 flashing_hid.md => pages/flashing_hid.md | 0 13 files changed, 10 insertions(+), 10 deletions(-) rename bios_glitch.png => img/bios_glitch.png (100%) rename no_relays.png => img/no_relays.png (100%) rename screen1.png => img/screen1.png (100%) rename v0.png => img/v0.png (100%) rename v0_usbcap.png => img/v0_usbcap.png (100%) rename v2.png => img/v2.png (100%) rename v2_splitter.png => img/v2_splitter.png (100%) rename v2_usbcap_rpi2.png => img/v2_usbcap_rpi2.png (100%) rename v2_usbcap_rpi4.png => img/v2_usbcap_rpi4.png (100%) rename v3_board.png => img/v3_board.png (100%) rename building_os.md => pages/building_os.md (100%) rename flashing_hid.md => pages/flashing_hid.md (100%) diff --git a/README.md b/README.md index e544ace..234e187 100644 --- a/README.md +++ b/README.md @@ -78,7 +78,7 @@ The website: http://pikvm.org. Also join to the [Discord Community Chat](https:/ We created [our very own MJPG video server](https://github.com/pikvm/ustreamer) written in C with multi-threading support and GPU video encoding - the fastest streaming solution available to provide the best video quality for Pi-KVM. We also tested a lot of hardware configurations so that you can be sure devices you assemble will work reliably. -drawing +drawing ----- @@ -130,13 +130,13 @@ It's completely supported and Pi-KVM works great with it. But it has some disadv * If you want to capture VGA from your server instead of HDMI, buy the [VGA-to-HDMI converter](https://aliexpress.ru/item/4000553298530.html). * Pi-KVM can be powered using PoE, but it is not recommend to use the official PoE HAT: it is unreliable and [not compatible with the HDMI bridge](https://github.com/pikvm/pikvm/issues/6). Use any other PoE hat without an I2C fan controller. * **Don't use random relay modules or random optocouplers!** Some relays or optocouplers may not be sensitive enough for the Raspberry Pi, some others may be low-level controlled. Either use relays that are activated by a high logic level, or follow the design provided and buy an OMRON. See details [here](https://github.com/pikvm/pikvm/issues/13). - drawing + drawing ----- # The future v3 platform (work in progress) -drawing +drawing We are also currently developing our own HAT for the Raspberry Pi 4. It will have all the features of the v2 platform, including: * HDMI capture based on the TC358743 (extra low latency and many features like compression control). @@ -164,18 +164,18 @@ Insert the flexible flat cable of the HDMI bridge into the narrow white connecto Connect USB dongle to exactly this port. It is bound in the software so the OS does not confuse the video device with something else. | Raspberry Pi 2 and 3 | Raspberry Pi 4 | |----------------------|----------------| -| drawing | drawing | +| drawing | drawing | Note: there are many revisions of the Raspberry Pi boards and you may come across one that we haven't tested. If the binding fails, the device will be available for all ports. Everything will work, but if you use a webcam and Linux mistakes it for a dongle, [write to us](https://discord.gg/bpmXfz5) and we will fix it. ## Setting up the v2 Here is a diagram shows that how to connect all of the pieces (click to full size). -drawing +drawing **Raspberry Pi 4 note**: since one USB-C female connector is used to receive power and perform keyboard/mouse/drive emulation a special Y-cable must be made that splits the DATA and POWER lines of USB-C (see [reasons](https://github.com/pikvm/docs/issues/11)). It can be made from two suitable connecting cables, or soldered together from scratch. Be sure to check the circuit diagram below, otherwise you may damage your devices. The appropriate USB pinout(s) can easily be found on Google. Please note that if you make a Y-cable from two no-name cables, the colors of the wires may not match those shown. Use a multimeter to make sure the connections are correct. -drawing +drawing See video howtos: * [Making USB Y-splitter cable](https://www.youtube.com/watch?v=uLuBuQUF61o). @@ -184,12 +184,12 @@ See video howtos: Also check out this small PCB for ATX (if you know how to make PCBs): https://easyeda.com/mark.gilbert/zerow-kvm-v1 ## Setting up the v0 -drawing +drawing ----- # Installing the OS -See [here](building_os.md) for complete instructions. +See [here](pages/building_os.md) for complete instructions. #### You're amazing! Congratulations! Your Pi-KVM will be available via SSH (`ssh root@` with password `root` by default) and HTTPS (try to open in a browser the URL `https://`, use login `admin` and password `admin`). For HTTPS a self-signed certificate is used by default. @@ -286,7 +286,7 @@ Our future [v3 platform](#the-future-v3-platform-work-in-progress) will contain ``` - Run `systemctl disable getty@ttyAMA0.service`. - Remove `console=ttyAMA0,115200` and `kgdboc=ttyAMA0,115200` from `/boot/cmdline.txt`. - - [Flash the Arduino HID](flashing_hid.md). + - [Flash the Arduino HID](pages/flashing_hid.md). - Run `reboot`. ----- @@ -303,7 +303,7 @@ Our future [v3 platform](#the-future-v3-platform-work-in-progress) will contain e.g - ASUS BIOS glitch + ASUS BIOS glitch This can be solved by enabling the **Compatibility Support Module (CSM)** in your BIOS, usually under the **Boot** options. diff --git a/bios_glitch.png b/img/bios_glitch.png similarity index 100% rename from bios_glitch.png rename to img/bios_glitch.png diff --git a/no_relays.png b/img/no_relays.png similarity index 100% rename from no_relays.png rename to img/no_relays.png diff --git a/screen1.png b/img/screen1.png similarity index 100% rename from screen1.png rename to img/screen1.png diff --git a/v0.png b/img/v0.png similarity index 100% rename from v0.png rename to img/v0.png diff --git a/v0_usbcap.png b/img/v0_usbcap.png similarity index 100% rename from v0_usbcap.png rename to img/v0_usbcap.png diff --git a/v2.png b/img/v2.png similarity index 100% rename from v2.png rename to img/v2.png diff --git a/v2_splitter.png b/img/v2_splitter.png similarity index 100% rename from v2_splitter.png rename to img/v2_splitter.png diff --git a/v2_usbcap_rpi2.png b/img/v2_usbcap_rpi2.png similarity index 100% rename from v2_usbcap_rpi2.png rename to img/v2_usbcap_rpi2.png diff --git a/v2_usbcap_rpi4.png b/img/v2_usbcap_rpi4.png similarity index 100% rename from v2_usbcap_rpi4.png rename to img/v2_usbcap_rpi4.png diff --git a/v3_board.png b/img/v3_board.png similarity index 100% rename from v3_board.png rename to img/v3_board.png diff --git a/building_os.md b/pages/building_os.md similarity index 100% rename from building_os.md rename to pages/building_os.md diff --git a/flashing_hid.md b/pages/flashing_hid.md similarity index 100% rename from flashing_hid.md rename to pages/flashing_hid.md