Welcome, Guest
You have to register before you can post on our site.

Username
  

Password
  





Search Forums



(Advanced Search)

Forum Statistics
» Members: 29,545
» Latest member: elver
» Forum threads: 16,209
» Forum posts: 116,954

Full Statistics

Latest Threads
Brand new sealed Pinetime...
Forum: General Discussion on PineTime
Last Post: elver
Today, 06:41 AM
» Replies: 0
» Views: 176
Call recording?
Forum: PinePhone Pro Software
Last Post: biketool
Yesterday, 04:14 AM
» Replies: 7
» Views: 6,680
Thoughts after a year wit...
Forum: General Discussion on Pinebook Pro
Last Post: Frank23t
09-08-2025, 10:30 PM
» Replies: 4
» Views: 1,895
Why projects like PinePho...
Forum: General Discussion on PinePhone
Last Post: biketool
09-08-2025, 12:51 PM
» Replies: 4
» Views: 3,886
more mobile linux on redd...
Forum: General Discussion on PinePhone
Last Post: biketool
09-08-2025, 12:03 PM
» Replies: 2
» Views: 1,766
Anyone selling a Pinebook
Forum: Pinebook Hardware and Accessories
Last Post: ams
09-08-2025, 09:26 AM
» Replies: 2
» Views: 1,993
Having trouble reading MP...
Forum: Getting Started
Last Post: Alex92
09-05-2025, 08:49 PM
» Replies: 1
» Views: 3,102
Special keys stopped work...
Forum: General Discussion on PineNote
Last Post: cheepeero
09-05-2025, 07:32 PM
» Replies: 0
» Views: 2,209
Booting Issues
Forum: PineNote Software
Last Post: vlagged
09-04-2025, 12:52 PM
» Replies: 20
» Views: 10,023
Experimental Mobian kerne...
Forum: PinePhone Pro Software
Last Post: teekay
09-04-2025, 01:40 AM
» Replies: 11
» Views: 4,469

 
  Boot from MicroSD
Posted by: ramboton - 11-16-2018, 11:36 AM - Forum: General Discussion on Pinebook - Replies (3)

New owner here, received my Pinebook yesterday, I wanted to try some of the other OS options but can not seem to get anything to boot from the MicroSD slot.  I have tried Android 7, Xenial and Q4OS.  I have written them to the MicroSD card with Etcher, and with the Pine64 version of Etcher, I have used 3 different MicroSD cards, 32g or less, one is a high speed card, nothing seems to work.  I power the unit on, the green power light comes on, the screen stays black, nothing ever loads. If I take the MicroSD card out the unit boots fine to the pre-installed OS.  What am I doing wrong?


  Netflix on KDE Plasma
Posted by: SoccerCrazed - 11-16-2018, 10:11 AM - Forum: Linux on Pinebook - No Replies

Is it possible to get Netflix running on the Pinebook in KDE Plasma?

I've tried just about everything I could find from Google searches, but it seems that all of the methods to get Netflix to work are either outdated or not compatible with the Pinebook. I've been unable to install Google Chrome for some reason, and I haven't been able to get DRM content to play in either Firefox or Chromium because I haven't been able to get Widevine to work.

Any suggestions would be greatly appreciated.


  [SOLVED] Can't boot when SD card inserted
Posted by: jschall - 11-16-2018, 09:21 AM - Forum: General Discussion on Pinebook - Replies (5)

I used a 64GB microSD card to install Q4OS to the EMMC card.

I was able to boot to Q4OS from the SD card when the original KDE Neon was on the EMMC.

Now, I normally boot from EMMC to Q4OS.

So, I re-formatted the microSD card, in order to use it for extra storage.

It works OK, I can mount the card and read/write files on it.

BUT -

If I reboot with the card inserted, my Pinebook will not boot. Black screen, no error message.

I have to remove the card and hard-reboot, then re-insert the card.

There is something on the card that makes the Pinebook try to boot from it, but there's no boot partition on the card:


adminq@pinebook1080p:~$ df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/root        15G  5.7G  8.1G  42% /
devtmpfs        798M     0  798M   0% /dev
tmpfs           995M   17M  979M   2% /dev/shm
tmpfs           995M  8.7M  987M   1% /run
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs           995M     0  995M   0% /sys/fs/cgroup
/dev/mmcblk0p1  100M   23M   77M  23% /boot
tmpfs           199M   12K  199M   1% /run/user/1000
adminq@pinebook1080p:~$ lsblk
NAME         MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
mmcblk0      179:0    0 14.6G  0 disk
├─mmcblk0p1  179:1    0  100M  0 part /boot
└─mmcblk0p2  179:2    0 14.5G  0 part /
mmcblk0boot0 179:8    0    4M  1 disk
mmcblk0boot1 179:16   0    4M  1 disk
mmcblk1      179:24   0   60G  0 disk
└─mmcblk1p1  179:25   0   60G  0 part
adminq@pinebook1080p:~$

If I insert a different microSD card, from my Android tablet, there is no such problem.

What do I have to remove or add to the 64GB card so that Pinebook doesn't try to boot from it?


Further to this problem.

I used the Pinebook Installer to write ARCH Linux image onto the 64GB card.

It still won't boot, and now it won't mount, either.

Does this dmesg|tail output suggest what is wrong with the card?

adminq@pinebook1080p:~$ dmesg|tail
[  195.062891] sunxi-mmc 1c0f000.sdmmc: sdc set ios: clk 400000Hz bm PP pm ON vdd 16 width 1 timing LEGACY(SDR12) dt B
[  195.098407] mmc2: host does not support reading read-only switch. assuming write-enable.
[  195.107276] sunxi-mmc 1c0f000.sdmmc: sdc set ios: clk 25000000Hz bm PP pm ON vdd 16 width 1 timing LEGACY(SDR12) dt B
[  195.119012] sunxi-mmc 1c0f000.sdmmc: sdc set ios: clk 25000000Hz bm PP pm ON vdd 16 width 4 timing LEGACY(SDR12) dt B
[  195.130659] mmc2: new SDXC card at address 0001
[  195.137285] mmcblk1: mmc2:0001 SD16G 60.0 GiB
[  195.145172]  mmcblk1: p1 p2 p3
[  227.609344] systemd[1]: local-fs.target: Cannot add dependency job, ignoring: Unit -.mount is masked.
[  274.112550] JBD2: Unrecognised features on journal
[  274.125997] EXT4-fs (mmcblk1p3): error loading journal
adminq@pinebook1080p:~$


  Rk3399 isp documentation
Posted by: ktc - 11-16-2018, 07:14 AM - Forum: General Discussion on ROCKPRO64 - Replies (3)

I am unable find any documentation regarding the ISP block in RK3399. Is this available ? Where can I find it ?


  PCIe Endpoint Cable/Converter
Posted by: dlh - 11-16-2018, 02:52 AM - Forum: RockPro64 Hardware and Accessories - No Replies

I would like to use the RockPro64 as a PCIe endpoint. To do this, I believe I need a special adaptor / male to male cable. Any information on how I could do this or where to purchase such an adaptor would be much appreciated.


Thanks


  OpenPHT for ROCK64 Possible?
Posted by: soerenderfor - 11-16-2018, 12:58 AM - Forum: Linux on Rock64 - Replies (2)

Hi

Is there someone that can make OpenPHT work for ROCK64? Or can point me in the right direction to make it?

Best Regards.


Thumbs Up My shiipping experience! (Pinebook 11")
Posted by: caps - 11-15-2018, 04:25 PM - Forum: Shipment Related Discussion - No Replies

Hello!

I decided I'd make a thread about my pleasant shipping experience as opposed to all the negative ones that this forum often gets. I figured it's the least I could do.

So, I placed my order for a pinebook late september-ish, early october and found out I was moving. This ordinarily wouldn't be a problem but the mail forwarding in my country's postal service (Canada) doesn't work for packages and, in addition, it was being shipped via DHL anyway so there was nothing I could do! In desperation I reached out to the customer service folk via e-mail and they told me that, unfortunately, they could not change my address to a P.O. box that I had opened as the package required a signature.

Distraught, I explained my situation and they assured me that my package would be coming soon enough and that I would have nothing to worry about. They then went on and explained that they would be shipping them very soon and that DHL would only take a few days to deliver my package. Of course I didn't believe them but I gave them the benefit of the doubt which I'm very glad I did!

A few days later I got a text (not an e-mail) with my shipping information and tracking number. Two days later and I'm now exploring my new Pinebook! It came with the laptop itself inside of a blue, clear case that protected it during shipping and to my (pleasant) surprise a 1080p screen instead of 1366x768! Not to mention a bunch of stickers to place on things, including the laptop itself.

So, that's my experience! I'm very happy with my purchase and I'm glad my patience paid off. :D I'm even writing this on my pinebook now!

I'll include some photos of the packaging! (Ignore the beat up coffee table, it's not coming with us in the move lmao)

[Image: whmhDM2.jpg]
[Image: rMTjyj2.jpg][Image: LiHPVIZ.jpg]


  Step by step guide PXE diskless configuration.
Posted by: burglar_ot - 11-15-2018, 03:30 PM - Forum: Rock64 Tutorials - Replies (13)

I haven't find a guide to setup a proper PXE boot for Rock64 (and Pine64) cards, so I will write down mine here hoping that it is useful.

In this guide I assume that the user is familiar with Linux, another assumption is about the distributions:
- on the Rock64 card we are going to install the Debian minimal;
- on the server that will provide the operating system I use Debian.
I think this guide can work for other distributions too but I haven't tried other combinations.
For the rest of the guide all the commands will run on the server Debian.

About the hardware I tried on a Rock64pro, I have also a Pine64 and a Rock64 but are in production and I needed a spare board to do the tests. Now that it works I will try also for the others, but for this guide I assume the Rock64pro.

Step 1: Flash the SPI
This is actually the only step that requires an SD card.
The SPI is a little memory (128MB) that can be flashed to add instruction at the boot time. Ayufan has a nice SPI image that adds the possibility to boot from network (PXE), and we are going to use it.

So go to this link and download the image file that is useful for your system. I used the u-boot-flash-spi-rockpro64.img.xz file.
Uncompress it with

Code:
unxz u-boot-flash-spi-rockpro64.img.xz
and flash it on the SD card with dd
Code:
dd bs=1M if=u-boot-flash-spi-rockpro64.img of=/dev/sd<SOMETHING>
Put the card into the Rock64 board and boot it. I had no monitor connected so I do not know what it writes on a screen, but it is enough that you wait some time (one minute is probably enough) and you will see the boot (white) led flashing once per second. It means that the SPI is flashed. You can now turn off the board and remove the SD card.
Step 2: find the ethernet address of the board.
I assume that you have already a DHCP server installed in your network that assign the addresses to every device connected.
If this DHCP server is the router of your internet connection you will have to change it later (unless is a very advanced router and you can specify advanced features). In any case to identify the mac address is sufficient that something assign an IP address to your board.
So turn on your Rock64. It will now spin up and try to boot from SD, eMMC, USB and PXE, and it will fail in all of these tentatives because it has no cards installed and the network boot is not yet configured. Nevertheless, when it tries the PXE the board will get an IP and it will announce its existence to the local network. This means that after few seconds that the ethernet led flashes you can write on your Debian server
Code:
arp -a
and you will get the list of connected devices on the network with their IP address and hardware address.
Write down the ethernet address; the one that I will use in my example is 56:31:cd:bb:92:7b.
Step 3: the DHCP server.
We need a DHCP server capable of some advanced features if you have the DHCP on your router you have to disable it and from this moment on you will use the DHCP on your Debian server.
Install it with
Code:
sudo apt-get install isc-dhcp-server
Once installed edit the /etc/dhcp/dhcpd.conf in this way

Code:
ddns-update-style none;
option domain-name "whatever.com";
option domain-name-servers 192.168.0.1;
default-lease-time 6000;
max-lease-time 72000;
log-facility local7;

subnet 192.168.0.0 netmask 255.255.255.0 {
   range 192.168.0.2 192.168.0.99;
   option subnet-mask 255.255.255.0;
   option broadcast-address 192.168.0.255;
   option routers 192.168.0.1;
   option domain-name-servers 192.168.0.1;
}

host rock64pro {
  hardware ethernet 56:31:cd:bb:92:7b;
  fixed-address 192.168.0.100;
  next-server 192.168.0.1;
}
authoritative;
I don't want to go into the details but basically this configuration allocates random addresses between 192.168.0.2 and 192.168.0.99 for the normal devices (like computers or telephones) and assign the 192.168.0.100 to the rock64pro identifying it with the ethernet address that we find in the previous step. Moreover, and this is the advanced feature, the server will tell to the rock64pro that after it takes the address it has to communicate with 192.168.0.1 for "further instructions" (the next-server directive).
Here I am assuming that 192.168.0.1 is the IP address of the Debian server.
Once this file is in place restart the DHCP server with

Code:
sudo systemctl restart isc-dhcp-server
 You can test if this configuration works turning on the Rock64pro board, waiting couple of seconds and try again the arp -a. If everything is fine you should see that now the Rock has the address 192.168.0.100.

Step 4: TFTP server
We have now to instruct the Rock64pro for the next step. The way to take information is through a special version of an ftp server called tftp (t is for trivial). So we need a tftp server running on our Debian and to install it we do
Code:
sudo apt-get install tftp-hpa
once installed edit the file /etc/defaults/tftpd-hpa as
Code:
TFTP_USERNAME="tftp"
TFTP_DIRECTORY="/storage/pxe-boot/tftp"
TFTP_ADDRESS="192.168.0.1:69"
TFTP_OPTIONS="--secure"
here I am assuming that we will store the data to boot the Rock64pro into a directory /storage/pxe-boot and in this directory we will put all the files for the boot and for the operating system.
So we need to do these steps

Code:
sudo mkdir /storage
sudo mkdir /storage/rock64pro
sudo mkdir /storage/tftp
sudo mkdir /storage/tftp/pxelinux.cfg
  In rock64pro we will put the operating system (the content of the boot image) while in the tftp we will put all the files to the initial boot procedure (linux kernel and its configurations).
Now we can restart the tftp server
Code:
sudo systemctl restart tftpd-hpa

Step 5: NFS server
The kernel and the boot execution is provided through the tftp server, but the operating system will live entirely on a folder that will be served to the rock64pro through NFS, so we need a working NFS server.
To install it
Code:
sudo apt-get install nfs-kernel-server rpcbind
the edit the file /etc/exports as
Code:
/storage/pxe-boot/rock64pro     *(rw,sync,no_root_squash)
and the file /etc/hosts.allow as
Code:
portmap: 192.168.0.
The first file says to NFS server that has to export the directory /storage/pxe-boot/rock64pro to everyone with specific flags (read/write, sync, and no limitation for root). The second file allows the IPs of the subnet 192.168.0.x to connect to the NFS server. You may want to limit the NFS server only to the IP of the rock64pro substituting 192.168.0.100 to the * of the exports file and writing the full ip into the hosts.allow.
Restart the NFS server with
Code:
sudo systemctl restart nfs-kernel-server

Step 6: setup the filesystem
Download the Debian image for your Rock card from this link (you can use wget). I used the stretch-minimal-rockpro64-0.7.11-1075-arm64.img.xz. Uncompress it with
Code:
unxz stretch-minimal-rockpro64-0.7.11-1075-arm64.img.xz

Once downloaded you have to mount the linux partition contained in the img file. The file contains also another partition that is to boot and we are not interested in it, so we have to find the right position of the linux. To do it we use fdisk as

Code:
sudo fdisk -l stretch-minimal-rockpro64-0.7.11-1075-arm64.img
the result is something like
Code:
Disk stretch-minimal-rockpro64-0.7.11-1075-arm64.img: 2 GiB, 2144337920 bytes, 4188160 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: FB84DCAE-4E0E-486F-890C-A979BEECCFF9

Device                                            Start     End Sectors  Size Type
stretch-minimal-rockpro64-0.7.11-1075-arm64.img1     64    8063    8000  3.9M Linux filesystem
stretch-minimal-rockpro64-0.7.11-1075-arm64.img2   8064    8191     128   64K Linux filesystem
stretch-minimal-rockpro64-0.7.11-1075-arm64.img3   8192   16383    8192    4M Linux filesystem
stretch-minimal-rockpro64-0.7.11-1075-arm64.img4  16384   24575    8192    4M Linux filesystem
stretch-minimal-rockpro64-0.7.11-1075-arm64.img5  24576   32767    8192    4M Linux filesystem
stretch-minimal-rockpro64-0.7.11-1075-arm64.img6  32768  262143  229376  112M Microsoft basic data
stretch-minimal-rockpro64-0.7.11-1075-arm64.img7 262144 4186111 3923968  1.9G Linux filesystem
Here you have to identify two things: the first one is the size of one unit sector (512 bytes) and the second information is the begin of the filesystem that we are looking for. In our case it is the last one and we know because is the one of 1.9GB of size. Then this filesystem starts at the position 262144. Now we multiply these two numbers: 512x262144=134217728. This is the starting position of the linux partition. We can use it to mount the partition as

Code:
sudo mkdir /storage/tmpimage
sudo mount -o loop,offset=134217728 stretch-minimal-rockpro64-0.7.11-1075-arm64.img /storage/tmpimage

now we copy the content of the filesystem into our nfs server. I use rsync to do it because I trust the way it preserves permissions and links, but probably a simple cp -a can do the job.

Code:
sudo rsync -val /storage/tmpimage/* /storage/pxe-boot/rock64pro/
After the sync the image is no longer needed

Code:
sudo umount /storage/tmpimage
sudo rmdir /storage/tmpimage
sudo rm stretch-minimal-rockpro64-0.7.11-1075-arm64.img

Step 7: Finalize the boot
We have now the system ready, we need only to put in the tftp directory the instructions to send the kernel to the board for the boot.
To do this we first copy the boot folder of the rock64pro filesystem to the tftp directory. We need to do it because we need to provide the kernel via tftp before mounting the NFS root.

Code:
sudo rsync -val /storage/pxe-boot/rock64pro/boot /storage/pxe-boot/tftp/

finally we need to provide to the board the extlinux.conf boot file. When the Rock boots it searches for a boot file with various names, we will use the pxelinux.cfg/default-arm-rockchip. So we first copy the extlinux.conf as
Code:
sudo cp /storage/pxe-boot/tftp/boot/extlinux/extlinux.conf /storage/pxe-boot/tftp/pxelinux.cfg/default-arm-rockchip
then we need to edit this file because by default it will try to load the kernel from the storage device (SD Card) but we want to mount the root directory from the nfs server. So edit it, remove the second block and modify the line of root as the following
Code:
timeout 10
menu title select kernel

label kernel-4.4.154-1124-rockchip-ayufan-ged3ce4d15ec1
   kernel /boot/vmlinuz-4.4.154-1124-rockchip-ayufan-ged3ce4d15ec1
   initrd /boot/initrd.img-4.4.154-1124-rockchip-ayufan-ged3ce4d15ec1
   devicetreedir /boot/dtbs/4.4.154-1124-rockchip-ayufan-ged3ce4d15ec1
   append rw panic=10 init=/sbin/init coherent_pool=1M ethaddr=${ethaddr} eth1addr=${eth1addr} serial=${serial#} cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1 root=/dev/nfs nfsroot=${serverip}:/storage/pxe-boot/rock64pro rootwait rootfstype=ext4
the only part to modify is the root= and the nfsroot= the rest of the file is the same as the extlinux.conf.
Finally, the SD card mounts the boot directory from a vfat partition while we are using our tftp boot, so we need to fix this.
The way is to edit the file /storage/pxe-boot/rock64pro/etc/fstab and remove the line about the boot (that should be the only one, so the final file will be empty).
Known Issues.
The reboot does't work always. It seems that the tftp server stucks and doesn't work in the next boot. I will try another tftp server.
The workaround is to force kill the tftpd and restart it.

If in the update process some component of the boot is upgraded, it is necessary to update the tftp boot folder and the pxelinux.cfg/default-arm-rockchip.


  [SOLVED] HELP! Four clocks on panel!
Posted by: jschall - 11-15-2018, 01:28 PM - Forum: General Discussion on Pinebook - Replies (2)

I'm running Q4OS with KDE Plasma DE.

Somehow I managed to add 4 analog clock widgets to the panel. I can't find any way to delete a widget from the panel.

HELP!


  Alsamixer - can't select with keys
Posted by: jschall - 11-15-2018, 10:00 AM - Forum: General Discussion on Pinebook - Replies (2)

I'm trying to adjust speaker and headphone volume with alsamixer.

But  it is stuck at the "Master" output, and the Left, Right, Up, Down keys don't work.

How can I get alsamixer working?