Re: Testing with NVMe
On Sat, Apr 4, 2020 at 4:03 PM pmkel...@frontier.com wrote: > > On 4/4/20 15:27, Richard Shaw wrote: > > On Sat, Apr 4, 2020 at 10:45 AM pmkel...@frontier.com < > pmkel...@frontier.com> > > wrote: > > > > > > > I'm not sure the having UEFI is the differentiator... I have a 6th gen I5 > > computer which boots UEFI fine but predates NVMe. On that one I use a > > PCIEx4 adapter and have /boot and /boot/EFI on the HD and then the system > > on the NVMe drive. > > > > My test machine is a 4th gen. i5-4570. From what I can tell it wouldn't > be able to boot to a NVMe on a PCI adapter. > Correct. > I could get a NVMe set up on an adapter like I was originally thinking, > but I do testing on Workstation-Live and I take the defaults for > installation; so is there someplace where I can learn how to split the > installation like you've done it with the /boot and /boot/EFI on the HD > and the System on the NVMe? > You have to setup all the partitioning manually unfortunately. > Then there is the question: Would testing Workstation set up like that > would be of value to the project? I'm thinking there aren't many users > set up like that. Also, it might be a confusion factor for any bugs I find. > Nope, I wouldn't bother testing it that way. I think in the original thread you said you don't have a new enough computer that has M.2/NVMe built-in correct? Kinda hard to test it then :) If you really want to be able to then you'll need some newer hardware. If $$$ is a problem, maybe an inexpensive micro-ATX and Athlon 200GE chip. Thanks, Richard ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: Testing with NVMe
On 4/4/20 15:27, Richard Shaw wrote: On Sat, Apr 4, 2020 at 10:45 AM pmkel...@frontier.com wrote: I'm not sure the having UEFI is the differentiator... I have a 6th gen I5 computer which boots UEFI fine but predates NVMe. On that one I use a PCIEx4 adapter and have /boot and /boot/EFI on the HD and then the system on the NVMe drive. My test machine is a 4th gen. i5-4570. From what I can tell it wouldn't be able to boot to a NVMe on a PCI adapter. I could get a NVMe set up on an adapter like I was originally thinking, but I do testing on Workstation-Live and I take the defaults for installation; so is there someplace where I can learn how to split the installation like you've done it with the /boot and /boot/EFI on the HD and the System on the NVMe? Then there is the question: Would testing Workstation set up like that would be of value to the project? I'm thinking there aren't many users set up like that. Also, it might be a confusion factor for any bugs I find. Thanks for your help. Stay Safe and Stay Well Pat (tablepc) ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: Testing with NVMe
On Sat, Apr 4, 2020 at 10:45 AM pmkel...@frontier.com wrote: > On 4/4/20 10:24, Richard Shaw wrote: > > On Sat, Apr 4, 2020 at 9:14 AM pmkel...@frontier.com < > pmkel...@frontier.com> > > wrote: > > M.2 SSD's can come in SATA and NVMe variants. > > > > As far as USB 3.0, it's pretty fast and someone may want compact a M.2 > NVMe > > SSD in a USB 3.0 enclosure for convenience. > > I guess, but an ordinary SSD in an external box would do as well. USB 3 > is the limiting factor for speed. Though being able to boot might be an > advantage for test. In this case I would ask what is it we really want > to test, high speed access and data flow, or just ordinary operation > like booting and normal use at desktop kind of speeds? > Can't say why manufacturing make 'em, but M.2 form is a little smaller than a 2.5" drive... > > From the various conversations with the test folks over time, it seems > >> many in the group test on laptops. Many of the newer lap tops have a > >> connector on the motherboard that connects an NVMe to PCI-E. This and > >> the above leads me to believe that the testing we want to do is with > >> NVMe on PCI-E. That's what I'm planning at this time. > >> > > > > Yes I think that would cover the vast majority of situations, but that > > includes many desktops today too, not just laptops. I'm running a Samsung > > 970 EVO on my Ryzen 5 2600 system. > > > > > > Is that your only "disk" for boot and whatever else you do? > I run it as my system drive with a 2TB drive dedicated to /home. > > I have only desktops none of the ones I support have such a slot on the > >> mother board. No worries; There are PCI-E adapter boards that NVMe > >> modules can be plugged into then the board plugs into a standard PCI-E > >> four channel slot. This is the route I'm planning to go. > >> > > > > That should work for secondary storage (and testing) but frequently the > > system can't boot from a NVMe add-in card because the BIOS doesn't > support > > it. > > > > Well that's certainly another point to consider. Do you happen to know > if UEFI supports it? I'll have to reboot my test machine later to see if > there is anything that looks like it in the config. pages. > I'm not sure the having UEFI is the differentiator... I have a 6th gen I5 computer which boots UEFI fine but predates NVMe. On that one I use a PCIEx4 adapter and have /boot and /boot/EFI on the HD and then the system on the NVMe drive. Thanks, Richard ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Fedora rawhide compose report: 20200404.n.0 changes
OLD: Fedora-Rawhide-20200403.n.0 NEW: Fedora-Rawhide-20200404.n.0 = SUMMARY = Added images:0 Dropped images: 3 Added packages: 4 Dropped packages:4 Upgraded packages: 182 Downgraded packages: 7 Size of added packages: 554.46 MiB Size of dropped packages:4.96 MiB Size of upgraded packages: 1.63 GiB Size of downgraded packages: 34.02 MiB Size change of upgraded packages: 354.94 MiB Size change of downgraded packages: -2.73 KiB = ADDED IMAGES = = DROPPED IMAGES = Image: Cloud_Base qcow2 ppc64le Path: Cloud/ppc64le/images/Fedora-Cloud-Base-Rawhide-20200403.n.0.ppc64le.qcow2 Image: Cloud_Base vmdk ppc64le Path: Cloud/ppc64le/images/Fedora-Cloud-Base-Rawhide-20200403.n.0.ppc64le.vmdk Image: Cloud_Base raw-xz ppc64le Path: Cloud/ppc64le/images/Fedora-Cloud-Base-Rawhide-20200403.n.0.ppc64le.raw.xz = ADDED PACKAGES = Package: eclipse-1:4.15-5.module_f33+8558+5e2e0c79 Summary: An open, extensible IDE RPMs:eclipse-contributor-tools eclipse-equinox-osgi eclipse-jdt eclipse-p2-discovery eclipse-pde eclipse-platform eclipse-swt Size:534.90 MiB Package: eclipse-ecf-3.14.7-1.module_f33+8420+75d411ed Summary: Eclipse Communication Framework (ECF) Eclipse plug-in RPMs:eclipse-ecf-core eclipse-ecf-runtime eclipse-ecf-sdk Size:4.51 MiB Package: eclipse-emf-1:2.21.0-1.module_f33+8420+75d411ed Summary: EMF and XSD Eclipse plug-ins RPMs:eclipse-emf-core eclipse-emf-runtime eclipse-emf-sdk eclipse-emf-xsd Size:14.90 MiB Package: pam-cryptsetup-0.1-0.3.20190823.7b42892.fc33 Summary: PAM module for updating LUKS-encrypted volumes RPMs:pam-cryptsetup Size:151.41 KiB = DROPPED PACKAGES = Package: dspam-3.10.2-30.fc31 Summary: A library and Mail Delivery Agent for Bayesian SPAM filtering RPMs:dspam dspam-client dspam-devel dspam-hash dspam-libs dspam-mysql dspam-pgsql dspam-sqlite3 dspam-web Size:3.79 MiB Package: fluxcapacitor-0-9.20180118gitf6c7f07.fc31 Summary: Run programs without blocking on syscalls RPMs:fluxcapacitor Size:85.28 KiB Package: google-crosextra-carlito-fonts-1.103-0.12.20130920.fc32 Summary: Sans-serif font metric-compatible with Calibri font RPMs:google-crosextra-carlito-fonts Size:809.11 KiB Package: rubygem-cocoon-1.2.6-12.fc32 Summary: Easier nested forms with standard forms, formtastic and simple-form RPMs:rubygem-cocoon rubygem-cocoon-doc Size:305.75 KiB = UPGRADED PACKAGES = Package: aether-connector-okhttp-0.17.6-3.module_f33+8420+75d411ed Old package: aether-connector-okhttp-0.17.6-3.module_f33+8406+feb0be7b Summary: OkHttp Aether Connector RPMs: aether-connector-okhttp aether-connector-okhttp-javadoc Size: 115.91 KiB Size change: 6 B Package: anaconda-33.7-1.fc33 Old package: anaconda-33.6-1.fc33 Summary: Graphical system installer RPMs: anaconda anaconda-core anaconda-dracut anaconda-gui anaconda-install-env-deps anaconda-live anaconda-tui anaconda-widgets anaconda-widgets-devel Size: 19.44 MiB Size change: 20.12 KiB Changelog: * Fri Apr 03 2020 Martin Kolman - 33.7-1 - Don't clear errors by expanding pages in the custom spoke (vponcova) - Fix the permission for changing a mount point (#1818500) (vponcova) - Allow to use an existing unlocked LUKS in one special case (#1772902) (vponcova) - Fix the encryption checkbox in the custom spoke (#1819360) (vponcova) - Don't manually trigger a device encryption change (vponcova) Package: antlr32-3.2-23.module_f33+8420+75d411ed Old package: antlr32-3.2-23.module_f33+8406+feb0be7b Summary: ANother Tool for Language Recognition RPMs: antlr32-java antlr32-javadoc antlr32-maven-plugin antlr32-tool Size: 1.55 MiB Size change: -2.42 KiB Package: apache-commons-collections-3.2.2-15.module_f33+8420+75d411ed Old package: apache-commons-collections-3.2.2-15.module_f33+8406+feb0be7b Summary: Provides new interfaces, implementations and utilities for Java Collections RPMs: apache-commons-collections apache-commons-collections-javadoc apache-commons-collections-testframework Size: 1.12 MiB Size change: -527 B Package: apache-commons-compress-1.19-1.module_f33+8420+75d411ed Old package: apache-commons-compress-1.19-1.module_f33+8406+feb0be7b Summary: Java API for working with compressed files and archivers RPMs: apache-commons-compress apache-commons-compress-javadoc Size: 1.05 MiB Size change: 58 B Package: apache-commons-discovery-2:0.5-23.module_f33+8420+75d411ed Old package: apache-commons-discovery-2:0.5-23.module_f33+8406+feb0be7b Summary: Apache Commons Discovery RPMs: apache-commons-discovery apache-commons-discovery-javadoc Size: 174.53 KiB Size change: -78 B Package: apache-commons-jxpath-1.3-34.module_f33+8420+75d411ed Old package: apache-commons-jxpath-1.3-34.module_f33+8406+feb0be7b Summary
Fedora 32 compose report: 20200404.n.0 changes
OLD: Fedora-32-20200403.n.0 NEW: Fedora-32-20200404.n.0 = SUMMARY = Added images:0 Dropped images: 0 Added packages: 15 Dropped packages:1 Upgraded packages: 47 Downgraded packages: 1 Size of added packages: 32.68 MiB Size of dropped packages:17.12 KiB Size of upgraded packages: 2.43 GiB Size of downgraded packages: 139.55 KiB Size change of upgraded packages: 40.50 MiB Size change of downgraded packages: -1.29 KiB = ADDED IMAGES = = DROPPED IMAGES = = ADDED PACKAGES = Package: algobox-1.0.3-1.fc32 Summary: Algorithmic software RPMs:algobox Size:2.77 MiB Package: dnstwist-20190706-3.fc32 Summary: Domain name permutation engine RPMs:dnstwist Size:91.48 KiB Package: goloris-0-0.1.20200326gita59fafb.fc32 Summary: Slowloris for NGINX DoS RPMs:golang-github-valyala-goloris-devel goloris Size:7.16 MiB Package: libqmatrixclient-0.5.2-1.fc32 Summary: Qt5 library to write cross-platform clients for Matrix RPMs:libqmatrixclient libqmatrixclient-devel Size:3.41 MiB Package: non-daw-1.2.0-19.20200307gitbbe8386.fc32 Summary: A digital audio workstation for JACK RPMs:non-daw non-mixer non-mixer-doc non-sequencer non-sequencer-doc non-session-manager non-session-manager-doc Size:16.96 MiB Package: python-asysocks-0.0.2-1.fc32 Summary: Socks5/Socks4 client and server library RPMs:python3-asysocks Size:33.62 KiB Package: python-bibtexparser-1.1.0-2.fc32 Summary: A BibTeX parsing library RPMs:python-bibtexparser-doc python3-bibtexparser Size:316.87 KiB Package: python-friendlyloris-1.0.1-1.fc32 Summary: A Slow Loris package for Python RPMs:python3-friendlyloris Size:15.08 KiB Package: python-makeelf-0.3.2-1.fc32 Summary: ELF reader-writer library RPMs:python3-makeelf Size:56.95 KiB Package: python-readability-lxml-0.7.1-2.20200326gitede4d01.fc32 Summary: Fast html to text parser (article readability tool) RPMs:python3-readability-lxml Size:40.12 KiB Package: python-requests-pkcs12-1.7-1.fc32 Summary: Add PKCS12 support to the requests library RPMs:python3-requests-pkcs12 Size:14.19 KiB Package: python-whois-0.9.6-2.fc32 Summary: Python module for retrieving WHOIS information of domains RPMs:python3-whois Size:22.68 KiB Package: quaternion-0.0.9.4c-1.fc32 Summary: A Qt5-based IM client for Matrix RPMs:quaternion Size:1.76 MiB Package: slowloris-0.2.0-1.fc32 Summary: Low bandwidth DoS tool RPMs:python3-slowloris slowloris Size:19.46 KiB Package: vim-rhubarb-0-2.20191014git513059.fc32 Summary: GitHub support for vim-fugitive plugin RPMs:vim-rhubarb Size:11.06 KiB = DROPPED PACKAGES = Package: gnome-shell-extension-no-topleft-hot-corner-19.0-3.fc32 Summary: Disable the "hot corner" in the top-left of GNOME Shell RPMs:gnome-shell-extension-no-topleft-hot-corner Size:17.12 KiB = UPGRADED PACKAGES = Package: HepMC3-3.2.1-1.fc32 Old package: HepMC3-3.2.0-2.fc32 Summary: C++ Event Record for Monte Carlo Generators RPMs: HepMC3 HepMC3-devel HepMC3-doc HepMC3-interfaces-devel HepMC3-rootIO HepMC3-rootIO-devel HepMC3-search HepMC3-search-devel python3-HepMC3 python3-HepMC3-rootIO python3-HepMC3-search Size: 44.27 MiB Size change: 302.66 KiB Changelog: * Tue Jan 28 2020 Mattias Ellert - 3.2.0-3 - Add Python 3.9 as a valid Python version * Sun Mar 22 2020 Mattias Ellert - 3.2.1-1 - Update to version 3.2.1 - Drop patches accepted upstream or previously backported - Fix glitches in the generation of the HepMC3-config script - Add additional Python 3 version package for EPEL 7 (cmake configuration now supports multiple Python 3 versions) - Use new cmake configuration options -DHEPMC3_ROOTIO_INSTALL_LIBDIR and -DHEPMC3_BUILD_STATIC_LIBS and simplify spec file accordingly - .egg-info filenames are now correct - auto generated provides work Package: NetworkManager-l2tp-1.8.2-1.fc32 Old package: NetworkManager-l2tp-1.8.0-5.fc32 Summary: NetworkManager VPN plugin for L2TP and L2TP/IPsec RPMs: NetworkManager-l2tp NetworkManager-l2tp-gnome Size: 1.08 MiB Size change: 3.37 KiB Changelog: * Thu Mar 26 2020 Douglas Kosovic - 1.8.2-1 - Updated to 1.8.2 release - Remove redundant patches - Recommends (libreswan or strongswan) instead of just libreswan Package: R-RInside-0.2.16-1.fc32 Old package: R-RInside-0.2.15-6.fc32 Summary: C++ Classes to Embed R in C++ (and C) Applications RPMs: R-RInside R-RInside-devel R-RInside-examples Size: 816.93 KiB Size change: 69.36 KiB Changelog: * Fri Mar 20 2020 Mattias Ellert - 0.2.16-1 - New release 0.2.16 Package: R-Rcpp-1.0.4-2.fc32 Old package: R-Rcpp-1.0.3-3.fc32 Summary: Seamless R and C++ Integration RPMs: R-Rcpp R-Rcpp-devel R-Rcpp-examples Size: 10.73 MiB Size change: -24.36 KiB Changelog: * Fri M
F32 Workstation-live 0401 drop
I just finished my testing of 0401 on my bare metal test system. The results were not reported because the current event is 0404. Everything looks good except for the bugs I already reported and they are not blockers. https://bugzilla.redhat.com/show_bug.cgi?id=1812510 https://bugzilla.redhat.com/show_bug.cgi?id=1812515 Stay Safe and Well Pat (tablepc) ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: Testing with NVMe
On 4/4/20 10:24, Richard Shaw wrote: On Sat, Apr 4, 2020 at 9:14 AM pmkel...@frontier.com wrote: One thing that seems rather puzzling is that NVMe is offered in three different connection configurations. PCI-E, USB (with a USB connector), and SSD via SATA (with an SATA connector. Since multichannel PCI-E is very much faster that either USB or SATA I don't really understand why the USB and SATA options are offered. It seems a bit like having a car that's designed and built for racing and only driving it on city streets. Are you sure you're not conflating M.2 and NVMe? From what I can tell NVMe is only for storage whereas M.2 is primarily used for storage but there are other types of M.2 cards. Sorry I wasn't more clear about that. Yes M.2 is a physical connector configuration with a specified key position on the connector. Modules with that connector are available in functional types I mentioned. M.2 SSD's can come in SATA and NVMe variants. As far as USB 3.0, it's pretty fast and someone may want compact a M.2 NVMe SSD in a USB 3.0 enclosure for convenience. I guess, but an ordinary SSD in an external box would do as well. USB 3 is the limiting factor for speed. Though being able to boot might be an advantage for test. In this case I would ask what is it we really want to test, high speed access and data flow, or just ordinary operation like booting and normal use at desktop kind of speeds? From the various conversations with the test folks over time, it seems many in the group test on laptops. Many of the newer lap tops have a connector on the motherboard that connects an NVMe to PCI-E. This and the above leads me to believe that the testing we want to do is with NVMe on PCI-E. That's what I'm planning at this time. Yes I think that would cover the vast majority of situations, but that includes many desktops today too, not just laptops. I'm running a Samsung 970 EVO on my Ryzen 5 2600 system. Is that your only "disk" for boot and whatever else you do? I have only desktops none of the ones I support have such a slot on the mother board. No worries; There are PCI-E adapter boards that NVMe modules can be plugged into then the board plugs into a standard PCI-E four channel slot. This is the route I'm planning to go. That should work for secondary storage (and testing) but frequently the system can't boot from a NVMe add-in card because the BIOS doesn't support it. Well that's certainly another point to consider. Do you happen to know if UEFI supports it? I'll have to reboot my test machine later to see if there is anything that looks like it in the config. pages. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
[Test-Announce] Fedora 32 Branched 20200404.n.0 nightly compose nominated for testing
Announcing the creation of a new nightly release validation test event for Fedora 32 Branched 20200404.n.0. Please help run some tests for this nightly compose if you have time. For more information on nightly release validation testing, see: https://fedoraproject.org/wiki/QA:Release_validation_test_plan Notable package version changes: anaconda - 20200401.n.1: anaconda-32.24.3-1.fc32.src, 20200404.n.0: anaconda-32.24.4-1.fc32.src Test coverage information for the current release can be seen at: https://www.happyassassin.net/testcase_stats/32 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_32_Branched_20200404.n.0_Summary The individual test result pages are: https://fedoraproject.org/wiki/Test_Results:Fedora_32_Branched_20200404.n.0_Installation https://fedoraproject.org/wiki/Test_Results:Fedora_32_Branched_20200404.n.0_Base https://fedoraproject.org/wiki/Test_Results:Fedora_32_Branched_20200404.n.0_Server https://fedoraproject.org/wiki/Test_Results:Fedora_32_Branched_20200404.n.0_Cloud https://fedoraproject.org/wiki/Test_Results:Fedora_32_Branched_20200404.n.0_Desktop https://fedoraproject.org/wiki/Test_Results:Fedora_32_Branched_20200404.n.0_Security_Lab Thank you for testing! -- Mail generated by relvalconsumer: https://pagure.io/fedora-qa/relvalconsumer ___ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test-announce@lists.fedoraproject.org
Re: Testing with NVMe
pmkel...@frontier.com composed on 2020-04-04 10:13 (UTC-0400): > One thing that seems rather puzzling is that NVMe is offered in three > different connection configurations. PCI-E, USB (with a USB connector), > and SSD via SATA (with an SATA connector. Since multichannel PCI-E is > very much faster that either USB or SATA I don't really understand why > the USB and SATA options are offered. It seems a bit like having a car > that's designed and built for racing and only driving it on city streets. You're right. That's an apt description of having PCIeX4 capability and putting a SATA stick in it. I didn't find out the difference until after I had bought two SATA M.2 sticks for motherboards with PCIeX4 capability. What you get though is backwards compatibility and flexibility, since motherboard M.2 sockets are rather more limited in supply than SATA ports. M.2 vs NVME: What's the difference? https://www.youtube.com/watch?v=fJCHx7mZEKo 9 minutes https://www.ureach.eu/index.php/en/newsroom/item/291-cheetah-or-kitten https://i.ebayimg.com/images/g/XHAAAOSw2dBdkCHK/s-l1600.jpg -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Fedora-IoT-32-20200404.0 compose check report
No missing expected images. Failed openQA tests: 1/8 (x86_64) Old failures (same test failed in Fedora-IoT-32-20200402.0): ID: 566783 Test: x86_64 IoT-dvd_ostree-iso base_services_start URL: https://openqa.fedoraproject.org/tests/566783 Passed openQA tests: 7/8 (x86_64) Installed system changes in test x86_64 IoT-dvd_ostree-iso install_default_upload: System load changed from 0.02 to 0.26 Previous test data: https://openqa.fedoraproject.org/tests/564263#downloads Current test data: https://openqa.fedoraproject.org/tests/566778#downloads -- Mail generated by check-compose: https://pagure.io/fedora-qa/check-compose ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: Testing with NVMe
On Sat, Apr 4, 2020 at 9:14 AM pmkel...@frontier.com wrote: > > One thing that seems rather puzzling is that NVMe is offered in three > different connection configurations. PCI-E, USB (with a USB connector), > and SSD via SATA (with an SATA connector. Since multichannel PCI-E is > very much faster that either USB or SATA I don't really understand why > the USB and SATA options are offered. It seems a bit like having a car > that's designed and built for racing and only driving it on city streets. > Are you sure you're not conflating M.2 and NVMe? From what I can tell NVMe is only for storage whereas M.2 is primarily used for storage but there are other types of M.2 cards. M.2 SSD's can come in SATA and NVMe variants. As far as USB 3.0, it's pretty fast and someone may want compact a M.2 NVMe SSD in a USB 3.0 enclosure for convenience. From the various conversations with the test folks over time, it seems > many in the group test on laptops. Many of the newer lap tops have a > connector on the motherboard that connects an NVMe to PCI-E. This and > the above leads me to believe that the testing we want to do is with > NVMe on PCI-E. That's what I'm planning at this time. > Yes I think that would cover the vast majority of situations, but that includes many desktops today too, not just laptops. I'm running a Samsung 970 EVO on my Ryzen 5 2600 system. I have only desktops none of the ones I support have such a slot on the > mother board. No worries; There are PCI-E adapter boards that NVMe > modules can be plugged into then the board plugs into a standard PCI-E > four channel slot. This is the route I'm planning to go. > That should work for secondary storage (and testing) but frequently the system can't boot from a NVMe add-in card because the BIOS doesn't support it. The complication is that there are different kinds of NVMe modules and > the PCI-E boards have different configurations as well. At this point I > think I will get a board for "M.2" modules and a module to go with it. > There are still some points I want to investigate before I go ahead. I > want read some of the module data sheets in detail to see if there are > any GotYas that need to be considered. Also I want to see what the "raw" > formatting of the module looks like and if it changes from brand to > brand or with module capacity. My observation has been that > manufacturers always want a "competitive advantage" and sometimes those > "advantages" can turn into "let the buyer beware". > > In regard to actual procurement. Many of the modules require heat > sinking most of the adapter boards provide at least some minimal > provision for adding a heat sink. Others come complete with all required > hardware for heat sinking. This gets a bit tricky. The modules provide > the specifications necessary to calculate temperature rise from modules > heat dissipating surface. I still need to find an adapter card with the > corresponding specifications. so a complete thermal analysis can be done. > > A final point of interest is that there are some NVMe modules that are > being called SATA instead of just being called NVMe. My google-fu may be failing me here, however there appear to be adapters, but again I think you're conflating NVMe and M.2. Thanks, Richard ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Testing with NVMe
At last Monday's meeting there was mention of a need to start testing with NVMe. I volunteered to get some and help with that. Part of my motivation was the desire to become familiar with it and see if it's something I might have an application for. NVMe seems to have been created created mostly for servers and a few other applications that need extremely fast data access and flow from "disk". From what I've seen the newer 19" rack servers offer a NVMe slot on the board. One thing that seems rather puzzling is that NVMe is offered in three different connection configurations. PCI-E, USB (with a USB connector), and SSD via SATA (with an SATA connector. Since multichannel PCI-E is very much faster that either USB or SATA I don't really understand why the USB and SATA options are offered. It seems a bit like having a car that's designed and built for racing and only driving it on city streets. From the various conversations with the test folks over time, it seems many in the group test on laptops. Many of the newer lap tops have a connector on the motherboard that connects an NVMe to PCI-E. This and the above leads me to believe that the testing we want to do is with NVMe on PCI-E. That's what I'm planning at this time. I have only desktops none of the ones I support have such a slot on the mother board. No worries; There are PCI-E adapter boards that NVMe modules can be plugged into then the board plugs into a standard PCI-E four channel slot. This is the route I'm planning to go. The complication is that there are different kinds of NVMe modules and the PCI-E boards have different configurations as well. At this point I think I will get a board for "M.2" modules and a module to go with it. There are still some points I want to investigate before I go ahead. I want read some of the module data sheets in detail to see if there are any GotYas that need to be considered. Also I want to see what the "raw" formatting of the module looks like and if it changes from brand to brand or with module capacity. My observation has been that manufacturers always want a "competitive advantage" and sometimes those "advantages" can turn into "let the buyer beware". In regard to actual procurement. Many of the modules require heat sinking most of the adapter boards provide at least some minimal provision for adding a heat sink. Others come complete with all required hardware for heat sinking. This gets a bit tricky. The modules provide the specifications necessary to calculate temperature rise from modules heat dissipating surface. I still need to find an adapter card with the corresponding specifications. so a complete thermal analysis can be done. A final point of interest is that there are some NVMe modules that are being called SATA instead of just being called NVMe. I would be think that pretending to be an SATA-SSD drive would just a superficial matter the desktop would handle and the highs peed data access and flow would be handled in a very light weight protocol in the kernel. This is just a guess, but I would think that using the SATA protocol would slow things down. Since NVMes apparently exist for applications with a huge need to speed I guess I don't understand this. Any comments or suggestions are always welcome Stay Safe and Well! Pat (tablepc) ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Fedora-Cloud-31-20200404.0 compose check report
No missing expected images. Passed openQA tests: 1/1 (x86_64) -- Mail generated by check-compose: https://pagure.io/fedora-qa/check-compose ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
