WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: GRUB 2 always starts in command line - can't proceed - EFI Boot  (Read 9094 times)

Offline Rich

  • TinyCore Moderator
  • Hero Member
  • *****
  • Posts: 6830
Re: GRUB 2 always starts in command line - can't proceed - EFI Boot
« Reply #45 on: August 16, 2019, 08:15:29 AM »
Hi Juanito
There's a small problem here:
http://tinycorelinux.net/10.x/x86_64/archive/10.0/distribution_files/
The  modules64  and  the  vmlinuz64  links (including the md5) are broken:
Code: [Select]
corepure64.gz                                      09-Jun-2019 12:39            10397440
corepure64.gz.md5.txt                              09-Jun-2019 12:39                  48
modules64.gz                                       09-Jun-2019 12:39                  52
modules64.gz.md5.txt                               09-Jun-2019 12:39                  60
rootfs64.gz                                        09-Jun-2019 12:39             3595754
rootfs64.gz.md5.txt                                09-Jun-2019 12:39                  46
vmlinuz64                                          09-Jun-2019 12:39                  49
vmlinuz64.md5.txt                                  09-Jun-2019 12:39                  57


Offline Rich

  • TinyCore Moderator
  • Hero Member
  • *****
  • Posts: 6830
Re: GRUB 2 always starts in command line - can't proceed - EFI Boot
« Reply #47 on: August 16, 2019, 08:46:10 AM »
Hi labeas
....
Q: are these sizes correct/compatible:
  vmlinuzBigr   4106416
  rotofs64.gz   3595754
  modules64.gz  6826959

AFAIR there was some inconsistency in the repository IMO.

==TIA
The  rootfs64.gz  and  modules64.gz  both appear to be from TC10.0 x86_64. The  vmlinuzBigr  is from TC9.0 x86:
Code: [Select]
Index of /9.x/x86/release/distribution_files/
../
core.gz                                            19-Mar-2018 10:33             8730363
core.gz.md5.txt                                    19-Mar-2018 10:33                  42
modules.gz                                         27-Feb-2018 07:19             6000561
modules.gz.md5.txt                                 27-Feb-2018 07:19                  45
modules64.gz                                       27-Feb-2018 07:19             6448695
modules64.gz.md5.txt                               27-Feb-2018 07:19                  47
rootfs.gz                                          19-Mar-2018 10:33             2763805
rootfs.gz.md5.txt                                  19-Mar-2018 10:33                  44
vmlinuz                                            27-Feb-2018 07:19             4106416  <--------------
vmlinuz.md5.txt                                    27-Feb-2018 07:19                  42
vmlinuz64                                          27-Feb-2018 07:19             4491536
vmlinuz64.md5.txt                                  27-Feb-2018 07:19                  44
So  vmlinuzBigr  is the wrong version and it's the wrong architecture.

Try reading Juanitos instructions again:
http://forum.tinycorelinux.net/index.php/topic,22999.msg144515.html#msg144515
This way you only have 2 files to deal with (corepure64.gz == rootfs64.gz  + modules64.gz).
You can find them here:
http://tinycorelinux.net/10.x/x86_64/release/distribution_files/


Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 11003
Re: GRUB 2 always starts in command line - can't proceed - EFI Boot
« Reply #49 on: August 17, 2019, 01:02:01 AM »
There's a small problem here:
http://tinycorelinux.net/10.x/x86_64/archive/10.0/distribution_files/
The  modules64  and  the  vmlinuz64  links (including the md5) are broken:

'hopefully fixed

Offline coreplayer2

  • Hero Member
  • *****
  • Posts: 3020
Re: GRUB 2 always starts in command line - can't proceed - EFI Boot
« Reply #50 on: August 17, 2019, 11:46:33 AM »
@ labeas

After correctly downloading and installing matching kernel and TC-10 files;  For a full diagnostic, please post the full and unedited results of these commands:

Code: [Select]
ls -l /mnt/sd*
Code: [Select]
fdisk -l | grep sd
Code: [Select]
dmesg | grep sd
Code: [Select]
blkid | grep sd