Greetings:
Could someone please verify, that if i updated once again up to rawhide, that it would be worth doing so?
For the last three days in a row, I have: 1) installed 17 final, 2) updated to current packages, 3) install fedora-release-rawhide, 4) updated to full rawhide, 5) reboot, 6) nothing, but let me expound of what I mean as to nothing...
I sit and wait and wait and wait some more, all that I ever get is a mouse pointer with a waiting symbol. I never get anywhere farther than the mouse cursor which does move all around the screen if I play with it....
I eventually after waiting for more than 5 minutes with the cursor, I reboot and re- install FC17 final!
I love to test and use rawhide, and I accept and understand how much it is crazy until it starts to settle down in the beta phase, but I would like a working system!
Could someone explain or show me what is goiing on?
Does anyone know of a workaround?
On 12/06/12 18:24, Rob Healey wrote:
Greetings:
Could someone please verify, that if i updated once again up to rawhide, that it would be worth doing so?
This is the most honest reply, I could think of. If you can manage what's on this link. Go for it, otherwise steer clear: https://fedoraproject.org/wiki/Rawhide
On 06/12/2012 08:24 PM, Rob Healey wrote:
I sit and wait and wait and wait some more, all that I ever get is a mouse pointer with a waiting symbol. I never get anywhere farther than the mouse cursor which does move all around the screen if I play with it....
Try booting into the single user mode. Might be able to find some useful information from /var/log and debug it further from there.
http://docs.fedoraproject.org/en-US/Fedora/17/html/Installation_Guide/ap-res...
Another easy thing to try is just select an older kernel from the GRUB boot menu. I doubt it helps in this case, but worth a try.
If none of the above helps, try creating a more detailed report -- where exactly does the booting stop? Do you see any error messages? Screenshot (use a camera); information from log files, and so on.
For what it's worth, I'm typing this on a rawhide installation running GNOME and it booted fine a few days ago, when I last tried. Granted, this is with a F17 kernel and initramfs, because I don't want to use the slow rawhide kernels that have debug options turned on.
On Tue, Jun 12, 2012 at 10:24:35 -0700, Rob Healey robhealey1@gmail.com wrote:
I sit and wait and wait and wait some more, all that I ever get is a mouse pointer with a waiting symbol. I never get anywhere farther than the mouse cursor which does move all around the screen if I play with it....
I eventually after waiting for more than 5 minutes with the cursor, I reboot and re- install FC17 final!
I have seen a problem with systemd-185-5. It seems to block mounting file systems late in the boot process. There is also a plymouth change that is required going from systemd-185-2 to systemd-185-5 and the real problem might lie there.When I manually recover from the mount issue, gdm doesn't seem to run (though maybe the display just isn't updated). Falling back to systemd-185-2 and the older plymouth got things working again. I haven't received any feedback on the bug report yet.