F10 hard lock issue [SOLVED, KINDA]

[Richard Shaw]

On Sun, Nov 30, 2008 at 3:38 PM, gary artim <gartim at gmail.com> wrote:
> On Sat, Nov 29, 2008 at 2:31 PM, gary artim <gartim at gmail.com> wrote:
>> On Fri, Nov 28, 2008 at 7:57 PM, Richard Shaw <hobbes1069 at gmail.com> wrote:
>>> On Sat, Nov 29, 2008 at 12:03 PM, Bill Davidsen <davidsen at tmr.com> wrote:
>>>> Richard Shaw wrote:
>>>>>
>>>>> On Thu, Nov 27, 2008 at 10:48 PM, gary artim <gartim at gmail.com> wrote:
>>>>>>
>>>>>> On Thu, Nov 27, 2008 at 7:16 PM, Richard Shaw <hobbes1069 at gmail.com>
>>>>>> wrote:
>>>>>>>
>>>>>>> I just upgraded my wife's laptop to F10 from F9 using preupgrade.
>>>>>>> other than not having enough free space (had to make some) the install
>>>>>>> went perfectly. Now I'm having a lockup issue.
>>>>>>>
>>>>>>> When it first starts everything hard locks. Then I hear the DvD head
>>>>>>> moving, some time later I can turn the caps lock on and off but there
>>>>>>> is a significant delay. Also, the mouse cursor works but nothing else
>>>>>>> does. I can't do Ctl-Alt-Backspace or get to any of the virtual
>>>>>>> terminals. Scanning through /var/log/messages I don't see anything
>>>>>>> useful. Any ideas on where to start? This thing was rock solid under
>>>>>>> F9.
>>>>>>>
>>>>>>> Compaq laptop Turion 64 1.8GHz w/ Radeon 200M chipset. 1GB system ram.
>>>>>>> Broadcom wireless using native driver.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Richard
>>>>>>>
>>>>>>> --
>>>>>>> fedora-list mailing list
>>>>>>> fedora-list at redhat.com
>>>>>>> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
>>>>>>> Guidelines:
>>>>>>> http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
>>>>>>>
>>>>>> you could try adding to the grub boot screen a trailing 3 to boot without
>>>>>> a graphics interface...then login as root and type 'yum update'.
>>>>>> That's if you can
>>>>>> get this far... -- Gary
>>>>>
>>>>> Actually I did end up trying something like that, so it is now fully
>>>>> updated...
>>>>>
>>>>> Here's a few conditions I've discovered:
>>>>>
>>>>> When I log in it seems I have 10-25 minutes before it locks.
>>>>> If I don't log (leave at login screen) in it does not lock up, but it
>>>>> locks up almost immediately when I do log in.
>>>>> It's seems to only be a GUI lock. I can SSH into the machine, however
>>>>> top doesn't show any process using 100% cpu.
>>>>>
>>>>> Any and all ideas are appreceated. This is actually the wife's laptop
>>>>> which I recently converted to linux. She was a happy F9 user but when
>>>>> my preupgrade upgrade went so well on my laptop I decided to upgrade
>>>>> her's as well. Needless to say she's less than thrilled right now.
>>>>>
>>>> You must be a newlywed to mess with your wife's *anything* until/unless you
>>>> are asked to do so. My wife is still on FC7, and she is happy with it. She
>>>> is behind two levels of firewall, and her (seamonkey) browser is fully
>>>> updated, and mail goes through my corporate filters, not some ISP.
>>>>
>>>> You might diddle the graphics settings on the boot line, video= and/or
>>>> xdriver= may help. Post video hardware and dmesg details here, hopefully
>>>> someone can offer useful hints.
>>>>
>>>> Good luck!
>>>>
>>>> --
>>>> Bill Davidsen <davidsen at tmr.com>
>>>
>>> Well so far today it has been working. BTW, is there a command line
>>> way to get network manager to connect to wireless? I went to console
>>> on boot up and was trying to get a connection without logging in (so
>>> it wouldn't lock up) but couldn't find a way. I ending up logging in
>>> and immediately going to a virtual terminal.
>>>
>>> It's a Radeon 200M video chipset, Plymouth looks great BTW. I was
>>> thinking of disabling selinux since I was getting AVC errors in the
>>> system tray, something about updatedb trying to access .gconf2. I did
>>> the restorecon -v thing it suggested but don't know if it's related to
>>> the lockup issue.
>>>
>>> Actually it just locked up when I was typing this message. Gmail saved
>>> the draft and I'm finishing it from my laptop. Something interesting
>>> to note. I used to fix most issues like this by doing a gdm-restart.
>>> Now under F10 I'm getting "Operation not supported". I did a
>>> gdm-safe-restart and then the lapop locked up fully (I lost my ssh
>>> session and couldn't log back in.). The requested dmesg output to
>>> follow. I've got it saved to a text file but have to get it off her
>>> computer or post it before it locks up.
>>>
>>> Thanks,
>>> Richard
>>>
>>> --
>>> fedora-list mailing list
>>> fedora-list at redhat.com
>>> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
>>> Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
>>>
>>
>> I had problems with a fglrx (radeon) driver and have an open ticket
>> which never went far.  I went so far as to get a serial cable and
>> captured the logs from an alternate system - i forget the exact
>> message but it pointed to the driver. I then switch X drivers from
>> fglrx to radeon and no freezes. maybe boot to runlevel 3, switch
>> /etc/X11/xorg.conf from fglrx to radeon -- not sure it this is the
>> correct protocal for changing the X drive (please correct if wrong),
>> then start X (startx). Note that when I had this kind of problem I
>> could boot in runlevel 3 and startx with the original driver and it
>> wouldn't freeze -- strange. With the radeon driver it worked no
>> matter.  -- gary
>>
>
> Note: this was on fc9, _note_ fc10, forgot to mention -- gary

Just in case someone was following this thread and not the one where I
found the workaround. All I did was add the nomodeset kernel option
which apparently turns off KMS, so no flicker free boot, however,
adding vga=318 as well still gets me the graphical Plymouth start-up.

Richard