Bug 468787 - With Kernel Mode Setting enabled. KDE login fails and computer hard locks.
With Kernel Mode Setting enabled. KDE login fails and computer hard locks.
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: X/OpenGL Maintenance List
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-10-27 20:02 EDT by Garry Reisky
Modified: 2009-04-01 16:31 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-04-01 16:31:37 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Xorg log (88.02 KB, application/octet-stream)
2008-10-27 20:02 EDT, Garry Reisky
no flags Details

  None (edit)
Description Garry Reisky 2008-10-27 20:02:43 EDT
Created attachment 321669 [details]
Xorg log

Description of problem:

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Boot and watch plymouth do it's thing.
2. KDM appears. login
3. Solar flare progress bar does it's thing and get's to the end and than the machine hard locks. I can't ssh in.
Actual results:

Expected results:

Additional info:

$ lspci -nn | grep Radeon
03:00.0 VGA compatible controller [0300]: ATI Technologies Inc Radeon R350
[Radeon 9800 Pro] [1002:4e48]
03:00.1 Display controller [0380]: ATI Technologies Inc Radeon R350 [Radeon
9800 Pro] (Secondary) [1002:4e68]
$ uname -r
$ rpm -q xorg-x11-drv-ati xorg-x11-server-Xorg
Comment 1 Garry Reisky 2008-10-29 15:30:25 EDT
I can login into KDE now. No lockups

$ uname -r
Comment 2 Garry Reisky 2008-11-05 01:31:25 EST
I was able to login but after I booted again it went back to locking up after I logged into KDE

$ uname -r
Comment 3 Bug Zapper 2008-11-25 23:20:08 EST
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.

More information and reason for this action is here:
Comment 4 François Cami 2009-02-02 16:45:13 EST
Hi Garry,

Do you still experience the problem with the updated kernel and xorg-x11-drv-ati packages ?
If yes, could you test with nomodeset on the command line ?

Comment 5 François Cami 2009-04-01 16:31:37 EDT
    The information we've requested above is required in order to review this problem report further and diagnose or fix the issue if it is still present. Since it has been thirty days or more since we first requested additional information, we're assuming the problem is either no longer present in the current Fedora release, or that there is no longer any interest in tracking the problem. 

    Setting status to "CLOSED: INSUFFICIENT_DATA". If you still experience this problem after updating to our latest Fedora release and can provide the information previously requested, please feel free to reopen the bug report. 

    Thank you in advance. 

Fedora Bugzappers volunteer triage team

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