linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 208911] Renesas USB controller - FW has invalid version :8224
Date: Fri, 21 Aug 2020 22:05:17 +0000	[thread overview]
Message-ID: <bug-208911-208809-tkPIkbJCDS@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-208911-208809@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=208911

neoweb@hackspherelabs.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |neoweb@hackspherelabs.com

--- Comment #14 from neoweb@hackspherelabs.com ---
Hello,

I am not trying to waste anyone's time here.  This is what I had:

[    1.578294] xhci_hcd 0000:0a:00.0: FW has invalid version :8215
[    1.578331] xhci_hcd 0000:0a:00.0: Direct firmware load for
renesas_usb_fw.mem failed with error -2
[    1.578334] xhci_hcd 0000:0a:00.0: request_firmware failed: -2
[    1.578339] xhci_hcd: probe of 0000:0a:00.0 failed with error -2

I can find a ton of detail about this, I never knew that cards like this needed
firmware to be loaded on every boot.  I know FreeBSD will load firmware into
LSI Raid cards IIRC.  So it looks like from the comment of the final patch: 
"Test if ROM is present and loaded, if so we can skip everything" that my card
is going to use the firmware that is in the EEPROM.

I never knew you could load firmware into a USB 3.0 card like this.  It looks
like someone has even created a userspace util + SystemD setup for this:  

*https://mjott.de/blog/881-renesas-usb-3-0-controllers-vs-linux/
*https://github.com/markusj/upd72020x-load
*https://lore.kernel.org/patchwork/patch/686290/

So to get to my point.  I have noticed I have some issues sometimes with my
Renesas USB card manufactured by StarTech.  Just standard USB stuff, and issues
with pluggable USB 3.0 hubs...sometimes I have to reboot to get everything
working again, or reset the hub.

Am I doing myself a disservice not upgrading the firmware on it using the
Windows utils from Startech...or should I systemd with the github stuff above,
and upgrade the firmware every boot?

I don't know much about this stuff, but should linux always push a new firmware
to the card like CPU microcode, or FreeBSD.

Like I said, sorry if this is a waste of time or I am posting in the wrong
place, but it would be doing linux a disservice if all the Windows drivers
pushed newer better firmware to these devices, and worked better, because
firmware loading was just skipped.

Anyone have any idea?

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2020-08-21 22:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-208911-208809@https.bugzilla.kernel.org/>
2020-08-15 17:06 ` [Bug 208911] Renesas USB controller - FW has invalid version :8224 bugzilla-daemon
2020-08-16  5:49 ` bugzilla-daemon
2020-08-17 10:55 ` bugzilla-daemon
2020-08-18  6:41 ` bugzilla-daemon
2020-08-20  7:14 ` bugzilla-daemon
2020-08-21  5:34 ` bugzilla-daemon
2020-08-21 22:05 ` bugzilla-daemon [this message]
2020-08-31  8:19 ` bugzilla-daemon
2020-09-16 21:13 ` bugzilla-daemon
2020-09-20 21:38 ` bugzilla-daemon
2020-09-21  5:05   ` Greg KH
2020-09-21  5:05 ` bugzilla-daemon
2020-09-21  7:26 ` bugzilla-daemon
2020-09-22  4:05 ` bugzilla-daemon
2020-10-05 16:42 ` 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-208911-208809-tkPIkbJCDS@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).