I have two systems with the same ASUS motherboard, one running Bullseye, and other running Buster.
They both have a Marvell AQtion AQC113CS 10gb Ethernet controller and an Intel I225-V 2.5G Ethernet controller embedded on the motherboard.
In the system running Bullseye, the OS recognizes the controllers and they work.
In Buster they are not recognized.
Intel has no Linux drivers for the 2.5gb controller, and as far as I know, have no plans to ever have one.
I asked ASUS and just got babble on installing a Windows driver.
Have not heard from Marvell yet on the 10gb controller.
Is there anyway to find the drivers on Bullseye and put them on Buster ?
Or, does anybody know of drivers that will work on Buster ?
Appreciate any help...
Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
Ethernet drivers needed - working now, sort of, lots of errors
Ethernet drivers needed - working now, sort of, lots of errors
Last edited by 02ebz06 on 2021-10-05 18:51, edited 1 time in total.
Re: Ethernet drivers needed
The driver is probably in the Bullseye kernel. This is one of those instances where I'd trip over to https://liquorix.net/ and get their latest kernel. It's an easy test. If you decide to try the Bullseye kernel on Buster be sure to put a hold on the Buster kernel so that apt doesn't remove it.
Make sure you have any relevant firmware, both free and non-free.
Make sure you have any relevant firmware, both free and non-free.
Re: Ethernet drivers needed
Thanks for the suggestions.
Don't know if you saw my post about Sonos, but they use the SMB1 protocol.
Samba in Bullseye removed it, so that is why I went back to Buster on one server, then ran into the Ethernet problem.
I found another option I decided to try.
After a lot of Googling, I found people have used the Raspberry Pi for their music server for Sonos.
So I ordered the Raspberry Pi 4B.
From the Raspberry PI, I should be able to nfs mount the drive on the server with the music on it, and share it out with Samba for Sonos.
The Raspberry Pi will stay at Buster, but at least I will be able keep my servers up to date.
I will try the backports while I'm waiting for the Raspberry.
I have my last Buster and first Bullseye systems backed up, so I can easily reload either.
Thanks again for the suggestions...
Don't know if you saw my post about Sonos, but they use the SMB1 protocol.
Samba in Bullseye removed it, so that is why I went back to Buster on one server, then ran into the Ethernet problem.
I found another option I decided to try.
After a lot of Googling, I found people have used the Raspberry Pi for their music server for Sonos.
So I ordered the Raspberry Pi 4B.
From the Raspberry PI, I should be able to nfs mount the drive on the server with the music on it, and share it out with Samba for Sonos.
The Raspberry Pi will stay at Buster, but at least I will be able keep my servers up to date.
I will try the backports while I'm waiting for the Raspberry.
I have my last Buster and first Bullseye systems backed up, so I can easily reload either.
Thanks again for the suggestions...
Re: Ethernet drivers needed
OK, I loaded the backport kernel 5.10
The cards are recognized now, but have a new problem.
Many TX/RX errors on the Marvell 10gb interface.
Looks OK at startup, running at 10g. This is from syslog:
Oct 5 12:12:14 Z06-Backup kernel: [ 0.849982] atlantic 0000:38:00.0 enp56s0: renamed from eth0
Oct 5 12:12:14 Z06-Backup sensors[805]: enp56s0-pci-3800
Oct 5 12:12:15 Z06-Backup kernel: [ 9.444921] bond0: (slave enp56s0): Enslaving as a backup interface with a down link
Oct 5 12:12:23 Z06-Backup kernel: [ 17.636073] atlantic 0000:38:00.0 enp56s0: atlantic: link change old 0 new 10000
Oct 5 12:12:23 Z06-Backup kernel: [ 17.684207] bond0: (slave enp56s0): link status up, enabling it in 300 ms
Oct 5 12:12:23 Z06-Backup kernel: [ 17.684212] bond0: (slave enp56s0): invalid new link 3 on slave
Oct 5 12:12:23 Z06-Backup kernel: [ 17.996241] bond0: (slave enp56s0): link status definitely up, 10000 Mbps full duplex
Here are the errors:
enp56s0: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 1500
ether 04:42:1a:26:0a:e9 txqueuelen 1000 (Ethernet)
RX packets 170 bytes 19376 (18.9 KiB)
RX errors 8589934592 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 8589934592 dropped 0 overruns 0 carrier 0 collisions 0
The switch is a Netgear with two 10g ports and eight 1g ports.
Cable is cat-6a. Tried a different cat-6a, still errors.
FYI - the two interfaces are set up as bond0.
Any ideas ?
The cards are recognized now, but have a new problem.
Many TX/RX errors on the Marvell 10gb interface.
Looks OK at startup, running at 10g. This is from syslog:
Oct 5 12:12:14 Z06-Backup kernel: [ 0.849982] atlantic 0000:38:00.0 enp56s0: renamed from eth0
Oct 5 12:12:14 Z06-Backup sensors[805]: enp56s0-pci-3800
Oct 5 12:12:15 Z06-Backup kernel: [ 9.444921] bond0: (slave enp56s0): Enslaving as a backup interface with a down link
Oct 5 12:12:23 Z06-Backup kernel: [ 17.636073] atlantic 0000:38:00.0 enp56s0: atlantic: link change old 0 new 10000
Oct 5 12:12:23 Z06-Backup kernel: [ 17.684207] bond0: (slave enp56s0): link status up, enabling it in 300 ms
Oct 5 12:12:23 Z06-Backup kernel: [ 17.684212] bond0: (slave enp56s0): invalid new link 3 on slave
Oct 5 12:12:23 Z06-Backup kernel: [ 17.996241] bond0: (slave enp56s0): link status definitely up, 10000 Mbps full duplex
Here are the errors:
enp56s0: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 1500
ether 04:42:1a:26:0a:e9 txqueuelen 1000 (Ethernet)
RX packets 170 bytes 19376 (18.9 KiB)
RX errors 8589934592 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 8589934592 dropped 0 overruns 0 carrier 0 collisions 0
The switch is a Netgear with two 10g ports and eight 1g ports.
Cable is cat-6a. Tried a different cat-6a, still errors.
FYI - the two interfaces are set up as bond0.
Any ideas ?
Re: Ethernet drivers needed
Samba is still in Bullseye.
Code: Select all
cat /etc/debian_version
11.0
$ aptitude search samba
p argonaut-samba - Argonaut scripts to generate Samba share c
p fusiondirectory-plugin-samba - samba3 plugin for FusionDirectory
p fusiondirectory-plugin-samba-sc - LDAP schema for FusionDirectory samba plug
p gosa-plugin-samba - samba3 plugin for GOsa²
p python3-samba - Python 3 bindings for Samba
v python3.9-samba -
p samba - SMB/CIFS file, print, and login server for
v samba-client -
c samba-common - common files used by both the Samba server
p samba-common-bin - Samba common files used by both the server
p samba-dev - tools for extending Samba
p samba-dsdb-modules - Samba Directory Services Database
i A samba-libs - Samba core libraries
p samba-testsuite - test suite from Samba
p samba-vfs-modules - Samba Virtual FileSystem plugins
p sambamba - tools for working with SAM/BAM data
p vlc-plugin-samba - Samba plugin for VLC
Re: Ethernet drivers needed - working now, sort of, lots of errors
Ok, thanks for correction. Never needed samba.