Do you have a command-line login or graphical (colorful) login?

Try tux and no password.

I would try a different flavor's file system.

One way is to install a micro linux to a small partition, boot it, and use it to copy system files from a regular or core cd to the hd.

It would be good if the loram iso were checked or updated.

Thanks for the suggestion.

Command line.

Tried tux and no password. No joy.

Interesting suggestion on using a micro linux to install from core.

There are smaller micros but slitaz has its own micro on 5 floppies (is that 2 floppies for v1.0?)-

http://mirror.slitaz.org/floppies/

Slitaz could promote that flavor in the micro categories on the internet.

Why is it, incidentally, that loram can't install core?

Loram is a live-cd booting method that can apply to any flavor and I think the website has instructions on how to make a loram (probably not for beginners, not sure if you are).

At least one of the v3.0 loram iso might have a bug (not sure if the other is ok).

Sliaz v2.0 loram might work.

Your suggestion that a full flavor should be able to install only the core is a good one.

http://doc.slitaz.org/en:guides:xorg-xvesa

I think making a loram is beyond me (for now).

Where can I get v2.0?

I've tried using the floppy boot disk to boot from the loram live-cd installed on a pen drive (via universal usb installer) (the bios will not support booting from usb), with the intention of manually installing to the hd from the core cd. But in the plop boot manager I get "boot error no boot device found, please retry it.

I've now tried slitaz-3.0-xvesa, but I get the same problem after doing a hd install as http://forum.slitaz.org/index.php/discussion/1026/hd-install-init:-can-t-log-tp-dev-tty5, ie

init: can't log to /dev/tty5
process '-bin/sh' (pid X) exited. Scheduling for restart
init: can't log to /dev/tty5
process '-bin/sh' (pid X) exited. Scheduling for restart
init: can't log to /dev/tty5
process '-bin/sh' (pid X) exited. Scheduling for restart
init: can't log to /dev/tty5
can't open /dev/tty2: No such file or directory
init: can't log to /dev/tty5
can't open /dev/tty3: No such file or directory
init: can't log to /dev/tty5
can't open /dev/tty4: No such file or directory

Looping to infinity, where X is incrementally +1 each time.

I've now copied /etc, /dev and /sbin to /media/disk from the slitaz-3.0-xvesa liveCD. When I boot from the hd I get the login/password issues as described before.

Is install to hd broken on both the loram and xvesa flavours? Is the computer just too poor? Or am I doing something wrong?

http://mirror.slitaz.org/iso/2.0/flavors/

There is v2. I used the sqfs iso for loram.

I use slitaz 3 xvesa without your boot problems but that is with plenty of ram.

If the slitaz 3 loram booted in live cd mode, use the live cd to copy from usb to hd.

I do not see the tty boot bug on my xvesa so I cannot explain the difference with yours (hardware difference?) but other users reported the tty bug and it could be something with busybox or inittab.

http://lists.busybox.net/pipermail/busybox/2008-May/065574.html

I wonder what would happen if someone with the tty5 loop commented out the tty5 line in /etc/inittab.

# /sbin/getty respawn shell invocations for selected ttys.
tty1::respawn:/sbin/getty 38400 tty1
tty2::respawn:/sbin/getty 38400 tty2
tty3::respawn:/sbin/getty 38400 tty3
tty4::respawn:/sbin/getty 38400 tty4
#tty5::respawn:/sbin/getty 38400 tty5
tty6::respawn:/sbin/getty 38400 tty6

I've tried a manual install from the slitaz-3.0-loram-cdrom, but the http://forum.slitaz.org/index.php/discussion/1026/hd-install-init:-can-t-log-tp-dev-tty5 issue is still present.

Is it a possibility that the lack of RAM in my system prevents the installation from working correctly?

There are supposed to be lorams that work with less than 24mb ram. You could run a memtest utility to see if your ram is working but other people reported the tty error too.

I noticed something strange-

slitaz-3.0-loram-cdrom.iso  [131.0M] - Loram flavor that can boot with only 16 MB and a little swap memory, but is unable to release the cdrom

http://www.slitaz.org/en/get/flavors.html

What happens if there is no swap partition?

You can try this v2 loram that worked for me before creating any swap-

http://mirror.slitaz.org/iso/2.0/flavors/slitaz-loram-cdrom-sqfs.iso

md5 8af12c207febc5b61527bc98aa1ebc75 slitaz-loram-cdrom-sqfs.iso

I've tried v2 slitaz-loram-cdrom and I can install the hard disk without problem (yet!).

Do you mean that, after installing a full hd installation and trying to boot the new hd os, v2 boots properly and completely but v3 does not?

Thank you.

Slicel,

Yes, that is the case. As far as I can tell I have had complete success at using v2 slitaz-loram-cdrom to install SliTaz to the HD, from where is boots properly and completely. I have not had the same success with v3 either with slitaz-loram-cdrom or slitaz-xvesa.

Is there some place that I can report these problems with v3 as a bug or something? Would this be a helpful thing to do?

Reporting the problem here helps, thank you.

I do not know how labs works-

http://labs.slitaz.org/issues

can you give more detail on your computer - which cpu ram etc...?

Toshiba Satellite 2140CDS
Processor: AMD K6-2 450 MHz
RAM: 32 MB SDRAM