SliTaz Forum
You are not logged in.
Hello,
I created a rootfs.gz of my Next64 version but when I boot it in frugal I meet the following issue: after login (as well as tux than root) I get a black screen; Ctrl+Alt+BkSpace comes back to console mode.
From the console, startx launches X and all works fine.
No problem to log from a full installation with the same packages installed.
4 days that I'm stuck on this problem 
I never knew this in SliTaz 3 / 5 / rolling...
In slim.log
[c]slim: waiting for X server to begin accepting connections.
slim: open_session: Unable to open session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.[/c]
and in xauth.log
[c] (none) auth.err passwd: password for tux changed by root
Dec 2 hh:mn:ss (none) auth.notice su: + console root:tux
Dec 2 hh:mn:ss (none) auth.info login[2000]: root login on 'tty'
Dec 2 hh:mn:ss (none) auth.notice dbus-deamon[1819]: [system] Failed to activate service 'org.freedesktop.ConsoleKit': timed out (service_start_timeout= 25000 ms)[/c]
Does anyone have an idea about it?
Thanks in advance.
Offline
there was a similar problem with next lxqt
http://forum.slitaz.org/topic/slitaz-next-i-give-up/page/2
I dont think, its the same, but just to mention
can you post the Xorg.0.log
Offline
Hi kultex,
Xorg.0_(frugal1).log is Xorg.0.log (saved in Xorg.0.log.old) after I tryed to login with SLiM (waiting # 1 min before to Ctrl+Alt+BackSpace)
Xorg.0_(frugal2).log is Xorg.0.log after startx
Xorg.0_(full).log after login from full installation
Offline
what hardware - I guess its a atom laptop with some celeron CPU?
Offline
I guess, its some kind of race problem.
the Xorg.logs are identical - until line 378
line 379 you started to kill the xserver
I have the same problem, but with two different laptops, but the same hardware - always with modsetting driver - not with intel driver - but this was with antix, I will check, if it is the same with slitaz.
The Asus boots fine to X and the dell goes to black screen.
I tink, there is no cheatcode to wait some seconds until starting X. I am on the way without computer. I dont remember which script starts X - but maybe you can ad there sleep 5 before you create the rootfs.gz
Offline
I set sleep at 5 (and even 10) this week end in the line
[c](sleep 2; /etc/init.d/$LOGIN_MANAGER start >/dev/null) &[/c]
of /etc/init.d/rcS because I thougth the computer booted to fast too. I hope it is the good file.
But it had no other effect than to lengthen the time between the message "Welcome to your box" and the login screen
I forgot to say that the rootfs of alanyih's ISO boots like a charm on the same computer.
Computer (acer Aspire V3-111P): Atom, hmm maybe 
hardware is not my cup of tea but yes, the processor is a Celeron N2830 @ 2.16 GHz.
Offline
Mine is a Celeron N3050 - difference mainly: yours is Bay Trail (2013) and mine is Braswell (2015) - both Atom CPUs
I think, you should not loose to much time on this problem. It would be nice, to get also your iso, to see if the troubles are the same as with alanyih's ISO
Offline
@ kultex
I've posted a link to download my justX flavor ISO (X + tazpkg + pcmanfm + leafpad) in the Update kernel topic.
Offline
[ Generated in 0.015 seconds, 7 queries executed - Memory usage: 1.54 MiB (Peak: 1.77 MiB) ]