realtek 8168 driver issue

[magner]

Hi phenigma,

Thank you very much for the information. Sorry I have taken so log to follow up your advise. I was having trouble getting onto web admin and after 3 different linuxmce mirrors have finally get my system up and running.

I followed your instructions, managed to download the file from the web site you suggested, tar, make, into net folder but still no connection.

I have also tried swapping eth 0 and eth1 in the web admin network settings. Now the onboard NIC is external eth1. I have plugged my internet cable into the onboard NIC and cannot connect to the net.

I have also tried disabling the firewall through web admin settings, still no connection...

Sorry I missed the 8169 file you uploaded. Will it be possible to make it available again.

Thanks for everything.

Dan

[phenigma]

The files look like they're still attached to my posts.  You should be able to grab them.  You should make sure your 8139 card/driver are not interfering.

You should get the ethernet cards working in kubuntu before you attempt to install LMCE otherwise you may not get a connection through the cards.

J.

[purps]

Sorry for my lack of replies, Dan. My core decided to destroy itself with no MDs or orbiters working, so I am having a week or so away from it for the sake of my mental health.

Cheers,
Matt.

[phenigma]

Sorry for my lack of replies, Dan. My core decided to destroy itself with no MDs or orbiters working, so I am having a week or so away from it for the sake of my mental health.

Ahh...  the ol' blew up the core mental health break...  I have taken a few.   ;-)

J.

[purps]

Ahh...  the ol' blew up the core mental health break...  I have taken a few.   ;-)

J.

Yeah I have just given up smoking as well, which made it so much more enjoyable.

[phenigma]

Hi phenigma,

Thank you very much for the information. Sorry I have taken so log to follow up your advise. I was having trouble getting onto web admin and after 3 different linuxmce mirrors have finally get my system up and running.

I followed your instructions, managed to download the file from the web site you suggested, tar, make, into net folder but still no connection.

Dan, good to see you're still puligging away at it.  To make things easier all around I recommend you start from scratch and use the drivers I provided for now.

To avoid any conflicts between cards I suggest that you proceed as follows:

Remove your 2nd NIC from the machine.
Do a fresh install of kubuntu from a snapshot dvd.
Put the 8168 AND the 8169 driver I provided in earlier posts in the drivers/net directory. 
You will have to use the 8169 driver I posted or blacklist the 8169 driver that kubuntu provides. (They will conflict).
Reboot your machine.
Your NIC should be detected by kubuntu and work in kubuntu at this point.
If it doesn't work then you should not proceed any further.  Stop here and get this NIC to work before proceeding.

Once the onboard NIC is working shut down the machine and install your 2nd NIC.
Boot the machine and, if the drivers are correct for the 8139, your 2nd NIC should also be active.
If your 8139 doesn't get detected properly you may need to DL & build newer drivers for it as well (I have no experience with the 8139).

Don't proceed with installing LMCE until both NICs are functioning and working in kubuntu.

Let us know how you make out.

J.

[phenigma]

Yeah I have just given up smoking as well, which made it so much more enjoyable.

I think I started smoking from my ears at that point.

J.

[purps]

Dan, good to see you're still puligging away at it.  To make things easier all around I recommend you start from scratch and use the drivers I provided for now.

To avoid any conflicts between cards I suggest that you proceed as follows:

Remove your 2nd NIC from the machine.
Do a fresh install of kubuntu from a snapshot dvd.
Put the 8168 AND the 8169 driver I provided in earlier posts in the drivers/net directory. 
You will have to use the 8169 driver I posted or blacklist the 8169 driver that kubuntu provides. (They will conflict).
Reboot your machine.
Your NIC should be detected by kubuntu and work in kubuntu at this point.
If it doesn't work then you should not proceed any further.  Stop here and get this NIC to work before proceeding.

Once the onboard NIC is working shut down the machine and install your 2nd NIC.
Boot the machine and, if the drivers are correct for the 8139, your 2nd NIC should also be active.
If your 8139 doesn't get detected properly you may need to DL & build newer drivers for it as well (I have no experience with the 8139).

Don't proceed with installing LMCE until both NICs are functioning and working in kubuntu.

Let us know how you make out.

J.

I have a Realtek RTL-8139/8139C/8139C+ and it worked out of the box for me.

Cheers,
Matt.

[magner]

Hi folks,

I have just

Stripped the PCI NIC out of my core.
Reformatted PC.
Reinstalled Kubuntu
tested card by trying to connect to the internet . no joy...

Copied r8168 AND r1869 into the /lib/modules/2.6.27-17-generic/kernel/drivers/net folder

Just to confirm the method I used to copy r8168 and 9 was:

 "cp r8169.file.location  /lib/modules/2.6.27-17-generic/kernel/drivers/net"

I checked the r8169 file before and after with nano. the file you supplied J has a lot more lines. can confirm the r8169 file was succussfully copied.

Restarted PC tested internet connection. still no joy.

Followed method of blaclisting r8169 of :

added r8169 to blacklist
update-initramfs -k all -u
rmmod r8169

Restarted PC still no joy.

Recon I must have a dud onboard NIC.

Mat I feel your pain with having to go through the entire reformat route...
I am fresh as fresh can be with the process of reinstalling. if there are any tasks you might be rusty on let me know.

Cheers Lads
 
Dan

p.s just to confirm when I  ifconfig

it shows me an eth0 connection, so the pc is recognizing the card.

[phenigma]

Just to confirm the method I used to copy r8168 and 9 was:

 "cp r8169.file.location  /lib/modules/2.6.27-17-generic/kernel/drivers/net"

Okay, the files should be 'r8169.ko' and 'r8168.ko' not 'r8169.file.location', can you confirm that?  And yes, the file would appear to have more 'lines' when viewed in nano.  Instead of using nano to compare file sizes you can use the 'ls' command.  Type 'ls -l' at a command prompt to get a listing of files in the current directory and it will show you exact file sizes counted in bytes, among other things.  Try 'ls --help' or 'man ls' for more information on using ls for file listings, it's very handy.

Back to the issue at hand:
When you plug the ethernet cable in to your on-board NIC do you see the LEDs light up next to the connector?

Have you tried a different Ethernet cable?
I have a cable that works with 100Mb cards but not 1000Mb cards (damaged pair in the cable).

J.

[magner]

Hi J,

Thank you for the tip on ls, given me food for thought there. Next job on my list of many is to learn the power of the letters and signage after commands. The joys of being a newbie...    

I can confirm r8168.ko and r8169.ko files.

Yes the LED lights up.

I have checked the ethernet switch by connecting switch to my wireless sky broadband router with an ethernet cable, then connecting my laptop to 1 of the 5 ports on the switch with a 2nd ethernet cable. I receive an internet connection.

The cable I use connects to my laptop which has gigbit ethernet and supplies internet connection no problem. Have tried a 2nd cable, all good.

Just want to make sure I have explored all options from command line with making sure everything is working ok.

Is there any other command results we can look at: 

lshw -C Network
ifconfig
lspci -nn
sudo dhclient eth0

Cheers
Dan

[phenigma]

Most commands followed by '--help' will show you all the usage methods.  man is your friend as well it will show you 'Manual' pages relating to the command/software you specify.

What is the result of the 'dhclient' command?

Do you have a dhcp server active on your router to provide an IP?  I assume you can connect other devices and they receive an IP address properly.

Have you tried setting a static IP (on your local subnet) through kubuntu?

J.

[magner]

Alright mate,

yea dhcp is active on my router.

lshw -C Network

*-network UNCLAIMED
       description: Ethernet controller
       product: RTL8111/8168B PCI Express Gigabit Ethernet controller
       vendor: Realtek Semiconductor Co., Ltd.
       physical id: 0
       bus info: pci@0000:01:00.0
       version: 06
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress msix vpd bus_master cap_list
       configuration: latency=0
  *-network DISABLED
       description: Ethernet interface
       physical id: 1
       logical name: pan0
       serial: 82:d0:a2:f0:85:3f
       capabilities: ethernet physical
       configuration: broadcast=yes driver=bridge driverversion=2.3 firmware=N/A link=yes multicast=yes

 ifconfig

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:20 errors:0 dropped:0 overruns:0 frame:0
          TX packets:20 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1000 (1000.0 B)  TX bytes:1000 (1000.0 B)

 dhclient eth0

Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

SIOCSIFADDR: No such device
eth0: ERROR while getting interface flags: No such device
eth0: ERROR while getting interface flags: No such device
Bind socket to interface: No such device

cheers
Dan

[magner]

I notice using lshw -C Network it states version 6. While Mat's lshw -C Network states version 3. I wonder if the difference in versions mean the need for different drivers?

Also the obvious of ifconfig not showing an interface connection for eth0.

Also these are the steps I took through terminal:
                              
                                          
   13  cd /home/daniel/Documents                                  
   14  ls                                                        
   15  tar xvf r8169.tar.bz2                                      
   16  ls                                                        
   17  nano r8169.ko                                                                  
   20  cp /home/daniel/Documents/r8169.ko /lib/modules/2.6.27-17-generic/kernel/drivers
   21  cd                                                                              
   22  cd /lib/modules/2.6.27-17-generic/kernel/drivers                                
   23  ls
   24  nano r8169.ko
   25  ifconfig
   26  cp /home/daniel/Documents/r8168.ko /lib/modules/2.6.27-17-generic/kernel/drivers
   27  cd /lib/modules/2.6.27-17-generic/kernel/drivers
   28  ls
   31  cd /etc
   33  cd modprobe.d
   34  ls
   35  nano blacklist
   36  update-initramfs -k all -u
   37  rmmod r8169

Just incase there is user error.

cheers

just noticed I copied file in drivers folder not net folder.

watch this space.....

[phenigma]

If you open the driver files with nano and save them when you exit you could alter the driver so it doesn't function.  Don't open the .ko files with nano.  nano is for editing text files only.

This is from mine:

lshw -C Network

Code: [Select]

*-network
       description: Ethernet interface
       product: RTL8111/8168B PCI Express Gigabit Ethernet controller
       vendor: Realtek Semiconductor Co., Ltd.
       physical id: 0
       bus info: pci@0000:01:00.0
       logical name: eth0
       version: 06
       serial: e0:cb:4e:ce:ce:28
       size: 1GB/s
       capacity: 1GB/s
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=r8168 driverversion=8.019.00-NAPI duplex=full ip=10.10.42.101 latency=0 link=yes module=r8168 multicast=yes port=twisted pair speed=1GB/s

Hmm, it looks like it's not associating your card with the driver, notice the driver= and module= parameters in configuration on mine.   Notice my version is 06.  Can you post the output of 'lspci -nn' (two n's) and 'dmesg | grep -i eth'.

J.