No announcement yet.

ATI driver and 5750

  • Filter
  • Time
  • Show
Clear All
new posts

  • ATI driver and 5750

    I was using an HD3450 on lucid with 2.6.32-rc8 kernel and the xorg-edgers ppa with great success. Each release kept on improving.

    I upgraded the HD3450 with an PowerColor 5750 SCS3.

    Lucid would not bring up X until I used the vesa driver.

    Does anybody have any idea when the ati driver from git sources will have support for this card or how to work around the issue?

    lspci -vvnn
    01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Device [1002:68be]
    Subsystem: Hightech Information System Ltd. Device [1787:2287]
    Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
    Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
    Latency: 0, Cache Line Size: 4 bytes
    Interrupt: pin A routed to IRQ 5
    Region 0: Memory at d0000000 (64-bit, prefetchable) [size=256M]
    Region 2: Memory at fdec0000 (64-bit, non-prefetchable) [size=128K]
    Region 4: I/O ports at ee00 [size=256]
    [virtual] Expansion ROM at fde00000 [disabled] [size=128K]
    Capabilities: [50] Power Management version 3
    Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
    Status: D0 PME-Enable- DSel=0 DScale=0 PME-
    Capabilities: [58] Express (v2) Legacy Endpoint, MSI 00
    DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s <4us, L1 unlimited
    ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
    DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
    RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
    MaxPayload 128 bytes, MaxReadReq 512 bytes
    DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr- TransPend-
    LnkCap: Port #0, Speed 2.5GT/s, Width x16, ASPM L0s L1, Latency L0 <64ns, L1 <1us
    ClockPM- Suprise- LLActRep- BwNot-
    LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+
    ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
    LnkSta: Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
    Capabilities: [a0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
    Address: 0000000000000000 Data: 0000
    Capabilities: [100] Vendor Specific Information <?>
    Capabilities: [150] Advanced Error Reporting <?>
    Last edited by Blue Beard; 29 November 2009, 02:55 AM.

  • #2
    You can use 2.6.32 with a very small fix which is done by my script automatically. But you can not use fglrx with Xserver 1.7+. lucid pure has got only Xserver 1.6, that would not be problematic, but the ppa you used basically broke the way for the binary only driver. And: there is no oss driver for your new card!


    • #3
      We hope to get initial open source support for hd5xxx cards out after the current batch of patches in the IP review pipeline make it out.
      Last edited by agd5f; 29 November 2009, 05:35 PM.


      • #4
        Would be nice when you put it in 6-12 branch or make master compatible with Debian lenny again.


        • #5
          Upgrade your xorg macros:

          Last edited by agd5f; 29 November 2009, 05:10 AM.


          • #6
            Why does radeon need that? radeonhd, openchrome, unichrome do not need this at all...


            • #7
              Build system cleanups.


              • #8
                Good News

                Originally posted by agd5f View Post
                We hope to get initial open source support for hd5xxx cards out after the current patch of patches in the IP review pipeline make it out.
                Thanks for the schedule info.

                The choice in fan-less cards is not great. Combine that with HDMI and the list is very short.

                I will work on the cleanup.


                • #9
                  Hey guys,

                  sorry for hijacking this thread for a more or less legal question.

                  Maybe you know PowerStrip, the only way for ATi cards under Windows to set custom resolutions and timings like vertical refresh (or advanced timings like scan lines and the like) in case of the demand for more sophisticated timings or bad EDID data provided by the display. It sets those parameters directly on hardware but the devs are lacking documentation for Evergreen/HD5000 series.

                  Would it legally be correct to use this information from the OpenSource driver? Or could you provide the required bits?

                  Thanks for reading.