Print

[baller3166]

Not to sound rude RCFA, but I see no mention of mkext files in your link provided above.  Could you perhaps give a slightly more thorough guide of how to fix this boot issue?  Does anyone have any other solutions to fix this?  I have no idea why my EEE is taking over a minute to boot OSX

[rcfa]

Not to sound rude RCFA, but I see no mention of mkext files in your link provided above.  Could you perhaps give a slightly more thorough guide of how to fix this boot issue?  Does anyone have any other solutions to fix this?  I have no idea why my EEE is taking over a minute to boot OSX

If you dd over the EFI partition, then a ready-built .mkext file is already on it.

Alternatively, you should find instructions on how to (re)build the mkext file in one of the readme files I had part of the disk image.
Anyway, basically it goes something along these lines:

Code: [Select]

sudo su - root
mkdir /tmp/EFI
mount_hfs /dev/disk0s1 /tmp/EFI
cd /tmp/EFI/Extra/Extensions
rm ../Extensions.mkext
chown -R root:wheel *
chmod -R 755 *
kextcache -a i386 -m ../Extensions.mkext *.kext
logout
or something like that (typing from memory here...), and of course, it depends on what device you are, partition layout, etc. but likely the above is right.
Similarly, the Extensions.mkext in /System/Library might be out of date. Simply delete it, the OS should automatically rebuild it there.

Otherwise, I'm not sure why it takes so long, e.g. permissions on your OS X partition may be off, so e.g. /System/Library/Caches/com.apple.kernelcaches/kernelcache might be out of date or not be consulted, etc.
To cure potential issues of that sort, run Disk Utility and do repair permissions on the boot drive.

Also, I don't know how well or badly things behave on the original 160GB drive, I have a 500GB drive in there, which sports faster throughput.

Stuff like this is rather hard to diagnose, without hands on the machine and e.g. looking at a live boot in verbose mode to see where time is spent, etc.

[shoota]

thanks rcfa. i'll look into  this more tomorrow when i'm not so sleepy. But let me get this straight, Do .mkexts need to be fixed if i used the iDeneb method or is this only for the retail method?

[baller3166]

thats my question shoota....im just a little worried about following instructions with the warning of "or something like that" especially when im doing everything in terminal

i havent seen anything else about mkexts anywhere, but i am curious why its booting slowly. shoota, how long does it take your 1000he to boot to osx

[cbf88]

thats my question shoota....im just a little worried about following instructions with the warning of "or something like that" especially when im doing everything in terminal

i havent seen anything else about mkexts anywhere, but i am curious why its booting slowly. shoota, how long does it take your 1000he to boot to osx

Basically, the commands rcfa gave you in his last post will put an Extensions.mkext file into your /EFI/Extras folder, and acts like a cache of your kexts for quick loading. Whether you need to do it or not is in the air, but if you do it right, there's no chance of doing harm.

[rcfa]

mkext's are a standard Mac OS X thing. They should equally apply to iDeneb or vanilla, it's just a matter of where iDeneb puts its kexts. If it puts all in /System/Library/Extensions and doesn't use any Extra/Extensions folder, be that on the main partition or on an EFI partition, then the OS should take care of the mkext file automatically. If any secondary folder containing kexts is used by iDeneb, then likely you will have to create the Extensions.mkext file manually, if you want to have the benefit of faster load times.

[shoota]

alright i just timed it. after the 5 second countdown of chamleon it took 1 min and 5 sec to get to a usable desktop. that seems just a touch too long, not a dealbreaker but there's room for improvement.

alright i found the Extension.mkext file. it's under System>Library>Extensions.mkext

does that seem like the right place?

[rcfa]

alright i just timed it. after the 5 second countdown of chamleon it took 1 min and 5 sec to get to a usable desktop. that seems just a touch too long, not a dealbreaker but there's room for improvement.

alright i found the Extension.mkext file. it's under System>Library>Extensions.mkext

does that seem like the right place?

That's the one the System creates for the contents of /System/Library/Extensions

If you have (I do not) a /Extra/Extensions folder on your OS partition, then you can cache these extensions by creating an /Extra/Extensions.mkext file, or if you have (which you will if you have the same setup as I) an Extra/Extensions folder on your EFI/Chameleon partition, then you can create a cache for these kernel extensions with the instructions I posted here earlier.

Also, you mix up two things here: boot time and login time!

Boot time is just until you get a login panel. You seem to have auto-login enabled, so you go straight to the desktop, which of course takes longer, because if first boots, then it logs you in, loads your personal settings, launches the Login Items, the Finder, the Dock, etc.

These are all relatively disk intensive things, so if your OS is located towards the end of the disk, and the disk isn't particularly fast, then a minute really isn't that bad.
We're talking about a NetBook after all, not a high-performance computer, and an OS that's designed for more modern hardware than WinXP.

Also, the idea behind an OS like Mac OS X is that booting is a rare thing to do. You log in, log out, you sleep or hibernate a laptop, but you don't really turn it off or boot it on a regular basis.
e.g. I own/manage more than a dozen Macs, the only time they get rebooted is when a new OS or something similar gets installed that requires a reboot, or if there's a power outage or a rather rare kernel panic. Otherwise, they keep running or are put to sleep. So for normal operations, the only thing that matters is wake up time, and that's pretty snappy.

[shoota]

very good points. i do have auto login enabled and like i said the minute wait doesn't really bother me i don't have the /extra/extensions folder. i try not to put my lappy to sleep cuz it makes the sound get wonky when it wakes up.

i think i'm going to attempt the .6 and .7 upgrades. they kinda make me nervous but what the heck. any pointers for the .6 upgrade?

[rcfa]

i try not to put my lappy to sleep cuz it makes the sound get wonky when it wakes up.

What sound driver are you using? VoodooHDA, or the old thing with Azalee?
VoodooHDA doesn't give me any issues with sleep. It just gives me the general issue that every now and then it crackles a bit because it seems to overrun some buffers, but I hope one of the next versions of that driver will fix this, and then sound will be mostly taken care of... (minus the mic volume not being hooked up to the proper OS X parameters)

i think i'm going to attempt the .6 and .7 upgrades. they kinda make me nervous but what the heck. any pointers for the .6 upgrade?

Hey, with the vanilla install I have, the upgrades were a breeze, only the 10.5.7 video drivers had to be patched again. Will be in the next version...

[shoota]

i'm using the voodooHDA, and i really like it.   with the 10.5.7 video issues did it log in at 800x600 and the kext install fixed it right up?

[rcfa]

i'm using the voodooHDA, and i really like it.   with the 10.5.7 video issues did it log in at 800x600 and the kext install fixed it right up?

Something like that. Not quite sure if I had to boot single user and temporarily copy old kext back that way, or what exactly I did, before I patched the 10.5.7 kexts. But basically the system works minus the screen, which gets garbled with the original drivers.
In general, it's good to have remote login enabled, that way you can always slogin into your machine, even if the console is not in a state that's usable. And in some cases Remote Desktop works just fine, too, thanks to the virtual framebuffer driver that Mac OX instantiates when it doesn't find a valid video driver.

[LonelyTV]

What sound driver are you using? VoodooHDA, or the old thing with Azalee?
VoodooHDA doesn't give me any issues with sleep. It just gives me the general issue that every now and then it crackles a bit because it seems to overrun some buffers, but I hope one of the next versions of that driver will fix this, and then sound will be mostly taken care of... (minus the mic volume not being hooked up to the proper OS X parameters)

You know, I've had some really strange audio issues using the VoodooHDA created by Thir... something. If I mute the sound and put the computer to sleep it'll wake up with the volume all the way up... however, the audio Icon still shows that it's muted. Also, I can't seem to get the Preference Panel to work I always get a "Can't map memory" error. Any clue if it has to do with the Modified VoodooHDA KEXT or the preference panel? Anyone else have issues with this?

[shoota]

yeah i got that error too. try using the os x's default audio panel. that one worked for some things i believe.

[rcfa]

I've had some really strange audio issues using the VoodooHDA created by Thir... something.

Just use the VoodooHDA that I put in as part of the package. That modified one has a bunch of problems.

[shoota]

hey guys i really need the LCD brightness control kext for leopard. can someone please attach it here? thanks.

bump: please???