2016-07-23 07:59:22 -0600 | commented question | Fedora24 Boot Problem[TripleBoot] It looks like GRUB can't find your initramfs files. Can you boot into rescue mode or use a rescue disk to get into Fedora and provide the output of: lsblk ls /boot I believe that package managers keep your most recent kernels so that you can boot using an older kernel in case something went wrong with a newer one. So when you updated your kernel you probably lost one of your older kernels from that list. My guess is that that older kernel is the one you've been booting into all this time and that you just need to update grub to use your current set of kernels. |
2016-03-13 07:03:32 -0600 | received badge | ● Famous Question (source) |
2016-03-13 07:03:32 -0600 | received badge | ● Notable Question (source) |
2015-11-11 16:23:24 -0600 | received badge | ● Popular Question (source) |
2015-06-16 01:10:04 -0600 | answered a question | Qt Creator + Nvidia = broken qDebug() This looks similar to my problem: https://ask.fedoraproject.org/en/ques... The problem was a bad (not broken) symlink for libGL.so.1. This happened after updating the nvidia drivers recently. Can you try removing libGL.so.1 and pointing it to nvidia/libGL.so.1 ? Make sure to take a backup first, or remember where libGL.so.1 was originally pointing. |
2015-06-16 01:10:03 -0600 | answered a question | dependency resolution It looks like mono has a guide already on setting up parallel mono environments. If you compile mono to a separate directory, you can use the binaries and libs there instead: http://www.mono-project.com/docs/comp... |
2015-06-16 01:10:02 -0600 | answered a question | Black screen after login So it turns out that the problem was a broken symlink when the nvidia drivers updated. I completely reinstalled the nvidia drivers ( http://www.if-not-true-then-false.com... ) and fixed the symlink by pointing it to the nvidia libGL instead: |
2015-06-15 12:13:52 -0600 | asked a question | Black screen after login Hey guys, I tried logging in this morning and was welcomed with a black screen (cursor still showed). I swapped over to another tty and noticed that kwin was stuck running at 100%, but when I tried to replace it it complained about a fatal error. Things were working fine last night, but here's some changes that happened recently:
So far I can login by booting into the old Fedora (3.19.5-200.fc21.x86_64) 21, and choosing KDE Plasma Failsafe login. I tried downgrading akmod-nvidia to 346.72-1, but the problem still persisted. Any ideas? Thank you |
2015-06-14 21:11:44 -0600 | commented answer | dependency resolution I'm not sure if I understand your suggestion. I tried deleting my current mono package (2.x) as well as banshee. This allowed me to update mono from the mono repository; however when I tried to reinstall banshee it complained about my mono version. It seems like I need both versions of mono in order to make this work. Is it possible to get something like this to work? |
2015-06-14 00:45:36 -0600 | commented question | yum dependencies To the moderator deleting my question: You are assuming that this is a duplicate of this https://ask.fedoraproject.org/en/ques... which actually is not a fix for my issue here. I think this may be unrelated, unless you've found a different duplicate? |
2015-06-13 21:44:03 -0600 | asked a question | dependency resolution Hey guys, I'm dealing with a dependency issue with yum. I have a project which requires me to update mono (>=3.2.8), but I think another application depends on an earlier version of mono: Following http://www.mono-project.com/docs/gett... I've created the repository file, /etc/yum.repos.d/download.mono-project.com_repo_centos_.repo And attempted to clean yum and update so that I could update mono. It looks like banshee requires a specific version of mono-addins which is blocking mono from updating? (more) |