Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1693438 - AMD Athlon 200GE does not produce display
Summary: AMD Athlon 200GE does not produce display
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 29
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-27 20:14 UTC by Ivo Sarak
Modified: 2019-04-09 13:22 UTC (History)
16 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)

Description Ivo Sarak 2019-03-27 20:14:34 UTC
1. Please describe the problem:
After update of the kernel, I get blank display.

2. What is the Version-Release number of the kernel:
kernel-4.20.16-200.fc29.x86_64
kernel-5.0.3-200.fc29.x86_64


3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  

Everything was working with kernel 4.19.10-300.fc29.x86_64, but anything later is a fail.


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

Update kernel past 4.19.10 (even 5 series does the same thing).

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``:

Haven't 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.

Comment 1 Ivo Sarak 2019-03-28 09:49:39 UTC
dmesg of working  kernel 4.19.10:
http://ranume.levikom.ee/dmesg-41910.txt
dmesg of not working kernel 5.0.3:
http://ranume.levikom.ee/dmesg-503.txt

Comment 2 Ivo Sarak 2019-04-01 20:49:47 UTC
dmesg of not working kernel 5.0.4:
http://ranume.levikom.ee/dmesg-504.txt

Comment 3 Ivo Sarak 2019-04-03 20:00:10 UTC
dmesg of not working kernel 5.0.5:
http://ranume.levikom.ee/dmesg-505.txt

Comment 4 Ivo Sarak 2019-04-09 13:22:49 UTC
dmesg of not working kernel 5.0.6:
http://ranume.levikom.ee/dmesg-506.txt


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