I want connect my two Linux PCs running in 2.6 kernel via cross over cable. To do this I have done the following settings after a Google search:

Display stuck on 640x480. 00:1d.7 USB controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d3) 00:1f.0 ISA bridge: Intel Corporation 82801FB/FR (ICH6/ICH6R) LPC Interface Bridge (rev 03) 00:1f.2 IDE interface: Intel Corporation 82801FR/FRW. Connecting two linux pcs via cross cable. Ask Question. USB UHCI #4 (rev 03) 00:1d.7 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev d3) 00:1f.0 ISA bridge: Intel Corporation 82801FBM (ICH6M) LPC Interface Bridge (rev 03) 00. Description of problem: I had sound working with FC4. Did a fresh install of FC5 and can not get sound to work using the ac-97, intel-hda or intel8x0m drivers.

In PC1

1. ifconfig eth0 10.10.11.16 netmask 255.255.255.0 up
2. route add default gw 10.10.11.13 eth0 (default gateway which is ip of pc2 )

In PC2

1. ifconfig eth0 10.10.11.13 netmask 255.255.255.0 up
2. route add default gw 10.10.11.16 eth0 (default gateway which is ip of pc1 )

Then i tried pinging i could not able to connect.Are these above settings enough or any thing am i missing?

For your more information

In PC1

ifconfig output

route -n output

In PC2

ifconfig output

route -n output

migrated from stackoverflow.comMay 5 '11 at 12:39

This question came from our site for professional and enthusiast programmers.

3 Answers

I connected two Fedora machines. Here, I used A and B as the machine names.

Step 1:

Edit File

and enter details for machine A

Step 2:

Edit File

and enter details for machine B

Step 3:

Connect both machines with an Ethernet crossover cable.

Step 4:

Optional reboot.

Step 5:

ping 192.168.1.1 from machine B and ping 192.168.1.2 from machine A

Following are the steps in case if you are still not able to ping. It might be possible that because of the network card's speed difference your machines are not able to ping. Set both machines' speed to constant. Then it might work.

82801fb/fbm/fr/fw/frw (ich6 Family) Usb2 Ehci Controller Driver Windows 7

Then repeat Step 5. If your machines are still not able to ping each other then do the following:

Check which drivers are loaded in dmesg | grep Ethernet lsmod | grep 8139

I entered the lspci command and looked at which Ethernet controller is using your machines.

My A Machine is using RTL8101E/8102E and above lspci output is of Machine B.Download the respective Linux drivers for the Ethernet card and install them. These drivers are very easy to install. Read the readme in the driver's folder.

The configuration that you have done appears to be correct, although it is not neccesary to set each PC as the gateway of the other, the PC just need to be on the same LAN for it to work.

Maybe it's a problem with you cable.

If your network cards have autosensing capabilities, any regular cable of cross-over cable will work (for that reason your test with the Windows PC work) but if they lack this function then you have to use a cross-over cable and a regular UTP cable will not work.

you don't need a route or an gateway if the hosts are in the same subnet (which is the case in your example)So remove the routes and restart the routing daemon (or restart network service)

If that still doesn't work: maybe there could be an problem with speed-negotiation look at the output of ethtool:

use ethtool to change duplex, speed and other settings. All thoes settings should be the same on both systems

Not the answer you're looking for? Browse other questions tagged linux or ask your own question.

82801fb/fbm/fr/fw/frw (ich6 Family) Usb2 Ehci Controller Driver Update

Attachments

82801fb/fbm/fr/fw/frw (ich6 Family) Usb2 Ehci Controller Drivers

Change History

Changed 13 months ago by pals

• attachmentXorg.0.log added

Changed 13 months ago by pals

• attachmentArch-2018-05-18-13-24-04.log added

comment:1 Changed 13 months ago by michael

• Status changed from new to closed
• Resolution set to invalid
• Summary changed from Failed to load module 'vboxvideo' (module does not exist, 0) to Failed to load module 'vboxvideo' (module does not exist, 0) -> expected behaviour