| Modems Test days | |
|---|---|
| |
| Date | 2016-08-25 |
| Time | all day |
| Website | QA/Test Days |
| IRC | #fedora-test-day (webirc) |
| Mailing list | test |
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 instalment of Fedora Test Day will focus on Modem support.
If you're interested to learn more about how do modems work in Linux and why is it important to test it, you can read this article: [1]
Who's available
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
- Development - Lubomir Rintel (lubko)
Prerequisite for Test Day
- A Fedora 25 nightly image
- A modem or a phone (Bluetooth DUN or ACM)
How to test?
- Plug in the modem
- Wait until the modem is available (seen with "mmcli --list-modems")
- Establish an internet connection
Update your machine
If you're running Fedora 25, make sure you have all the current updates for it installed, using the update manager. If you want to try Rawhide, see the instructions on the Rawhide page on the various ways in which you can install or update to Rawhide. Or:
Live image
Instead of testing with an installed system, you may download a non-destructive nightly live image for your architecture. Tips on using a live image are available at FedoraLiveCD. Live image links can be found here: please be sure to download one for the correct release.
Reporting bugs
If you have problems with any of the tests, please report a bug to Bugzilla usually for the component ModemManager.
Please include the following information:
- The model of your modem/phone
- The output of "lsusb -vv" and "mmcli --list-modems"
- The journal (run "journalctl -fl" when plugging the modem and activating the connection
- The most detailed log is obtained by running ModemManager in debug mode: "systemctl stop ModemManager; ModemManager --debug --log-level=DEBUG"
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.
Test Results
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.
| User | Modem model | Modem vendor/product (from lsusb) | Test result | References |
|---|---|---|---|---|
| Lubomir Rintel | D-Link DWM-156 A3 3.02WW | 07d1:a804 D-Link System |  |
|
| Lubomir Rintel | HSDBA Wireless Data Card | 05c6:6000 Qualcomm, Inc. |  |