Remove kext on HD using USB stick installer terminal?

[meanwhile]

Can anyone tell me how to remove a kext file from usb stick terminal? I installed a kext thats causing the kernel panic and i cant properly boot to my HD and to HD using usb stick.

I tried the single user -s but didnt work

i tried -s cpus=1 GraphicsEnabler=No

-v -f GraphicsEnabler=No cpus=1

-x cpus=1

 

All of them didnt work. This is the error it gives

 

Any ideas?

 

[Gringo Vermelho]

cd Volumes/nameofsystemdrive

 

rm -rf /System/Library/Extensions/nameofkext.kext

 

Then you have to boot with -f, otherwise it will just load from the cache.

[meanwhile]

Thanks commands are working but a little correction on cd Volumes. It must be "/Volumes"

Aside from that everyting works fine but the problem is I cant delete it because its read only. Do you know how to remove the file restriction? Thanks

[Gringo Vermelho]

That's odd, running Terminal from the installer I can delete anything I want on my system drive. I don't know why it doesn't work for you.

[meanwhile]

That's odd, running Terminal from the installer I can delete anything I want on my system drive. I don't know why it doesn't work for you.

Yes. I wonder how can i remove it

 

[RehabMan]

cd Volumes/nameofsystemdrive

 

rm -rf /System/Library/Extensions/nameofkext.kext

 

Then you have to boot with -f, otherwise it will just load from the cache.

Won't work.  /System/Library/Extensions will always refer to the kexts at the root.  When booting from the USB stick, root is the USB stick itself.

 

What was meant:

cd /Volumes/nameofsystemvolume

rm -rf ./System/Library/Extensions/nameofkext.kext

[Gringo Vermelho]

Yes that's exactly what I said.. I think.. what's the difference?

[meanwhile]

Won't work.  /System/Library/Extensions will always refer to the kexts at the root.  When booting from the USB stick, root is the USB stick itself.

 

What was meant:

cd /Volumes/nameofsystemvolume

rm -rf ./System/Library/Extensions/nameofkext.kext

 

So ah.. how exactly to remove kext from usb if the following code wont work?

[RehabMan]

Yes that's exactly what I said.. I think.. what's the difference?

It is not exactly what you said.  Look more closely.  There is a big difference between './something' and '/something'.

So ah.. how exactly to remove kext from usb if the following code wont work?

I provided the answer.

[3.14r2]

So ah.. how exactly to remove kext from usb if the following code wont work?

IMO

rm -rf /Volumes/mountainlion/System/Library/Extensions/IOACPIFamily.kext

[Gringo Vermelho]

That's what I said, except I didn't place it all on one line. So that won't work either.

 

RehabMan: Can you explain why, in this particular case, does it work with the dot first?

I mean, I know to place the dot when running an executable from terminal (ie ./mame64 pacman -window) but I've never seen this when executing commands?

Not pulling your leg, I'm simply curious about the reason why.

[RehabMan]

That's what I said, except I didn't place it all on one line. So that won't work either.

 

RehabMan: Can you explain why, in this particular case, does it work with the dot first?

I mean, I know to place the dot when running an executable from terminal (ie ./mame64 pacman -window) but I've never seen this when executing commands?

Not pulling your leg, I'm simply curious about the reason why.

The '.' refers to the 'current working directory' (cwd)  The cwd is changed by the 'cd' command.  By starting with '/' you're ignoring the cwd and giving it an absolute path starting at root.

 

All of these sequences would be equivalent:

#1a
cd /Volumes/nameofsystemvolume
rm -rf System/Library/Extensions/nameofkext.kext
#1b
cd /Volumes/nameofsystemvolume
rm -rf ./System/Library/Extensions/nameofkext.kext
#2a
cd /Volumes/nameofsystemvolume/System/Library/Extensions
rm -rf nameofkext.kext
#2b
cd /Volumes/nameofsystemvolume/System/Library/Extensions
rm -rf ./nameofkext.kext
#3
rm -rf /Volumes/nameofsystemvolume/System/Library/Extensions/nameofkext.kext

All this is "Unix shell 101" kind of stuff.  If you plan to do things in Terminal, it is a good idea to read/walk through a few tutorials on it.