Differences

This shows you the differences between two versions of the page.

--- doc:appunti:hardware:jumper_ezbook_s3 [2018/07/31 09:31] – [How To Make the WiFi Working] niccolo
+++ doc:appunti:hardware:jumper_ezbook_s3 [2018/08/01 07:29] – [TODO] niccolo
@@ Line 3: / Line 3: @@
 Installing **Debian** testing (Buster) on the **Jumper EZbook S3 notepad**.
-===== Booting from USB Key =====
+===== Booting from the USB Key =====
 We downloaded the netinst image **debian-buster-DI-alpha3-amd64-netinst.iso** from the [[https://www.debian.org/devel/debian-installer/|Debian Installer Page]] and copied over an USB memory stick (using dd, destination the whole device).
@@ Line 21: / Line 21: @@
   * **firmware-misc-nonfree** (for i915/bxt_dmc_ver1_07.bin)
+===== Installing on the Hard Disk =====
+Everything went flawlessy with the Debian Installer: during manual partitioning we **removed** the **main Windows partition** (about 240 Gb) and a 700 Mb **Windows Recovery partition**. We leaved the first two reserver partition and created //swap// and //rootfs//:
+^ # ^ Size     ^ Type  ^
+| 1 |   105 Mb | EFI system partition  |
+| 2 |  16.8 MB | Microsoft reserved partition  |
+| 3 |  8000 MB | linux-swap  |
+| 4 |   248 GB | rootfs  |
+The EFI boot loader was copied into the first partition, you can see it mounted into **/boot/efi/EFI/debian/grubx64.efi**.
 ===== How To Make the WiFi Working =====
@@ Line 27: / Line 38: @@
 The WiFi did not work with the stock installation. The **scanning** for available access points **is indeed working**, but **associating fails**. After the failed association, even the scanning stops working. We upgraded the kernel to **linux-image-4.17.0-1-amd64** in the hope that this will fix the WiFi problem, but nope.
-We downloaded the sources of a kernel module which expressly states the compatibility with that device, from it's **[[https://github.com/lwfinger/rtl8723bu|GitHub page]]**.
+We downloaded the sources of a kernel module (developed by **lwfinger**) which expressly states the compatibility with that device. This is the source code **[[https://github.com/lwfinger/rtl8723bu|GitHub page]]**.
 <code>
@@ Line 41: / Line 52: @@
 This will install a new kernel module into **/lib/modules/4.17.0-1-amd64/kernel/drivers/net/wireless/8723bu.ko** and execute ''depmod'' to update the kernel modules list.
-To be safe, blacklist the original kernel module by writing into **/etc/modprobe.d/blacklisst.conf** the line:
+The kernel module **will not survive a kernel upgrade** (it should be recompilerd and reinstalled), so we have deinstalled the pseudo package //linux-image-amd64// and leaved only the specific //linux-image-4.17.0-1-amd64//, to avoid automatic upgrades. The kernel module should be compatible with **DKMS** (the  [[https://wiki.debian.org/KernelDKMS|Debian kernel modules auto-building system]]), but our first try failed, so we went with the manual mode.
+To be safe, blacklist the original kernel module by writing into **/etc/modprobe.d/blacklist.conf** the line:
 <file>
@@ Line 51: / Line 64: @@
 ==== WiFi Resume Problem Workaround ====
-The WiFi adapter **does not resume** after the stand-by! It seems there is the **[[https://github.com/lwfinger/rtl8723bu/issues/91|issue #91]]** already fiexd? A manual workaround is:
+The WiFi adapter **does not resume** after the stand-by! It seems there is the **[[https://github.com/lwfinger/rtl8723bu/issues/91|issue #91]]** into the //lwfinger rtl8723bu// module, but already fiexd? A manual workaround is:
 <code>
@@ Line 58: / Line 71: @@
 </code>
-An automatic workaround seems to be creating a file **/usr/lib/systemd/system-sleep/fix_internet.sh** with:
+An automatic workaround seems to be creating an executable file **/lib/systemd/system-sleep/fix-wifi** with:
 <code bash>
@@ Line 71: / Line 84: @@
 esac
 </code>
+===== Suspend and Hibernate =====
+Tried with success the command line version of the commands:
+<code>
+systemctl suspend
+systemctl hibernate
+</code>
+The hibernate requires a swap partition equal or greather than the available RAM.
 ===== TODO =====
   * How to prevent the notebook to go into stand-by mode, which make it unreachable from the network (e.g. ssh login).
   * Bluetooth not working?
-  * WiFi adapter not working after resume?
+  * FIXME **Enter** key misbehaving in **less**. Problem: e.g. man page, backslash to search, hit Enter does not work, it prints **ESCOM** string instad. Workaround: use **Ctrl-M**. Tips: ''xev'' says that Enter sends ''KP_Enter'' instead of ''Return'', but changing keysym with ''%%xmodmap -e "keysym KP_Enter = Return"%%'' does not resolve. Use ''.lesskey'' to modifiy?
-  * How to hibernate instead of stand-by?