Dell XPS 1340 under OSX 10.6, including boot-132 install cd

[SPLITER]

Almost everything is working on my 10.6 DELL XPS 1340, thanks to bcc9! Just one thing I need to fix, which is the wireless card. I have read that the 1340 ships with either a Dell 1515 802.11 wireless or a 1510 card. Although I am not certain, since the wireless card does not work right now, I am assuming that I have a 1515. Is there a fix for this, a kext, or a driver?

[bcc9]

Almost everything is working on my 10.6 DELL XPS 1340, thanks to bcc9! Just one thing I need to fix, which is the wireless card. I have read that the 1340 ships with either a Dell 1515 802.11 wireless or a 1510 card. Although I am not certain, since the wireless card does not work right now, I am assuming that I have a 1515. Is there a fix for this, a kext, or a driver?

1510 & 1515 work out of the box.

If your wireless isn't working you probably have something else like a 1520. You should check...

[kelobb]

Hello Spliter,

 

From my experience, I oryginally had dell 1397 half-size only b/g wifi (works with osx after adding pci id), but I removed it and add oem bcm4328 full-length card from any vendor in gsm-modem third pcie socket (the wifi switch is ignoring this but it's only small minus).

I have tried bcm4222(24) half card from dell 1520 but this broadcom is not (yet) supported (snow leo).

 

From my point of view - the best option is the dell 1510 mini-half card with a/g/n support. After rebranding to airport (see google about "rebranding broadcom wifi") it could do the job and it cost ~20$.

 

Regards

[SPLITER]

1510 & 1515 work out of the box.

If your wireless isn't working you probably have something else like a 1520. You should check...

How would I go about doing this? And if I do have smething like a 1520, how do I get it to work?

 

 

Hello Spliter,

 

From my experience, I oryginally had dell 1397 half-size only b/g wifi (works with osx after adding pci id), but I removed it and add oem bcm4328 full-length card from any vendor in gsm-modem third pcie socket (the wifi switch is ignoring this but it's only small minus).

I have tried bcm4222(24) half card from dell 1520 but this broadcom is not (yet) supported (snow leo).

 

From my point of view - the best option is the dell 1510 mini-half card with a/g/n support. After rebranding to airport (see google about "rebranding broadcom wifi") it could do the job and it cost ~20$.

 

Regards

Thanks for the info kelobb, I'll see what I can do at my local electronic stores... and it's best that I avoid the topic of having a mac installed on a DELL right? And, is this the card you are talking about?

http://search.dell.co.uk/1/2/2086-dell-wla...i-card-kit.html

[bcc9]

How would I go about doing this? And if I do have smething like a 1520, how do I get it to work?

You need to look up the PCI id under device manager under windows or in your ioregistry under OSX or under system profiler under OSX.

Or just open the dang cover on the laptop and read the part # on on the mini pci card.

Thanks for the info kelobb, I'll see what I can do at my local electronic stores... and it's best that I avoid the topic of having a mac installed on a DELL right? And, is this the card you are talking about?

http://search.dell.co.uk/1/2/2086-dell-wla...i-card-kit.html

I would be sure that your card cannot be made to work under osx before buying more hardware. For example if you have a 1520, it may be as simple as fixing the pci id to match against the existing broadcom driver.

[SPLITER]

You need to look up the PCI id under device manager under windows or in your ioregistry under OSX or under system profiler under OSX.

Or just open the dang cover on the laptop and read the part # on on the mini pci card.

 

Under PCI Cards in System Profile, it reads "This computer does not appear to have any PCI cards installed." I have googled how to check the ID by opening the device, but I have had no luck in doing this. Do you know where exactly I am supposed to open to find the card(what is a dang cover...)?

 

I would be sure that your card cannot be made to work under osx before buying more hardware. For example if you have a 1520, it may be as simple as fixing the pci id to match against the existing broadcom driver.

 

Do you mean "can be made to work"? How would I go about fixing the PCI ID?

[bcc9]

Under PCI Cards in System Profile, it reads "This computer does not appear to have any PCI cards installed." I have googled how to check the ID by opening the device, but I have had no luck in doing this. Do you know where exactly I am supposed to open to find the card(what is a dang cover...)?

I didn't say to check under PCI cards. It's probably under "Ethernet Cards".

Looking under windows is probably the easiest if you're having trouble with system profiler.

Cover, as in the base cover held on with 10 screws.

Do you mean "can be made to work"? How would I go about fixing the PCI ID?

No, I mean cannot, just as I wrote.

Fixing the id: as in modifying the pci match clause in the Info.plist for the driver that should be supporting your hardware.

[SPLITER]

I'm just slightly confused:

 

I would be sure that your card cannot be made to work under osx before buying more hardware.

You're telling me that I cannot make my card to work under OS X, and you're suggesting that I buy "more hardware," as in a new LAN card if I want to get this working.

 

For example if you have a 1520, it may be as simple as fixing the pci id to match against the existing broadcom driver.

Then you tell me that I CAN make my card work under OS X(withOUT buying new hardware) through a simple method of altering the PCI ID in a "Info.plist" file (please specify where I am supposed to find this).

 

 

 

Additionally, here is the information I have found under "Ethernet Cards":

Type: Ethernet Controller
Bus: PCI
Vendor ID: 0x10de
Device ID: 0x0ab0
Subsystem Vendor ID: 0x1028
Subsystem ID: 0x0271
Revision ID: 0x00b1

 

There is no "PCI ID" as you have been referring to, but I am guessing that it is "0x0ab0," labelled Device ID - correct me if I am wrong. Which Info.plist do I modify to get this working?

[kelobb]

Hi,

bcc9 - 1520 device is still problematic device - and adding dev id to plist gives "nothing" and card is not functioning.

 

Spliter - install lspci (from www.osx86.es) and it will tell you what kinf of hardware you have (lspci -nn).

 

That card from dell store is perfect.

 

Regards

[SPLITER]

Hi,

bcc9 - 1520 device is still problematic device - and adding dev id to plist gives "nothing" and card is not functioning.

 

Spliter - install lspci (from www.osx86.es) and it will tell you what kinf of hardware you have (lspci -nn).

 

That card from dell store is perfect.

 

Regards

 

 

Thanks for the information kelobb! This is the output received from the "lspci -nn" command:

06:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g [14e4:4315] (rev 01)

 

I'm going to need some help here again, because I can't quite tell what is what... but if I'm correct, I own a "Broadcom Corporation BCM4312 802.11b/g," which should work under the assumption that all broadcom cards work. Am I right?

[pmcnano]

SPLITER, your card sshould be able to handle it. Then again, I will give you an insight in your conversation with bcc9.

 

He meant, that you should make sure the card will not work before buying something else (was an advice..) then he SUGGESTED trying to inject the id to the info.plist, thats all, dont get all confused. Anyway, your problem should be fixable, let me upload a kext for you! one second.

 

Edit, ok SPLITER, put this in E/E repair permisions, aka in terminal:

 

sudo -s
cd /Extra/Extensions
chown -R 0:0 *
chmod -R 755 *

 

Then restart =) there you go

 

BroadcomFix.kext.zip

[SPLITER]

SPLITER, your card sshould be able to handle it. Then again, I will give you an insight in your conversation with bcc9.

 

He meant, that you should make sure the card will not work before buying something else (was an advice..) then he SUGGESTED trying to inject the id to the info.plist, thats all, dont get all confused. Anyway, your problem should be fixable, let me upload a kext for you! one second.

 

Edit, ok SPLITER, put this in E/E repair permisions, aka in terminal:

 

sudo -s
cd /Extra/Extensions
chown -R 0:0 *
chmod -R 755 *

 

Then restart =) there you go

 

BroadcomFix.kext.zip

 

Hugs and kisses my man! It worked! Thanks, pmcnano, bcc9, and kelobb!

But if wireless works, bluetooth should too right? How would I get that working?

[olegpronin]

Hugs and kisses my man! It worked! Thanks, pmcnano, bcc9, and kelobb!

But if wireless works, bluetooth should too right? How would I get that working?

 

 

For bluetooth use bcc9 work, in first post in this thread

[SPLITER]

For bluetooth use bcc9 work, in first post in this thread

 

Well, I installed that but theres no Bluetooth settings in System Preferences, and when I open "Bluetooth File Exchange" I receive a "No Bluetooth Hardware Found" error.

[bcc9]

Hi,

bcc9 - 1520 device is still problematic device - and adding dev id to plist gives "nothing" and card is not functioning.

Apparently not as that's exactly the effect of the posted BroadcomFix.kext.zip which solved his problem.

 

Oh and Thanks pmcnano for clarifying.

[kelobb]

Bcc9 - Spliter has got 1515 card not 1520 - so his plist in Airport's kext has to been upgraded by the script or manualy.

What I have to say is to avoid 1520 card until somebody will patch another kext (AppleAirPortBrcm43224.kext) to support 1520 card.

 

We will see - it's question of time maybe.

 

_regards

[bcc9]

Bcc9 - Spliter has got 1515 card not 1520 - so his plist in Airport's kext has to been upgraded by the script or manualy.

What I have to say is to avoid 1520 card until somebody will patch another kext (AppleAirPortBrcm43224.kext) to support 1520 card.

 

We will see - it's question of time maybe.

 

_regards

I see I need to clarify further.

Spliter has some broadcom card that is apparently not automatically matched by the existing broadcom drivers' pci match clauses. Said drivers have worked just fine and matched against the dell wireless 1510 card automatically for others. I still do not know the exact part number spliter has, he never reported it. I'm guessing it's a dell branded mini pci card but even that's not a given. Yet, as I correctly guessed even without knowing what hardware pci id he had, updating the I/O kit match clauses to match against his hardware's PCI id solves his problem.

 

Updating AppleAirPortBrcm43224.kext to match additional hardware is likely just as trivial as what was posted so I believe it's wrong to steer someone into buying new hardware before such options are explored. It was bum advice in this case at least.

[pmcnano]

@bcc9 he did posted his ID hahaha he posted the lspci -nn log! haha =P rawr! Anyway, he has some other card indeed, not sure wtf! Anyway, its working, anddd

 

SPLITER: Install the bluetooth fix in S/L/E folder not in E/E.

 

and ..again

 

 

@bcc9: a while ago since I moved anything to my laptop, afaik im updated to this thread but..Im not sure why, I can sleep my computer only once!..Close lid, it will sleep perfectly. Open lid wakes perfectly, Close lid again, it wont sleep anymore and shutdown will not work either after that first sleep! Just let me know if you experience the same

 

Thanks man! Nice talking to you again haha

[bcc9]

@bcc9 he did posted his ID hahaha he posted the lspci -nn log! haha =P rawr! Anyway, he has some other card indeed, not sure wtf! Anyway, its working, anddd

Right, we have the PCI id finally, but still don't know what the part # was. Oh well, nice find on the injector kext.

From google it looks like it probably is a dell wireless 1397.

@bcc9: a while ago since I moved anything to my laptop, afaik im updated to this thread but..Im not sure why, I can sleep my computer only once!..Close lid, it will sleep perfectly. Open lid wakes perfectly, Close lid again, it wont sleep anymore and shutdown will not work either after that first sleep! Just let me know if you experience the same

 

Thanks man! Nice talking to you again haha

After the first resume from suspend, the firewire controller loses its GUID. This gets logged over&over and the logging keeps the system from suspending (I know, stupid behavior, but...). You can see that the logging is the problem by turning off syslog (you'll see that fixes it). Personally I do:

#!/bin/bash
  sle=/System/Library/Extensions/IOFireWireFamily.kext/Contents/PlugIns
  mv $sle/AppleFWOHCI.kext $sle/AppleFWOHCI.kext.good

Which avoids the problem.

If someone has a fix for the GUID problem that'd obviously be a lot better. I do use firewire once in a while.

 

The same syslog preventing suspend problem happens with the AppleHDA assertion messages, anyone have the assertion messages fixed?

[pmcnano]

I made the injector myself! Found a guide a long time ago somewhere, dont remember where though. I think there was a DSDT fix for the firewire, I will try to look into it, will check. Anyway, since im bored, im updating to 10.6.4..rawr

[bcc9]

I made the injector myself! Found a guide a long time ago somewhere, dont remember where though. I think there was a DSDT fix for the firewire, I will try to look into it, will check. Anyway, since im bored, im updating to 10.6.4..rawr

Ah great. I saw there were a few Broadcomfix.kext's floating around already so I thought it was just a copy.

[kelobb]

Bcc9 - You a right, I forgot to check - Spliter has got the same card that I had - 1397 (only b/g), and this card id (4315) it's not listed in original apple kext plist. So to finish the thread - 1397 (and older 139X), 1510 and 1515 works well in OSX, 1520 not (yet).

 

I noticed the same firewire problems with second sleep - I got sometimes crazy KP after sleep from voodoohda (latest russian beta) but not always 1 per 3 wakeups - maybe later version of voodoohda will fix this.

 

Anyway, thanks for discussion

Regards

[pmcnano]

Ok bcc9, seems you are still here, I have been working on firewire (for once, I can say I helped on the development of the laptop, please LET BCC9 CHECK THIS FIRST but I think I fixed the firewire issue, by this I mean THE SLEEP ISSUE not the GUID, guid seems to still be {censored}ed up but I just slept and wake my laptop..maybe..5 times in a row without a problem.

 

You will see that on boot, you will get instead of PCI firewire, "onboard firewire".

 

I added the Firewire to the DSDT =)!RAWRAWR! LEt me know what you think and please check the sleep thing! I will try sleeping and waking again without my just made dsdt to check its actually my work.

 

 

 

Archive.zip

 

edit: MEH! Autoestime down =( I didnt do a {censored}, though it IS detected like onboard now, it doesnt change anything at all! I just *discovered* (I Guess everyone else noticed this yet..) but..wtf if you are on AC Adapter you can sleep/wake as many times as you want, but.....with battery still only once, and then no shutdown/restart.

 

In the other side, if you are on AC sleep wake unplug you can sleep/wake on battery as many times as you want also!

 

That sucks balls! LOL

 

Anyway, it sucks just being able to sleep once..

 

Cheers! and sorry =( Made an effort here, didnt work though

[bcc9]

Ok bcc9, seems you are still here, I have been working on firewire (for once, I can say I helped on the development of the laptop, please LET BCC9 CHECK THIS FIRST but I think I fixed the firewire issue, by this I mean THE SLEEP ISSUE not the GUID, guid seems to still be {censored}ed up but I just slept and wake my laptop..maybe..5 times in a row without a problem.

 

You will see that on boot, you will get instead of PCI firewire, "onboard firewire".

 

I added the Firewire to the DSDT =)!RAWRAWR! LEt me know what you think and please check the sleep thing! I will try sleeping and waking again without my just made dsdt to check its actually my work.

 

 

 

Archive.zip

 

edit: MEH! Autoestime down =( I didnt do a {censored}, though it IS detected like onboard now, it doesnt change anything at all! I just *discovered* (I Guess everyone else noticed this yet..) but..wtf if you are on AC Adapter you can sleep/wake as many times as you want, but.....with battery still only once, and then no shutdown/restart.

 

In the other side, if you are on AC sleep wake unplug you can sleep/wake on battery as many times as you want also!

 

That sucks balls! LOL

So yeah, with that change I don't notice anything different except that the firewire controller is showing up as built-in.

Same GUID error messages as before (as per post #1), and so the system doesn't sleep.

 

AC vs battery makes no difference in my experience.

 

Anyway, it sucks just being able to sleep once..

 

Cheers! and sorry =( Made an effort here, didnt work though

Well my workaround does allow the system to auto sleep over&over...

[pmcnano]

Well I dont know whats up inmy system, but If I sleep the first time on AC wake up and unplug I can sleep over and over again!