grub prompt after update

GoinEasy9 · #1 26th March 2011, 01:53 PM

After the update last night, rebooting left me with a grub prompt. Just checking to see if anyone else saw this. I should have updated in runlevel 3, since there's no reboot or shutdown in gnome, hindsight is great, isn't it?

Boricua · #2 26th March 2011, 03:09 PM

Quote:

Originally Posted by GoinEasy9

After the update last night, rebooting left me with a grub prompt. Just checking to see if anyone else saw this. I should have updated in runlevel 3, since there's no reboot or shutdown in gnome, hindsight is great, isn't it?

I applied some updates this morning but haven't reboot the machine, and I am frankly too scared to try, since this is the only machine I have available at the time

.

***DBelton*** · #3 26th March 2011, 04:06 PM

sure there is a reboot in gnome! that big button that's located on the front of the case!

I mentioned elsewhere that yesterday's updates fixed my reboot lockup problem, but it didn't

I'm still having it here. It did fix the super long boot time, though. It no longer sits for 3 minutes "rebuilding volatile file systems".

actually, there is a power off in gnome, but it still locks up my system. click on your user name in the upper right corner and then hit the a;t key. Suspend will change to Power Off.

GoinEasy9 · #4 26th March 2011, 04:17 PM

Yes, and when you change the suspend to power off ... clicking power off is what locks it up. I'm going to use a recue disk when I get home and see if I can use the previous kernel. BTW ... I'm very close to using the button on the front to shut down. Why does every update need a fix?

Boricua · #5 26th March 2011, 06:17 PM

Well, I'm alive. I was forced to shut down my Lenovo T60, after a severe freeze while switching from AC to battery power. Fortunately, this baby boot up as usual, although I lost, again, myself as a registered user, being forced to log in as "other". Apart from that, everything else seems to be fine

.

troyatlarge · #6 26th March 2011, 07:43 PM

I had the freeze from the power off button too, only days ago. From then on I've used the terminal command

sudo shutdown +0
or
sudo reboot

to shutdown or reboot, and it works fine. I suspect there are problems with that whole drop-down menu under your name as other things go wrong when using it as a path to get there - for example, changing you wallpaper - however, I'm certainly no expert - I just pretty much avoid using it for the time being and the system seems to work well for being in such an early stage.

ryptyde · #7 26th March 2011, 07:45 PM

Quote:

Originally Posted by GoinEasy9

After the update last night, rebooting left me with a grub prompt. Just checking to see if anyone else saw this. I should have updated in runlevel 3, since there's no reboot or shutdown in gnome, hindsight is great, isn't it?

I use the terminal to reboot or shutdown, have to be "su" to shutdown though but not to reboot. From the
terminal to shutdown I enter:

Code:

shutdown -h now

the recent updates here had NetworkManager have probs so I skipped it from the update and
the rest went well and G3 seems to be making progress.

phil

tuxor · #8 26th March 2011, 10:27 PM

Hm, the latest updates brought some real ameliorations to my system. I'm now able to reboot and shutdown from the gnome-menu (alt key).

Before the update, there was no "reboot"-option and even the shut down option just made my screen freeze:
https://bugzilla.redhat.com/show_bug.cgi?id=690781
(as you see in the bug report, the updates didn't solve this entirely)

Besides that, I can change wallpapers now flawlessly and don't have black background from time to time:
https://bugzilla.redhat.com/show_bug.cgi?id=690420 (fixed entirely)

I didn't have this grub-prompt-thing you are talking about. Everything seems fine.

Concerning this: "Why does every update need a fix?"
This is the "updates-testing"-Repo of an Alpha-Version. So what did you expect? To be honest, I'm not surprised...

troyatlarge · #9 26th March 2011, 11:38 PM

I can't seem to get updated at all now. It seems there are missing packages with the Network Manager - again the
--skip-broken does not work to get around it, nor does the automatic update manager seem to do the trick. Not sure what to do. Sounds good that once you do get the updates more stuff works - like to hear it.

ryptyde · #10 27th March 2011, 12:18 AM

Quote:

Originally Posted by troyatlarge

I can't seem to get updated at all now. It seems there are missing packages with the Network Manager - again the
--skip-broken does not work to get around it, nor does the automatic update manager seem to do the trick. Not sure what to do. Sounds good that once you do get the updates more stuff works - like to hear it.

I have installed yumex and run it and just select the packages that have no dependency issues. When you run
yumex and select all packages to update the ones with errors will be listed and then deselect the offenders.
Sometimes it is best to just update a few at a time so its easier to eliminate the ones with issues.

phil

Code:

yum install yumex

troyatlarge · #11 27th March 2011, 01:26 AM

I tried yumex - was a long time picking through the pile until I found what I could and could not download, but it did work. I too am having the drop down off the name working now inclusive of logout and such.

GoinEasy9 · #12 27th March 2011, 02:31 AM

I used a rescue disk and changed the default in grub to boot the last kernel, now it's working. I guess the freeze on shutdown and then powering off must have borked the new kernel setup. Since I'm the only one who saw this, I guess it was unique to my machine. As far as trying to update with all the dependency errors, I think I'll just wait till they're resolved, then, reinstall with KDE. I'll probably be less cranky if I stop looking at Gnome 3 for a while.

tuxor · #13 27th March 2011, 10:37 AM

When updating, you will have to exclude these packages:

Code:

NetworkManager.x86_64                       1:0.8.997-4.git20110325.fc15
NetworkManager-glib.x86_64                  1:0.8.997-4.git20110325.fc15
NetworkManager-gnome.x86_64                 1:0.8.997-4.git20110325.fc15
NetworkManager-openvpn.x86_64               1:0.8.995-1.fc15
NetworkManager-pptp.x86_64                  1:0.8.995-1.fc15
NetworkManager-vpnc.x86_64                  1:0.8.996-2.fc15
control-center.x86_64                       1:2.91.92-3.fc15
control-center-filesystem.x86_64            1:2.91.92-3.fc15
geoclue.x86_64                              0.12.0-7.fc15

(maybe some more, if you have more packages installed, that rely on NetworkManager or any of the packages listed here)

troyatlarge · #14 27th March 2011, 04:09 PM

Ahhh! wish I had saw that list yesterday. Yumex seems like it works well for this selection type. Today I included;

empathy
libsocialweb
libsocialweb-keys

To the list of packages that needed to be excluded.

Is there a way in here we can make a dynamic list of these packages that won't update? A list that updates daily or so.