Bug 2125620 - xorg-x11-drv-ati fails with kernel-5.19.7-200.fc36.x86_64
Summary: xorg-x11-drv-ati fails with kernel-5.19.7-200.fc36.x86_64
Keywords:
Status: CLOSED DUPLICATE of bug 2125536
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 36
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-09-09 13:25 UTC by Ralf Corsepius
Modified: 2022-09-10 17:30 UTC (History)
18 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-09-10 17:30:46 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Ralf Corsepius 2022-09-09 13:25:40 UTC
1. Please describe the problem:
With kernel-5.19.7-200.fc36.x86_64, a machine which so far required xorg-x11-drv-ati fails to start up a graphical login

(According to lspci: VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RS880M [Mobility Radeon HD 4225/4250])

The machine seems to boot up "mostly", but no graphical login is presented nor is a shell. ssh'ing into it from remote is possible.

2. What is the Version-Release number of the kernel:
kernel-5.19.7-200.fc36.x86_64

3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :
kernel-5.19.6-200.fc36.x86_64

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:
Boot.

5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:
Not tried.

6. Are you running any modules that not shipped with directly Fedora's kernel?:
No.

7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.
Even though ssh'ing is possible, for reasons I don't know, there are no logs of these incidents.

Comment 1 Ralf Corsepius 2022-09-10 17:30:46 UTC
Seemingly a duplicate of RHBZ#2125536.

*** This bug has been marked as a duplicate of bug 2125536 ***


Note You need to log in before you can comment on or make changes to this bug.