If antiX-15-V_386-full.iso runs under QEMU,"Failsafe Boot" works until

[ ok ] Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon.
[....] Starting uuid generator: uuidd

There the screen turns black and no further progress is evident.
A photo of the display is at
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://easthope.ca/antiXuuidd.jpg"
linktext was:"http://easthope.ca/antiXuuidd.jpg"
====================================
.

Is uuidd problematic? Other ideas?

Thanks, ... Peter E.

Not sure if it is Qemu related. I run 32 bit AntiX 15 on different hardware with no bootup problems.
I read your
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"antix.freeforu ms.org/viewtopic.php?f=53&t=6110"
linktext was:"boot from iso thread"
====================================
and it seems you get almost the same behavior.

Make me just wonder if a md5sum of the iso was done before attempting any of the the 2 threads.
Sorry. I am not much help on this. I usually don't answer when I do not have the answer in my head or a idea
on where to look.

Anti is the boot from iso expert as well as a couple of other members here. But you caught us during a building new releases phase so the dust is still waiting to settle after all the testing and setting up the new tutorials and other stuff required when things like this are done.

Just be patient.

It works ok on my set up, no problems booting failsafe option.
My host is antiX sid.

Mon Dec 28, 2015 12:26 pm
> Make me just wonder if a md5sum of the iso was done before attempting
> any of the the 2 threads.

Oops! You are correct. The checksum on the iso failed. I should have checked before using the file.

Will try the QEMU and fromiso methods again and should be able to report about one week hence.

Thanks and apologies for the goose chase, ... Peter E.

With a fresh copy of the ...iso and this stanza in / etc/grub.d/40_custom installation was completed.

menuentry"(hd0,msdos1) antiX" {
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
echo 'Loading antiX-15-V_386-full.iso ...'
linux /boot/vmlinuz root=UUID=ae5f8bf4-b2a2-4b10-8da2-922d9f4e6e91 from=hd fromiso=/boot/antiX-15-V_386-full.iso load=all reboot=bios ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.gz
}

Booted to a console; cli-installer was used.

Booting the fresh installation and attempting login as the user gave the screen here.

========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://easthope.ca/antiXloginFailure.jpg"
linktext was:"http://easthope.ca/antiXloginFailure.jpg"
====================================


Login in as root, password=root, gave this screen and nothing further.

========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://easthope.ca/antiXrootLogin.jpg"
linktext was:"http://easthope.ca/antiXrootLogin.jpg"
====================================


Any ideas about login?

Thanks, ... Peter E.

user=demo

password=demo

> user=demo
> password=demo

The user created in the installation process is in / etc/passwd with directory
/home/user. Nevertheless, /home doesn't exist. Therefore /home/user
doesn't exist. Therefore login by user fails.

The part for home, created with gparted before antiX installation, is available;
but there is no entry for it in / etc/fstab. Probably I made a bad choice in the
installation. Adding an entry to / etc/fstab is easy enough. If it remains after
reboot, user login is likely to work.

Thanks for the help, ... Peter E.