Users online right now: 55 - Login  » search  » forum index  

Booting slax 7 on a mac

wrote 3 years ago

Ok so I'm trying to boot slax 7 on a mac from a usb. I'm using rEFI and the drive boots that fine. It recognizes that slax is on the drive (in another partition) and it attempts to boot it, but the fails with an error message saying "put in a boot-able disk."

I believe the issue is that rEFI from what I can tell is looking for a lilo or grub boot loader, and slax 7 uses syslinux.

I want to know how to use a different boot loader (lilo should be fine) to boot slax, or what changes I should make to the rEFI config file to allow it to recognize syslinux. I'll post the rEFI config file.

This would be a great way to make a usb version of slax universally boot-able as the rEFI only takes up a very small partition and slax still boots fine on my regular PC.
wrote 3 years ago

here's the rEFI config file contents:

# refit.conf
# Configuration file for the rEFIt boot menu

# Timeout in seconds for the main menu screen. Setting the timeout to 0
# disables automatic booting (i.e., no timeout).
timeout 20

# Disable menu options for increased security. These are intended for a lab
# environment where the administrator doesn't want users to mess with the
# operating system. List the names for the options you want to hide from
# the boot menu. Currently supported:
# shell - remove the EFI shell
# tools - remove all EFI tools (shell and gptsync)
# optical - no booting from optical drives
# external - no booting from external disks or USB flash drives
# internal - no booting from internal disks; this setting is not
# recommended because it locks you out of all operating
# systems installed on the internal hard disks.
# singleuser - remove the submenu options to boot Mac OS X in single-user
# or verbose modes
# hwtest - remove the submenu option to run Apple Hardware Test
# all - all of the above, except for 'internal'
#disable external optical shell singleuser
#disable all

# Note: The 'disableopticalboot' and 'disableexternalboot' options from
# Charles Ahn's patch are also supported for compatibility. They are
# equivalent to 'disable optical' and 'disable external', respectively.

# Use a custom title banner instead of the rEFIt icon and name. The file
# path is relative to the directory where refit.efi is located. The color
# in the top left corner of the image is used as the background color
# for the menu screens. Currently uncompressed BMP images with color
# depths of 24, 8, 4 or 1 bits are supported.
#banner hostname.bmp

# Custom images for the selection background. There is a big one (144 x 144)
# for the OS icons, and a small one (64 x 64) for the function icons in the
# second row. If only a small image is given, that one is also used for
# the big icons by stretching it in the middle. If only a big one is given,
# the built-in default will be used for the small icons.
# Like the banner option above, these options take a filename of
# an uncompressed BMP image file.
#selection_big selection-big.bmp
#selection_small selection-small.bmp

# Hide the volume badge icons in the graphical main menu. There are three
# settings:
# none - show all volume badges (default)
# internal - hide badges on internal disk volumes only, allowing you to
# distinguish CDs and occasionally connected external disks
# all - never show volume badges (not recommended)
#hidebadges internal

# Hide various user interface elements. Here you can list the names of
# interface elements to hide. Currently supported:
# banner - the rEFIt title banner
# shell - the EFI shell icon
# tools - all EFI tools (shell and gptsync)
# funcs - built-in functions (about, restart)
# ('tools' and 'funcs' together hide the complete second row of icons.)
# label - text label in the menu
# hdbadges - volume badges for internal disk volumes (same as
# 'hidebadges internal')
# badges - all volume badges (same as 'hidebadges all'); this setting
# is not recommended because it won't let you distinguish
# installed OSes and bootable CDs/DVDs.
# all - all of the above, except for 'badges'
# Note: The 'shell' and 'tools' options are equivalent to the 'disable'
# options with the same names.
#hideui tools funcs hdbadges
#hideui all

# Use text mode only. When enabled, this option forces rEFIt into text mode.

# List legacy options first. When enabled, legacy BIOS based boot options
# (e.g. Windows, Linux via LILO or GRUB) will be listed first. This is
# intended as a quick fix to change the default boot choice until full
# configurability arrives.

# Set the default menu selection. The available arguments match the
# keyboard accelerators available within rEFIt. You may select the default
# loader using a one-character abbreviation for the OS name ("M" = Mac OS X,
# "L" = Linux, "W" = Windows). You may also specify a digit between 1 and
# 9, in which case the Nth loader in the menu will be the default. You can
# also select a rEFIt tool entry ("S" = EFI Shell, "P" = Partitioning Tool,
# "U" = shutdown). This is intended as a quick fix to change the default
# boot choice until full configurability arrives.
#default_selection L

wrote 3 years ago

ok, after some more research I think I know what the problem is. I think the reason rEFI can't boot slax (or porteus, I tried it too) is because it looks for a boot loader at the root of the volume. I think if I put the boot loader at the root, then rEFI could initialize it.

SO, I need help doing this with two things kept in mind. I want to be able to boot on a regular machine as well as a mac. I don't mind having to go through another menu. The other thing to keep in mind is I am basically a linux novice. I've been learning, but don't expect too much from me.

Please if I can get this to work it will be a BIG breakthrough and VERY helpful. Thank you
wrote 3 years ago

Hi, Sorry for my bad english, I will try to explain me.... I wanna to boot a WifiSlax SO from my usb stick, in a old 2008 macbook, I have refit system installed on my mac, and I found a method that use a file in the usb called "bootX64.efi" that helps to refit to launch a linux, more precisely an ubuntu distribution, and works greatly with ubuntu but don't with slax base system (WifiSlax). My sugestion is that if we could modify the "bootX64" file to launch correctly an slax system, so we could find a nice solution for this, the problem is that I has been searching the sourcecode or some documentation for this.... but is so hard. I hope that someone give us a clue.
wrote 3 years ago

I have heard of wifislax (from distrowatch) but have never download it.
Notwitstanding it's name , does it even use slax Tomas (slax creator) linux live script ?.

In Distrowtatch it is stated as been based on slackware.

To my knowledge , the wifislax creator never posted or at least never identify himself /herselr or them as wifislax creator in slax's forum.

So you could be asking in a totaly wrong forum , if wifislax ie the "slax" in their name is incidental (meaning it has nothing to do with slax but may come from slackware).

  » search  » forum index  

Post your reply

Your name (Login):


These HTML tags are allowed: <quote>, <b>, <u>, <i>, <pre>, <code>, <small>, <h1>, <h2>, <h3>, <li>

Slax is generously supported by: P&P Software GmbH and wisol technologie GmbH