On Tue, 2009-09-29 at 16:55 +0200, Per Jessen wrote:

Mark Misulich wrote:

...

Hi, I just finished building a new desktop computer, in order to teach myself more about how they work. I have installed a linux driver for the integrated ethernet card on the motherboard from realtek, and it works well. Unfortunately it only works after I configure the card in yast each time after I boot. How do I configure things so that the card will be activated at boot? [snip] STARTMODE='auto'

I'm not certain, but maybe STARTMODE=onboot will do it.

/Per

Thanks, but that didn't do it. Mark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Are you using the NetworkManager thingiemajig or are you using the traditional ifup/down ? If the former, that's where you'll have to look - I never use it, so can't help you much.

/Per

I am using traditional ifup. But I tried NetworkManager and that didn't help. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Tue, 2009-09-29 at 19:50 +0200, Per Jessen wrote:

Okay. So to sum up you've got a network card that isn't automatically configured when you boot up -

Yes, that is correct.

is the card not at all there, or do you see it, but with no address configured?

When I open yast to the network devices, it shows the card is there but not connected.

What does 'ip addr' show right after boot up?

In yast it says ip address automatically assigned via DHCP. In Terminal ip addr shows exactly the same thing on bootup both before and after I activate the card via yast. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Tuesday 29 September 2009 11:41:35 pm Per Jessen wrote:

I'm slowly beginning to suspect a DHCP problem - if 'ip addr' shows exactly the same output before and after you activate the card, the activation doesn't do anything. Can we see the output from 'ip addr' please? Maybe also the output from 'grep -i dhcp /var/log/messages' ?

i think there's no default route set up. yast does that when it runs thru' it's config. routine. -- phani. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

But Mark doesn't need a default route unless he wants to access something outside his local network.

Mark, when you say "Unfortunately it only works after I configure the card in yast each time after I boot", what do you mean by "works" ?

I mean that I can't connect to the internet until I configure the card in yast. I can see that the little led's next to the plug in on the back of the computer are lighting, so the card isn't dead.

How do you test it? Can you ping a local machine from the new system or can you ping the new system from a local machine? I don't know how to do that, I know how to use ping but I don't know what the address would be of my older computer connected to the same router.

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Wednesday 30 September 2009 12:10:58 am Mark Misulich wrote:

I mean that I can't connect to the internet until I configure the card in yast. I can see that the little led's next to the plug in on the back of the computer are lighting, so the card isn't dead.

the last email (which you sent to per an me instead of the list address) shows that you don't have a default route set up. this means your network doesn't know where to find the internet. it may be enough to create the routes file in your network directory. you can do that with the following commands: ----------------------- su [enter root password when prompted] cat > /etc/sysconfig/network/routes [after entering this, type the following exactly as shown here:] default 192.168.0.1 - - [now press ctrl + d] ----------------------- this should create the required file, hopefully with the proper permissions. this _might_ be enogh to get you connected to the internet after booting. if not, there are other files that may need to be edited... -- phani. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Tuesday 29 September 2009 11:36:14 pm Mark Misulich wrote:

In Terminal ip addr shows exactly the same thing on bootup both before and after I activate the card via yast.

you mean it shows an actual IP address, that's assigned by the DHCP server? that means your card is working. what's probably not working is your route configuration, means your network can't get anywhere. what's in /etc/sysconfig/network/routes (before configuration with yast)? -- phani. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Tuesday 29 September 2009 12:50:54 pm Per Jessen wrote:

Okay. So to sum up you've got a network card that isn't automatically configured when you boot up -

is the card not at all there, or do you see it, but with no address configured?

What does 'ip addr' show right after boot up?

/Per

Per, It sound like a module isn't being loaded at boot and is loaded after he goes through the yast-network config. Mark, boot your system and BEFORE you start the network do a: lsmod > net-before Then start your network with yast and get it running. After it is running, do lsmod > net-after then diff net-before net-after Then post the result of the diff (if any) -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Tuesday 29 September 2009 02:50:14 pm phanisvara das wrote:

On Wednesday 30 September 2009 01:10:15 am David C. Rankin wrote:

...

It sound like a module isn't being loaded at boot and is loaded after he goes through the yast-network config. Mark, boot your system and BEFORE you start the network do a:

don't think that's it. IMO it's just that he's got no default route, perhaps no DNS server configured either. after all, he wrote that his network card was blinking, probably connecting to something on the local net.

Ah, I hadn't followed the thread that closely and had missed the blinking part. I agree, if it's blinking, then something is talking to the card. I'll catch up on the thread and see if I can't mess it up again ;-) -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

appears that you were right, after all. after getting all types of network stats before starting yast, it became clear that the card wasn't enabled at all. he then managed to fix his modules according to instructions he found somewhere else, so now it's working. :)

-- phani.

Ok, that was how things were, but I just got the problem solved. I checked lsmod before using yast to start the ehternet card to see what modules were loaded. Then I checked lsmod after starting the ethernet card, and I found that the r8169 module was loaded, but not the r8101 module. I removed r8169 yesterday, but it was back again, and r8101 was gone. I removed r8169 using rmmod r8169, but it came back shortly afterwards. So I added the comment blacklist r8169 to /etc/modprobe.d/blacklist. Then I removed r8169 again using rmmod r8169 and it went away. Then, I added the following to /etc/modprobe.conf ########################################################################################### #replacement network driver ########################################################################################### alias eth0 r8101 Then,I recompiled the r8101 module per the instructions in the readme file. I next made sure that my modifications from yesterday to the /etc/sysconfig/network/ifcfg-eth0 were still there, and they were. They read: DEVICE='eth0' BOOTPROTO='dhcp' ONBOOT='yes' Voila, the network card connects to the internet as soon as the computer boots up. Hi, I've been thinking about this and trying to figure out why the r8101 module went away. I did some updates on the computer after I got the ethernet card to work, and one of them required that I reboot the computer. I expect that must have been a kernel update, and that may be why I had to reinstall the r8101 kernel module. Now that I have blacklisted the default r8169 kernel module that comes preinstalled in the linux kernel, how may I keep the r8101 module without having to recompile it and reinstall it every time there is a kernel update? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

...

I noticed sometimes in if I have network settings in Yast

(Yast --> Network Devices --> Network Settings)

set to use Network Manager it doesn't work properly, If you use the traditional ifup it works fine.

Then click on the overview tab and highlight the device, then click on Edit then click on the General tab then the first option says Activate Device and make sure it says at boot then keep hitting Next until it goes through it's thing and restart network services.

That worked for me in opensuse 11.1

Hi, I have been using the trad. ifup method and then as per your instructions above, but something is preventing the card from starting until I start it in yast. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Tue, 2009-09-29 at 21:18 +0530, phanisvara das wrote:

On Tuesday 29 September 2009 08:25:14 pm Per Jessen wrote:

...

I'm not certain, but maybe STARTMODE=onboot will do it.

in my installation STARTMODE is also "auto," and the network starts ok.

what about runlevels (yast2 -> system services (runlevel))? perhaps "network" or "network-remotefs" isn't set to start at the appropriate runlevels (2, 3, and 5) ?

-- phani.

In my installation runlevels for network and network-rfs are set to start at 2, 3, & 5. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Hi, maybe this info may help you to instruct me a little better. I read through the readme file again and I wonder if more of it might be pertinent. I setup the network information as per 2b DHCP, and I thought that was all that was needed. Maybe I have to do more, so have a look and see if I am causing the problem.

you sent your email to my personal address again. that's not good, since nobody else on this list will see it. please use the list address for replies. perhaps david is correct and it really is a module problem, in which case the readme of your ethernet controller would be useful. i still suspect it's the configuration of your route and DNS resolution, though. we can find out what's happening if you post the output of the following two commands: arp -n cat /etc/resolv.conf and for good measure, you can add the output of these two commands again: ifconfig route -n before configuring your network via yast. that should show if your network is working at all or not. -- phani. [lengthy readme file follows below]

<Linux device driver for Realtek Ethernet controllers>

This is the Linux device driver released for RealTek RTL8101E, RTL8102E(L) and RTL8103E(L), the Fast Ethernet controller with PCI-Express interface.

<Requirements>

- kernel source tree (supported Linux kernel 2.6.x and 2.4.x) - For linux kernel 2.4.x, this driver supports linux kernel 2.4.20 and latter. - compiler/binutils for kernel compilation

<Quick install with proper kernel settings> Check whether the built-in driver, r8169.ko (or r8169.o for kernel 2.4.x), is installed. # lsmod | grep r8169

If it is installed, please remove it. # rmmod r8169 note: If the built-in driver cannot removed by rmmod, please edit /etc/modprobe.conf and comment 'alias eth0 r8169'. Then, remmove it again or reboot your computer.

Unpack the tarball : # tar vjxf r8101-1.aaa.bb.tar.bz2

Change to the directory: # cd r8101-1.aaa.bb

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 # modprobe r8101

You can check whether the driver is loaded by using following

commands.

# lsmod | grep r8101 # ifconfig -a

If there is a device name, ethX, shown on the monitor, the linux driver is loaded. Then, you can use the following command to activate the ethX.

# ifconfig ethX

,where X=0,1,2,...

<Set the network related information> 1. Set manually a. Set the IP address of your machine.

# ifconfig ethX "the IP address of your machine"

b. Set the IP address of DNS.

Insert the following configuration in /etc/resolv.conf.

nameserver "the IP address of DNS"

c. Set the IP address of gateway.

# route add default gw "the IP address of gateway"

2. Set by doing configurations in /etc/sysconfig/network-scripts /ifcfg-ethX for Redhat and Fedora, or /etc/sysconfig/network /ifcfg-ethX for SuSE. There are two examples to set network configurations.

a. Fixed IP address: DEVICE=eth0 BOOTPROTO=static ONBOOT=yes TYPE=ethernet NETMASK=255.255.255.0 IPADDR=192.168.1.1 GATEWAY=192.168.1.254 BROADCAST=192.168.1.255

b. DHCP: DEVICE=eth0 BOOTPROTO=dhcp ONBOOT=yes

<Modify the MAC address> There are two ways to modify the MAC address of the NIC. 1. Use ifconfig:

# ifconfig ethX hw ether YY:YY:YY:YY:YY:YY

,where X is the device number assigned by Linux kernel, and YY:YY:YY:YY:YY:YY is the MAC address assigned by the user.

2. Use ip:

# ip link set ethX address YY:YY:YY:YY:YY:YY

,where X is the device number assigned by Linux kernel, and YY:YY:YY:YY:YY:YY is the MAC address assigned by the user.

<Force Link Status>

1. Force the link status when insert the driver.

If the user is in the path ~/r8101, the link status can be forced to one of the 4 modes as following command.

# insmod ./src/r8101.ko speed=SPEED_MODE duplex=DUPLEX_MODE autoneg=NWAY_OPTION

,where SPEED_MODE = 100 for 100Mbps = 10 for 10Mbps DUPLEX_MODE = 0 for half-duplex = 1 for full-duplex NWAY_OPTION = 0 for auto-negotiation off (true force) = 1 for auto-negotiation on (nway force) For example:

# insmod ./src/r8101.ko speed=100 duplex=0 autoneg=1

will force PHY to operate in 100Mpbs Half-duplex(nway force).

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 ethX speed SPEED_MODE duplex DUPLEX_MODE autoneg NWAY_OPTION

,where SPEED_MODE = 100 for 100Mbps = 10 for 10Mbps DUPLEX_MODE = half for half-duplex = full for full-duplex NWAY_OPTION = off for auto-negotiation off (true force) = on for auto-negotiation

on (nway force)

For example:

# ethtool -s eth0 speed 100 duplex full autoneg on

will force PHY to operate in 100Mpbs Full-duplex(nway force).

<Jumbo Frame> RTL8101E, RTL8102E and RTL8103E do not support Jumbo Frame.

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Tue, 2009-09-29 at 21:43 -0400, Mike wrote:

On September 29, 2009, Mike wrote:

...

On September 29, 2009, Mark Misulich wrote:

...

With the wrong driver mine appears to work but is unable to receive. The system tries to load the r8169 driver and I have to force the 8168 instead.

OK it looks like you have the same driver issue I have.

When you reconfigure in Yast do you change the driver fron to 8168 each time?

Do you have the r8168 module built for your curent kernel?

have you added this to your modprobe.conf? #################################### #replacement network driver #################################### alias eth0 r8168

and have you added this to /etc/modprobe.d/blacklist blacklist r8169

Hi, no, I think that the previous post that I made was misunderstood. The 8169 kernel module is built in the Linux kernel by default. The readme file told me to remove it, so I did. Then I compiled a kernel module for the 8101/8102 pci fast ethernet card on the motherboard and installed it. I don't have to change the driver from 8169 to 8101/2 each time I go into yast, I just have to open up the Network settings, hit Ok when it displays. It starts network services and I can get on the internet. Ok, that was how things were, but I just got the problem solved. I checked lsmod before using yast to start the ehternet card to see what modules were loaded. Then I checked lsmod after starting the ethernet card, and I found that the r8169 module was loaded, but not the r8101 module. I removed r8169 yesterday, but it was back again, and r8101 was gone. I removed r8169 using rmmod r8169, but it came back shortly afterwards. So I added the comment blacklist r8169 to /etc/modprobe.d/blacklist. Then I removed r8169 again using rmmod r8169 and it went away. Then, I added the following to /etc/modprobe.conf ########################################################################################### #replacement network driver ########################################################################################### alias eth0 r8101 Then,I recompiled the r8101 module per the instructions in the readme file. I next made sure that my modifications from yesterday to the /etc/sysconfig/network/ifcfg-eth0 were still there, and they were. They read: DEVICE='eth0' BOOTPROTO='dhcp' ONBOOT='yes' Voila, the network card connects to the internet as soon as the computer boots up. Thanks to everyone who has helped me yesterday and today to get to a solution to this problem. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org