Jump to content

[GUIDE] Dell Latitude E6410

- - - - -

  • Please log in to reply
152 replies to this topic

#21
silica

silica

    InsanelyMac Protégé

  • Members
  • Pip
  • 10 posts
thanks for the great writeup. i followed your guide and installed it on dell e6510 i7-720QM, 4gb ram. i am having some issues
- it recognized bus speed as 533Mhz which is lower than the real speed.
- i have 4gb ddr3 1066MHz sdram, it recognized as ddr2, 667 Mhz speed memory.
- it recognized the processors as 32 bit processors and it always boots using 32 bit kernel. i have i7-720QM is it possible to switch to 64bit kernel? i tried to modify Extra boot.plist and different boot options, didn't have any luck. i was using http://www.ahatfullo...ms/SMS/SMS.html to see 32 bit or 64 bit kernel.

#22
mmoore5553

mmoore5553

    InsanelyMac Protégé

  • Members
  • Pip
  • 5 posts
curious did you have error with acpi ? i have set the bios to have ata and also set off everything i can leapord is giving me unable to find driver for acpi ? know of anything i can do ?

#23
mmoore5553

mmoore5553

    InsanelyMac Protégé

  • Members
  • Pip
  • 5 posts
okay i got paste that but i have a camera on the screen and it looks like a button turning on ...not sure what that is ... i can post a screenshot if i need too.

#24
ktbos

ktbos

    InsanelyMac Protégé

  • Members
  • PipPip
  • 61 posts

curious did you have error with acpi ? i have set the bios to have ata and also set off everything i can leapord is giving me unable to find driver for acpi ? know of anything i can do ?


I should have mentioned in my guide about the BIOS setting. In the BIOS, under the System Configuration heading, I've set SATA Operation to "AHCI". Not sure if that will help you.

(I've added this step to the guide as the first thing to do.)

It'd be interesting to know if anyone has tried this guide with a setting other than AHCI and to know how it went.

#25
ktbos

ktbos

    InsanelyMac Protégé

  • Members
  • PipPip
  • 61 posts

thanks for the great writeup. i followed your guide and installed it on dell e6510 i7-720QM, 4gb ram. i am having some issues
- it recognized bus speed as 533Mhz which is lower than the real speed.
- i have 4gb ddr3 1066MHz sdram, it recognized as ddr2, 667 Mhz speed memory.
- it recognized the processors as 32 bit processors and it always boots using 32 bit kernel. i have i7-720QM is it possible to switch to 64bit kernel? i tried to modify Extra boot.plist and different boot options, didn't have any luck. i was using http://www.ahatfullo...ms/SMS/SMS.html to see 32 bit or 64 bit kernel.


Hmm, hadn't thought to check bus speed. How did you do that and how can I check mine to compare?

Another good point about the RAM - I confirmed that it found the right quantity, but System Info does show DDR2 667 instead of the real DDR3. Not sure that matters much, though. Especially to me where I won't be doing anything with this Hac that taxes the memory.

I knew about the kernel being 32-bit, although my experience was removing the boot flag caused a failure to boot. I believe it has to do with the custom boot kernel. So until somebody can find a better kernel to use with our laptop, I think we are probably stuck with 32-bit. Again, not a big deal for me since I won't be running apps that could really take advantage of it.

#26
mmoore5553

mmoore5553

    InsanelyMac Protégé

  • Members
  • Pip
  • 5 posts
okay it is finally installed ...is there a way to fix wireless . i been looking everywhere for it ..any updates on this ? thanks so much for all this work you have done. I did not run the sudo command should i ?Also does the battery charge still work. I noticed my battery says condition replace now and 15:02. i have the power adapter hooked up and wondering if not charging ? This is brand new laptop also .

#27
mmoore5553

mmoore5553

    InsanelyMac Protégé

  • Members
  • Pip
  • 5 posts
not sure if anyone has seen this on e6410 but does there grab work ? I have tried another program to get screen shots and it is like my monitor does not exist or can capture from. I am so confused .i have looked all over the net and wondered if anyone else has same problem. I can download any desktop capture program and the screen shot shows up blank ..how do i check to see if i have right video drivers.

#28
ktbos

ktbos

    InsanelyMac Protégé

  • Members
  • PipPip
  • 61 posts

not sure if anyone has seen this on e6410 but does there grab work ? I have tried another program to get screen shots and it is like my monitor does not exist or can capture from. I am so confused .i have looked all over the net and wondered if anyone else has same problem. I can download any desktop capture program and the screen shot shows up blank ..how do i check to see if i have right video drivers.


Wow, good find mmoore5553. Same thing happens to me. I'm not sure how Grab works or what it is a sign of. If Grab requires Core Image/Quartz Extreme to work, then that's an easy answer why Grab isn't working. But if that's not the case, I really don't know why other than to say that it is apparently related to having a video driver that isn't completely working. It could be that we'll need to wait for the Hacintosh video drivers to catch up to our hardware.

Which video card do you have, anyway? That might help start establishing a data point. Mine is the NVS3100M (discrete card).

#29
mmoore5553

mmoore5553

    InsanelyMac Protégé

  • Members
  • Pip
  • 5 posts
well normally i am a pc guy and use another program to find out called siw ...does mac have a good program for me to find out and i will start to search for things to fix it.

#30
CalaverX11

CalaverX11

    InsanelyMac Protégé

  • Members
  • Pip
  • 44 posts
  • Gender:Male
  • Location:Chicago, IL
EDIT: Never mind, I found the problem. I forgot to remove VoodooHDA before upgrading. Trying again with a fresh install.

As it turns out, AppleHDA is not the culprit, it's AppleSMC causing the kernel panic at about 95%.

#31
CalaverX11

CalaverX11

    InsanelyMac Protégé

  • Members
  • Pip
  • 44 posts
  • Gender:Male
  • Location:Chicago, IL

I updated to 10.6.4 using the software updater and everything worked fine. I suspect as ktbos mentioned the audio kext might be the problem because I have not yet installed it and my update worked without issues.

Did you run the Post-Installer before updating to 10.6.4, or did you update right out of the box?

#32
kailm

kailm

    InsanelyMac Protégé

  • Members
  • Pip
  • 11 posts
I got QE/CI working with the NVS 3100m video card on the dell E6410.

What you need are kexts from fermi_package_20100803.dmg someone has the bundle for the new gtxs and it works for the NVS 3100m.

Just install the dmg, reboot and nvenabler should have QE/CI working. It says unknow nvidia card, but i dont mind. Havent bothered to add a device string.

Everything works except the wireless.

#33
ktbos

ktbos

    InsanelyMac Protégé

  • Members
  • PipPip
  • 61 posts

I got QE/CI working with the NVS 3100m video card on the dell E6410.

What you need are kexts from fermi_package_20100803.dmg someone has the bundle for the new gtxs and it works for the NVS 3100m.

Just install the dmg, reboot and nvenabler should have QE/CI working. It says unknow nvidia card, but i dont mind. Havent bothered to add a device string.

Everything works except the wireless.


Great find, kalim! Thanks! When I get a chance I'll do it on my E6410 and update the package to include that dmg.

#34
nailz

nailz

    InsanelyMac Protégé

  • Just Joined
  • Pip
  • 4 posts

Great find, kalim! Thanks! When I get a chance I'll do it on my E6410 and update the package to include that dmg.

It's not stable! If i play around in Dashboard it takes approx 1min. until the Notebook locks up. Removing the inject setting from chameleon, fixes the lockups but also disables QE :-/

Any help is welcome.

#35
kailm

kailm

    InsanelyMac Protégé

  • Members
  • Pip
  • 11 posts
I did install nvdia cuda drivers 3.1 (dl from nvidia), not sure if having those makes it work.
Dashboard, frontrow all work just fine, it doesnt lockup for me.

#36
stizz

stizz

    InsanelyMac Protégé

  • Members
  • Pip
  • 6 posts
I am trying (triple boot) guide on my e6510 and I get stuck between step 14 and 15 in the Mac OS Setup part. The install fails as expected, and after reboot the chameleon boot loader shows the HFS+ partition. But when I try to boot from it, I get an error that forces the system to shutdown.


/dev/rdisk0s3
Unexpected Inconsistency
Exited with Signal 8
Can't initialize disk cache
fsck failed
...
CPU HALTED

I have tried to identify /dev/rdisk0s3, which seems to be my hfs+ partition.
I have re-installed several times and redone the partition scheme different ways (mainly GUID)

At one point I gave up in frustration and used clonezilla to restore my dell back to factory settings (Win7) from the iso I made prior to the Hac attempt. Then I tried installing SL on a 16GB Kingston thumb drive only to get hung up at the exact same spot.

I boot back into the installer to use terminal to run fsck and fsck reports back:
Bad Super Block: Magic Number Wrong



Any suggestions? The only thing I'm doing different from your guide is I'm using SnowLeopard installer from an 8GB Kingston thumbdrive instead of an actual install DVD. I have installed from this installer on other Hacintosh without problems.

Posted Image

#37
ktbos

ktbos

    InsanelyMac Protégé

  • Members
  • PipPip
  • 61 posts

I am trying (triple boot) guide on my e6510 and I get stuck between step 14 and 15 in the Mac OS Setup part. The install fails as expected, and after reboot the chameleon boot loader shows the HFS+ partition. But when I try to boot from it, I get an error that forces the system to shutdown.


/dev/rdisk0s3
Unexpected Inconsistency
Exited with Signal 8
Can't initialize disk cache
fsck failed
...
CPU HALTED

I have tried to identify /dev/rdisk0s3, which seems to be my hfs+ partition.
I have re-installed several times and redone the partition scheme different ways (mainly GUID)

At one point I gave up in frustration and used clonezilla to restore my dell back to factory settings (Win7) from the iso I made prior to the Hac attempt. Then I tried installing SL on a 16GB Kingston thumb drive only to get hung up at the exact same spot.

I boot back into the installer to use terminal to run fsck and fsck reports back:
Bad Super Block: Magic Number Wrong



Any suggestions? The only thing I'm doing different from your guide is I'm using SnowLeopard installer from an 8GB Kingston thumbdrive instead of an actual install DVD. I have installed from this installer on other Hacintosh without problems.

Posted Image


I'm not sure why fsck would need to run - perhaps there is a disk hardware problem? What happens if you boot in single user mode using the MAC OS install DVD and do a manual call to fsck on your hard drive?

#38
stizz

stizz

    InsanelyMac Protégé

  • Members
  • Pip
  • 6 posts

I'm not sure why fsck would need to run - perhaps there is a disk hardware problem? What happens if you boot in single user mode using the MAC OS install DVD and do a manual call to fsck on your hard drive?


I get the same BAD SUPER BLOCK: MAGIC NUMBER WRONG error...

fsck also told me there were blocks it could not access,

I'm going to try a few more things and take some more screenshots.

#39
stizz

stizz

    InsanelyMac Protégé

  • Members
  • Pip
  • 6 posts
I tried installing to my thumb drive that I formatted and partitioned on another Hac and when I attempt to boot from it I get the same error as before, although now on /dev/rdisk1s2 , which is the hfs+ partition I installed to.


This is from my terminal when I boot into the installer and run fsck:

Posted Image

#40
stizz

stizz

    InsanelyMac Protégé

  • Members
  • Pip
  • 6 posts
so it seems my problem has to do with the fact that my e6510 has 8GB of ram..

http://www.insanelym...p...1876&st=100

A solution was proposed, but I am unsure how to boot into single user mode AND have read/write privs.

I tried the following, but every command returned a scolding about how I was in read only directory.

Nope, nothing weird.
You are running Hac in 32-bit mode, thus user-space tools are limited with 4GB of address space.


Actually, this is fsck_hfs faulting on checks with RAM >4GB. And it fails only for the root partition.
Just boot in single-user mode and do:

# mv /sbin/fsck_hfs{,.orig}# printf '#!/bin/bash\nexec /sbin/fsck_hfs.orig -c512m "$@"' > /sbin/fsck_hfs# chmod +x /sbin/fsck_hfs#

Enjoy full RAM over 4GB!







1 user(s) are reading this topic

0 members, 1 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