Re: FedUp makes F17 no longer boot after botched "upgrade" to F19

2013-11-03 Thread John Pilkington
On 03/11/13 05:50, Fernando Cassia wrote: On Sun, Nov 3, 2013 at 2:38 AM, Joe Zeff mailto:j...@zeff.us>> wrote: You may have run afoul of this: https://bugzilla.redhat.com/__show_bug.cgi?id=980543 Yes, it refers to 18-19, but

Re: FedUp makes F17 no longer boot after botched "upgrade" to F19

2013-11-03 Thread Roger
NO MATTER what I select, it hangs. Ive tried all kernels. It hangs right after the [f] logo has its glow, and just stays there. Have you tried booting to level 3? Fedora 19's been doing this intermittently on my machines for months. More so on the little Dell1520 laptop. There are no error mes

Re: FedUp makes F17 no longer boot after botched "upgrade" to F19

2013-11-03 Thread Temlakos
On 11/03/2013 01:43 AM, Roger wrote: On 11/03/2013 04:18 PM, Ed Greshko wrote: On 11/03/13 12:19, Fernando Cassia wrote: NO MATTER what I select, it hangs. Ive tried all kernels. It hangs right after the [f] logo has its glow, and just stays there. Have you tried booting to level 3? Fedora 19

Re: FedUp makes F17 no longer boot after botched "upgrade" to F19

2013-11-02 Thread Roger
On 11/03/2013 04:18 PM, Ed Greshko wrote: On 11/03/13 12:19, Fernando Cassia wrote: NO MATTER what I select, it hangs. Ive tried all kernels. It hangs right after the [f] logo has its glow, and just stays there. Have you tried booting to level 3? Fedora 19's been doing this intermittently on

Re: FedUp makes F17 no longer boot after botched "upgrade" to F19

2013-11-02 Thread Fernando Cassia
On Sun, Nov 3, 2013 at 2:38 AM, Joe Zeff wrote: > You may have run afoul of this: https://bugzilla.redhat.com/ > show_bug.cgi?id=980543 Yes, it refers to 18-19, but it hit me on an > upgrade from 17-19. Also, the maintainers are claiming that it's caused by > a process that's just taking longer

Re: FedUp makes F17 no longer boot after botched "upgrade" to F19

2013-11-02 Thread Joe Zeff
On 11/02/2013 10:22 PM, Fernando Cassia wrote: No, I wanted to know first if this was a known scenario, before I went to the command line and started messing up things further ;). You may have run afoul of this: https://bugzilla.redhat.com/show_bug.cgi?id=980543 Yes, it refers to 18-19, but

Re: FedUp makes F17 no longer boot after botched "upgrade" to F19

2013-11-02 Thread Fernando Cassia
On Sun, Nov 3, 2013 at 2:18 AM, Ed Greshko wrote: > Have you tried booting to level 3? OK, here's what I see after booting in runlevel 3 with quiet and rgbh removed: systemd[1]: dbus.service start request repeated too quickly, refusing to start systemd[1]: Unit dbus.socket entered a failed stat

Re: FedUp makes F17 no longer boot after botched "upgrade" to F19

2013-11-02 Thread Fernando Cassia
On Sun, Nov 3, 2013 at 2:18 AM, Ed Greshko wrote: > Have you tried booting to level 3? No, I wanted to know first if this was a known scenario, before I went to the command line and started messing up things further ;). But yes, that sounds like the right step FC -- During times of Univers

Re: FedUp makes F17 no longer boot after botched "upgrade" to F19

2013-11-02 Thread Ed Greshko
On 11/03/13 12:19, Fernando Cassia wrote: > NO MATTER what I select, it hangs. Ive tried all kernels. It hangs right > after the [f] logo has its glow, and just stays there. Have you tried booting to level 3? -- Getting tired of non-Fedora discussions and self-serving posts -- users mailing li

FedUp makes F17 no longer boot after botched "upgrade" to F19

2013-11-02 Thread Fernando Cassia
System: AMD Opteron 2216 server, 2GB RAM 250GB SATA-300 HDD ATI X1600 PCI-X video card Running Fedora 17 on an encrypted volume The system was decomissioned pending hardware repairs for quite a while (since July-2012). Once I finally gotba spare new hdd and monitor, it was brought back to life and