You are not logged in.
Hi,
The last Rolling core64 ISO (20200329) return the error message
[c]
error: read out of range
press any key to continue
[/c]
when trying to boot from the .iso file.
I can't say if the problem existed with the previous ISOs; I didn't boot in this way since september.
I reloaded the ISO but the problem remains.
My entry in grub.cfg:
[c]
menuentry "SliTaz Rolling core64 - LiveISO (kernel 3.16.55)" {
loopback taziso (hd0,4)/slitaz/64bit/slitaz-rolling-core64.iso
linux (taziso)/boot/bzImage64 rw root=/dev/null video=-32 kmap=fr-latin1
initrd (taziso)/boot/rootfs.gz
}
[/c]
No problem when booting in frugal mode with the rootfs.gz and bzImage64 extracted from the ISO.
Offline
Booting from slitaz-rolling-core64.iso with grub2 works on my biostar A780L3G
tux@slitaz:/media/crux/boot/iso$ md5sum -c slitaz-rolling-core64.md5
slitaz-rolling-core64.iso: OK
tux@slitaz:/media/crux/boot/iso$ cat slitaz-rolling-core64.md5
7f98bb7c122d92aa65ee4a9f26de61c6 slitaz-rolling-core64.iso
[c]menuentry "SliTaz Rolling Core64" {[/c]
[c]loopback loop /boot/iso/slitaz-rolling-core64.iso[/c]
[c]linux (loop)/boot/bzImage64 root=/dev/null autologin[/c]
[c]initrd (loop)/boot/rootfs.gz[/c]
[c]}[/c]
Offline
Hello mojo,
Thanks for testing.
Weird... I tried rolling and rolling-core ISO from 20200329; both work.
I tried too rolling-core64 from 20200322; works too.
It's not really a problem as it works in frugal. I'll test the next build.
Note the error message appears just after I hit the F10 key (boot after editing an entry); it seems in my case the problem is with the kernel.
Offline
Note the error message appears just after I hit the F10 key (boot after editing an entry); it seems in my case the problem is with the kernel.
Forget it.
I just changed my linux line as this:
[c]linux (taziso)/boot/vmlinuz-3.16.55-slitaz64 rw root=/dev/null video=-32 kmap=fr-latin1[/c]
and the problem is exactly the same. And if Ihit a key or let the system to continue, it starts to boot and ends in a kernel panic.
No matter, I'll see next week.
Offline
ISO 200405 solved the problem
EDIT: Well, in fact this is a randomly problem when ISOs are stored on a NTFS partition; copying them in an other directory can solve the issue for some but create it for others... Downloading ISOs on an ext2/3/4 partition never fails 
Offline
[ Generated in 0.015 seconds, 7 queries executed - Memory usage: 1.54 MiB (Peak: 1.77 MiB) ]