Jump to content

Studio XPS 13

digital8

By digital8,
in OSx86 10.5 (Leopard)

 Share
222 posts in this topic

Recommended Posts

bcc9
bcc9
Posted
Posted
Mine has the 9500M option.
Ok, I'm guessing that the two video parts are sharing the same PCI bridge and the dynamic memory reallocation is not going so well with this combination.

 

Do you have linux? Can you do:

lspci -nnv

and

cat /sys/devices/pci0000:00/0000:00:10.0/0000:03:00.0/resource

and I think

cat /sys/devices/pci0000:00/0000:00:10.0/0000:02:00.0/resource

 

Also when the grey screen is still up, does it seem like booting has completed?

If you could then hit the power button followed by enter to shutdown the system then it's probably booted ok except the VRAM has been moved to some new address.

Link to comment
Share on other sites
dalma
dalma
Posted
Posted
Ok, I'm guessing that the two video parts are sharing the same PCI bridge and the dynamic memory reallocation is not going so well with this combination.

 

Do you have linux? Can you do:

lspci -nnv

and

cat /sys/devices/pci0000:00/0000:00:10.0/0000:03:00.0/resource

and I think

cat /sys/devices/pci0000:00/0000:00:10.0/0000:02:00.0/resource

 

Also when the grey screen is still up, does it seem like booting has completed?

If you could then hit the power button followed by enter to shutdown the system then it's probably booted ok except the VRAM has been moved to some new address.

 

Thanks for the help,

Here is my info:

cat /sys/devices/pci0000:00/0000:00:10.0/0000:03:00.0/resource

0x00000000aa000000 0x00000000aaffffff 0x0000000000000200

0x00000000b0000000 0x00000000bfffffff 0x000000000000120c

0x0000000000000000 0x0000000000000000 0x0000000000000000

0x00000000cc000000 0x00000000cdffffff 0x000000000000120c

0x0000000000000000 0x0000000000000000 0x0000000000000000

0x0000000000005000 0x000000000000507f 0x0000000000000101

0x00000000c0000000 0x00000000c001ffff 0x0000000000007202

 

cat /sys/devices/pci0000:00/0000:00:10.0/0000:02:00.0/resource

cat: /sys/devices/pci0000:00/0000:00:10.0/0000:02:00.0/resource: No such file or directory

 

Attached is my lspci output.

 

When the grey screen comes up, it does appear like its booted up fine.

lspci.txt

Link to comment
Share on other sites
bcc9
bcc9
Posted
Posted

Dalma- Wow, that's pretty different from what I get. Looks like you're getting the expansion ROM mapped correctly under linux, without any problems:

[virtual] Expansion ROM at c0000000 [disabled]

I don't get that. What version&distro of linux are you using? Can you try one more thing:

 

od -tx4 /sys/devices/pci0000:00/0000:00:10.0/0000:03:00.0/config

?

and without my IOPCIFamily change, under osx:

 

ioreg -n NVDA -r -l -t -x -w900

 

So that we can compare what memory is getting mapped under OSX for the video card with your working linux map. We'd want to look at what is showing up under "IODeviceMemory" and "assigned-addresses" for the video card.

Link to comment
Share on other sites
dalma
dalma
Posted
Posted
Dalma- Wow, that's pretty different from what I get. Looks like you're getting the expansion ROM mapped correctly under linux, without any problems:

[virtual] Expansion ROM at c0000000 [disabled]

I don't get that. What version&distro of linux are you using? Can you try one more thing:

 

od -tx4 /sys/devices/pci0000:00/0000:00:10.0/0000:03:00.0/config

?

and without my IOPCIFamily change, under osx:

 

otool -n NVDA -r -l -t -x -w900

 

So that we can compare what memory is getting mapped under OSX for the video card with your working linux map. We'd want to look at what is showing up under "IODeviceMemory" and "assigned-addresses" for the video card.

 

Hi, I am using RHEL 5 as my linux OS. Here is the output:

 

od -tx4 /sys/devices/pci0000:00/0000:00:10.0/0000:03:00.0/config

0000000 086610de 00100007 030000b1 00000000

0000020 aa000000 b000000c 00000000 cc00000c

0000040 00000000 00005001 00000000 02711028

0000060 00000000 00000060 00000000 00000105

0000100 02711028 00000000 00000000 00000000

0000120 00000001 00000001 0023d6ce 00000000

0000140 00026801 00000000 00800005 00000000

0000160 00000000 00000000 00000000 00000000

*

0000220 33000000 00000083 00005793 8000000f

0000240 00000000 00000000 00000000 00000000

*

0000360 00000000 0008ff00 00010000 00000000

0000400

 

I'll get the other output once I get back into OSX and I will post that one later.

 

Thanks

Link to comment
Share on other sites
dalma
dalma
Posted
Posted

Hi bcc9, I got xcode install and ran your otool command, but there were some switches that were not recognized.

 

It didn't like the -n, -w, -x switches. When I removed them it then complained about:

otool: can't open file: NVDA (No such file or directory)

 

So this is where I am at now, sorry I am not much help here. Any guidance is appreciated.

Link to comment
Share on other sites
bcc9
bcc9
Posted
Posted
Hi bcc9, I got xcode install and ran your otool command, but there were some switches that were not recognized.

 

It didn't like the -n, -w, -x switches. When I removed them it then complained about:

otool: can't open file: NVDA (No such file or directory)

 

So this is where I am at now, sorry I am not much help here. Any guidance is appreciated.

Wow, sorry I was being real dyslexic, I meant ioreg not otool. ioreg should already be installed on your machine standard. Sorry about that.
Link to comment
Share on other sites
bcc9
bcc9
Posted
Posted

Anyone want to try this newer, simpler version?

It doesn't change any PCI memory assignments, it just delays when the PCI devices are connected to the io device tree. Surprisingly that alone (well with the EFI strings of course) seems to be sufficient to get QE/CI working for me.

 

Newer version here:

http://www.insanelymac.com/forum/index.php...t&p=1121723

Link to comment
Share on other sites
bcc9
bcc9
Posted
Posted
@bbc9

 

do u use a x86 tool created EFI string or did u rebuild an efi string with MBP details?

I am just using an EFI string generated with x86 tool right now; no extra entries from the MBP ioregistry.
Link to comment
Share on other sites
dalma
dalma
Posted
Posted
Anyone want to try this newer, simpler version?

It doesn't change any PCI memory assignments, it just delays when the PCI devices are connected to the io device tree. Surprisingly that alone (well with the EFI strings of course) seems to be sufficient to get QE/CI working for me.

And we have a winner. This one worked for me, now I have QI/QE working properly. Thanks for all of your help. Now we need sound and power management and we are all set.

Link to comment
Share on other sites
Japandler
Japandler
Posted
Posted

Don't forget wireless.

 

Info on Audio: I got sounds again, but they came out VERY gobbledy-gook. I don't have any more time to work on this until Spring Break starts (just 34 hours and counting! haha) but then I'll be able to devote myself to "the cause."

 

Anyone feel like writing up an "idiot-proof" way of getting the QI/QE working? ;)

Link to comment
Share on other sites
bcc9
bcc9
Posted
Posted
And we have a winner. This one worked for me, now I have QI/QE working properly. Thanks for all of your help. Now we need sound and power management and we are all set.
Awesome. Now I still wish I better understood why this change was necessary for the dell but not macbooks. Unless perhaps the macbooks ship with a special IOPCIFamily as well.

 

And, thanks for the debug info, that helped. Your ioreg output shows that your 9500m based system maps the same 3 memory regions as the 9400m (again missing the video bios section). So the fact that all 4 regions map OK under RHEL 5 linux is a bit of an anomaly. The linux folks have been changing the PCI assignment code around a lot lately in 2.6.27, they probably broke something. I think you're running 2.6.18 with RHEL5?

In any case, this PCI assignment problem apparently wasn't what really matters after all for working QE/CI.

 

Info on Audio: I got sounds again, but they came out VERY gobbledy-gook.
For audio, I tried installing HDAEnabler.kext and an AppleHDA.kext that had been modified to use vendor/device ID 0x111d7675, and it didn't work. Under system preferences no audio input or output devices are found. What else have you had to do to get audio to start to work? Did you modify the pin configuration? When I check vista's registry for the audio driver, I don't see the pinconfig related key present that the pin config guide claims should be there for IDT drivers.

 

Since this laptop shares the same IDT device code as the dell 1535&1735, and those have working audio, you'd think this would be a slam dunk.

Link to comment
Share on other sites
rschultz101
rschultz101
Posted
Posted

dell XPS 16 with ati radeon HD 3670

 

for the xps 13, it's to close to the macbook, to consider the trouble

 

but a xps 16 with an HD screen, that be a consideration

since the 15 pro is rez limited,.... and the 17" is not really a laptop anymore,...

 

the ati mobility for laptops, is still a show stopper,... any news?

Link to comment
Share on other sites
bcc9
bcc9
Posted
Posted
dell XPS 16 with ati radeon HD 3670

 

for the xps 13, it's to close to the macbook, to consider the trouble

Please, a separate thread for the xps16. It has a whole different chipset so it doesn't make sense to clutter the thread here with that other model that is really only related in styling.

 

And please, the xps13 is worthy of a lot of trouble. Its hardware is superior to the macbook in I/O ports (has ESATA, expresscard, firewire, hdmi, standard displayport). Not to mention cost effective options: SSD drives (1/2 price of apple), 4GB memory standard, and so on.

Link to comment
Share on other sites
Japandler
Japandler
Posted
Posted
Please, a separate thread for the xps16. It has a whole different chipset so it doesn't make sense to clutter the thread here with that other model that is really only related in styling.

 

And please, the xps13 is worthy of a lot of trouble. Its hardware is superior to the macbook in I/O ports (has ESATA, expresscard, firewire, hdmi, standard displayport). Not to mention cost effective options: SSD drives (1/2 price of apple), 4GB memory standard, and so on.

 

Yeah yeah! XPS 13 ftw. Anywho, what's bugging me, and is possibly the problem with the whole thing, is that my "learn more about this mac" states that i have a "built in audio" but that there's still no input or output under my sound preference area. This is what caused the gobbledy-gook, i think. After look at the strings, it says there's power going to "an unknown audio device" but I can't find anything to MAKE the audio device known... I hope to figure this out on Friday or Saturday.

 

Any news at all on the wifi front?

Link to comment
Share on other sites
bcc9
bcc9
Posted
Posted

Ok I looked into fixing the IDT audio on this laptop and I'm pretty stumped. I dumped the codec details with "cat /proc/asound/card0/codec#0 > file" and compared it to the posted file for the 1735, here, http://www.insanelymac.com/forum/index.php...st&id=31468 and the two laptops share all the same nodes, node IDs and functions. There are a couple bit differences in the pincaps but I don't think those should matter as they don't define the node functions and also the AppleHDA.kext mods for the 1735 don't include pincaps in the ConfigData key in the AppleHDAController plugin.

I think this means we should be able to use the sample AppleHDA.kext as the 1535/1735 laptops, even the same pathmap entries, no? Only thing I'm confused about is why the PathMapID was set to 1 instead of 9 like it says it should be in this guide:

http://www.insanelymac.com/forum/index.php?showtopic=127819

 

I even hand built pincaps from the codec dump and added those to AppleHDAController but it didn't make a difference.

 

Anyone have a clue why audio doesn't work at all for me?

Yes I'm using the standard HDAEnabler.kext as well.

 

Codec dump attached.

audio.txt

Link to comment
Share on other sites
bcc9
bcc9
Posted
Posted
Any news at all on the wifi front?
You keep asking that :happymac: If you're asking me, I haven't bothered to try the atheros driver, and probably don't care until after these work:
  • working audio
  • working touchpad after resume
  • working power mgmt
  • touchpad gestures

Link to comment
Share on other sites
babs
babs
Posted
Posted

WiFi works here on the studio xps 13.

How?

Put a Dell wireless card mini PCIe 1390 or simular in the WWan slot.

Must startup with -v -f.

 

or

replace the 1515 with a 1510

 

for the display resolution of 1280x800 instead of 1024x768

add these lines in com.apple.Boot.plist

 

<key>Graphics Mode</key>

<string>1280x800x32</string>

 

 

Now waiting for the solution for the audio and CI/QE thanks to BCC9 for the CI/QE and audio solution :)

 

Laptop:Dell Studio XPS 13 2.4Ghz Nvidia 9500

Windows 7

Vista Home

OSX: XXX 10.5.6 final

Link to comment
Share on other sites
bcc9
bcc9
Posted
Posted
Now waiting for the solutions for the audio and CI/QE
I've already posted a kext which combined with my EFI strings recommendation provides working QE/CI. Is there something I need to make more clear?

The solution could be made foolproof by bundling into an install package like the nice one ridgeline did for the 1535/1735 but it'd be nice to get more pieces like the audio working first.

Link to comment
Share on other sites
bcc9
bcc9
Posted
Posted

Japandler,

Do you have any debug info for when audio somewhat works on your laptop?

Which applehda/hdaenabler kexts are you using? Anything logged in /var/log/system.log? I just get:

HDAEnabler: Copyright (c) 2008 by Kabyl
HDAEnabler: 05/05/2008 Added SPAudio support:Taruga
Sound assertion "0 == fInterruptSource" failed in "/SourceCache/AppleHDA/AppleHDA-157.1.24/AppleHDAController/AppleHDAController.cpp" at line 215 goto Exit1

What about your ioregistry; I'd be interested in seeing what 'ioreg -n HDEF -r -l -t -x -w900' shows. I don't get anything below the main HDEF entry like I should if AppleHDA was working properly.

Link to comment
Share on other sites
bcc9
bcc9
Posted
Posted
hiho....anything new on the audio front????

 

i will install win7 today maybe i can find a pinconfig on it.

I've taken the topic up with the folks who got audio working on the dell 1535/1575 with IDT audio, over here http://www.insanelymac.com/forum/index.php...p;#entry1107151 but still no breakthru to report.

I did already post the codec dumps from linux over there.

 

Perhaps if japandler would report on what he did to get audio working somewhat those 1 or 2 times we'd have something.

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...