From: Roger <rogerx.oss@gmail.com>
To: nouveau@lists.freedesktop.org
Subject: [Nouveau] i2c-dev driver corrupts display?
Date: Thu, 25 Feb 2021 17:40:22 -0500 [thread overview]
Message-ID: <YDgnVpKo8ya8WRAF@localhost4.local> (raw)
HARDWARE:
Dell Inspiron 8100 laptop
nVIDIA Geforce2 Go (NV11) with Intel AGP
PROBLEM:
Display corruption whenever nouveau module was loaded, seemingly at random.
CULPRIT:
Whenever the i2c-dev.ko driver/module was loaded, the display would become
corrupted, or as if the timing became out of sync with hardware specifications,
with weird moving pixels throughout the display.
If the i2c-dev is built into the kernel, possible the display would turn-off
upon nouveau module loading, but could be possibly worked around (I think) by
building the nouveau driver statically into the kernel, possibly loading prior
to i2c-dev loading?
Been having this problem for many years, finally found it, and nothing found
via Google on i2c-dev & nouveau.
WORKAROUND:
/etc/modprobe.d/blacklist.conf
blacklist i2c_dev
Or, rebuild the kernel without i2c-dev.
Quite a few Linux distributions either compile the i2c-dev into the kernel, or
load the module during booting, creating significant display problems (as noted
above) when trying to install from a Linux distribution CD/DVD. Most people
performing an install, I'm guessing, are then simply performing a nomodeset
during boot and/or reverting to VESA/UVESAFB.
--
Roger
http://rogerx.sdf.org/
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau
next reply other threads:[~2021-02-25 22:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-25 22:40 Roger [this message]
2021-02-25 23:58 ` [Nouveau] i2c-dev driver corrupts display? Ilia Mirkin
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=YDgnVpKo8ya8WRAF@localhost4.local \
--to=rogerx.oss@gmail.com \
--cc=nouveau@lists.freedesktop.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).