Jump to content

How do you guys review your kexts on your EFI partition?


  • Please log in to reply
25 replies to this topic

#1
iCF-74 ToughMac

iCF-74 ToughMac

    InsanelyMac Protégé

  • Members
  • PipPip
  • 69 posts
  • Gender:Male
  • Location:Canada eh?
I've gotten lazy with my nicely running 10.5.6 Retail system by swapping kexts in and out of my extensions folder tweaking things into submission. What I guess I should be doing is tweaking the kexts in my EFI partition instead, leaving my system/library/extension folder virgin.(so future updates won't break my system)

So when you guys want to add or subtract kexts, how do you go about it?


Originally I used 'Chameleon DFE for hard disk', but I seem to remember adding other kexts after the fact once, and noticing I eventually ran out of room to add more. (In the extra folder). I probably kept the usual kexts in there, and was re-running chameleon while adding other kexts on top on the usual ones, and its as though it didn't know better than to sidestep the ones it already had installed and to just install the new ones. As a result each time I re-ran chameleon I lost a pile of available space.


Can I mount my EFI partition and review whats there and tweak the kext contents?


I hope this makes sense . . . :blink:



Joe

#2
MoonScryer

MoonScryer

    InsanelyMac Protégé

  • Members
  • Pip
  • 16 posts
I usually just drop to the Terminal and do:
sudo -s (BE CAREFUL!)

df -h (to see where the primary disk mounts - look for /) 

then: mkdir /Volumes/EFI

then: mount_hfs /dev/disk2s1 /Volumes/EFI

then I do what I need to do.

After I'm done I unmount the partition and reboot to see the effect.

The /Volumes/EFI directory is only a temporary name so it needs to be put in each time you do the work. You could make it visible and perm mounted in OSX, but I prefer the hard way.

#3
iCF-74 ToughMac

iCF-74 ToughMac

    InsanelyMac Protégé

  • Members
  • PipPip
  • 69 posts
  • Gender:Male
  • Location:Canada eh?
MoonScryer,

Nice .. thanks!

Here is what I obtained so far -

Filesystem	  Size   Used  Avail Capacity  Mounted on
/dev/disk0s2   200Gi   25Gi  174Gi	13%	/
devfs		  109Ki  109Ki	0Bi   100%	/dev
fdesc		  1.0Ki  1.0Ki	0Bi   100%	/dev
map -hosts	   0Bi	0Bi	0Bi   100%	/net
map auto_home	0Bi	0Bi	0Bi   100%	/home
/dev/disk0s3	32Gi   31Gi  1.8Gi	95%	/Volumes/MAC-DATA
/dev/disk1s1   3.9Gi  1.3Gi  2.6Gi	34%	/Volumes/FLASH_DRIVE

So does this mean I use /dev/disk0s2 ? Is that the EFI partition? It's my Leo partition @ 200Gi .. my EFI partition should be around 200mb, no?


Also, I'd like to make it permanently visible for now .. how does one go about that?


Thanks,



Joe

#4
iCF-74 ToughMac

iCF-74 ToughMac

    InsanelyMac Protégé

  • Members
  • PipPip
  • 69 posts
  • Gender:Male
  • Location:Canada eh?
I tried various mount points ... here are the results:

bash-3.2# df -h
Filesystem	  Size   Used  Avail Capacity  Mounted on
/dev/disk0s2   200Gi   28Gi  171Gi	15%	/
devfs		  114Ki  114Ki	0Bi   100%	/dev
fdesc		  1.0Ki  1.0Ki	0Bi   100%	/dev
/dev/disk0s3	32Gi   31Gi  1.8Gi	95%	/Volumes/MAC-DATA
map -hosts	   0Bi	0Bi	0Bi   100%	/net
map auto_home	0Bi	0Bi	0Bi   100%	/home
vfstool@fuse0   32Gi  3.1Gi   29Gi	10%	/private/tmp/651/C
bash-3.2# mkdir /Volumes/EFI
bash-3.2# mount_hfs /dev/disk0s1 /Volumes/EFI
mount_hfs: Invalid argument
bash-3.2# mount_hfs /dev/disk2s1 /Volumes/EFI
mount_hfs: No such file or directory
bash-3.2# mount_hfs /dev/disk0s2 /Volumes/EFI
mount_hfs: Resource busy
bash-3.2#


So I'm at a loss as to where mount the EFI partition ... :)

#5
hecker

hecker

    InsanelyMacaholic

  • Members
  • PipPipPipPipPipPipPipPipPipPipPip
  • 2,669 posts
  • Gender:Male
What you actually need is the full diskid number for you current EFI partition, which the command "df -h" does not provide.
Use
diskutil list
instead. Look for the entry that contains your current OSX main partition. Notice that that drive will also contain an EFI partition. This is the one you need to use as a parameter for you mount command. Usually it's diskXs1, so in your case it would be "disk0s1". Now you can mount it with:
sudo su
mkdir /Volumes/EFI 
mount /dev/disk0s1 /Volumes/EFI

Good luck!

#6
iCF-74 ToughMac

iCF-74 ToughMac

    InsanelyMac Protégé

  • Members
  • PipPip
  • 69 posts
  • Gender:Male
  • Location:Canada eh?
hecker,


Thanks for the input. I tried this and got an error......but at last I can see my EFI partition; to point at it anyways *L*

Any idea what went wrong here ?

/dev/disk0
   #:					   TYPE NAME					SIZE	   IDENTIFIER
   0:	  GUID_partition_scheme						*232.9 Gi   disk0
   1:						EFI						 200.0 Mi   disk0s1
   2:				  Apple_HFS iLEOPARD				200.0 Gi   disk0s2
   3:				  Apple_HFS MAC-DATA				32.4 Gi	disk0s3
ileopards-cf-74gcdadbm:~ iNTELMAC$ sudo su
Password:
sh-3.2# mkdir /Volumes/EFI
sh-3.2# mount /dev/disk0s1 /Volumes/EFI
/dev/disk0s1 on /Volumes/EFI: Incorrect super block.


Joe

#7
hecker

hecker

    InsanelyMacaholic

  • Members
  • PipPipPipPipPipPipPipPipPipPipPip
  • 2,669 posts
  • Gender:Male
Ah, sorry. My mistake.
It should be
mount_hfs /dev/disk0s1 /Volumes/EFI


#8
iCF-74 ToughMac

iCF-74 ToughMac

    InsanelyMac Protégé

  • Members
  • PipPip
  • 69 posts
  • Gender:Male
  • Location:Canada eh?
Must be me .. *L*

sh-3.2# mkdir /Volumes/EFI
sh-3.2# mount_hfs /dev/disk0s1 /Volumes/EFI
mount_hfs: Invalid argument
sh-3.2# mount_hfs /dev/disk0s1 /Volumes/EFI
mount_hfs: Invalid argument


Ok, what did I miss this time :)



Joe

#9
hecker

hecker

    InsanelyMacaholic

  • Members
  • PipPipPipPipPipPipPipPipPipPipPip
  • 2,669 posts
  • Gender:Male
Try it with sudo at the beginning.

#10
iCF-74 ToughMac

iCF-74 ToughMac

    InsanelyMac Protégé

  • Members
  • PipPip
  • 69 posts
  • Gender:Male
  • Location:Canada eh?
Sorry, I didn't copy all the code. I actually did use sudo su as suggested at the beginning, as below:

ileopards-cf-74gcdadbm:~ iNTELMAC$ sudo su
Password:
sh-3.2# diskutil list
/dev/disk0
   #:					   TYPE NAME					SIZE	   IDENTIFIER
   0:	  GUID_partition_scheme						*232.9 Gi   disk0
   1:						EFI						 200.0 Mi   disk0s1
   2:				  Apple_HFS iLEOPARD				200.0 Gi   disk0s2
   3:				  Apple_HFS MAC-DATA				32.4 Gi	disk0s3
sh-3.2# mkdir /Volumes/EFI
sh-3.2# mount_hfs /dev/disk0s1 /Volumes/EFI
mount_hfs: Invalid argument

Anything we're overlooking?


Cheers,

Joe

#11
fredouille

fredouille

    InsanelyMac Legend

  • Members
  • PipPipPipPipPipPipPipPip
  • 1,193 posts
  • Location:GROVILLE du Nord
mkdir /Volumes/EFI
mount_hfs /dev/diskXs1 /Volumes/EFI X=EFI drive)
killall Finder

if invalid argument try :
fsck_hfs /dev/disxXs1

all credits to munky and the rest

#12
iCF-74 ToughMac

iCF-74 ToughMac

    InsanelyMac Protégé

  • Members
  • PipPip
  • 69 posts
  • Gender:Male
  • Location:Canada eh?
Fred,

I did everything as before and when I got to the invalid argument, I added the code you suggested. Here is what came back:

sh-3.2# fsck_hfs /dev/disk0s1
** /dev/rdisk0s1

After that I tried mounting again, and go the same invalid argument error.



Joe

#13
fredouille

fredouille

    InsanelyMac Legend

  • Members
  • PipPipPipPipPipPipPipPip
  • 1,193 posts
  • Location:GROVILLE du Nord
you have to unmonut the partition, then reboot and try again, with all steps:
umount /Volumes/EFI (If this fails, do umount -f /Volumes/EFI).
reboot and


mkdir /Volumes/EFI
mount_hfs /dev/diskXs1 /Volumes/EFI X=EFI drive)
killall Finder

if invalid argument try :
fsck_hfs /dev/disxXs1

#14
iCF-74 ToughMac

iCF-74 ToughMac

    InsanelyMac Protégé

  • Members
  • PipPip
  • 69 posts
  • Gender:Male
  • Location:Canada eh?
When I tried to umount, it said /Volumes/EFI was not mounted, so I rebooted and did the following:

ileopards-cf-74gcdadbm:~ iNTELMAC$ sudo su
Password:
sh-3.2# mkdir /Volumes/EFI
sh-3.2# mount_hfs /dev/disk0s1 /Volumes/EFI
mount_hfs: Invalid argument
sh-3.2# 
sh-3.2# 
sh-3.2# fsck_hfs /dev/disk0s1
** /dev/rdisk0s1
sh-3.2# killall Finder
sh-3.2#


I watched as Finder disappeared off my dock...

So tried:

cd /Volumes/EFI
ls

..and got no results.


Then my Finder reappeared, but I do not see my EFI partition yet.


Hard nut to crack ..


Joe

#15
fredouille

fredouille

    InsanelyMac Legend

  • Members
  • PipPipPipPipPipPipPipPip
  • 1,193 posts
  • Location:GROVILLE du Nord
You have to do step by step on each boot because the number of the disk and partition can changes.
so

1) Open Terminal

2) sudo -s (and type in your password)

3) diskutil info / | grep Identifier - this tells you the values for diskXsY for '/', which is the currently-booted system. (If you're doing this on a disk other than the one you've booted from, you need to modify accordingly.)

4) diskutil list - diskXs1 should be called EFI. this is the hidden EFI partition on your target drive.
then the rest of the steps

#16
og-phantom

og-phantom

    InsanelyMac Geek

  • Members
  • PipPipPip
  • 153 posts
  • Gender:Male

I've gotten lazy with my nicely running 10.5.6 Retail system by swapping kexts in and out of my extensions folder tweaking things into submission. What I guess I should be doing is tweaking the kexts in my EFI partition instead, leaving my system/library/extension folder virgin.(so future updates won't break my system)

So when you guys want to add or subtract kexts, how do you go about it?
Originally I used 'Chameleon DFE for hard disk', but I seem to remember adding other kexts after the fact once, and noticing I eventually ran out of room to add more. (In the extra folder). I probably kept the usual kexts in there, and was re-running chameleon while adding other kexts on top on the usual ones, and its as though it didn't know better than to sidestep the ones it already had installed and to just install the new ones. As a result each time I re-ran chameleon I lost a pile of available space.
Can I mount my EFI partition and review whats there and tweak the kext contents?
I hope this makes sense . . . :(
Joe

here is my terminal output if it helps any;

sudo -s
Password:
bash-3.2# mkdir /Volumes/EFI
bash-3.2# diskutil list
.....
/dev/disk3
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *372.6 Gi disk3
1: EFI 200.0 Mi disk3s1
2: Apple_HFS Macintosh HD 372.3 Gi disk3s2

......
bash-3.2# mount_hfs /dev/disk3s1 /Volumes/EFI
bash-3.2# cd /Volumes/EFI
bash-3.2# ls
.fseventsd Extensions System dsdt.aml update.sh
Disabled Library boot update.log
bash-3.2# cd ..
bash-3.2# umount EFI
bash-3.2# rmdir EFI
bash-3.2#

Unless something weird is going on, you should be able to do the same

Also, here is the output when i fsck_hfs my EFI partition;

bash-3.2# fsck_hfs /dev/disk3s1
** /dev/rdisk3s1
** Checking Non-journaled HFS Plus volume.
** Checking Extents Overflow file.
** Checking Catalog file.
** Checking multi-linked files.
** Checking Catalog hierarchy.
** Checking Extended Attributes file.
** Checking volume bitmap.
** Checking volume information.
** The volume EFI appears to be OK.
bash-3.2#

Does your output look the same? If not, something fishy is going on with your HD....

#17
iCF-74 ToughMac

iCF-74 ToughMac

    InsanelyMac Protégé

  • Members
  • PipPip
  • 69 posts
  • Gender:Male
  • Location:Canada eh?
sh-3.2# diskutil info / |grep Identifier
   Device Identifier:		disk0s2
sh-3.2# diskutil list
/dev/disk0
   #:					   TYPE NAME					SIZE	   IDENTIFIER
   0:	  GUID_partition_scheme						*232.9 Gi   disk0
   1:						EFI						 200.0 Mi   disk0s1
   2:				  Apple_HFS iLEOPARD				200.0 Gi   disk0s2
   3:				  Apple_HFS MAC-DATA				32.4 Gi	disk0s3
sh-3.2#

No matter what my EFI partition is disk0s1, yet I always get the invalid argument error...


So I guess I should refocus on WHY I keep getting the invalid argument. Perhaps a symptom of something larger than this exercise??


Wierd..


Joe



sh-3.2# fsck_hfs /dev/disk0s1
** /dev/rdisk0s1
sh-3.2#


This is the ONLY data I get back on the fsck command. Might shed light on the issue I hope


Joe

#18
og-phantom

og-phantom

    InsanelyMac Geek

  • Members
  • PipPipPip
  • 153 posts
  • Gender:Male

sh-3.2# diskutil info / |grep Identifier
   Device Identifier:		disk0s2
sh-3.2# diskutil list
/dev/disk0
   #:					   TYPE NAME					SIZE	   IDENTIFIER
   0:	  GUID_partition_scheme						*232.9 Gi   disk0
   1:						EFI						 200.0 Mi   disk0s1
   2:				  Apple_HFS iLEOPARD				200.0 Gi   disk0s2
   3:				  Apple_HFS MAC-DATA				32.4 Gi	disk0s3
sh-3.2#

No matter what my EFI partition is disk0s1, yet I always get the invalid argument error...
So I guess I should refocus on WHY I keep getting the invalid argument. Perhaps a symptom of something larger than this exercise??
Wierd..
Joe
sh-3.2# fsck_hfs /dev/disk0s1
** /dev/rdisk0s1
sh-3.2#
This is the ONLY data I get back on the fsck command. Might shed light on the issue I hope
Joe


In case you didn't see my PM yet, did you use the "munky" DFE install method? If not, that explains everything. I will dig out the thread here in a second and send you the link. I believe your EFI partition is blank at the moment (ie, unused) and that explains everything. Following the "munky" method is very simple...thread link will be coming shortly....

here is link;

http://forum.insanel...howtopic=127330

#19
iCF-74 ToughMac

iCF-74 ToughMac

    InsanelyMac Protégé

  • Members
  • PipPip
  • 69 posts
  • Gender:Male
  • Location:Canada eh?

In case you didn't see my PM yet, did you use the "munky" DFE install method? If not, that explains everything. I will dig out the thread here in a second and send you the link. I believe your EFI partition is blank at the moment (ie, unused) and that explains everything. Following the "munky" method is very simple...thread link will be coming shortly....

here is link;

http://forum.insanel...howtopic=127330



:)

Opps. Ok .... I'll dive into that article, and hopefully later today I can get that done so I can begin returning ,my extensions folder to stock.


Good catch og_phantom!


Joe

#20
og-phantom

og-phantom

    InsanelyMac Geek

  • Members
  • PipPipPip
  • 153 posts
  • Gender:Male

:)

Opps. Ok .... I'll dive into that article, and hopefully later today I can get that done so I can begin returning ,my extensions folder to stock.
Good catch og_phantom!
Joe

No problem!!! Just as in the PM I sent you, ask the question (in that thread) about replacing the DFE bootloader and using the efiv6.1 from munky (without doing a re-install). I believe it can be done painlessly, but ask just in case. I don't want to be the cause of you losing all your data!!! :)





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

© 2014 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Mac Netbook  |   PHP hosting by CatN  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy