Test Day:2014-09-18 ARM

Fedora Test Days
ARM Test Day
Date	2014-09-18
Time	all day
Website	QA/Fedora_21_test_days
IRC	#fedora-test-day (webirc)
Mailing list	test

Can't make the date?
If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at Bugzilla, and add your results to the results section. If this page is more than a month old when you arrive here, please check the current schedule and see if a similar but more recent Test Day is planned or has already happened.

What to test?

Today's installment of Fedora Test Day will focus on ARM 21_Alpha_TC7, and determine our supported hardware platforms.

Who's available

The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...

• Development - pbrobinson (pbrobinson), Developer2 (irc_nick2)
• Quality Assurance - pwhalen (pwhalen), roshi (roshi), Tester3 (irc_nick5)

Prerequisite for Test Day

• MicroSD, SD (SATA HD optional)
• Supported ARM board (full list can be found here.)
• Free space on HD
• Todays Fedora 21 Release Candidate image : 21_Alpha_RC1 Images

How to test?

Download a disk image from Koji, and write to media. Existing instructions for supported hardware can be found at on the Fedora Wiki . After writing the disk image and U-Boot test basic functionality including:

• Network - test wired and wireless connectivity.
• Storage - test all storage options, minimally USB.
• Display - test all available display options.
• Audio - test all audio outputs.

Testing

Minimal recommended testing - Please add additional useful tests to the wiki!

Serial

Connect serial cable to your device, use minicom to connect

sudo minicom -D /dev/ttyUSB0 # may need to be adjusted if testing more than one device

USB and Storage

yum install usbutils
lsusb
dmesg | grep sda

Network

ip addr
# Check for updates
yum update

Test Results

Construct a table or list to allow testers to post results. Each column should be a test case or configuration, and each row should consist of test results. Include some instructions on how to report bugs, and any special instructions. Here's an example, from a Palimpsest test day:

If you have problems with any of the tests, report a bug to Bugzilla usually for the component udisks, or gnome-disk-utility for bugs in the Palimpsest graphical front end itself. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you. Once you have completed the tests, add your results to the Results table below, following the example results from the first line as a template. The first column should be your name with a link to your User page in the Wiki if you have one. For each test case, use the result template to enter your result, as shown in the example result line.

Primary

Board	User	Serial	Networking	Storage	Audio	References
Example Board	Sample User	none	pass	warn	fail
Banana-Pi	none	none	none	none	none
BeagleBone-Black	none	none	none	none	none
CubieBoard	none	none	none	none	none
CubieTruck	none	none	none	none	none
Cubox-i	none	none	none	none	none
Highbank	none	none	none	none	none
Hummingboard	none	none	none	none	none
Midway	none	none	none	none	none
PandaBoard	none	none	none	none	none
RIoTBoard	none	none	none	none	none
Tegra-K1-Jetson	none	none	none	none	none
Trimslice	none	none	none	none	none
Utilite	none	none	none	none	none
VExpress	none	none	none	none	none

Secondary

Board	User	Serial	Networking	Storage	Audio	References
Example Board	Sample User	none	pass	warn	fail
BeagleBone-White	none	none	none	none	none
Beagle-xM	none	none	none	none	none
Novena	none	none	none	none	none
Qualcomm-(IFC6410,DragonBoard)	none	none	none	none	none
UDOO	none	none	none	none	none