LinuxQuestions.org
Latest LQ Deal: Complete CCNA, CCNP & Red Hat Certification Training Bundle
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 12-05-2017, 12:44 PM   #1
Jeebizz
Senior Member
 
Registered: May 2004
Distribution: Slackware 14.2 64-bit with multilib
Posts: 2,411

Rep: Reputation: 639Reputation: 639Reputation: 639Reputation: 639Reputation: 639Reputation: 639
Question Slackware EFI in Virtualbox


I still cannot get passed the Grub menu when trying to mess with EFI in VirtualBox. I guess maybe it is no longer VirtualBox's problem. So is there any way around this? Maybe Current has updated Grub perhaps?

Click image for larger version

Name:	VirtualBox_Slackware Linux_05_12_2017_11_40_14.png
Views:	15
Size:	2.7 KB
ID:	26479

As you can see I am not even presented with a proper menu, it just freezes there. Latest stable VirtualBox Version 5.2.2 r119230
 
Old 12-05-2017, 12:58 PM   #2
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 1,318

Rep: Reputation: 3709Reputation: 3709Reputation: 3709Reputation: 3709Reputation: 3709Reputation: 3709Reputation: 3709Reputation: 3709Reputation: 3709Reputation: 3709Reputation: 3709
I have a report here that someone ran into the same issue and fixed it by changing the module list in make-grub.sh to these modules:

Code:
part_gpt part_msdos ext2 fat iso9660 linux boot configfile normal reboot halt search search_fs_file search_label gzio echo font cat help ls lsmod loadenv bitmap_scale test all_video
And using the script to regenerate replacements for bootx64.efi and efiboot.img. I just got the report a few days ago and haven't had a chance to test it out here yet, but it's on the TODO list. I did notice that "lsmod" doesn't seem to be a valid GRUB module, and I'm also not convinced that the module list should need to be reduced by that much.

Just in case it's helpful...
 
Old 12-05-2017, 01:01 PM   #3
Jeebizz
Senior Member
 
Registered: May 2004
Distribution: Slackware 14.2 64-bit with multilib
Posts: 2,411

Original Poster
Rep: Reputation: 639Reputation: 639Reputation: 639Reputation: 639Reputation: 639Reputation: 639
Quote:
Originally Posted by volkerdi View Post
I have a report here that someone ran into the same issue and fixed it by changing the module list in make-grub.sh to these modules:

Code:
part_gpt part_msdos ext2 fat iso9660 linux boot configfile normal reboot halt search search_fs_file search_label gzio echo font cat help ls lsmod loadenv bitmap_scale test all_video
And using the script to regenerate replacements for bootx64.efi and efiboot.img. I just got the report a few days ago and haven't had a chance to test it out here yet, but it's on the TODO list. I did notice that "lsmod" doesn't seem to be a valid GRUB module, and I'm also not convinced that the module list should need to be reduced by that much.

Just in case it's helpful...
This is a really really stupid question on my part - I would have to do that in the virtualbox shell BEFORE it even tries to boot Slackware right? Because I can't do anything as soon as that menu hits.

And yea, I just answered my own question in Slackware being at fault. I have no problem with Devuan booting in EFI mode in Virtualbox.

Click image for larger version

Name:	VirtualBox_Devuan_05_12_2017_11_58_17.png
Views:	14
Size:	29.0 KB
ID:	26480
Click image for larger version

Name:	VirtualBox_Devuan_05_12_2017_11_58_29.png
Views:	15
Size:	49.0 KB
ID:	26481
 
Old 12-05-2017, 01:10 PM   #4
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 1,318

Rep: Reputation: 3709Reputation: 3709Reputation: 3709Reputation: 3709Reputation: 3709Reputation: 3709Reputation: 3709Reputation: 3709Reputation: 3709Reputation: 3709Reputation: 3709
Quote:
Originally Posted by Jeebizz View Post
This is a really really stupid question on my part - I would have to do that in the virtualbox shell BEFORE it even tries to boot Slackware right? Because I can't do anything as soon as that menu hits.
Actually, you'd have to rebuild those files and then regenerate the whole ISO first.
 
1 members found this post helpful.
Old 12-05-2017, 04:17 PM   #5
Jeebizz
Senior Member
 
Registered: May 2004
Distribution: Slackware 14.2 64-bit with multilib
Posts: 2,411

Original Poster
Rep: Reputation: 639Reputation: 639Reputation: 639Reputation: 639Reputation: 639Reputation: 639
Technically the issue is resolved, just not sure where I fscked up?

Click image for larger version

Name:	VirtualBox_Slackware Linux_05_12_2017_15_12_42.png
Views:	15
Size:	4.5 KB
ID:	26482

I copy/pasted the command EXACTLY into make-grub.sh and rebuilt.

Code:
# First, build bootx64.efi, which will be installed here in /EFI/BOOT:
grub-mkimage --format=x86_64-efi --output=bootx64.efi --config=grub-embedded.cfg --compression=xz --prefix=/EFI/BOOT 
part_gpt part_msdos ext2 fat iso9660 linux boot configfile normal reboot halt search search_fs_file search_label gzio echo font cat help ls lsmod loadenv bitmap_scale test all_video
regexp minicmd reboot halt search search_fs_file search_fs_uuid search_label gfxterm gfxmenu efi_gop efi_uga all_video loadbios gzio echo true probe loadenv bitmap_scale font cat help ls png jpeg tga test at_keyboard usb_keyboard
 
Old 12-05-2017, 04:30 PM   #6
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2 on Lenovo Thinkpad W520
Posts: 7,867

Rep: Reputation: 2780Reputation: 2780Reputation: 2780Reputation: 2780Reputation: 2780Reputation: 2780Reputation: 2780Reputation: 2780Reputation: 2780Reputation: 2780Reputation: 2780
All arguments of grub-mkimage should be on the same line.You can split in several lines but then all lines but the last one should end with a backslash.

This is true for all shell commands.
 
Old 12-05-2017, 08:19 PM   #7
Jeebizz
Senior Member
 
Registered: May 2004
Distribution: Slackware 14.2 64-bit with multilib
Posts: 2,411

Original Poster
Rep: Reputation: 639Reputation: 639Reputation: 639Reputation: 639Reputation: 639Reputation: 639
Well I can't figure out what I am doing wrong with creating the iso
Code:
root@slackmachine:/home/slackuser/slackeware64-current# xorriso -as mkisofs -iso-level 3 -full-iso9660-filenames -R -J -A "Slackware Install" -hide-rr-moved -v -d -N -eltorito-boot isolinux/isolinux.bin -eltorito-catalog isolinux/boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table -isohybrid-mbr /usr/share/syslinux/isohdpfx.bin -eltorito-alt-boot -e isolinux/efiboot.img-no-emul-boot -isohybrid-gpt-basdat -m 'source' -volid "SlackDVD" -output /tmp/slackware-dvd.iso 
xorriso 1.4.6 : RockRidge filesystem manipulator, libburnia project.

Drive current: -outdev 'stdio:/tmp/slackware-dvd.iso'
Media current: stdio file, overwriteable
Media status : is blank
Media summary: 0 sessions, 0 data blocks, 0 data, 55.4g free
xorriso : WARNING : -volid text does not comply to ISO 9660 / ECMA 119 rules
xorriso : FAILURE : Cannot find in ISO image: -boot_image ... bin_path='/isolinux/isolinux.bin'
xorriso : aborting : -abort_on 'FAILURE' encountered 'FAILURE'
Per the readme in isolinux I just have to be in the top level directory which I am..
Code:
slackuser@slackmachine:~/slackeware64-current$ ls
ANNOUNCE.14_2          COPYING            ChangeLog.txt  PACKAGES.TXT      README_LVM.TXT   SPEAKUP_DOCS.TXT   extra/     patches/
CHANGES_AND_HINTS.TXT  COPYING3           EFI/           README.TXT        README_RAID.TXT  SPEAK_INSTALL.TXT  isolinux/  slackware64/
CHECKSUMS.md5          COPYRIGHT.TXT      FILELIST.TXT   README.initrd     README_UEFI.TXT  Slackware-HOWTO    kernels/   testing/
CHECKSUMS.md5.asc      CRYPTO_NOTICE.TXT  GPG-KEY        README_CRYPT.TXT  RELEASE_NOTES    UPGRADE.TXT        pasture/   usb-and-pxe-installers/
slackuser@slackmachine:~/slackeware64-current$
-edit

I also noticed something weird - when I rebuild - I just get an empty bootx64.efi file ,

Code:
1440+0 records in
1440+0 records out
1474560 bytes (1.5 MB, 1.4 MiB) copied, 0.00491771 s, 300 MB/s
mkfs.fat 3.0.28 (2015-05-16)

Done building /EFI/BOOT/bootx64.efi and /isolinux/efiboot.img.
root@slackmachine:/home/slackuser/slackeware64-current/EFI/BOOT# ls
bootx64.efi  grub-embedded.cfg	grub.cfg  huge.s  initrd.img  make-grub.sh  osdetect.cfg  tools.cfg
root@slackmachine:/home/slackuser/slackeware64-current/EFI/BOOT# file bootx64.efi 
bootx64.efi: empty

Last edited by Jeebizz; 12-05-2017 at 08:56 PM.
 
Old 12-05-2017, 08:44 PM   #8
bassmadrigal
Senior Member
 
Registered: Nov 2003
Location: Newport News, VA
Distribution: Slackware
Posts: 4,544

Rep: Reputation: 2494Reputation: 2494Reputation: 2494Reputation: 2494Reputation: 2494Reputation: 2494Reputation: 2494Reputation: 2494Reputation: 2494Reputation: 2494Reputation: 2494
Based on the error, it can't find /isolinux/isolinux.bin. Noticed that first slash. So it looks like it is looking at the root of your filesystem. I wonder if you could change it to ./isolinux/isolinux.bin in the command to have it look in the current directory. You might need to do it with any other files referenced in that command.
 
Old 12-05-2017, 08:57 PM   #9
Jeebizz
Senior Member
 
Registered: May 2004
Distribution: Slackware 14.2 64-bit with multilib
Posts: 2,411

Original Poster
Rep: Reputation: 639Reputation: 639Reputation: 639Reputation: 639Reputation: 639Reputation: 639
Quote:
Originally Posted by bassmadrigal View Post
Based on the error, it can't find /isolinux/isolinux.bin. Noticed that first slash. So it looks like it is looking at the root of your filesystem. I wonder if you could change it to ./isolinux/isolinux.bin in the command to have it look in the current directory. You might need to do it with any other files referenced in that command.
Same error with or without the slash , plus this still does not answer why bootx64.efi is now empty
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] fedora 25 virtualbox guest efi mtdew3q Fedora 2 03-26-2017 07:58 PM
[Suggestion] Register /EFI/Slackware for use by Slackware Linux, Inc. Didier Spaier Slackware 2 11-21-2015 01:59 AM
[SOLVED] Can't find /boot/efi/EFI/Slackware/vmlinuz kernel configuration ironQiu Slackware 4 02-09-2015 07:21 AM
Tip. Want to install 64-current through VirtualBox with EFI ? Use a 64 bit host. Didier Spaier Slackware 1 05-31-2013 02:27 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 08:24 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration