Jump to content

Dell Vostro 1500 Mega Thread

Hexidecimal

By Hexidecimal,
in OSx86 10.5 (Leopard)

 Share
474 posts in this topic

Recommended Posts

Lil W
Lil W
Posted
Posted

Hi guys, i followed this topic for 2 days, and happily that i can install iPC 10.5.6 working great on my Vostro 1500. This morning, i using iDeneb 10.5.7 combo update and my system got a problem like PS/2 not working anymore, so I can't patch the kernel 'coz i can't type password :)

 

Because of that, I decide to reinstall, but the problem is i can't boot from DVD iPC anymore, i dont know what's going wrong with that, i try all of options to boot. When boot from DVD, at F8 screen, i think that i forgot what boot option to boot with iPC 10.5.6. I wonder if you can help me with that.

 

Thank a lot

 

This is my Laptop config.

Dell Vostro 1500

Intel Core 2 Duo T7300 @ 2.0 GHz

Intel 965PM Express chipset

160GB Toshiba - but i use Western External HDD 1TB to install iPC (it's working well until my stupid decided this morning)

2GB RAM DDR2 667MHz

Nvidia GeForce 8600M GT 256MB 1280x800

Sigmatel 9205

Broadcom 440x 10/100 Integrated LAN

Intel Wireless WiFi Link 3945ABG

Lil W
Lil W
Posted
Posted

I don't know what wrong with my Laptop. I must reinstall iATKOS v2i and then reinstall iATKOS v5i with boot -x -f. after that i using the combo update iDeneb 10.5.7 (must backup the driver and extension before the combo update). my laptop working well now, except Reboot and Shutdown, not yet test on sleep but I'm pretty sure it's not work.

timeshifter
timeshifter
Posted
Posted

I'm interested in the EFI partition / Retail install. I'm so tired of downloading patched OSs and dealing with each one's quirks. In case you're not familiar with this method here's a quote from munky's method

The release of dfe's amazing boot-132 loader was an eye-opener for many of us in the community. The fact we can boot the shrink-wrapped, unmodified retail Leopard DVD on modern Intel machines (and, it turned out, on any SSE2 or better Intel machine) means we have the ability to boot a totally unmodified OS X. (The install DVD of course boots into Mac OS X).

 

However, it seemed most people didnt realise the gravity of this, or simply thought 'oh thats nice, use retail to install. ok, back to hacking in /System/Library/Extensions....'.

 

This is, imho, the wrong approach.

 

The *right* approach is to leave /System/Library/Extensions alone, and apply patches and modifications to the system from a different vector, just like boot-132.

 

This is, in my humble opinion, the ultimate hackintosh install method.

 

What benefit does that give you?

 

* Well, how about trouble-free Software Update direct from Apple? Even on SSE2 Intels? (and AMDs when Voodoo 9.5.0 final comes out...)

 

* How about being able to completely erase and reinstall the OS without breaking ur carefully-assembled patches?

 

* How about being able to boot *the same disk* on a real mac and your hack?

 

* How about having a com.apple.Boot.plist completely outwith the installed OS?

 

all without losing the usual EFI strings goodness you've come to expect from a bootloader... (Thx to Chameleon team!)

So munky, where's the beef?

 

Well first, a little history...

 

When you format a GPT (GUID Partition Table) disk in Disk Utility, there is always a hidden, 200Mb partition created as the first partition on the disk. This is supposed to be a 200Mb FAT-32 partition used for storing EFI drivers, and is mandated by the EFI / GPT specs.

 

Apple honours the specs and so puts the 200Mb partition there. However, (and this is the important part...) *Apple dont use it!*

 

So we can hijack it and use it for our own ends. :(

You're still not getting to the point...

 

Ok ok. So here goes. We repurpose the EFI system partition to hold our kexts (and, if necessary, kernels) so we dont have to change the main installation. AT ALL.

 

The nice thing is that Mac OS X and Disk Utility (at least the graphical version) will continue to hide the EFI partition, as you're not supposed to see it. But you also have the option to mount it if you need to make changes. And, of course, on ALL systems (currently Intel SSE2 and better), Software Update can be used without much chance (if any) of breakage.

 

Hmmm... ok i'm sold. So how do I do it?

 

Well, first grab the attached zip file. This contains a modified version of boot0 from chameleon, the unmodified boot1h from chameleon, and a fork of dfe's boot2. boot0 has been changed to look for the EFI system partition, and boot2 has been modified to load extra kexts from the EFI partition.

I had some success with a Retail guide that uses MacLoader. But now I'm trying munky's method, it seems cleaner. Can't figure out what kexts I need to start off with to get it to boot from the hard drive. I can get it to boot from the generic Boot-132 disk that I downloaded.

 

So, I guess my question is: what kexts do I need that differ from a Retail DVD? Also, what EFI string should I use for my Nvidia 8600 graphics card?

medwezys
medwezys
Posted
Posted

timeshifter, if you are able to boot from with generic boot-132, just install chameleon bootloader when your OS install is finished and copy all kexts from generic boot-132 to /Extra/Extensions/

here's my ones:

ls /Extra/Extensions/
AppleACPIPlatform.kext				  IOATAFamily.kext
AppleAHCIPort.kext					  IntelCPUPMDisabler.kext
AppleIntelIntegratedFramebuffer.kext	JMicronATA.kext
ApplePS2Controller.kext				 SMBIOSEnabler.kext
AppleSMBIOS.kext						dsmos.kext

 

And I add ApplePS2Controller.kext for giGGler, hope this helps to fix ur keyboard

ApplePS2Controller.kext.zip

ApplePS2Controller.kext.zip

timeshifter
timeshifter
Posted
Posted

Thanks medwezys, that sounds good. A couple of concerns. First - I installed the bootloader according to munky's instructions quoted below. Can I just download the latest Chameleon RC and install that to the EFI partition?

 

Second - I don't have any kexts. I thought I would just copy them from the Boot-132 CD too. But when I look on there I don't see anything that resembles a kext. I see:

 Volume in drive D is BOOT-DFE-146-BUM
Volume Serial Number is 6ABF-38C0

Directory of D:\

06/30/2008  06:05 PM			64,064 boot
06/30/2008  01:07 PM		10,518,016 initrd.img
06/30/2008  12:55 PM	<DIR>		  isolinux
04/10/2008  06:30 AM			12,241 isolinux.bin
06/30/2008  06:00 AM			47,532 mboot.c32
		   4 File(s)	 10,641,853 bytes
		   1 Dir(s)			   0 bytes free

Of course this is from Windows, but it looks about the same under OS X.

 

Third - his instructions have me copying kexts to /Volumes/EFI/Extensions. Looks like you're indicating copying kexts to /Volumes/EFI/Extra/Extensions

 

Phase 1: Reformatting the EFI System Partition.

 

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.

 

5) diskutil eraseVolume "HFS+" "EFI" /dev/diskXs1 - now, be *VERY* sure this is the correct drive. this will format the EFI partition as HFS+. (NB After erasing it will try to mount it, but will fail with "Could not mount disk0s1 with name after erase". Ignore this).

 

Phase 2: Installing the modified bootloader.

 

1) Extract the attached zip file to a directory (Safari might do this for you).

 

2) in terminal, cd to that directory (the one containing boot0, boot1h, boot-turbo-munky.bin and fdisk)

 

3) ./fdisk -f boot0 -u -y /dev/rdiskX - this puts the stage 0 bootloader onto the target disk

 

4) dd if=boot1h of=/dev/rdiskXs1 - this puts the stage 1 bootloader onto the target partition (EFI partition)

 

5) mkdir /Volumes/EFI

 

6) mount_hfs /dev/diskXs1 /Volumes/EFI

 

7) cp boot-turbo-munky.bin /Volumes/EFI/boot

 

8) cp update.sh /Volumes/EFI/

 

Phase 3: Make the disk bootable

 

This stage may not be necessary on some boards, but on my Intel board and Bad Axe boards it is. If you skip this step and your system wont boot, try doing it. That said, doing this on boards which DONT need it will do no harm so my logic is do it anyway.

 

Type the fdisk command and then each line as shown:

 

1) ./fdisk -e /dev/rdiskX (NB: Ignore any fdisk: could not open MBR file /usr/standalone/i386/boot0: No such file or directory error)

 

2) f 1

 

3) w

 

4) q

 

Phase 4: Setup your new bootloader EFI partition

 

1) Setup directory tree:

 

mkdir -p /Volumes/EFI/System/Booter

mkdir /Volumes/EFI/Extensions

mkdir /Volumes/EFI/.fseventsd

 

2) touch /Volumes/EFI/.fseventsd/no_log - this prevents the File System Events Daemon (fseventsd) from logging on this volume, which can cause the EFI partition to become unmountable.

 

3) copy necessary extensions into /Volumes/EFI/Extensions (eg:

 

cd <directory containing kexts>

cp -R *.kext /Volumes/EFI/Extensions)

 

4) if necessary, copy patched kernel into /Volumes/EFI/ (eg:

 

cd <directory containing the wonderful Voodoo kernel)

cp mach_kernel.voodoo /Volumes/EFI/

 

5) cd /Volumes/EFI

chmod +x update.sh

sudo ./update.sh - this will build a kextcache in /System/Booter. Please check update.log for any errors. (Dependency warnings are ok and normal - the dependencies will be available at boot time from /System/Library/Extensions).

 

6) umount /Volumes/EFI (If this fails, do umount -f /Volumes/EFI).

 

7) rm -rf /Volumes/EFI

 

8) If your machine cannot use the vanilla kernel, at this point you must take a note of your install's UUID. Open Disk Utility.app and click on the partition containing your fresh install. Click the blue 'I' information icon and look for Universal Unique Identifier. This should be a fairly long hex string. Write this down somewhere on a piece of paper. (not in a text file on the computer!)

 

You should be ready to boot at this stage.

 

Phase 5: Test boot!

 

So this differs slightly depending on whether you have a Core cpu or not - that is, whether you can (or choose to) run the vanilla kernel or a patched kernel.

 

If you boot the vanilla kernel, you should just have to press Return, as the bootloader should find your installed OS.

 

If you boot a patched kernel, the magic you need is this:

 

bt(0,0)/mach_kernel.voodoo -v boot-uuid=<the install's uuid you wrote down earlier>.

 

With a bit of luck, you'll boot up into your nice shiny new Leopard install, and be able to use Software Update without worrying.

Phase 6: Post-Install - Kexts, EFI strings, Boot.plist, Troubleshooting

 

Kexts:

 

So you booted back up, but you maybe dont have gfx support, or are missing some nice LAN kext... To mount EFI:

 

sudo -s

mkdir /Volumes/EFI

mount_hfs /dev/diskXs1 /Volumes/EFI

 

to install new kexts:

 

sudo -s

cd path/to/kext

cp -R Blah.kext /Volumes/EFI/Extensions

cd /Volumes/EFI

./update.sh

EFI Strings and com.apple.Boot.plist:

 

v3 of the bootloader supports a com.apple.Boot.plist file located on the EFI partition. You can place this in either of these two locations:

 

/Volumes/EFI/com.apple.Boot.plist

-or-

/Volumes/EFI/Library/Preferences/SystemConfiguration/com.apple.Boot.plist

 

Its your choice, and it makes no difference. If you have both it will favour the one in /Library/Pref.....

 

This is, of course, the place to put EFI strings - aka device properties - strings. This bootloader supports EFI strings in the same format as Chameleon expects them.

timeshifter
timeshifter
Posted
Posted
Thanks medwezys, that sounds good. A couple of concerns. First - I installed the bootloader according to munky's instructions quoted below. Can I just download the latest Chameleon RC and install that to the EFI partition?

 

Third - his instructions have me copying kexts to /Volumes/EFI/Extensions. Looks like you're indicating copying kexts to /Volumes/EFI/Extra/Extensions

OK, I think this is explained in the comments at the Chameleon site under the RC announcement, post number 29.

 

if you’re using GUID and munky’s boot132

 

step-by-step:

 

1. download file

2. unzip file

3. open up terminal

4. cd /

5. mkdir /Volumes/EFI; mount_hfs /dev/disk<drive>s1 /Volumes/EFI; cd /Volumes/EFI

6. mkdir Extra; cp -R /Volumes/EFI/Extensions /Volumes/EFI/Extra

7. if you have a modified com.apple.Boot.plist, copy it into /Volumes/EFI

8. cd into Chameleon download directory

9. cp -R smbios.plist Themes /Volumes/EFI/Extra

10. sudo fdisk -f boot0 -u -y /dev/rdisk<drive>

11. sudo dd if=boot1h of=/dev/rdisk<drive>s2

12. sudo cp boot /Volumes/EFI

 

Where <drive> is a number 1+, you can find in disk utility by right clicking on a parition and clicking information.

Also, it looks like Chameleon uses the Extra folder where munky didn't .

 

Have tried any of this yet.

medwezys
medwezys
Posted
Posted

sorry, i hadn't read the whole munky thing. I have used these http://menoob.com/hackintosh/hackintosh-in...il-dvd-on-a-pc/ instructions a year ago and it works till now. Used generic boot132.iso, kexts are in INITRD.IMG as I remember.

timeshifter
timeshifter
Posted
Posted
sorry, i hadn't read the whole munky thing. I have used these http://menoob.com/hackintosh/hackintosh-in...il-dvd-on-a-pc/ instructions a year ago and it works till now. Used generic boot132.iso, kexts are in INITRD.IMG as I remember.
Great, that helps.

 

Here's my notes from last night, I'm almost there, just gotta get sleep working. I'm going to do a clean install on another partition.

 

Notes:

decided to re-do with Chameleon 2.0 RC

Used instructions I posted here: http://www.insanelymac.com/forum/index.php...t&p=1168340

only change is in step 11 I used "rdisk0s1" instead of "rdisk0s2"

copied all the standard kexts on the INITRD.IMB from Boot-132 over (didn't have any in EFI Extensions folder)

CHAMELEON BOOTS PERFECTLY!

 

Next steps

10.5.6 update

keyboard working

video working

power management

sound

 

remove ApplePS2 kext, install VoodooPS2 kext

chmod -R 755

chown -R root:wheel

 

screw it, giving up on virgin install

install VoodooPS2 kext using installer

keyboard and trackpad now work, no pref pane for trackpad though

 

EFI studio gives me 1440 x 900 video by selecting 8600 256 MB and writing out com.Apple.Boot.Plist (or whatever the hell it's called)

 

reboot / shutdown don't work any more

 

reinstall VoodooPS2 package and choose "all users of computer" and be sure to check prefpane install, it installs a larger file size 356 kb vs 150 or so. Reboot, TWO FINGER SCROLLING WORKS!

 

sound works, installed VoodooHDA, except output volume is very weak

double-clicked VoodooHDA prefpane, got errors, rebooted:

same errors: Error can't map memory

 

noticed Trackpad prefpane

selecting "dragging" makes all dock clicks appear as right-clicks

 

remaining steps:

power management

sleep / reboot

3G

misc features - SD card, VGA out, etc.

 

Installed Voodoopower, VoodooBattery, VoodooUSBEHCI

Battery and power management seem to be working, about 3 hours reported available battery time on full charge (I have the 9 cell battery)

 

Sleep doesn't work!

It goes to sleep and then a moment later it wakes up. The bluetooth LED flashes when this happens. I've disabled all wireless devices (wifi, bluetooth, 3g) in BIOS yet it still wakes up. Not sure why.

 

I'm going to start over by installing another copy of Leopard into partition number 2. Also making a disk image of 1st Leopard install to third partition (hell, I've got 6 partitions on this disk, I'm gonna use 'em!)

timeshifter
timeshifter
Posted
Posted
That was a lot of work... finally got an install I'm happy with.

Retail install (my disc is 10.5.1 I think?) updated with 10.5.6 combo updater (I'm kind of scared to upgrade to 10.5.7 in case something breaks... I'll make a backup and try at some point).

I've got Chameleon 2.0 installed to the EFI partition. I've put these extensions in the EFI extensions folder (I'll check if I've missed any) VoodooUSBEHCI (and the IOUSBFamily with the change needed for this), VoodooHDA (with IOAudioFamily and OSvKernDSPLib), VoodooBattery, VoodooPower, dsmos... I think that's it (I installed VoodooPS2 normally and haven't bothered moving it yet). And in extra I've got a DSDT.aml (had to make it myself, the patchers seemed to put things in the wrong place, it's a bit messy though because it was rushed, but seems to work), com.apple.boot.plist and smbios.plist.

The DSDT gets the 8600m GT working and the clamshell sleep on lid-close thing, and means I can use AppleIntelCPUPowerManagement. I ended up making the DSDT because every other thing I tried ended up with no QE/CI. I haven't tested VGA and TV out yet, but I suspect that at least VGA out is working.

Only real problem is that shutdown and restart don't work with the graphics working, no one seems to have found a fix.

 

I also have to work out what to do about wifi, I've got a 3945abg, and I'm upgrading to a 4965agn... maybe I should get another card and run them both (I use Vista too, and want the 4965agn for that).

Could you post your DSDT.aml file, please... pretty please!?
medwezys
medwezys
Posted
Posted

timeshifter, does VoodooPS2 enables all of media keys in front panel of your laptop?

Sleep fix is VoodooUSBEHCI.kext together with modified /System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBEHCI.kext/ from http://www.superhai.com/darwin.html

xxmunxx
xxmunxx
Posted
Posted

Hi everybody :D

My Vostro 1500's touchpad does not work correctly :D

Anybody help me fix it, plz??? Thanks very much

Can U give me the link to download driver for touchpad??

 

 

Dell Vostro 1500 T7500, GF8600m GT256MB, 1GB DDR2.

xXx Leo 10.5.6

Works: everything except shutdown/restart, sleep, touchpad.....Help me

giGGler
giGGler
Posted
Posted

what do you mena by *flashing the bios*? I think I do have the latest revision, A06. :thumbsup_anim:

 

And, of course, voodooPower.

 

I installed iAtkos 5 with SMBIOSResolver, Disabler, voodoo kernel, ps2 and broadcom 440x. No sound, simple video config, no wifi (there's no driver:() but shutdown/restart worked. boot with -x.

 

Then upgraded to 10.5.7 so no keyb/touchpad (external works) and boot with -x.

Added VoodooUSBEHCI, VoodooBattery, VoodooPower: battery setup and keyb/touchpad works. :)

Added nvinject and graphics are fine. :)

Restart/shutdown don't work :)

 

Is there any alternatives to graphics and sound? I think nvinject corrputs power handlers

timeshifter
timeshifter
Posted
Posted
timeshifter, does VoodooPS2 enables all of media keys in front panel of your laptop?

Sleep fix is VoodooUSBEHCI.kext together with modified /System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBEHCI.kext/ from http://www.superhai.com/darwin.html

The volume up and down definitely work. Mute key I'm not certain about. I thought it didn't function correctly. But with my install on partition number 2 I think it did.

 

I tried the sleep fix of VoodooUSBEHCI.kext and tried to modify the plist according to these instructions:

Readme for EHCISleepEnabler

 

To enable it you have to edit the Info.plist in

/System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBEHCI.kext/Contents/

You need to add these lines

 

<key>OSBundleCompatibleVersion</key>

<string>1.0</string>

 

under

 

<key>CFBundleVersion</key>

<string>3.1.5</string>

 

CFBundleVersion was 3.5.2 (not sure if that was exact version, but it wasn't 3.1.5).

 

Sleeep didn't work. That's probably the biggest roadblock to me using Mac OS on a daily basis on my laptop. I need sleep to work and I'm on and off the machine multiple times a day.

medwezys
medwezys
Posted
Posted

timeshifter, my version is also 3.5.2 and everything is working.

try setting sleepmode to ram:

 

sudo pmset -a hibernatemode 0

 

also mark the box in power prefs "automaticaly restart after power failure"

write if it helps

 Share
Go to topic listing
×
×
  • Create New...