Good morning,
The F26 Alpha 1.2 candidate is available now for testing on arm and aarch64.
Please record your results for aarch64 on the wiki here: https://fedoraproject.org/wiki/Architectures/AArch64/QA/Fedora_26_Alpha_1.2
For armhfp see below.
Thanks and happy testing! Paul
----- Forwarded Message -----
From: rawhide@fedoraproject.org To: test-announce@lists.fedoraproject.org Sent: Wednesday, March 22, 2017 4:36:05 AM Subject: [Test-Announce] Fedora 26 Candidate Alpha-1.2 Available Now!
According to the schedule [1], Fedora 26 Candidate Alpha-1.2 is now available for testing. Please help us complete all the validation testing! For more information on release validation testing, see: https://fedoraproject.org/wiki/QA:Release_validation_test_plan
Test coverage information for the current release can be seen at: https://www.happyassassin.net/testcase_stats/26
You can see all results, find testing instructions and image download locations, and enter results on the Summary page:
https://fedoraproject.org/wiki/Test_Results:Fedora_26_Alpha_1.2_Summary
The individual test result pages are:
https://fedoraproject.org/wiki/Test_Results:Fedora_26_Alpha_1.2_Installation https://fedoraproject.org/wiki/Test_Results:Fedora_26_Alpha_1.2_Base https://fedoraproject.org/wiki/Test_Results:Fedora_26_Alpha_1.2_Server https://fedoraproject.org/wiki/Test_Results:Fedora_26_Alpha_1.2_Cloud https://fedoraproject.org/wiki/Test_Results:Fedora_26_Alpha_1.2_Desktop https://fedoraproject.org/wiki/Test_Results:Fedora_26_Alpha_1.2_Security_Lab
All Alpha priority test cases for each of these test pages [2] must pass in order to meet the Alpha Release Criteria [3].
Help is available on #fedora-qa on irc.freenode.net [4], or on the test list [5].
Current Blocker and Freeze Exception bugs: http://qa.fedoraproject.org/blockerbugs/current
[1] http://fedorapeople.org/groups/schedule/f-26/f-26-quality-tasks.html [2] https://fedoraproject.org/wiki/QA:Release_validation_test_plan [3] https://fedoraproject.org/wiki/Fedora_26_Alpha_Release_Criteria [4] irc://irc.freenode.net/fedora-qa [5] https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/ _______________________________________________ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-leave@lists.fedoraproject.org _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org
Tested minimal and server images on RPi 3.
Two issues: - boot OOPSes in mmc card initialisation (just before remount to root fs) and if it is not freezes completely ends in dracut prompt - USB keyboard is not working when dracut prompt is reached (keyboard is OK as I'm able to use it in uboot prompt)
I've started testing those images because my original +5 months almost ever day updated rawhide bases system has been bricked somewhere after kernel 4.11 rc2 when it seems RPi 3 firmware has been updated. After this last update I found that my RPi 3 is not bringing up eth interface. Trying to diagnose this issue I found that additionally usb keyboard was cut off as well. Seems what was introduced after first 4.11 ~rc2 kernel now is part of every day regenerated images.
Would be glad if someone could confirm the same effects on RPi 3 (to be sure that my HW still is OK).
kloczek
On Wed, Mar 22, 2017 at 5:13 PM, Tomasz Kłoczko kloczko.tomasz@gmail.com wrote:
Tested minimal and server images on RPi 3.
Two issues:
- boot OOPSes in mmc card initialisation (just before remount to root fs)
and if it is not freezes completely ends in dracut prompt
- USB keyboard is not working when dracut prompt is reached (keyboard is OK
as I'm able to use it in uboot prompt)
Can you try adding module_blacklist=bcm2835-dma to the kernel command line and see if that helps.
I've started testing those images because my original +5 months almost ever day updated rawhide bases system has been bricked somewhere after kernel 4.11 rc2 when it seems RPi 3 firmware has been updated. After this last update I found that my RPi 3 is not bringing up eth interface. Trying to diagnose this issue I found that additionally usb keyboard was cut off as well. Seems what was introduced after first 4.11 ~rc2 kernel now is part of every day regenerated images.
Would be glad if someone could confirm the same effects on RPi 3 (to be sure that my HW still is OK).
kloczek
Tomasz Kłoczko | LinkedIn: http://lnkd.in/FXPWxH
arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-leave@lists.fedoraproject.org
-
Paul Whalen -
Peter Robinson -
Tomasz Kłoczko