Reply
Thread Tools
Alecsandru's Avatar
Posts: 439 | Thanked: 282 times | Joined on Oct 2012
#531
startx
exec enlightenment_start

if i remember correctly
__________________
N900 Beast featuring :
8GB OPTFS@ext4(*performance mount options)
overclock: cpu[125 - 1,150(*VDD1)+Dsp overclock
CSSU-T latest version
 
Posts: 153 | Thanked: 81 times | Joined on Dec 2011 @ P town
#532
I think the problem isn't e17, but more in X.
Because one of the error message when I run "exec /usr/bin/enlightenment_start" is:
Enlightenment cannot initialize Ecore_X!
 
Alecsandru's Avatar
Posts: 439 | Thanked: 282 times | Joined on Oct 2012
#533
did you start powervr first?
startx gives-you any errors?
__________________
N900 Beast featuring :
8GB OPTFS@ext4(*performance mount options)
overclock: cpu[125 - 1,150(*VDD1)+Dsp overclock
CSSU-T latest version
 
Posts: 153 | Thanked: 81 times | Joined on Dec 2011 @ P town
#534
Originally Posted by Alecsandru View Post
did you start powervr first?
startx gives-you any errors?
I don't have powervr on my Alarm. What package is this?

IIRC, startx is only a script to execute the DM. I don't have startx script, instead I create /usr/bin/starte17, which contain this line:
Code:
exec /usr/bin/enlightenment_start
And when I run starte17, it gives me this error:
Code:
E - PID=8448, valgrind=0
ESTART: 0.00000 [0.00000] - Begin Startup
ESTART: 0.00354 [0.00354] - Signal Trap
ESTART: 0.00412 [0.00058] - Signal Trap Done
ESTART: 0.01071 [0.00659] - Eina Init
ESTART: 0.07205 [0.06134] - Eina Init Done
ESTART: 0.07288 [0.00082] - Determine Prefix
INF<e>e_prefix.c:25 =================================
INF<e>e_prefix.c:26 Enlightenment relocation handling
INF<e>e_prefix.c:27 =================================
INF<e>e_prefix.c:28 PREFIX:  /usr
INF<e>e_prefix.c:29 BINDIR:  /usr/bin
INF<e>e_prefix.c:30 LIBDIR:  /usr/lib
INF<e>e_prefix.c:31 DATADIR: /usr/share/enlightenment
INF<e>e_prefix.c:32 LOCALE:  /usr/share/locale
INF<e>e_prefix.c:33 =================================
ESTART: 0.14020 [0.06732] - Determine Prefix Done
ESTART: 0.14087 [0.00067] - Environment Variables
ESTART: 0.14154 [0.00067] - Environment Variables Done
ESTART: 0.14203 [0.00049] - Parse Arguments
ESTART: 0.14255 [0.00052] - Parse Arguments Done
ESTART: 0.14301 [0.00046] - Eet Init
ESTART: 0.24542 [0.10242] - Eet Init Done
ESTART: 0.25989 [0.01447] - Ecore Init
ESTART: 0.26233 [0.00244] - Ecore Init Done
ESTART: 0.26300 [0.00067] - EIO Init
ESTART: 0.28461 [0.02161] - EIO Init Done
ESTART: 0.31189 [0.02728] - Ecore Event Handlers
ESTART: 0.31247 [0.00058] - Ecore Event Handlers Done
ESTART: 0.31290 [0.00043] - Ecore_File Init
ESTART: 0.38342 [0.07053] - Ecore_File Init Done
ESTART: 0.38406 [0.00064] - Ecore_Con Init
ESTART: 0.38440 [0.00033] - Ecore_Con Init Done
ESTART: 0.38477 [0.00037] - Ecore_Ipc Init
ESTART: 0.38513 [0.00037] - Ecore_Ipc Init Done
ESTART: 0.38550 [0.00037] - Ecore_X Init
<<<< Enlightenment Error >>>>
Enlightenment cannot initialize Ecore_X!

E17: Begin Shutdown Procedure!
 
Posts: 204 | Thanked: 754 times | Joined on Jan 2012 @ Finland
#535
@sLumPia

fbdev-driver you have is not compiled for Xorg 1.14, try pacman -Syu and if there is no updated version, you need to pass -ignoreABI to Xorg, chances are it may even work.

For the SGX variant, you need to start/enable powervr service first, there are modules and firmware to be loaded. Cant remember if I compiled it for 1.14 or not.
 

The Following 2 Users Say Thank You to Skry For This Useful Post:
Posts: 153 | Thanked: 81 times | Joined on Dec 2011 @ P town
#536
Originally Posted by Skry View Post
@sLumPia
fbdev-driver you have is not compiled for Xorg 1.14, try pacman -Syu and if there is no updated version, you need to pass -ignoreABI to Xorg, chances are it may even work.
I have try run X -configure -ignoreABI, but still failed

When I run pacman -Syu, I got this error message:
Code:
error: failed to commit transaction (conflicting files)
filesystem: /bin exist in filesystem
filesystem: /sbin exist in filesystem
filesystem: /usr/sbin exist in filesystem
Errors occured, no packages were upgraded.
 
Posts: 204 | Thanked: 754 times | Joined on Jan 2012 @ Finland
#537
Don't run it with -configure, it'll probably just mess things up.

Now, the filesystem errors, do you have the right mirror for my repository? I could swear I upgraded my packages for the new filesystem package, not sure though. This could also be caused by not doing the filesystem package update right, or at all. Instructions are at Arch Linux news, if you have not done this and have not installed from the latest rootfs.
 

The Following User Says Thank You to Skry For This Useful Post:
Posts: 153 | Thanked: 81 times | Joined on Dec 2011 @ P town
#538
Skry, yes I'm still using the old rootfs. I managed to update the system after following the instruction in here.

But I still can't start e17/X.
I'm using the SGX variant and as you said for SGX variant powervr is needed.
I got this error when I start powervr service:
Code:
# systemctl start powervr
Job for powervr.service failed. See 'systemctl status powervr.service' and 'journalctl -xn' for details.
And this is the output of systemctl status and journalctl:
Code:
# systemctl status powervr
powervr.service - PowerVR SGX
Loaded: loaded (/usr/lib/systemd/system/powervr.service; enabled)
Active: failed (Result: timeout) since Sun 2013-08-18 07:50:24 CDT; 3s ago
Process: 153 ExecStartPre=/sbin/modprobe omaplfb (code=killed, signal=TERM)

Aug 18 07:50:24 alarm systemd[1]: powervr.service operation timed out. Terminating.
Aug 18 07:50:24 alarm systemd[1]: Failed to start PowerVR SGX.
Aug 18 07:50:24 alarm systemd[1]: Unit powervr.service entered failed state.
Code:
# journalctl -xn
-- Logs begin at Sun 2013-05-05 12:11:01 CDT, end at Sun 2013-08-18 07:49:34 CDT. --
Aug 18 07:49:19 alarm systemd-udevd[58]: worker [68] /devices/platform/smc91x timeout; kill it
Aug 18 07:49:19 alarm systemd-udevd[58]: seq 696 '/devices/platform/smc91x' killed
Aug 18 07:49:19 alarm systemd-udevd[58]: worker [73] /devices/platform/pvrsrvkm timeout; kill it
Aug 18 07:49:19 alarm systemd-udevd[58]: seq 688 '/devices/platform/pvrsrvkm' killed
Aug 18 07:49:19 alarm systemd-udevd[58]: worker [130] /devices/platform/rx51-audio timeout; kill it
Aug 18 07:49:19 alarm systemd-udevd[58]: seq 693 '/devices/platform/rx51-audio' killed
Aug 18 07:49:20 alarm systemd-udevd[58]: worker [130] terminated by signal 9 (Killed)
Aug 18 07:49:21 alarm kernel: bq27x00-battery 2-0055: battery is not calibrated! ignoring capacity values
Aug 18 07:49:24 alarm systemd-udevd[58]: worker [69] /devices/platform/twl4030_madc_hwmon timeout; kill it
Aug 18 07:49:24 alarm systemd-udevd[58]: seq 697 '/devices/platform/twl4030_madc_hwmon' killed
 
Posts: 204 | Thanked: 754 times | Joined on Jan 2012 @ Finland
#539
Do a systemctl poweroff from Arch try to boot again, should work. That is the reboot problem mentioned in the first post.

BTW I'll be returning to this project when Jolla starts shipping. There is some interesting progress happening with the upstream kernel.
 

The Following 5 Users Say Thank You to Skry For This Useful Post:
Posts: 1,141 | Thanked: 781 times | Joined on Dec 2009 @ Magical Unicorn Land
#540
Thanks Skry & all other contributers, I'm now running Arch on my second N900 with LXDE. It's great to have a modern kernel & distro running on it!

I used the prebuilt n900 rootfs image. Long time Linux user but I've never used Arch before, so I had some interesting times dealing with the move of everything to /usr/bin but it was nothing Google couldn't help with.
 
Reply


 
Forum Jump


All times are GMT. The time now is 01:13.