You are not logged in.
Pages: 1
I had a second computer waiting to be formatted, I use Artix, Mx, and Slitaz in my 3 systems..
On the Slitaz system, as about start of May, about May 6th, which version exactly can't say, I upgraded my Slitaz system through iso, and no boot, I had other computer to fuck around so I left the Slitaz rig waiting for next version..
On 17th May, when new version uploaded to server, I immediately burnt a usb bootable and formatted again (ext2-3-4 btrfs tried all) and it didn't boot.
error:
$ can't find vesamenu.c32 $
# this problem keeps repeating itself in boot mode and fills the screen eventually.
I folded my sleeves to look for a solution: Turns out, it fails to create a feasible boot folder.
When I did a quick inspection, I found out syslinux folder was half-empty.
Solution I had:
1-After fresh install, run livesession (tux)
2-Using terminal super user, change 'chmod 777' (permission) of /boot folder, replace boot files from the original iso to the /boot and turn chmod 755 (read-only).
After this it boots.
Funny why it started happening in the few months, I wonder why. Writing this for coder/compiler's notice and for help if anyone got the same blues.
Offline
Sorry I'm really bad at non-editing style messagings,
*forgot to mention:
Slitaz64-5.0 is current version I'm using. Thanks to @Shann's link "https://people.slitaz.org/~shann/slitaz-current64-stuff/isos/slitaz-6.0-core64-grub2.iso", I'll try version 6.0 as soon as I can.
Offline
UPDATE
This problem doesn't exist on Slitaz6.0-64, I'm marking as resolved.
Package basket is a bit empty on new repositories however, it will soon have more packages uploaded.
Offline
Pages: 1
[ Generated in 0.023 seconds, 7 queries executed - Memory usage: 1.54 MiB (Peak: 1.77 MiB) ]