From: Todd Musall <tmusall@comcast.net>
To: linux-hotplug@vger.kernel.org
Subject: virtual console has black text
Date: Thu, 17 Jun 2004 22:16:43 +0000 [thread overview]
Message-ID: <1087510603.17479.26.camel@parents> (raw)
I've been using udev (as /dev mounted on tmpfs) and hotplug for quite
some time now without any problems, but something strange started
happening after upgrading to 2.6.7 kernel yesterday. At boot when
hotplug starts my vc is blanked or the text color is set to black. I
can still login, but can't see any text. Also doing a 'reset' or
'setterm -reset' doesn't correct the problem.
I did some testing and found that when /etc/hotplug/pci.rc calls udev
for my video card (Radeon 8500LE AGP) is when the screen goes black.
This didn't happen under 2.6.6 kernel, so I'm wondering if this is a
driver issue?
I'm not sure what cold plugging the video card actually does, but as a
quick fix I added a check in pci.rc so it skips that device and
everything seems to work fine.
Vital Info:
udev 027
hotplug 2004_04_01
kernel 2.6.7
Anyone have any ideas as to what might be causing this?
--
Todd Musall <tmusall@comcast.net>
-------------------------------------------------------
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next reply other threads:[~2004-06-17 22:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-17 22:16 Todd Musall [this message]
2004-06-17 23:12 ` virtual console has black text Greg KH
2004-06-18 0:51 ` Todd Musall
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1087510603.17479.26.camel@parents \
--to=tmusall@comcast.net \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).