Freezing at login

[Uno Engborg]

Antonio M wrote:
> 2010/1/19 iarly selbir | ski0s <iarlyy at gmail.com>:
>   
>> I have same problem here, my video card driver is Intel too, after complete
>> service starting, it freezes after Fedora logo blink, any command doesn't
>> works ( ctr+alt+f1, del, etc )
>> I guess may be the plymouth getting problems to start login screen ( in my
>> case KDE )
>>
>> Regards,
>>
>> - -
>> iarly selbir | ski0s
>>
>> :wq!
>>
>>
>> On Tue, Jan 19, 2010 at 12:05 AM, Uno Engborg <uno at webworks.se> wrote:
>>     
>>> antonio montagnani skrev 2010-01-19 00:51:
>>>       
>>>> I upgraded a f12 to rawhide, but when I rebooted my system freezes
>>>> before having the login screen with an arrow that I can move, but that's
>>>> all.
>>>>
>>>> I started also in text mode but when I issue startx, system freezes
>>>> again.
>>>> The same with nomodeset in boot option.
>>>>
>>>> How do I recover???
>>>>
>>>>
>>>>         
>>> You don't happen to use the intel Xorg driver? That driver will fail
>>> fail in the way you describe if you try to turn off kernel modesetting.
>>>
>>> In Fedora 11 I had to have  kernel modesetting disabled to get
>>> hibernate/suspend/resume to work properly, and when I upgraded I got
>>> this failure. Unfortunately the hibernate functionality still fails on
>>> my Thinkpad 50e with modset on.
>>>
>>> Regards
>>> /uno
>>> --
>>> test mailing list
>>> test at lists.fedoraproject.org
>>> To unsubscribe:
>>> https://admin.fedoraproject.org/mailman/listinfo/test
>>>       
>> --
>> test mailing list
>> test at lists.fedoraproject.org
>> To unsubscribe:
>> https://admin.fedoraproject.org/mailman/listinfo/test
>>
>>     
>
> try to start with nomodeset in text mode and then startx...see my previous post
>
>   
Actually, it is when I specify nomodeset that EVERYTHING hangs, if I 
just go with the default modeset and plymuth it is  JUST 
hibernate/suspend resume that doesn't work.  At least on early versions 
of Xorg/intel on Fedora 11 everything worked if I used nomodeset at the 
boot prompt. In other words the nomodeset workaround is not working 
anymore presumably due to some bug in the intel driver

/uno

/uno