Summary: | RV350 AP [Radeon 9600] and RV280 [Radeon 9200 PRO] lock up system at server initialization | ||||||
---|---|---|---|---|---|---|---|
Product: | xorg | Reporter: | Matthew A. R. Sherian <hechz> | ||||
Component: | Driver/Radeon | Assignee: | Xorg Project Team <xorg-team> | ||||
Status: | RESOLVED FIXED | QA Contact: | |||||
Severity: | blocker | ||||||
Priority: | highest | CC: | nutello | ||||
Version: | 7.0.0 | ||||||
Hardware: | x86 (IA32) | ||||||
OS: | Linux (All) | ||||||
Whiteboard: | |||||||
i915 platform: | i915 features: | ||||||
Attachments: |
|
Description
Matthew A. R. Sherian
2006-04-04 00:47:01 UTC
don't create device sections for the x:x:1 PCI IDs, they're not real devices. Please attach your complete X log and xorg.conf. Created attachment 5201 [details]
Current Xorg configuration file
Further update: I made the PCI Card the primary card. Upon initialization of the X server with 'system-config-display --reconfig' the system locked up as during configuration with multiple monitors. The X-Server and Linux HAL report the card as a "Radeon 9200 PRO", the model number on the sticker reports "Radeon 9200LX", and the serial number reports back as "Radeon 9250" I am seeing something similar: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=186663 01:00.0 VGA compatible controller: nVidia Corporation NV18 [GeForce4 MX 440 AGP 8x] (rev a2) (prog-if 00 [VGA]) Subsystem: nVidia Corporation Unknown device 0191 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 64 (1250ns min, 250ns max) Interrupt: pin A routed to IRQ 11 Region 0: Memory at fd000000 (32-bit, non-prefetchable) [size=16M] Region 1: Memory at e0000000 (32-bit, prefetchable) [size=128M] Expansion ROM at fea00000 [disabled] [size=128K] Capabilities: [60] 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: [44] AGP version 3.0 Status: RQ=32 Iso- ArqSz=0 Cal=3 SBA+ ITACoh- GART64- HTrans- 64bit- FW+ AGP3+ Rate=x4,x8 Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- Rate=<none> 02:09.0 VGA compatible controller: ATI Technologies Inc RV280 [Radeon 9200 SE] (rev 01) (prog-if 00 [VGA]) Subsystem: Info-Tek Corp. Unknown device 0141 Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Interrupt: pin A routed to IRQ 16 Region 0: Memory at f0000000 (32-bit, prefetchable) [size=128M] Region 1: I/O ports at de00 [size=256] Region 2: Memory at fcec0000 (32-bit, non-prefetchable) [size=64K] Expansion ROM at fce00000 [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- 02:09.1 Display controller: ATI Technologies Inc RV280 [Radeon 9200 SE] (Secondary) (rev 01) Subsystem: Info-Tek Corp. Unknown device 0140 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 64 (2000ns min), Cache Line Size 10 Region 0: Memory at e8000000 (32-bit, prefetchable) [size=128M] Region 1: Memory at fced0000 (32-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- I think this is fixed in CVS and should be in 7.1 (In reply to comment #5) > I think this is fixed in CVS and should be in 7.1 Hi Dave, can you please tell more about this? Was it a bug in the driver or somewhere else? I was hoping I could try packages from the latest X builds in Red Hat's Raw Hide to confirm the fix (if I am being bitten by the same problem...), maybe even with the fewest new packages possible. Thanks for any help you can provide. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.