Support for X553 Intel NIC in Xenial
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| linux (Ubuntu) |
Medium
|
Unassigned | ||
| Xenial |
Medium
|
Unassigned | ||
| Zesty |
Medium
|
Unassigned |
Bug Description
Hey!
The Intel Atom C3000 platform comes with an integrated X553 Intel NIC. Support was added in Linux 4.11: https:/
Would it be possible to backport such support into 4.4? Redhat provided support for such chips a few months back (through DKMS): https:/
Thanks.
Changed in linux (Ubuntu): | |
status: | New → Incomplete |
tags: | added: xenial |
Changed in linux (Ubuntu): | |
importance: | Undecided → Medium |
Changed in linux (Ubuntu Xenial): | |
status: | New → Triaged |
Changed in linux (Ubuntu Zesty): | |
status: | New → Triaged |
Changed in linux (Ubuntu): | |
status: | Incomplete → Triaged |
Changed in linux (Ubuntu Xenial): | |
importance: | Undecided → Medium |
Changed in linux (Ubuntu Zesty): | |
importance: | Undecided → Medium |
tags: | added: kernel-da-key zesty |
Leroy Tennison (ltennison) wrote : | #2 |
I am also needing the updated driver for a firewall appliance.
Changed in linux (Ubuntu): | |
status: | Triaged → Confirmed |
Leroy Tennison (ltennison) wrote : | #3 |
I logged in using the elinks browser (since the system has no GUI), allowed the application to have access via my account and nothing apparent happened. I did change the status to confirmed as requested above. If I need to do something after allowing the application to have access then please provide the steps i need to take, thanks.
AlsaDevices:
total 0
crw-rw----+ 1 root audio 116, 1 Jan 8 13:21 seq
crw-rw----+ 1 root audio 116, 33 Jan 8 13:21 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=
InstallationDate: Installed on 2019-01-08 (0 days ago)
InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
IwConfig: Error: [Errno 2] No such file or directory
MachineType: Supermicro Super Server
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 astdrmfb
ProcKernelCmdLine: BOOT_IMAGE=
ProcVersionSign
RelatedPackageV
linux-
linux-
linux-firmware 1.157.11
RfKill: Error: [Errno 2] No such file or directory
Tags: xenial xenial xenial
Uname: Linux 4.4.0-87-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: True
dmi.bios.date: 08/28/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.1
dmi.board.
dmi.board.name: A2SDi-2C-HLN4F
dmi.board.vendor: Supermicro
dmi.board.version: 1.00
dmi.chassis.
dmi.chassis.type: 17
dmi.chassis.vendor: Supermicro
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: Super Server
dmi.product.
dmi.sys.vendor: Supermicro
tags: | added: apport-collected |
Leroy Tennison (ltennison) wrote : CRDA.txt | #5 |
apport information
apport information
apport information
Leroy Tennison (ltennison) wrote : Lspci.txt | #8 |
apport information
Leroy Tennison (ltennison) wrote : Lsusb.txt | #9 |
apport information
apport information
apport information
apport information
apport information
Leroy Tennison (ltennison) wrote : UdevDb.txt | #14 |
apport information
apport information
Leroy Tennison (ltennison) wrote : | #16 |
Good! I had to subscribe to the bug to get apport-collect to work but obviously after doing so (and answering Yes to "... really .. proceed?" then "Send report") it did what it said.
tags: | added: cscc |
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1708870
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.