Bug 53971 - [drm:radeon_get_legacy_connector_info_from_bios] *ERROR* Unknown connector type: 8
Summary: [drm:radeon_get_legacy_connector_info_from_bios] *ERROR* Unknown connector ty...
Status: RESOLVED MOVED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Radeon (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium trivial
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-23 15:17 UTC by Orion Poplawski
Modified: 2019-11-19 08:28 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Orion Poplawski 2012-08-23 15:17:42 UTC
[    1.003495] [drm] Initialized drm 1.1.0 20060810
[    1.032838] [drm] radeon defaulting to kernel modesetting.
[    1.032842] [drm] radeon kernel modesetting enabled.
[    1.036619] [drm] initializing kernel modesetting (RS480 0x1002:0x5954 0x103C:0x3009).
[    1.036645] [drm] register mmio base: 0xFDAF0000
[    1.036647] [drm] register mmio size: 65536
[    1.036867] [drm] Generation 2 PCI interface, using max accessible memory
[    1.036883] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[    1.036885] [drm] Driver supports precise vblank timestamp query.
[    1.036904] [drm] radeon: irq initialized.
[    1.037130] [drm] Detected VRAM RAM=64M, BAR=128M
[    1.037133] [drm] RAM width 128bits DDR
[    1.040862] [drm] radeon: 64M of VRAM memory ready
[    1.040864] [drm] radeon: 512M of GTT memory ready.
[    1.040884] [drm] GART: num cpu pages 131072, num gpu pages 131072
[    1.044037] [drm] radeon: ib pool ready.
[    1.044111] [drm] radeon: 3 quad pipes, 1 z pipes initialized.
[    1.048814] [drm] PCIE GART of 512M enabled (table at 0x0000000134C80000).
[    1.053590] [drm] fence driver on ring 0 use gpu addr 0x80000000 and cpu addr 0xffff88013533f000                                
[    1.053656] [drm] Loading R300 Microcode
[    1.059591] [drm] radeon: ring at 0x0000000080001000
[    1.059611] [drm] ring test succeeded in 1 usecs
[    1.059753] [drm] ib test succeeded in 0 usecs
[    1.059922] [drm:radeon_get_legacy_connector_info_from_bios] *ERROR* Unknown connector type: 8
[    1.059966] [drm] Radeon Display Connectors
[    1.059967] [drm] Connector 0:
[    1.059968] [drm]   VGA
[    1.059971] [drm]   DDC: 0x68 0x68 0x68 0x68 0x68 0x68 0x68 0x68
[    1.059972] [drm]   Encoders:
[    1.059973] [drm]     CRT1: INTERNAL_DAC2
[    1.059975] [drm] Connector 1:
[    1.059976] [drm]   DVI-D
[    1.059977] [drm]   HPD1
[    1.059979] [drm]   DDC: 0x198 0x198 0x19c 0x19c 0x1a0 0x1a0 0x1a4 0x1a4
[    1.059980] [drm]   Encoders:
[    1.059982] [drm]     DFP1: INTERNAL_DVO1
[    1.105608] [drm] fb mappable at 0xD0040000
[    1.105610] [drm] vram apper at 0xD0000000
[    1.105612] [drm] size 7680000
[    1.105613] [drm] fb depth is 24
[    1.105615] [drm]    pitch is 6400
[    1.105739] fbcon: radeondrmfb (fb0) is primary device
[    1.186275] fb0: radeondrmfb frame buffer device
[    1.186277] drm: registered panic notifier
[    1.186313] [drm] Initialized radeon 2.16.0 20080528 for 0000:01:05.0 on minor 0

Doesn't seem to cause any problems, is this worthy of "*ERROR*"?

01:05.0 VGA compatible controller: ATI Technologies Inc RS480 [Radeon Xpress 200G Series]
HP dx5150 MT BIOS 1.09 11/22/2005

Kernel 3.4.9-1.fc16.x86_64
Comment 1 Orion Poplawski 2015-06-22 21:45:28 UTC
Still present with kernel-4.0.5-200.fc21.x86_64:

[drm:radeon_get_legacy_connector_info_from_bios [radeon]] *ERROR* Unknown connector type: 8
Comment 2 Alex Deucher 2015-06-24 18:17:06 UTC
Probably a bios bug.  What physical connectors are actually on the board?
Comment 3 Martin Peres 2019-11-19 08:28:39 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/293.


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.