Greetings testers,
Adam Williamson and Ben Skeggs have lined up an exciting Fedora Test Day topic. This Thursday, March 26 will focus on testing the new nouveau graphics driver. If the Intel graphics test day [1] was any indication, this will be a busy event.
As outlined in the NouveauAsDefault feature page [2], the nouveau driver will be replacing the previous 'nv' driver for nVidia chipsets. There are several notable improvements including RANDR 1.2 support and accelerated XRENDER support. To determine if you have the required hardware, run the following command:
# /sbin/lspci -d 10de: | grep -iq VGA && echo "Join Nouveau Fedora Test Day"
So come join #fedora-qa this Thursday, March 26, 2009 to share your Nouveau graphics test results. A Fedora live image will be available to aid testing. Stay tuned for more details are available at https://fedoraproject.org/wiki/QA/Test_Days/2009-03-24.
Thanks, James
[1] https://fedoraproject.org/wiki/QA/Test_Days/2009-03-12 [2] https://fedoraproject.org/wiki/Features/NouveauAsDefault
_______________________________________________ Fedora-devel-announce mailing list Fedora-devel-announce@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-announce
Hi!
On 24.03.2009 22:28, James Laska wrote:
Greetings testers,
Adam Williamson and Ben Skeggs have lined up an exciting Fedora Test Day topic. This Thursday, March 26 will focus on testing the new nouveau graphics driver. If the Intel graphics test day [1] was any indication, this will be a busy event.
Why are these "Fedora Test Day" announcements being send to fedora-devel-announce? I can't see how they fit into the rule set that https://www.redhat.com/mailman/listinfo/fedora-devel-announce lists. Quoting it here again:
"""
This list is intended to be a LOW TRAFFIC announce-only list for Fedora development.
Acceptable Types of Announcements
- Policy or process changes that affect developers.
- Infrastructure changes that affect developers.
- Tools changes that affect developers.
- Schedule changes
- Freeze reminders
Unacceptable Types of Announcements
- Periodic automated reports (violates the INFREQUENT rule)
- Discussion
- Anything else not mentioned above
In order to post. you must be subscribed as a member. Then your post will be allowed into the moderation queue.
"""
They IMHO violate the hinted "INFREQUENT rule", as they come weekly right now.
CU knurd (who is getting more and more worried that packagers with only one or two packages start to ignore fedora-devel-announce because it gets more and more mails that are not of interest for them)
P.S.: While at it: The mail "Fedora 11 Beta slip" definitely was okay for fedora-devel-announce, but I wonder if it should have gone to fedora-announce-list as well, as such slips in the past normally have been announced there; take the F11 Alpha slip for example: http://www.redhat.com/archives/fedora-announce-list/2009-February/msg00003.h...
On Wed, 2009-03-25 at 07:38 +0100, Thorsten Leemhuis wrote:
Hi!
On 24.03.2009 22:28, James Laska wrote:
Greetings testers,
Adam Williamson and Ben Skeggs have lined up an exciting Fedora Test Day topic. This Thursday, March 26 will focus on testing the new nouveau graphics driver. If the Intel graphics test day [1] was any indication, this will be a busy event.
Why are these "Fedora Test Day" announcements being send to fedora-devel-announce? I can't see how they fit into the rule set that https://www.redhat.com/mailman/listinfo/fedora-devel-announce lists. Quoting it here again:
James, I think Thorsten's probably right here. We should probably send them to just -devel, not -devel-announce.
On Wed, 2009-03-25 at 05:21 -0700, Adam Williamson wrote:
On Wed, 2009-03-25 at 07:38 +0100, Thorsten Leemhuis wrote:
Hi!
On 24.03.2009 22:28, James Laska wrote:
Greetings testers,
Adam Williamson and Ben Skeggs have lined up an exciting Fedora Test Day topic. This Thursday, March 26 will focus on testing the new nouveau graphics driver. If the Intel graphics test day [1] was any indication, this will be a busy event.
Why are these "Fedora Test Day" announcements being send to fedora-devel-announce? I can't see how they fit into the rule set that https://www.redhat.com/mailman/listinfo/fedora-devel-announce lists. Quoting it here again:
James, I think Thorsten's probably right here. We should probably send them to just -devel, not -devel-announce.
Sounds like a plan. I'll make sure future announcements go out to fedora-devel-list@.
Thanks for the feedback! James
On Wed, 2009-03-25 at 07:38 +0100, Thorsten Leemhuis wrote:
P.S.: While at it: The mail "Fedora 11 Beta slip" definitely was okay for fedora-devel-announce, but I wonder if it should have gone to fedora-announce-list as well, as such slips in the past normally have been announced there; take the F11 Alpha slip for example: http://www.redhat.com/archives/fedora-announce-list/2009-February/msg00003.h...
Just oversight on my part when trying to quickly get the message out before a local appointment took me away for the rest of the day.
Hi,
I would like to test, but currently the livecd is not available (though links are there), any chance to fix that until ~16:00 ALPHA?
thanks
christoph
On Wed, 2009-03-25 at 10:10 +0100, Christoph Höger wrote:
Hi,
I would like to test, but currently the livecd is not available (though links are there), any chance to fix that until ~16:00 ALPHA?
James Laska is going to upload the images some time today - we were mostly focusing on having them up before Thursday. Unfortunately the images we generated yesterday are missing the updated libdrm from Koji (I didn't realize we needed that as well as kernel and the nouveau package), so we may have to rebuild them today. They'll definitely be up by tomorrow at the latest, though.
Hi,
I just did the test and at least the live cd boots into X, that's a lot more than my last test of nouveau.
But a few questions arised:
- how can I install mplayer into that live system to test XV? shouldn't yum install mplayer work? Do I have to manually set up rawhide repos?
- what is the way to restart X on that livecd? Just killing the xserver did not work and someone did deactivate CTRL - ALT - BACKSPACE (grml, as if people would hit that combo accidentally...)
- I did not see any KMS stuff (native solution, playmouth gfx) should I?
regards
christoph
On Wed, 2009-03-25 at 19:55 +0100, Christoph Höger wrote:
Hi,
I just did the test and at least the live cd boots into X, that's a lot more than my last test of nouveau.
But a few questions arised:
- how can I install mplayer into that live system to test XV? shouldn't
yum install mplayer work? Do I have to manually set up rawhide repos?
Do a shift-refresh on that page. I've reworked the test case not to use mplayer, since it's not actually available in the official repos (it's in rpmfusion). The updated version of the test case uses totem.
this sucks, because mplayer is great - it gives very verbose output on what the hell it's doing, which no other video player does. Ah well.
- what is the way to restart X on that livecd? Just killing the xserver
did not work and someone did deactivate CTRL - ALT - BACKSPACE (grml, as if people would hit that combo accidentally...)
You can actually follow the test case - you can edit the boot options for the live CD as described in the test case. Other than that, ctrl-alt-f2, log in as root, kill the Xorg process, run startx.
- I did not see any KMS stuff (native solution, playmouth gfx) should I?
No - it's not enabled by default. If you want to test it, you can enable it: set 'nouveau.modeset=1' as a kernel parameter. I might throw together a test case for this.
On Wed, 2009-03-25 at 12:27 -0700, Adam Williamson wrote:
- I did not see any KMS stuff (native solution, playmouth gfx) should I?
No - it's not enabled by default. If you want to test it, you can enable it: set 'nouveau.modeset=1' as a kernel parameter. I might throw together a test case for this.
I've just added a KMS test case to the Test Day page. Everyone who's already tested, if you could add your result for the KMS test, that would be awesome. I may also add a rendercheck test case before tomorrow.
Thanks!
Hi,
this was awesome! I got KMS; xv, restart x working flawlessly. Pretty good job. Thanks for the work made. I am still impressed from KMS.
posting my results to the wiki soon
christoph
On Wed, 2009-03-25 at 12:44 -0700, Adam Williamson wrote:
I've just added a KMS test case to the Test Day page. Everyone who's already tested, if you could add your result for the KMS test, that would be awesome. I may also add a rendercheck test case before tomorrow.
I must be doing something wrong, but enabling modeset on grub boot tells me incorrect parameter? If you wanted to edit your grub.conf itself and add it there , would someone post theirs and show me what line and how it's set for it to work? I've done it via grub.conf and tried via just boot up and adding it before booting and either way gives me an error.
Am Mittwoch, den 25.03.2009, 17:40 -0500 schrieb Mike Chambers:
On Wed, 2009-03-25 at 12:44 -0700, Adam Williamson wrote:
I've just added a KMS test case to the Test Day page. Everyone who's already tested, if you could add your result for the KMS test, that would be awesome. I may also add a rendercheck test case before tomorrow.
I must be doing something wrong, but enabling modeset on grub boot tells me incorrect parameter? If you wanted to edit your grub.conf itself and add it there , would someone post theirs and show me what line and how it's set for it to work? I've done it via grub.conf and tried via just boot up and adding it before booting and either way gives me an error.
Just go on, kernel complained about incorrect param to me too, but kms worked like a charm.
On Wed, 2009-03-25 at 23:49 +0100, Christoph Höger wrote:
Am Mittwoch, den 25.03.2009, 17:40 -0500 schrieb Mike Chambers:
On Wed, 2009-03-25 at 12:44 -0700, Adam Williamson wrote:
I've just added a KMS test case to the Test Day page. Everyone who's already tested, if you could add your result for the KMS test, that would be awesome. I may also add a rendercheck test case before tomorrow.
I must be doing something wrong, but enabling modeset on grub boot tells me incorrect parameter? If you wanted to edit your grub.conf itself and add it there , would someone post theirs and show me what line and how it's set for it to work? I've done it via grub.conf and tried via just boot up and adding it before booting and either way gives me an error.
Just go on, kernel complained about incorrect param to me too, but kms worked like a charm.
Right - that message is bogus, just ignore it. I've added a note to the test case now.
On Wed, Mar 25, 2009 at 17:40:19 -0500, Mike Chambers mike@miketc.net wrote:
I must be doing something wrong, but enabling modeset on grub boot tells me incorrect parameter? If you wanted to edit your grub.conf itself and add it there , would someone post theirs and show me what line and how it's set for it to work? I've done it via grub.conf and tried via just boot up and adding it before booting and either way gives me an error.
modeset is the default. You use nomodeset to turn it off.
On Wed, Mar 25, 2009 at 07:43:17PM -0500, Bruno Wolff III wrote:
On Wed, Mar 25, 2009 at 17:40:19 -0500, Mike Chambers mike@miketc.net wrote:
I must be doing something wrong, but enabling modeset on grub boot tells me incorrect parameter? If you wanted to edit your grub.conf itself and add it there , would someone post theirs and show me what line and how it's set for it to work? I've done it via grub.conf and tried via just boot up and adding it before booting and either way gives me an error.
modeset is the default. You use nomodeset to turn it off.
This wasn't my experience on the Test Day Live image. I had to use the modeset parameter to explicitly enable modesetting.
Paul W. Frields wrote:
On Wed, Mar 25, 2009 at 07:43:17PM -0500, Bruno Wolff III wrote:
On Wed, Mar 25, 2009 at 17:40:19 -0500, Mike Chambers mike@miketc.net wrote:
I must be doing something wrong, but enabling modeset on grub boot tells me incorrect parameter? If you wanted to edit your grub.conf itself and add it there , would someone post theirs and show me what line and how it's set for it to work? I've done it via grub.conf and tried via just boot up and adding it before booting and either way gives me an error.
modeset is the default. You use nomodeset to turn it off.
This wasn't my experience on the Test Day Live image. I had to use the modeset parameter to explicitly enable modesetting.
Modesetting is only on by default on ATI and Intel. Nvidia, it is opt-in.
Rahul
I Can't make my second monitor work with norveau
I am using lasted rawhide.
mirroring screen works, but I don't want a mirrored screen (I want independent screens)
On Thu, Mar 26, 2009 at 12:41 PM, Rahul Sundaram sundaram@fedoraproject.org wrote:
Paul W. Frields wrote:
On Wed, Mar 25, 2009 at 07:43:17PM -0500, Bruno Wolff III wrote:
On Wed, Mar 25, 2009 at 17:40:19 -0500, Mike Chambers mike@miketc.net wrote:
I must be doing something wrong, but enabling modeset on grub boot tells me incorrect parameter? If you wanted to edit your grub.conf itself and add it there , would someone post theirs and show me what line and how it's set for it to work? I've done it via grub.conf and tried via just boot up and adding it before booting and either way gives me an error.
modeset is the default. You use nomodeset to turn it off.
This wasn't my experience on the Test Day Live image. I had to use the modeset parameter to explicitly enable modesetting.
Modesetting is only on by default on ATI and Intel. Nvidia, it is opt-in.
Rahul
-- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Itamar Reis Peixoto wrote:
I Can't make my second monitor work with norveau
I am using lasted rawhide.
mirroring screen works, but I don't want a mirrored screen (I want independent screens)
On Thu, Mar 26, 2009 at 12:41 PM, Rahul Sundaram sundaram@fedoraproject.org wrote:
Paul W. Frields wrote:
On Wed, Mar 25, 2009 at 07:43:17PM -0500, Bruno Wolff III wrote:
On Wed, Mar 25, 2009 at 17:40:19 -0500, Mike Chambers mike@miketc.net wrote:
I must be doing something wrong, but enabling modeset on grub boot tells me incorrect parameter? If you wanted to edit your grub.conf itself and add it there , would someone post theirs and show me what line and how it's set for it to work? I've done it via grub.conf and tried via just boot up and adding it before booting and either way gives me an error.
modeset is the default. You use nomodeset to turn it off.
This wasn't my experience on the Test Day Live image. I had to use the modeset parameter to explicitly enable modesetting.
Modesetting is only on by default on ATI and Intel. Nvidia, it is opt-in.
Rahul
-- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
There's a current Xorg limitation with virtual screen size maxing out at 1920x1920, so if the sum of the vertical or horizontal sizes of your screen exceeds 1920, it won't work.
This can be fixed in the xorg.conf with Section "Screen" Identifier "Screen0" Device "Videocard0" DefaultDepth 24 SubSection "Display" Virtual 3600 1200 Viewport 0 0 Depth 24 EndSubSection EndSection
for example
- -- Stephen Gallagher RHCE 804006346421761
Looking to carve out IT costs? www.redhat.com/carveoutcosts/
On Thu, 2009-03-26 at 12:38 -0300, Itamar Reis Peixoto wrote:
I Can't make my second monitor work with norveau
I am using lasted rawhide.
mirroring screen works, but I don't want a mirrored screen (I want independent screens)
Lots of people have reported this: the problem is the same one intel used to have, it doesn't automatically allocate a framebuffer big enough for both screens. There's a bug for this now:
https://bugzilla.redhat.com/show_bug.cgi?id=492175
in that bug I've asked Ben for his input on the status of this wrt nouveau. As someone else followed up, the workaround is the same as it used to be for Intel - you need an xorg.conf file with a proper Screens section, and set the Virtual in the screens section to be the combined resolution for the dual-head mode you want.
On Wed, 2009-03-25 at 19:43 -0500, Bruno Wolff III wrote:
On Wed, Mar 25, 2009 at 17:40:19 -0500, Mike Chambers mike@miketc.net wrote:
I must be doing something wrong, but enabling modeset on grub boot tells me incorrect parameter?
That's expected, and you can ignore it. The *kernel* complains because it doesn't understand 'nouveau.modeset=1'. But the nouveau *module* understands it fine.
If you wanted to edit your grub.conf itself and add it there , would someone post theirs and show me what line and how it's set for it to work? I've done it via grub.conf and tried via just boot up and adding it before booting and either way gives me an error.
modeset is the default. You use nomodeset to turn it off.
That's for intel and radeon, not nouveau. See the *other* feature page for details on modesetting with nouveau:
http://fedoraproject.org/wiki/Features/NouveauModesetting
I added a note to the NouveauAsDefault wiki page to clarify a bit.
-w
On Wed, 2009-03-25 at 19:43 -0500, Bruno Wolff III wrote:
On Wed, Mar 25, 2009 at 17:40:19 -0500, Mike Chambers mike@miketc.net wrote:
I must be doing something wrong, but enabling modeset on grub boot tells me incorrect parameter? If you wanted to edit your grub.conf itself and add it there , would someone post theirs and show me what line and how it's set for it to work? I've done it via grub.conf and tried via just boot up and adding it before booting and either way gives me an error.
modeset is the default. You use nomodeset to turn it off.
Not for nouveau. It's disabled by default on nouveau.
On Wed, Mar 25, 2009 at 3:40 PM, Mike Chambers mike@miketc.net wrote:
On Wed, 2009-03-25 at 12:44 -0700, Adam Williamson wrote:
I've just added a KMS test case to the Test Day page. Everyone who's already tested, if you could add your result for the KMS test, that would be awesome. I may also add a rendercheck test case before tomorrow.
I must be doing something wrong, but enabling modeset on grub boot tells me incorrect parameter? If you wanted to edit your grub.conf itself and add it there , would someone post theirs and show me what line and how it's set for it to work? I've done it via grub.conf and tried via just boot up and adding it before booting and either way gives me an error.
The kernel doesn't know what to do with the parameter because nouveau is a loadable module. But modprobe will pick up the option when it's run by udev. Don't worry about the kernel saying it's an incorrect parameter. At some point, the kernel should probably be fixed to issue this warning when the module is builtin.
-- Dan
2009/3/24 James Laska jlaska@redhat.com:
Greetings testers,
Hi, when I try to boot from the Live CD, I get the following messages:
Buffer I/O error on device sr0, logical block 333952 end_request: I/O error, dev sr0, sector 1335680
As far as I can tell, the CD burned okay.
On Thu, 2009-03-26 at 18:32 -0700, Christopher Stone wrote:
2009/3/24 James Laska jlaska@redhat.com:
Greetings testers,
Hi, when I try to boot from the Live CD, I get the following messages:
Buffer I/O error on device sr0, logical block 333952 end_request: I/O error, dev sr0, sector 1335680
As far as I can tell, the CD burned okay.
It almost certainly didn't. That's a classic bad burn error, and no-one else has had it.
On Thu, Mar 26, 2009 at 8:57 PM, Adam Williamson awilliam@redhat.com wrote:
On Thu, 2009-03-26 at 18:32 -0700, Christopher Stone wrote:
2009/3/24 James Laska jlaska@redhat.com:
Greetings testers,
Hi, when I try to boot from the Live CD, I get the following messages:
Buffer I/O error on device sr0, logical block 333952 end_request: I/O error, dev sr0, sector 1335680
As far as I can tell, the CD burned okay.
It almost certainly didn't. That's a classic bad burn error, and no-one else has had it.
hmm okay, well I have already cleaned all the dust out of my PC, and I have upgraded my IDE cable to an 80-conductor cable, and the DVDRW is now a primary instead of a slave. These actions did not help however, I get slightly different results (different block and sector numbers). I will try doing a full erase and burn again and see if this helps at all.
Greetings testers,
Thanks to all who participated! Test days with Live images are always very popular. I've also learned that Test Days that focus on high-profile features that impact a large set of users are even more popular.
Just wanted to share some highlights:
* 1 test day announcement that pointed to the wrong wiki page [1] (https://www.redhat.com/archives/fedora-test-list/2009-March/msg01126.html) * 6 nouveau test cases created by Adam Williamson (https://fedoraproject.org/wiki/Category:Nouveau_Test_Cases) * 68 recorded unique participants (https://fedoraproject.org/wiki/QA/Test_Days/2009-03-26#Results) * 47 bugs filed (http://tinyurl.com/dxvexk) * 38 NEW * 4 CLOSED DUPLICATE * 4 CLOSED NOTABUG * 1 CLOSED RAWHIDE
Many thanks to Adam Williamson for coordinating testing and tirelessly keeping the communication lines flowing throughout the day.
Thanks again, James
[1] I *think* dmalcolm fixed my goof here. Thank you Dave!
On Tue, 2009-03-24 at 17:28 -0400, James Laska wrote:
Greetings testers,
Adam Williamson and Ben Skeggs have lined up an exciting Fedora Test Day topic. This Thursday, March 26 will focus on testing the new nouveau graphics driver. If the Intel graphics test day [1] was any indication, this will be a busy event.
As outlined in the NouveauAsDefault feature page [2], the nouveau driver will be replacing the previous 'nv' driver for nVidia chipsets. There are several notable improvements including RANDR 1.2 support and accelerated XRENDER support. To determine if you have the required hardware, run the following command:
# /sbin/lspci -d 10de: | grep -iq VGA && echo "Join Nouveau Fedora Test Day"
So come join #fedora-qa this Thursday, March 26, 2009 to share your Nouveau graphics test results. A Fedora live image will be available to aid testing. Stay tuned for more details are available at https://fedoraproject.org/wiki/QA/Test_Days/2009-03-24.
Thanks, James
[1] https://fedoraproject.org/wiki/QA/Test_Days/2009-03-12 [2] https://fedoraproject.org/wiki/Features/NouveauAsDefault
-- fedora-test-list mailing list fedora-test-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
James Laska <jlaska <at> redhat.com> writes:
Greetings testers,
Thanks to all who participated! Test days with Live images are always very popular. I've also learned that Test Days that focus on high-profile features that impact a large set of users are even more popular.
Will there be a followup test day to allow anyone who was not available on the test day to contribute test results once changes have been made following the success of the test day?
I have two nvidia cards that seem not to have been covered in the test day results. I would certainly like to see the nouveau driver have the best chance of working from day 1 of the next release.
Mike Cloaked wrote:
James Laska <jlaska <at> redhat.com> writes:
Greetings testers,
Thanks to all who participated! Test days with Live images are always very popular. I've also learned that Test Days that focus on high-profile features that impact a large set of users are even more popular.
Will there be a followup test day to allow anyone who was not available on the test day to contribute test results once changes have been made following the success of the test day?
I have two nvidia cards that seem not to have been covered in the test day results. I would certainly like to see the nouveau driver have the best chance of working from day 1 of the next release.
Then test it as soon as you can with the live cd's provided or with the beta release and file bug reports if things aren't working. There is no reasons to limit bug reports to just test days.
Rahul
Rahul Sundaram <sundaram <at> fedoraproject.org> writes:
Then test it as soon as you can with the live cd's provided or with the beta release and file bug reports if things aren't working. There is no reasons to limit bug reports to just test days.
OK will run tests on one of them tonight - and add to the wiki....
On Sat, 2009-03-28 at 18:47 +0000, Mike Cloaked wrote:
James Laska <jlaska <at> redhat.com> writes:
Greetings testers,
Thanks to all who participated! Test days with Live images are always very popular. I've also learned that Test Days that focus on high-profile features that impact a large set of users are even more popular.
Will there be a followup test day to allow anyone who was not available on the test day to contribute test results once changes have been made following the success of the test day?
As it says on the page and as it said in most of the announcements, results submitted after (or before) the test day are still very welcome - you can still perform each of the test cases, either with the live CD or with the latest Rawhide, and report your results. Please be careful to check whether issues you're seeing have already been reported, if you use the live CD (several common issues that many people hit have already been reported and fixed for Rawhide).
I have two nvidia cards that seem not to have been covered in the test day results. I would certainly like to see the nouveau driver have the best chance of working from day 1 of the next release.
I'd like to do a follow-up but we're really running out of days! I'm already committed to a follow-up for the intel test day, and we're already double-dipping test days each week because we've run out of regular Thursday slots right up to the release. I don't want to overload the schedule too far. But if we can crowbar it in somewhere, sure, we'll do it.
On Monday, March 30 2009, Adam Williamson said:
I'd like to do a follow-up but we're really running out of days! I'm already committed to a follow-up for the intel test day, and we're already double-dipping test days each week because we've run out of regular Thursday slots right up to the release. I don't want to overload the schedule too far. But if we can crowbar it in somewhere, sure, we'll do it.
Perhaps it makes sense to have the follow-up day be "modesetting, all graphics drivers" rather than just an Intel-specific one.
Of course, nothing stops people from running through the test day tests with later images that weren't intended for that test day either...
Jeremy
On Mon, 2009-03-30 at 15:18 -0400, Jeremy Katz wrote:
On Monday, March 30 2009, Adam Williamson said:
I'd like to do a follow-up but we're really running out of days! I'm already committed to a follow-up for the intel test day, and we're already double-dipping test days each week because we've run out of regular Thursday slots right up to the release. I don't want to overload the schedule too far. But if we can crowbar it in somewhere, sure, we'll do it.
Perhaps it makes sense to have the follow-up day be "modesetting, all graphics drivers" rather than just an Intel-specific one.
It's not only modesetting - each test day covered a rather wide range of topics. The idea of a combined test day for all three drivers was mooted, but I felt it would be rather unwieldy - we'd have hundreds of people and several developers trying to follow several entirely different topics all at once.
Of course, nothing stops people from running through the test day tests with later images that weren't intended for that test day either...
Yes, in fact the live CD image links for older test days will probably get updated to the images generated for later test days.
devel@lists.stg.fedoraproject.org