Bug 168054
Summary: | linux consoles flicker after udev starts (not X) | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | G.Wolfe Woodbury <redwolfe> |
Component: | kernel | Assignee: | Dave Jones <davej> |
Status: | CLOSED RAWHIDE | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | pfrields, wtogami |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-09-14 05:16:48 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
G.Wolfe Woodbury
2005-09-11 20:16:07 UTC
The problem is in hte tridentfb module. Adding tridentfb to /etc/hotplug/blacklist prevents the module from being loaded by rc.sysinit and the flicker/blinking goes away and everything is fine from then on. I note that rc.sysinit references /etc/hotplug/blacklist and there is also an /etc/modprobe.d/blacklist that purports to handle the same sort of errors. Which rules? Also, how would I go about adding module parameters for the tridentfb module in /etc/sysconfig/modules/* ? It may be that fiddling with the parameters can help the problem. Even so, the tridentfb driver is positively ancient (2002?) Thanks to whomever for the note on fedora-devel mailing list about the framebuffers module loading. It pointed the way. Note that with initscripts-8.14-1, it will no longer be loaded on boot (which is the correct behavior.) I'm going to close this as RAWHIDE, as I'm not going to actively debug this further (largely due to lack of hardware, but also due to being overwhelmed with more urgent bugs). If you feel inclined to help get the tridentfb driver in shape, please bring it up in the upstream bugzilla at http://bugme.osdl.org Thanks. |