I have different problem now with power plugged the power led blinks. If I unplug battery connector and then replug it, pinebook boot. If I remove power supply pinebook will turned off.
The purpose of this blog post is to introduce the i3 window manager , as well the ayufan xenial-i3 pine community image. I am a completely sold out i3wm convert ; never going back-- i3 for me !
The i3 Window Manager Tutorials and Introductory Videos
The above tutorials are well worth the time and effort, are fast--and fun--and will get you up and running with this super tiling windows manager on your new Pinebook !
I am currently running the 0.4.16 xenial-i3 on my Pinebook with the mate-terminal; you may quickly want to replace the terminal on i3 because the font is so small, and because the dafault is a minimalist terminal; the mate-terminal is fully equipped and ready to roll with nice fonts and a rich tool-bar:
sudo apt install mate-terminal
Below I am going to show the interface of this excellent tiling window manager, and provide a batt_status.sh script which can be used to monitor your battery status more effectively than the i3 status bar.
The pic above is my first ( #1 ) virtual work space; I have three terminals open-- it is clearly obvious why its called a tiling window manager. Not to worry , floating windows are configurable too!
I'm doing some Python work in the left terminal, and in the right terminal I'm displaying the code ( also included here ) for displaying the battery status in a loop-- running in the bottom right-hand terminal of work-space #1.
I removed the battery block of my .i3status.conf file. The script below ( batt_status.sh ) goes in your ~/bin/ folder and runs in a forever loop in a small terminal showing the battery current status ( charging | discharging ) the voltage in micro volts, and the percent capacity.
Note: the battery status bar component is broken on this image. The script below is a simple elegant solution for battery monitoring in a tiling terminal environment.
batt_status.sh
Code:
#!/bin/bash
while [ 1 == 1 ]
do
echo " capacity : " `cat /sys/class/power_supply/battery/capacity`
echo " voltage : " `cat /sys/class/power_supply/battery/voltage_now`
echo " status : " `cat /sys/class/power_supply/battery/status`
sleep 7
done
Note: the little quote-like characters above ARE NOT quotes-- they are back-ticks; the little character under the tilde ( to the left of the 1 key on most keyboards ).
Remember, i3 is a tiling window manager NOT an OS; the operating system under the covers is ubuntu which is a debian derivative.
Hi all - I just received my Pinebook yesterday and I have really enjoyed the couple of hours that I have had to mess around with it. (Definitely pleased that I have not experienced any of the DHL cracked screen / dead pixel / wonky keyboard issues that people have been writing about.)
I am still trying to get comfortable with the different OSes that are available to us and, after installing Android 6 and then flipping the machine back to Mate, I started wondering if anybody had given any thought to dual-booting the machine. Would something like this be possible?
Yeah, I suppose I could keep an SD card around and have one OS on it but, well, dual booting would be convenient.
I have enjoyed reading the forum over the last couple of days as I waited for my machine to arrive.
Hey guys, Linux newbie here. I got my Rock64 running with the new ubuntu image (xenial-mate-rock64-0.5.5-93-arm64.img.xz) and I'm trying to compile the Wifi+BT driver for my combo USB dongle. I cloned the git repo (Git) and tried compile it with "sudo make", but I keep getting an error. Anybody here can help me out?
Code:
rock64@rock64:~/.git/rtl8723bu$ sudo make
[sudo] password for rock64:
make ARCH=aarch64 CROSS_COMPILE= -C /lib/modules/4.4.77-rockchip-ayufan-93/build M=/home/rock64/.git/rtl8723bu modules
make[1]: Entering directory '/usr/src/linux-headers-4.4.77-rockchip-ayufan-93'
Makefile:634: arch/aarch64/Makefile: No such file or directory
make[1]: *** No rule to make target 'arch/aarch64/Makefile'. Stop.
make[1]: Leaving directory '/usr/src/linux-headers-4.4.77-rockchip-ayufan-93'
Makefile:321: recipe for target 'modules' failed
make: *** [modules] Error 2
I already tried installing the linux-headers from ayufans repo with dpkg, didn't help. The same command works on my normal ubuntu PC.
hi. i have a yuntab B102(tulip-p1) tablet with an allwinner chipset that is stuck on the initial boot screen. i can enter recovery, but nothing in it resolves anything...
1. rebooting to bootloader freezes at the initial boot screen
2. factory reset works, but doesn't help
3. mounting system the 1st time actually caused this problem for some reason. no modifying.
i have tried the (HDMI version) marshmallow firmware(that's what it came with) rooted and no root. all i get is a blank screen when trying to boot. i don't know what else to do.
My pinebook arrived today and I am very happy with its look and am happily running android 7.1 now. Still one thing that's bother me a lot is that the spacebar must be pushed exactly the center (around 1.5~2 cm) in order to have pinebook to register a keystroke. I used to place my thumb on the 1/3 of the left (and right) of the spacebar when I am typing, this is killing me that now every single spacebar I hit it's not taken by the pinebook.
Am I getting a defective pinebook or this is the usual case?
I don't know why I can only boot once. If I just unplug the power, I cannot boot the second time when I power it on.
I use a Linux image which is called stretch-minimal-rock64-0.4.16-83-arm64.
(08-28-2017, 04:29 PM)fbms Wrote: I don't know why I can only boot once. If I just unplug the power, I cannot boot the second time when I power it on.
I use a Linux image which is called stretch-minimal-rock64-0.4.16-83-arm64.
Actually, when I boot the board on the second time I have to unplug the HDIM wire and replug it into the board. I don't know it's a problem of my TV ( I use a TV) or it's a problem of the Linux image. Anyway if you meet the same problem just try what I said.
I also use ‘USB image tool’ to write the image. It works great.
![[Image: 4jZ8VKT.png]](http://i.imgur.com/4jZ8VKT.png)
