LINUX on UEFI 32bit | [linuxos] tablets and TV box INTEL Bay \ Cherry Trail



Rep: (126)
LINUX on UEFI 32/64 bit


The topic discusses installing any kind of LINUX on tablets and TV boxes on INTEL Bay [Cherry] Trail with UEFI 32 / 64bit

Specifications
Specifications:
INTEL Bay [Cherry] Trail.
The screen size, touchscreen, Ram, Rom, it's all not important, they are almost identical, in tablets on Intel.
additional information
If you were able to launch Linux on your machine, write its name, what does not work and what works and how you launched it.
P.SThe topic is forbidden to discuss dualboot Android / Windows only linux / windows
Linux builds
Instructions
Drivers and sources
Kernel

Neighboring topics



There is no curator in the subject. For questions about filling the caps, please contact me atQMSif you found an interesting article or information.


Post has been editedM | A | G - 20.04.20, 18:06
Reason for editing: + autorotation guide



Rep: (566)
* Narovchatus,
2) here I wrote about itLinux on UEFI 32Bit (Arkan49 post # 76010748)

Post has been editedarkan49 - 09.11.19, 06:56



Rep: (8)
* arkan49,
Arkan49 @ 08/13/18, 21:14 *
And from here, the GNOME-Shell output in the ligament with LightDM and the EVDEV driver, the best solution for using Linux on the tablet.
- Clear, thanks! At the moment, what you will advise Ubuntu, Xubuntu, Mint or something else (only it's one thing to choose a distribution, another to put it, so that it is visible to the BIOS loader. With my bios, not everything can be put)?

Post has been editedNarovchatus - 09.11.19, 12:43



Rep: (566)
* Narovchatus,
Under the touch of Ubuntu, for MINT claws.



Rep: (8)
* arkan49, Well, the dwarf went and could be put on the midst, I mean, it is better to put from distributions; What will be comfortable to drag on the tablet with 2 gigami of RAM.



Rep: (0)
Hello friends.
I have allview vivai10g tablet running android 4.4.2 and Intel processor.
After starting, there are reports that part of the GOGL processes stop working. Can I install some kind of Linux? If so, how?
thank



Rep: (88)
* vesodimov ,
Everything is in the hat
LINUX at UEFI 32bit (Post iillyyaa2033 # 74034680)



Rep: (0)
* Silent Forest thank.



Rep: (8)
My Naitarias, on the TouchScreen-on-on on the IRBIS_TW78 tablet.
Distribution that I have installed on the tablet -Xubuntu-19.10-Desktop-AMD64.iso

What for:
Because this is my first experience of using Linux on the tablet, I write in order for me to not have experienced those flour that I experienced. Well, in order to give more experienced Linux users to the tip / helped with what can still be taken (well, about it later).

Background:
After the tested flour from the Windows 10 work on this device, I decided to go to Linux. Let's just say - the leap of faith, because These are fundamentally different systems and require different knowledge and habits from their use. The choice fell on Xubuntu 19.10, since it is less demanding towards the possibilities of "iron" rather than Ubuntu. After installing on the tablet (What had to be done to make the tablet saw a flash drive with xubuntu) I did not work Touchscreen. Agree - unpleasant. The tablet stupidly turned into a tablet to a netbook))).

Next, I will describe the help that I had forum usersATILL2123 Silent forestandarkan49. Guys are great thanks for you !!!

Let's start:

1. Preparation:
Download everything you need:
1.1. Drivers under Windows from Irbis TW78From the official website of the manufacturer. In your case, this is the official website of your device.
1.2. Utility with GitHub, open the terminal and drive:
sudo apt install git

We enter your account password and do it every time you need to do something in a sudo user mode.
Then, I recommend to close the terminal and open it again so that the other actions are not from the user's root.
We enter
git clone https://github.com/onitake/gsl-firmware

and
git clone https://github.com/onitake/gslx680-acpi

1.3. Install Build-Essential Libelf-DeV packages (I did not have a touchscreen driver correctly converted
Sudo APT Install Build-Essential Libelf-Dev

1.4. After all manipulations reboot the system.In general, so that something came into force after the cardinal changes must be rebooted.

2. Pull the touchscreen firmware from Windows drivers:
2.1. Open the File Manager Folder Tools - Path / Home / Inquiry / Tools / GSL-Firmware / Tools / Tools / Tools / and there I copy the inet_i101_3692_32bit_landscape_pg_pg_fc101s124_pg_pg_fc101s124_pg_20161205_shenbt.h and sileadtouch.sys. In your case, these are files with .h and .sys extensions.Attached fileI101_pg_fc101s124_20161205_ruiyun.zip.(85.3 kb)


Attention!!! It must be executed clause 1.3.
2.2. We get the firmware from the ".h" file.Go to the Tools folder - Path / Home / Login_name / GSL-Firmware / Tools / Tools / (If you are no longer there), press the right mouse button and select "Open Terminal". You should have something from this - the name_name @ Balance_name: ~ / GSL-Firmware / Tools $.
We enter
./untscfg inet_i101_3692_32bit_landscape_pg_fc101s124_20161205_shengt.h firmware.fw.

The Firmware.fw tablet firmware file appears in the Tools folder
2.3. We get the firmware from the ".sys" file.Go to the Tools folder - Path / Home / Login_name / GSL-Firmware / Tools / Tools / (If you are no longer there), press the right mouse button and select "Open Terminal". You should have something from this - the name_name @ Balance_name: ~ / GSL-Firmware / Tools $.
We enter
./scanwindrv SileadTouch.sys

In the Tools folder, the Firmware_00.fw tablet file appears

Test whether the driver firmware works at all
It is not necessary to do this in general, only to find out in the right way to go comrades))).
1. We learn the path and name where and how to throw one of the two files received.
dmesg | Grep Silead.

We get exhaust
5.722584] Silead_TS I2C-MSSL1680: 00: I2C-MSSL1680: 00 Supply VDDIO Not Found, using dummy regulator
5.722628] Silead_ts I2C-MSSL1680: 00: I2C-MSSL1680: 00 Supply Avdd Not Found, using dummy regulator
5.726709] Silead_TS I2C-MSSL1680: 00: Silead Chip ID: 0x80360000
5.900071] Silead_ts I2C-MSSL1680: 00: Direct Firmware Load for Silead / MSSL1680.fw Failed with Error -2
5.900080] Silead_ts I2C-MSSL1680: 00: Firmware Request Error -2
5.900255] Silead_ts: Probe of I2C-MSSL1680: 00 Failed WITH Error -2

It follows from this that one of two files (firmware.fw and firmware_00.fw) We renamet in MSSL1680.fw and reset along the way - / usr / lib / firmware / Silead /. In my case, the Silead folder was not and therefore I had to create it.
2. Rename the files and the method of professional-pointed tyk, we learn which of the files will suit us. Threw off the file, rebooted, the touch came to life - joy; No - we delete and throw off the following and reboot.
Check the result
Drive the team
dmesg | Grep Silead.

Exhaust of my tablet
[5.664620] Silead_ts I2C-MSSL1680: 00: I2C-MSSL1680: 00 Supply VDDIO NOT Found, using Dummy Regulator
[5.664683] Silead_ts I2C-MSSL1680: 00: I2C-MSSL1680: 00 Supply Avdd NOT Found, using Dummy Regulator
[5.664979] Silead_TS I2C-MSSL1680: 00: Silead Chip ID: 0x80360000
[7.196928] Input: Silead_ts AS / Devices / Platform / 80860F411: 03 / I2C-3 / I2C-MSSL1680: 00 / INPUT / INPUT16
[43.843760] Silead_TS I2C-MSSL1680: 00: More Touches Reported Then Supported 7> 5

* About Miracle !!! Everything works as needed (your tablet is needed to an exhibition or hang on the wall as the best employee of the month). But it is very unlikely - there are no miracles in the technique.
** Touch just came to life. Reacts to pressing (at least something), while the cursor lives its own life, then it should be.

Here we have two ways -plain But very unstable and complicated . Bottling and everything will be clearly. If you decide to go difficult, then we turn to step 3.
Simple but very unstable way
Pros:
* easy to implement
Minuses:
* Normal work only in one position of the screen - which set up,
* It will not work in GNOME (and it is most sharpened under the tablet, it works cleanpad in XFCE as a touchpad without the right mouse button),
* Multitach does not work (at least I could not configure it).
Doshift driver.
1. Install the EVDEV driver (only Xinput-Calibrator works with them).
Sudo Apt Install XServer-Xorg-Input-EVDEV

Then remove the Libinput driver (so as not to conflict)
Sudo APT PURGE XSERVER-XORG-INPUT-LIBINPUT

Put Xinput-Calibrator
sudo apt install xinput-calibrator

2. Most likely, your screen is in portrait mode, and a regular keyboard on the side, then you can turn the image using the script:
xrandr -o right
Xsetwacom --Set "Silead_ts" Rotate CW

Return to portrait
xrandr -o normal
Xsetwacom --Set "Silead_ts" Rotate None

Instead of Silead_TS - the name of your touchscreen, you can find it in the terminal:
xinput

Display only if items 2.4. and 2.5. Made.
My tablet xinput exhaust
⎡ Virtual core pointer id = 2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id = 4 [slave pointer (2)]
⎜ Hantick Hantick Wireless Device Mouse ID = 8 [Slave Pointer (2)]
⎜ Hantick Hantick Wireless Device Consumer Control ID = 10 [Slave Pointer (2)]
⎜ Microsoft Microsoft® Nano TRANSCEER V2.0 Mouse ID = 13 [Slave Pointer (2)]
⎜ ↳ Microsoft Microsoft® Nano Transceiver V2.0 Consumer Control ID = 14 [Slave Pointer (2)]
⎜ ↳ Microsoft Microsoft® Nano Transceiver V2.0 Consumer Control ID = 16 [Slave Pointer (2)]
⎜ ↳ 2.4g Mouse ID = 17 [Slave Pointer (2)]
⎜ ↳ Silead_ts id = 19 [Slave Pointer (2)]
⎣ Virtual core keyboard id = 3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id = 5 [slave keyboard (3)]
↳ Video BUS ID = 6 [SLAVE KEYBOARD (3)]
↳ Hantick Hantick Wireless Device ID = 7 [Slave Keyboard (3)]
↳ Hantick Hantick Wireless Device System Control ID = 9 [Slave Keyboard (3)]
↳ Hantick Hantick Wireless Device Wireless Radio Control ID = 11 [Slave Keyboard (3)]
↳ Microsoft Microsoft® Nano TRANSCEER V2.0 ID = 12 [Slave Keyboard (3)]
↳ Microsoft Microsoft® Nano Transceiver V2.0 System Control ID = 15 [SLAVE KEYBOARD (3)]
↳ BYTCR-RT5640 Headset ID = 18 [Slave Keyboard (3)]
↳ AXP20X-PEK ID = 20 [SLAVE KEYBOARD (3)]
↳ GPIO-KEYS ID = 21 [SLAVE KEYBOARD (3)]
↳ GPIO-KEYS ID = 22 [Slave Keyboard (3)]

3. In the terminal:
sudo xinput_calibrator --output-filename /usr/share/x11/xorg.conf.d/99-calibration.conf

In some XINPUT systems-Calibrator, not Xinput_Calibrator.
The calibrator will open and will need to poke along the four sides of the monitor. And now the mouse pointer will be clear where you picked up with your finger.
4. Reboot to the changes to take effect.
If you need to re-recalibly, first delete the 99-Calibration.conf file along the path /USR/Share/x11/xorg.conf.d/, then reboot, calibrate reboot, reboot.

Script files (paragraph 3.1.), Which will work on a double-click. They can be placed on the desktop.Attached fileNormal and Right.tar.gz.(212 bytes)




How to throw off the file in the root section
In the terminal, open a file manager with superuser rights:
Xubuntu
sudo thunar

Ubuntu
sudo nautilus

Mint
Sudo Nemo.



3. Calibration of firmware file
We decided to go difficult to go.
3.1. Go to the foldergsl-firmwareAnd there are two files with youfirmware.fwandfirmware_00.fw. We are determined with what file we need / running (more in the previous stage of the spoiler - a test whether the driver firmware works at all). One of them remove or move so that it does not interfere, and the other is renamed infirmware_00.fw
Further turns into a fortune teller, and we will help you with the FWTool utility, which is located in the GSL-Firmware / Tools folder. Open the FWTOOL file itself and there is a description of the parameters that we need to correctly calibrate the firmware itself. From under the Tools folder, open the terminal and enter
./fwtool -c firmware_00.fw -m 1680 -w 1525 -H 2000 -f Swap, Track -T 10 Silead_ts.fw

Or (we guess further)
./fwtool -c firmware_00.fw -m 1680 -w 1525 -H 1975 -f Swap, Track -T 10 Silead_ts.fw

or
./fwtool -c firmware_00.fw -m 1680 -w 1515 -H 1975 -f Swap, Track -T 10 Silead_ts.fw


Here then, we become fortunellers, because We know only the controller model and that the X and Y axes are confused (these features you will learn if you follow the steps from the spoiler - the test, whether the driver firmware is at all). Width (W) and height (h) we will need to be guessing.
Attention!!! We all do in portrait mode of the tablet !!!(The one that is your default). I recommend it to do surrounded by an XFCE desktop. Gnome will not determine the mouse pointer, because After pressing it will hide (tablet mode).
In general, we need to get a filesilead_ts.fwBy all the truths and inconsistencies, let while with the inverted axes and with the other non-confinement, it will rule later.
3.1. File received by ussilead_ts.fwDrop on the wayUSR / LIB / FIRMWARE /, and filemssl1680.fwwhich we (if) tested before delete along with the foldersilead(Silead / MSSL1680.fw). It is necessary to do this that there is no conflict.
Attached filesilead_ts.fw(18.97 Kb)

3.2. Go to the GSLX680-ACPI folder (and if you downloaded it and unpackled from the archive, the folder is called GSLX680-ACPI-Master) and open the terminal from there. We enter
make

The terminal climbs the folder where the kernel modules are lying (something does it), clips with the file/usr/lib/firmware/silead_ts.fw.And creates a filegslx680_ts_acpi.koAnd other files, but you need it with you.
Attached fileGSLX680_TS_ACPI.7Z.(5.78 KB)

Run
sudo insmod ./gslx680_ts_acpi.ko

After that, Tachskrin must earn.
We continue to be a fortune chart, because we repeat the algorithm:
1. Take offsilead_ts.fw
2. Startedgslx680_ts_acpi.ko
3. Selecting the width, height and options convert using the FWTOOL file utilitysilead_ts.fwfrom firmware_00.fw (clause 3.1).
4. Reboot (completely and not only "x"), launchgslx680_ts_acpi.ko
5. It turned out (calibrated) go further, and if not, then - the algorithm re-re-all will fail.

4. Replacing the moduleSilead.ko.ongslx680_ts_acpi.ko

We enter
modinfo silead

We get exhaust
filename: /lib/modules/5.3.0-23-generic/kernel/drivers/input/touchscreen/silead.ko.
license: GPL
Description: Silead I2C Touchscreen Driver
Author: Robert Dolca<[email protected]>
SRCVERSion: 9648FD436AF28DE004D4C8A.
Alias: I2C: MSSL1680
Alias: I2C: GSL3692
Alias: I2C: GSL3675
Alias: I2C: GSL3670
Alias: I2C: GSL1688
Alias: I2C: GSL1680
Alias: ACPI *: MSSL0017: *
Alias: ACPI *: MSSL0002: *
Alias: ACPI *: MSSL0001: *
Alias: ACPI *: MSSL1680: *
Alias: ACPI *: GSL3692: *
Alias: ACPI *: GSL3675: *
Alias: ACPI *: GSL3670: *
Alias: ACPI *: GSL1688: *
Alias: ACPI *: GSL1680: *
depends:
Retpoline: Y.
intree: Y
Name: Silead.
Vermagic: 5.3.0-23-Generic SMP MOD_UNLOAD
SIG_ID: PKCS # 7
SIGNER: Build Time Autogenerated Kernel Key
SIG_KEY: 71: C6: AB: C9: AE: A0: 87: E1: 57: 55: D2: B6: C9: ED: B9: 0A: B4: DD: BA: 4D
SIG_HASHALGO: SHA512.
Signature: 79: 77: 7d: 88: 64: DE: 17: B4: C8: 4B: 2F: FA: 29: C5: 58: 96: 9D: 23: 66: A6:
12: BA: 91: 7B: CC: 3B: BE: 66: 57: 7B: 55: 43: D9: 4F: 42: 1F: 46: 1F: 7E: DF:
49: 1d: 31: F5: CB: C5: DC: 22: 8E: 56: A4: 18: F0: B8: 37: F0: 9F: 97: DB: C6:
ED: C4: 42: F6: 14: 03: F1: EB: C9: 1E: 3A: 2A: A6: 62: A7: EA: E1: 7A: EC: D2:
F7: A0: 42: AF: 0B: 27: ED: 66: 09: 8C: 7B: 9C: CF: AD: EF: 57: C2: 3F: D6: 59:
7B: C8: E6: 05: 15: F5: F4: E5: 39: BE: 1B: 63: 5F: E0: 30: 43: 42: 76: 5A: CE:
61: 38: F6: 59: 07: BB: FD: 7D: 18: 6B: 1A: B5: F6: CD: 98: 06: 85: B9: 31: CE:
1C: 98: E3: EB: 65: 61: 0D: 62: 68: 98: 66: E1: A5: EE: A6: B1: 36: 31: F0: 9A:
1F: 9E: 6A: C6: 4A: 9E: 60: 7B: EF: 48: 9F: 54: B6: 54: F6: 14: 4E: E1: 0A: 73:
29: 62: CB: C0: AE: 92: A5: 15: 86: 15: E4: 98: 0a: 4C: AA: 60: 63: A1: 67: 44:
F8: C4: 34: 45: 78: 33: FB: 90: C6: 14: EF: 33: 42: 70: 7d: 89: 64: F9: C2: C1:
E9: 79: 85: F9: C0: 22: 3E: 53: 49: 42: 19: 22: 83: 84: B2: 99: 04: F1: A5: 2F:
FB: 0A: D8: 80: 5B: 72: AC: 68: 52: 3B: 0C: 48: AA: F9: A6: 35: 76: 9C: 67: 72:
83: BD: A5: 5B: DD: 45: 56: D7: 74: 13: AA: 99: F8: BF: 4D: F2: 08: AD: 05: 09:
B2: 1C: 68: E3: 0E: 06: 78: E8: FF: AA: 06: 5C: 26: 14: 5B: 4D: D2: EC: 29: AD:
DA: 37: E4: 7C: 1B: F1: 07: 28: 8F: 10: 6E: D8: C9: 53: 19: 03: A4: 83: BB: A4:
E2: A4: 45: 05: 46: 63: 8c: 2a: 63: 2c: 39: 5b: F7: B2: B2: 4A: E1: BA: EB: FE:
33: 55: FE: 9C: 84: 7A: 40: 8B: 80: 90: F0: CE: A0: 5F: 96: CA: B6: 6B: BF: 35:
4d: 76: 9A: 01: 6B: AE: A5: 56: B8: 17: 92: 34: E8: A5: B8: 01: E4: 42: 9B: 2C:
57: 2D: 1E: B9: 2B: 82: 3D: AA: B5: EF: A6: FD: 16: E4: C7: A0: 9A: B0: B8: 0D:
4C: 7C: 40: 83: 98: C9: 91: C0: A0: A4: 2E: 00: E0: F9: ED: 98: 90: 11: 5C: 83:
13: 80: F1: 27: D5: 56: 4B: B4: 7E: 92: af: 68: d0: 83: 99: 52: 05: 32: 9e: CC:
0B: 9C: C9: BB: 38: 7E: 16: FF: 3D: C5: 85: 46: 74: 1e: 61: A1: FB: E6: C7: 74:
F4: 57: FA: 10: A5: 22: 2C: EB: CC: 78: 65: 0E: 35: 52: EF: 45: AC: 0E: 91: 3D:
11: 06: E0: 9F: 86: F7: 68: 4A: 89: BA: 2D: 04: E4: B5: 35: A2: 07: 88: 0B: 65:
51: A3: B2: 03: 44: D0: 3D: C3: 0D: A4: E2: A5

Get the path and file / lib/modules/03.0-23-generic/kernel/drivers/input/touchscreen/silead.ko
Rename the GSLX680_TS_ACPI.KO file in Silead.ko and replacing the Silead.ko file to renamed. Reboot. After that, everything worked for me.
Output after changing the command file
modinfo silead

filename: /lib/modules/5.3.0-23-generic/kernel/drivers/input/touchscreen/silead.ko.
license: GPL
Version: 0.2.1
Author: GREGOR RIEPL<[email protected]>
Description: GSLX680 Touchscreen Controller Driver
SRCversion: 23F446A874B2C141FB7F66B.
Alias: I2C: GSLX680
Alias: ACPI *: PNP3680: *
Alias: ACPI *: PNP1680: *
Alias: ACPI *: MSSL3680: *
Alias: ACPI *: MSSL1680: *
depends:
Retpoline: Y.
Name: gslx680_ts_acpi
Vermagic: 5.3.0-23-Generic SMP MOD_UNLOAD
PARM: FW_NAME: Firmware File Name (Default: Silead_ts.fw) (Charp)


Xinput output after file substitution
⎡ Virtual core pointer id = 2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id = 4 [slave pointer (2)]
⎜ Hantick Hantick Wireless Device Mouse ID = 8 [Slave Pointer (2)]
⎜ Hantick Hantick Wireless Device Consumer Control ID = 10 [Slave Pointer (2)]
⎜ ↳ 2.4G Mouse id = 12 [Slave Pointer (2)]
⎜ ↳ Microsoft Microsoft® Nano Transceiver V2.0 Consumer Control ID = 14 [Slave Pointer (2)]
⎜ Microsoft Microsoft® Nano TRANSCEER V2.0 Mouse ID = 15 [Slave Pointer (2)]
⎜ ↳ Microsoft Microsoft® Nano Transceiver V2.0 Consumer Control ID = 16 [Slave Pointer (2)]
⎜ Silead GSLX680 Touchscreen ID = 19 [Slave Pointer (2)]
⎣ Virtual core keyboard id = 3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id = 5 [slave keyboard (3)]
↳ Video BUS ID = 6 [SLAVE KEYBOARD (3)]
↳ Hantick Hantick Wireless Device ID = 7 [Slave Keyboard (3)]
↳ Hantick Hantick Wireless Device System Control ID = 9 [Slave Keyboard (3)]
↳ Hantick Hantick Wireless Device Wireless Radio Control ID = 11 [Slave Keyboard (3)]
↳ Microsoft Microsoft® Nano TRANSCEER V2.0 ID = 13 [Slave Keyboard (3)]
↳ Microsoft Microsoft® Nano Transceiver V2.0 System Control ID = 17 [Slave Keyboard (3)]
↳ BYTCR-RT5640 Headset ID = 18 [Slave Keyboard (3)]
↳ AXP20X-PEK ID = 20 [SLAVE KEYBOARD (3)]
↳ GPIO-KEYS ID = 21 [SLAVE KEYBOARD (3)]
↳ GPIO-KEYS ID = 22 [Slave Keyboard (3)]
↳ Hantick Hantick Wireless Device Consumer Control ID = 23 [Slave Keyboard (3)]
↳ Microsoft Microsoft® Nano Transceiver V2.0 Consumer Control ID = 24 [Slave Keyboard (3)]
↳ Microsoft Microsoft® Nano Transceiver V2.0 Consumer Control ID = 25 [Slave Keyboard (3)]




P.S. Well, it seems to be everything! Fuh.

Dooforming later
1. The idea is when I turn on Right scripts (landscape mode) or Normal (portrait mode), depending on how I want to rotate the screen and the touchscreen itself, then I would like to add a line that at the same time I could have calibration.
Script content so that you just don't download them.
right
#! / bin / sh
xrandr -o right
Xsetwacom --Set "Silead_ts" Rotate CW

normal
#! / bin / sh
xrandr -o normal
Xsetwacom --Set "Silead_ts" Rotate None

Theoretically, they can be enjoyed to hang them on the key combination (Cttl + left, etc.).
Start>Settings>Keyboard>Key combinations>To add
2. If it is not possible to add something to the script, which would change the calibration of the touchscreen, then it can add some marker (or flag, I don't know how it is called) to change the screen calibration option.

Maybe somehow and something can be added to the /usr/share/x11/xorg.conf.d/x11/xorg.conf.d/99-calibration.conf options in which one parameters will be alone in the landscape format, and in portrait others?
My configs (made from two downloads, each time with the deletion of the file config)
Landscape mode
Section "InputClass"
Identifier "calibration"
MatchProduct "silead_ts"
Option "Calibration" "32 1977 1498 20"
Option "swapaxes" "0"
Endsection

Portrait mode
Section "InputClass"
Identifier "calibration"
MatchProduct "silead_ts"
MatchISTABLET "ON"
MatchDevicePath "/ dev / input / event *"
DRIVER "EVTOUCH"
Option "Calibration" "1247 1243 616 629"
Option "SwapAxes" "1"
Endsection

Naturally, all this was applied immediately, and not after rebooting.

Or there is a different turning experience, not only images, but also touchscreen and at the same time changing the calibration of the touchscreen.


Post has been editedNarovchatus - 23.04.20, 19:35



Rep: (131)
Narovchatus @ 12.11.19, 20:30*
If it is not possible to add something to the script, which would change the calibration of the touchscreen, then it can add some marker (or flag, I don't know how it is called) to change the screen calibration option.

Maybe somehow and something can be added to the /usr/share/x11/xorg.conf.d/x11/xorg.conf.d/99-calibration.conf options in which one parameters will be alone in the landscape format, and in portrait others?

If I understood correctly, you ideally want that the screen orientation varies with automatt when the device is rotated. Once used this scripthttps://github.com/jfw...port-scripts/rotate.sh.
I had to choose xinputs = (9 10 11) and the path / SYS / BUS / IOO / DEVICES / IIO \: Device1 / in_accel_x_raw
In this case, it is probably possible to register your team instead of (or in addition) to Xinput Set-Prop.

Still found this optionhttps://github.com/scadl/autorotate-linux
Requires a package IIO-SENSORS-PROXY
In general, in the presence of the aforementioned package, in the shell GNOME, KDE Wayland and Fly (in Astra Linux) the screen is rotated.



Rep: (238)
Narovchatus @ 12.11.19, 16:30*
I would like to add a line that would at the same time would change the calibration

You can probably dynamically change the OPTION parameters from the 99-Calibration.conf file by the same XsetWacom command:
# Touchscreen Calibration for Landscape
xsetwacom --set "silead_ts" "Calibration" "32 1977 1498 20"
xsetwacom --set "silead_ts" "swapaxes" 0 "

# Touchscreen Calibration for Portrait
Xsetwacom --Set "Silead_ts" "Calibration" "1247 1243 616 629"
xsetwacom --set "silead_ts" "swapaxes" "1"

Add these commands to your scripts to change the orientation.



Rep: (8)
* Cut in Thanks, I will try.

Posted on 11/15/2019, 13:25:

* ipc_ngs, Thanks for the answer. Only now I decided to abandon the idea of ​​using 99-Calibration.conf and everything connected with it. Multitouch disappears. In general, I went in a different way. In "Nutrition" I will describe the option that I chose.



Rep: (8)
I figured out with the touchscreen (the process described in "Sotarsva", added to the header), installed GNOME Shell. It is best adapted to the tablet. But there is another trouble - the screen turns incorrectly. I will explain: the tablet is connected to the standard keyboard, therefore it is in landscape format. At this time, the position of the screen is rooted 90 degrees counterclockwise, i.e. In portrait mode. It is worth taking a tablet and put it on the side, i.e. In the portrait mode, the image rotates counterclockwise 90 degrees. The tablet stands in portrait mode, and the image on it in the album. Probably, the accelerometer (MB gyroscope) works incorrectly. Now the problem is solved by a temporary solution - turn the tablet and squeeze the "Block the auto-rotation" button.
The question is what, how can this be fixed in CNOME-Shell?



Rep: (131)
Narovchatus @ 11/16/19, 19:46*
Probably, the accelerometer (MB gyroscope) works incorrectly.
It just soldered him as more convenient. For correction, the so-called transformation matrix is ​​used.Linux on UEFI 32Bit (PRESSER FRESTION # 60606898) Linux on UEFI 32Bit (post Russianneuromancer # 60691948) LINUX on UEFI 32bit (cut in post # 66213319)

Post has been editedCut in - 16.11.19, 16:52



Rep: (8)
* Cut in
So far nothing happens (
A little bit wrong, well, still ...
I decided to open the tablet and see what's from cooling. And after that he dropped 10 minutes) I applied the photo
Attached Image
Attached Image
Attached Image


P.S. The manufacturer says that the tablet does not support Simkards.

Post has been editedNarovchatus - 18.11.19, 12:21



Rep: (8)
DRAW @ 04/19/17, 15:54*
This is an option for DEXP, where the SMO8500 sensor and the screen turns 90 ° counterclockwise.
In this file, first should be the only string.
ACCEL_MOUNT_MATRIX = 1, 0, 0; 0, 1, 0; 0, 0, 1

And how can I find out the model of my sensor ???



Rep: (131)
Narovchatus @ 11/18/19, 19:16*
And how can I find out the model of my sensor ???
Try to get started
SENSOR: Modalias: ACPI: *: DMI: *: *

How to look for a sensor model, I do not know. More precisely, I would watch the / SYS / Bus / Acpi / Devices catalog, but there should be a simpler way.



Rep: (8)
* Cut in
URAAA !!! Victory!!! (The problem - the image was turned against a clockwise arrow, after turning the screen, a gyroscope was triggered and it turned out again counterclockwise)
How I did it:
IOO-SENSOR-PROXY must be installed.
If it is (set) Ubuntu-Desktop (or GNOME-Shell), then it is placed in charge of it. If for some reason it is not, then we introduce in the terminal:
sudo apt update

sudo apt install iio-sensor-proxy

And this, I think it will not be superfluous
sudo apt install iio-sensor-proxy inotify-tools


Introduced in the terminal (https://www.aixin.fr/jipeblog/?p=119.)
Sudo UDevadm Info -N / Dev / IIO \: Device0

Exhaust
P: / Devices / Platform / 80860F41: 02 / I2C-2 / I2C-BMA250E: 00 / IIO: Device0
N: IIO: Device0
L: 0.
E: DevPath = / Devices / Platform / 80860F41: 02 / I2C-2 / I2C-BMA250E: 00 / IIO: Device0
E: devname = / Dev / IIO: Device0
E: Devtype = IIO_Device
E: Major = 240
E: minor = 0
E: Subsystem = IIO
E: USC_INITIALIZED = 9032188
E: IIO_SENSOR_PROXY_TYPE = IIO-Buffer-Accel
E: SystemD_Wants = IIO-Sensor-Proxy.Service
E: Tags =: SystemD:

BMA250E - first meaning

sudo dmidecode

The desired part of the exhaust
Handle 0x0001, DMI type 1, 27 bytes
System information
Manufacturer: IRBIS
Product Name: I101
Version: Type1 - TBD by OEM
SERIAL NUMBER: TYPE1 -
Wake-up Type: Power Switch
SKU NUMBER: TW78
Family: Type1 - Family

IRBIS - second meaning
I101 - Third Meaning

Formula
SENSOR: Modalias: ACPI: [Device_Modalias] *: DMI: *: SVN [Manufacturer] *: PN [Product_Name]: *


Get
SENSOR: Modalias: ACPI: BMA250E *: DMI: *: SVNIRBIS *: PNI101: *


Further create a 61-sensor-local.hwdb file in the /usr/lib/udev/hwdb.d directory

# To Add Local Entries, Create A New File
# /etc/udev/hwdb.d/61-sensor-local.hwdb.
# and add your rules there. To Load The New Rules Execute (as root):
# SYSTEMD-HWDB UPDATE
# UDevadm trigger -y `dirname $ (UDevadm info -N" / Dev / IIO: DeviceXXX "-Q PATH)`
# WHERE / DEV / IIO: DeviceXXX is the Device in Question.
#
# Allowed Properties Are:
# Accel_mount_matrix =.<matrix>
#
# WHERE<matrix>IS A MOUNT-MATRIX IN THE FORMAT SPECIFIED IN THE IIO
# Subsystem [1]. The Default, Whene Unset, Is Equivalent To:
# Accel_mount_matrix = 1, 0, 0; 0, 1, 0; 0, 0, 1
# EG. The Identity Matrix.
#
# [1]: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=dfc57732ad38f93ae6232a3b4e6232a3b4e64fd077383a0f1
#
#
# Sort by Brand, Model

#########################################
# Irbis
#########################################
SENSOR: Modalias: ACPI: BMA250E *: DMI: *: SVNIRBIS *: PNI101: *
ACCEL_MOUNT_MATRIX = 0, 1, 0; 100; 0, 0, 1


Then enter in the terminal wait for the end of the process:
Sudo Systemd-Hwdb UDDATE && Sudo UDevadm Control --Reload-Rules && Sudo UDevadm Trigger


Reload the tablet - Ideally, it should earn, but it will be one but: with landscape, everything is as it should, but in the book it will be turned over.

Then there is something that does not obey any logic. Open our 61-sensor-local.hwdb file in the /usr/lib/udev/hwdb.d directory and change the value. 0, 1, 0;1,0, 0; 0, 0, 1 to 0, 1, 0;-1, 0, 0; 0, 0, 1

We reboot the tablet - and everything works about the miracle.

Attached file61-Sensor-local.hwdb.zip.(2.26 KB)


Why it is impossible to immediately make 0, 1, 0;-10, 0; 0, 0, 1 - I do not know, apparently, some magic is mixed here. What I just did not do, but it turned out just like that. How I learned about accel_mount_matrix = 0, 1, 0; -100; 0, 0, 1 - Most likely lucky.
I came to this meaning, thanks to the "XRANDR" table
- https: //wiki.ubuntu.co...ordinatetransformation.
LEFT ROTATE (Clockwise 90 °)
Lets Say We Physically Rotate The Screen by 90 ° (from left) to the right. The X Server Screen Can Be Rotated So That Display Output Matches The New Orientation:
$ XRANDR -O LEFT
Warning /! \ NOT ALL Graphics Drivers Support Rotation
NOW WE WANT TO MAP OUR TOUCHSCREEN TO THE NEW ORIENTATION (90 ° (FROM LEFT) TO THE RIGHT) AS WELL. Using The Affine Transformation Rules We Would Want Our Transformation Matrix To Be:
⎡ 0 -1 1 ⎤
⎜ 1 0 0 ⎥
⎣ 0 0 1 ⎦

Right Rotate (counterclockwise 90 °)
For 90 ° (from right) to the left.
$ XRANDR -O Right
Warning /! \ NOT ALL Graphics Drivers Support Rotation
With a Transformation Matrix of:
⎡ 0 1 0 ⎤
⎜ -1 0 1 ⎥
⎣ 0 0 1 ⎦

Invert Rotate (ClockWise or Counterclockwise 180 °)
$ xrandr -o inverted
Warning /! \ NOT ALL Graphics Drivers Support Rotation
With a Transformation Matrix of:
⎡ -1 0 1 ⎤
⎜ 0 -1 1 ⎥
⎣ 0 0 1 ⎦


Every time I needed to enter XRANDR -O Right for normal orientation. Then I thought that you need these values ​​by default namely:
⎡ 0 1 0 ⎤
⎜ -1 0 1 ⎥
⎣ 0 0 1 ⎦
According to this, it should be 0, 1, 0; -1, 0, 1; 0, 0, 1, but with these data, the same was not everything smoothly. The screen worked as it should be, if it is to keep it in an almost vertical position, it is worth omitting (tilt) 45 degrees tablet and below, as the tablet passed into the landscape orientation. The professional tyk method was chosen by the value of accel_mount_matrix = 0, 1, 0; -100; 0, 0, 1
Something like this)))
Maybe in my version, this is a single case, but still it happened.

P.S. Just in case, I have Ubuntu-Desktop, everything worked in it as it should.
Installed like this:
sudo apt install ubuntu-desktop


Post has been editedNarovchatus - 14.04.20, 21:33



Rep: (12)
* Narovchatus ,
Through xinput.



Rep: (0)
Already half a year as a set (through netinstall) and runs on Debian 10 Prestigio Multipad Visconte V. normal flight. Several nansov with which I have dealt with tailor the:
1) The system was loaded through time. Often hung black screen after starting core and shell. To cope with it, putting the kernel 4.16 (of caps) instead of standing 4.19
2) Module RTL8723BS tossed on a flash drive when you install the OS and everything went okay, but the installed system, this module is filled up dmesg errors about some failures, and wi-fi did not work. Helped to install the package firmware-realtekAttached filefirmware-realtek_20190717-1_all.deb(503.14 KB)
Where have I desired module.
3) there was no sound, even after actions bythisinstructions. After a "detective work" in Google learned about deb-package firmware-intel-sound, and really, after installing the sound came.

Who I am trying to set up Skype. The camera is not determined, but here it is in the drivers. With that I will still be picked. The microphone is determined, but there is no sound. Digging in alsamixer, for all sorts of instructions on the Internet led CAPTURE 50 percent. I tried to record sound in arecord through the terminal. Record goes, but the pop-up file is quiet, barely audible hiss and nothing else.



Rep: (131)
NODWS @ 19.11.19, 22:52*
Who I am trying to set up Skype. The camera is not determined, but here it is in the drivers. With that I will still be picked. The microphone is determined, but there is no sound. Digging in alsamixer, for all sorts of instructions on the Internet led CAPTURE 50 percent. I tried to record sound in arecord through the terminal. Record goes, but the pop-up file is quiet, barely audible hiss and nothing else.
The camera, as if most of the tablet is connected via atomisp, will not work - the driver has not been brought to mind, and removed from the kernel. On the microphone, try the kernel 5.x and newer alsa-lib (UCM necessary files are in the package with a name like libasound2-data_1.1.9-0ubuntu1_all.deb). Put on Astra (it is based on an older version of Debian) such packages from Ubuntu.


Full version    

Help     rules

Now: 05.12.20, 14:05