Today I was able to get the machine to sleep properly - I finally have a machine I can take out on the road. Sleep was the last major hurdle preventing this machine from outside adventures. There are still issues - it is a work in progress - and eventually I'll start in on making it a Snow Leopard machine. For now it is quite a good Leopard 10.5.8 netbook. Here are some of the things I found interesting during the process.
I used the Restore.dmg method from binglax09 (thanks much by the way!). This worked pretty fast. At first I was having difficulties with the installation. I thought it had to do with the BIOS - a backdating to the
f.05 was performed (the machine had f.18). This seemed to make a difference although it could have been using the
NetbootMaker that actually made that bit work. I did have some difficulties with passwords and in the end had to solve this issue by resetting them for all the accounts in the install.
Most things were working pretty well - except for sleep. I checked out the boards for sleep issues. I found Bryan's
sleep fix. This was very exciting - except it didn't work.
More digging around and putting off I stumbled on LeMaurien19's
2 gig ram card post. This didn't seem relevant to my sleep issue - yet it looked interesting, and indeed it was a gem. Reading through thread I learned that many people had found that amount of ram they had installed could cause the sleep to fail. Well that's an easy test - out came the 2 gig card and in went the 1 gig card. It worked beautifully - exactly the way Bryan had posted in his thread. I don't know if it was just the ram issues or a combination of Bryan's fix and the ram.
Further in the ram card thread posts lead me to believe that by editing the DSDT file I should be able to get the system working with 2 gigs. Several people have done
iDeneb 1.3 reinstalls with 2 gigs installed and have it functional. It would appear that now is the time to learn about DSDT files.
Most systems I've tested are working great. binglax09 has already dealt with the two CPU threads, turning on Quartz (GPU action), getting the screen resolution, etc. The two things currently deficient that I've checked are ethernet - it sees no connection, and the mic input doesn't work. The audio out is very quiet as well. These are fairly well known issues. I haven't tested the audio in/out port, or bluetooth/ cellular modem (I don't have a bluetooth or cellular modem card). The web cam does work, and the LED indicating that camera is on works as well. Wifi worked straight away and has continued through most of the hacking about that I've done.
The track pad is working and has all the features - however it drives me nuts. The features are there - the quality just isn't. I've put a lot of time in to adjusting the parameters and it is still jumpy, imprecise, fails with treed menus. I've found it to be such a hassle that I've been screen sharing (yes this works quite well!) to work on the machine. When forced to actually use the mini directly I've been using a mouse. From looking at the Extensions folder the VoodooPS2Controller.kext is loaded and it is the VoodooPS2 preference panel that I've used to adjust the track pad. It is quite possible that I have a bad track pad.
Speaking of kernel extensions - from the Terminal a handy command is
kextstat. It displays status of loaded kernel extensions - this can be quite handy for debugging.
Hey binglax09 - if you have a chance could you let us know the configuration of the machine on which you made the Restore.dmg - things like the BIOS version, ram, passwords, what kexts you used etc. Thanks man - this is a great idea, and you've performed quite a service for the group.
NINE