LinuxQuestions.org
View the Most Wanted LQ Wiki articles.
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
 
LinkBack Search this Thread
Old 02-15-2013, 08:14 AM   #1
cendryon
Member
 
Registered: Aug 2005
Location: France
Distribution: Slackware64 current
Posts: 72

Rep: Reputation: 21
elilo package missing x86_64 EFI binary?


Hi

I'm really glad to see UEFI support making its way "officially" to Slackware.

Once upon a time, I set it up manually with refind, elilo and UEFI shell on my ASUS mainboard, following ArchLinux UEFI wiki page.

Now I wanted to take the fresh elilo from -current as the foundation of my UEFI setup, and it did not work.

I looked into it and it occurred to me that only IA32 and IA64 EFI binaries are presents, while x86_64 EFI is the one needed.

Upon further readings, the elilo binary must match the "UEFI BIOS" bit width, which has nothing to do with kernel bit width:
  • IA64 is for Itanium-based systems
  • IA32 is for 32bits EFI systems, which became uncommon nowadays
  • x86_64 is for 64bits UEFI systems, whether you run Slackware 32bits or Slackware64

Hope it helps

Cheers
 
Old 02-15-2013, 10:15 AM   #2
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: SlackwareŽ
Posts: 10,882
Blog Entries: 1

Rep: Reputation: 1307Reputation: 1307Reputation: 1307Reputation: 1307Reputation: 1307Reputation: 1307Reputation: 1307Reputation: 1307Reputation: 1307Reputation: 1307
Member Response

Hi,

Look at: Slackware on UEFI for some very useful information.
 
Old 02-16-2013, 01:57 AM   #3
cendryon
Member
 
Registered: Aug 2005
Location: France
Distribution: Slackware64 current
Posts: 72

Original Poster
Rep: Reputation: 21
I put my elilo.conf in /boot and rEFInd nicely picked up /boot/elilo-x86_64.efi to boot my Slackware.
Thanks Pat!

Code:
prompt
timeout=50
default=slackware64
append=" vt.default_utf8=1"

image=vmlinuz
  label=slackware64
  description="Slackware64"
  append=" initrd=initrd.gz root=/dev/rafalevg/root splash showopts load_ramdisk=1 prompt_ramdisk=0 ro printk.time=0 vga=0x34d irqpoll"
  initrd=initrd.gz
  read-only

image=recovery64/huge.s
  label=recovery64
  description="Slackware64 recovery (install img)"
  append=" initrd=recovery64/initrd.img load_ramdisk=1 prompt_ramdisk=0 rw printk.time=0 SLACK_KERNEL=huge.s vga=ext kbd=fr-latin1 nic=auto:eth0:dhcp"
  initrd=recovery64/initrd.img
rEFInd can read ext2 and ext4 partitions with its EFI drivers, even if it's RAID1.
Then initrd does all the work for / on RAID, LUKS and LVM.

The recovery entry comes from SlackDoc (either Setting up a Recovery Boot Option or Booting the Installation Environment from HDD), with extra for keyboard and network from AlienBob.
Beware memtest that can't be run this way.

Cheers
 
Old 02-16-2013, 08:51 AM   #4
AlleyTrotter
Member
 
Registered: Jun 2002
Location: Coal Township PA
Distribution: Slackware64-14.1 (3.14.0) UEFI enabled
Posts: 344

Rep: Reputation: 71
Was the "missing /boot/elilo-x86_64.efi" already in /boot? or did you do something extra to install it there?
Maybe the better question would be where did the Slackware package install the elilo-x86_64.efi binary?
I guess I am missing something here.
Thanks
john
 
Old 02-16-2013, 08:54 AM   #5
fskmh
Member
 
Registered: Jun 2002
Location: South Africa
Distribution: Slackware64-current multilib
Posts: 225

Rep: Reputation: 52
Pat's rev 3 of elilo-3.14 contains the x86_64 efi and the ia32 efi. Rev 2 contained the ia64 and ia32 efi-s.

Quote:
Fri Feb 15 22:46:52 UTC 2013
a/elilo-3.14-x86_64-3.txz: Rebuilt.
Include the x64 bootloader, not the Itanium one. Thanks to cendryon.
We're also keeping the ia32 version, even though 32-bit UEFI is
practically unknown. There might be some 32-bit EFI implementations
out there, so it doesn't hurt to have it.
 
Old 02-16-2013, 09:38 AM   #6
AlleyTrotter
Member
 
Registered: Jun 2002
Location: Coal Township PA
Distribution: Slackware64-14.1 (3.14.0) UEFI enabled
Posts: 344

Rep: Reputation: 71
Thanks for the clarification.
Just did an explodepkg also to see where it gets installed. So it seems that /boot will now be an efi partition.
Not really a new question as I will shortly be installing current on a spare drive to see where things are going for (my bet) slackware 15

Thanks
john
 
Old 02-16-2013, 07:31 PM   #7
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 836

Rep: Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620
Quote:
Originally Posted by AlleyTrotter View Post
Thanks for the clarification.
Just did an explodepkg also to see where it gets installed. So it seems that /boot will now be an efi partition.
That's unlikely. I was just looking for an obvious place to keep the binaries.

In many cases a machine will already have an EFI partition for use by Windows, and more than likely there will be enough extra space there to create a directory \efi\slackware to keep our files in. Otherwise, the user will probably have to make one with cgdisk before running setup. It would make sense for setup to warn the user about that if it finds no existing EFI partition on a machine using UEFI, too.

I'd rather stay away from trying to modify the machine's UEFI boot menu automatically in any way, so there will be extra steps that will need to be done, especially when setting up to dual boot.

Anyway, we're not really at the point where those things can be implemented yet. The next step is getting the installer bootable from UEFI, and this could be pretty tricky. Beyond the issues with just getting it to load (will an image load from a USB stick larger than the image? Is it possible to boot a disc conforming to the ISO9660 standards?), it appears the installer will need to support KMS for text output to work. That might end up resulting in that lovely tiny text for all installs, not just the UEFI ones. Passing a video= kernel option can't really be done by default since we don't know the native screen resolution up front. And I'm sure there are plenty more hurdles ahead.
 
1 members found this post helpful.
  


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
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
EFI main GPT overwritten everytime (when windows 7 runs) - structure of EFI masuch Linux - Newbie 2 07-20-2012 02:49 PM
[SOLVED] x86 binary file not work on x86_64 mahmoodn Ubuntu 3 10-25-2010 03:03 AM
binary kernel package == source package ? narc Ubuntu 4 07-29-2007 09:28 AM
How to check if a package(eg. gdebi)will be available in 'Etch' as binary package? Akhran Debian 4 08-28-2006 11:53 AM
Need FC2 x86_64 binary RPM of unison BobBuchanan Linux - Software 0 02-15-2005 08:00 PM


All times are GMT -5. The time now is 04:40 AM.

Main Menu
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
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration