June 22, 201214 yr hey guys! just finished up my first unraid build and found then when I booted it up, I could not access it via the browser @ http://tower. I logged into the machine locally and ran an ifconfig which displayed - lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) and no eth0. However, I have activity lights on the NIC. I have double-checked my flash drive for proper formatting and all looks good. The board I am using is an Intel DP43BF which uses a Broadcom BCM57788 chipset. Any ideas on what may be going on? Syslog incoming. I am hoping this isn't because the NIC is unsupported.... Mobo - Intel DP43BF NIC - GigE Broadcom BCM57788 UNRAID v5.0-rc4 syslog.txt
June 24, 201214 yr Author well, a day later and still the same thing. i am getting the impression this damn NIC just isn't supported. what a disappointment... anyways, is there a cheap GigE PCI card that will guarantee compatibility that comes recommended?
June 24, 201214 yr Intel is highly recommended. Although, I've used a cheap Rosewill NIC with a Marvel chip and it works so far.
June 24, 201214 yr According to a google search, your broadcom driver is apparently supported by the tg3 driver module modules.order:kernel/drivers/net/tg3.ko That driver does exist in the 5.0-rc5 version I just installed. (I used this version http://lime-technology.com/forum/index.php?topic=21019.0) Might want to give it a try before installing a new NIC card. Joe L.
June 24, 201214 yr Author According to a google search, your broadcom driver is apparently supported by the tg3 driver module modules.order:kernel/drivers/net/tg3.ko That driver does exist in the 5.0-rc5 version I just installed. (I used this version http://lime-technology.com/forum/index.php?topic=21019.0) Might want to give it a try before installing a new NIC card. Joe L. doesn't seem to make a difference unfortunately. still nothing doing under eth0. gah.
June 24, 201214 yr According to a google search, your broadcom driver is apparently supported by the tg3 driver module modules.order:kernel/drivers/net/tg3.ko That driver does exist in the 5.0-rc5 version I just installed. (I used this version http://lime-technology.com/forum/index.php?topic=21019.0) Might want to give it a try before installing a new NIC card. Joe L. doesn't seem to make a difference unfortunately. still nothing doing under eth0. gah. Can you attach a syslog ?? (you can copy it to the flash drive, then zip it and attach) Or, if you are technical enough, is your NIC found when booting? (look in syslog for clues) You can always try modprobe t3g /etc/rc.d/rc.inetd restart and then see if it then works (You did label the flash drive as UNRIAD (six characters, all upper case))
June 24, 201214 yr Author According to a google search, your broadcom driver is apparently supported by the tg3 driver module modules.order:kernel/drivers/net/tg3.ko That driver does exist in the 5.0-rc5 version I just installed. (I used this version http://lime-technology.com/forum/index.php?topic=21019.0) Might want to give it a try before installing a new NIC card. Joe L. doesn't seem to make a difference unfortunately. still nothing doing under eth0. gah. Can you attach a syslog ?? (you can copy it to the flash drive, then zip it and attach) Or, if you are technical enough, is your NIC found when booting? (look in syslog for clues) You can always try modprobe t3g /etc/rc.d/rc.inetd restart and then see if it then works (You did label the flash drive as UNRIAD (six characters, all upper case)) Joe, my syslog is posted above, on the first post. I can take another one if need be, but nothing has changed other than running the new RC. I looked through it earlier and saw no references to any networking... unless I missed something. Link for the card is up and there is activity on the port. It is not turned off in the BIOS. I will give those commands a shot and see what happens. Yes, flash drive is labeled 'UNRAID'.
June 24, 201214 yr Author According to a google search, your broadcom driver is apparently supported by the tg3 driver module modules.order:kernel/drivers/net/tg3.ko That driver does exist in the 5.0-rc5 version I just installed. (I used this version http://lime-technology.com/forum/index.php?topic=21019.0) Might want to give it a try before installing a new NIC card. Joe L. doesn't seem to make a difference unfortunately. still nothing doing under eth0. gah. Can you attach a syslog ?? (you can copy it to the flash drive, then zip it and attach) You can always try modprobe t3g (You did label the flash drive as UNRIAD (six characters, all upper case)) When I run the modprobe command, I receive the following error - 'FATAL:Module t3g not found'
June 24, 201214 yr According to a google search, your broadcom driver is apparently supported by the tg3 driver module modules.order:kernel/drivers/net/tg3.ko That driver does exist in the 5.0-rc5 version I just installed. (I used this version http://lime-technology.com/forum/index.php?topic=21019.0) Might want to give it a try before installing a new NIC card. Joe L. doesn't seem to make a difference unfortunately. still nothing doing under eth0. gah. Can you attach a syslog ?? (you can copy it to the flash drive, then zip it and attach) You can always try modprobe tg3 (You did label the flash drive as UNRIAD (six characters, all upper case)) When I run the modprobe command, I receive the following error - 'FATAL:Module t3g not found' then you are not running the version I pointed you to. (or, more likely typed t3g instead of tg3. ) It does indeed exist and load on my server. root@Tower2:/lib/modules/3.0.35-unRAID# modprobe tg3 root@Tower2:/lib/modules/3.0.35-unRAID# lsmod Module Size Used by tg3 106879 0 md_mod 45765 6 xor 13949 1 md_mod pl2303 8664 0 pata_jmicron 1432 0 sg 13023 0 usbserial 20265 1 pl2303 sata_sil 5434 0 r8168 170439 0 jmicron 1097 0 ahci 17441 7 libahci 13678 1 ahci i2c_i801 6261 0 i2c_core 12704 1 i2c_i801 Joe L.
June 24, 201214 yr Author According to a google search, your broadcom driver is apparently supported by the tg3 driver module modules.order:kernel/drivers/net/tg3.ko That driver does exist in the 5.0-rc5 version I just installed. (I used this version http://lime-technology.com/forum/index.php?topic=21019.0) Might want to give it a try before installing a new NIC card. Joe L. doesn't seem to make a difference unfortunately. still nothing doing under eth0. gah. Can you attach a syslog ?? (you can copy it to the flash drive, then zip it and attach) You can always try modprobe tg3 (You did label the flash drive as UNRIAD (six characters, all upper case)) When I run the modprobe command, I receive the following error - 'FATAL:Module t3g not found' then you are not running the version I pointed you to. (or, more likely typed t3g instead of tg3. ) It does indeed exist and load on my server. root@Tower2:/lib/modules/3.0.35-unRAID# modprobe tg3 root@Tower2:/lib/modules/3.0.35-unRAID# lsmod Module Size Used by tg3 106879 0 md_mod 45765 6 xor 13949 1 md_mod pl2303 8664 0 pata_jmicron 1432 0 sg 13023 0 usbserial 20265 1 pl2303 sata_sil 5434 0 r8168 170439 0 jmicron 1097 0 ahci 17441 7 libahci 13678 1 ahci i2c_i801 6261 0 i2c_core 12704 1 i2c_i801 Joe L. Joe, You are correct I had simply mistyped it. My apologies. When I run the commands you suggested, the following appears - root@Tower# modprobe tg3 root@Tower# lsmod md_mod 45765 0 xor 13949 1 md_mod sg 13023 0 tg3 106879 0 ahci 17441 0 libahci 13678 1 ahci i2c_i801 6261 0 i2c_core 12704 1 i2c_i801 patamarvell 1837 0 so it does appear to load that module, but no signs of anything installed at eth0.
June 24, 201214 yr Author I did. I left it out because it did not change anything. *attached syslog as well* syslog.txt
June 24, 201214 yr I did. I left it out because it did not change anything. *attached syslog as well* I see in the syslog an attempt to use the tg3 driver. Jun 25 06:55:01 Tower kernel: tg3 0000:07:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 Jun 25 06:55:01 Tower kernel: tg3 0000:07:00.0: setting latency timer to 64 Jun 25 06:55:01 Tower kernel: scsi1 : pata_marvell Jun 25 06:55:01 Tower kernel: ata1: PATA max UDMA/100 cmd 0xd040 ctl 0xd030 bmdma 0xd000 irq 16 Jun 25 06:55:01 Tower kernel: ata2: DUMMY Jun 25 06:55:01 Tower kernel: tg3 mdio bus: probed Jun 25 06:55:01 Tower kernel: tg3 0000:07:00.0: No PHY devices Jun 25 06:55:01 Tower kernel: tg3 0000:07:00.0: Problem fetching invariants of chip, aborting Jun 25 06:55:01 Tower kernel: tg3 0000:07:00.0: PCI INT A disabled based on a google search of same types of error reported, https://bugzilla.redhat.com/show_bug.cgi?id=525966 and https://lists.linux-foundation.org/pipermail/bugme-new/2010-February/024284.html you might try this series of commands modprobe -r tg3 modprobe broadcom modprobe tg3 /etc/rc.d/rc.inetd restart
June 25, 201214 yr Author I did. I left it out because it did not change anything. *attached syslog as well* I see in the syslog an attempt to use the tg3 driver. Jun 25 06:55:01 Tower kernel: tg3 0000:07:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 Jun 25 06:55:01 Tower kernel: tg3 0000:07:00.0: setting latency timer to 64 Jun 25 06:55:01 Tower kernel: scsi1 : pata_marvell Jun 25 06:55:01 Tower kernel: ata1: PATA max UDMA/100 cmd 0xd040 ctl 0xd030 bmdma 0xd000 irq 16 Jun 25 06:55:01 Tower kernel: ata2: DUMMY Jun 25 06:55:01 Tower kernel: tg3 mdio bus: probed Jun 25 06:55:01 Tower kernel: tg3 0000:07:00.0: No PHY devices Jun 25 06:55:01 Tower kernel: tg3 0000:07:00.0: Problem fetching invariants of chip, aborting Jun 25 06:55:01 Tower kernel: tg3 0000:07:00.0: PCI INT A disabled based on a google search of same types of error reported, https://bugzilla.redhat.com/show_bug.cgi?id=525966 and https://lists.linux-foundation.org/pipermail/bugme-new/2010-February/024284.html you might try this series of commands modprobe -r tg3 modprobe broadcom modprobe tg3 /etc/rc.d/rc.inetd restart wow joe, thats some great info. thanks! for whatever reason, when i run the modprobe broadcom entry, it returns a message of Module broadcom not found. You gave me a good place to look though, thank you.
June 25, 201214 yr Author Joe, it would appear that this is exactly the case. The broadcom module needs to load before tg3. However, it seems as tho there is no broadcom module that is loading. But it WOULD appear this NIC is compatible....
June 25, 201214 yr Joe, it would appear that this is exactly the case. The broadcom module needs to load before tg3. However, it seems as tho there is no broadcom module that is loading. But it WOULD appear this NIC is compatible.... It might just be that the broadcom module is known by a different module name these days, or as likely, it is built into the kernel. perhaps a bit more investigation might lead to a different loadable module you could use instead of broadcom.
June 25, 201214 yr Author Joe, it would appear that this is exactly the case. The broadcom module needs to load before tg3. However, it seems as tho there is no broadcom module that is loading. But it WOULD appear this NIC is compatible.... It might just be that the broadcom module is known by a different module name these days, or as likely, it is built into the kernel. perhaps a bit more investigation might lead to a different loadable module you could use instead of broadcom. Thanks again, Joe. You've been great with this. I'll stumble with a bit more to see what I can uncover. Quite the conundrum.
June 25, 201214 yr Author Joe, I received a broadcom.ko file from LimeTech support to support this particular NIC (which, btw, I received at 12am, only a few hours later. Could not believe the turnaround on that. GREAT job guys!!!) However, after doing some searching, I'm not 100% sure as to what to do with this file in order to load it. I am assuming it needs to be placed with other modules so that when the 'modprobe broadcom' command is issued, it grabs it correctly. Thoughts?
Archived
This topic is now archived and is closed to further replies.