On 10/03/2014 12:45 AM, Ed Greshko wrote:
On 10/03/14 10:18, jd1008 wrote:
On 10/02/2014 07:16 PM, Ed Greshko wrote:
At this point, if I were you, I'd create a bootable LIVE USB or a LIVE CD from the F20 release and boot it and see if it works.
Definitely worth a try.
Yes, and then you can compare the logs....
If you did keep the "rescue" grub entry you could boot into that and try your "experiments" with loading modules. You'll probably have to extract and replace the /usr/lib/modules/whatever-kernel directory from the initramfs as that was probably removed (or cleaned out) when the kernel related to the "rescue" boot was removed.
Of course, this would assume that when the system was first installed you hadn't installed the rpmfusion packages until at least the next kernel update. Otherwise, the initramfs would contain rpmfusion bits.
It turns out that when I had installed the rpmfusion nvidia packages,
the initramfs
of 3.14.0-200 was saved as
/boot/initramfs-3.14.9-200.fc20.x86_64-nouveau.img
So, I committed a desperate act of
mv initramfs-3.16.3-200.fc20.x86_64.img
initramfs-3.16.3-200.fc20.x86_64.img.not
cp -f initramfs-3.14.9-200.fc20.x86_64-nouveau.img
initramfs-3.16.3-200.fc20.x86_64.img
and rebooted.
And my resolution is now correct.
Question:
Will this "working" initramfs prevail when a new kernel is installed via
updates?
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
