I keep breaking Fedora 17 (help! boot issue)

[WIsheezy]

Okay so I'm fairly new to linux..I use RHEL at work but on a basic level but recently i've decided to dual boot Windows 7 and Fedora. Easy, no problem.

The real issue is I keep messing it up once i'm up and running every time! (last time I think I ruined all permissions and boot was hanging and just decided to restart)

This time i'd like to troubleshoot it a bit more and as I'm a noob in LInux i'd grealy appreciate your help. All i remember doing was running updates, changing the logon screen in beefy-miracle.xml and also trying to install javascript and flash. I remember installing OpenJKD? and also flash and running the commands to enable/install flash plugin for FIrefox.

Now when I boot normally I get this:




Log file attached to post.

I can boot into Grub and get into recovery mode then crtl+alt+f2(or f3?) and get into a terminal to login as me and then startx to get in. Thats how I can log in to the OS and that's how i'm posting this right now.


More info if needed:

1TB hdd partitioned with 70GB for Fedora 17 rest is for Windows 7
Installed via Live USB
also put the MBR back to windows instead of grub through a programme called EasyBCD incase any of this is relevant.

Thanks in advance

[sea]

Weird it works that way...
The logfile starts after 5 min runtime (300 = 5 * 60s), which doesnt list the actual issue.

Instead, try updating to a newer kernel.
If that doesnt work, i hope you have an older kernel available to choose in grub, try a such one.

[WIsheezy]

Thanks for the response mate. Sorry but how could I "update" to a newer kernel or go back to an older version? In Grub I have three options, two look like the same Fedora desktop and one is advanced options for linux which enables me to boot into recovery mode. And if so, does an older kernel or an updated one then become my main boot loader choice ?

About the log file, should I have got a different one elsewhere or was the log file irrelevant for this situation?

thanks

[sea]

This log file is irrelevant is its for the XWindow system.
The error is much earlier, so the output of dmesg|tail might help more, or a diffrent log file, but i couldnt name one

To update your kernel, simply verify you have an internet connection and the

sudo yum update kernel

EDIT:
Regarding another kernel at GRUB;
have a look at "Advanced Options".