SliTaz Forum
You are not logged in.
I am new to Slitaz linux. Was doing allot of reading and like the idea of a small size rolling release that I can run from a 4GB USB Drive.
This is where I am at this point. I have been able to get it working on a BIOS/UEFI computer in Legacy mode. I created a USB drive with adding GRUB uefi from 5 year old instructions. However when booting it I get the GRUB menu but it just ends up with a black screen and I have to hard reboot the laptop.
I will provide whatever is needed to try to troubleshoot this.
I have tried different iso's but don't know which one is the best for this.
Let me know if I can help make this type of install easier.
Thanks
Offline
When slitaz-rolling-core64.iso is copied to a USB flash drive via:
[c]# dd if=slitaz-rolling-core64.iso of=/dev/sdb bs=1M[/c]
where /dev/sdb is the flash drive,
SliTaz can be booted in UEFI mode from that device.
Beware: all other data on the USB flash drive is lost with the above command!
With slitaz-current-core64.iso this does not work!
EFI/esp.img in that ISO is much smaller than that in rolling.
Offline
All that does is put the EFI folder on the flash drive.
It does not boot on my Laptop.
What are the next steps to make that flash drive able to boot into Slitaz?
Offline
With [c]of=[/c] the name of the whole device must be given (say /dev/sdb), not the name of a partition (like /dev/sdb1) and the EFI device menue must be entered to select the USB flash drive.
Offline
Did you use the same computer to boot in BIOS Legacy then in UEFI or are they 2 different computers?
In the second case, maybe the UEFI computer is too recent and its graphic card is not supported in Rolling.
Offline
@HGT I did /dev/sda
@Ceel 2 different computers. The one where I have the live USB booting is BIOS/UEFI
The one that I want to use is a UEFI only HP Laptop with 2 video cards.
[c]Machine:
Type: Convertible System: HP product: HP Spectre x360 Convertible 15-df1xxx
v: N/A serial: <superuser required> Chassis: type: 31
serial: <superuser required>
Mobo: HP model: 863F v: 54.24 serial: <superuser required>
part-nu: 7UT64UA#ABA uuid: <superuser required> UEFI: AMI v: F.29
date: 11/02/2022
Battery:
ID-1: BAT0 charge: 63.7 Wh (100.0%) condition: 63.7/63.7 Wh (100.0%)
volts: 12.9 min: 11.6 model: HP Primary type: Li-ion serial: <filter>
status: full cycles: 239
Device-1: hid-0018:04F3:2992.0001-battery model: ELAN2514:00 04F3:2992
serial: N/A charge: N/A status: N/A
CPU:
Info: model: Intel Core i7-10510U bits: 64 type: MT MCP
arch: Comet/Whiskey Lake note: check gen: core 10 level: v3 note: check
built: 2018 process: Intel 14nm family: 6 model-id: 0x8E (142)
stepping: 0xC (12) microcode: 0xF8
Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache:
L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB
L3: 8 MiB desc: 1x8 MiB
Speed (MHz): avg: 2540 high: 3875 min/max: 400/4900 scaling:
driver: intel_pstate governor: powersave cores: 1: 3807 2: 3809 3: 400
4: 400 5: 3875 6: 3800 7: 400 8: 3833 bogomips: 36812
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities:
Type: gather_data_sampling mitigation: Microcode
Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
Type: retbleed mitigation: Enhanced IBRS
Type: spec_rstack_overflow status: Not affected
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
sanitization
Type: spectre_v2 mitigation: Enhanced / Automatic IBRS, IBPB:
conditional, RSB filling, PBRSB-eIBRS: SW sequence
Type: srbds mitigation: Microcode
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: Intel CometLake-U GT2 [UHD Graphics] vendor: Hewlett-Packard
driver: i915 v: kernel arch: Gen-9.5 process: Intel 14nm built: 2016-20
ports: active: eDP-1 empty: DP-1,DP-2 bus-ID: 00:02.0 chip-ID: 8086:9b41
class-ID: 0300
Device-2: NVIDIA GP108M [GeForce MX250] vendor: Hewlett-Packard
driver: nvidia v: 550.54.14 alternate: nouveau,nvidia_drm non-free: 545.xx+
status: current (as of 2024-02; EOL~2026-12-xx) arch: Pascal code: GP10x
process: TSMC 16nm built: 2016-2021 pcie: gen: 1 speed: 2.5 GT/s lanes: 4
link-max: gen: 3 speed: 8 GT/s bus-ID: 3b:00.0 chip-ID: 10de:1d13
class-ID: 0302
Device-3: Chicony HP Wide Vision FHD Camera driver: uvcvideo type: USB
rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-5:2 chip-ID: 04f2:b67b
class-ID: 0e02 serial: <filter>
Display: x11 server: X.Org v: 21.1.11 with: Xwayland v: 23.2.4
compositor: kwin_x11 driver: X: loaded: modesetting,nvidia dri: iris
gpu: i915 display-ID: :0 screens: 1
Screen-1: 0 s-res: 3840x2160 s-dpi: 220 s-size: 443x249mm (17.44x9.80")
s-diag: 508mm (20.01")
Monitor-1: eDP-1 model: AU Optronics 0x30eb built: 2017 res: 3840x2160
hz: 60 dpi: 284 gamma: 1.2 size: 344x193mm (13.54x7.6") diag: 394mm (15.5")
ratio: 16:9 modes: 3840x2160
API: EGL v: 1.5 hw: drv: intel iris drv: nvidia platforms: device: 0
drv: nvidia device: 1 drv: iris device: 3 drv: swrast surfaceless:
drv: nvidia x11: drv: iris inactive: gbm,wayland,device-2
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: intel mesa v: 24.0.2-manjaro1.1
glx-v: 1.4 direct-render: yes renderer: Mesa Intel UHD Graphics (CML GT2)
device-ID: 8086:9b41 memory: 14.9 GiB unified: yes
API: Vulkan v: 1.3.276 layers: 5 device: 0 type: discrete-gpu
name: NVIDIA GeForce MX250 driver: nvidia v: 550.54.14 device-ID: 10de:1d13
surfaces: xcb,xlib device: 1 type: integrated-gpu name: Intel UHD
Graphics (CML GT2) driver: mesa intel v: 24.0.2-manjaro1.1
device-ID: 8086:9b41 surfaces: xcb,xlib
Audio:
Device-1: Intel Comet Lake PCH-LP cAVS vendor: Hewlett-Packard
driver: sof-audio-pci-intel-cnl alternate: snd_hda_intel, snd_soc_skl,
snd_sof_pci_intel_cnl bus-ID: 00:1f.3 chip-ID: 8086:02c8 class-ID: 0401
API: ALSA v: k6.7.7-1-MANJARO status: kernel-api with: aoss
type: oss-emulator tools: alsactl,alsamixer,amixer
Server-1: JACK v: 1.9.22 status: off tools: N/A
Server-2: PipeWire v: 1.0.3 status: active with: 1: pipewire-pulse
status: active 2: pipewire-media-session status: active 3: pipewire-alsa
type: plugin tools: pactl,pw-cat,pw-cli
Network:
Device-1: Intel Comet Lake PCH-LP CNVi WiFi driver: iwlwifi v: kernel
bus-ID: 00:14.3 chip-ID: 8086:02f0 class-ID: 0280
IF: wlan0 state: up mac: <filter>
Info: services: NetworkManager, systemd-networkd, systemd-timesyncd,
wpa_supplicant
Drives:
Local Storage: total: 935.29 GiB used: 250.07 GiB (26.7%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung
model: SSD 970 EVO Plus 1TB size: 931.51 GiB block-size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: 2B2QEXM7 temp: 38.9 C scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Silicon Motion model: N/A
size: 3.77 GiB block-size: physical: 512 B logical: 512 B type: USB rev: 2.0
spd: 480 Mb/s lanes: 1 mode: 2.0 tech: N/A serial: <filter> fw-rev: 1100
scheme: GPT
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
ID-1: / raw-size: 163 GiB size: 160.13 GiB (98.24%) used: 55.9 GiB (34.9%)
fs: ext4 dev: /dev/nvme0n1p8 maj-min: 259:8
ID-2: /boot/efi raw-size: 499 MiB size: 498 MiB (99.80%)
used: 32.9 MiB (6.6%) fs: vfat dev: /dev/nvme0n1p2 maj-min: 259:2
ID-3: /home raw-size: 399.57 GiB size: 392.23 GiB (98.16%)
used: 194.09 GiB (49.5%) fs: ext4 dev: /dev/nvme0n1p7 maj-min: 259:7
Swap:
Alert: No swap data was found.
Sensors:
System Temperatures: cpu: 55.0 C pch: 53.0 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Memory: total: 16 GiB note: est. available: 15.26 GiB used: 4.01 GiB (26.2%)
Processes: 353 Power: uptime: 23m states: freeze,mem,disk suspend: s2idle
wakeups: 1 hibernate: platform avail: shutdown, reboot, suspend, test_resume
image: 6.08 GiB services: org_kde_powerdevil,upowerd Init: systemd v: 255
default: graphical tool: systemctl
Packages: pm: pacman pkgs: 1882 libs: 472 tools: pacaur,pamac,pikaur,yay
Compilers: clang: 16.0.6 gcc: 13.2.1 Shell: Bash v: 5.2.26
running-in: alacritty inxi: 3.3.33[/c]
Offline
I'm not on a SliTaz computer at this moment.
Add [c]screen=text[/c] at the end of the linux line; this should allow you to boot in console. Then run [c]startx[/c] and post the [c]/var/log/Xorg.0.log[/c]
Seems your intel card use 915resolution (that is in the ISO); the NVidia should run with the [c]nouveau[/c] driver. What is the output of [c]lsmod[/c]?
Maybe you need to install [c]xorg-xf86-video-nv[/c] (I don't remember if it is in the ISO but I don't think so). But not sure you can connect to the internet? A way that has always work for me: connect through a smartphone via USB, change [c]eth0[/c] by [c]usb0[/c] in [c]/etc/network.conf[/c] and restart the network: [c]/etc/init.d/network.sh restart[/c]
Offline
OK I don't think you guys are following me or I am not understanding something.
When I use the dd command from above I end up with a EFI folder that has some files in it.
That doesn't boot on its own.
I created a live usb from the 5in1 iso. I can boot to it in my Legacy or BIOS/UEFI machine.
When I use that to create a usb I use the option to make the usb a rolling release from the web option.
I select bootable and it creates the usb. But I can't boot to that either on my UEFI only laptop.
@Ceel I don't think I am where you are at on my USB drive.
I hope this makes sense.
Offline
I have been thinking about what I see here.
I see that I have 3 separate pieces that need to be put together in one .iso.
I am not sure how to do that but here is what I see.
1. We have the base system that is the running Slitaz OS.
2. We have the EFI for UEFI systems.
3. And we have GRUB .
I don't know if this can be done but let me know what you think?
Thanks
Offline
What you see on the flash drive depends on how you mount it:
[c]# mount /dev/sda1 /mnt[/c]
makes just the directory EFI available in /mnt
[c]# mount /dev/sda /mnt[/c]
makes additionally the directory boot available in /mnt
So all files for booting SliTaz should be available on the flash drive.
When it is not mandatory to boot SliTaz live from a flash drive and the "main" system is booted by GRUB2, SliTaz live can be booted from an ISO file on SSD with GRUB loopback:
Suppose slitaz-current-core64.iso is stored in /boot, the following menue entry can be added to
the GRUB2 configuration file:
[c]
menuentry 'Slitaz current64 (loopback)' {
insmod gzio
set isofile=/boot/slitaz-current-core64.iso
loopback lb $isofile
linux (lb)/boot/bzImage64
initrd (lb)/boot/rootfs.gz
}
[/c]
For testing the above statements (within the curly braces) can be entered in GRUB2 command mode.
Offline
Still can't get it to boot into the os.
Here is my boot partition.
I do get grub and see the menu entries.
[c]demo@Manjaro mnt]$ tree
.
├── boot
│ ├── bzImage
│ ├── grub
│ │ ├── grub.cfg
│ │ └── splash.xpm.gz
│ ├── ipxe
│ ├── isolinux
│ │ ├── boot.cat
│ │ ├── c32box.c32
│ │ ├── help.en
│ │ ├── help.fr
│ │ ├── i18n.cfg
│ │ ├── isolinux.bin
│ │ ├── isolinux.cfg
│ │ ├── kbd
│ │ ├── opts.en
│ │ ├── opts.fr
│ │ ├── splash.png
│ │ ├── ter-v16v.psf
│ │ └── vesamenu.c32
│ ├── linld.com
│ ├── memtest
│ ├── rootfs.gz
│ ├── slitaz-rolling-core64.iso
│ └── vmlinuz-4.9.30-slitaz
└── efi
└── boot
└── bootx64.efi
6 directories, 23 files[/c]
Offline
vmlinuz-4.9.30-slitaz
From where does this kernel come from? It is not in the repo.
Offline
I followed the instructions from this page:
https://doc.slitaz.org/en:guides:uefi-live
Where it says
wget http://cook.slitaz.org/next64/grub2/browse/taz/grub2-efi-2.02/fs/boot/efi/boot/bootx64.efi
I changed 2.02 to 2.04
Offline
My 2cents...
The executable
└─── efi
└─── boot
└─── bootx64.efi
calls up the menu
├─── boot
│ ├─── bzImage.
│ ├─── grub
│ │ ├── grub.cfg
And the whole thing sits on a fat32 partition on a gpt-formatted flash drive.
The OS launched: either it is live, or it sits on a linux partition.
From here you need to set which in the grub.cfg menu.
At boot you give an "ls" and find out which partitions it sees
ex.
set=root (hd0,gpt1)
In some cases and for some strange reason, the pc only runs exclusively (bootia32.efi) 32-bit.
I doubt however that slitaz supports xorg wayland....
-------------------------------------------------------------------------
I miei 2cents...
L'eseguibile
└── efi
└── boot
└── bootx64.efi
richiama il menu
├── boot
│ ├── bzImage
│ ├── grub
│ │ ├── grub.cfg
ed il tutto se ne sta su una partizione fat32 su chiavetta formattata di tipo gpt
Il Sistema operativo lanciato: o è live, o se ne sta su una partizione linux.
Da qui occorre settare quali nel menu di grub.cfg.
Al boot si dà un “ls” e si scopre quali partizioni vede
es.
set=root (hd0,gpt1)
In qualche caso e per qualche strana ragione, il pc esegue solo esclusivamente (bootia32.efi) a 32 bit.
Dubito comunque che slitaz supporti xorg wayland...
Offline
Below is the grub.cfg menu entries I am trying to use on the usb drive.
I created these from various web searches I found
All I get when trying to use these is the message:
"Booting a command list"
[c]### CONFIGURATION FILE FOR GRUB 2 ###
#
# Comment the line if you want SliTaz to start automatically at boot or
# change the value to define the time (seconds) to wait before booting.
set TIMEOUT=-1
# Menu 0: boot SliTaz Next
menuentry "SliTaz Next (ISO 20170930 - kernel 4.9.30)" {
set root=(hd0,2)
linux /boot/bzImage ro root=/dev/null video=-32 autologin
initrd /boot/rootfs.gz
}
menuentry 'Slitaz current64 (loopback)' {
insmod gzio
set isofile=/boot/slitaz-rolling-core64.iso
loopback lb $isofile
linux (lb)/boot/bzImage64 root=/dev/null video=-32 autologin
initrd (lb)/boot/rootfs.gz
}
menuentry "SliTaz, ISO 4.0" {
set isofile="/boot/slitaz-rolling-core64.iso"
loopback iso $isofile
linux (iso)/boot/bzImage64 from=$isofile ramdisk_size=6666 home=usb root=/dev/ram0 rw autoexec=startx changes=s512.dat
initrd (iso)/boot/rootfs.gz
}
Here is the bootefimgr list .
This is when I boot to an os on the ssd drive with the usb drive plugged in.[/c]
demo@Manjaro ~]$ efibootmgr
BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 0005,0004,0007,0003,0009,0006,0002,0001,0000,0008,9999
Boot0000* Windows Boot Manager HD(2,GPT,5758188c-330c-4b9b-a98f-e999cf7ec14e,0x109000,0xf9800)/\EFI\Microsoft\Boot\bootmgfw.efi57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000061000100000010000000040000007fff0400
Boot0001* grub HD(2,GPT,5758188c-330c-4b9b-a98f-e999cf7ec14e,0x109000,0xf9800)/\EFI\grub\grubx64.efi
Boot0002* ubuntu HD(1,GPT,f35fcaa5-ddbe-49dc-95ed-e6be2e5016fc,0x1000,0x96000)/\EFI\ubuntu\shimx64.efi
Boot0003* Solus Linux Bootloader HD(1,GPT,3bccf0a6-d282-4f37-bc0e-1760c1bcaeae,0x800,0xf4800)/\EFI\com.solus-project\bootloaderx64.efi
Boot0004* opensuse-secureboot HD(1,GPT,989c0e84-410b-4da9-a089-427a380ba194,0x800,0xfa000)/\EFI\opensuse\shim.efi
Boot0005* debian HD(1,GPT,8795ca5b-6416-fe42-9a1b-3d9d19d83ded,0x1000,0x1dcd65)/\EFI\debian\shimx64.efi
Boot0006* void HD(1,MBR,0x47100c3d,0x800,0x1dcd65)/\EFI\void\grubx64.efi
Boot0007* pclinuxos HD(1,MBR,0x8158218d,0x800,0x200000)/\EFI\pclinuxos\grubx64.efi
Boot0008* Solid State Disk PciRoot(0x0)/Pci(0x1d,0x4)/Pci(0x0,0x0)/NVMe(0x1,00-25-38-58-01-40-F1-74)/HD(2,GPT,5758188c-330c-4b9b-a98f-e999cf7ec14e,0x109000,0xf9800)0000424f
Boot0009* Slackware HD(1,GPT,c2928cd9-958c-4d44-86ea-ca1584314bea,0x800,0x1dd000)/\EFI\Slackware\elilo.efi
Boot9999* USB Drive (UEFI) PciRoot(0x0)/Pci(0x1d,0x0)/USB(16,0)0000424f`
Let me know what to change or any other info you need.
Thanks
Offline
Here is more info:
Partition table entries are not in disk order.
Disk /dev/sda: 3.77 GiB, 4051697664 bytes, 7913472 sectors
Disk model:
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xfd7d5949
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 1026047 1024000 500M c W95 FAT32 (LBA)
/dev/sda2 1026048 2254847 1228800 600M 83 Linux
Offline
I'm struggling to follow the reasoning because of the language... first question
Can you get the flash drive grub at boot?
If no, the problem is how it is prepared (e.g., it lacks EFI-type partition and maybe GPT-type), or bios settings like secureboot.
If yes, but you get no boot, the problem is with the grub.cfg configuration or slitaz not supporting your hardware.
-------------------------------------------------------------------------
Fatico a seguire i ragionamenti per via della lingua... prima domanda
Riesci ad avere il grub della chiavetta al boot?
Se no, il problema è come è preparata (es. manca della partizione tipo EFI e magari di tipo GPT), o delle impostazione del bios tipo secureboot.
Se sì, ma non ottieni nessun avvio, il problema è della configurazione del grub.cfg o di slitaz che non supporta il tuo hardware.
Offline
I followed the instructions from this page:
https://doc.slitaz.org/en:guides:uefi-live
OK that's clearer. This method works. But you didn't use the Rolling release. "Next" is an old discontinued and unstable project. Better to switch to Rolling.
Booting a command list
This is a good news. It means you edit an entry from the menu and press [F10] to boot.
So, boot from your flash drive. When the Grub menu displays, select [c]SliTaz Next (ISO 20170930 - kernel 4.9.30)[/c] and press [E] to edit the entry.
At the end of the [c]linux[/c] line add [c]screen=text[/c]:
[c]linux /boot/bzImage ro root=/dev/null video=-32 autologin screen=text[/c]
and press [F10].
Does the computer boots in console mode?
Note it can take time before the boot starts (a few tens of seconds) because the kernel and the rootfs must be loaded first.
If the boot ends in a [c]kernel panic[/c] try again adding [c]rootdelay=10[/c] after [c]screen=text[/c]; this is useful with some USB drives to let the kernel time to detect them.
[c]menuentry "SliTaz, ISO 4.0" {
set isofile="/boot/slitaz-rolling-core64.iso"[/c]
Is it a tipo?
Slitaz 4.0 won't boot in UEFI.
Offline
Adding those kernel parameters didn't make any difference. Still locked up without any additional messages.
Of the 3 menu entries I have should I concentrate on just one of them?
The menu entry titles don't mean much to me. I just copied them from one of the examples I found. I can change it to whatever you want.
@gibor Yes I have a grub menu upon booting. Just can't get anywhere from there.
Offline
Try:
slitaz-current-core64.iso or slitaz-rolling-core64.iso
https://mirror1.slitaz.org/iso/rolling/slitaz-rolling-core64.iso
https://mirror1.slitaz.org/iso/current/slitaz-current-core64.iso
and
When slitaz-rolling-core64.iso is copied to a USB flash drive via:
# dd if=slitaz-rolling-core64.iso of=/dev/sdb bs=1M
where /dev/sdb is the flash drive,
SliTaz can be booted in UEFI mode from that device.
https://forum.slitaz.org/topic/uefi-only-laptop-trouble-booting#post-52099
Offline
@alanyih
After doing what you showed. All I end up with is one partition on the flash drive and the machine doesn't boot to grub anymore and just locks up with a blank screen.
[demo@Manjaro ~]$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 1 3.8G 0 disk
└─sda1 8:1 1 52.7M 0 part
nvme0n1 259:0 0 931.5G 0 disk
├─nvme0n1p1 259:1 0 529M 0 part
├─nvme0n1p2 259:2 0 499M 0 part /boot/efi
├─nvme0n1p3 259:3 0 16M 0 part
├─nvme0n1p4 259:4 0 219G 0 part
├─nvme0n1p5 259:5 0 961M 0 part
├─nvme0n1p6 259:6 0 90G 0 part
├─nvme0n1p7 259:7 0 397.6G 0 part /home
├─nvme0n1p8 259:8 0 163G 0 part /
├─nvme0n1p9 259:9 0 44G 0 part
├─nvme0n1p11 259:10 0 16G 0 part
└─nvme0n1p12 259:11 0 3M 0 part
Offline
Looking at what it installed closer all that is on the flash drive is an EFI folder.
I think I mentioned that in a previous post.
Offline
Something weird is going on with my system.
For some reason when I try to read the contents of the iso file it only shows the EFI folder not any of the other folders.
Not sure what is going on.
Offline
The isoloop method doesn't work for me, if I want to test iso's I have to extract them.
Following the comments preceded by the symbol >>>
the rest is the terminal output
>>>create temp folder
mkdir slitaz-rolling-core
>>>download iso core
wget http://mirror.slitaz.org/iso/rolling/slitaz-rolling-core.iso
>>>unpack iso
7z x slitaz-rolling-core.iso
>>>insert usb stick (my case dev/sda)
fdisk /dev/sda
Welcome to fdisk (util-linux 2.36).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
The backup GPT table is corrupt, but the primary appears OK, so that will be used.
>>>create gpt table "g"
Comando (m per richiamare la guida): g
Created a new GPT disklabel (GUID: 831FC7E4-EAEB-BF4E-85BE-F44E48F233EE).
>>>create new partition "n"
Comando (m per richiamare la guida): n
Numero della partizione (1-128, default 1):
First sector (2048-496606, default 2048):
Last sector, +/-sectors or +/-size{K,M,G,T,P} (2048-496606, default 496606):
Created a new partition 1 of type 'Linux filesystem' and of size 241,5 MiB.
Partition #1 contains a vfat signature.
Do you want to remove the signature? [Y]es/[N]o: y
The signature will be removed by a write command.
>>>change partition 'linux' to 'EFI System' "t" "1"
Comando (m per richiamare la guida): t
Selected partition 1
Partition type or alias (type L to list all): 1
Changed type of partition 'Linux filesystem' to 'EFI System'.
>>>write and exit fdisk
Comando (m per richiamare la guida): wq
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.
>>>format partition FAT32
mkdosfs -F32 -v -n "" /dev/sda1
>>> mount partition on temp folder
mount /dev/sda1 /tmp
ls
boot EFI md5sum slitaz-rolling-core64.iso
'[BOOT]' index.html README
>>>copy folder EFI and boot from iso extracted
cp -r boot EFI /tmp/
umount /tmp
>>>reboot system with usb key inserted and the bios show bootable usb
>>>From me so the 32bit core iso boots correctly, while the 64 iso boots but not in graphics.
>>>The grub menu is missing because it is not contained in the iso. To get it you have to copy from a working systema the /boot/grub folder to the stick.
Offline
Have you tried this on a UEFI only system?
This doesn't work.
I get the files on the usb drive.
I copied an existing grub over but it doesn't boot to it.
Even if it worked it would only be the boot files. None of the OS files are there.
Can we get the the EFI 64 boot files, GRUB and the OS files all on one iso and have the iso get installed with something like etcher or some other iso installer so it would create the directories and format the usb for the boot partition and the OS linux partions so that when you reboot there is a GRUB entry and you select it and it boots into slitaz?
It looks like you have some of the pieces but not all put together.
Offline
[ Generated in 0.019 seconds, 7 queries executed - Memory usage: 1.63 MiB (Peak: 1.77 MiB) ]