SliTaz Forum
You are not logged in.
Please tell me which image I need to download in order to add booting from a Grub2 ISO image?
I've been reading forums and trying different images for two days, and nothing works!
I only need the basic version without a desktop.
Offline
Found an answer to my question...
Here is a link http://mirror.slitaz.org/iso/4.0/flavors/ in which it is said that: The images *-isohybrid.iso will boot from a cdrom *and* USB.
Downloaded "slitaz-4.0-base-isohybrid.iso", flashed on the USB drive but, it does not run! What I do wrong?
Offline
PS - I'm trying to just load from the flash drive! And then in Grub2 ...
Offline
Hello,
I don't understand your configuration. SliTaz's ISOs don't come with GRUB2 but Syslinux.
How did you "flash" the ISO on your USB drive?
Do you want to boot from an ISO file with GRUB2 or make a LiveUSB?
Offline
I want to add in Grub2 new entry to load from ISO image "slitaz-4.0-base-isohybrid.iso". However, if Am I correct in understanding that the ISO image "slitaz-4.0-base-isohybrid.iso" does not work in UEFI? And I need to modify the image so that it can boot in UEFI.
Offline
Maybe you probably want to edit the "/etc/grub.d/40_custom" file to add a menuentry?
#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
menuentry "Alpine Linux alpine-standard-3.17.3-x86.iso" {
set isofile="/alpine-standard-3.17.3-x86.iso"
loopback loop (hd0,3)$isofile
linux (loop)/boot/vmlinuz-lts iso-scan/filename=$isofile modules=loop,squashfs,sd-mod,usb-storage,ext4 quiet splash
initrd (loop)/boot/initramfs-lts
}
menuentry "Linux lts" {
set root=(hd0,2)
linux /boot/vmlinuz-lts root=UUID=99f68d25-fc87-4ffe-899a-8dd8a63c697d modules=sd-mod,usb-storage,ext4
initrd /boot/initramfs-lts
}
Offline
Yes, you are correct. I want to add a new menuentry using the "/etc/grub.d/40_custom" file. But, I need only command line without the desktop environment. For this purpose, I think I need to select the "slitaz-4.0-base.iso" image. Did I choose the ISO image nemed "slitaz-4.0-base.iso" is correctly?
Will it boot in Grub with UEFI?
Offline
OK. No need the ISO is hybrid and UEFI is not a problem.
Something like that should work:
menuentry "SliTaz 4.0-base" {
set root=(hdX,Y) # (disk,partition) where the ISO is
loopback loop /path/to/slitaz-4.0-base-isohybrid.iso
linux (loop)/boot/vmlinuz-2.6.37-slitaz
initrd (loop)/boot/rootfs.gz
}
You could also boot a console from the Rolling ISO loading only [c]rootfs4.gz[/c]:
menuentry "SliTaz Rolling-base" {
set root=(hdX,Y) # (disk,partition) where the ISO is
loopback loop /path/to/slitaz-rolling.iso
linux (loop)/boot/vmlinuz-3.16.55-slitaz
initrd (loop)/boot/rootfs4.gz
}
Offline
The "SliTaz 4.0-base.iso" image is located on partition "nvme0n1p5" in the "iso" folder. I have adjusted my script accordingly to your message. However, I'm encountering the following error: "You need to load the kernel first."
What am I doing wrong?
[attachment=51694,3397]
Offline
Sorry, I forgot to show my script!
#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
menuentry "SliTaz 4.0-base" {
set root=(hd0,gpt5) # (disk,partition) where the ISO is
loopback loop (root)/iso/slitaz-4.0-base.iso
linux (loop)/boot/vmlinuz-2.6.37-slitaz
initrd (loop)/boot/rootfs.gz
}
Offline
Edit the line [c]loopback[/c]: suppress [c](root)[/c].
You can also suppress the comment [c]# (disk,partition) where the ISO is[/c] 
[c]loopback loop /iso/slitaz-4.0-base.iso[/c]
should solve the problem if GRUB2 finds the ISO.
Offline
Thanks for the replay!
I downloaded a "slitaz-rolling-core 64.iso" image and created a script for it.
menuentry "slitaz-rolling-core64" {
set root=(hd0,gpt5)
loopback loop /iso/slitaz-rolling-core64.iso
linux (loop)/boot/vmlinuz-3.16.55-slitaz64
initrd (loop)/boot/rootfs.gz
}
And it works well!
But the same script, for the "slitaz-4.0-base.iso" image.
menuentry "Slitaz base ISO" {
set root=(hd0,gpt5)
loopback loop /iso/slitaz-4.0-base.iso
linux (loop)/boot/vmlinuz-2.6.37-slitaz
initrd (loop)/boot/rootfs.gz
}
It doesn't work! Grub doesn't write any errors, just a blank screen, that's all! Perhaps it's not compatible with 64-bit systems?
Offline
Right, I can reproduce it; probably the kernel 2.6.37 is too old... 
If you really want to boot in console only you can use slitaz-rolling.iso and load [c]rootfs4.gz[/c] only. In this case you'll access only at 4GB RAM max because the ISO has a 32bit kernel with PAE disabled. If you are interested in, I can send you a link to download the 32bit kernel with PAE enabled so that you can access at the entire memory.
Note that if slitaz-rolling-core64.iso has a 64bit kernel it uses the same packages (32bit) that slitaz-rolling.iso.
Offline
Yes, I would greatly appreciate it if you could provide me with the link to download the 32-bit kernel with PAE (Physical Address Extension) enabled. Thank you in advance!
Could you also please tell me how to extract the rootfs.gz file?
I would like to make changes such as adding a password for automatic login...
I have tried the following methods without success:
(zcat rootfs.gz 2>/dev/null || lzma d rootfs.gz -so) | cpio -id
This command gives me the following errors:
lzma: invalid key - 's[c]lzma: Try 'lzma --help' for more information.[/c]`unexpected end of archive error
I have also tried -
gunzip rootfs.gz
tar -xzf rootfs.gz[c]xz -d rootfs.gz[/c]`zcat rootfs.gz | cpio -id
None of these commands have been successful.
Could you please provide guidance on how to properly extract the rootfs.gz file?
Offline
Here is a link to a zip file:
https://drive.google.com/file/d/17PQu407MpHqPbKQsbXw9B7hImqcIbI5M/view?usp=sharing
Boot the console from slitaz-rolling.iso with [c]initrd (loop)/boot/rootfs4.gz[/c]
From the unziped [c]3.16.55-pae.zip[/c] file, install the linux package:
[c]tazpkg -i /path/to/3.16.55-pae/linux-3.16.55.tazpkg --forced[/c]
and block the package:
[c]tazpkg -b linux[/c]
Copy the new kernel from [c]/boot[/c] in the nvme0n1p5 partition.
Create a rootfs:
[c]tazusb writefs lzma rootfs.gz[/c]
The file is generated in the current directory, copy it in the nvme0n1p5 partition.
Modify the (or create a new) entry in the GRUB2 menu as this:
menuentry "SliTaz Rolling - Console" {
set root=(hd0,gpt5)
linux /boot/vmlinuz-3.16.55-slitaz
initrd /boot/rootfs.gz
}
Reboot and select the entry, you should boot with the PAE kernel if I didn't do any mistake... Login and type [c]free[/c] to check. If it's OK, you can delete the ISOs from nvme0n1p5, you don't need them anymore.
Note that the [c]linux-*-3.16.55[/c] packages from the SliTaz's mirrors are not compatible with the PAE kernel.
Thats's why you'll find other packages in the zip file.
Let's say you want to install the wi-fi: install in this order:
[c]tazpkg -i /path/to/3.16.55-pae/linux-crypto-3.16.55.tazpkg
tazpkg -i /path/to/3.16.55-pae/linux-wireless-3.16.55.tazpkg
tazpkg -gi wpa_supplicant[/c]
Maybe you'll need also linux-firmware
[c]tazpkg -i /path/to/3.16.55-pae/linux-firmware-3.16.55.tazpkg[/c]
Don't forget to block all packages installed from the zip file.
When your configuration works, generate a new [c]rootfs[/c] and copy it in nvme0n1p5 (better to rename the old [c]rootfs[/c] before in case you have a problem with the new one).
Could you please provide guidance on how to properly extract the rootfs.gz file?
The best way is to boot in frugal mode (kernel and rootfs in nvme0n1p5 partition) and not from an ISO. Modify the files you want, add some packages and then save your modifications with Tazusb as described above.
More information about Tazusb: http://hg.slitaz.org/tazusb/raw-file/tip/doc/tazusb.en.html
EDIT:
Forgot to install wpa_supplicant 
Offline
Thank you, but you have too high of an opinion about my Linux knowledge! 
1) I formatted the USB to Fat32 and extracted the downloaded archive "3.16.55-pae.zip" onto it.
2) I booted from the "slitaz-rolling-core64.iso" image and mounted the USB to /mnt.
3) I executed the following commands:
tazpkg -i /path/to/3.16.55-pae/linux-3.16.55.tazpkg --forced
tazpkg -b linux
tazusb writefs lzma rootfs.gz
see screens...
and about this:
Modify the (or create a new) entry in the GRUB2 menu as this:
menuentry "SliTaz Rolling - Console" {
set root=(hd0,gpt5)
linux /boot/vmlinuz-3.16.55-slitaz
initrd /boot/rootfs.gz
}
Question: To complete this step, should the created files be copied with replacement into the "slitaz-rolling-core64.iso" ISO image or directly injected into Grub2?
"I tried doing it that way, but it doesn't work! It gives me the following error message:" server not specified... [attachment=51702,3402] [attachment=51702,3403]
Offline
.
Offline
Hey, no problem with your Linux knowledge, you've done all right!
Now, just copy the [c]vmlinuz-3.16.55-slitaz[/c] and the new [c]rootfs.gz[/c] files in the same place the SliTaz ISO you use for the first boot is.
I guess you have another ditro installed. Then always edit the GRUB2 menu using [c]/etc/grub.d/40_custom[/c] file.
Though, a detail: you used [c]slitaz-rolling-core64.iso[/c] to start... It would be better to use [c]slitaz-rolling.iso[/c] and load [c]rootfs4.gz[/c] in the [c]initrd[/c] line of the menu (the [c]slitaz-rolling.iso[/c] has 4 rootfs). The [c]rootfs.gz[/c] generated with Tazusb will be only ~15MB instead of 56MB and the boot will be much quicker. I suggest you do it again.
Offline
"Now, just copy the vmlinuz-3.16.55-slitaz and the new rootfs.gz files in the same place the SliTaz ISO you use for the first boot is." - I don't understand this line! Do I need to insert the files named "vmlinuz-3.16.55-slitaz" and "rootfs.gz" that were I created yesterday into the ISO image,
in my case, it's "slitaz-rolling.iso"?
I know how to extract a content of an ISO image! To me, need to mount the ISO image to a folder and copy the contents to another folder - it's easy!
But I don't know how to create a new image from the modified "ISO" folder!
Offline
No no no, that's much simpler than what you imagine!
Say your nvme0n1p5 partition is mounted at [c]/mnt[/c], then `
cp vmlinuz-3.16.55-slitaz /mnt
cp rootfs.gz /mnt`
and that's all!
How does boot the computer from the ISO?
The bootloader loads in memory from the root you have defined ([c]set root=(hd0,gpt5)[/c])
[*]the ISO ([c]loopback loop /iso/slitaz-rolling-core64.iso[/c])
[*]then from this, loads the kernel ([c]linux (loop)/boot/vmlinuz-3.16.55-slitaz64[/c])
[*]and the rootfs ([c]initrd (loop)/boot/rootfs.gz[/c])
We don't need the ISO anymore after [c]vmlinuz-3.16.55-slitaz64[/c] and [c]rootfs.gz[/c]) have been extracted of it.
There are advantages to have [c]vmlinuz-3.16.55-slitaz[/c] and [c]rootfs.gz[/c] on the HD
[*]the boot is faster (no need to load an ISO)
[*]you save space in memory (the one occupied by the ISO)
[*]you don't need to build a new ISO each time you generate a new rootfs, just replace the previous one
But as said in my previous post, it would be better to rebuild a new [c]rootfs.gz[/c] starting from [c]slitaz-rolling.iso[/c] (32bit) and its [c]rootfs4.gz[/c] than from core64. I'm not sure that mixing a 32bit kernel with files from a system with a 64bit kernel is a good deal... and [c]rootfs4.gz[/c] is smaller than [c]rootfs.gz[/c] of core64 -> boot still faster.
Offline
I found the answer to my question. https://doc.slitaz.org/en:handbook:hacklivecd
And here's my result
My ISO "slitaz-zerg.iso" is 211,2 МиБ!
My image is loading several times slower than image "slitaz-rolling.iso"!
However, all the memory is being used!
Question: Why did my image become so heavy? [attachment=51708,3405]
Offline
I didn't see your last message! I will redo everything...
Offline
Well done!
211MB... probably because the ISO is not compressed and because core64 is an ISO that boots (when compatible with your HW) in graphic mode.
Using the command [c]tazlito writeiso lzma[/c] will generate a compressed ISO (~60MB) but still slower than booting from a kernel and a compressed rootfs on the HD.
Tell us when you'll have succeeded to boot in frugal mode.
By the way, I forgot to answer on one point: when you generate a new rootfs you can see [c]Failed[/c] when you answer "no" at the question
[c]Do you whish to remove local/keymap settings?[/c]
Don't take care ot it; same thing for me but all seems OK...
Offline
I created a new partition on my SSD drive with a size of 100MB. Formatted it as FAT32, and saved files onto it.
I modified Grub2, and now I can boot from this disk partition "nvme0n1p8"!
Is this what is referred to as booting in frugal mode?
I need make:
1.it does not ask for the username and password.
2. Install "btrfs-progs"
3 Add a bash script to the startup, for example, Hello world!
#!/bin/bash
echo "Hello, world!"
Is it possible in my case? I mean booting from a hard "nvme0n1p8" drive that only has two "files rootfs.gz" and "vmlinuz-3.16.55-slitaz"?
Or do I need to create a ISO image?
Offline
Is this what is referred to as booting in frugal mode?
Yes.
I need make:
1.it does not ask for the username and password.
2. Install "btrfs-progs"
3 Add a bash script to the startup, for example, Hello world!
[*]Normaly, adding [c]autologin[/c] in the [c]linux[/c] line of the GRUB2 menu: [c]linux /boot/vmlinuz-3.16.55-slitaz autologin[/c] does SliTaz boots with the default user (tux); seems not working in console...
[*]As root:
[c]tazpkg -gi btrfs-progs[/c]
Remember you must create and save a new rootfs before to shutdown when you installed new packages if you want to find them at next boot.
[*]This is possible when SliTaz boots in graphic mode but I don't know how to do it in console
Offline
[ Generated in 0.019 seconds, 7 queries executed - Memory usage: 1.6 MiB (Peak: 1.77 MiB) ]