From: owner@bugs.debian.org   
      
   This is a multi-part message in MIME format...   
      
   Your message dated Sat, 21 Feb 2026 16:38:50 +0100   
   with message-id    
   and subject line Re: Bug#1128567: linux-image-6.18.5+deb13-amd64: amdgpu.dc=0   
   causes Xorg 1:7.7+24 error "no screens found"   
   has caused the Debian Bug report #1128567,   
   regarding linux-image-6.18.5+deb13-amd64: amdgpu.dc=0 causes Xorg 1:7.7+24   
   error "no screens found"   
   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.)   
      
      
   --    
   1128567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1128567   
   Debian Bug Tracking System   
   Contact owner@bugs.debian.org with problems   
      
   Received: (at submit) by bugs.debian.org; 21 Feb 2026 09:48:50 +0000   
   X-Spam-Checker-Version: SpamAssassin 4.0.1-bugs.debian.org_2005_01_02   
    (2024-03-25) on buxtehude.debian.org   
   X-Spam-Level:   
   X-Spam-Status: No, score=-10.5 required=4.0 tests=BAYES_00,   
    BODY_INCLUDES_PACKAGE,FOURLA,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,   
    HAS_PACKAGE,HELO_MISC_IP,RCVD_IN_PBL,RDNS_NONE,SPF_NEUTRAL,   
    SPOOFED_FREEMAIL,SPOOFED_FREEMAIL_NO_RDNS,WORD_WITHOUT_VOWELS,   
    XMAILER_REPORTBUG autolearn=ham autolearn_force=no   
    version=4.0.1-bugs.debian.org_2005_01_02   
   X-Spam-Bayes: score:0.0000 Tokens: new, 55; hammy, 150; neutral, 603; spammy,   
    0. spammytokens: hammytokens:0.000-+--XDebbugsCc,   
    0.000-+--X-Debbugs-Cc, 0.000-+--HTo:N*Debian, 0.000-+--H*Ad:N*Bug,   
    0.000-+--H*Ad:N*Tracking   
   Return-path:    
   Received: from [2a02:1210:381d:3500:7:391f:2be8:db0f] (port=49676   
   helo=[192.168.1.107])   
    by buxtehude.debian.org with esmtp (Exim 4.96)   
    (envelope-from )   
    id 1vtjbU-00AK3K-3A   
    for submit@bugs.debian.org;   
    Sat, 21 Feb 2026 09:48:50 +0000   
   Content-Type: text/plain; charset="us-ascii"   
   MIME-Version: 1.0   
   Content-Transfer-Encoding: 7bit   
   From: JohnDoeThe3rd    
   To: Debian Bug Tracking System    
   Subject: linux-image-6.18.5+deb13-amd64: amdgpu.dc=0 causes Xorg 1:7.7+24   
   error "no screens found"   
   Message-ID: <177166731619.1953.9826469988028054583.reportbug@x7>   
   X-Mailer: reportbug 13.2.0   
   Date: Sat, 21 Feb 2026 10:48:36 +0100   
   Delivered-To: submit@bugs.debian.org   
      
   Package: src:linux   
   Version: 6.18.5-1~bpo13+1   
   Severity: important   
   X-Debbugs-Cc: mk939@ymail.com   
      
      
   Greetings.   
      
   When the Kernel command-line parameter 'amdgpu.dc=0' is used, the screen   
   resolution   
   (and TTY font) does not change on boot (i.e. stays whatever was used in GRUB).   
   The boot messages stop updating and a few seconds after, the screen turns off.   
      
   Excerpt from 'journalctl --boot=PREVIOUS_BOOT_HASH':   
   ---   
   Feb 21 08:54:18 x7 systemd[1]: lightdm.service: Main process exited,   
   code=exited, status=1/FAILURE   
   Feb 21 08:54:18 x7 systemd[1]: lightdm.service: Failed with result 'exit-code'.   
   Feb 21 08:54:18 x7 systemd[1]: lightdm.service: Triggering OnFailure=   
   dependencies.   
   ---   
      
   Exerpt from '/var/log/Xorg.0.log.old'   
   ---   
   [ 13.170] (II) AMDGPU(0): glamor X acceleration enabled on AMD Radeon RX   
   570 Series (radeonsi, polaris10, ACO, DRM 3.64, 6.18.5+deb13-amd64)   
   [ 13.170] (II) AMDGPU(0): glamor detected, initialising EGL layer.   
   [ 13.170] (==) AMDGPU(0): TearFree property default: auto   
   [ 13.170] (==) AMDGPU(0): VariableRefresh: disabled   
   [ 13.170] (==) AMDGPU(0): AsyncFlipSecondaries: disabled   
   [ 13.170] (II) AMDGPU(0): KMS Pageflipping: enabled   
   [ 13.170] (WW) AMDGPU(0): No outputs definitely connected, trying again...   
   [ 13.170] (WW) AMDGPU(0): Unable to find connected outputs - setting   
   1024x768 initial framebuffer   
   [ 13.170] (II) AMDGPU(0): mem size init: gart size :1f0bb8000 vram size:   
   s:fefd0000 visible:fad0000   
   [ 13.170] (==) AMDGPU(0): DPI set to (96, 96)   
   [ 13.170] (==) AMDGPU(0): Using gamma correction (1.0, 1.0, 1.0)   
   [ 13.170] (II) Loading sub module "ramdac"   
   [ 13.170] (II) LoadModule: "ramdac"   
   [ 13.170] (II) Module "ramdac" already built-in   
   [ 13.170] (EE) AMDGPU(0): No modes.   
   [ 13.171] (II) UnloadModule: "amdgpu"   
   [ 13.171] (II) UnloadSubModule: "glamoregl"   
   [ 13.171] (II) Unloading glamoregl   
   [ 13.171] (EE) Screen(s) found, but none have a usable configuration.   
   [ 13.171] (EE)   
   Fatal server error:   
   [ 13.171] (EE) no screens found(EE)   
   [ 13.171] (EE)   
   ---   
   Full log: https://paste.debian.net/hidden/6f585df9 (expires: 2026-05-22   
   09:39:21 UTC+0)   
      
      
   Manual bisect results:   
      
   - 6.12.63+deb13-amd64 --> GOOD   
   - 6.16.7+deb14-amd64 --> GOOD   
   - 6.17.13+deb13-amd64 --> GOOD   
   - 6.18.5+deb13-amd64 --> BAD   
      
   Removing the paramameter 'amdgpu.dc=0' does bring back Xorg to a working state.   
   However, this should not break Xorg at all. Currently I need this parameter   
   such that   
   adjusting the brightness is possible using the 'ddcutil' application.   
      
      
      
   -- Package-specific info:   
   ** Kernel log: boot messages should be attached   
      
   ** Model information   
   sys_vendor: Gigabyte Technology Co., Ltd.   
   product_name: Z87-HD3   
   product_version: To be filled by O.E.M.   
   chassis_vendor: Gigabyte Technology Co., Ltd.   
      
   [continued in next message]   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   
|