Bug 127043 - rhgb doesn't show output with kernel 2.6.6.-1.435
Summary: rhgb doesn't show output with kernel 2.6.6.-1.435
Alias: None
Product: Fedora
Classification: Fedora
Component: rhgb (Show other bugs)
(Show other bugs)
Version: 2
Hardware: i686 Linux
Target Milestone: ---
Assignee: Daniel Veillard
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2004-06-30 22:36 UTC by Armijn Hemel
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-06-30 22:58:49 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Armijn Hemel 2004-06-30 22:36:48 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040510

Description of problem:
If I boot my machine with kernel 2.6.6-1.435 rhgb doesn't show
anything at all and the monitor doesn't get any signal at all. The
signal comes back when starting gdm. I don't have this problem with
the SMP version and 2.6.5-1.358 SMP.

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

How reproducible:

Steps to Reproduce:
1. boot kernel 2.6.6-1.435

Actual Results:  Screen went blank when rhgb was started

Expected Results:  I expected to see graphical goodness!

Additional info:

The machine is a Medion Titanium MD 8080, the monitor is a Iiyama
Vision Master 403. Switching between virtual terminals (i.e. pressing
ctrl-alt-f1, etc.) does give a signal back on the monitor, pressing
ctrl-alt-f8 makes it the signal go away gain. Nothing interesting is
showing up in /var/log/messages and I have no clue what to do or how
to fix it.

Comment 1 Armijn Hemel 2004-06-30 22:58:49 UTC
ARGH. The problem turned out to be that for some unknown reason
/dev/pts/1 wasn't created during startup and the X server didn't like
it. I tried it some more, it does work. Sorry for wasting your time :(

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