| Bug ID | 102372 |
|---|---|
| Summary | [dc] [kabini] Errors during startup - X doesn't start |
| Product | DRI |
| Version | XOrg git |
| Hardware | Other |
| OS | All |
| Status | NEW |
| Severity | normal |
| Priority | medium |
| Component | DRM/AMDgpu |
| Assignee | dri-devel@lists.freedesktop.org |
| Reporter | mike@fireburn.co.uk |
Created attachment 133715 [details]<=
/span>
Dmesg
Logs filled with errors, managed to SSH in and capture the dmesg before
rebooting
Please attach your full dmesg output from when the driver load= ed and your xorg log.
| What | Removed | Added |
|---|---|---|
| CC | mike@fireburn.co.uk |
The driver is built in, I noticed Dave spotted the same (or si= milar issue)=20 Harry Wentland said he sent a patch fixing the issue but I don't think it's included in your tree yet and I'm not sure which is the right patch
Thought I'd revert and retest with all the latest code KMS does work but X doesn't start
| What | Removed | Added |
|---|---|---|
| Attachment #133715 is obsolete | 1 |
| What | Removed | Added |
|---|---|---|
| Attachment #134326 is obsolete | 1 |
| What | Removed | Added |
|---|---|---|
| Attachment #134327 is obsolete | 1 |
Looks like X starts now with the drm-next-4.16-wip branch There's still an error in the logs: [ 0.604111] [drm] amdgpu: dpm initialized [ 0.605298] [drm] Found UVD firmware Version: 1.64 Family ID: 9 [ 0.605737] [drm] Found VCE firmware Version: 50.10 Binary ID: 2 [ 0.606558] [drm] DC: create_links: connectors_num: physical:3, virtual:0 [ 0.606596] [drm:construct] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:1! [ 0.606606] [drm] dal_graphics_object_id_is_equal: Warning: comparing invalid object 'id2'! [ 0.609069] [drm] Display Core initialized! [ 0.642428] [drm] dc_link_detect: manufacturer_id =3D 2D4C, product_id = =3D C00, serial_number =3D 1000601, manufacture_week =3D 42, manufacture_year =3D 24, display_name =3D SAMSUNG, speaker_flag =3D 1, audio_mode_count =3D 3 [ 0.642444] [drm] dc_link_detect: mode number =3D 0, format_code =3D 1, channel_count =3D 1, sample_rate =3D 7, sample_size =3D 7 [ 0.642454] [drm] dc_link_detect: mode number =3D 1, format_code =3D 2, channel_count =3D 5, sample_rate =3D 7, sample_size =3D 80 [ 0.642464] [drm] dc_link_detect: mode number =3D 2, format_code =3D 7, channel_count =3D 5, sample_rate =3D 4, sample_size =3D 192 I'll check drm-next and Linus's branches when I get home so we can hopefully revert the kabini disablement on DC
What physical display connectors are actually on the board?
I've just checked https://www.computeruniverse.net/en/products/90526096/acer-as= pire-xc-105.asp It has HDMI and a VGA connector, I've only ever used the HDMI connector
Whilst I still get the following message: [ 0.583506] [drm:construct] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:1! type 0 expected 3 DC does now work on Kabini, so can the following revert be applied
Created atta= chment 136924 [details] [= review] Revert of the Kabini DC disablement I can send this to the list, though happy for you just to apply it
Poke: this should be reverted, as mentioned in IRC enabling DC= has unfortunately broken the displays on this TONGA GPU as well. GPU info: [AMD/ATI] Tonga PRO [Radeon R9 285/380] [1002:6939] (rev f1) more info https://people.freedesktop.org/~lyudess/archiv= e/06-24-2018/4.17-rc-breaks-lyude-machine.txt
(In reply to Lyude Paul from comment #13) > Poke: this should be reverted, as mentioned in I= RC enabling DC has > unfortunately broken the displays on this TONGA GPU as well. GPU info: >=20 > [AMD/ATI] Tonga PRO [Radeon R9 285/380] [1002:6939] (rev f1) Tonga is a different generation of display hardware so is unrelated to this= .
| What | Removed | Added |
|---|---|---|
| Resolution | --- | INVALID |
| Status | NEW | RESOLVED |