bnx2x fails to load firmware on Dell R430
-
I’ve enabled debug and cranked logging to 7 (max) so i’m going to restart the server and see what we get.
-
Ok this is probably my ignorance showing, but under reports/imaging logs i have nothing, i checked the other listings too. where are the logs supposed to show?
-
@grey are you looking in the FOS Linux on the target computer? These logs will not be on the fog server.
-
@george1421
darnit yes i was looking on the fog server, how do I access the kernel on the target computer?
-
@grey Well I guess we miss something here. Lets start over.
- In the fog gui go to the following location: FOG Configuration Page->FOG Settings->FOG Boot Settings->FOG_KERNEL_LOGLEVEL and set the logging level to 7.
- Register this server with fog you will need the mac address of the interface you are going to pxe boot from.
- Once the target computer is registered, then schedule a debug capture in the FOG web gui
- PXE boot the target computer this should start the FOS linux on the server, you should see the error about the firmware and not being able to pickup an IP address, but after some time on the target computer you should be dropped to a linux command prompt. Again this is on the target computer.
- From here you can navigate to the /var/log directory (on the target computer) and inspect the logs. You will have to do this from the server’s console since your networking is not working yet, or you could connect via ssh if you set root’s password (which is blank by default, so sshd will not let you connect).
-
@george1421 said in bnx2x fails to load firmware on Dell R430:
@grey Well I guess we miss something here. Lets start over.
ok, sat through the whole boot process, once i get the errors it drops to a menu with reboot, network info, partition info, etc etc. it never actually gets me to a login prompt. it doesn’t recognize ctl C. really all i can do is reboot from that point.- In the fog gui go to the following location: FOG Configuration Page->FOG Settings->FOG Boot Settings->FOG_KERNEL_LOGLEVEL and set the logging level to 7.
- Register this server with fog you will need the mac address of the interface you are going to pxe boot from.
- Once the target computer is registered, then schedule a debug capture in the FOG web gui
- PXE boot the target computer this should start the FOS linux on the server, you should see the error about the firmware and not being able to pickup an IP address, but after some time on the target computer you should be dropped to a linux command prompt. Again this is on the target computer.
- From here you can navigate to the /var/log directory (on the target computer) and inspect the logs. You will have to do this from the server’s console since your networking is not working yet, or you could connect via ssh if you set root’s password (which is blank by default, so sshd will not let you connect).
-
@grey Well that didn’t work out well. Can you take a screen shot where you see the error with a mobile phone and post it here?
I would still like to see you disable pxe booting on all LOM network adapters and have you attempt to pxe boot off an older nic installed in a riser slot. The only goal here is to get to a FOS linux command prompt. From there we should be able to review the boot time logs.
-
@george1421 I believe you should hit enter, at least that how I normally do it.
Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.
Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)
Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG
-
@Tom-Elliott said in bnx2x fails to load firmware on Dell R430:
@george1421 I believe you should hit enter, at least that how I normally do it.
< i didn’t try that, its sitting at the menu in debug mode now, i’ll go try that
-
@grey ok just needed to hit enter… here is the relevant part of the syslog
I have the whole log if I did’nt capture what you wanted.Sep 15 22:45:51 fogclient user.warn kernel: bnx2x 0000:04:00.1: Direct firmware load for bnx2x/bnx2x-e2-7.13.1.0.fw failed with error -2 Sep 15 22:45:51 fogclient user.err kernel: bnx2x: [bnx2x_init_firmware:13444(eth1)]Can't load firmware file bnx2x/bnx2x-e2-7.13.1.0.fw Sep 15 22:45:51 fogclient user.err kernel: bnx2x: [bnx2x_func_hw_init:5785(eth1)]Error loading firmware Sep 15 22:45:51 fogclient user.err kernel: bnx2x: [bnx2x_nic_load:2727(eth1)]HW init failed, aborting Sep 15 22:46:26 fogclient user.warn kernel: bnx2x 0000:05:00.0: Direct firmware load for bnx2x/bnx2x-e2-7.13.1.0.fw failed with error -2 Sep 15 22:46:26 fogclient user.err kernel: bnx2x: [bnx2x_init_firmware:13444(eth2)]Can't load firmware file bnx2x/bnx2x-e2-7.13.1.0.fw Sep 15 22:46:26 fogclient user.err kernel: bnx2x: [bnx2x_func_hw_init:5785(eth2)]Error loading firmware Sep 15 22:46:26 fogclient user.err kernel: bnx2x: [bnx2x_nic_load:2727(eth2)]HW init failed, aborting Sep 15 22:47:01 fogclient user.warn kernel: bnx2x 0000:05:00.1: Direct firmware load for bnx2x/bnx2x-e2-7.13.1.0.fw failed with error -2 Sep 15 22:47:01 fogclient user.err kernel: bnx2x: [bnx2x_init_firmware:13444(eth3)]Can't load firmware file bnx2x/bnx2x-e2-7.13.1.0.fw Sep 15 22:47:01 fogclient user.err kernel: bnx2x: [bnx2x_func_hw_init:5785(eth3)]Error loading firmware Sep 15 22:47:01 fogclient user.err kernel: bnx2x: [bnx2x_nic_load:2727(eth3)]HW init failed, aborting Sep 15 22:48:47 fogclient user.notice kernel: random: nonblocking pool is initialized -
@grey When you do a debug capture the FOS engine will boot just like its going to do a capture, but instead of capturing it will print a bunch of instructions on the screen. You have to press enter a few times (on the target computer)
… ok you just posted the logs that is a good find in the logs.
-
@george1421
i’ve been reading through all this and i wanted to make this distinctionthis is the RJ45 1 gig ethernet nic, the one i’m using for imageing
2:00.0 Ethernet controller [0200]: Broadcom Corporation NetXtreme BCM5720 Gigabit Ethernet PCIe [14e4:165f]this is a 10g fiberchannel port and is not important for imaging
04:00.1 Ethernet controller [0200]: Broadcom Corporation NetXtreme II BCM57810 10 Gigabit Ethernet [14e4:168e] (rev 10)just don’t want anyone to waste effort on the 10g port as its not being used for this.
-
@grey OK then, we are looking for device 02:00.0. If I understand the logs correctly you posted the error for device 04:00.0
Just to make sure eth0 and eth1 are the 1GbE nics?
I’ve also been searching on that error, I did find two posts that were similar errors
https://github.com/coreos/bugs/issues/450
https://lkml.org/lkml/2016/5/9/797I’m still trying to understand if the error -2 means the firmware doesn’t exist or its some other indication.
Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
-
You mind rerunning the installer? I’ve added the missing firmware to the kernel build.
Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.
Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)
Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG
-
I just got a moment to do the same thing, heres more of the logfile,
the devices stuff is difficult for me to interprete, the device i need to work is Broadcom 5720 DP 1Gb Network Interface * I think*
Sep 15 22:44:45 fogclient user.info kernel: tg3 0000:02:00.1 eth5: Link is up at 1000 Mbps, full duplex
Sep 15 22:44:45 fogclient user.info kernel: tg3 0000:02:00.1 eth5: Flow control is off for TX and off for RX
Sep 15 22:44:45 fogclient user.info kernel: tg3 0000:02:00.1 eth5: EEE is disabled
Sep 15 22:45:15 fogclient user.warn kernel: bnx2x 0000:04:00.0: Direct firmware load for bnx2x/bnx2x-e2-7.13.1.0.fw failed with error -2
Sep 15 22:45:15 fogclient user.err kernel: bnx2x: [bnx2x_init_firmware:13444(eth0)]Can’t load firmware file bnx2x/bnx2x-e2-7.13.1.0.fw
Sep 15 22:45:15 fogclient user.err kernel: bnx2x: [bnx2x_func_hw_init:5785(eth0)]Error loading firmware
Sep 15 22:45:15 fogclient user.err kernel: bnx2x: [bnx2x_nic_load:2727(eth0)]HW init failed, aborting
Sep 15 22:45:51 fogclient user.warn kernel: bnx2x 0000:04:00.1: Direct firmware load for bnx2x/bnx2x-e2-7.13.1.0.fw failed with error -2
Sep 15 22:45:51 fogclient user.err kernel: bnx2x: [bnx2x_init_firmware:13444(eth1)]Can’t load firmware file bnx2x/bnx2x-e2-7.13.1.0.fw
Sep 15 22:45:51 fogclient user.err kernel: bnx2x: [bnx2x_func_hw_init:5785(eth1)]Error loading firmware
Sep 15 22:45:51 fogclient user.err kernel: bnx2x: [bnx2x_nic_load:2727(eth1)]HW init failed, aborting
Sep 15 22:46:26 fogclient user.warn kernel: bnx2x 0000:05:00.0: Direct firmware load for bnx2x/bnx2x-e2-7.13.1.0.fw failed with error -2
Sep 15 22:46:26 fogclient user.err kernel: bnx2x: [bnx2x_init_firmware:13444(eth2)]Can’t load firmware file bnx2x/bnx2x-e2-7.13.1.0.fw
Sep 15 22:46:26 fogclient user.err kernel: bnx2x: [bnx2x_func_hw_init:5785(eth2)]Error loading firmware
Sep 15 22:46:26 fogclient user.err kernel: bnx2x: [bnx2x_nic_load:2727(eth2)]HW init failed, aborting
Sep 15 22:47:01 fogclient user.warn kernel: bnx2x 0000:05:00.1: Direct firmware load for bnx2x/bnx2x-e2-7.13.1.0.fw failed with error -2
Sep 15 22:47:01 fogclient user.err kernel: bnx2x: [bnx2x_init_firmware:13444(eth3)]Can’t load firmware file bnx2x/bnx2x-e2-7.13.1.0.fw
Sep 15 22:47:01 fogclient user.err kernel: bnx2x: [bnx2x_func_hw_init:5785(eth3)]Error loading firmware
Sep 15 22:47:01 fogclient user.err kernel: bnx2x: [bnx2x_nic_load:2727(eth3)]HW init failed, aborting
Sep 15 22:48:47 fogclient user.notice kernel: random: nonblocking pool is initialized
Sep 15 22:49:12 fogclient user.info kernel: usb 1-1.4: USB disconnect, device number 3
Sep 15 22:49:20 fogclient user.info kernel: usb 1-1.4: new high-speed USB device number 5 using ehci-pci
Sep 15 22:49:20 fogclient user.info kernel: usb-storage 1-1.4:1.0: USB Mass Storage device detected
Sep 15 22:49:20 fogclient user.info kernel: scsi host6: usb-storage 1-1.4:1.0
Sep 15 22:49:21 fogclient user.notice kernel: scsi 6:0:0:0: Direct-Access SanDisk Cruzer Blade 1.00 PQ: 0 ANSI: 6
Sep 15 22:49:21 fogclient user.notice kernel: sd 6:0:0:0: [sdi] 15630336 512-byte logical blocks: (8.00 GB/7.45 GiB)
Sep 15 22:49:21 fogclient user.notice kernel: sd 6:0:0:0: [sdi] Write Protect is off
Sep 15 22:49:21 fogclient user.debug kernel: sd 6:0:0:0: [sdi] Mode Sense: 43 00 00 00
Sep 15 22:49:21 fogclient user.notice kernel: sd 6:0:0:0: [sdi] Write cache: disabled, read cache: enabled, doesn’t support DPO or FUA
Sep 15 22:49:21 fogclient user.info kernel: sdi: sdi1
Sep 15 22:49:21 fogclient user.notice kernel: sd 6:0:0:0: [sdi] Attached SCSI removable disk
Sep 15 22:49:27 fogclient auth.info sshd[4338]: Server listening on 0.0.0.0 port 22.
Sep 15 22:53:32 fogclient daemon.info init: starting pid 4575, tty ‘/dev/tty0’: ‘-/bin/bash’
Sep 15 22:57:49 fogclient user.info kernel: usb 1-1.4: USB disconnect, device number 5
Sep 15 23:00:41 fogclient user.info kernel: usb 1-1.4: new high-speed USB device number 6 using ehci-pci
Sep 15 23:00:41 fogclient user.info kernel: usb-storage 1-1.4:1.0: USB Mass Storage device detected
Sep 15 23:00:41 fogclient user.info kernel: scsi host7: usb-storage 1-1.4:1.0
Sep 15 23:00:42 fogclient user.notice kernel: scsi 7:0:0:0: Direct-Access SanDisk Cruzer Blade 1.00 PQ: 0 ANSI: 6
Sep 15 23:00:42 fogclient user.notice kernel: sd 7:0:0:0: [sdj] 15630336 512-byte logical blocks: (8.00 GB/7.45 GiB)
Sep 15 23:00:42 fogclient user.notice kernel: sd 7:0:0:0: [sdj] Write Protect is off
Sep 15 23:00:42 fogclient user.debug kernel: sd 7:0:0:0: [sdj] Mode Sense: 43 00 00 00
Sep 15 23:00:42 fogclient user.notice kernel: sd 7:0:0:0: [sdj] Write cache: disabled, read cache: enabled, doesn’t support DPO or FUA
Sep 15 23:00:42 fogclient user.info kernel: sdj: sdj1
Sep 15 23:00:42 fogclient user.notice kernel: sd 7:0:0:0: [sdj] Attached SCSI removable disk
Sep 15 23:00:54 fogclient user.err kernel: FAT-fs (sdi1): unable -
sure np
-
@Tom-Elliott said in bnx2x fails to load firmware on Dell R430:
You mind rerunning the installer? I’ve added the missing firmware to the kernel build.
So does that bring the current kernel to 4.7.4? Just for my knowledge.
-
@george1421 No, it is the version of the current kernel (4.7.3) as on kernel.org
Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.
Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)
Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG
-
@Tom-Elliott Understood, thx.
-
@Tom-Elliott said in bnx2x fails to load firmware on Dell R430:
You mind rerunning the installer? I’ve added the missing firmware to the kernel build.
ok, re-installed fog rebooted on the new kernel, drivers loaded fine but all drivers say there is no link, although its running on a pxe kernel :-p. all the firmware errors are gone. I’m running out of time here today, but I’ll jump into tomorrow and see what the link issue is about. the debug kernel selection is still loading by default so i guess it will do that until i delete the task.
