Hide Forgot
Created attachment 486713 [details] The dmesg log, with some interesting messages from nouveau in it. Description of problem: I've downloaded the Fedora 15 Alpha live image and put it onto a USB flash drive using liveusb-creator. All went fine, and I booted to Fedora 15. At the bootup, I get a message from the nouveau driver, saying "Pointer to BIT loadval table invalid" After this, the desktop seems to load correctly, but shortly after that, small visual glitches start to appear. In a few minutes all text disappears from every window and after this, the user interface becomes totally non-responsive. I have to reboot to use the system again. I will attach the dmesg log. How reproducible: Always Steps to Reproduce: 1. Boot into Fedora 15 2. Log in to the desktop 3. Watch as it falls apart Actual results: The system practically hangs after about 5 minutes. Expected results: The system should not hang. This hardware should be capable of running gnome-shell flawlessly. Additional info: Because it all starts with visual glitches and an error from Nouveau, I'm suspecting that this is all Nouveau's fault, I think I may have to test it with the properitary drivers too, to see if the issue appears then. My hardware is the following: Fujitsu Amilo Pi 3560 with - Intel T4300 - NVidia GeForce GT 240M - 3 GB RAM
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 * X server log file (/var/log/Xorg.*.log), and * system log (/var/log/messages) 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.
Hello Matej, Sorry I couldn't reply to you earlier. I was finally able to do a proper F15 install to my hard drive. It seems that after the latest updates, the issue I described doesn't appear any more. I have not encountered it again, but I will report back if I encounter it again. Thank you guys for fixing this! :)
Thank you for letting us know.