Created attachment 486808 [details]
Screenshot: no X
Description of problem:
My system has an NVidia 7600GS (G73) video card and X does not start when using the kernel mentioned bellow.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot kernel-2.6.38-0.rc5.git1.1.fc15.x86_64 in "graphical.target" (runlevel 5)
X does not start. See attached screenshot. The messages seem to be from the previous (re)boot possibly with the older kernel.
X should start.
X starts when using kernel-2.6.38-0.rc5.git1.1.fc15.x86_64.rpm, although it still doesn't work too well. If I start a program, e.g. firefox or gnome-terminal its window will start to flicker. It will appear and disappear rapidly forever.
lspci output for video card:
01:00.0 VGA compatible controller: nVidia Corporation G73 [GeForce 7600 GS] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Giga-byte Technology Device 341a
Flags: bus master, fast devsel, latency 0, IRQ 11
Memory at e1000000 (32-bit, non-prefetchable)
Memory at d0000000 (64-bit, prefetchable)
Memory at e0000000 (64-bit, non-prefetchable)
I/O ports at 2000
Capabilities:  Power Management version 2
Capabilities:  MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities:  Express Endpoint, MSI 00
The /var/log/Xorg.* files seem to old to be from this failed boot, so I won't attach them.
Created attachment 486809 [details]
It contains messages from both kernels.
Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.
Please add drm.debug=0x04 to the kernel command line, restart computer, and attach
* your X server config file (/etc/X11/xorg.conf, if available),
* X server log file (/var/log/Xorg.*.log), and
* output of the dmesg command
to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above.
We will review this issue again once you've had a chance to attach this information.
Thanks in advance.
I've tried again with the following packages:
This time the screen was full of artifacts (see attachment).
Kernel command line:
b1d-b5e0-2eed2e993c8b rd_NO_LUKS rd_NO_LVM rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SY
SFONT=latarcyrheb-sun16 KEYTABLE=us drm.debug=0x04
Created attachment 487549 [details]
Screenshot: no X (2)
Lots of artifacts.
Created attachment 487550 [details]
Created attachment 487551 [details]
Created attachment 487552 [details]
I've retested with kernel-18.104.22.168-8.fc15.x86_64 and I had mixed results. My memory isn't helping me, so please take the following with a grain of salt.
First boot in _text mode_ (multi-user.target) didn't work at all and the screen had only artifacts which by the way made the LCD screen buzz. Then I booted kernel-22.214.171.124-6.fc15.x86_64, kernel-2.6.38-1.fc15.x86_64 and kernel-2.6.38-0.rc5.git1.1.fc15.x86_64 and none of them worked. The system was not even responding to ping requests. I booted kernel-2.6.38-0.rc5.git1.1.fc15.x86_64 _with nomodeset_ and it worked. Then I tried _without nomodeset_ in GUI mode (graphical.target) and it kind of worked, meaning that I had that flickering issue again.
Finally, I rebooted and started kernel-126.96.36.199-8.fc15.x86_64. The background of Fedora 15 appeared nicely on the screen, but that was it. I had no user list or anything else. I was able to connect to the system via SSH, so I was able to collect the information requested by Matej Cepl. N.B.: The logs contain information from all kernels.
If you happen to have any wild or crazy ideas please mention them, because I'll remove the drive with Fedora 15 in a couple of days and afterwards I might not have enough space for testing Fedora 15.
Created attachment 488543 [details]
Created attachment 488544 [details]
Created attachment 488546 [details]
Contains messages from kernel-2.6.38-0.rc5.git1.1.fc15.x86_64, kernel-2.6.38-1.fc15.x86_64, kernel-188.8.131.52-6.fc15.x86_64, kernel-184.108.40.206-8.fc15.x86_64.
Is this a regression from something? Has the card worked previously?
With the exception of bug #550720 it worked fine in Fedora 14, but please take note that I use the nvidia driver most of the time because of that bug.
I have exact the same video-card. My system totally locks up with KDE_fc-15_beta_tc1 from 2011, April, 1. It looks to be an issue with the kernel part (drm) of the video driver, because I'm using rawhide (fc16) without a problem. Better openGL is working like a charm :-) The nouveau driver is in fc15 and rawhide the same, the kernels (and xorg-server) are different:
btw: the following kernels were also working ok:
Hope this helps and thanks,
@Ben I hope you can solve this issue before fc15 gets Gold, because I don't like to use the propriety blob :-)
martin is right, it does work in Fedora rawhide with those packages, but on the other hand I don't have any 3D acceleration, so I can't run the full GNOME3 shell. I can't even run glxgears:
Xlib: extension "GLX" missing on display ":0.0".
Error: couldn't get an RGB, Double-buffered visual
Okay, I believe I've identified the issue here. There's a kernel building now that will hopefully fix the problem:
I've retested with kernel-220.127.116.11-12.fc15.x86_64.rpm and X is working again. I have even played OpenArena in 1920x1200 (by the way the brightness setting doesn't seem to work) and Teeworlds.
Unfortunately suspend still doesn't work too well, but that's another issue. The bug can be closed when the fix hits the official repositories.
*** Bug 693133 has been marked as a duplicate of this bug. ***
kernel-18.104.22.168-18.fc15 has been submitted as an update for Fedora 15.
* should fix your issue,
* was pushed to the Fedora 15 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing kernel-22.214.171.124-18.fc15'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
kernel-126.96.36.199-18.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.