[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#499121: marked as done (PCI: (3:0:1) ATI Technologies Inc unknown chipset (0x5b75) rev 128, Mem @ 0xf8010000/16)



Your message dated Wed, 17 Sep 2008 10:59:24 +0200
with message-id <48D0C6EC.6040806@ens-lyon.org>
and subject line Re: Bug#499121: PCI: (3:0:1) ATI Technologies Inc unknown chipset (0x5b75) rev 128, Mem @ 0xf8010000/16
has caused the Debian Bug report #499121,
regarding PCI: (3:0:1) ATI Technologies Inc unknown chipset (0x5b75) rev 128, Mem @ 0xf8010000/16
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
499121: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=499121
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: xserver-xorg-video-ati
Version: 1:6.9.0-1+lenny2
Severity: normal

Hello,

I'm running lenny on i386 and my Xorg.0.log tells me:

(--) PCI:*(3:0:0) ATI Technologies Inc RV370 5B65 [FireGL D1100 (PCIE)] rev 128, Mem @ 0xf0000000/27, 0xf8000000/16, I/O @ 0x9000/8
(--) PCI: (3:0:1) ATI Technologies Inc unknown chipset (0x5b75) rev 128, Mem @ 0xf8010000/16

I tested it with 1:6.9.0-1+lenny2, 1:6.9.0-1+lenny4 and the one in experimental
(rebuild it to get it installed) but always have this "unknown chipset".

The card has a cradle for the two DVI outputs which are runing as clones after
a lenny installation.

How to get the chipset known to x.org?

# lspci -n
...
03:00.0 0300: 1002:5b65 (rev 80)
03:00.1 0380: 1002:5b75 (rev 80)
...

# lspci -vv
...
03:00.0 VGA compatible controller: ATI Technologies Inc RV370 5B65 [FireGL D1100 (PCIE)] (rev 80)
        Subsystem: ATI Technologies Inc Device 0402
        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: 64 bytes
        Interrupt: pin A routed to IRQ 17
        Region 0: Memory at f0000000 (64-bit, prefetchable) [size=128M]
        Region 2: Memory at f8000000 (64-bit, non-prefetchable) [size=64K]
        Region 4: I/O ports at 9000 [size=256]
        [virtual] Expansion ROM at f8020000 [disabled] [size=128K]
        Capabilities: [50] Power Management version 2
                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 (v1) Endpoint, MSI 00
                DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <128ns, L1 <2us
                        ExtTag+ AttnBtn- AttnInd- PwrInd- RBE- FLReset-
                DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
                        RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
                        MaxPayload 128 bytes, MaxReadReq 128 bytes
                DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
                LnkCap: Port #0, Speed 2.5GT/s, Width x16, ASPM L0s L1, Latency L0 <128ns, 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: [80] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
                Address: 0000000000000000  Data: 0000
        Capabilities: [100] Advanced Error Reporting <?>
        Kernel modules: radeonfb

03:00.1 Display controller: ATI Technologies Inc Device 5b75 (rev 80)
        Subsystem: ATI Technologies Inc Device 0403
        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: 64 bytes
        Region 0: Memory at f8010000 (64-bit, non-prefetchable) [size=64K]
        Capabilities: [50] Power Management version 2
                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 (v1) Endpoint, MSI 00
                DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <128ns, L1 <2us
                        ExtTag- AttnBtn- AttnInd- PwrInd- RBE- FLReset-
                DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
                        RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
                        MaxPayload 128 bytes, MaxReadReq 128 bytes
                DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
                LnkCap: Port #0, Speed 2.5GT/s, Width x16, ASPM L0s L1, Latency L0 <128ns, 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-
...

Do you need more information?

Thank you.

-- System Information:
Debian Release: lenny/sid
  APT prefers lenny
Architecture: i386

Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash



--- End Message ---
--- Begin Message ---
Noèl Köthe wrote:
> Am Dienstag, den 16.09.2008, 13:29 +0200 schrieb Julien Cristau:
>
>   
>>> Do you need more information?
>>>
>>>       
>> Is there an actual problem?
>>     
>
> Sorry for being unclear.:(
>
> I just want to help with the information to get this chipset into the
> database so its not unknown anymore.
>
> If it doesn't make any sense then just close it.
>   


This secondary PCI id is just used by old windows to enable dual-monitor
support IIRC. Xorg doesn't need it, only the primary device is used (and
known). The secondary PCI id is probably missing from the pci id
database (http://pci-ids.ucw.cz/iii/), but it doesn't matter for us.

Brice



--- End Message ---

Reply to: