Hi there,

I am pretty new to this whole topic and therefore that might be a noob question 


I’ve bought a ROCKPRO64 and my goal is to build a NAS with openmediavault. For Powering the HDDs I had ordered the cable by pine64 but somehow I forgot to order the raid/sata controller. 

In hope that everything would work here I just bought a Raid Controller online now, actually it is a Star Tech 2xSATA Raid Controller with Marvell - 88SE9128 Chipset. As soon as arrived directly pluged into my rockpro64 but unfortunetaly I can not see the Raid Controller and therefore of course also no Disk ... :/ Google around a bit and checked with lspci etc but never able to see the raid controller. 

Can you help me out here please? Or is this Controller simply just not supported with the rockpro? 

Thanks a lot for your Help,
Kind Regards,
MAN

Hello! I've been using Manjaro Arm (burned on the emmc) on my PBP for a few weeks now and it's awesome; thanks a lot for all the work that goes into this. Really love this pinebook.

But I do have a problem happening on boot:
When I hold the Power button a few seconds, the LED light up; but the screen stays dark for 32s before anything starts showing (the M Manjaro logo comes first; then my login screen).
It's a shame because once the screen lights up the boot is pretty fast. Is this delay normal? I don't remember having these kind of delays on the default debian install.

The 30s value make me think it could be a timer on a misconfigured u-boot that maybe tries some invalid boot option, wait for 30s then tries Manjaro? I have no expierience with u-boot and am not very clear on how to debug this issue? Any clues would be welcome.

Had my PBP now for a couple of months and while the default build it shipped with was fine I have been messing around with the excellent Mate build kindly done by Wizzard  here

https://forum.pine64.org/showthread.php?tid=8119

............................but stopped short of installing KDE as I had used Kubuntu for a few years before and the Mate build was good. I had even installed Mutiny Theme



However I have been using Unity Ubuntu and now Ubuntu Desktop for long enough on a main pc that I wanted to install Ubuntu (classic as I call it) 

After a few failures I realised that just installing ubuntu-desktop on top of the Mate build was not going to work for me

It installed but would not boot even with LightDM and GDM seemed to just break the installation. So another method was needed.

I reinstalled the Mate build and then followed the updates kindly provided by Ayufan here after of course installing the trackpad updates and uboot fixes

https://github.com/ayufan-rock64/linux-b...tag/0.9.14

Then installed ubuntu-unity-desktop with the following command:

sudo apt install ubuntu-unity-desktop --install-recommends

This installed fine and booted as well after selecting Unity (default) at login



However this gave me some small problems as none of the apps I use showed up in the Dash when pressing the Pine super button.

Secondly I could not open a terminal and lastly my right click on the trackpad no longer worked

So I had to reach out for help

Firstly after a few hours of thinking I remembered the old skills.

I hit Alt and F2....of course....then search for terminal  (see attached photo)

Bingo

Same for finding all the other apps I needed and had installed on Mate build

This kindly provided by Tophneal fixed the right click issue:

https://itsfoss.com/fix-right-click-touchpad-ubuntu/

So Pinebook now up and running with Unity Ubuntu ...a few system errors but for now ....its just how I want it for now...no doubt it will come with a few issues but it looks good enough

See other attachment

Good luck and let me know if you get stuck

Also keen to see if others have had better luck with another method

Just some glamour shots I took while filming the unboxing of my Pinebook Pro ANSI notebook for Category5 TV.

You're welcome to use them (commercial or non-commercial), royalty free, but please credit me (CC BY 2.0 CA). See license.txt for info.

Don't forget to give me a "thumbs up" RATE below if you like or use the photos, or just appreciate me sharing them

Full-res download: https://drive.google.com/drive/folders/1...sp=sharing

Sample Thumbnails:

I've had the Pinebook Pro for a few months now, and it's been perfectly fine until this afternoon. I was using it earlier this morning, plugged in with the barrel jack at 10% charge, to watch YouTube on the default OS. I left it to charge for a few hours (again, with the barrel jack) and when I came back the computer had zero charge. It will boot when plugged in, but of course shuts down when power is removed. I opened up the device and nothing appears out of the ordinary.

Hello,

the command : pmbootstrap install --sdcard /dev/sdb

ask muliple sudo passwod :
(base) moi@debian:~/pmbootstrap$ pmbootstrap init

[16:34:16] Location of the 'work' path. Multiple chroots (native, device arch, device rootfs) will be created in there.
[16:34:16] Work path [/home/moi/.local/var/pmbootstrap]:
[16:34:32] WARNING: Your work folder version needs to be migrated (from version 0 to 4)!
[16:34:32] Changelog:
[16:34:32] * Building chroots have a different username (#709)
[16:34:32] Migration will do the following:
[16:34:32] * Zap your chroots
[16:34:32] * Adjust '/home/moi/.local/var/pmbootstrap/config_abuild/abuild.conf'
[16:34:32] Continue? (y/n) [n]: y
[sudo] Mot de passe de moi :
[sudo] Mot de passe de moi :
[16:34:52] Cleared up ~0 MB of space
.../...

Hi

I'm trying to get hdmi hotplug on a rock64 with debian buster. HDMI only works if I boot it with a screen already attached. I tried explicitly specifying the EDID but got a "size is invalid" there, and it's not exactly what I want, it should detect whatever screen I plug in. 

Any help?

https://linuxjourney.com/?utm_source=omgubuntu

Learn the ways of LINUX.

  In the wiki the boot order with the "OEM Debian installed" is listed as :
     1)  SD card
     2)  eMMC
           (This boot order is loaded on the original OEM eMMC install)
  
     So the SD will boot first if one is installed, or it will go to the eMMC if there is no SD card.
        --------------------------


         But the board default is listed as :
          1) SPI NOR
          2) eMMC
          3) SD card
          4) USB OTG

       Does this mean that if it does not find anything bootable on #1 or #2 that it should still default then to the SD card ?
   
      Since there is nothing on the SPI NOR from the factory, and if one was to botch their eMMC during a failed installation
      or maybe just wiped it clean, ..  ..  ..  then the SD card should 'boot'  ?
           (a botched install may cause it to hang "trying" to boot from the eMMC) ?

       BUT,  the SD card being used still must have the ''Correct boot instructions for this particular board"... (? yes ?)
            boot instructions being matched to the hardware being used... ?
                                  -----------------------------


       The OSes listed in the wiki have the correct boot software already installed ?
            SO ?  If you want to install a different OS, you need to perhaps borrow the boot portion from a working OS ?

Inadvertently I chose a photo in some start up menu. Now on start up the photo fills the screen and I can't log in. Anyway to get around this?