Are you sure you have made a complete update and everything is current? (pacman -Suy)
We are starting from scratch again, I can't assume what the current status is and how it relates to output from 04-05/1
|-(0,Enabled,classic) tty@ -tty1
You have a tty@ -tty1 enabled in root? # 66-disable -t root -S tty@ -tty1
Edit /etc/66/init.conf and change verbosity=4 reboot and /run/66/log/current should be a detailed log of anything that happens during boot. What happens with the next enabled tree will not show, but if everything is good with boot then you can log in and use 66-intree and 66-inservice to diagnose each tree and service analytically.
The log for X is at /var/log/Xorg.0.log
# cat /var/log/Xorg.0.log | grep "(EE)"
This will only show lines from the log that have errors, the first error is what is important
Now you have sddm enabled still, or not? If sddm was working you would see the console login screen temporarily and then sddm would kick in and take you to a graphic display to login. I was asking about updates because there was some brief time that sddm had a problem and that was fixed. So I am working on the assumption your system is current (upgraded).
If you have sddm disabled now, there are two things you need to have to startx or xinit. /etc/X11/Xwrapper.config with contents:
# /etc/X11/Xwrapper.config
needs_root_rights = yes
have a .xinitrc that ends with either command:
# exec ck-launch-session openbox-session
exec openbox-session
without consolekit running
exec ck-launch-session openbox-session
# exec openbox-session
with consolekit running (I simply leave the # comment in there so you can switch depending on what you need running or not - easier than typing a different command)
Make sure other commands are disabled. (lines that begin with exec or cmd)
Your openbox should start
You can also boot with an obarun live JWM image and from terminal mount the partition (I believe I see it is /dev/sda10 --> sudo mount /dev/sda10 /mnt --> sudo arch-chroot /mnt ) and make changes to your system, but since you get to console you should try and do the repairs from console.
If you run most console commands you can follow them with a >/tmp/log and it will send the output to a file named /tmp/log
If you want to append to that file you use >>
so as user:
% sudo 66-intree -g >/tmp/66tree
% 66-intree -g >>/tmp/66tree
Will write the output to /tmp/66tree
first for root then for user.