none
ATI Radeon drivers. (8.6 on XPe)

    Question

  • (shuttle SG33G5W + noname FANLESS hd 3470)

     

     

    Has anyone tried building an SLD for the catalyst drivers (and or that abomination, catalyst bloat centre?)

     

    A casual attempt results in nearly a thousand historical devices in any number of flavours.

     

    Examining the .INF file gives me the impression that I could create generic versions of the main culprits, such

    as about the only thing changing on a lot of these records is the "SUBSYS_raspberry_ripple".

     

    TAP has the following:

     

    Code Snippet
      <CATEGORY Name="PCI">
       <DEVICE ConfigFlags="0">
        <DEVICEDESC>ATI Radeon HD 3400 Series</DEVICEDESC>
        <HARDWAREIDS>
         <DEVICEID Order="1">PCI\VEN_1002&amp;DEV_95C0&amp;SUBSYS_E390174B&amp;REV_00</DEVICEID>
         <DEVICEID Order="2">PCI\VEN_1002&amp;DEV_95C0&amp;SUBSYS_E390174B</DEVICEID>
         <DEVICEID Order="3">PCI\VEN_1002&amp;DEV_95C0&amp;CC_030000</DEVICEID>
         <DEVICEID Order="4">PCI\VEN_1002&amp;DEV_95C0&amp;CC_0300</DEVICEID>
        </HARDWAREIDS>
        <COMPATIBLEIDS>
         <DEVICEID Order="1">PCI\VEN_1002&amp;DEV_95C0&amp;REV_00</DEVICEID>
         <DEVICEID Order="2">PCI\VEN_1002&amp;DEV_95C0</DEVICEID>
         <DEVICEID Order="3">PCI\VEN_1002&amp;CC_030000</DEVICEID>
         <DEVICEID Order="4">PCI\VEN_1002&amp;CC_0300</DEVICEID>
         <DEVICEID Order="5">PCI\VEN_1002</DEVICEID>
         <DEVICEID Order="6">PCI\CC_030000</DEVICEID>
         <DEVICEID Order="7">PCI\CC_0300</DEVICEID>
        </COMPATIBLEIDS>
       </DEVICE>
       <DEVICE ConfigFlags="0">
        <DEVICEDESC>Microsoft UAA Bus Driver for High Definition Audio</DEVICEDESC>
        <HARDWAREIDS>
         <DEVICEID Order="1">PCI\VEN_1002&amp;DEV_AA28&amp;SUBSYS_AA28174B&amp;REV_00</DEVICEID>
         <DEVICEID Order="2">PCI\VEN_1002&amp;DEV_AA28&amp;SUBSYS_AA28174B</DEVICEID>
         <DEVICEID Order="3">PCI\VEN_1002&amp;DEV_AA28&amp;CC_040300</DEVICEID>
         <DEVICEID Order="4">PCI\VEN_1002&amp;DEV_AA28&amp;CC_0403</DEVICEID>
        </HARDWAREIDS>
        <COMPATIBLEIDS>
         <DEVICEID Order="1">PCI\VEN_1002&amp;DEV_AA28&amp;REV_00</DEVICEID>
         <DEVICEID Order="2">PCI\VEN_1002&amp;DEV_AA28</DEVICEID>
         <DEVICEID Order="3">PCI\VEN_1002&amp;CC_040300</DEVICEID>
         <DEVICEID Order="4">PCI\VEN_1002&amp;CC_0403</DEVICEID>
         <DEVICEID Order="5">PCI\VEN_1002</DEVICEID>
         <DEVICEID Order="6">PCI\CC_040300</DEVICEID>
         <DEVICEID Order="7">PCI\CC_0403</DEVICEID>
        </COMPATIBLEIDS>
       </DEVICE>

     

     

    Which basically stipulate that I can match all the way down to VEN_1002 "ati" and still get away with it. But I suspect that is wishful thinking.

    Thus instead of any number of

    HD 2400 plugh

    HD 3450 goat

    HD 2400 pro goat

    maker radeon HD 3550

    HD 2350 turbo gti type-R vspec

    HD 2400 xyzzy 

     

    I would have

    Generic Radeon HD RV610 based (24xx 34xx )

    Generic Radeon HD RV630 based (26xx 36xx 38xx all the same chip!)

    Generic Radeon HD R7X based (48xx)

     

    Has anyone tried this? Is it a recipe for disaster due to unforseen consequences?

     

    Monday, July 14, 2008 3:31 AM

Answers

  • I eventually solved this with a super genericised radeon driver. That project however, sank without trace in the murky depths of corpulent politics.

    However, never fear, the experience was useful and I get to do the radeon dance all over again with a new project. This time I'm wondering if doing it as a RunOnce Installer might be easiest.

     


    =^x^=
    • Marked as answer by P E Monday, May 03, 2010 10:22 AM
    Monday, May 03, 2010 10:22 AM
  • Technically, all you need is one component to be in the image. So long as the INF file and the drivers are in the image, the driver should load. The trick with ATI is the HotKeyPoler resource. You need to either delete it or add LocalSystem to the Start name property.

    If you need the Catalyst software, I suggest that you run the installer. FBA Generic command at a later FBA phase is recommneded since RunOnce might be a littler early in the FBA process.

    -Sean

     

     


    www.sjjmicro.com / www.seanliming.com, Book Author - XP Embedded Advanced, XPe Supplemental Toolkit, WEPOS / POS for .NET Step-by-Step
    • Marked as answer by P E Wednesday, May 12, 2010 12:01 AM
    Friday, May 07, 2010 4:00 PM

All replies

  • Hi,

    I am going through old posts that do not have a reply to find out if the issue has been resolved, or if it is still applicable?

    Lynda

    • Marked as answer by P E Monday, May 03, 2010 10:22 AM
    • Unmarked as answer by P E Monday, May 03, 2010 10:22 AM
    Wednesday, April 28, 2010 11:30 PM
    Owner
  • I eventually solved this with a super genericised radeon driver. That project however, sank without trace in the murky depths of corpulent politics.

    However, never fear, the experience was useful and I get to do the radeon dance all over again with a new project. This time I'm wondering if doing it as a RunOnce Installer might be easiest.

     


    =^x^=
    • Marked as answer by P E Monday, May 03, 2010 10:22 AM
    Monday, May 03, 2010 10:22 AM
  • Glad to know you got it solved, anyway!
    Friday, May 07, 2010 12:03 AM
    Owner
  • Technically, all you need is one component to be in the image. So long as the INF file and the drivers are in the image, the driver should load. The trick with ATI is the HotKeyPoler resource. You need to either delete it or add LocalSystem to the Start name property.

    If you need the Catalyst software, I suggest that you run the installer. FBA Generic command at a later FBA phase is recommneded since RunOnce might be a littler early in the FBA process.

    -Sean

     

     


    www.sjjmicro.com / www.seanliming.com, Book Author - XP Embedded Advanced, XPe Supplemental Toolkit, WEPOS / POS for .NET Step-by-Step
    • Marked as answer by P E Wednesday, May 12, 2010 12:01 AM
    Friday, May 07, 2010 4:00 PM
  • That was the magic hint I needed. That ATI Hotkey Poller is so annoying.

    Their driver is also overly sensitive, sometimes the same make and model of card won't be recognised.

    Anyway, I now have a working 10.4 sld, which will be driving 45" screens in stations. ^^!


    =^x^=
    Monday, May 17, 2010 10:41 AM