netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hayes Wang <hayeswang@realtek.com>
To: Ferenc Fejes <fejes@inf.elte.hu>, Jakub Kicinski <kuba@kernel.org>
Cc: netdev <netdev@vger.kernel.org>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: RE: r8152: error when loading the module
Date: Fri, 20 Oct 2023 07:40:32 +0000	[thread overview]
Message-ID: <d9c75e609001461d8eb0e38c18771cb2@realtek.com> (raw)
In-Reply-To: <47d463bce1ef62ecb34b666f21d7dd0d7439ac23.camel@inf.elte.hu>

Ferenc Fejes <fejes@inf.elte.hu>
> Sent: Friday, October 20, 2023 2:34 PM
[...]
> > However, I check the firmware and find some wrong content.
> > Could you remove /lib/firmware/rtl_nic/rtl8156b-2.fw and unplug the device.
> > Then, plug the device and check it again.
> 
> Yes, I'll do that, but strangely enough the error has disappeared since
> then. I played with the setup yesterday a little more. The NIC is
> actually built into my monitor, which is always powered on - so
> regardless if my laptop connected or not, the NIC is probably on. I
> rebooted to Windows, and then rebooted to Linux, and magically the bug
> just disappeared.
> 
> Is this possible/makes sense to you?

I guess it is relative to the firmware.
Maybe the windows load the correct firmware, and fix it.

Best Regards,
Hayes



      reply	other threads:[~2023-10-20  7:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-19 11:48 r8152: error when loading the module Ferenc Fejes
2023-10-20  0:45 ` Jakub Kicinski
2023-10-20  5:59   ` Hayes Wang
2023-10-20  6:33     ` Ferenc Fejes
2023-10-20  7:40       ` Hayes Wang [this message]

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=d9c75e609001461d8eb0e38c18771cb2@realtek.com \
    --to=hayeswang@realtek.com \
    --cc=fejes@inf.elte.hu \
    --cc=kuba@kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=netdev@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).