pkaa

As far as I know there are 3 laptops with a Mobility Firegl T2 GPU. Two IBM models and HP NW8000. As a CAD admin we decided to go for laptops in our product development and ended up getting 20 HP NW8000 laptops. That was a bad choice.

Ati does not provide its own driver packages for mobility versions but rely on laptop manufacturers to package them. HP drivers are a year old and there were some major issues with our 3D software (Pro/E WF2). As with 99.9% of all CAD software it uses opengl not directx. But there is no way of upgrading the driver so that opengl works. Omega drivers and patjes patch work with directx but not with opengl. As discussed in these threads:

http://www.hardwareheaven.com/mobility-radeon-drivers-support/76447-opengl-omegas-work-firegl-mobility.html
http://www.hardwareheaven.com/mobility-radeon-drivers-support/72506-ati-mobility-firegl-9000-opengl.html

This did not work:
http://www.hardwareheaven.com/showthread.php?t=76447



After much wondering I came to this solution for our NW8000 machines.

-Get the CPanel directory from Catalyst drivers
-Get the DRIVERS directory from the IBM Ati Mobility driver package
-Get the Radlinker directory from Omega drivers
-Remove everything Ati related from Add / Remove programs
-Uninstall Firegl from Device Manager
-Reboot
-When windows finds new hardware point it to \DRIVER\2KXP_INF\C2_21425.INF
-After install just hit cancel on the following new hardware it finds
-Install CPanel and Radlinker
-Reboot and test Opengl

I am waiting for Omega drivers or patjes patcher to address this issue. I think it would be quite easy to reverse engineer IBM's and HP's driver packages.

Lokk

I will have to try what you have suggested. I have the same GPU as you do, in my IBM Thinkpad T42p. It can run DX, but not OpenGL :\ Hope this works!

Lokk

Couldn't get it to work, what happens is after deleting the ATI stuff (and in device manager), I restart and it automatically detects and installs drivers for the FireGL. I have my ATI/support/drivers directories deleted as well. I think is hampering me from a clean install. Any suggestions?

Stefan_VTi

The new 5.7 mobility drivers have native MFGL T2 support (including the proper GL driver)

Lokk

Yeah, I tried installing and could still not run the games, but I think that's because of my system automatically recognizing and installing the old drivers without me asking whenever I restart my computer.

The Captain

I have an NW8000 with a mobility firegl t2, and I have found that there are two driver related problems that you must fix in order to use opengl properly.

1. Unlike mobility firegl t2's in other laptops, the device id of the card in the NW8000 is the same as that of a mobility 9600/9700. So when you try to install official ATI drivers or Omega drivers, the registry entry needed for opengl to work with firegl based cards is not made. To fix this, you can either modify the device id in the .inf install file or manually add the following registry entries:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\OpenGLDrivers\atifglws]
"Version"=dword:00000002
"DriverVersion"=dword:00000001
"Flags"=dword:00000001
"Dll"="atioglxx.dll"

2. Omega's drivers use several opengl and 3d tweaks that cause problems for opengl games and applications with the mobility firegl t2. I fixed this by removing the "opengl tweaks" and "3d tweaks" sections from omega's .inf file.

After I did these things, everything worked perfectly. I'm going to try the official 5.7 mobility drivers now and see if they work.

redsolar

I am sticking this thread. Thanks for proposed solutions, pkaa. It seems like there are issues like that popping out all the time.

__________________
Real_Men_Do_Not_Use_Space_Bar

Main rig:
Intel Core i7 930 @ 4.0 Ghz | Corsair H50 Push/Pull | 12GB OCZ DDR3 | ASUS Radeon HD 5850 | 3x 1TB Samsung F3 RAID5 on Dell PERC 5i SAS + 1TB Hitachi | MSI X58 Pro-e | 850W Antec Truepower Quattro | RocketFish by Lian Li Full Tower Case | Gateway XHD3000 30" LCD | Dell 2408WFP 24" LCD | Dell 2407WFP 24" LCD | Logitech Z-5500 Speakers | Windows 7 Ultimate x64

Laptop:
Samsung x360-34P | Core 2 Duo SU9400 1.4 GHz | 4GB DDR3 | 128GB Samsung SSD | Intel 4500M w/ HDMI | WiFi | Bluetooth | 13.3" WLED 1280x800 | Windows 7 Professional x64

The Captain

I tried the official mobility drivers, but they gave me resolution problems (strange resolutions in UT, resolutions won't switch back to normal after quitting UT, etc).

So, now I am using Omega's 5.6 drivers, which work great. Here's what I did to make them work (NOTICE: only do this if you have an NW8000!).

1. I changed the device id of the mobility firegl t2 entry in the .inf file, and I commented out the entry for "ati mobility radeon 9600/9700 series" because it uses the same device id. The entry for the firegl t2 should read:
"ATI MOBILITY FIRE GL T2/T2e (Omega 2.6.42)" = ati2mtag_M10GL, PCI\VEN_1002&DEV_4E50

2. I commented out all of the entries under the "OpenGL tweaks" and "3D tweaks" sections

3. (Optional) I commented out multiple lines which provided extra resolutions, because most of the uncommon resolutions cause the NW8000 to go into panning mode when used.

For everyone's convenience, I have uploaded my modified version of Omega's inf file so that you guys can try it out. Just install Omega's catalyst 5.6 setup files as you normally would, but don't install the drivers when it gives you the option. Close out of the setup program, and copy over the regular inf file with mine in the "C:\Program Files\Radeon Omega Drivers\v2.6.42\2KXP_INF" directory. Then go to Start -> Radeon Omega Drivers -> (Re) Intall Omega Drivers.

You can download the inf file at http://www.rose-hulman.edu/~schrocml/CX2K_RAD_OMEGA.rar.

floatingkiwi

I have well, similar sorts of issues with this:

I just upgraded to the newest set of drivers from the HP website, and man, what a mistake. My frame rate in Quake 2 has dropped to 15 or so from 60-80. I reinstalled the old drivers (and did it the proper way with drivercleaner etc) but even with the old drivers the frame rate is still the same!! So I'm thinking it did something to the bios..

Tried the Omega drivers - OK but no crosshair in Quake 2.
Tried the catalyst with dhmodder 2.2 - OK but same crosshair problem.
Can't get the Rage3D tweaker 3.9 to load on the original drivers as it ends with a "not supported" error.

3D seems to be OK with either original or above mods, but I just can't get back to the original state where the HP drivers actually worked OK with OpenGL. I've even done a full reinstall.

So I guess I'm in a slightly better boat than some of you above where you can't even get OpenGL to work with this card and the modded Catalyst/omega What have you.

Lokk

Gonna try your .INF file on my T42p, hope it works

edit: didn't work, im f***ed for life

The Captain

If you have a T42p, then the device id for your mobility firegl t2 is probably 4E54 (which is what it should be - nw8000 are just strange). So go into my INF file and change the line for the mobility firegl t2 to:

"ATI MOBILITY FIRE GL T2/T2e (Omega 2.6.42)" = ati2mtag_M10GL, PCI\VEN_1002&DEV_4E54

floatingkiwi

Hi Captain

I tried your modified inf as well:
Fully modified, I still have a huge framerate issue with Quake 2 and Open GL games.
I then modified only the Device id and left all the tweaks there - OpenGL will not run at all!!

I'm definitely having what one could call "issues"!!

By the way, tried the new 5.7 cataysts as well - still have the framerate issue, but apart from that they are OK.

Matt

The Captain

You may want to try using different atioglxx.dll files. I'm not sure if that will fix the problem or not.

floatingkiwi

Is it possible to install OpenGL drivers and D3d drivers seperately?

The Captain

Well, you can change out the various opengl driver files in C:\WINDOWS\system32. Just replace the atioglxx.dll file with another one. You can even try using the atioglgl.dll (the firegl opengl driver) files from firegl specific driver releases (just go onto ATI's site to find firegl drivers). Just make sure that the registry key is correct:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\OpenGLDrivers\atifglws]
"Version"=dword:00000002
"DriverVersion"=dword:00000001
"Flags"=dword:00000001
"Dll"="atioglxx.dll"

The last line should specify the name of the opengl driver file in C:\WINDOWS\system32. If you use atioglgl.dll, make sure the last line is changed to "Dll"="atioglgl.dll"

The Captain

I noticed the other day that opengl wasn't working again, but I found the problem: triple buffering. It seems that the mobility firegl cards in the nw8000 can't handle triple buffering in opengl. So if you are using ati tray tools or another such tool, make sure that triple buffering is disabled for opengl.

peace.

floatingkiwi

Thanks captain

Why do we have 2 OpenGL files in these drivers (atioglxx and atioglgl)?
I guess for the fire gl part and the normal part? (I know this is abit vague, I'm not really familiar with driver files). The registry entry you just mentioned, does it tell the system which OGL driver file to use? Or is this only for Fire gl apps?

Matt

floatingkiwi

Triple buffering....

Yes, I noticed that as well, but when I installed the Omega drivers it was enabled, and GL was working OK. There must be another tweak that when used at the same time, allows GL to function properly.

Matt

The Captain

It seems that firegl based drivers use atioglgl and radeon based drivers use atioglxx (at least that's what I have seen). The registry entry tells the entire system which OGL driver file to use. Without it correct, you won't be able to use any OGL app or game.

floatingkiwi

I have tried to just copy the old atioglgl, atioglxx files into windows/system32 but the files don't seem to be "recognised" by the system (the registry setting is OK - and in fact doesn't seem to make any difference - I changed it around with no differences). And OpenGL goes back to the 1.0 Microsoft entries (as seen by RealTech VR openGL extensions viewer, so they aren't being recognised somehow. Maybe I could replace and rename the .dl_ files in the drivers installation directory?

Incidentally HP have just released a new set of drivers for this laptop, http://h18007.www1.hp.com/support/fi...oad/22858.htmlI haven't tried them yet.

So what about anyone else - can you guys run Quake 2 (and what FPS to you get and with what drivers?)

Matt

The Captain

You are replacing the atioglxx.dll files with .dll files, not .dl_ files, right? .dl_ files are compressed versions which need to be uncompressed to work.

floatingkiwi

Oh, well, that would cause the problem then! Told you I didn't know about driver files.....
Matt

floatingkiwi

Bumpity bump.
Hi all

Anyone made any more progress with this little beastie of a notebook?

I've got the brand new HP drivers installed again (see last page for the link) as Omega's new offering along with the 5.7 catalysts still don't work for things like Doom3 and Quake 2 evolved (although good old Quake 2 still does) - albeit STILL the frame rate problem with the HP drivers. Strange though, I can get 60fps easily with Quake 2 Evolved but can only manage 11 fps with Original Quake 2 (yes, yes I know, still playing it after all these years).

Cheers

Matt

The Captain

I'm not sure, but I think the culprit may have something to do with a setting somewhere that our mobility firegl's don't like. For example, the triple buffering issue I mentioned in post #16. Perhaps the game itself (in your case Quake II) makes a setting automatically that disagrees with the gfx card.

floatingkiwi

Just tried the new Mobility catalyst 5.8. I modded the inf to use the correct device id (4e50) and it only loaded the firegl Opengl driver, namely atioglgl.dll. The registry setting still has both entries, but the ati2dvag one is empty.
BUT OPengl is working.... (well, the new games are anyway, doom 3 and Quake 2 evolved etc.)

Matt

rino_yeh

hi everyone

this is my first post in DH...i'm come from taiwan.

hope everyone can forgive my poor english...thx...

first, many people who have t42p like me, used Omega 2.6.47 or higher version.

can't play doom3 or 3ds max any about opengl programs...

i tried and tried many way...finally, let me find out a solution...

now, the omega version 2.6.61 is working on my t42p and can run doom3 and 3ds max...

anyway, cuz my poor english, so i dont wanna talk to much...

see my way below

1.go to ibm web site to download the ISV driver for t42p(i downloaded isv for 3ds max)
http://www-306.ibm.com/pc/support/si...cid=MIGR-57570
2.remove all the ati driver everything about fire gl driver, then reboot.

3.install the Omega 2.6.61 driver, then reboot.

4.install the ISV driver,(don't overwrite any driver from Omega, Just click nonononono till finish the procedure),then reboot.

5.install the Omega 2.6.61 again,(use START/Radeon Omega Drivers/(Re) Install Omega Drivers)

6.then use regedit to change the opengl driver.

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\OpenGLDrivers\atifglws]
"Version"=dword:00000002
"DriverVersion"=dword:00000001
"Flags"=dword:00000001
"Dll"="atioglxx.dll"

see this "atioglxx.dll" change to "atioglgl.dll"(cuz u already install the isv, so u will be have this file in ur windows/system32/

done this procedure then close this window

7.then execute the video setting, there will have a setting about 3ds/viz...etc...
(cuz my system is chinese, i dont know what name is it in english system, sorry abt it)
but it's very ez to find out, install the isv it will be there. and select the 3D Studio Max/VIZ
,then press ok.

then try to run the 3ds max (if u have) or Doom3, and good luck everyone.

it's working normal on my t42p now.

btw, the ATT still can working well.

DOOM3-640X480-64fps

thx again evevyone.

floatingkiwi

Hi all

Just installed Mob Cat 6.2 on the NW8000 and noticed a very bizarre thing:
The default clock speeds are now 209/209 rather than 344/202, which is obviously not a GOOD THING.

Anyone seen/heard of this??? Can I change it back again via some settings or by modifying the driver files?

Matt

**Edited - actually I must have been crying wolf. The problem has fixed itself, or possibly some confliction with Centrino Hardware Control program***

Open GL is still working! Yee ha!!

floatingkiwi

Above problem sorted out, just the Cat control center not recognising when the AC main was plugged in or not.

OK now, installed Cat 6.3 and guess what: Ati2mtag.sys from cat 6.3 causes the computer NOT to resume from standby and gives the BSOD!! (all verified by multiple re-installs and trouble-shooting).

Matt

ceeol

Anyone experienced this?

At some point in history (unknown reason) DirectDraw etc. became unavailable according to dxdiag.

Trying to get it going again I have now installed the latest drivers from Omega (yes - and cleaned properly first, + changed inf-file as someone recommended above), reinstalled DirectX... And, no success.

DirectX does not seem to detect that the adapter has any memory, saying Approx. Total Memory being n/a.

The DirectX Caps Viewer that comes with the drivers shows me that I have a DirectX Graphics Adapter, being the T2, everything looking good so far.
However, under DirectDraw Devices, there is first a Primary Display Driver (display) , then comes the ATI MOBILITY <...> and finally a hardware emulation layer. Neither the Primary Display Adapter nor ATI MOBILITY has any memory nor capabilities. To be exact, all memory values are 0, and DDCAPS_NOHARDWARE is Yes.

What is the Primary Display Adapter? Read about someone who had a problem with PC-Duo, it was installed on my machine too, any connection here? Or is the solution to my problem elsewhere?

Ideas?

Cheers,
Ole

Edited:
For your information:

PCDuo left the registry with 0x00000000, not 0x00000007 in the registry at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\GraphicsDrivers\DCI\Timeout. And that was it really. No idea how many hours it took to find that out. At least I got my drivers updated.

molf

Hi All(noob)

I have exactly the same problem. but i do not have the Omega thingie (dont what it is...)
my direct draw and 3d are now disabled. on their own.

by the way this problem spans across HP Laptops with the ATI cards. nc8000,nw8000,nc8240...
they basically fail the direct x display tests.

someone please help ceeol.
... and myself