Announcement

Collapse
No announcement yet.

G400 card not recognised after install

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • G400 card not recognised after install

    Any ideas?

    I uninstalled my old AGP Rage Pro 2x - also had a diamond voodoo 2 running the 3d graphics. I unistalled the voodoo 2 and removed the Rage Pro from the device manager.

    Put in the G400 16mb AGP (sinlgle head) in the AGP slot - rebooted - it detected the new hardware - I ran the installation CD provided with the card. It copied across files - with no errors.

    When I try to load up after installing I get an error saying "display properties are not set properly change resolution to display better" - or somthing like that. But I am unable to change anything - and only get very limited options anyway. It is stuck on very basic resolution settings. If I try to change them I get a "display adaptor not set properly" error.

    I have removed G400 - deleted all relevant files - reinstalled. No conflicts in device manager that I can see - and G400 shows under display adaptor. Help please!! it is probably something obvious - any pointers would be appreciated.

    thanks.

  • #2
    I shall try this. Thanks. I have been told their could be a IRQ conflict as well which I will try.

    Comment


    • #3
      Let me guess ...

      You are using a non-standard FSB frequency, right ?

      It looks like your G400 failed to be recognized properly.

      Did you try a 2nd reboot ?
      If not, try it and report if it works now ...

      ------------------
      Cheers,
      Maggi
      ________________________

      Working Rig:
      Asus P2B-DS @ 103MHz FSB
      Double Pentium III-450 @ 464 MHz
      4 x 128MB CAS2 SDRAM
      Matrox Millennium G400 32MB DualHead
      Nokia 445Xi (21")
      Nokia 447Xpro (17")

      Home Rig:
      Asus P2B-S Bios 1010 @ 112MHz FSB
      Celeron 300A @ 504MHz
      2 x 128MB CAS2 SDRAM
      Matrox Millennium G400 32MB DualHead @ 150/200MHz
      CTX VL710T (17")
      Despite my nickname causing confusion, I am not female ...

      ASRock Fatal1ty X79 Professional
      Intel Core i7-3930K@4.3GHz
      be quiet! Dark Rock Pro 2
      4x 8GB G.Skill TridentX PC3-19200U@CR1
      2x MSI N670GTX PE OC (SLI)
      OCZ Vertex 4 256GB
      4x2TB Seagate Barracuda Green 5900.3 (2x4TB RAID0)
      Super Flower Golden Green Modular 800W
      Nanoxia Deep Silence 1
      LG BH10LS38
      LG DM2752D 27" 3D

      Comment


      • #4
        What is a FSB Frequency?? I haven't a clue what that is. Please advise I am happy to look at anything you suggest.

        I tried several reboots - no luck...god damn it!!

        Comment


        • #5
          Maggi is basically asking if you are overclocking your CPU. If you go to a non-standard Front Side Bus (fsb) frequency....say 83, 112, 124 MHz...etc it will change the frequency of the AGP bus and can cause conflicts with the AGP card. If you use standard bus speeds e.g. 66 & 100 MHz most motherboards have a divider that will scale the AGP bus down to the appropriate levels.

          Hope that helps and I hope I didn't put any words in Maggi's mouth.

          Paul
          Despite my nickname causing confusion, I have no religious affiliations.

          Comment


          • #6
            FrontSideBus ... meaning the main clock your system is running at.

            Just post as much as you know about your system (MoBo, CPU, peripherals etc.) and at what speed you CPU is running at.

            I had a very similar problem as the one you reported, but I'm OCing my machine:

            - after installation > reboot > black screen & lockup
            - reboot > the error message you reported appeared follow by a standard display control panel
            - I cancelled and rebooted
            - everything was fine, except for I was running at AGP1x instead of AGP2x

            I crosschecked my findings and it looks like the G400 is not on all system able to reach AGP2x when your FSB runs at higher speed than default, switching it back to normal settings cured the prob.

            ------------------
            Cheers,
            Maggi
            ________________________

            Working Rig:
            Asus P2B-DS @ 103MHz FSB
            Double Pentium III-450 @ 464 MHz
            4 x 128MB CAS2 SDRAM
            Matrox Millennium G400 32MB DualHead
            Nokia 445Xi (21")
            Nokia 447Xpro (17")

            Home Rig:
            Asus P2B-S Bios 1010 @ 112MHz FSB
            Celeron 300A @ 504MHz
            2 x 128MB CAS2 SDRAM
            Matrox Millennium G400 32MB DualHead @ 150/200MHz
            CTX VL710T (17")
            Despite my nickname causing confusion, I am not female ...

            ASRock Fatal1ty X79 Professional
            Intel Core i7-3930K@4.3GHz
            be quiet! Dark Rock Pro 2
            4x 8GB G.Skill TridentX PC3-19200U@CR1
            2x MSI N670GTX PE OC (SLI)
            OCZ Vertex 4 256GB
            4x2TB Seagate Barracuda Green 5900.3 (2x4TB RAID0)
            Super Flower Golden Green Modular 800W
            Nanoxia Deep Silence 1
            LG BH10LS38
            LG DM2752D 27" 3D

            Comment


            • #7
              Good one, Paul !

              I guess it took me a little tooo long to reply in time

              and no foot in my mouth yet

              ------------------
              Cheers,
              Maggi
              ________________________

              Working Rig:
              Asus P2B-DS @ 103MHz FSB
              Double Pentium III-450 @ 464 MHz
              4 x 128MB CAS2 SDRAM
              Matrox Millennium G400 32MB DualHead
              Nokia 445Xi (21")
              Nokia 447Xpro (17")

              Home Rig:
              Asus P2B-S Bios 1010 @ 112MHz FSB
              Celeron 300A @ 504MHz
              2 x 128MB CAS2 SDRAM
              Matrox Millennium G400 32MB DualHead @ 150/200MHz
              CTX VL710T (17")
              Despite my nickname causing confusion, I am not female ...

              ASRock Fatal1ty X79 Professional
              Intel Core i7-3930K@4.3GHz
              be quiet! Dark Rock Pro 2
              4x 8GB G.Skill TridentX PC3-19200U@CR1
              2x MSI N670GTX PE OC (SLI)
              OCZ Vertex 4 256GB
              4x2TB Seagate Barracuda Green 5900.3 (2x4TB RAID0)
              Super Flower Golden Green Modular 800W
              Nanoxia Deep Silence 1
              LG BH10LS38
              LG DM2752D 27" 3D

              Comment


              • #8
                If in Device Manger your specific make monitor isn't listed, it may be your display driver(monitor). I downloaded the driver for my Hitachi. Go into your display properties>>>Click the settings tab>>>then into the advanced properties>>>then click the monitor tab. Click change. Choose Have Disk then point to the directory that contains the monitor's driver. Hope this helps.

                ------------------
                "I will stop...the first wave"
                "I will stop...the first wave"

                Comment


                • #9
                  Cade didn't you just die...
                  Oh sorry different reality

                  Mark F.

                  ------------------
                  OH NO, my retractable cup holder swallowed a CD



                  [This message has been edited by Mark F (edited 12 October 1999).]
                  Mark F. (A+, Network+, & CCNA)
                  --------------------------------------------------
                  OH NO, my retractable cup holder swallowed a DVD...
                  and burped out a movie

                  Comment


                  • #10
                    Start your computer in Safe Mode.
                    Go into Control Panel -> System -> Device Manager -> Display Adapters.
                    See if there are some remenents of your former cards to delete.
                    chuck


                    ------------------
                    ABit BH6 w/ Celery 333@500, 128mb gh@cas2, 10gb IBM@7200, SB Live Value@44kh, noname CDRom@40x, Mitsumi CDRW@2x2x8, Zoom@56k, Princeton EO75@1024x768x32x85hz, USB mouse,Matrox G400 MAX!!!!

                    Chuck
                    秋音的爸爸

                    Comment


                    • #11
                      THANKS EVERYONE FOR YOUR REPLIES.

                      I guess by the timings of the replies you lot are mainly in the states?? As I am in London by the time I get to see your replies I am back at work.

                      I will provide full system specs tonight when I get home. and shall definelty check out FPS - thanks for that Maggi.

                      Cade - my monitor is a Shinho - which is "plug and play" so does it require drivers?

                      I had another bash at it last night - no luck I'm afraid. One other thing I did notice is that it has installed onto IRQ 11 along with two other items called called Control Steering PCI - any ideas what this is?

                      I couldn't move the card from IRQ 11 to another free one it wouldn't let - basically said I was unable to do this. Though I could move other items.

                      I'll get back to you all later - thanks again for the advice, as a novice I need it. You lot are gurus compared to me.

                      Comment


                      • #12
                        IRQ 11 is where you want the card. Sharing it with PCI steering should not cause any problems. However I can't recall if there should be just one PCI steering or two. Could someone check how many devices they have on the same IRQ as the G400?

                        I also recall people having problems with G400's and monitors with crappy plug-and-play. See if you can hook up a different monitor or select a generic VGA monitor (from Matrox Power Desk).

                        Also check for any remaining 3dfx files. Do a file search for *3dfx.* However, problems caused by old drivers/files tend to show up as crashes or inability to properly run D3D/OGL software. I still think its a problem with the plug-and-play monitor.


                        Strider

                        Comment


                        • #13
                          Matty, I now believe this is a monitor issue. I checked other bulletin boards and found almost similar cases with Shinho/Matrox users. I found a link directly for a shinho driver. It didn't indicate any specific model, I believe it's for any of their models.
                          http://www.windrivers.com/script/dri...company=Shinho

                          If for some reason this link doesn't get you there, go to www.windrivers.com. Do a search for shinho. It's an INF file that's only 7kb's.

                          ------------------
                          "I will stop...the first wave"
                          "I will stop...the first wave"

                          Comment


                          • #14
                            Cade, thanks, I'm coming to the same conclusion. Though I don't discount anything.

                            I noticed that it is finding a default monitor.inf - certainly not one that I have ever installed. I will check that web site out shortly.

                            Thanks for your help - this weekend I am going to go crazy and try to resolve it once and for all. I work such long hours I get no time in the evenings.

                            thanks again.

                            Comment

                            Working...
                            X