Feedback on Nvidia 0.1a alpha driver release

munky · September 23, 2005

cant wait for release 0.2!

Stratus Fear · September 23, 2005

put pci10de,e2 that worked for me

Yes, this is correct. Don't put the leading zeros, for a device id or vendor id.

Swad · September 23, 2005

Btw, i wonder why this thread was moved from the "Drivers" board to the "Technical Work". I see the drivers board full of threads like "no driver for this, no driver for that other", we are working on a driver and the thread is moved to a no popular board????
Makes no sense to me.

Hmm... I don't know about that one. It was probably moved due to its "work together" nature, but I'll check with the mods to see who moved it. Sorry for the inconvenience - we don't make a habit of moving the threads, and your next one will be fine in the "Drivers" section!

jordanvanbergen · September 23, 2005

2 questions/remarks:

1. How is one able to save the startup sequence if you use the verbose -v option? I'm getting a whole lot of memory allocation faults when using AppleI386PCI with the correct vendor strings (see question 2 below)? I would love to put this in a posting but I can't find the log of startup anywhere on the harddisc. So does anyone know if the startup verbose mode is logged somewhere and if yes, where?

2. How to get the AGP thing working without memory allocation errors:

Using system profiler I saw:

PCI Cards

GeForce FX Go5700:

Name: display

Type: VGA-Compatible Controller

Bus: PCI

Slot: PCI Slot 1

Vendor ID: 0x10de

Device ID: 0x0347

Subsystem Vendor ID: 0x1025

Subsystem ID: 0x006e

Revision ID: 0x00a1

If I put in Info.plist

of

I can see that during startup the system is trying to startup AppleI386AGP but with a lot (and I mean a lot ;-) error messages scrolling over the display ;-) LOL. After 20 seconds or so I get a PANIC ;-(

So the AGP won't load if you ask me and I get the following error messages:

extension ".........IPGraphicsFamily" cannot be found

Can't determine dependencies for com.free.driver.NVIDIA

Couldn't alloc class "NVIDIA"

AppleI386AGP: bad bridge bus numbering, no room to fix, bailing out!

AppleI386AGP: cardbus memory allocation failed

Panic (CPU 0 caller 0xC180F1E)

Debugger called: <panic>

End of story. I have to use MacDrive to fix the Info.plist to make OSX(86) start again. Starting in single mode doesn't do the trick. So if I hadn't have MacDrive installed I would have to re install everything ;-) But thank god I did.

Anyone with the same problem(s) and able to fix them or anyone else with a solution for the above?

In Windows I can see that there are 2 items sharing memory. Maybe this is why the thing won't work (yet) in macOSX(86)? See what windows info tells me:

Processor: GeForce FX Go5700

IRQ: 16

BIOS: 4.36.20.46.04

Adapter information

Bus: AGP 8X

Memory: 64 MB

Sharing resources:

Resource Device

I/O Port 0x000003C0-0x000003DF VIA CPU to AGP2.0/AGP3.0 Controller

I/O Port 0x000003C0-0x000003DF NVIDIA GeForce FX Go5700

Memory Address 0xC1000000-0xC1FFFFFF VIA CPU to AGP2.0/AGP3.0 Controller

Memory Address 0xC1000000-0xC1FFFFFF NVIDIA GeForce FX Go5700

Memory Address 0xE0000000-0xEFFFFFFF VIA CPU to AGP2.0/AGP3.0 Controller

Memory Address 0xE0000000-0xEFFFFFFF NVIDIA GeForce FX Go5700

Memory Address 0xA0000-0xBFFFF PCI bus

Memory Address 0xA0000-0xBFFFF VIA CPU to AGP2.0/AGP3.0 Controller

Memory Address 0xA0000-0xBFFFF NVIDIA GeForce FX Go5700

I/O Port 0x000003B0-0x000003BB VIA CPU to AGP2.0/AGP3.0 Controller

I/O Port 0x000003B0-0x000003BB NVIDIA GeForce FX Go5700

So the memory is shared and that's why it's called a AGP bridge I assume? but as explained above I get a lot of error messages when starting.

Anyone with the same problem(s) and able to fix them or anyone else with a solution for the above?

Regards

Jordan

myzar · September 23, 2005

ehehe via chipset that thing is problematic under anyos

<string>pci10de,347</string> is wrong for sure 10de is nvidia

dunno if <string>pci1025,6e</string> is correct for the via agp bridge if it is then it can't be helped

Chebyshev · September 23, 2005

2 questions/remarks:

1. How is one able to save the startup sequence if you use the verbose -v option? I'm getting a whole lot of memory allocation faults when using AppleI386PCI with the correct vendor strings (see question 2 below)? I would love to put this in a posting but I can't find the log of startup anywhere on the harddisc. So does anyone know if the startup verbose mode is logged somewhere and if yes, where?

2. How to get the AGP thing working without memory allocation errors:

Using system profiler I saw:

PCI Cards

GeForce FX Go5700:

Name: display

Type: VGA-Compatible Controller

Bus: PCI

Slot: PCI Slot 1

Vendor ID: 0x10de

Device ID: 0x0347

Subsystem Vendor ID: 0x1025

Subsystem ID: 0x006e

Revision ID: 0x00a1

If I put in Info.plist

<string>pci10de,347</string>

of

<string>pci1025,6e</string>

I can see that during startup the system is trying to startup AppleI386AGP but with a lot (and I mean a lot ;-) error messages scrolling over the display ;-) LOL. After 20 seconds or so I get a PANIC ;-(

So the AGP won't load if you ask me and I get the following error messages:

extension ".........IPGraphicsFamily" cannot be found

Can't determine dependencies for com.free.driver.NVIDIA

Couldn't alloc class "NVIDIA"

AppleI386AGP: bad bridge bus numbering, no room to fix, bailing out!

AppleI386AGP: cardbus memory allocation failed

Panic (CPU 0 caller 0xC180F1E)

Debugger called: <panic>

End of story. I have to use MacDrive to fix the Info.plist to make OSX(86) start again. Starting in single mode doesn't do the trick. So if I hadn't have MacDrive installed I would have to re install everything ;-) But thank god I did.

Anyone with the same problem(s) and able to fix them or anyone else with a solution for the above?

In Windows I can see that there are 2 items sharing memory. Maybe this is why the thing won't work (yet) in macOSX(86)? See what windows info tells me:

Processor: GeForce FX Go5700

IRQ: 16

BIOS: 4.36.20.46.04

Adapter information

Bus: AGP 8X

Memory: 64 MB

Sharing resources:

Resource Device

I/O Port 0x000003C0-0x000003DF VIA CPU to AGP2.0/AGP3.0 Controller

I/O Port 0x000003C0-0x000003DF NVIDIA GeForce FX Go5700

Memory Address 0xC1000000-0xC1FFFFFF VIA CPU to AGP2.0/AGP3.0 Controller

Memory Address 0xC1000000-0xC1FFFFFF NVIDIA GeForce FX Go5700

Memory Address 0xE0000000-0xEFFFFFFF VIA CPU to AGP2.0/AGP3.0 Controller

Memory Address 0xE0000000-0xEFFFFFFF NVIDIA GeForce FX Go5700

Memory Address 0xA0000-0xBFFFF PCI bus

Memory Address 0xA0000-0xBFFFF VIA CPU to AGP2.0/AGP3.0 Controller

Memory Address 0xA0000-0xBFFFF NVIDIA GeForce FX Go5700

I/O Port 0x000003B0-0x000003BB VIA CPU to AGP2.0/AGP3.0 Controller

I/O Port 0x000003B0-0x000003BB NVIDIA GeForce FX Go5700

So the memory is shared and that's why it's called a AGP bridge I assume? but as explained above I get a lot of error messages when starting.

Anyone with the same problem(s) and able to fix them or anyone else with a solution for the above?

Regards

Jordan

You need to put in the information for your PCI to AGP bridge, not your video card (that info goes in NVidia.text). You can get the information here www.pcidatabase.com. Your vendor ID is 0x1106 (VIA) and you can find the rest from there. The string you need to add would be pci1106,<device id>. Hope this helps.

jordanvanbergen · September 23, 2005

Thank you for the reply:

>Your vendor ID is 0x1106 (VIA) and you can find the

>rest from there. The string you need to add would be

>pci1106,<device id>. Hope this helps.

I found out the following already using Windows:

PCI\VEN_1106&DEV_B188

So it should be B188, more info:

0xB188 Chip Description: PCI-to-PCI Bridge (AGP 2.0/3.0)

Notes: K8HTB chipset

Okay, So I edited the string to:

cleared the kext cache, rebooted with -v option. See all the kext that are loaded again scrolling over my windows, my systems starts but system profiler shows PCI instead of AGP and the kext is not loaded.

What AppleI386PCI.kext do I need to use? The standard one from tiger-x86, the open darwin v8.0.1 or the one that is on this forum and that's 372 KB. big?

Any other suggestions or ideas? Really appreciate the feedback!

Regards

Jordan

matiseijas · September 23, 2005

You need to put in the information for your PCI to AGP bridge, not your video card (that info goes in NVidia.text). You can get the information here www.pcidatabase.com. Your vendor ID is 0x1106 (VIA) and you can find the rest from there. The string you need to add would be pci1106,<device id>. Hope this helps.

Can you help me out here a little bit; my vendor ID is: 1039, so I went to www.pcidatabase.com and entered the vendor number ID and a huge list of devices appeared, the thing is i'm not sure which one of those Devices ID to use.

Can somebody help me plz?? Thx!!

jordanvanbergen · September 23, 2005

I have a working AGP environment now thanks to all the help from you!!! Don't see any difference for now but I assume it's important to see AGP listed as I know I couldn't get my card installed correctly under windows when the Via Chipset AGP to PCI was not installed. So hopefully this will help me with futher driver versions for the NVidia cards.

By the way: I started up using "platform=X86PC" and suddenly AGP appeared. rebooted and now with normal startup and it staid there. Could it be that starting once with "platform=X86PC" helped me seeing Bus: AGP?

This is what I have now:

GeForce FX Go5700:

Chipset Model: GeForce FX Go5700

Type: VGA-Compatible Controller

Bus: AGP

Vendor: nVIDIA (0x10de)

Device ID: 0x0347

Revision ID: 0x00a1

Displays:

Display:

Resolution: 1024 x 768

Depth: 32-bit Color

Core Image: Not Supported

Main Display: Yes

Mirror: Off

Online: Yes

Quartz Extreme: Not Supported

Thanks to everyone placing replies.

Regards

Jordan

macgirl · September 23, 2005

I also modified the Info.plist of the AppleI386PCI.kext, it loads even that I have no AGP card, but in windows shows PCI2PCI Bridge, the NVIDIA kext loads even if the AppleI386PCI doesn't load.

munky · September 23, 2005

jordanvanbergen and others with problems:

did you remove the NVidia alpha driver and reboot? this helped me get AGP recognised. after that i reinstalled NVidia alpha driver and rebooted and got card recognised as well as Bus: AGP

DiegoMax · September 23, 2005

Hmm... I don't know about that one. It was probably moved due to its "work together" nature, but I'll check with the mods to see who moved it. Sorry for the inconvenience - we don't make a habit of moving the threads, and your next one will be fine in the "Drivers" section!

Thanks a lot Mashugly, really appreciated.

omni · September 23, 2005

Hey Diego

Good work on the project so far, I'm just wondering when are you guys going to put up something on the CVS so the rest of us can take a peek?

thanks

Ke0 · September 24, 2005

I'm still lost, I have a MSI Neo Platinum 2, and that's a Nforce 3 board, so mine should read pci10de,e2 Correct? There are two lines of pci already entered, do I just delete one, and replace the other with pci10de,e2?

JaS · September 24, 2005

I'm still lost, I have a MSI Neo Platinum 2, and that's a Nforce 3 board, so mine should read pci10de,e2 Correct? There are two lines of pci already entered, do I just delete one, and replace the other with pci10de,e2?

Yes you can do edit it like that

omni · September 24, 2005

I dont understand why is everyone having so much problems with detection of their cards...

Simply edit the Info.plist and change the parameter to a wide mask:

The later number is the mask; ffff makes 0x10de unchangable, but why would you want to change it - it's the NVIDIA Vendor ID. All you really want is the wide Device ID mask, and in my example 0000 will match anything and everything under the Sun from NVIDIA.

i1sam · September 24, 2005

Same here folks:

Chipset Model: GeForce 5900

Type: VGA-Compatible Controller

Bus: AGP

Vendor: nVIDIA (0x10de)

Device ID: 0x0331

Revision ID: 0x00a1

Displays:

Display:

Resolution: 1280 x 1024

Depth: 32-bit Color

Core Image: Not Supported

Main Display: Yes

Mirror: Off

Online: Yes

Quartz Extreme: Not Supported

I've tried an xBench before and after in opengl and graphics (not quatrz extreme) and the average score is the same: about 54/55.

I didn't noticed any change. But the most strange is that System Profiler still says "No kext loaded"

Anyway, i think that's something amazing already and soon we'll be able to have full support.

wow!!! how didyou manage to get the resolution above by 1024 by 768...

hope you can share the idea.. i having a nvidia Geforce FX 5200 128MB 128bit card..

Stefan Wouters · September 24, 2005

wow!!! how didyou manage to get the resolution above by 1024 by 768...

hope you can share the idea.. i having a nvidia Geforce FX 5200 128MB 128bit card..

Try this: Messing with the boot options.

jordanvanbergen · September 24, 2005

jordanvanbergen and others with problems:

did you remove the NVidia alpha driver and reboot? this helped me get AGP recognised. after that i reinstalled NVidia alpha driver and rebooted and got card recognised as well as Bus: AGP

No, I didn't remove the NVidia alpha driver. I removed the following files before a reboot:

/System/Library/Extensions/Extensions.kextcache

/System/Library/Extensions/Extensions.mkext

So the kextcache is empty. Now I reboot my machine to reload ALL kext (drivers?) all over again. This helped me to test the AppleI386PCI Info.plist settings without having to delete the NVidia.kext. After trying a lot of <strings> settings and after booting once with "platform=X86PC" the BUS: AGP suddenly showed.

So, no I didn't remove the NVidia alpha driver to get AGP working.

Regards

Jordan

wiebeest · September 24, 2005

{censored}, I can't seem to get it right.

NVidia Geforce 6600 PCIe (Leadtek WinFast px6600td 256mb)

In Windows:

DirectDiag:

---------------

Display Devices

---------------

Card name: NVIDIA GeForce 6600

Manufacturer: NVIDIA

Chip type: GeForce 6600

DAC type: Integrated RAMDAC

Device Key: Enum\PCI\VEN_10DE&DEV_0141&SUBSYS_2001107D&REV_A2

Display Memory: 256.0 MB

Current Mode: 1024 x 768 (32 bit) (85Hz)

Monitor: SONY HMD-A220

Monitor Max Res: 1280,1024

Driver Name: nv4_disp.dll

Driver Version: 6.14.0010.7777 (English)

DDI Version: 9 (or higher)

Driver Attributes: Final Retail

Driver Date/Size: 7/20/2005 21:07:00, 3908864 bytes

WHQL Logo'd: n/a

WHQL Date Stamp: n/a

VDD: n/a

Mini VDD: nv4_mini.sys

Mini VDD Date: 7/20/2005 21:07:00, 3198368 bytes

Device Identifier: {D7B71E3E-4201-11CF-AC6D-0B0003C2CB35}

Vendor ID: 0x10DE

Device ID: 0x0141

SubSys ID: 0x2001107D

Revision ID: 0x00A2

In OS X:

Profiler -->Display:

Type: VGA-Compatible Controller

Bus: PCI

Vendor ID: 0x15ad

Device ID: 0x0405

Revision ID: 0x0000

Kernel Extension Info: No Kext Loaded

So I'd say I should edit the .plist to 0x040515ad --> no show.

But then I notice that NVidia = 10de --> I change it to 0x040510de. Still no show.

What puzzles me is that under Windows DirectX gives me different ID's than OS X does; VEN_10DE&DEV_0141. Shouldn't ID's be the same in osx & windows (since the ID's are substracted from the GPU's hardware?)

What am I doing wrong here? Or perhaps my card not supported yet? Should I try to change it to the windows ID's? Or do I risk OSX no longer booting?

Any advice would be very welcome.

i1sam · September 24, 2005

Try this: Messing with the boot options.

Thanks a mucho Stefan.... it WORKs... i copy the file to another location... edit it there and paste the edited file to the original location and restart....

now i have a 1280x1024x32@85 display..

cool!!!

jordanvanbergen · September 24, 2005

{censored}, I can't seem to get it right.
Device Key: Enum\PCI\VEN_10DE&DEV_0141&SUBSYS_2001107D&REV_A2

So I'd say I should edit the .plist to 0x040515ad --> no show.

But then I notice that NVidia = 10de --> I change it to 0x040510de. Still no show.

What puzzles me is that under Windows DirectX gives me different ID's than OS X does; VEN_10DE&DEV_0141. Shouldn't ID's be the same in osx & windows (since the ID's are substracted from the GPU's hardware?)

What am I doing wrong here? Or perhaps my card not supported yet? Should I try to change it to the windows ID's? Or do I risk OSX no longer booting?

Any advice would be very welcome.

Try:

<key>IOPCIMatch</key>

After saving the Info.plist from the NVidia.kext Contents directory make sure all directories have the correct user permissions:

root:wheel /NVidia.kext/ ... ....

After this clear the extension cache, delete the files:

/System/Library/Extensions.kextcache

/System/Library/Extensions.mkext

And reboot. Hopefully it will function now!

Regards

Jordan

wiebeest · September 24, 2005

NVidia Geforce 6600 PCIe (Leadtek WinFast px6600td 256mb)

So I'd say I should edit the .plist to 0x040515ad --> no show.

But then I notice that NVidia = 10de --> I change it to 0x040510de. Still no show.

What puzzles me is that under Windows DirectX gives me different ID's than OS X does; VEN_10DE&DEV_0141. Shouldn't ID's be the same in osx & windows (since the ID's are substracted from the GPU's hardware?)

Problem solved: the nvidia.kext only works if you run osx natively.

Under MVware: 0x040515ad, same osx natively: 0x014110de,

same as under windows and editing the Info.plist to that code lead to this:(see attachment)

macgirl · September 24, 2005

Problem solved: the nvidia.kext only works if you run osx natively.
Under MVware: 0x040515ad, same osx natively: 0x014110de,

same as under windows and editing the Info.plist to that code lead to this:(see attachment)

Of course, Video Card in VMWare is emulated and not the real one. If you install windows in VMWare it asks for the VMWare Video Driver.

Casab · September 24, 2005

Success with kext and agp here as well.

I edited the info.plist from macvidia's nvidia.kext so that it contains my graphics device id from system profiler, then did the wheel on it.

Next I got applei386pci.kext (thank you for that JaS :rolleyes: ) and changed the pci string to the one I found in windows (cpu to agp). I did chmod, the wheel and kextload on that one, rebooted and I got agp I didn't even had to remove the nvidia.kext or boot on x86pc platform, it just worked after reboot.

QE doesn't work yet and I still can't change the screen res with system preferences, but I believe agp supported will come in handy for the future

Feedback on Nvidia 0.1a alpha driver release

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites