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

Username
  

Password
  





Search Forums



(Advanced Search)

Forum Statistics
» Members: 29,466
» Latest member: Creig
» Forum threads: 16,192
» Forum posts: 116,855

Full Statistics

Latest Threads
Pinephone Pro wont boot t...
Forum: General Discussion of PinePhone Pro
Last Post: KNERD
11 hours ago
» Replies: 1
» Views: 68
PinePhone Pro discontinue...
Forum: General Discussion of PinePhone Pro
Last Post: KNERD
11 hours ago
» Replies: 4
» Views: 155
Are there plannes to crea...
Forum: PinePhone Pro Hardware
Last Post: franzthiemann
Yesterday, 04:43 AM
» Replies: 2
» Views: 801
prototyping to help someo...
Forum: General
Last Post: xerosenex
Yesterday, 02:31 AM
» Replies: 0
» Views: 42
Password reset via u-boot...
Forum: PineNote Software
Last Post: lunnabae
08-13-2025, 01:17 AM
» Replies: 6
» Views: 1,698
incorporate a multimeter ...
Forum: General
Last Post: lalisa12
08-13-2025, 01:14 AM
» Replies: 2
» Views: 494
New PineNote: No WiFi aft...
Forum: PineNote Software
Last Post: krexplex
08-12-2025, 01:09 PM
» Replies: 5
» Views: 1,419
Full desktop Surfing and ...
Forum: General Discussion on Pinebook Pro
Last Post: Pattienner
08-10-2025, 10:35 PM
» Replies: 2
» Views: 478
Any recommended brands/mo...
Forum: Pinebook Pro Hardware and Accessories
Last Post: fnfgopro
08-10-2025, 08:38 PM
» Replies: 2
» Views: 859
Thoughts after a year wit...
Forum: General Discussion on Pinebook Pro
Last Post: tantamount
08-10-2025, 02:25 PM
» Replies: 3
» Views: 620

 
  Eth0 dhcp issues
Posted by: LTronic - 08-27-2017, 03:10 AM - Forum: Linux on Rock64 - Replies (5)

Hello,

Pretty often at boot time my eth0 does not get an DHCP address assigned.
I have to play with

sudo dhclient
sudo ifconfig eth0 down
sudo ifconfig eth0 up

between 2 and 5 times to finally get network configuration from DHCP server.

Is it a known issue on Linux (happens on most images I have tested) ?
I have seen a similar thread on Android.

Well at least since latest ayufan fixes (0.5.1 images) we always get the same MAC address Smile


  Writeup About Pinebook
Posted by: dahni - 08-27-2017, 01:49 AM - Forum: General Discussion on Pinebook - Replies (4)

Hi everyone, just thought i'd share this article:
http://dt.iki.fi/pinebook/
i have outlined the whole process from getting the pinebook to having it work satisfactorily.
i really recommend the two distros i tried: Q4OS and armbian.


  Xenial Mate: Screensaver Preview & LibreOffice Slideshow problems
Posted by: moravecz - 08-26-2017, 09:59 PM - Forum: Linux on Rock64 - Replies (2)

Using Xenial Mate on Rock64 4GB, I have consistent problems with the Control Center Screensaver and the LibreOffice Impress Slideshow. 

In the Control Center Screensaver whenever I press the Preview button, the system locks up. The mouse cursor moves around, but both keyboard and mouse are not able to do anything.

In LibreOffice Impress, when I try to run a Slideshow (F5), the Slideshow is not seen, but the system appears to be locked up. The mouse cursor moves, but you cannot do anything on the desktop. However, if you press the Esc key, then LibreOffice Impress returns to normal mode. It seems like it tried to launch the Slideshow, but the Slideshow never appears.  Note that the LibreOffice Impress Slideshow function worked correctly and reliably in the Debian image Build 20170809. So there is something unique about the CXenial Mate image. 

Any suggestions would be very much appreciated.


Information How to Setup Serial Console Cable Over the Rock64 SBC
Posted by: MarkHaysHarris777 - 08-26-2017, 08:22 PM - Forum: Rock64 Hardware and Accessories - Replies (10)

Greetings,

The purpose of this photo blog is to provide a tutorial on setting up a serial console over the Rock64 ( or any other SBC ) from the Pinebook ( or any other notebook ) !


Materials & Preparation

You will need a usb extension cable ( two 1m cables will do ) and the CH340g usb to serial ttl bridge adapter carried by the Pine store.  Also you will need to have three  6"  F-F  jumper wires;  the ch340g is placed in short proximity to the Rock64 board and is attached to the Rock64 via the three F-F 6" jumper wires to the PI-2 bus, pins ( 6, 8, 10 ) covered later.  The usb extension cable(s) then run from the ch340g adapter to the notebook computer;  in this case the Pinebook.  You will also need to make sure you have serial terminal software installed ( I recommend the old standby minicom ).  We'll talk about that later as well.

Theory and Pinebook caveats

The theory is fairly straight-forward;  the Rock64 has a uart serial console port on the PI-2 bus pins (6, 8, 10) which allows another computer ( Pinebook ) to connect from usb port via the serial console adapter ( ch340g ).  

With the terminal software running , and all connections correct , you will be able to see the console messages from the Rock64 when the SBC boots, on the serial console terminal.  You can debug boot-up messages, also shutdown messages, as well logon to the Rock64 from the serial console after boot-up. 

         

The Pinebook usb ports are not identical.  For one thing the correct port ( pic on right ) is on a usb hub, and is designed to be used as a console.  The "incorrect" port to use ( pic on the left ) should not be used as a console.  Failure to heed the warning to use only the correct port ( the right-hand usb port ) will cause you endless frustration, grumpiness, and probably hair loss.  

Procedure

Make the Connections to the CH340g

                   

The pic at the left shows the connections on the CH340g;  the pic at the right shows the connections at the Rock64 SBC.  I like to Scotch tape the CH340g to the table top in close proximity to the Rock64;  so that the 6" F-F jumper wires can easily be connected.  The Tx, Rx, and gnd are in reference to the Rock64 SBC.  You will notice that the Rock64 Tx is connected to the CH340g Rx, and the Rock64 Rx is connected to the CH340g Tx.  The ground from the Rock64 is connected to the ground on the CH340g.  

                Rx-->Tx,   Tx-->Rx,    ground--ground

Notice that the gold jumper on the CH340g is set to select 3v3 logic level for the adapter.  This is critical.  Failure to observe this will irrevocably damage your Rock64 !  (words to the wise) 

The red LED on the CH340g is a power indicator;  there are other green LED(s) by the connectors which flicker during comms.  

Do not plug in the green Rx wire at this time;  this is the transmit (Tx) line from the CH340g and usually carries 3v3 even in idle which will "back feed" or bleed current into the Rock64 often keeping it from booting up !  We will wait to plug in the Rx line until after the boot-up and when we have a logon prompt on the console.

Plug in the usb cable extension into the CH340g;  this will run over to the Pinebook ( or other notebook ).

Plug in the USB Cable on the Pinebook and Start the Terminal Software 

Plug the other end of the usb extension cable into the Pinebook right-hand usb port ( note that the left-hand usb port is not suitable as a console port ).  Open a terminal on the Pinebook.  This terminal will become the serial console.  For now issue the following command to verify that the Pinebook can "see" the  CH340g serial adapter:

          dmesg  |tail  -n  10

You should see a line that says, " usb ch341-uart converter now attached to ttyUSBx ".  Pay attention to the ttyUSBx!  This will probably be ttyUSB0,  but it may be another value;  this is the device that you will enter when you start the minicom terminal emulation software for serial comms with the Rock64.

Start the console terminal emulation software ( minicom ) with the following command sequence:

          sudo  minicom  -s  -D  /dev/ttyUSB0  -b  1500000  --color=on

The  -s  flag will open the configuration menu when minicom initiates;  select "Serial Port Setup" and press enter.  On the serial port setup dialogue check your defaults ( 1500000 8N1  /dev/ttyUSB0 ) and make sure that hardware and software flow control are both NO;  then press the enter key.

Select  'Exit'  from the menu, and press the enter key;  the terminal emulation software will be running.

Note:   If your device ( found with dmesg ) was not /dev/ttyUSB0 then use your device in the minicom initialization command sequence !

Boot the Rock64 SBC

Apply power to the Rock64 SBC board and almost immediately the Rock64 boot-up messages will begin scrolling down the serial console terminal emulation software running on the Pinebook.  Congratulations! --  you have setup a serial console over your Rock64, using your Pinebook !   ... nice job.

When the logon prompt appears on the serial console then plug the green Rx line from the Rock64 into the CH340g Tx pin, and then logon to the Rock64 from the serial console on the Pinebook.  To shutdown the Rock64 enter:

                 sudo halt

You will be able to see the shutdown messages as well ! 


             


The pic above is the serial console running on my Pinebook over my production Rock64 running xenial-mate 0.4.16 #83.  You will notice the RED status bar at the bottom of the terminal.  You will not see this unless you grab the bottom edge of your terminal with your mouse and pull the bottom of the terminal down ONE line  ( 80x25 ). 

Shy


  ROCK64 Acrylic Enclosure Assembly
Posted by: ironhand - 08-26-2017, 02:17 PM - Forum: Rock64 Hardware and Accessories - Replies (2)

Has anyone installed his ROCK64 in the 'ROCK64 ACRYLIC OPEN ENCLOSURE'?  There don't appear to be any assembly instructions....  From the product photo, it looks like the board is supposed to be pressed onto the toothed brass standoffs that are included with the enclosure hardware but the mounting holes on the board would have to be opened-up a bit in order to be pressed on to the standoffs and not damage the board.  I don't want to open up the holes if there's something I'm missing regarding the assembly...

Thanks!

Ron


  ROCK64 STEREO AUDIO DAC ADD-ON BOARD Sketch
Posted by: killor - 08-26-2017, 07:37 AM - Forum: Rock64 Hardware and Accessories - Replies (4)

Hi !!

I have already made a first design of a wooden enclosure for Rock64
(you can see here  rock64 wooden case  )


But I want to make an adaptation for
 the Audio board called ROCK64 STEREO AUDIO DAC ADD-ON BOARD [Image: undecided.png] ...

Soo

I attach a link to download a PDF of a sketch,
 And the measures I need to make the new case Adapted for the ROCK64 audio card. too..

PDF Rock64 stereo Audio DAC sketch

Thanks for your great help ..!!  Angel


Information How To Setup Serial Console Cable Over the Pinebook
Posted by: MarkHaysHarris777 - 08-26-2017, 06:05 AM - Forum: Pinebook Hardware and Accessories - Replies (4)

Greetings,

The purpose of this photo blog is to provide a working tutorial for setting up a serial console over the Pinebook, by utilizing the audio headphone jack which also doubles as a universal asynchronous receiver|transmitter; uart(0).



Materials

You will need a usb extension cable for the serial adapter cable.  You will also need a usb ttl serial bridge adapter.  And you will need a 3.5 phone plug and cable.  The headphone jack is technically an apple style four pole 3.5 jack;  however, a three pole plug will work also.  You might also want to have some electrical tape, shrink tubing, and female header connectors;  I made my phone jack cable; however, commercial cables are available !

Theory

The serial console is the "sonic screwdriver" of the embedded world.  With it you can monitor boot-up messages, shutdown messages, and even logon to the system via serial connection with terminal software like minicom, from another system. The Pinebook's audio headphone jack has a double function;  with minimal configuration steps ( all covered here ) the headphone jack may be configured to run as a serial uart(0) device.

Procedure

                      


First let's talk about the plugs diagram pic(s) above;  the headphone jack is a four plug port, but a three pole plug will work just fine.  I have chosen to use a three pole plug for the proof of concept, and because they are readily available from the market with a cable-- ready for the female header jumpers to be installed.

In the left pic above the plugs have been labeled:  tip--Rx,  ring--Tx,  ring--Gnd.   These labels are in respect of the Pinebook; in other words, the labels are the Pinebook's pin definitions. The Pinebook receives on Rx (red wire, tip) and transmits on Tx (white wire, ring).  The second ring is the Pinebook's ground, and the collar (unused) is the Pinebook's mic connection.  The reason the three pole plug works is that the HP-jack shorts the unused mic connection to ground;  the important connections Rx, Tx, and Gnd  are all valid and fully functional.  I chose to use the right angle three pole plug in the pic, but feel free to use an actual four pole plug if you feel more comfortable with that electrical choice ( it really comes down to availability and price ).

Create the Cable

Please refer to the pics above.  I have added standard female header jumpers to my phone plug cable (solder and crimp) and then have sealed it with heat shrink tubing.  Make sure the plug is fully seated in the HP-jack-- not doing so is a common mistake which will keep your serial console from working !  You will notice from the pic of the ch340g adapter that the red Rx line from the Pinebook is plugged into the adapter Tx position, and that the white Tx line from the Pinebook is plugged into the Rx position of the adapter  (ground black is plugged into ground). The relationship is cross-wired for serial comm as follows :    ( you must use all three wires )

                                Rx-->Tx,  Tx-->Rx,  ground--ground

Please note the gold jumper in the second pic from the left.  This jumper on the ch340g (from the Pine Store) selects the logic voltage either 5v or 3v3.  Important:  always set the logic voltage to 3v3;  failure to do so can irreparably damage your Pinebook!  On the connector end of the ch340g serial adapter exist green LED(s) which will flicker during xmit and recv;  the red LED is a power indicator for the usb 5v rail.

Plug in the Cables and Connectors

I am actually using the Pine Rock64 board (desktop configuration running xenial-mate) as the serial console over the Pinebook.  I have connected the usb extension cable into the Rock64 usb2.0 lower port, and I have plugged the other end of the usb extension cable into the ch340g serial ttl bridge adapter ( make sure to set the logic jumper to 3v3, or you will damage your Pinebook!).  The ch340g adapter may be purchased from the Pine store for about $1.98 usd.  This adapter has become my standard go-to  serial adapter for all of my serial console use cases.

          Important Note:   In the pic above you will notice that all three wires are plugged in.  In practice don't do this on the outset;  only plug in the black and white wires-- only ground and the Pinebook's transmit wire ( in my case white-Tx ).   The reason for this is that often the Pinebook will not boot at all, or only partially boot, if the red wire-Rx is plugged in-- because the Tx line from the Rock64 provides 3v3 voltage (bleed current) that interferes with the Pinebook!  Start the boot-up with the red-Rx wire unplugged and then plug it in after the logon prompt appears on the console.  Failure to heed this warning will cause frustration -- words to the wise.

Start the Terminal Software

Open a terminal on your Rock64 ( or other gnu+linux computer);  this terminal will eventually be our serial console, but for the time being enter the following command after connecting the CH340g to the Rock64 usb port:

         dmesg  |tail  -n  10

Assuming the kernel can "see" your CH340g you should see this line in the output:

          usb ch341-uart converter now attached to /dev/ttyUSB0

If your device is different, please make a note of it;  you will use that device name in the minicom initialization command string below!

I prefer to use minicom for my terminal software-- it is the old standby;  others will work like "screen,"  or "cu".  Minicom is the best in my opinion;  the most flexible, and has the most features.  Please refer to the minicom man page for details. From a terminal on the Rock64 I start minicom with the command sequence :

          sudo  minicom  -s  -D  /dev/ttyUSB0  -b  115200  --color=on

The  -s  flag will take you into the minicom configuration panel;  choose Serial Port Setup and confirm the following defaults;  make sure the software and hardware flow controls are both set to NO.

      device  /dev/ttyUSB0
      baud  115200
      parms  8n1    8 bits,  no parity,  1 stopbit

... on the same panel press enter,  then select 'exit' and press enter again;  the serial terminal emulation software should now be running.

Set the Pinebook for uart(0) mode, and plug in the 3.5 jack plug

To use the uart(0) serial port you must toggle a switch inside the Pinebook.  Please refer to this link for details.

Also you will need to shutdown the headphones service in systemd with the following command:

           sudo  systemctl  disable  pinebook-headphones     ( important )

          plug in the 3.5 cable plug

Power-ON the Pinebook

With all connections made, and the terminal software running on the Rock64,  power up the Pinebook by pressing the power button briefly.  Almost immediately (everything being correct) boot-up messages will begin flowing on the serial console, culminating in a logon prompt  ( at this time plug in the red-Rx wire from the Pinebook to the ch340g ). 

   

The pic above is the console running on my Rock64.   I have logged on to the Pinebook and run some commands, the output(s) of which you can see here.

We now have a serial console running. We can use it for boot diagnostics, as a control terminal interface and to view the power-off messages as well.

Press the power button;  the shutdown dialogue will appear on the Pinebook.  Select 'shutdown' and again, almost immediately the shutdown messages will scroll down the serial console culminating in systemd  target shutdown , and then the Pinebook should power off. 

Close the Terminal Software

Press Ctrl + A on the serial console minicom software.  Then press x followed by the enter key.  Minicom will exit


Information Pinebook Linux Power-Down Procedure
Posted by: MarkHaysHarris777 - 08-26-2017, 03:12 AM - Forum: Linux on Pinebook - Replies (3)

Greetings, 

The Pinebook Linux Power-Down Procedure that has been found to be most effective (although not 100% reliable) is to use the "power button" to pull up the shutdown dialogue !




Testing has shown that if the shutdown command happens in a terminal (or serial console), or if it is selected with the mouse from the System menu or the tool-bar the system  correctly hits the systemd target shutdown;  however, the hardware ARISC PMIC does not power off the system.

On the other hand,  if the user will press the actual "power button"  (upper right hand key on the keyboard)  then after the systemd  target shutdown the hardware will correctly (most of the time) power off the hardware.

... but don't trust it,  check it !!


Shy


  Pinebook first impressions
Posted by: Pagliacci - 08-26-2017, 02:18 AM - Forum: General Discussion on Pinebook - Replies (11)

Just received the Pinebook.

First impressions and thoughts.

At first all seemed well.

The battery was 95% charged upon delivery so that was an improvement on many people's experience (flat due to not shutting down properly after testing).

Then I spotted a stuck LCD panel pixel - just a single pixel off to the upper left screen permanently green. Poor QA. Should never have left the factory in that condition.

More concerning is quite serious keyboard faults. For some reason I can't fathom, the '-' (minus) key (between '0' (zero) and '+' (plus) produces multiple key presses on a single quick touch, and then sticks causing repeat characters until I hit another key. Disabling the key repeat in the Mate operating system helps, but why the fault?

I've checked the seating of the ribbon cable. It is fine. I've even lifted off the key cap. No difference with the key cap off and no change when I pop it back on either.

Additionally, I later found that the combination left Shift and 'm' does not produce a capital 'M'. It doesn't produce any key press. The right Shift combined with 'm' correctly produces 'M'.

I can't work out how, if or whether this could be a physical hardware problem or a software scan problem.

Finally, there is no video output to the mini HDMI port on the left hand side on the Pinebook. Should this work yet or do I need to wait for a driver update?

I also have a Rock64, 4GB RAM with 64GB eMMC, which I am very impressed with. I even managed to flash the eMMC without faffing about with a console cable. Just used a jumper cable (actually a GPIO wire from my several Raspberry Pi models!), waited for a few seconds so both eMMC and microSD card were visible to the system, booted off the SD and then wrote an image to /dev/mmcblk0 (the eMMC)

On the whole I am quite disappointed with the Pinebook and regret buying it.  I am pleasantly surprised with the Rock64 which seems to hold much promise. I'm glad I didn't suffer the dreadful experiences with the original Pine64. But I feel I've been stung with the Pinebook. Should have just stuck with the order for the Rock. Oh well!

Any advice and comments would be welcome.


  android 7.1 v0.3.10-r66 wifi issues
Posted by: m1ntamorph - 08-26-2017, 01:40 AM - Forum: Android on Pinebook - No Replies

Hi ,

I have noticed the 90% of the times when I turn on the pinebook the wifi does not work. If I check the settings it seems to be active and  stuck at looking for hotspots. No amount of starting /stopping the wifi works.  The only way to fix this is to  activate Flight Mode and then deactivate it after a few seconds. Any idea? Any suggestion for a permanent fix ? Thanks