kernel-packages team mailing list archive
-
kernel-packages team
-
Mailing list archive
-
Message #107435
[Bug 1429240] [NEW] Fail to configure shiner T network adapter during installation
You have been subscribed to a public bug:
Problem Description
========================
fail to configure shiner T network adapter during installation
---uname output---
Ubuntu15-04
---Additional Hardware Info---
Shiner T network adapter
Machine Type = 9119-MHE
Steps to Reproduce
=========================
GNU GRUB version 2.02~beta2
+----------------------------------------------------------------------------+
| Install Ubuntu 15.04 |
|*Install Ubuntu 15.04 w/ multipath |
| Install Ubuntu 14.04.1 LTS |
| Install Ubuntu 14.04.1 LTS w/ preseed |
| Rescue mode (14.10 kernel) |
| |
| |
| |
| |
| |
| |
| |
+----------------------------------------------------------------------------+
Use the ^ and v keys to select which entry is highlighted.
Press enter to boot the selected OS, `e' to edit the commands
before booting or `c' for a command-line.
[!!] Configure the network
Your system has multiple network interfaces. Choose the one to use as
the primary network interface during the installation. If possible,
the first connected network interface found has been selected.
Primary network interface:
eth0: Ethernet
===> eth1: Broadcom Corporation NetXtreme II BCM57810 10 Gigabit Ether
eth2: Broadcom Corporation NetXtreme II BCM57810 10 Gigabit Ether
eth3: Broadcom Corporation NetXtreme II BCM57810 10 Gigabit Ether
eth4: Broadcom Corporation NetXtreme II BCM57810 10 Gigabit Ether
<Go Back>
[!!] Configure the network
Network autoconfiguration failed
Your network is probably not using the DHCP protocol. Alternatively,
the DHCP server may be slow or some network hardware is not working
properly.
<Continue>
[!!] Configure the network
From here you can choose to retry DHCP network autoconfiguration
(which may succeed if your DHCP server takes a long time to respond)
or to configure the network manually. Some DHCP servers require a
DHCP hostname to be sent by the client, so you can also choose to
retry DHCP network autoconfiguration with a hostname that you
provide.
Network configuration method:
Retry network autoconfiguration
Retry network autoconfiguration with a DHCP hostname
===> Configure network manually
Do not configure the network at this time
<Go Back>
[!!] Configure the network
The IP address is unique to your computer and may be:
* four numbers separated by periods (IPv4);
* blocks of hexadecimal characters separated by colons (IPv6).
You can also optionally append a CIDR netmask (such as "/24").
If you don't know what to use here, consult your network
administrator.
IP address:
10.33.27.148___________________________________________________
<Go Back> <Continue>
[!!] Configure the network
The netmask is used to determine which machines are local to your
network. Consult your network administrator if you do not know the
value. The netmask should be entered as four numbers separated by
periods.
Netmask:
255.255.0.0_________________________________________________________
<Go Back> <Continue>
[!!] Configure the network
The gateway is an IP address (four numbers separated by periods) that
indicates the gateway router, also known as the default router. All
traffic that goes outside your LAN (for instance, to the Internet) is
sent through this router. In rare circumstances, you may have no
router; in that case, you can leave this blank. If you don't know
the proper answer to this question, consult your network
administrator.
Gateway:
10.33.0.1____________________________________________________________
<Go Back> <Continue>
[!!] Configure the network
The name servers are used to look up host names on the network.
Please enter the IP addresses (not host names) of up to 3 name
servers, separated by spaces. Do not use commas. The first name
server in the list will be the first to be queried. If you don't want
to use any name server, just leave this field blank.
Name server addresses:
9.3.66.216___________________________________________________________
<Go Back> <Continue>
[!] Configure the network
Error
An error occurred and the network configuration process has been
aborted. You may retry it from the installation main menu.
<Continue>
[!] Configure the network
Please enter the hostname for this system.
The hostname is a single word that identifies your system to the
network. If you don't know what your hostname should be, consult your
network administrator. If you are setting up your own home network,
you can make something up here.
Hostname:
riverlp1_____________________________________________________________
<Go Back> <Continue>
[!] Configure the network
The domain name is the part of your Internet address to the right of
your host name. It is often something that ends in .com, .net, .edu,
or .org. If you are setting up a home network, you can make
something up, but make sure you use the same domain name on all your
computers.
Domain name:
isst.aus.stglabs.ibm.com_____________________________________________
<Go Back> <Continue>
[!!] Download debconf preconfiguration file
Failed to retrieve the preconfiguration file
The file needed for preconfiguration could not be retrieved from
http://10.33.11.31/distros/ubuntu/preseed.cfg. The installation will
proceed in non-automated mode.
<Continue>
[!!] Download debconf preconfiguration file
Installation step failed
An installation step failed. You can try to run the failing item
again from the menu, or skip it and choose something else. The
failing step is: Download debconf preconfiguration file
<Continue>
[?] Ubuntu installer main menu
Choose the next step in the install process:
Choose language
Configure the keyboard
Detect network hardware
Configure the network
==> Download debconf preconfiguration file
Choose a mirror of the Ubuntu archive
Download installer components
Change debconf priority
Save debug logs
Execute a shell
Abort the installation
Then it goes to loop for "Download debconf preconfiguration file".
Install method: NFS
== Comment: # - Vaishnavi Bhat <vaish123@xxxxxxxxxx> - ==
>From the log we see a lot of bnx2x error
Mar 5 19:59:28 check-missing-firmware: no missing firmware in /dev/.udev/firmware-missing /run/udev/firmware-missing
Mar 5 19:59:29 kernel: [ 25.157501] bnx2x 0001:50:00.0: Direct firmware load for bnx2x/bnx2x-e2-7.10.51.0.fw failed with error -2
Mar 5 19:59:29 kernel: [ 25.157505] bnx2x: [bnx2x_init_firmware:12969(eth1)]Can't load firmware file bnx2x/bnx2x-e2-7.10.51.0.fw
Mar 5 19:59:29 kernel: [ 25.157506] bnx2x: [bnx2x_func_hw_init:5523(eth1)]Error loading firmware
Mar 5 19:59:29 kernel: [ 25.157509] bnx2x: [bnx2x_nic_load:2704(eth1)]HW init failed, aborting
Mar 5 19:59:29 kernel: [ 25.237479] bnx2x 0001:50:00.1: Direct firmware load for bnx2x/bnx2x-e2-7.10.51.0.fw failed with error -2
Mar 5 19:59:29 kernel: [ 25.237482] bnx2x: [bnx2x_init_firmware:12969(eth2)]Can't load firmware file bnx2x/bnx2x-e2-7.10.51.0.fw
Mar 5 19:59:29 kernel: [ 25.237483] bnx2x: [bnx2x_func_hw_init:5523(eth2)]Error loading firmware
Mar 5 19:59:29 kernel: [ 25.237486] bnx2x: [bnx2x_nic_load:2704(eth2)]HW init failed, aborting
Mar 5 19:59:29 kernel: [ 25.349468] bnx2x 0002:80:00.0: Direct firmware load for bnx2x/bnx2x-e2-7.10.51.0.fw failed with error -2
Mar 5 19:59:29 kernel: [ 25.349471] bnx2x: [bnx2x_init_firmware:12969(eth3)]Can't load firmware file bnx2x/bnx2x-e2-7.10.51.0.fw
Mar 5 19:59:29 kernel: [ 25.349472] bnx2x: [bnx2x_func_hw_init:5523(eth3)]Error loading firmware
Mar 5 19:59:29 kernel: [ 25.349475] bnx2x: [bnx2x_nic_load:2704(eth3)]HW init failed, aborting
Mar 5 19:59:29 kernel: [ 25.433470] bnx2x 0002:80:00.1: Direct firmware load for bnx2x/bnx2x-e2-7.10.51.0.fw failed with error -2
Mar 5 19:59:29 kernel: [ 25.433473] bnx2x: [bnx2x_init_firmware:12969(eth4)]Can't load firmware file bnx2x/bnx2x-e2-7.10.51.0.fw
Mar 5 19:59:29 kernel: [ 25.433475] bnx2x: [bnx2x_func_hw_init:5523(eth4)]Error loading firmware
Mar 5 19:59:29 kernel: [ 25.433477] bnx2x: [bnx2x_nic_load:2704(eth4)]HW init failed, aborting
Looks like the bnx2x fail is causing the installation failure.
** Affects: linux-firmware (Ubuntu)
Importance: Undecided
Status: New
** Tags: architecture-ppc64le bot-comment bugnameltc-122410 severity-critical targetmilestone-inin---
--
Fail to configure shiner T network adapter during installation
https://bugs.launchpad.net/bugs/1429240
You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu.
