You are not logged in.
There is option in boot menu
to boot directly to X or GTK2.
Also "Slitaz Live" does not boot.
But Slitaz core and another text based option does boot normnally.
System doestotal freeze in init sequence, when it is loading us keyboard,
CRTL-ALT-DEL nor power switch does not affect.
My computer is anno 2010 model HP desktop that has
USB keyboeard and nouveau graphics card.
Dpo I need some option to load USB keyboard driver?
BTW: Slitaz seems very interesting distro, because it is so lightweight.
Offline
Hum I'm new too to Slitaz but I can say my USB keyboard load fine without any special drivers.
To have an hint about why it is stuck when booting look for the file "boot.log" in the \var\log\boot.log
It should show you what happen in the boot sequence.
N.B.: It will work only if it is a "fixed" installation of Slitaz since in a live version you will not be able to access the "boot.log" file.
Maybe somebody more experienced will be able to help you more. 
Regards.
Offline
I cannot and I have not reason to install Slitaz to my computer,
because it does not boot
installer in X windows mode.
I tested Slitaz Live with my old laptop. It seems OK.
Slitaz boots then to live mode, and I get Midori and other cool stuff.
But again with desktop computer HP p6769Sc slitaz boots only to "base" and "core"
command line only.
There is Finnish PC105 USB keyboard connected to computer.
Boot stucks to text "Loading console keymap: us"
Then goes total freeze: must take power wire off to restart
computer again. Computer does not react even power switch.
I think again, tthis problem has something to do with USB
keyboard.
X windows boot sequence must be differennt than text mode boot!
Offline
Slitaz boots normally to graphical interfece, when I install it directly to hard disk, copy all files.
But it does not start to X, when i boot it from stick.
Offline
But it does not start to X, when i boot it from stick.
Try adding [c]rootdelay=10[/c] at the end of the kernel line in the menu.
USB1 ?
Offline
I tested with X only option from booting command line this "rootdelay=10" once.
It wasn't help me. It does same thing yet again. When system.sh is loading "us" keyboard, computer stucks.
There are so many USB ports in my computer, that i cant tell which hardware usb port # it is where my slitaz stick is.
I do my slitaz stick directly with DD.
Linux installs quite randomly all USB devices to sdc, sdf, shg, sdh etc.
Offline
Now boot problem is in hard disk, too.
I use now slitaz from hard disk, with lzma/cpio extarted file system.
When I boot first time slitaz from hard disk, all goes OK.
I install some programs.
But at second time hard disk boot stucks again loading kayboard us in system.sh
I boot with grub2, that installs ok to slitaz HDD
set menu_color_normal=white/blue
set menu_color_highlight=light-blue/white
# Set menu display time
set timeout=5
# Set the default boot entry (first is 0)
set default=0
menuentry "Login Prompt" {
#root (hd0,0)
linux /boot/bzImage root=/dev/sda1 rw vga=normal
}
Problem row in system.sh is
this line
/sbin/tazkeymap $kmap >/dev/null
when computer stucks
but i cannot fix it.
Offline
I found the solution to my problem 
I traced the linux/slitaz startup-sequence to understand how it work sine I'm new to linux.
The problem is that certain Slitaz ISO files for a strange reason don't create some important folders when you try to install slitaz with the TazPanel.
So when you try to boot the system Slitaz try to find configuration files and those files are not created... in fact whole folders are missing that's why it default to terminal instead of graphical interface.
Here's the folders/files that are not created: /root/.config/slitaz/applications.conf
what could be done would be to create them manually but for me it was to much time consuming since I'm new to linux.
What I've done is to use another ISO image.
"GOOD" image/ISO = slitaz-4.0-loram-cdrom.iso
"BAD" image/ISO = slitaz-4.0-loram.iso
IMO I think the defective image/ISO have not been tested for "Installation" only tested to see if it's boot from USB/CD and it boot fine but don't install fine, so when you are a newbie like me it's confusing. ;-)
Hoping it will help you to have it run on your computer.
Thanks to everybody for the help ! 
Offline
Maybe my computer is too new and fast for slitaz.
There are some four (4) processor and computer is too
fast for boot.
Maybe in boot sequence initializing files system start, and
running init forks to xext stage.
When init system gets line
/sbin/tazkeymap $kmap >/dev/null
there is not year adequate file system.
It is way to slow down and wait file system
creation, or secure boot file system creation in
faster machines.
Offline
[ Generated in 0.020 seconds, 7 queries executed - Memory usage: 1.55 MiB (Peak: 1.77 MiB) ]