Hide Forgot
Description of problem: I have tried to install Fedora 24 on my laptop but it stopped loading the live booting proccess after line "User ID 1000". So, I have downloaded Fedora 25 Alpha release which booted OK as live system. I have started the installation proccess but it freezed when creating "filesystem ext4" in Anaconda installer. The parameters I've used where "Custom partitioning" - "Create partitions automatically" using LVM. So, I booted again in Troubleshooting mode (screen resolution was by default 400x300 instead of 1920x1080), in this mode I was able to install Fedora 25 on my system, but I remained blocked on 400x300 resolution. If I want to change the resolution I get "Unknown monitor". The images I used were of Fedora 24 and 25 Workstation Live 64bit - GNOME Desktop, both on a USB device created with Fedora Disk Writer (bootable image). I tried to install Fedora 25 Beta, same issues as before. However, in Fedora 25 Beta Release I got some alerts that the kernel has been tainted (flags:GL) and they cannot be reported. And also an alert from xorg about crashing and restarting (only when I tried installing with 1920x1080 resolution). Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Installation of Fedora 25 Beta on a ASUS GL752VW computer 2. 3. Actual results: It installed on 400x300 resolution Expected results: Normal workstation environment 1920x1080 resolution Additional info: System hardware: ASUS GL752VW laptop with GTX 960M - 4096MB GPU and Intel HD Graphics 530, 16 GB RAM, Intel i7-6700HQ CPU, 1SDD - 128GB, 1 HDD - 1TB. I have installed the system on HDD not on the SSD.
Solved with Fedora 25 by removing the "rhgb" option from the boot menu
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 25 kernel bugs. Fedora 25 has now been rebased to 4.9.3-200.fc25. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 26, and are still experiencing this issue, please change the version to Fedora 26. If you experience different issues, please open a new bug report for those.