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

Username
  

Password
  





Search Forums



(Advanced Search)

Forum Statistics
» Members: 29,524
» Latest member: WarrenCop
» Forum threads: 16,205
» Forum posts: 116,934

Full Statistics

Latest Threads
Experimental Mobian kerne...
Forum: PinePhone Pro Software
Last Post: Jite
1 hour ago
» Replies: 8
» Views: 1,166
Why projects like PinePho...
Forum: General Discussion on PinePhone
Last Post: Kevin Kofler
2 hours ago
» Replies: 2
» Views: 158
irradium (based on crux l...
Forum: Linux on Quartz64
Last Post: mara
09-01-2025, 10:26 AM
» Replies: 6
» Views: 3,497
The PPP behaves as if the...
Forum: General Discussion of PinePhone Pro
Last Post: teekay
09-01-2025, 04:07 AM
» Replies: 2
» Views: 471
Pinephone Pro Neural Proc...
Forum: General Discussion on PinePhone
Last Post: biketool
09-01-2025, 02:05 AM
» Replies: 1
» Views: 1,509
Giving away a Pinebook Pr...
Forum: Pinebook Hardware and Accessories
Last Post: alchemist
09-01-2025, 12:24 AM
» Replies: 4
» Views: 2,066
A few questions before I ...
Forum: General Discussion on PinePhone
Last Post: L67GS
08-31-2025, 01:41 PM
» Replies: 4
» Views: 583
Want to buy second hand P...
Forum: General Discussion on PinePhone
Last Post: Fish
08-31-2025, 07:18 AM
» Replies: 2
» Views: 2,112
Star64 Irradium (based on...
Forum: Getting Started
Last Post: mara
08-30-2025, 05:47 PM
» Replies: 7
» Views: 4,056
StarPro64 Irradium (based...
Forum: Getting Started
Last Post: mara
08-30-2025, 03:28 PM
» Replies: 6
» Views: 1,276

 
  [solved] Unable to start X
Posted by: Osiander - 07-09-2018, 06:56 AM - Forum: Linux on Rock64 - Replies (8)

Hello together,

I've got some troubles to start X on my Rock64.

So, fist of all I've donwloaded "Debian Stretch Mate Community Build Image [microSD Boot] [0.5.15-136-20171222]", this one: http://files.pine64.org/os/ROCK64/debian...m64.img.xz

After burning the image on sd I've bootet from this and then apt update and apt upgrade.

After reboot I've saw in the console:

Code:
[  OK  ] Started Light Display Manager.
[  OK  ] Stopped Light Display Manager.
[FAILED] Failed to start Light Display Manager.
See 'systemctl status lightdm.service' for details.

Okay, systemctl status lightdm.service says:


Code:
root@rock64:~# systemctl status lightdm.service
● lightdm.service - Light Display Manager
  Loaded: loaded (/lib/systemd/system/lightdm.service; enabled; vendor preset: enabled)
  Active: failed (Result: exit-code) since Mon 2018-07-09 10:46:10 UTC; 1h 58min ago
    Docs: man:lightdm(1)
 Process: 662 ExecStart=/usr/sbin/lightdm (code=exited, status=1/FAILURE)
 Process: 657 ExecStartPre=/bin/sh -c [ "$(cat /etc/X11/default-display-manager 2>/dev/null)" = "/usr/sbin/lightdm" ] (code=exited, status=0/SUCCESS)
Main PID: 662 (code=exited, status=1/FAILURE)

Jul 09 10:46:10 rock64 systemd[1]: lightdm.service: Failed with result 'exit-code'.
Jul 09 10:46:10 rock64 systemd[1]: lightdm.service: Service hold-off time over, scheduling restart.
Jul 09 10:46:10 rock64 systemd[1]: Stopped Light Display Manager.
Jul 09 10:46:10 rock64 systemd[1]: lightdm.service: Start request repeated too quickly.
Jul 09 10:46:10 rock64 systemd[1]: Failed to start Light Display Manager.
Jul 09 10:46:10 rock64 systemd[1]: lightdm.service: Unit entered failed state.
Jul 09 10:46:10 rock64 systemd[1]: lightdm.service: Failed with result 'exit-code'.
root@rock64:~#

The manual startx bringt:


Code:
root@rock64:~# startx


X.Org X Server 1.19.2
Release Date: 2017-03-02
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.9.0-4-arm64 aarch64 Debian
Current Operating System: Linux rock64 4.4.126-rockchip-ayufan-239 #1 SMP Sun May 27 18:38:24 UTC 2018 aarch64
Kernel command line: rw root=LABEL=linux-root rootwait rootfstype=ext4 panic=10 init=/sbin/init coherent_pool=1M ethaddr=16:fc:cc:d2:25:67 eth1addr=16:fc:cc:d2:25:87 serial=aa8010ecb10fe21 cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1
Build Date: 16 October 2017  08:11:43AM
xorg-server 2:1.19.2-1+deb9u2 (https://www.debian.org/support)
Current version of pixman: 0.34.0
       Before reporting problems, check http://wiki.x.org
       to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
       (++) from command line, (!!) notice, (II) informational,
       (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Mon Jul  9 12:45:33 2018
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(EE) armsoc: module ABI major version (20) doesn't match the server's version (23)
(EE)
Fatal server error:
(EE) no screens found(EE)
(EE)
Please consult the The X.Org Foundation support
        at http://wiki.x.org
for help.
(EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
(EE)
(EE) Server terminated with error (1). Closing log file.

Okay, the ABI version doesn't match, no problem:

Code:
root@rock64:~# startx -- -ignoreABI


X.Org X Server 1.19.2
Release Date: 2017-03-02
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.9.0-4-arm64 aarch64 Debian
Current Operating System: Linux rock64 4.4.126-rockchip-ayufan-239 #1 SMP Sun May 27 18:38:24 UTC 2018 aarch64
Kernel command line: rw root=LABEL=linux-root rootwait rootfstype=ext4 panic=10 init=/sbin/init coherent_pool=1M ethaddr=16:fc:cc:d2:25:67 eth1addr=16:fc:cc:d2:25:87 serial=aa8010ecb10fe21 cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1
Build Date: 16 October 2017  08:11:43AM
xorg-server 2:1.19.2-1+deb9u2 (https://www.debian.org/support)
Current version of pixman: 0.34.0
       Before reporting problems, check http://wiki.x.org
       to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
       (++) from command line, (!!) notice, (II) informational,
       (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Mon Jul  9 12:47:21 2018
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(WW) armsoc: module ABI major version (20) doesn't match the server's version (23)
(EE)
Fatal server error:
(EE) AddScreen/ScreenInit failed for gpu driver 0 -1
(EE)
(EE)
Please consult the The X.Org Foundation support
        at http://wiki.x.org
for help.
(EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
(EE)
(EE) Server terminated with error (1). Closing log file.

Okay, -ignoreABI is not enougth...

I've attached the log file from X.org.

Any ideas?



Attached Files
.log   Xorg.0.log (Size: 18.39 KB / Downloads: 454)

Sad Windows 10 iot ffu
Posted by: lawrencejd - 07-08-2018, 03:24 AM - Forum: Windows 10 IoT - Replies (1)

Can any one tell me how to deploy windows 10 iot to SD card coz i tried the 3 ways on my PC one of them Using IoTCoreImageHelper but still the software frozen and not responding Huh

What can i do??


  Mali OpenGL ES 2.0 SDK
Posted by: ab1jx - 07-07-2018, 10:04 PM - Forum: Linux on Rock64 - Replies (4)

Docs are linked from
https://developer.arm.com/products/graph...li-450-gpu
see DUI0607C_mali_opengl_es_20_sdk_for_linux_on_arm_ug.pdf

This is a weird URL but it was hard to find:
http://openlinux.amlogic.com:8000/downlo...x86.tar.gz  I think arm/mali pulled it

I managed to get all the examples to build on a Raspberry Pi, but it doesn't have a Mali so they don't run.  There's one called frame_buffer_object that's a spinning cube and on each of its faces is another spinning cube, supposedly anyway.

If you've got all the prerequisites installed, unpack the tar.gz.  In the directory that creates make a build_arm directory and cd into it.
do:
export TOOLCHAIN_ROOT=/usr/bin/
then
cmake -G "Unix Makefiles" -DTARGET=arm ..

If it builds OK look in the samples directory that gets created.  There are samples of OpenGL ES 2.0, 3.0, 3.2.


  Docker Mssql
Posted by: Riverman - 07-07-2018, 08:49 PM - Forum: Linux on Rock64 - Replies (5)

Anybody have any luck installing mssql Docker image. 

I can pull the image ok and create the container but the container does not display port 1433 used in the installation command.

I'm using ubuntu 16.04.04 and Docker 18.03.1-ce


  [split] Node-RED
Posted by: neeeds - 07-07-2018, 07:58 PM - Forum: Pine A64 Projects, Ideas and Tutorials - No Replies

Hi, does it have gpio support ? 
thank you.


  Sound
Posted by: teddyj - 07-07-2018, 02:16 PM - Forum: Getting Started - Replies (4)

I have two 2G boards. I am having issues with sound... they both used to play sound, however not any more. I have reflashed OS multiple times and nothing. Any advice?

Thank you
Ted


  ayufan's bionic minimal boots only the first time
Posted by: fczuardi - 07-07-2018, 01:44 PM - Forum: Linux on RockPro64 - Replies (6)

I got my rockpro64 and I am trying to get it running, I have created a sd card with the image bionic-minimal-rockpro64-0.7.3-1040-arm64.img.xz

The first boot works seamlessly, the white LED is on, hdmi tv is detected and login with rock64/rock64 takes me to the shell...

But if I turn the computer off and on again, nothing happens anymore: no LED, no signal on hdmi...

Any ideas on how to get more information or what might be happening?


  Content Control
Posted by: teddyj - 07-07-2018, 01:22 PM - Forum: Getting Started - Replies (1)

Team, 

Trying to load apps on the google play store and keep getting a warning for "Error: Your Content Filtering Level does not allow you to purchase this item." .... The app I am attempting to DL, Amazon Video. Running > Android 6.0 (HDMI Video Output) [20170112 v2.0.1]. I have relaxed all User Controls in settings, and no change to the "Error". 

Little help on how to remove this control. Thank you,
Ted


  wiki Android TV 7.1 file error
Posted by: ycllwl - 07-07-2018, 09:32 AM - Forum: Android on Rock64 - Replies (3)

wiki Android TV 7.1 file error

http://wiki.pine64.org/index.php/ROCK64_...oid_TV_7.x

MD5 equally
After the installation,display ubuntu 16.04  Huh Huh Huh 

Waste time

Please correct it
Thank you



Attached Files Thumbnail(s)
   

  RFE for next ROCK64
Posted by: mcerveny - 07-06-2018, 04:19 PM - Forum: General Discussion on ROCK64 - Replies (4)

Hello.

I have some enhancement suggestion for next update of ROCK64:

  1. connector for RTC battery for RK805
  2. connector for RESET and POWERON
    - needed for external control (power on by event)
  3. connector for true PoE/PoE+/4PPoE (802.3af/802.3at/802.3bt with mode a,b,a+b over 1gbit) with 1GBit connector+magnetics for example "EDAC A70-112-331N126" or "LINK-PP LPJG0926HENL" (must be carefully routed with operating up to 600mA@57V and with PoE isolation requirements)
  4. connector between barrel power connector and board power (both pins, with installed jumpers from factory) that can be used for:
    - internal (in case) DC/DC converter (also isolated variant) from higher voltage (12V)
    - combined DC from embedded UPS battery with cooperation with external DC
    - combined DC from PoE DC/DC with cooperation with external DC (also possibility to supply any DC to external component back over DC connector (available power +-10W reserved for ROCK64 from 12.95W(PoE)/25.50W(PoE+)/51W(4PPoE) (for external powered usb hub, speakers, small lcd panel, camera, positioning motors, ...)))
  5. power distribution over mounting holes connected to barrel power connector selectable with pinheaders/jumpers (probably with additional internal DC/DC converter from previous point to compensate voltage drop for massive stacking) - see Paralella
  6. connector (with installed jumper from factory) to unselect internal SPI (SPI_CSN0_M2) (but with possibility to boot from external SPI flash directly from embedded ROM over PI-2 connector)
  7. larger internal SPI to accommodate boot+stripped_down_kernel+ramdisk miniroot with something like NOOBS (New Out Of the Box Software) distribution download from internet and etcher flash to local SDCARD/eMMC
  8. maybe connector with PMEB+VCC33_LAN+GND (or embed this to board - 1xLDO + 3xdiode? (untested)) from RTL8211F to implement Wake-on-LAN (WoL) with external logic but VCC33_LAN must be reworked to supply RTL8211F chip externally too. Example scenario (untested):
    1) new attach of PoE (ethernet connector) or external DC must start rk3328+rk805 to setup/config RTL82211F for WoL (actual behavior due to C736)
    2) PoE or external DC still available (eg. VCC_SYS==5V) but rk3328+rk805 is down (eg. no BUCK4 VCC_IO->VCC33_LAN) and VCC33_LAN externally over pin or with own LDO from VCC_SYS (combined power with diodes?)
    3) PMEB should signal WoL to pin or to POWERON (over diode or transistor)
  9. Colored connector like TinkerBoard or adafruit
  10. USB and power test pads from bottom to stack USB peripherals like RPI ZERO USB hub
  11. Add some programmable peripheral co-processor like 8-bit (AVR) or 32-bit (ARM M0+) or other hw peripheral rich chip (connected with i2c+interrupt to RK3328, connected to RESET/POWERON to RK805, serial firmware programming with external connection, maybe "alway-on" (not RK805) powered also on vBAT...) for programmable hw tasks like true PWM (motor or fan speed control), A/D (also for independent voltage/current board monitor), programmable sw logic, WoL monitor, external watchdog, oneWire bridge, IR transmitter ... with connection on PI2 unusable pins (11,12,13,24(SPI CSN0),29,31 and maybe 32-40)
  12. Add some simple undervoltage detector (op-amp comparator) to driver green led (LED705) (bicolor led (green/red) may be better)

I estimate material expenses about $1 (~14 pinheaders, ~3 diodes, ~1 LDO and replace "HANRUN HR911130A" to "LINK-PP LPJG0926HENL") + $0.5-$2 for coprocessor.

Something like this:
[Image: rock64_board_rfe.jpg]