Bug 130000 - Monitor goes to sleep when doing a text kickstart install
Summary: Monitor goes to sleep when doing a text kickstart install
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: anaconda   
(Show other bugs)
Version: 3.0
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Mike McLean
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-08-16 15:18 UTC by Chris Gifford
Modified: 2007-11-30 22:07 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-08-16 17:10:21 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Chris Gifford 2004-08-16 15:18:21 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)

Description of problem:
When doing a kickstart install (over NFS) of RH Ent WS 3.0 on an HP 
xw8000 with 2 videocards (both Nvidia Quadro 4, one AGP, one PCI), 
the monitor is put to sleep right after running /sbin/loader.  
Removing the PCI videocard seems to fix the problem.  Previous 
versions of Redhat (I know 8.0 for sure), did not have this problem 
with the exact same hardware.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Perform a kickstart install over nfs
    

Additional info:

Comment 1 Chris Gifford 2004-08-16 15:31:16 UTC
Upon futher troubleshooting, it appears that removeing the second 
videocard didn't fix it, the monitor eventually went to sleep during 
the install.  Trying to reinstall on the same machine, the monitor 
again goes to sleep as soon as /sbin/loader is started

Comment 2 Jeremy Katz 2004-08-16 15:33:08 UTC
Does booting with 'linux nofb' help?

Comment 3 Chris Gifford 2004-08-16 16:59:50 UTC
Yes, nofb solves the problem.  Thanks!


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