Bug 110202 - system freeze on login when graphical boot mode is on
Summary: system freeze on login when graphical boot mode is on
Keywords:
Status: CLOSED DUPLICATE of bug 73733
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 1
Hardware: i386
OS: Linux
medium
high
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-11-17 00:03 UTC by lucas dixon
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-02-21 19:00:02 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description lucas dixon 2003-11-17 00:03:42 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.5) Gecko/20031016

Description of problem:
Using a Toshiba Satellite 2800 laptop, using vidia graphics drivers
with GForceGo 16MB card, after a graphical startup, a few seconds
after the login-screen has appeared the systems beeps once, and then
freezes. When it restarts it does so without graphical startup, it
gets to the login screen and beeps, but doesn't freeze. With graphical
startup off, it doesn't freeze.

Version-Release number of selected component (if applicable):
kernel-2.4.22-1.2115.nptl

How reproducible:
Always

Steps to Reproduce:
1. Startup with graphical boot enabled
2. wait until ogin screen appears, wait a few seconds
3. the system completely freezes.
    

Actual Results:  feeze

Expected Results:  be able to ssh in, or change tty, or login, or
restart from keyboard etc etc, ie be able to do something.

Additional info:

Toshiba laptop: Satellite 2800, with Nvidia GForce2 graphics card, and
orinoco  pcmcia (11MBS, Gold) card. Using the NVidia drivers. Not sure
if this happens without them.

Comment 1 lucas dixon 2003-11-17 00:04:10 UTC
oops, that should read a GForceGo graphics card.

Comment 2 Arjan van de Ven 2003-11-17 14:48:54 UTC

*** This bug has been marked as a duplicate of 73733 ***

Comment 3 Red Hat Bugzilla 2006-02-21 19:00:02 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.


Note You need to log in before you can comment on or make changes to this bug.