From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 207219] [BISECTED] Sony Vaio laptop built-in ricoh webcam no longer found on Fedora 31 with 5.4.11 kernel
Date: Sun, 26 Apr 2020 17:55:03 +0000 [thread overview]
Message-ID: <bug-207219-208809-eNBmfK92RB@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-207219-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=207219
--- Comment #11 from William Bader (williambader@hotmail.com) ---
I see the instructions for making a usbmon trace in an earlier comment.
How do I keep the ehci-pci driver from getting loaded, and how do I load it
manually?
Is this how to keep it from being loaded?
# echo blacklist ehci_hcd > /etc/modprobe.d/ehci_hcd.conf
# cp /boot/initrd.$(uname -r).img save
# mkinitrd -o /boot/initrd.$(uname -r).img $(uname -r)
# reboot
How do I load it? I was guessing modprobe, but "lsmod | grep hci" shows only
sdhci, cqhci, and sdhci_pci.
"Set up your system so that the ehci-pci driver doesn't get loaded
automatically, in either the running system or the initrd image. Then when the
system has started up, start up a usbmon trace from the 0u file (that is, all
buses) and load ehci-pci manually. That way we can see exactly what happens
when the webcam gets initialized for the first time."
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2020-04-26 17:55 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-12 23:35 [Bug 207219] New: [BISECTED] Sony Vaio laptop built-in ricoh webcam no longer found on Fedora 31 with 5.4.11 kernel bugzilla-daemon
2020-04-13 17:16 ` [Bug 207219] " bugzilla-daemon
2020-04-13 17:54 ` bugzilla-daemon
2020-04-13 17:54 ` bugzilla-daemon
2020-04-14 15:19 ` bugzilla-daemon
2020-04-14 21:59 ` bugzilla-daemon
2020-04-15 1:26 ` Alan Stern
2020-04-15 1:26 ` bugzilla-daemon
2020-04-16 23:22 ` bugzilla-daemon
2020-04-17 15:24 ` bugzilla-daemon
2020-04-25 21:51 ` bugzilla-daemon
2020-04-26 14:25 ` bugzilla-daemon
2020-04-26 17:55 ` bugzilla-daemon [this message]
2020-04-26 21:07 ` bugzilla-daemon
2020-04-27 17:26 ` bugzilla-daemon
2020-04-28 18:44 ` bugzilla-daemon
2020-04-28 22:17 ` bugzilla-daemon
2020-04-30 16:49 ` bugzilla-daemon
2020-04-30 23:26 ` bugzilla-daemon
2020-05-01 19:21 ` bugzilla-daemon
2020-05-01 21:55 ` bugzilla-daemon
2020-05-02 1:52 ` bugzilla-daemon
2020-05-02 2:57 ` bugzilla-daemon
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=bug-207219-208809-eNBmfK92RB@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-usb@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).