Fedora not starting due to new kernel update...pls help pls help

[Nikhil Parmar]

hello friends, I am using Fedora 17
Today morning my laptop just updated to the latest kernel ie 3.5 where as my old kernel was 3.4 is still present . But the problem is now my fedora is not starting at all . It just boots with the Fedora F loading graphics and just sticks to that, but doesn't bring up the login.

As new entry in the BIOS is available for 3.5 and 3.4 ,I tried both but still no help.
Faced same problem on my desktop in F14 long back due to updation...Sometimes this make me feel UBUNTU in better than fedora.

Pls help i have few imp softwares installed and my exam is just in next week and i need my fedora system to work..

pls pls help
Thank U.

[blasedef]

Boot up, and switch to another terminal ( http://linux.about.com/od/linux101/l/blnewbie4_3_1.htm )

login

then paste what

dmesg | tail

returns

[Nikhil Parmar]

Sorry for the late rep, actually i was writing the output for "dmesg | tail"
output is :

[34.080940] ieee80211 phy0: brcms_ops_brs_info_changed: qos enabled : true(implement)
[34.080947] ieee80211 phy0: brcmsmac: brcms_ops_brs_info_changed:associated
[34.080951] changing basic rate failed:-22
[34.080954] arp filtering: brcms_ops_brs_info_changed: enabled true count 0 (implement)
[34.081198] ADDRCONF (NETDEV_CHANGE):wlan0 link become ready
[34.110844]: wlan0:moving STA 08:86:36:91:55:eb to state 3
[34.415753] arp filtering: brcms_ops_brs_info_changed: enabled true count 1 (implement)
[44.983704] wlan0:no IPv6 router present

[172.908009] ieee80211 phy0: brcms_c_dotxstatus: INTERMEDIATE but AMPDU
[233.077753] ieee80211 phy0: brcms_c_dotxstatus: INTERMEDIATE but AMPDU
[572.764459] ieee80211 phy0: brcms_c_dotxstatus: INTERMEDIATE but AMPDU

[blasedef]

What is your graphics card?

lspci | grep VGA

---------- Post added at 05:45 PM ---------- Previous post was at 05:44 PM ----------

I found this http://forums.fedora-fr.org/viewtopic.php?id=55538 and thought it might be a shot until someone who knows more comes along...

[JamesNZ]

Try logging in from the terminal again and run this as root:

systemctl mask ip6tables.service

That will disable the ipv6 service, but it won't affect any of your networking. Well, it didn't for me

EDIT: And if something breaks, then you can enable it again with 'systemctl unmask ip6tables.service'.