[SOLVED] StarTech ST1000BT32 PCI Network Adapter and FC-16

[gkasica]

Hello:

I was recommened to buy the StarTech ST1000BT32 PCI Network Adapter on another linux forum and have it here today. Unfortunately I cannot seem to get it to be seen by the FC16 OS much less obviously actovated with an IP.

The server is running now with an internal NIC Via-Ehine-II at 100MB Full-Duplex to a 1GB D-Link Switch.

For now this card is installed and I was going to bring it up as eth1 to just make sure the link will come up and it will take an IP etc. before making IT ethi0 and disabling the existing built in eth0 card.

Problem being that I cannot seem to get the driver to load properly at all either by command line lsmod, modprobe etc. or the Netwiork GUI.

IS this card supported under FC16 and what do I need to do here to get it working? I'm hoping its in the stock kernel that comes out or can be made to work easilyt as I prefer not to be custom building a kernel just for a 1GB net card.

Here is what I can do so far and it seems to load but doesn't show up when I do an ifconfig -a

Kernel I'm running is 3.3.5-2.fc16.i686

# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:133:64:87:E1
inet addr:108.76.168.146 Bcast:108.76.168.159 Mask:255.255.255.240
inet6 addr: fe80::213:d3ff:fe64:87e1/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:44697 errors:0 dropped:0 overruns:0 frame:0
TX packets:44759 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4201829 (4.0 MiB) TX bytes:35252669 (33.6 MiB)
Interrupt:23 Base address:0xc000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1256 errors:0 dropped:0 overruns:0 frame:0
TX packets:1256 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:266717 (260.4 KiB) TX bytes:266717 (260.4 KiB)


# depmod -a

# modprobe r8169
WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/.

# lsmod | grep r8169
r8169 51125 0
mii 13311 2 r8169,via_rhine

# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:133:64:87:E1
inet addr:108.76.168.146 Bcast:108.76.168.159 Mask:255.255.255.240
inet6 addr: fe80::213:d3ff:fe64:87e1/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:48035 errors:0 dropped:0 overruns:0 frame:0
TX packets:47782 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4508934 (4.3 MiB) TX bytes:37019110 (35.3 MiB)
Interrupt:23 Base address:0xc000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1354 errors:0 dropped:0 overruns:0 frame:0
TX packets:1354 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:286006 (279.3 KiB) TX bytes:286006 (279.3 KiB)


Any and all help is appreciated I'm totally syumped here. I can return the carfds to amazon if needed but it needs to happen fairly quick if thats the issue.

[george_toolan]

What kind of a server board is this? If you have a pci express x1 slot you should definitely get a pci express nic instead, because pci is obsolete now and way too slow.

Disable the onboard nic and try again. Try to remove the deprecated config file /etc/modprobe.conf

lspci | grep -i eth

[gkasica]

I don't have PCI Express slots only 2 PCI which is why this card is being used speed is not a critical issue here but I washoping to at least be consistant with the cards as I have 3 other servers running the same card and trhis way don't need to keep multiple spares around.

The board is an A4XPER I believe but short of opening up the box and trying to locate I model/serial # I don't know for certain.

I've removed the config file and retried it what I see is below:

rm -rf modprobe.conf

[root@saturn etc]# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:133:64:87:E1
inet addr:108.76.168.146 Bcast:108.76.168.159 Mask:255.255.255.240
inet6 addr: fe80::213:d3ff:fe64:87e1/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1368696 errors:0 dropped:0 overruns:0 frame:0
TX packets:1331147 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:197122702 (187.9 MiB) TX bytes:639579770 (609.9 MiB)
Interrupt:23 Base address:0xc000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:26742 errors:0 dropped:0 overruns:0 frame:0
TX packets:26742 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:5669618 (5.4 MiB) TX bytes:5669618 (5.4 MiB)

# lspci | grep -i eth
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 78)

# depmod -a

# lsmod | grep r8169

# modprobe r8169

# lsmod | grep r8169
r8169 51125 0
mii 13311 2 r8169,via_rhine

# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:133:64:87:E1
inet addr:108.76.168.146 Bcast:108.76.168.159 Mask:255.255.255.240
inet6 addr: fe80::213:d3ff:fe64:87e1/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1368696 errors:0 dropped:0 overruns:0 frame:0
TX packets:1331147 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:197122702 (187.9 MiB) TX bytes:639579770 (609.9 MiB)
Interrupt:23 Base address:0xc000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:26742 errors:0 dropped:0 overruns:0 frame:0
TX packets:26742 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:5669618 (5.4 MiB) TX bytes:5669618 (5.4 MiB)

# lspci | grep -i eth
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 78)

I willtry to disable the on board later today and see if that does anything but I've already done that when I started here with this and what I end up with is no ethernet at all. Will try with a knoppic CD.

---------- Post added at 11:18 AM ---------- Previous post was at 06:28 AM ----------

OK. Problem solved. Turns out the card wasn't seated all the way apparently. I reseated it and it popped right up as eth1. One thing I HAVE run into is that no matter what I do including disabling the built in poet in BIOS the network manager still wants it to be eth1 and despite anything I try it won't run unless set as eth1. Even though there is no eth0. Nolt abig deal but took a bit of thinking to figure that one out.

Thanks.