James,<div><br></div><div>These day I find nouveau kms can work corectly. After booting kernel and loading drm, then the monitor turns to sleep mode and leads to an all black. But I look for bugzilla and do not find out the similar bug report. </div>
<div><br></div><div>Here is my HW: <a href="http://www.smolts.org/client/show_all/pub_2cfd8066-d0ed-4131-bb9e-04bbdcc0c7bd">http://www.smolts.org/client/show_all/pub_2cfd8066-d0ed-4131-bb9e-04bbdcc0c7bd</a><br><div><br><div class="gmail_quote">
I have tested kernel-2.6.33.3-84.fc13.x86_64 and the latest nouveau dirver on Koji. It fails to boot into gdm. </div><div class="gmail_quote"><br></div><div class="gmail_quote">Liang Suilong</div><div class="gmail_quote">
<br></div><div class="gmail_quote">On Thu, May 6, 2010 at 11:20 PM, James Laska <span dir="ltr"><<a href="mailto:jlaska@redhat.com">jlaska@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Greetings folks,<br>
<br>
Just a quick update on the status of F13Blocker. According to the<br>
schedule [1], Fedora 13 is scheduled to enter the release candidate<br>
phase *today*, May 6, 2010. In order to enter this phase, all OPEN<br>
F13Blocker bugs must be in MODIFIED or ON_QA.<br>
<br>
The numbers are certainly moving in the right direction. Thank you all<br>
for being on top of your bugs. There are now only 4 OPEN (NEW +<br>
ASSIGNED) issues remaining (see list below).<br>
<br>
To get a bug off the list, you can ...<br>
1. Resolve the issue as desired (followed by a build and F13 bodhi<br>
update)<br>
2. Prove there is minimal, or no, impact to the Fedora Release<br>
Criteria [2]<br>
<br>
Use your last minute analogy of choice (end game, final lap, eleventh<br>
hour, don't cut the blue wire (just seeing if you're paying attention)).<br>
Today is the scheduled date for creating the Fedora 13 release<br>
candidate. Any delays in creating the release candidate put Fedora 13<br>
at risk for a 1 week slip.<br>
<br>
Thanks,<br>
James<br>
<br>
[1]<br>
<a href="http://poelstra.fedorapeople.org/schedules/f-13/f-13-quality-tasks.html" target="_blank">http://poelstra.fedorapeople.org/schedules/f-13/f-13-quality-tasks.html</a><br>
[2] <a href="https://fedoraproject.org/wiki/Fedora_13_Final_Release_Criteria" target="_blank">https://fedoraproject.org/wiki/Fedora_13_Final_Release_Criteria</a><br>
<br>
= anaconda =<br>
* 571900 (<a href="mailto:mgracik@redhat.com">mgracik@redhat.com</a>) NEW - Keyboard mapping not correct<br>
(USA instead of Belgium) when first login after install Fedora<br>
13 Alpha -<br>
* 588597 (<a href="mailto:anaconda-maint-list@redhat.com">anaconda-maint-list@redhat.com</a>) NEW - "DeviceError:<br>
('device has not been created'<br>
<br>
= kernel =<br>
* 587171 (<a href="mailto:ajax@redhat.com">ajax@redhat.com</a>) ASSIGNED - Intel kms leads to an all<br>
black display<br>
<br>
= preupgrade =<br>
* 587627 (<a href="mailto:richard@hughsie.com">richard@hughsie.com</a>) ASSIGNED - Kickstart file is not<br>
generated when no space for install.img<br>
<br>--<br>
devel mailing list<br>
<a href="mailto:devel@lists.fedoraproject.org">devel@lists.fedoraproject.org</a><br>
<a href="https://admin.fedoraproject.org/mailman/listinfo/devel" target="_blank">https://admin.fedoraproject.org/mailman/listinfo/devel</a><br></blockquote></div><br><br clear="all"><br>-- <br>Fedora && Debian User, former Ubuntu User<br>
My Page: <a href="http://www.liangsuilong.info">http://www.liangsuilong.info</a><br>Fedora Project Contributor -- Packager && Ambassador<br><a href="https://fedoraproject.org/wiki/User:Liangsuilong">https://fedoraproject.org/wiki/User:Liangsuilong</a><br>
</div></div>