Re: dmesg reporting lots of errors apparently emanating from a Realtek RTL810xE PCI Express Fast Ethernet controller ...

2024-01-09 Thread Hans 
I discovred on some BIOSes undocumented features:

Some options can be enabled when set UEFI active, or also when setting a boot 
password and a 
BIOS password. 

Sometimes even new settings appear, when passwords are set. I know, this sounds 
weired, but 
as I said: this ware undocumented.

Also take a look at "modified bioses". There are many people, who are reverse 
engennering 
BIOSes, and add things or set things free.

There are some sites in the web, where you can get modded bioses. They are 
mostly tested and 
never had problems with those.

This is an example:

https://www.bios-mods.com/downloads/[1]

but I suggest to search for other sites, too.

Hope this helps.

Good luck,

Hans  


[1] https://www.bios-mods.com/downloads/

Re: dmesg reporting lots of errors apparently emanating from a Realtek RTL810xE PCI Express Fast Ethernet controller ...

2024-01-09 Thread Andrew M.A. Cater 
On Tue, Jan 09, 2024 at 04:50:28AM +, Albretch Mueller wrote:
> On 1/6/24, Albretch Mueller  wrote:
> >  I may not even have an NVMe card in my computer as the manufacturer
> > claims.
> 
>  My DELL Inspiron 5593 actually does have a M.2 512GB KIOXIA NVMe SSD,
> which I need to use! The problem, as I described here without getting
> a solution for it:
> 
> // __ I cannot change BIOS settings on my laptop?
> 
>  
> https://forums.tomshardware.com/threads/i-cannot-change-bios-settings-on-my-laptop.3833102/
> ~

Where did the laptop come from? Some (few) ex-business laptops are sold
with a BIOS password set by an original owner, say, where the vendor
has reconditioned them but can't unlock the BIOS.

That is unusual: if the worst comes to the worst, just reflash the BIOS.

>  is that I can't access/change the BIOS settings on my own laptop to
> make the hdd work in AHCI mode, I think. I have also read that Debian
> Linux has problems operating such cards:
> 

Which operating system(s) do you have on this? Do you have a Windows 10 that
was preinstalled by someone? Dells have an annoying habit of installing
with the BIOS setting as RAID by default. if Windows or another operating
system is there and already installed, it may be that you can't modify it
while there's an OS using it, if you see what I mean. 

The same goes for a vendor installing Windows as Legacy/MBR - if you then
want to change to UEFI, it's easier just to reinstall the whole thing.

> https://superuser.com/questions/1502756/debian-not-detecting-nvme-asus-zenbook-ux430ua
> 
> I purchased a Dell XPS 8930 with an NVMe dirve. Debian and Fedora did
> not recognize the NVMe. I had to use Ubuntu 18.04 for the drive to be
> recognized. I'm not sure what Ubuntu is doing that Debian is not, but
> I suspect it has something to do with updates. Debian tends to stick
> with old and broken software. They will not upgrade for users. – jww
> Nov 23, 2019 at 4:28
> ~

That's a very old quote now ...

>  You may know how to deal with such problems, better than I do, since
> I don't tend to mind the intricate technical details about computer
> hardware, even though I understand well the physics in them.
> 

Can you get into the BIOS to change anything e.g. time settings or
default NumLock to check?

>  Every piece of computer hardware my paranoia uses seems to have a
> mind of its own. I have decided to not use computers (do all the
> writing by hand on paper), but the data processing and algorithmic
> basis of my paper I have to do on a computer.
> 
>  Any suggestions?
> 
>  lbrtchx
>

All best, as ever,

Andy
(amaca...@debian.org)

Re: dmesg reporting lots of errors apparently emanating from a Realtek RTL810xE PCI Express Fast Ethernet controller ...

2024-01-08 Thread Albretch Mueller 
On 1/6/24, Albretch Mueller  wrote:
>  I may not even have an NVMe card in my computer as the manufacturer
> claims.

 My DELL Inspiron 5593 actually does have a M.2 512GB KIOXIA NVMe SSD,
which I need to use! The problem, as I described here without getting
a solution for it:

// __ I cannot change BIOS settings on my laptop?

 
https://forums.tomshardware.com/threads/i-cannot-change-bios-settings-on-my-laptop.3833102/
~
 is that I can't access/change the BIOS settings on my own laptop to
make the hdd work in AHCI mode, I think. I have also read that Debian
Linux has problems operating such cards:

https://superuser.com/questions/1502756/debian-not-detecting-nvme-asus-zenbook-ux430ua

I purchased a Dell XPS 8930 with an NVMe dirve. Debian and Fedora did
not recognize the NVMe. I had to use Ubuntu 18.04 for the drive to be
recognized. I'm not sure what Ubuntu is doing that Debian is not, but
I suspect it has something to do with updates. Debian tends to stick
with old and broken software. They will not upgrade for users. – jww
Nov 23, 2019 at 4:28
~
 You may know how to deal with such problems, better than I do, since
I don't tend to mind the intricate technical details about computer
hardware, even though I understand well the physics in them.

 Every piece of computer hardware my paranoia uses seems to have a
mind of its own. I have decided to not use computers (do all the
writing by hand on paper), but the data processing and algorithmic
basis of my paper I have to do on a computer.

 Any suggestions?

 lbrtchx

Re: dmesg reporting lots of errors apparently emanating from a Realtek RTL810xE PCI Express Fast Ethernet controller ...

2024-01-06 Thread Albretch Mueller 
 Sorry, but I don't think I am making much sense out those reported errors.
 I may not even have an NVMe card in my computer as the manufacturer claims.
 lbrtchx

Re: dmesg reporting lots of errors apparently emanating from a Realtek RTL810xE PCI Express Fast Ethernet controller ...

2024-01-06 Thread Albretch Mueller 
On 1/6/24, Jeffrey Walton  wrote:
> Before going down the rabbit hole, I would:
>
>   2. use a new [known good] ethernet cable

 I am not even using a cable!

>There is another discussion of PCI AER at
>.
>You might find something of interest in it.

 Thank you I spent some time going over their discussions which in two
cases were pretty similar to my problem and I decided to post my
problem:

 
https://forums.developer.nvidia.com/t/dmesg-reporting-lots-of-errors-apparently-relating-to-my-nvidia-card-and-realtek-rtl810xe-pci-express-fast-ethernet-controller/278001

 I will let you know how it went.

 lbrtchx

Re: dmesg reporting lots of errors apparently emanating from a Realtek RTL810xE PCI Express Fast Ethernet controller ...

2024-01-05 Thread Jeffrey Walton 
On Fri, Jan 5, 2024 at 9:18 AM Albretch Mueller  wrote:
>
>  I decided to upgrade to Bookworm because I needed to use some NVRAM
> memory supposedly available in my computer, but then my wireless
> Ethernet started to "complain". I initially thought those errors might
> be related to the lazy use of the Ethernet drivers from Bullseye but
> when I started to use Bookworm's drivers the errors became more
> complicated. Following some hints from:
>
>  
> https://askubuntu.com/questions/863150/pcie-bus-error-severity-corrected-type-physical-layer-id-00e5receiver-id
>
> [290569.588458] pcieport :00:1d.0: AER: Multiple Corrected error
> received: :01:00.0
> [290569.588488] r8169 :01:00.0: PCIe Bus Error:
> severity=Corrected, type=Physical Layer, (Receiver ID)
> [290569.588489] r8169 :01:00.0:   device [10ec:8136] error
> status/mask=0001/6000
> [290569.588491] r8169 :01:00.0:[ 0] RxErr  (First)
>
>  I found out it was the Realtek RTL810xE PCI Express Fast Ethernet controller:
>
> $ lspci -nn | grep PCIe
> 00:1d.1 PCI bridge [0604]: Intel Corporation Ice Lake-LP PCIe Port
> [8086:34b1] (rev 30)
>
> $ sudo hwinfo --pci
> ...
> 14: PCI 100.0: 0200 Ethernet controller
>   [Created at pci.386]
>   Unique ID: lkKU.j9EpqGNzpV9
>   Parent ID: 1GTX.j6F4IaHYGk7
>   SysFS ID: /devices/pci:00/:00:1d.0/:01:00.0
>   SysFS BusID: :01:00.0
>   Hardware Class: network
>   Model: "Realtek RTL810xE PCI Express Fast Ethernet controller"
>   Vendor: pci 0x10ec "Realtek Semiconductor Co., Ltd."
>   Device: pci 0x8136 "RTL810xE PCI Express Fast Ethernet controller"
>   SubVendor: pci 0x1028 "Dell"
>   SubDevice: pci 0x097c
>   Revision: 0x07
>   Driver: "r8169"
>   Driver Modules: "r8169"
>   Device File: enp1s0
>   I/O Ports: 0x3000-0x3fff (rw)
>   Memory Range: 0x9140-0x91400fff (rw,non-prefetchable)
>   Memory Range: 0x9120-0x91203fff (ro,non-prefetchable)
>   IRQ: 16 (2575859 events)
>   HW Address: c0:3e:ba:26:aa:93
>   Permanent HW Address: c0:3e:ba:26:aa:93
>   Link detected: no
>   Module Alias: "pci:v10ECd8136sv1028sd097Cbc02sc00i00"
>   Driver Info #0:
> Driver Status: r8169 is active
> Driver Activation Cmd: "modprobe r8169"
>   Config Status: cfg=new, avail=yes, need=no, active=unknown
> ...
> $
>
> $ sudo hwinfo --network
> 25: None 00.0: 10701 Ethernet
>   [Created at net.126]
>   Unique ID: VV91.ndpeucax6V1
>   Parent ID: qru8.BzdVZ3YOQjC
>   SysFS ID: /class/net/wlp2s0
>   SysFS Device Link: /devices/pci:00/:00:1d.1/:02:00.0
>   Hardware Class: network interface
>   Model: "Ethernet network interface"
>   Driver: "ath10k_pci"
>   Driver Modules: "ath10k_pci"
>   Device File: wlp2s0
>   HW Address: 5c:3a:45:0a:fb:c1
>   Permanent HW Address: 5c:3a:45:0a:fb:c1
>   Link detected: yes
>   Config Status: cfg=new, avail=yes, need=no, active=unknown
>   Attached to: #4 (Ethernet controller)
>
> 26: None 00.0: 10700 Loopback
>   [Created at net.126]
>   Unique ID: ZsBS.GQNx7L4uPNA
>   SysFS ID: /class/net/lo
>   Hardware Class: network interface
>   Model: "Loopback network interface"
>   Device File: lo
>   Link detected: yes
>   Config Status: cfg=new, avail=yes, need=no, active=unknown
>
> 27: None 00.0: 10701 Ethernet
>   [Created at net.126]
>   Unique ID: QObM.ndpeucax6V1
>   Parent ID: lkKU.j9EpqGNzpV9
>   SysFS ID: /class/net/enp1s0
>   SysFS Device Link: /devices/pci:00/:00:1d.0/:01:00.0
>   Hardware Class: network interface
>   Model: "Ethernet network interface"
>   Driver: "r8169"
>   Driver Modules: "r8169"
>   Device File: enp1s0
>   HW Address: c0:3e:ba:26:aa:93
>   Permanent HW Address: c0:3e:ba:26:aa:93
>   Link detected: no
>   Config Status: cfg=new, avail=yes, need=no, active=unknown
>   Attached to: #8 (Ethernet controller)
> $
>
>  After using Bookworm drivers I am still getting:
>
> [ 9514.141680] pcieport :00:1d.0: AER: Multiple Corrected error
> received: :01:00.0
> [ 9514.141723] r8169 :01:00.0: PCIe Bus Error: severity=Corrected,
> type=Physical Layer, (Receiver ID)
> [ 9514.141728] r8169 :01:00.0:   device [10ec:8136] error
> status/mask=0001/6000
> [ 9514.141734] r8169 :01:00.0:[ 0] RxErr  (First)
>
> Why would such errors start happening with I tried to use the NVRAM
> card? Why would that happen? How do you troubleshoot such errors in a
> more in depth way?

Before going down the rabbit hole, I would:

  1. update firmware for the computer and card
  2. use a new [known good] ethernet cable
  3. change ports at the switch

It is possible the messages are somewhat expected since they appear to
be part of PCI AER (Advanced Error Reporting). It is possible another
host is putting bad bits on the wire, and your machine is correcting
them. If another machine on your network is responsible, then you
might see different results if you plug your computer directly into
your router rather than a switch on your internal network.

There is an

Re: dmesg reporting lots of errors apparently emanating from a Realtek RTL810xE PCI Express Fast Ethernet controller ...

2024-01-05 Thread Albretch Mueller 
 I started my computer with the Bullseye Debian live DVD and the dmesg
log is not flooded with such error messages (as it does with
Bookworm):

[ 8095.737532] pcieport :00:1d.0: AER: Multiple Corrected error
received: :01:00.0
[ 8095.737572] r8169 :01:00.0: PCIe Bus Error: severity=Corrected,
type=Physical Layer, (Receiver ID)
[ 8095.737576] r8169 :01:00.0:   device [10ec:8136] error
status/mask=0001/6000
[ 8095.737579] r8169 :01:00.0:[ 0] RxErr  (First)

 This is what dmesg told me about the two networking interfaces
(before I exposed my computer):

$ sudo dmesg | grep "r8169\|ath10k_pci"
[1.162609] r8169 :01:00.0 eth0: RTL8106e, c0:3e:ba:26:aa:93,
XID 449, IRQ 124
[1.191058] r8169 :01:00.0 enp1s0: renamed from eth0
[   47.676697] ath10k_pci :02:00.0: enabling device ( -> 0002)
[   47.677983] ath10k_pci :02:00.0: pci irq msi oper_irq_mode 2
irq_mode 0 reset_mode 0
[   47.982673] ath10k_pci :02:00.0: firmware: failed to load
ath10k/pre-cal-pci-:02:00.0.bin (-2)
[   47.982709] ath10k_pci :02:00.0: firmware: failed to load
ath10k/cal-pci-:02:00.0.bin (-2)
[   47.982723] ath10k_pci :02:00.0: firmware: failed to load
ath10k/QCA9377/hw1.0/firmware-6.bin (-2)
[   47.982735] ath10k_pci :02:00.0: firmware: failed to load
ath10k/QCA9377/hw1.0/firmware-5.bin (-2)
[   47.982747] ath10k_pci :02:00.0: firmware: failed to load
ath10k/QCA9377/hw1.0/firmware-4.bin (-2)
[   47.982758] ath10k_pci :02:00.0: firmware: failed to load
ath10k/QCA9377/hw1.0/firmware-3.bin (-2)
[   47.982771] ath10k_pci :02:00.0: firmware: failed to load
ath10k/QCA9377/hw1.0/firmware-2.bin (-2)
[   47.982774] ath10k_pci :02:00.0: Failed to find firmware-N.bin
(N between 2 and 6) from ath10k/QCA9377/hw1.0: -2
[   47.982777] ath10k_pci :02:00.0: could not fetch firmware files (-2)
[   47.982779] ath10k_pci :02:00.0: could not probe fw (-2)
[   88.046124] r8169 :01:00.0: firmware: failed to load
rtl_nic/rtl8106e-1.fw (-2)
[   88.046204] r8169 :01:00.0: Direct firmware load for
rtl_nic/rtl8106e-1.fw failed with error -2
[   88.046223] r8169 :01:00.0: Unable to load firmware
rtl_nic/rtl8106e-1.fw (-2)
[   88.046679] RTL8208 Fast Ethernet r8169-0-100:00: attached PHY
driver [RTL8208 Fast Ethernet] (mii_bus:phy_addr=r8169-0-100:00,
irq=IGNORE)
[   88.213703] r8169 :01:00.0 enp1s0: Link is Down

 Then I install the ath10 drivers to be able to connect to the
Internet and dmesg is still fine, but I can't use the NVRAM.

$ sudo lspci -nn | grep PCIe
$
$ sudo lspci -nn | grep PCI
00:1d.0 PCI bridge [0604]: Intel Corporation Ice Lake-LP PCI Express
Root Port #9 [8086:34b0] (rev 30)
00:1d.1 PCI bridge [0604]: Intel Corporation Device [8086:34b1] (rev 30)
01:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd.
RTL810xE PCI Express Fast Ethernet controller [10ec:8136] (rev 07)
$

 In order to use the NVRAM you suggested to me to update to Bookworm,
but then there appears to be some conflict between the NVRAM which I
do see and the wired Realtek Ethernet controller, which I don't
understand because I am not using that:

01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL810xE
PCI Express Fast Ethernet controller (rev 07)

 firmware at all.

 Any elucidations on such firm-, hardware, OS conflicts?

 lbrtchx

dmesg reporting lots of errors apparently emanating from a Realtek RTL810xE PCI Express Fast Ethernet controller ...

2024-01-05 Thread Albretch Mueller 
 I decided to upgrade to Bookworm because I needed to use some NVRAM
memory supposedly available in my computer, but then my wireless
Ethernet started to "complain". I initially thought those errors might
be related to the lazy use of the Ethernet drivers from Bullseye but
when I started to use Bookworm's drivers the errors became more
complicated. Following some hints from:

 
https://askubuntu.com/questions/863150/pcie-bus-error-severity-corrected-type-physical-layer-id-00e5receiver-id

[290569.588458] pcieport :00:1d.0: AER: Multiple Corrected error
received: :01:00.0
[290569.588488] r8169 :01:00.0: PCIe Bus Error:
severity=Corrected, type=Physical Layer, (Receiver ID)
[290569.588489] r8169 :01:00.0:   device [10ec:8136] error
status/mask=0001/6000
[290569.588491] r8169 :01:00.0:[ 0] RxErr  (First)

 I found out it was the Realtek RTL810xE PCI Express Fast Ethernet controller:

$ lspci -nn | grep PCIe
00:1d.1 PCI bridge [0604]: Intel Corporation Ice Lake-LP PCIe Port
[8086:34b1] (rev 30)

$ sudo hwinfo --pci
...
14: PCI 100.0: 0200 Ethernet controller
  [Created at pci.386]
  Unique ID: lkKU.j9EpqGNzpV9
  Parent ID: 1GTX.j6F4IaHYGk7
  SysFS ID: /devices/pci:00/:00:1d.0/:01:00.0
  SysFS BusID: :01:00.0
  Hardware Class: network
  Model: "Realtek RTL810xE PCI Express Fast Ethernet controller"
  Vendor: pci 0x10ec "Realtek Semiconductor Co., Ltd."
  Device: pci 0x8136 "RTL810xE PCI Express Fast Ethernet controller"
  SubVendor: pci 0x1028 "Dell"
  SubDevice: pci 0x097c
  Revision: 0x07
  Driver: "r8169"
  Driver Modules: "r8169"
  Device File: enp1s0
  I/O Ports: 0x3000-0x3fff (rw)
  Memory Range: 0x9140-0x91400fff (rw,non-prefetchable)
  Memory Range: 0x9120-0x91203fff (ro,non-prefetchable)
  IRQ: 16 (2575859 events)
  HW Address: c0:3e:ba:26:aa:93
  Permanent HW Address: c0:3e:ba:26:aa:93
  Link detected: no
  Module Alias: "pci:v10ECd8136sv1028sd097Cbc02sc00i00"
  Driver Info #0:
Driver Status: r8169 is active
Driver Activation Cmd: "modprobe r8169"
  Config Status: cfg=new, avail=yes, need=no, active=unknown
...
$

$ sudo hwinfo --network
25: None 00.0: 10701 Ethernet
  [Created at net.126]
  Unique ID: VV91.ndpeucax6V1
  Parent ID: qru8.BzdVZ3YOQjC
  SysFS ID: /class/net/wlp2s0
  SysFS Device Link: /devices/pci:00/:00:1d.1/:02:00.0
  Hardware Class: network interface
  Model: "Ethernet network interface"
  Driver: "ath10k_pci"
  Driver Modules: "ath10k_pci"
  Device File: wlp2s0
  HW Address: 5c:3a:45:0a:fb:c1
  Permanent HW Address: 5c:3a:45:0a:fb:c1
  Link detected: yes
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #4 (Ethernet controller)

26: None 00.0: 10700 Loopback
  [Created at net.126]
  Unique ID: ZsBS.GQNx7L4uPNA
  SysFS ID: /class/net/lo
  Hardware Class: network interface
  Model: "Loopback network interface"
  Device File: lo
  Link detected: yes
  Config Status: cfg=new, avail=yes, need=no, active=unknown

27: None 00.0: 10701 Ethernet
  [Created at net.126]
  Unique ID: QObM.ndpeucax6V1
  Parent ID: lkKU.j9EpqGNzpV9
  SysFS ID: /class/net/enp1s0
  SysFS Device Link: /devices/pci:00/:00:1d.0/:01:00.0
  Hardware Class: network interface
  Model: "Ethernet network interface"
  Driver: "r8169"
  Driver Modules: "r8169"
  Device File: enp1s0
  HW Address: c0:3e:ba:26:aa:93
  Permanent HW Address: c0:3e:ba:26:aa:93
  Link detected: no
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #8 (Ethernet controller)
$



 After using Bookworm drivers I am still getting:

[ 9514.141680] pcieport :00:1d.0: AER: Multiple Corrected error
received: :01:00.0
[ 9514.141723] r8169 :01:00.0: PCIe Bus Error: severity=Corrected,
type=Physical Layer, (Receiver ID)
[ 9514.141728] r8169 :01:00.0:   device [10ec:8136] error
status/mask=0001/6000
[ 9514.141734] r8169 :01:00.0:[ 0] RxErr  (First)

Why would such errors start happening with I tried to use the NVRAM
card? Why would that happen? How do you troubleshoot such errors in a
more in depth way?

lbrtchx