Tag Archives: EFI-X.com

[MacOS] Chameleon On USB: Mounting USB Stick Correctly

Leave a reply

Inserting USB sticks to your Mac OS X based system makes Mac OS X mount the stick without assigning certain permissions like owners, or groups.

I. How things get mounted on Mac OS

The mount command on the terminal returns most likely some lines, like that:

  • testuser$ mount
  • /dev/disk0s2 on / (hfs, local, journaled)
    devfs on /dev (devfs, local, nobrowse)
    map -hosts on /net (autofs, nosuid, automounted, nobrowse)
    map auto_home on /home (autofs, automounted, nobrowse)
    /dev/disk3s1 on /Volumes/CHAMBOOT (hfs, local, nodev, nosuid, journaled, noowners)
    /dev/disk1s4 on /Volumes/Mac OS X Install DVD (hfs, local, nodev, nosuid, noowners)

You can see quite a lot of slices (i.e. ~partitions) are mounted to that system I am running here. For instance disk1s4 is the forth slice of disk1 and it countains an image of a Mac OS X Install DVD. And you can see a CHAMBOOT named drive mounted with several options.

II. Mount Options/Permissions

Our beloved USB stick named CHAMBOOT (contains Chameleon and) is disk3s1 and is mounted to /Volumes/CHAMBOOT. Mac OS handles USB mounting for most of our every day life operations fairly reliable. But this comes at a cost, as this simplicity is achieved here by applying options like nosuid and noowners during the mount process.

For people willing to run Chameleon from a USB stick permissions are inevitable, as for instance an Extensions.mkext kextcache can only be generated with proper file permissions being set.

II. Mounting USB with permissions

This just requires some simple mount operations being performed manually on the terminal. Do the following:

  • testuser$ sudo -s
    Become ultimate root now.
  • testuser$ cd
    Get back to the home folder whereever you’ve been before.
  • testuser$ sync
    Force completion of pending disk writes.
  • testuser$ umount -f /Volumes/CHAMBOOT
    This unmounts the USB stick called CHAMBOOT
  • testuser$ mkdir chamboottemp
    Create a temporary folder for our mounting session
  • testuser$ mount_hfs /dev/disk3s1 chamboottemp/
    Mount the USB stick to the temporary folder
  • testuser$ mount
    See how the drives are mounted now
  • /dev/disk0s2 on / (hfs, local, journaled)
    devfs on /dev (devfs, local, nobrowse)
    map -hosts on /net (autofs, nosuid, automounted, nobrowse)
    map auto_home on /home (autofs, automounted, nobrowse)
    /dev/disk3s1 on /Users/admin/chamboottemp (hfs, local, journaled)
    /dev/disk1s4 on /Volumes/Mac OS X Install DVD (hfs, local, nodev, nosuid, noowners)    You can see the USB stick is now mounted without “extra” options.

Now you can apply changes to the USB stick’s files in the proper manner (like copying files, repairing permissions and creating a kextcache). After having performed all the changes, you can correctly unmount. Read here:

III. Manually Unmounting

  • testuser$ cd
    Get back to the home folder whereever you’ve been before.
  • testuser$ umount -f chamboottemp
    Force to unmount the device mounted to the chamboottemp folder now.
  • testuser$ rmdir chamboottemp
    It is safe to delete the chamboottemp folder now.

IV. Links

» Mac OS X Reference Library: Man Page for “sync”…
» Mac OS X Reference Library: Man Page for “mount”…
» AsereBln.BlogSpot.com: Some terminal work…

[MacOS] Save your Data after EFI-X Crash

12 Replies

I. Abstract

Imagine the following situation. You are very keen on this EFI-X device that’s now on sale. So you order a testing device. Some days later the device arrives from Taiwan. Your EFI-X compliant system already kept waiting with a blank SATA 250GB on a Gigabyte EP35-DS3.

After having plugged the EFI-X module to your system, you install MacOS on your PC. It’s really worth the bunch of money since EFI-X lets MacOS boot like a charm. Easy and nice to handle for everyone who is not more willing to hack device drivers into their Hackintoshs. But as a tinkerer who wants to see how it works in real life and so you decide to apply the newest update for your EFI-X module. Since you’re a Mac user you decide to use the MacOS tool provided by the EFI-X team.

All works well during update, until you do the reboot. All of a sudden the intro boot screen of EFI-X looks quite garbled (like the screen below). You wonder what might have happened and do a reboot. As it doesn’t help you plug your EFI-X to another computer hoping you may be able to flash it again using Windows XP. But after all the installation argy-bargy with EFI-X’ virtual device driver under Windows XP – the update tool tells you, you are running the current version.

efi-x-crash_ep35_03_bootscreen_garbled.jpg

efi-x-crash_ep35_02_osx_startup.jpg

To make a long story short. EFI-X has customer service and they will exchange their defective units. You may also have a look at the EFi-X Bug Hunt forums for further assistence (please don’t link our article from EFI-X Bug Hunt forums, they will remove it and may ban you – don’t say we didn’t warn ya ;-) Anyway if you need to have access to your data until the RMA unit arrives, we prepped the following article. We’re going to show you how to make your system bootable after the EFI-X device broke for whatever reason.

A short remark before we start: this article is partly based on a HowTo by a guy going by the nick Menoob. We shamelessly stole the method of installing retail Leopards on PCs and adapted it a tiny bit for this EFI-X specific case. Anyway: all the shouts fly out to him.

II. What you need

  • 30 minutes of your precious life time – you may use this time to think about why you didn’t buy a real Mac
  • a Boot-132 disk – it contains your MacOS compatible bootloader (find a list of Boot-132.iso’s for different mainboards and chipsets here – in case you don’t know you should always give the generic.iso a try) – Kudos to Sonotone/Hackint0sh forums!
  • burn the Boot-132 onto a blank CD-R or CD-RW

III. Prepping your hardware

  1. remove the defective EFI-X device and if you feel you don’t need it, send it to the CCC for further examination
  2. let only the MacOS drive and the CD/DVD drive plugged, unplug all other drives from your motherboard
  3. start your computer and hit DEL key to go into your BIOS
  4. inside of your BIOS: set the MacOS harddrive as first boot device and enable AHCI mode for SATA drives – your drives will appear orange/yellow in MacOS, don’t worry about that
  5. save the BIOS changes and reboot
    efi-x-crash_ep35_01_bios.jpg

IV. Booting your system

  1. turn on your computer
  2. insert the just burnt Boot-132 CD-R into CD/DVD drive
  3. during BIOS startup hit the F12 key to manually choose your boot device (applies to Gigabyte boards only!!!)
  4. Choose to boot your CD/DVD drive
  5. Your screen will show that ISOLINUX 3.6x is prepping to boot the Multiboot loader
  6. since this ISOLINUX bootloader is not too user-friendly ;-) you will find yourself with a screen similar to this.
    efix-crash_ep35_04_slimbuild_preboot1.jpg
  7. Hit the F8 Key. You’re gonna see this:
    efix-crash_ep35_04_slimbuild_preboot2.jpg
  8. Hit the ESC Key. and You’re gonna be welcomed with this screen.
    efix-crash_ep35_04_slimbuild_preboot3.jpg
  9. Now enter 80 and hit return, if the name of your MacOS harddrive shows up, 80 was the right number, if it does not show up, give 81 a try and so on.
  10. Once you’ve found your MacOS harddrive, the bootloader will require again some parameters. Simply enter -v -x as parameters and hit return (you may find more infos about these Darwin boot parameters here)
    efix-crash_ep35_04_slimbuild_preboot5.jpg
  11. if you experience the “still waiting for root device” issue, just reset your system and play with the AHCI mode for SATA inside of your BIOS
  12. Anyway: booting will take a long while – in our case about 5 minutes until the login screen appears
  13. login into your system

V. Saving your data

  1. Examine which data you require from your formerly known as almost native system
  2. plug your external harddrive (if you plan to migrate data to Windows, better have the external drive FAT32 formatted)
  3. Copy the files

VI. Final Words

Ooop duh. You got some more options here that we cannot cover at this time:

  1. You may revive this system with the hackint0sh ingredients (dsmos.kext and kexts for audio and video cards) – this will be a longer journey
  2. You may also get a real Mac. In this case Apple will suddenly love you…
  3. We recommend to give also Microsoft’s Vista a try. We feel like Vista Aero Glass effects are currently superior to Leopard’s effects. In this case Microsoft will love you (and us for suggesting this)…
  4. You could also go up the hill to the end and find Debian and ask yourself why it took so long to understand that unix is beautiful – in this case nobody will really love you but during installation you’ll find plenty of new friends in the Ubuntu community explaining you Debian…
  5. :-)

Anyway we hope that article helped you a tiny bit. If so you may also consider our sponsors, they also help you (and us of course)…

[MacOS] EFI-X.com releases compatibility list

7 Replies

Update jan 01, 2009: EFI software solution called EPOS available for free…
Update june 26, 2008: read latest news about EFI-X here…

We yet reported the rumors about an EFI emulator being put into a USB boot device (read here). The project is called EFI-X.com and the guys behind announced to open their shop tomorrow. Anyway they updated their website already and released some more details about “their” products. Though there are no information about pricing yet.

EFiX seem to start with two products (see here)

EFiX USB V1

  • EFiX interactive system boot selector
  • allows to install MacOS X from retail DVD (and online updates)
  • installed into internal USB (this is quite vague still)

EFiX USB Deluxe / Sound

  • EFiX interactive system boot selector
  • allows to install MacOS X from retail DVD (and online updates)
  • includes USB Soundcard
  • USB Hub
  • installed into internal USB (this is quite vague still)

Supported Hardware (see here)

EFI-X supports the following CPUs:

  • Intel Core 2 Extreme
  • Intel Core 2 Quad
  • Intel Core 2 Duo
  • Intel Pentium dual-core (E2xx0)
  • Intel Celeron dual-core (E1200)
  • Intel Celeron (420, 430, 440)
  • Intel Multi Core CPU

and graphic adapters using these chipsets:

  • nVidia Geforce 7300 GS / GT
  • nVidia Geforce 7600 GT
  • nVidia Geforce 7800 GT / GTX
  • nVidia Geforce 7900 GS / GT
  • nVidia Geforce 7950 GT
  • nVidia Geforce 8600 GTS / GT
  • nVidia Geforce 8800 GS / GT / GTS / GTX / Ultra
  • nVidia Quattro FX 5600
  • ATI Radeon 2600 XT
  • ATI Radeon HD 3870

and these motherboards:

  • Gigabyte GA-P35-DS3P (rev. 2.0)
  • Gigabyte GA-EP35-DS3P (rev. 2.1)
  • Gigabyte GA P35-DS3R
  • Gigabyte GA P35-DS3L

What (we) the people think

Many endusers will welcome this product. Endusers won’t need to download illegal distributions of adjusted and custom hacked/packed install DVDs (like Kalyway or iAtkos). People who where following the Brazil-Mac’s way will also like it. It simply seems to make the installation of MacOS X on whitebox PCs hassle-free, because we all will be able to use original retail DVDs. People will tend to buy those DVDs rather than just downloading from dark torrent sites. This is a strong position to like this product. Apple might like it aswell since it may help their propable guerilla strategy to silently undercut the PC market.

Anyway in the meantime several things have been mentioned that might detain people from buying it. First being the question of the legal status of EFiX. There has been a strong dispute about if EFI-X is legal or if it might contain parts of code that have been released under Apple’s open source license (like Dave Elliot’s Darwin Bootloader or the EFI emulaton Chameleon), which would require to release the source code of EFi-X as open source aswell. Second being something we’re gonna tell when we got enuff information…

[MacOS] Boot native MacOS X with EFI-X USB Dongle

6 Replies

Update 26.06.2008: Read latest news about EFI-X here…
Update 22.06.2008: Read latest news about EFI-X here…

The newest on the market is announced to be released on 23. June. It is called EFI-X and seems to be quite a revolution. Technically it is a small USB dongle that contains a bootloader. That bootloader allows booting of native MacOS X installer DVDs or yet installed MacOS X installations…

Are you yet shackling your heads? Well, we are. It is said it will support any PC hardware to run OS X. At that point we are skeptical, since even Apple themselves are not able to support any hardware… We expect this to allow seamless installation on close-to-original-mac hardware. Which means: Intel Core2Duo on MoBo’s with Intel chipset and typical ATI or NVidia graphic adapters. But anyway: the installation will become simple and easy. No more BrazilMac workarounds or illegal downloading thru torrents from darkest places on the net. More features – as far as known yet – to be found in the updates section below the video.

We are quite curious about more details but currently the project’s website doesn’t contain anything more than we just told you. Netkas provides a video that shows the bootscreen. Sadly it is of poor quality and light, but see here:

Update (14.08.08):
Rumors on forums are telling about the specifications of your PC required to allow EFiX to run MacOS X

  • Intel Core 2 Duo (not likely to support AMD)
  • Intel chipsets on MoBo’s req
  • ALC889A or ALC885 audio chipset on MoBo to work out of the box
  • USB stick needs to plugged all the time (well who cares?)

Update II (15.06.08):
Althought not finished, the website of EFI-X.com has been updated during the last few hours. It seems, the following product versions of EFi-X will be sold:

  • EFiX for desktop computers
  • EFiX for notebooks
  • EFiX PCI version
  • EFiX complete systems

That looks promising. More to come at latest on 23rd…
Update III (16.06.08)
An FAQ has been published by the EFi-X Team. It clearly states, AMD CPUs are not supported, yet – as expected…