SliTaz Forum

UEFI only Laptop - Trouble booting

(102 posts) (6 voices)

• Started 1 month ago by maybl8
• Latest reply from maybl8
• This topic is not resolved

Tags:

No tags yet.

1. 

   maybl8
   

   online

   Member

   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

   Posted 1 month ago #
2. 

   gibor
   

   offline

   Moderator

   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.

   Posted 1 month ago #
3. 

   Ceel
   

   offline

   Administrator

   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 SliTaz Next (ISO 20170930 - kernel 4.9.30) and press [E] to edit the entry.
   At the end of the linux line add screen=text:
   linux /boot/bzImage ro root=/dev/null video=-32 autologin screen=text
   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 kernel panic try again adding rootdelay=10 after screen=text; this is useful with some USB drives to let the kernel time to detect them.

   menuentry "SliTaz, ISO 4.0" {
set isofile="/boot/slitaz-rolling-core64.iso"

   Is it a tipo?
   Slitaz 4.0 won't boot in UEFI.

   Posted 1 month ago #
4. 

   maybl8
   

   online

   Member

   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.

   Posted 1 month ago #
5. 

   alanyih
   

   offline

   Administrator

   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

   Posted 1 month ago #
6. 

   maybl8
   

   online

   Member

   @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

   Posted 1 month ago #
7. 

   maybl8
   

   online

   Member

   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.

   Posted 1 month ago #
8. 

   maybl8
   

   online

   Member

   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.

   Posted 1 month ago #
9. 

   gibor
   

   offline

   Moderator

   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.

   Posted 1 month ago #
10. 

    maybl8
    

    online

    Member

    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.

    Posted 1 month ago #
11. 

    gibor
    

    offline

    Moderator

    Unfortunately, I don't have any other suggestions on this
    the tests I did on this tablet, and the bios does not support legacy mode; only efi/uefi.

    https://www.manualeduso.it/miia/mwt-743g/manuale

    Posted 1 month ago #
12. 

    maybl8
    

    online

    Member

    OK I had this kind of working.
    I was able to build a EFI GRUB partition with menu entries.
    What I couldn't do was get the GRUB Menu entry to launch the OS.
    So what I think I need to do is create 2 partitions.
    1. an EFI boot partition with GRUB on it for EFI 64 bit
    2. A Linux ext4 partition with the OS on it.

    Somehow I need to get the boot to launch the OS.
    My menu entries must be wrong so far.
    I will post back with my progress.

    Posted 1 month ago #
13. 

    maybl8
    

    online

    Member

    It looks like to me the .zip files have all the files in them but the .iso files don't.
    Can anyone confirm this for me?

    Posted 1 month ago #
14. 

    maybl8
    

    online

    Member

    After messing around a little more I got these messages.

    Booting a command list

    error: unknown filesystem.
    error: you need to load the kernel first.

    Posted 1 month ago #
15. 

    alanyih
    

    offline

    Administrator

    @maybl8

    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.

    Here is my boot partition.
    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

    slitaz-rolling-core64.iso

    # mount -o loop slitaz-rolling-core64.iso /media/cdrom
    mount: /media/cdrom0: WARNING: source write-protected, mounted read-only.

    # tree /media/cdrom
    /media/cdrom
    ├── EFI
    │ ├── boot
    │ │ ├── bootx64.efi
    │ │ ├── linux.cmdline
    │ │ └── rootfs.gz
    │ └── esp.img
    ├── README
    ├── boot
    │ ├── bzImage64
    │ ├── grub
    │ │ └── splash.xpm.gz
    │ ├── ipxe.exe
    │ ├── isolinux
    │ │ ├── boot.cat
    │ │ ├── c32box.c32
    │ │ ├── help.en
    │ │ ├── help.fr
    │ │ ├── i18n.cfg
    │ │ ├── isolinux.bin
    │ │ ├── isolinux.cfg
    │ │ ├── kbd
    │ │ ├── opts.en
    │ │ ├── opts.fr
    │ │ ├── splash.jpg
    │ │ └── vesamenu.c32
    │ ├── linld.com
    │ ├── memtest.exe
    │ ├── memtest64.exe
    │ ├── plop.exe
    │ ├── rootfs.gz
    │ └── vmlinuz-3.16.55-slitaz64
    ├── index.html
    └── md5sum

    6 directories, 28 files

    # file /media/cdrom/EFI/boot/bootx64.efi
    /media/cdrom/EFI/boot/bootx64.efi: Linux kernel x86 boot executable bzImage, version 3.16.55-slitaz64 (root@tank) #2 SMP Thu Jul 14 18:20:24 UTC 2022, RO-rootFS, swap_dev 0X3, Normal VGA

    # cat /media/cdrom/EFI/boot/linux.cmdline
    rw root=0x100 video=-32 autologin initrd=\EFI\boot\rootfs.gz
    #

    slitaz-current-core64.iso

    # mount -o loop slitaz-current-core64.iso /media/cdrom
    mount: /media/cdrom0: WARNING: source write-protected, mounted read-only.

    # tree /media/cdrom
    /media/cdrom
    ├── EFI
    │ ├── boot
    │ │ ├── bootx64.efi
    │ │ ├── linux.cmdline
    │ │ └── rootfs.gz
    │ └── esp.img
    ├── README
    ├── boot
    │ ├── bzImage64
    │ ├── grub
    │ │ └── splash.xpm.gz
    │ ├── ipxe.exe
    │ ├── isolinux
    │ │ ├── boot.cat
    │ │ ├── c32box.c32
    │ │ ├── help.en
    │ │ ├── help.fr
    │ │ ├── i18n.cfg
    │ │ ├── isolinux.bin
    │ │ ├── isolinux.cfg
    │ │ ├── kbd
    │ │ ├── opts.en
    │ │ ├── opts.fr
    │ │ ├── splash.jpg
    │ │ └── vesamenu.c32
    │ ├── linld.com
    │ ├── memtest.exe
    │ ├── memtest64.exe
    │ ├── plop.exe
    │ ├── rootfs.gz
    │ └── vmlinuz-5.10.210-slitaz64
    ├── index.html
    └── md5sum

    6 directories, 28 files

    # file /media/cdrom/EFI/boot/bootx64.efi
    /media/cdrom/EFI/boot/bootx64.efi: Linux kernel x86 boot executable bzImage, version 5.10.210-slitaz64 (root@tank) #2 SMP Thu Mar 7 14:38:29 Europe 2024, RO-rootFS, swap_dev 0X5, Normal VGA

    # cat /media/cdrom/EFI/boot/linux.cmdline
    rw root=0x100 video=-32 autologin initrd=\EFI\boot\rootfs.gz
    #

    Posted 1 month ago #

RSS feed for this topic

Reply »

You must log in to post.