Open themightyoarfish opened 4 years ago
I'm seeing this as well. Exact same issue on Ubuntu 18.04.03 server. Looks like I'm using the same kernel as well.
This is most probably because .deb installation sequence does not take into account the module dependencies.
As a workaround please try doing modprobe ptp crc_itu_t
and then repeat installation.
But please be aware that such installation will not always override inbox driver. Inbox driver usage is a preferred way for majority of regular users.
By inbox driver you mean a driver bundled with Ubuntu? I don't seem to have one, at least the interface does not show up in ifconfig (lspci Shows the adapter).
On 6 January 2020 09:22:14 CET, Igor Russkikh notifications@github.com wrote:
This is most probably because .deb installation sequence does not take into account the module dependencies. As a workaround please try doing
modprobe ptp crc_itu_t
and then repeat installation.But please be aware that such installation will not always override inbox driver. Inbox driver usage is a preferred way for majority of regular users.
-- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: https://github.com/Aquantia/AQtion/issues/11#issuecomment-571048875
-- Sent from my Android device with K-9 Mail. Please excuse my brevity.
I just tried the modprobe command listed above. Unfortunately the same error still appears after bulding the module from source.
I'm getting this error when trying to install the driver on Debian (specifically the latest version of Open Media Vault). Already tried the previous suggestion of modprobe
. Uses the 5.5.0 headers.
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'atlantic' instead of './atlantic_1592352125.deb'
atlantic is already the newest version (1592352125).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] Y
Setting up atlantic (1592352125) ...
make -j4 -C /lib/modules/5.5.0-0.bpo.2-amd64/build M=/var/build_aq_drv/1592352125/Linux modules
make[1]: Entering directory '/usr/src/linux-headers-5.5.0-0.bpo.2-amd64'
Building modules, stage 2.
MODPOST 1 modules
make[1]: Leaving directory '/usr/src/linux-headers-5.5.0-0.bpo.2-amd64'
insmod: ERROR: could not insert module atlantic.ko: Unknown symbol in module
dpkg: error processing package atlantic (--configure):
installed atlantic package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
atlantic
E: Sub-process /usr/bin/dpkg returned an error code (1)
Can you paste here your dmesg log? it should have error message in it.
When I turned off secure boot in BIOS, I was able to do
sudo apt-get install ./atlantic_1578154949.deb
Isn't secure boot for windows?