Hi,

i have a Cobalt Raq4i with Fedora Core 5 but i can't use the second ethernet port - can anywhere help me ? or which Linux Operation System can use the second ethernet device - Strongbolt,CentOS,Debian ?

the same Problem i have with a raq 3i

If it's working with the primary then it should work with the secondary port.

any RaQ os should work just fine.

As Zeffie notes, the second port on a Raq3i, Raq4i, or other system should be supported by any OS you choose to use. If your additional port is on an add-in card, then the situation might be different, but since the only systems that had a PCI slot where the 3i/4i, I don't know how that could be.

Here are the debug steps:

1) When you plug in the cable, does the LINK and/or TX/RX led on the backpanel light up? If not, your cable may be bad, or you're using a crossover cable improperly, or the port on the other end of the cable is bad;

2) If the backpanel lights go on, then login via SSH (or telnet) and su to root, and run the command /sbin/ifconfig. You should get a result like this:


]# /sbin/ifconfig
eth0 Link encap:Ethernet HWaddr 00:DE:AD:BE:EF:19
inet addr:123.123.123.123 Bcast:123.123.123.251 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:681318 errors:0 dropped:0 overruns:0 frame:0
TX packets:811778 errors:0 dropped:0 overruns:3276 carrier:0
collisions:0 txqueuelen:100
Interrupt:11 Base address:0x1100

eth1 Link encap:Ethernet HWaddr 00:DE:AD:BE:EF:18
inet addr:192.168.0.34 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:939398 errors:0 dropped:0 overruns:0 frame:0
TX packets:49304 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
Interrupt:10 Base address:0x1200

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:3924 Metric:1
RX packets:4125 errors:0 dropped:0 overruns:0 frame:0
TX packets:4125 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0


If it doesn't say "UP" and "RUNNING", then you have a problem. /sbin/ifconfig is the primary tool for manipulating the ports. Read the man page for ifconfig to see what you can do -- you can try to set it to "up" manually, but if you're not seeing it work, then you may have a hardware problem, about which you can do very little.

Good luck!

if your still having problems with this you should post your
/etc/sysconfig/network
/etc/sysconfig/network-scripts/ifcfg-eth*
files and then run
/sbin/ifconfig

That should give me enough to work with...

Hmmm. A reply to a month-old topic? I think he's either solved his problem or given up.

He's not the only one in the world and if someone was to still have a problem like this, then they need to do as I suggested.