Z83-4 with Ubuntu 18.04.1 not open

B

Billybreg

Member
Hi i'm Marco from Italy
I have this problem with Z83-4 with Ubuntu 18.04.1 dawnloaded here
When I turn on the Minix the Ubuntu purple screen appears and I press exit and go to recovery mode then ubuntu opens but if I turn it off it won't turn on anymore and I have to go back into recovery. How can I do ?
Ciao grazie
 

Attachments

  • Minix.JPG
    Minix.JPG
    40.7 KB · Views: 22
Billybreg said:
Hi i'm Marco from Italy
I have this problem with Z83-4 with Ubuntu 18.04.1 dawnloaded here
When I turn on the Minix the Ubuntu purple screen appears and I press exit and go to recovery mode then ubuntu opens but if I turn it off it won't turn on anymore and I have to go back into recovery. How can I do ?
Ciao grazie
Click to expand...
Hi and welcome ☺
@linuxium can you please give your opinion about this question ?
 
Last edited:
Billybreg said:
Hi i'm Marco from Italy
I have this problem with Z83-4 with Ubuntu 18.04.1 dawnloaded here
When I turn on the Minix the Ubuntu purple screen appears and I press exit and go to recovery mode then ubuntu opens but if I turn it off it won't turn on anymore and I have to go back into recovery. How can I do ?
Ciao grazie
Click to expand...

You are in the 'UEFI: Built-in EFI Shell' which is not part of Ubuntu. You need to enter 'fs0:\efi\ubuntu\grubx64.efi' to boot GRUB.

As there is currently a bug in the BIOS that prevents the latest Ubuntu Bionic kernel from booting with HDMI support you should use the temporary work around of interrupting the GRUB boot process by pressing ESC when you see the purple screen. From the menu that appears select the "Advanced options for Ubuntu" and then the "recovery" option of the kernel you want to boot e.g. Ubuntu, with Linux 4.15.0-64-generic (recovery mode). After a few moments, it will display a Recovery Menu with a number of options. Select the first option "resume" for "Resume normal boot" followed by "OK". Your device will then complete booting and HDMI will now work.

Also follow the post https://theminixforum.com/index.php...untu-issues-on-minix-neo-z83-4-mini-pcs.1787/ for updates on when the HDMI issue will be fixed in Ubuntu.
 
Billybreg said:
Hi
I try fs0:\efi\ubuntu\grubx64.efi but tells me "command not found".
I went to recovery mode but nothing changed
Click to expand...

Can you explain in more detail? You went to recovery mode but nothing changed ... what didn't change and what were you expecting? While in recovery mode did you select the "resume" option and did Ubuntu boot?
 
notrui2 said:
https://www.linux.com/tutorials/how-rescue-non-booting-grub-2-linux/
Try that link:
See the part in Booting From grub and see if it works.
Sorry but i am novice in linux, i rarely use ubuntu (and in a virtual machine)
I only know a few things.
Click to expand...

@notrui2: The picture does not show GRUB so that link is not applicable. The picture shows the UEFI: Built-in EFI Shell which incidentally has nothing to do with Ubuntu and can be accessed directly from the BIOS.

@Billybreg: At the 'Shell>' prompt what do the following commands show?

ls fs0:
ls fs0:\efi
ls fs0:\efi\ubuntu
ls fs0:\efi\boot

Edited: To include clarification of whom the comments are directed to.
 
Last edited:
ls lists directory contents of files and directories.
I used before ssh in command prompt.
I know how to list directories , show files, copy files , changing from one directory to other, etc. and how work with that....
If we know how to use command prompt in windows and navigate to folders we know how to work with linux.
I also used putty and i have devices that are using linux , so i know how to connect to them , NAS , router, etc.
I have routers running dd-wrt and i love it ?

But Like i said i only know basic things because i dont spent many time with it.
I learned before a long time ago and recently i tested again.
It is not interesting for me learning more about this matter (linux commands and some other stuff in linux world), i prefer others things, the basic for me is enough.
But Thank you @linuxium ☺.
It is good to have someone like you in this forum , with that experience.
Yes the picture does not show GRUB, you are right.

One of my NAS (synology ds418) has pxe network (linux ☺) and it has a boot menu similar to GRUB and before i was replying @Billybreg question, i did not see the picture again.
 
Last edited:
linuxium said:
Can you explain in more detail? You went to recovery mode but nothing changed ... what didn't change and what were you expecting? While in recovery mode did you select the "resume" option and did Ubuntu boot?
Click to expand...
Yes wen i select resume ubuntu start normaly but wen i restart dont work. In recovery mode i select eaven the restore grub but nothing change.
 
linuxium said:
@notrui2: The picture does not show GRUB so that link is not applicable. The picture shows the UEFI: Built-in EFI Shell which incidentally has nothing to do with Ubuntu and can be accessed directly from the BIOS.

@Billybreg: At the 'Shell>' prompt what do the following commands show?

ls fs0:
ls fs0:\efi
ls fs0:\efi\ubuntu
ls fs0:\efi\boot

Edited: To include clarification of whom the comments are directed to.
Click to expand...
marco@NEO-Z83-4:~$ ls fso
ls: impossibile accedere a 'fso': File o directory non esistente
marco@NEO-Z83-4:~$ ls fs0:
ls: impossibile accedere a 'fs0:': File o directory non esistente
marco@NEO-Z83-4:~$ ls fs0:\efi
ls: impossibile accedere a 'fs0:efi': File o directory non esistente
marco@NEO-Z83-4:~$ ls fs0:\efi\ubuntu
ls: impossibile accedere a 'fs0:efiubuntu': File o directory non esistente
marco@NEO-Z83-4:~$ ls fs0:\efi\boot
ls: impossibile accedere a 'fs0:efiboot': File o directory non esistente
marco@NEO-Z83-4:~$
Unable to access file or directory that does not exist
 
Hi everyone
I did this command sudo apt get install grub end it happen this
Reading package list ... Done
Dependency tree generation
Reading status information ... Done
The grub package has no versions available, but is named by another
package. This could indicate that the package is missing, obsolete
or is available only within another source
However, these packages replace it:
grub2-common: i386 grub-pc: i386 grub-efi-ia32: i386 grub-efi-amd64: i386
grub2-common grub-pc grub-efi-ia32 grub-efi-amd64

E: The "grub" package has no candidate to install
marco @ NEO-Z83-4: ~
 
In recovery mode i try to restore grub and and the result was:
File or directory not exist and look the attachment
 

Attachments

  • Schermata da 2019-09-27 16-26-40.png
    Schermata da 2019-09-27 16-26-40.png
    128 KB · Views: 8
Billybreg said:
Yes wen i select resume ubuntu start normaly but wen i restart dont work. In recovery mode i select eaven the restore grub but nothing change.
Click to expand...

'Yes wen i select resume ubuntu start normaly but wen i restart dont work': This is current 'normal' behaviour and as expected given the latest kernels and the (faulty) BIOS. When you 'restart' you have to again go through the recovery option to restart successfully.

'i select eaven the restore grub but nothing change': Nothing should change as this is not a GRUB issue. It is a kernel issue so reinstalling GRUB will have no effect.

Billybreg said:
marco@NEO-Z83-4:~$ ls fso
ls: impossibile accedere a 'fso': File o directory non esistente
marco@NEO-Z83-4:~$ ls fs0:
ls: impossibile accedere a 'fs0:': File o directory non esistente
marco@NEO-Z83-4:~$ ls fs0:\efi
ls: impossibile accedere a 'fs0:efi': File o directory non esistente
marco@NEO-Z83-4:~$ ls fs0:\efi\ubuntu
ls: impossibile accedere a 'fs0:efiubuntu': File o directory non esistente
marco@NEO-Z83-4:~$ ls fs0:\efi\boot
ls: impossibile accedere a 'fs0:efiboot': File o directory non esistente
marco@NEO-Z83-4:~$
Unable to access file or directory that does not exist
Click to expand...

You were meant to perform these commands in the UEFI: Built-in EFI Shell at the 'Shell>' prompt as per the picture you first posted. Instead you ran them in the Ubuntu shell so this is the reason they failed. It is probably why the original command 'fs0:\efi\ubuntu\grubx64.efi' also failed as this should not be run in the Ubuntu shell. Therefore if you find yourself in the same situation as the first picture then run 'fs0:\efi\ubuntu\grubx64.efi' to boot GRUB and use the recovery option as described above to boot Ubuntu.

Billybreg said:
In recovery mode i try to restore grub and and the result was:
File or directory not exist and look the attachment
Click to expand...

To recap this is a kernel problem and not a GRUB problem. Don't keep trying to reinstall GRUB as you could eventually break something. Boot (and reboot) Ubuntu by going through the previously described 'recovery' option and keep your kernel up to date by using 'apt upgrade' because soon the problem will be fixed. I will post kernel progress updates on https://theminixforum.com/index.php...untu-issues-on-minix-neo-z83-4-mini-pcs.1787/ for you to know when the (kernel) HDMI issue will be fixed in Ubuntu.

Edited: s/known/know/
 
Hello guys
I'm sorry but I'm back to windows.
When it is solved I will install Ubuntu again.
The only thing now is how to prevent windows 10 from making updates and above all preventing upgrades since I only have 27 Gb left of space in C:
Thanks
 
You must log in or register to reply here.
Back
Top