ExitiosuS

Okay, lately, with the two new driver revisions of catalysts, I haven't been able to install them on my mobility card... When I try to do so, it reboots, and I'm left without any D3D capabilities... DXDIAG reports no D3D, games report no D3D, and ya.

Basically, what I've done, is *completely* remove the drivers, following common practice which I've done since cat 3.6, after that failed, I tried using the driver cleaner... That failed, so I followed the newb guide. Every one of the above methods failed, in terms of removing them and reinstall them.

However, when I use Omega's drivers, they work. But, I like to do my own personal benchmark between the two, and lately I haven't been able to do so and I can't figure this out.

Yes, I do use mobility modder on the standard catalysts...


If anyone knows what I should try, please help! If all you're going to say is, "Just use omega's" then don't bother posting, please... I'm well aware I can just wait for omega's. Anyways...


Thanks for any constructive input in advance

If you need any screens of the errors, or my methodology, just ask... I'll provide them when I get home. I'm at school, atm, so I can't. Hopefully I was descriptive enough!

No_Style

There's a manual method of installing the Catalysts. Use the MM tool to mod the drivers, but don't use the installer to install it. Just go to Device Manager and manually update the driver. Afterwards you can just use the Control Panel's installer to install the CP. I've done that for my IGP320. It works I hope that helps.

__________________

ExitiosuS

Even that method is a no-go, for some reason.

That's how I used to install all the formers, but I don't get it... These two driver releases I haven't been able to do it...

Maybe it's time I format. lol. I don't want to format again - haha.

But ya, here's a screen of what I see, just as fyi~



I'm at home now, as you can tell... But ya... I wish I could understand this.


Thanks though

No_Style

Hmmm.... That's very odd indeed. Have you formatted the laptop prior to using 4.8s and/or 4.9s?

__________________

KYPREO

I had exactly THAT problem. smartgart was automatically disabling all agp functions, which is why you have no D3D hardware acceleration. The oem drivers were fine because it doesn't use smartgart.

I believe in my case this occurred because the task scheduler service was disabled at the time (which prevents device drivers doing automatic tests on bootup). What fixed the problem was a complete system reinstall However, I believe in hindsight if I had set task scheduler to automatic it may have fixed it. All this started after installing and uninstalling omega drivers, so you never know, that *may* have caused the whole problem although I can't be sure. No offence to omega driversas they have some cool features, but I'm getting better 3dmark score asnd better doom3 scores with catalyst 4.8 and 4.9 anyway so I see no reason to change - everything is perfectly stable now.

A manual install *should* work as this way smartgart doesnt run and therefore won't shut down your AGP settings.

If you still have problems look at your bios to make sure agp is enabled, and also look up reinstall your motherboard drivers.

Is it only 4.8 and 4.9 that do it? Try your OEM drivers again - I bet they work, in which case smartgart is probably the cause.

patje

Hi Guys, I'm aware of this issue, I had on my Laptop as well. For me it helped reinstalling the dirvers a couple of times and suddenly it worked. Problem is I can't reproduce the problem.
All drivers seem to install correctly now.

Kypreo, I do not believe it has to do with the task scheduler. This thing does not prevents device drivers doing automatic tests on bootup. the only thing that does this is are the services which you can access ttough administrative tools in the control panel. I am investigation this problem also since quite a lot of people are having this issue. And I hope one day i can figure it out

__________________

ExitiosuS

Well, I haven't done anything with my drivers since I got this error, Patje, so if you need any help with information on this error, just ask me - I've been swamped with school work, so I haven't done too much in terms of gaming, so I'm content at the moment since I'm not doing much D3D activity. lol
On the weekend I planned on fixing it, even if it meant format. But like I said, if you want any info on this issue, I'll leave the error on and maybe we can use my machine as a dummy, if you know what I mean.

And... as for task scheduler, I've got mine enabled, and it usually always is enabled - since I like to have automated tasks doing the things I hate seeing being done when I'm not around.

Anyways, thanks for all the input! It's good to know others are hitting this road block too - misery loves company. :P

ExitiosuS

Well this is interesting...

I got home and decided to take a look at the directX files, and I found this -




So I figured I'd reinstall DX9.0c, and ya, that didn't work, it didn't even care... lol. Kind of depressing... What's up with that? All I did was upgrade my drivers, and now I somehow have an older DX file that I can't update? lol

Anyways... that might be why my D3D capabilities aren't there. And, as for the SmartGart, the SmartGart reports that I'm running with Fastwrites on and 4x AGP, even when I turn fastwrites off it doesn't change anything.


I feel so close to a solution!

patje

Ok i have some news,

I finally am able to reproduce the problem, so will be easier to study for a fix.

I currently installed XP pro with SP2 on a laptop with a mobility radeon 7500.
I used the modtool to mod the 4.9's and installed it along with the normal control panel.
conclusion: NO AGP For me.
Solution: not yet lol.

I hope to have some time tomorrow or today to investigate this. But eventually I will solve this, you'll see.

__________________

ExitiosuS

That's sweet.

Your help is a lot more then appreciated, I really didn't want to format again... I just formatted a month or so back before school so that I could do the semester before I should need a format again... That routine once every four months ratio type thing.

But ya.
Thanks again!
I'll be interested in seeing the outcome.

No_Style

Nice, Patje

__________________

vander

I've some problems too, with IGP320M. I started Cata4.9, use the ModTool2.0b and installed with the DeviceManager. Before I restart the notebook, I've to set the resolution from 640x480x256 to 1024x768 for example. If I don't do so, I get a black screen after restart. After the restart I get immediatly the problem that 3D-accel won't work!

My current solution for this. Get a look into the cx_17633.inf. In the section ATI.Mfg are 2 entries.
"Radeon IGP 320M"= ati2mtag_U1, PCI\VEN1002&DEV_4136
"Radeon IGP 320M"= ati2mtag_U1, PCI\VEN1002&DEV_4336
The IGP320M has two modells, the U1 and the A3. I think my notebook has the A3(DEV4336) and I correct the second line to:
"Radeon IGP 320M"= ati2mtag_A3, PCI\VEN1002&DEV_4336
After installing I get a display with the resolution 640x480 and the 3D-accel worked.
Next time I will test my system a little bit more, but I think I'm on the right way. It would be nice if anybody can verify my results.

ExitiosuS

Hey, I'd be glad to verify your results... but honestly, when it comes to those codes: Like the "UI" and the "A3," how can you tell which one your laptop would have?

My DeviceID = 4c66
Vendor ID = 1002
Subsystem ID = 011e
Subsystem Vendor ID = 1028

I use a Radeon 9000, provided by Dell... Not sure what the difference is!


Oh, and this is what I see in the cx_17633.inf file under the ati.mfg section:
[ATI.Mfg]
"Mobility Radeon 9000"= ati2mtag_M9, PCI\VEN_1002&DEV_4C66
"Mobility Radeon 9000"= ati2mtag_M9, PCI\VEN_1002&DEV_4C65
"Mobility Radeon 9000"= ati2mtag_M9, PCI\VEN_1002&DEV_4C67
To my eyes, that looks right to me...

MobileTerror

Yeah, I have the same problem with my Mobility Radeon 9000, I'm thinkin it must be a no go for us until the bug is fixed. Sorry I can't be of more help = /

P.S. Try the Omegas LOL

ExitiosuS

Wow! I got it working!
Thanks to Vander's idea, I decided to go into mine and make a few changes, too. Figured there wasn't much to lose, right? But tell me if what I did was wrong/bad/illegal in terms of compromising Omega's ati2mtag_M9 softwaredevicesettings section and replacing Patje's!

Firstly, I removed the two from this section that didn't apply to my card:
[ATI.Mfg]
"Mobility Radeon 9000"= ati2mtag_M9, PCI\VEN_1002&DEV_4C66
"Mobility Radeon 9000"= ati2mtag_M9, PCI\VEN_1002&DEV_4C65
"Mobility Radeon 9000"= ati2mtag_M9, PCI\VEN_1002&DEV_4C67

So I was left with:
[ATI.Mfg]
"Mobility Radeon 9000"= ati2mtag_M9, PCI\VEN_1002&DEV_4C66

After doing that, I went down the the ati2mtag_M9 settings, and to my stupid head, they looked right - so I went into what's known to work, the Omega 4.8s' ati2mtag_M9 settings, and copied those and replaced what I saw there with Omegas.

Saved, did a driver clean, etc... Restarted. Installed the drivers. Restarted. It worked in DXDIAG, tried a game, and that too worked! Everything says I have Cat04.9 installed, and ya! Is this right? OR am I just a babbling moron that got lucky?

Yay. I hope. lol

Edit: Hey Patje, on that note, maybe that helps in some way, if it's right, where the 'problem' is in the Mobility Modder? I'd love to hear something like that.

patje

that sure does help me a lot! thanks for posting this ExitiosuS, during the weekend i haven't had the time to test this, but i'm trying this on monday. there is some thing wrong in the software devicesettings, but I don't know just what it is.

strange, but thanks for the info!

__________________

MobileTerror

At Guru3d.com there is a file below the download required for windows in order for the driver to work. Its called "Microsoft .NET Framework 1.1". I am pretty sure this will help any other people with the same problem.

ExitiosuS

Nono, that's for CCC... you need .net Framework 1.1 for CCC. The driver on the other hand, no you don't.


However, even if you did, I have it installed - as well as 2.0b... So. It can't be that. :P And... that'd mean it wouldn't work on those of us who don't use .NET 1.1... From what I've heard, there's more then a handful of them using 4.9s. So!

.NET Framework = CCC
No .NET Framework = Drivers and old CP

vander

You overestimate my knowledge, I should write I believe my notebook has an IGP320/A3 GPU. Simply because the fact that here are two devices with only an entry for the U1 and this won't work.

Lists with vendor numbers are standard and exists everywhere in the net, here are many tools like pcilist, crystalcpuid, ... The device numbers are not so clear, since every vendor can use his own strategy for numbering. ATI should know which GPU is device 4C66, but I don't believe they will tell you something about it.

ExitiosuS

From your description, you make it seem like I underestimated your knowledge.


Good thinking to do all that - I wouldn't of thought of it, especially to edit the .inf, so ya. I give all credit to you in solving my Catalyst 4.9 issue! Just because you fathered the idea!

I just can't wait 'till Patje leaves a message saying something like, "All fixed!" Then I can do the same on my other laptops... I don't feel like going through the work on the other ones. Lazy? I agree.


Thanks a ton guys

KYPREO

Thanks patje!

The only reason I thought Task Scheduler was because I looked at Black Viper's services info and it said Task Scheduler may be needed in order for devices to do some auto-detecting. But if others have had the same problem with hardware acceleration being turned off automatically, then that theory is probably wrong as you say.

If it helps diagnose this issue, the major steps I had followed in order for this issue to arise in my notebook are the following:

Install SP2 - no issues
Install/Uninstall Cat 4.8 and 4.9 beta using mobility modder - no issues
Install Omega drivers - no issues (except for crashing when a game uses sun glare and some fog effects)
Uninstall Omega and Reinstall OEM drivers - no issues
Reinstall Cat's using mobility modder - NOW WE HAVE ISSUES
Go back to OEM drivers - no issues
Go back to Omega - WE HAVE ISSUES AGAIN.

At all times I was using driver cleaner. I also tried manually deleting relevant registry entries and it was still an issue. It all began after either using omega drivers or going back to OEM drivers.

I have now done a fresh reinstall of the whole OS, but am sticking with SP1. I have tried cat 4.8 and 4.9 and all is fine - I have no DVD playbook issues like others have experienced.

Sharkims

Are you using drivercleaner 3.3?

__________________
System-1:
MSI K8N Neo Platinum || A64 3200+(200x11) - Zalman 7000A-AlCu || 1x1gb OCZ PC3200@400(3-3-3-7) || 9800XT || WD Raptors 2x36 RAID0
System-2:
MSI 875P Neo-FIS2R || P4 2.4c(FSB:200) - Intel Cooler || 2x256 GEIL PC3200@400(2-3-3-6) || AIW9000 || WD SE 120x2 RAID0
System-3:
DELL Inspiron 9100 || P4 3.0c(mobile) || 2x256mb PC3200(3-3-3-8) || Mobility Radeon 9700 - 128mb || WSXGA+ 15.4" || 60gb 5400RPM 8mb

ExitiosuS

I don't think DriverCleaner is causing/helping the problem in any way, personally. I used to do all my driver cleaning manually, and I tried the manual way after the format to no avail. Before the format, I was using Drivercleaner for the sake of ease. In both scenarios, however, I ran into the problem.

I think the only way to fix it, imo, since it's worked for 2/2 people that've pissed around with it, is to go into the .inf and make some changes manually.

Now, there might've been more people that've done it this way and failed and/or succeeded... But I only know of Vander and I, so...

Give it a try!

Once again, though, I don't think Drivercleaner is remotely near a solution, for another reason, after a clean format the drivers *still* don't work right off the bat.

patje

amen to that. IMO Drivercleaner will not interfere in any way. It must be in the inf's haven't found out what yet, but i'm working on it.

__________________

KYPREO

Love your work patje...thanks again!

patje

some update:

install xp with SP2, standard dirvers, install modded 4.9 no go.
use ATI uninstaller, evrything gone
Install modded 4.6 which works
Now without uninstalling, I overinstall the modded 4.9 again and it works

makes no sense really but i'm getting closer

__________________

ExitiosuS

Huh?
That doesn't make any sense to me, same mobility modder version doing this!? That's class.

Now, one thing, however... I never tried this, and I'm not up for a reformat to see if it works, but do the 4.9's modded work if you never install SP2? Or is it after the SP2 installation that it goes whacko?

If I knew, I must've forgotten... but this problem occured so close to SP2 that I just kind of thought about it... even after I formatted, I went used a slipstreamed SP2 CD so I never got to try it out. :/

Actually, I have a question - Is there a way to slipstream DX9.0c? I couldn't find a way. :/

Anyways... Back to the school work.

patje

Hi mate,

I'm pretty sure SP2 has nothing to do with it. cause my windows 2000 machine has the same problem with the 4.9

However, I did manage to install the new beta driver from ati using the mod tool. So i'm hoping this problem will dissapear with a new set, cause my hair is turning grey and it's not a pretty sight

__________________

KYPREO

Does 4.6 use smartgart on startup to automatically configure the AGP settings?

Cos my OEM drivers didn't and installed fine even though the cat drivers didn't.

I swear something isn't allowing to smartgart to do its thing properly. On the occasions were I had the AGP disabling problem, the screen didn't go black and readjust etc as I thought it was meant to when smartgart runs correctly.

And I haven't had the problem since i did a fresh reinstall with SP1 and no SP2. I have heard that SP2 has its own AGP driver - could this be a contributing factor - or could it have something to do with directx 9.0c?

Hope that helps locate the problem in some small way.

patje

could be, but if you try to mod the new "beta" 8.07 drivers it works as a charm.
So i'm gessing something is wrong with the 4.9's bizar.

If you mod the beta drivers do this: extract the file, it will create a folder C:\ATI\blbalbal but you have to create a folder Support between them. Create a folder support under the folder ATI, then MOVE (not copy) the blablbalba folder to the support folder so you end up with C:\ATI\Support\blablal then it should work.

__________________