vsiege
November 30th, 2007, 06:06 PM
Im installing U Server and I got to the part where it wants to look for a network - and it cannot detect DHCP. What do I do?
All my other boxes (mac and windows) are running fine on my router. The lights on the back of the soon-to-be linux box does not indicate a network connection (little lights next to RJ-45 socket) and the one on my router. I took down the netowork and put it back up and still nothing.
I thought that maybe it would not work b/c its installling linux and maybe the driver to run the NIC card neeeds to be installed - so I looked on my MOBO disk for Linux drivers and found a NIC driver and heres what i found...sounds like i need to have it installed after linux is in. any ideas?
<Linux device driver for Realtek Ethernet controllers>
This is the Linux device driver released for RealTek Ethernet controllers, which are listed as following.
1. RTL8169S/SB/SC (Gigabit Ethernet with PCI interface)
2. RTL8168B (Gigabit Ethernet with PCI-Express interface)
3. RTL8101E (Fast Ethernet with PCI-Express interface)
<Requirements>
- kernel source tree (supported versions 2.4.x or 2.6.x)
- compiler/binutils for kernel compilation
<Quick install with proper kernel settings>
Unpack the tarball :
tar vzxf r1000_vX.YZ.tgz
Change to the directory:
cd r1000_vX.YZ
If you are running the target kernel, then you should be
able to do :
make clean modules (as root or with sudo)
make install
depmod -a
<Force Link Status>
1. Force the link status when insert the driver.
If the user is in the path ~/r1000, the link status can be forced to one of the 5 modes as following command.
#insmod ./src/r1000.ko speed=SPEED_MODE duplex=DUPLEX_MODE autoneg=NWAY_OPTION
,where
SPEED_MODE = 1000 for 1000Mbps
= 100 for 100Mbps
= 10 for 10Mbps
DUPLEX_MODE = 0 for half-duplex
= 1 for full-duplex
NWAY_OPTION = 0 for auto-negotiation off
= 1 for auto-negotiation on
For example:
#insmod ./src/r1000.ko speed=100 duplex=0 autoneg=0
will force PHY to operate in 100Mpbs Half-duplex.
2. Force the link status by using ethtool.
a. Insert the driver first.
b. Make sure that ethtool exists in /sbin.
c. Force the link status as the following command.
#ethtool -s eth? speed SPEED_MODE duplex DUPLEX_MODE autoneg NWAY_OPTION
,where
SPEED_MODE = 1000 for 1000Mbps
= 100 for 100Mbps
= 10 for 10Mbps
DUPLEX_MODE = half for half-duplex
= full for full-duplex
NWAY_OPTION = off for auto-negotiation off
= on for auto-negotiation on
All my other boxes (mac and windows) are running fine on my router. The lights on the back of the soon-to-be linux box does not indicate a network connection (little lights next to RJ-45 socket) and the one on my router. I took down the netowork and put it back up and still nothing.
I thought that maybe it would not work b/c its installling linux and maybe the driver to run the NIC card neeeds to be installed - so I looked on my MOBO disk for Linux drivers and found a NIC driver and heres what i found...sounds like i need to have it installed after linux is in. any ideas?
<Linux device driver for Realtek Ethernet controllers>
This is the Linux device driver released for RealTek Ethernet controllers, which are listed as following.
1. RTL8169S/SB/SC (Gigabit Ethernet with PCI interface)
2. RTL8168B (Gigabit Ethernet with PCI-Express interface)
3. RTL8101E (Fast Ethernet with PCI-Express interface)
<Requirements>
- kernel source tree (supported versions 2.4.x or 2.6.x)
- compiler/binutils for kernel compilation
<Quick install with proper kernel settings>
Unpack the tarball :
tar vzxf r1000_vX.YZ.tgz
Change to the directory:
cd r1000_vX.YZ
If you are running the target kernel, then you should be
able to do :
make clean modules (as root or with sudo)
make install
depmod -a
<Force Link Status>
1. Force the link status when insert the driver.
If the user is in the path ~/r1000, the link status can be forced to one of the 5 modes as following command.
#insmod ./src/r1000.ko speed=SPEED_MODE duplex=DUPLEX_MODE autoneg=NWAY_OPTION
,where
SPEED_MODE = 1000 for 1000Mbps
= 100 for 100Mbps
= 10 for 10Mbps
DUPLEX_MODE = 0 for half-duplex
= 1 for full-duplex
NWAY_OPTION = 0 for auto-negotiation off
= 1 for auto-negotiation on
For example:
#insmod ./src/r1000.ko speed=100 duplex=0 autoneg=0
will force PHY to operate in 100Mpbs Half-duplex.
2. Force the link status by using ethtool.
a. Insert the driver first.
b. Make sure that ethtool exists in /sbin.
c. Force the link status as the following command.
#ethtool -s eth? speed SPEED_MODE duplex DUPLEX_MODE autoneg NWAY_OPTION
,where
SPEED_MODE = 1000 for 1000Mbps
= 100 for 100Mbps
= 10 for 10Mbps
DUPLEX_MODE = half for half-duplex
= full for full-duplex
NWAY_OPTION = off for auto-negotiation off
= on for auto-negotiation on