doc:appunti:hardware:jumper_ezbook_s3
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
doc:appunti:hardware:jumper_ezbook_s3 [2018/07/31 11:31] – [How To Make the WiFi Working] niccolo | doc:appunti:hardware:jumper_ezbook_s3 [2018/08/01 09:31] (current) – [How To Make the WiFi Working] niccolo | ||
---|---|---|---|
Line 3: | Line 3: | ||
Installing **Debian** testing (Buster) on the **Jumper EZbook S3 notepad**. | 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:// | We downloaded the netinst image **debian-buster-DI-alpha3-amd64-netinst.iso** from the [[https:// | ||
Line 21: | Line 21: | ||
* **firmware-misc-nonfree** (for i915/ | * **firmware-misc-nonfree** (for i915/ | ||
+ | ===== 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 **/ | ||
===== How To Make the WiFi Working ===== | ===== How To Make the WiFi Working ===== | ||
- | The integrated WiFi card is attached to the USB bus, it is identified by ID **obda: | + | The integrated |
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, | 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, | ||
- | We downloaded the sources of a kernel module which expressly states the compatibility with that device, from it' | + | We downloaded the sources of a kernel module |
< | < | ||
Line 34: | Line 45: | ||
git clone https:// | git clone https:// | ||
cd rtl8723bu | cd rtl8723bu | ||
- | # In Makefile: commented-out | + | # In Makefile: commented-out the line EXTRA_CFLAGS += -DCONFIG_CONCURRENT_MODE |
make | make | ||
make install | make install | ||
Line 41: | Line 52: | ||
This will install a new kernel module into **/ | This will install a new kernel module into **/ | ||
- | To be safe, blacklist the original kernel module by writing into **/ | + | The kernel module **will not survive a kernel upgrade** (it should be recompilerd and reinstalled), |
+ | |||
+ | To be safe, blacklist the original kernel module by writing into **/ | ||
< | < | ||
Line 51: | Line 64: | ||
==== WiFi Resume Problem Workaround ==== | ==== WiFi Resume Problem Workaround ==== | ||
- | The WiFi adapter **does not resume** after the stand-by! It seems there is the **[[https:// | + | The WiFi adapter **does not resume** after the stand-by! It seems there is the **[[https:// |
< | < | ||
Line 58: | Line 71: | ||
</ | </ | ||
- | An automatic workaround seems to be creating | + | An automatic workaround seems to be creating |
<code bash> | <code bash> | ||
Line 71: | Line 84: | ||
esac | esac | ||
</ | </ | ||
+ | ===== Suspend and Hibernate ===== | ||
+ | |||
+ | Tried with success the command line version of the commands: | ||
+ | |||
+ | < | ||
+ | systemctl suspend | ||
+ | systemctl hibernate | ||
+ | </ | ||
+ | |||
+ | The hibernate requires a swap partition equal or greather than the available RAM. | ||
+ | |||
+ | |||
===== TODO ===== | ===== TODO ===== | ||
* How to prevent the notebook to go into stand-by mode, which make it unreachable from the network (e.g. ssh login). | * 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? | * Bluetooth not working? | ||
- | * WiFi adapter not working after resume? | + | * FIXME **Enter** key misbehaving in **less**. Problem: e.g. man page, backslash |
- | | + |
doc/appunti/hardware/jumper_ezbook_s3.1533029475.txt.gz · Last modified: 2018/07/31 11:31 by niccolo