Re: Device Driver loading error on 2nd PCI card, WinXP SP1

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: Alexander Grigoriev (alegr_at_earthlink.net)
Date: 05/12/04


Date: Wed, 12 May 2004 07:17:16 -0700

Are you sure your pPartialDescriptorTranslated is valid?

"Curtis Rubel" <crubel@compro.net> wrote in message
news:a90c8db8.0405111152.51f5e3a0@posting.google.com...
> Hello,
>
> We have a PCI memory card that is requesting 64MB of Memory Resource
> space, along with a small amount, 256K of register access memory
resources,
> and a PCI interrupt resource. There is also a 1MB DMA CommonBuffer setup
> for this device to use.
>
> I am mapping the 64MB region into my driver space via the call:
>
> pDevExt->local_sram_ptr =
> MmMapIoSpace
(pPartialDescriptorTranslated->u.Memory.Start,
>
pPartialDescriptorTranslated->u.Memory.Length,
> MmNonCached);
>
> Everything works fine if only one such card is installed into
> the system. Driver verifier shows no abnormalities with the driver
running,
> all IOCTL calls tested, DMA testing passes ok as well. Even ran the
driver
> with /PAE enabled just to make sure the driver was PAE correctly aware.
>
> When a 2nd card is installed the Add_Device routine runs successfully
> and exits, however when the Start_Device routine is called the system
> fails with a Bug(0x7E) error and never actually makes it into my
> Start_Device handler. If I remove the MmMapIoSpace call for
> the 64MB area the driver loads successfully on both cards. Obviously
> the memory on the card is then not accessable.
>
> I am suspecting that there is a memory resource problem causing this
> issue, however I would not expect the system to crash. I would expect the
> MmMapIoSpace call to return insufficient resources if there was a resource
> problem as its supposed to do. But it never actually makes it into the
> Start_Device routine to give me that error.
>
> The WinNt4 version of our driver does not load successfully on
> the 2nd PCI card either, but it does at least return an error and
> does not crash the system.
>
> Why can I not MmMap the 64MB of PCI address space into
> my driver twice? I have set the SystemPages entry in the registry
> to 0xffffffff as some posts suggest and it has no affect on the error.
>
> Thank you,
>
> Curtis Rubel



Relevant Pages

  • Re: MCE - HDTV Connection S-Video vs Component
    ... Well your 6600 card apparently has 128MB of memory which is what is needed ... Is your desktop resoluton also set to 1280x720 or to some other resolution? ... that the driver supports all versions of the 6600 card. ...
    (microsoft.public.windows.mediacenter)
  • Re: misc questions about the device&driver arch
    ... now i am dealing with the pciexpress resource release and allocation ... card 's resource,how can i attach it to the newly add-in card? ... :> the model is that you quess the driver, the os tells you somehow it is ... hooks up to the MOD_UNLOAD with a QUIESCE flag. ...
    (freebsd-hackers)
  • Re: AMD Dual Core Core # 2 Maxing out at 100%
    ... Available Physical Memory 1.98 GB ... Adapter driver: 8.493.0.0 5/12/2008 ... Graphics Card: Diamond Radeon HD 3650 1GB/GO DDR2 ... You'll have much better luck getting useful answers in a Windows Vista group. ...
    (microsoft.public.dotnet.languages.vc)
  • Re: AGP vs PCI-E - how big is the difference?
    ... The first card was a Radeon X1650Pro (512MB of DDR2 memory). ... I set out to update every driver I could. ...
    (alt.comp.hardware.pc-homebuilt)
  • Re: Need Help in purchasing new Graphic Card
    ... Driver Version 6.14.10.8421 ... Memory Address 0xFD000000-0xFEAFFFFF ... It comes with one DVI-I to VGA ... And if you are sensitive to noise, or expect a noiseless card, ...
    (microsoft.public.windowsxp.hardware)