+- PINE64 (https://forum.pine64.org)
+-- Forum: ROCK64 (https://forum.pine64.org/forumdisplay.php?fid=85)
+--- Forum: Linux on Rock64 (https://forum.pine64.org/forumdisplay.php?fid=88)
+--- Thread: [solved] Unable to start X (/showthread.php?tid=6265)
[solved] Unable to start X - Osiander - 07-09-2018
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/stretch-mate-rock64-0.5.15-136-20171222-arm64.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?
RE: Unable to start X - zet_lab - 07-09-2018
0.5.15 is old version, use 0.6.44
RE: Unable to start X - t4_4t - 07-09-2018
Code:
Before upgrade:
ls -la /etc/X11/xorg.conf.d/
-rw-r--r-- 1 root root 177 Oct 12 2017 20-modesetting.conf
After upgrade:
ls -la /etc/X11/xorg.conf.d/
-rw-r--r-- 1 root root 564 May 28 03:33 20-armsoc.conf
-rw-r--r-- 1 root root 177 Oct 12 2017 20-modesetting.conf
-rw-r--r-- 1 root root 177 May 28 03:33 20-modesetting.conf.bak
----
Restart. after doing the following
# cd /etc/X11/xorg.conf.d/
# mv 20-armsoc.conf 20-armsoc.conf.bakThere is another way to build from source code.
However, there is no big advantage in doing it
ayufan-rock64/xf86-video-armsoc
https://github.com/ayufan-rock64/xf86-video-armsoc/archive/ayufan/rock64-ppa/1.9.3ayufan6.xenial4/xenial.tar.gz
RE: Unable to start X - pfeerick - 07-09-2018
This may apply if you're trying to upgrade.
Quote:X11 and older releases
When upgrading from older releases, some users have reported issues with X11 no longer starting. If you are upgrading an older (i.e. 0.5.x) release with a desktop environment, before rebooting the system it is advisable that you run the following command:
sudo apt-get install xserver-xorg-video-armsoc
You may also want to check the contents of the /etc/X11/xorg.conf.d/ directory, and if 20-modesetting.conf is present, move or rename it. i.e. sudo mv /etc/X11/xorg.conf.d/20-modesetting.conf /etc/X11/xorg.conf.d/20-modesetting.disabled
If you don't do this, there is a chance that X11 will crash on next boot, and you'll need to login to your system using a serial console or via SSH, and run the above commands. You should then be able to reboot your system and be greeted with a working X11 install again!
RE: Unable to start X - t4_4t - 07-09-2018
> sudo apt-get install xserver-xorg-video-armsoc
The result of doing it is as he indicated
(EE) armsoc: module ABI major version (20) does not match the server's version (23)
In short, at least as of today the files uploaded to the repository
"xserver-xorg-video-armsoc_1.9.3ayufan6.xenial4_arm64.deb"
there is a problem with this file itself.
To avoid it
· Use traditional modesetting_drv.so
· Receive source code and rebuild (in correct environment)
· Wait for the correct file to be uploaded
It becomes one of the above choices.
---
An example, result of rebuilding: (I do not expect performance this driver, but at least it works)
Code:
--- Xorg.0.log @ rebuilded armsoc_drv.so from source code ---
...
[ 1020.958] (II) LoadModule: "armsoc"
[ 1020.958] (II) Loading /usr/lib/xorg/modules/drivers/armsoc_drv.so
[ 1020.959] (II) Module armsoc: vendor="X.Org Foundation"
[ 1020.959] compiled for 1.19.2, module version = 1.4.1
[ 1020.959] Module class: X.Org Video Driver
[ 1020.959] ABI class: X.Org Video Driver, version 23.0
[ 1020.959] (II) ARMSOC: Driver for ARM Mali compatible chipsets
...RE: Unable to start X - Osiander - 07-10-2018
Hello guys,
after upgrade to 0.6.44-minimal and installation XFCE, X is starting properly.
Attached is the logfile.
RE: Unable to start X - Falkor - 07-11-2018
(07-10-2018, 04:09 AM)Osiander Wrote: Hello guys,
after upgrade to 0.6.44-minimal and installation XFCE, X is starting properly.
Attached is the logfile.
Hi,
Thank's for this thread, as I'm experiencing the same issue.
@Osiander : did you flashed a new image or is there a command for this upgrade ?
@t4_4t : what kind of delay can we expect for the correct file to be available ? (if its on his way…)
RE: [solved] Unable to start X - Osiander - 07-12-2018
First of all I've flashed the new image and after that "apt update" and install XFCE4 per tasksel.
RE: [solved] Unable to start X - jovval - 10-03-2018
(07-12-2018, 10:46 AM)Osiander Wrote: First of all I've flashed the new image and after that "apt update" and install XFCE4 per tasksel.
OK. I presume you did
tasksel
and selected XFCE4
So, here I am.
[ 44.071] (II) LoadModule: "armsoc"
[ 44.071] (WW) Warning, couldn't open module armsoc
[ 44.071] (II) UnloadModule: "armsoc"
[ 44.071] (II) Unloading armsoc
[ 44.071] (EE) Failed to load module "armsoc" (module does not exist, 0)
[ 44.071] (EE) No drivers available.
[ 44.071] (EE)
Fatal server error:
[ 44.072] (EE) no screens found(EE)
[ 44.072] (EE)
What did you do third to install the armsoc module shown in your log?
Clearly, you did not do this,
apt-get install xserver-xorg-video-armsoc
...
Get:1 http://ppa.launchpad.net/ayufan/rock64-ppa/ubuntu xenial/main arm64 xserver-xorg-video-armsoc arm64 1.9.3ayufan6.xenial4 [31.1 kB]
because then your Xorg's log would read as mine does.
[ 963.471] (II) LoadModule: "armsoc"
[ 963.471] (II) Loading /usr/lib/xorg/modules/drivers/armsoc_drv.so
[ 963.471] (II) Module armsoc: vendor="X.Org Foundation"
[ 963.471] compiled for 1.18.4, module version = 1.4.1
[ 963.471] Module class: X.Org Video Driver
[ 963.472] ABI class: X.Org Video Driver, version 20.0
[ 963.472] (EE) armsoc: module ABI major version (20) doesn't match the server's version (23)
[ 963.472] (II) UnloadModule: "armsoc"
[ 963.472] (II) Unloading armsoc
[ 963.472] (EE) Failed to load module "armsoc" (module requirement mismatch, 0)
[ 963.472] (EE) No drivers available.
And how did you force the system to select 23 and not 20 when you did that critical, missing third step?
Please, be kind enough to include these crucial details.
For now, I fail to see how this issue can possibly be "solved" until someone posts the full solution specifying how to install armsoc version 23. Nonetheless, I offer my attempt to explain how I executed a work-around stated by t4_4t above.
I have what appears to be a (partially?) functional X screen at boot by doing the following as root. (These are my full steps starting with a freshly flashed microSD. The first two steps are good practice, but are not necessary.)
apt update
apt-get upgrade
tasksel
I selected MATE; installation of 788 packages ensued.
cd /etc/X11/xorg.conf.d
mv 20-armsoc.conf 20-armsoc.conf-requires_version_23
mv 20-modesetting.conf.bak 20-modesetting.conf
Then, either of the following gives (a scarcely tested) X at hdmi's console:
startx
and/or
reboot
Unlike text console, the GUI returns to life at the hdmi upon input (from my mouse) and lets me see what I type.
So, ahm, how about version 23 of armsoc and ./install_desktop? How to make those work?