PDA

View Full Version : Problems with OpenGL and Ethernet, help


fatbastard7904
03-03-05, 05:13 AM
Hi!

I own a Quadro FX 4000 in a Windows XP system.
Everytime I start an application which uses OpenGL (e.g. Maya or Blender or a C++-Program with OpenGL statments) it takes 25 to 30 seconds to initalize OpenGL (no output at this time, application "freezes").
I detected that this problem is caused by any active Ethernet card in the system!
If I deactivate the Ethernet drivers, the problem is gone and the apps starts immediately.
To change the Ethernet card has no effect.
I tried different Quadro drivers too.

Anybody knows such a problem with any NVidia card or with the Quadro drivers and can help my?
Maybe a problem with a Novell network?

Please help.

Bye
Harald

retsam
03-07-05, 06:47 PM
Hi!

I own a Quadro FX 4000 in a Windows XP system.
Everytime I start an application which uses OpenGL (e.g. Maya or Blender or a C++-Program with OpenGL statments) it takes 25 to 30 seconds to initalize OpenGL (no output at this time, application "freezes").
I detected that this problem is caused by any active Ethernet card in the system!
If I deactivate the Ethernet drivers, the problem is gone and the apps starts immediately.
To change the Ethernet card has no effect.
I tried different Quadro drivers too.

Anybody knows such a problem with any NVidia card or with the Quadro drivers and can help my?
Maybe a problem with a Novell network?

Please help.

Bye
Harald

this sounds like its some sort of irq problem ... or dma .... you should see if you can get newer drivers for you nic. also assign an irq in your bios for the pci slot ...

saturnotaku
03-07-05, 06:50 PM
Not only new NIC drivers, but also he should try moving the ethernet card to a different PCI slot. Or, if he's using an onboard solution, to disable it via the BIOS and try a PCI one. It definitely sounds like an IRQ sharing problem.

I also wouldn't put it past anyone that the problem could be Novell related. I hate Novell networks with a passion.

retsam
03-08-05, 05:05 AM
Maybe a problem with a Novell network? oh man i didnt notice that part .... this could very well be your cause .... but are you running novell or just a novell network on windows ?