Bug 1555042

Summary: Regenerate install to 64 or do not connect by preventing installation
Product: [Fedora] Fedora Reporter: xzj8b3 <xzj8b3>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 27CC: airlied, bskeggs, ewk, hdegoede, ichavero, itamar, jarodwilson, jglisse, john.j5live, jonathan, josef, kernel-maint, linville, mchehab, mjg59, steved
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-04-06 18:59:42 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Regenerate install to 64 or do not connect by preventing installation none

Description xzj8b3 2018-03-13 20:40:53 UTC 
Created attachment 1407719 [details]
Regenerate install to 64 or do not connect by preventing installation

With last reported bugs I had several problems connecting giving up Fedora 27....

I would like to reinstall it just mounted a new SSD, but you should regenerate install to new kernels or not connect!!!!
Comment 1 Josh Boyer 2018-03-13 20:49:05 UTC 
Please state your problem more clearly.  It is impossible to determine what the issue you are having is.
Comment 2 xzj8b3 2018-03-15 18:04:05 UTC 
It does not connect with older kernels with that network card.... it does not install and has happened to many other!!!!

If you upgrade to install in a few weeks I can try again as I replace SSD
Comment 3 xzj8b3 2018-04-04 18:30:47 UTC 
Problems always due to the bug in the link below reported more correctly!!!!



https://bugzilla.redhat.com/show_bug.cgi?id=1560763
Comment 4 Adam Jackson 2018-04-06 18:59:42 UTC 

*** This bug has been marked as a duplicate of bug 1560763 ***