Sign in with
Sign up | Sign in
Your question

Need help installing Realtek LAN driver for Ubuntu 10.10 64bit please

Last response: in Linux/Free BSD
Share
February 4, 2011 6:52:53 PM

Hello,

I'm new to Linux, trying to self learn a new OS and have 10.10 64bit installed with the help of iJack but apparently I need a Linux driver for my motherboards Realtek LAN ethernet. I can't access internet when in Ubuntu. Cox Communications and I narrowed it down to a driver. I have the driver but I don't know the terminal commands or how to use the text editor or whatever I have to do. A walk-through or a link showing me the process would be great if possible. Thank you.

Cyrixx

PS Any good books to pick up for learning Linux?
a b 5 Linux
February 4, 2011 7:17:34 PM

What Realtek NIC is it? And what is the name of the file that you have got? Normally you have to compile new device drivers as modules; they tend to be supplied as shell scripts that you run with a command like:

sudo sh <filename>

but, depending upon the type of file you may need to uncompress or extract it first (if so it will end in an extension like .tar, .tar.bz2, .tar.gz). Often they come with a README file that describes what needs to be done.
m
0
l
February 4, 2011 7:55:44 PM

Ijack said:
What Realtek NIC is it? And what is the name of the file that you have got? Normally you have to compile new device drivers as modules; they tend to be supplied as shell scripts that you run with a command like:

sudo sh <filename>

but, depending upon the type of file you may need to uncompress or extract it first (if so it will end in an extension like .tar, .tar.bz2, .tar.gz). Often they come with a README file that describes what needs to be done.


The Realtek NIC is a onboard chip on my Gigabyte GA-790FXTA-UD5 mobo. The file is .tar.bz2 but is also extracted. I have copies of both on on USB flash drive and on my desktop within Ubuntu 10.10. The extracted file folder name is: r8168-8.021.00 within the file folder are 4 things: a folder named SRC, autorun.sh, makefile, readme. i tried the readme but it's foreign to me.

Cyrixx
m
0
l
Related resources
a b 5 Linux
February 4, 2011 8:09:03 PM

At a guess I would say that you need to stry the command:

sudo sh autorun.sh

from the directory that the folder and those 3 files are in. This should compile and install the driver module. It's possible that it might throw up some errors if you haven't got the appropriate compilers and headers installed, but try that as a starter.

Having said all that, I've found a long thread here that discusses problems with Realtek NICs and Ubuntu 10.10; it seems to indicate that the card should be supported as is, i.e. that the driver is already present, but there are certain problems with it. Have a read of it and see if any of the suggestions help you.
m
0
l
February 4, 2011 8:22:38 PM

Ijack said:
At a guess I would say that you need to stry the command:

sudo sh autorun.sh

from the directory that the folder and those 3 files are in. This should compile and install the driver module. It's possible that it might throw up some errors if you haven't got the appropriate compilers and headers installed, but try that as a starter.

Having said all that, I've found a long thread here that discusses problems with Realtek NICs and Ubuntu 10.10; it seems to indicate that the card should be supported as is, i.e. that the driver is already present, but there are certain problems with it. Have a read of it and see if any of the suggestions help you.


Hmm...should I go to Ubuntu 10.04 then or try Fedora?
m
0
l
a b 5 Linux
February 5, 2011 12:03:45 AM

ijack that thread is ANCIENT, from 2007...
That being said, im surprised that its having issues... that driver should be built into the kernel already... It is in arch linux anyway... as its a popular chipset.

Cyrixx please post the output of "lspci" and "lsmod"
m
0
l
February 5, 2011 12:16:48 AM

I'm using 2 of those boards plus numerous others with RealTek NICs and never had a problem (10.10, 10.04 and 9.04)

There are a few other issues with Ubuntu 10 and networking that are easy to fix once you isolate them. Both assume your computer at least sees the NIC but has network connection.
m
0
l
a b 5 Linux
February 5, 2011 7:03:10 AM

@skittle. It is indeed an old thread. But that doesn't necessarily mean that it is not worth trying some of the suggestions there - all it takes is a little time. What has the OP got to loose?
m
0
l
February 5, 2011 7:50:01 AM

skittle said:
ijack that thread is ANCIENT, from 2007...
That being said, im surprised that its having issues... that driver should be built into the kernel already... It is in arch linux anyway... as its a popular chipset.

Cyrixx please post the output of "lspci" and "lsmod"


As per your request here is the output for lspci and lsmod.

Lspci outputs the following.....

00:00.0 Host bridge: ATI Technologies Inc RD790 Northbridge only dual slot PCI-e_GFX and HT3 K8 part
00:02.0 PCI bridge: ATI Technologies Inc RD790 PCI to PCI bridge (external gfx0 port A)
00:04.0 PCI bridge: ATI Technologies Inc RD790 PCI to PCI bridge (PCI express gpp port A)
00:05.0 PCI bridge: ATI Technologies Inc RD790 PCI to PCI bridge (PCI express gpp port B)
00:07.0 PCI bridge: ATI Technologies Inc RD790 PCI to PCI bridge (PCI express gpp port D)
00:09.0 PCI bridge: ATI Technologies Inc RD790 PCI to PCI bridge (PCI express gpp port E)
00:0a.0 PCI bridge: ATI Technologies Inc RD790 PCI to PCI bridge (PCI express gpp port F)
00:0b.0 PCI bridge: ATI Technologies Inc RD790 PCI to PCI bridge (external gfx1 port A)
00:11.0 SATA controller: ATI Technologies Inc SB700/SB800 SATA Controller [IDE mode]
00:12.0 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller
00:12.1 USB Controller: ATI Technologies Inc SB700 USB OHCI1 Controller
00:12.2 USB Controller: ATI Technologies Inc SB700/SB800 USB EHCI Controller
00:13.0 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller
00:13.1 USB Controller: ATI Technologies Inc SB700 USB OHCI1 Controller
00:13.2 USB Controller: ATI Technologies Inc SB700/SB800 USB EHCI Controller
00:14.0 SMBus: ATI Technologies Inc SBx00 SMBus Controller (rev 3c)
00:14.1 IDE interface: ATI Technologies Inc SB700/SB800 IDE Controller
00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA)
00:14.3 ISA bridge: ATI Technologies Inc SB700/SB800 LPC host controller
00:14.4 PCI bridge: ATI Technologies Inc SBx00 PCI to PCI Bridge
00:14.5 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI2 Controller
00:18.0 Host bridge: Advanced Micro Devices [AMD] Family 10h Processor HyperTransport Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] Family 10h Processor Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] Family 10h Processor DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] Family 10h Processor Miscellaneous Control
00:18.4 Host bridge: Advanced Micro Devices [AMD] Family 10h Processor Link Control
01:00.0 VGA compatible controller: ATI Technologies Inc Juniper [Radeon HD 5700 Series]
01:00.1 Audio device: ATI Technologies Inc Juniper HDMI Audio [Radeon HD 5700 Series]
02:00.0 USB Controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 03)
03:00.0 IDE interface: Marvell Technology Group Ltd. Device 91a3 (rev 11)
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03)
05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03)
06:00.0 SATA controller: JMicron Technology Corp. JMB362/JMB363 Serial ATA Controller (rev 03)
06:00.1 IDE interface: JMicron Technology Corp. JMB362/JMB363 Serial ATA Controller (rev 03)
07:00.0 VGA compatible controller: ATI Technologies Inc Juniper [Radeon HD 5700 Series]
07:00.1 Audio device: ATI Technologies Inc Juniper HDMI Audio [Radeon HD 5700 Series]
08:0e.0 FireWire (IEEE 1394): Texas Instruments TSB43AB23 IEEE-1394a-2000 Controller (PHY/Link)

Lsmod outputs the following.......

xhci_hcd 58578 0
i2c_piix4 10047 0
soundcore 1240 1 snd
snd_page_alloc 8588 2 snd_hda_intel,snd_pcm
lp 10201 0
parport 37032 3 ppdev,parport_pc,lp
usbhid 42062 0
hid 84678 1 usbhid
radeon 906714 2
usb_storage 50372 2
ttm 68212 1 radeon
drm_kms_helper 32836 1 radeon
firewire_ohci 24679 0
firewire_core 54327 1 firewire_ohci
pata_jmicron 2771 0
ahci 21857 0
crc_itu_t 1739 1 firewire_core
libahci 26167 4 ahci
r8169 42222 0
mii 5261 1 r8169
pata_atiixp 4405 0
drm 206161 4 radeon,ttm,drm_kms_helper
i2c_algo_bit 6208 1 radeon
m
0
l
a b 5 Linux
February 5, 2011 8:06:04 AM

First thing to say is that Ubuntu is using the wrong driver (r8169 when it should be r8168); this is a Ubuntu bug. But, that driver should work - if not perfectly. HAve a look at this thread (don't worry, folks, this is a more recent thread).

You should be able to force the ethernet to work with the wrong driver. Do

sudo ifconfig

and report the output (it should show a section headed "eth0" and one headed "lo"). Here's what it looks like on my install:

eth0 Link encap:Ethernet HWaddr 08:00:27:34:7f:85
inet addr:192.168.1.160 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::a00:27ff:fe34:7f85/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:243 errors:0 dropped:0 overruns:0 frame:0
TX packets:65 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:17529 (17.5 KB) TX bytes:9260 (9.2 KB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:480 (480.0 B) TX bytes:480 (480.0 B)
m
0
l
February 5, 2011 7:19:52 PM

One more command in addition to the others is the output from:

dmesg

Its going to be a huge ammount of information, but in the lower third you should find something about realtek. Post that info here if you can find it. Don't post the whole output from dmesg however, its huge.
m
0
l
February 7, 2011 2:53:27 AM

someone19 said:
One more command in addition to the others is the output from:

dmesg

Its going to be a huge ammount of information, but in the lower third you should find something about realtek. Post that info here if you can find it. Don't post the whole output from dmesg however, its huge.


here is what i could find at the end of the output for the command: dmesg

[ 9.164221] type=1400 audit(1297051543.233:11): apparmor="STATUS" operation="profile_replace" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1259 comm="apparmor_parser"
[ 9.283899] r8169 0000:04:00.0: eth0: link down
[ 9.284565] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 9.312959] r8169 0000:05:00.0: eth1: link down
[ 9.313580] ADDRCONF(NETDEV_UP): eth1: link is not ready
[ 9.385650] vgaarb: device changed decodes: PCI:0000:07:00.0,olddecodes=io+mem,decodes=none:o wns=none
[ 9.385653] vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=none:o wns=io+mem
[ 10.063656] EXT4-fs (sdb5): re-mounted. Opts: errors=remount-ro,commit=0
[ 10.119416] EXT4-fs (sdb3): re-mounted. Opts: commit=0
[ 11.413057] hda-intel: IRQ timing workaround is activated for card #1. Suggest a bigger bdl_pos_adj.
[ 12.074890] EXT4-fs (sdb5): re-mounted. Opts: errors=remount-ro,commit=0
[ 12.076708] EXT4-fs (sdb3): re-mounted. Opts: commit=0
[ 12.460567] hda-intel: IRQ timing workaround is activated for card #2. Suggest a bigger bdl_pos_adj.
[ 28.607669] Intel AES-NI instructions are not detected.
[ 28.635254] padlock: VIA PadLock not detected.

Cyrixx
m
0
l
February 7, 2011 12:35:52 PM

That's good info, and it confirms that your loading the wrong driver and it isn't finding the link. Your machine undoubtedly has the correct driver, but I'm not an Ubuntu user and can't specifically say how to load the correct one. I'd suggest asking on the Ubuntu forums and check how to load the correct module (linux name for kernel driver).

Good luck.
m
0
l
February 7, 2011 1:21:43 PM

I got impatient and tried a different distro thinking maybe it would work better (Fedora) but now the boot loaders are conflicting I think because I get a error at boot screen saying no device found with a huge code then says grub rescue with a blinking cursor. Boot loader was on my c: drive with my main OS Win 7. Did I just nuke Win 7?

Cyrixx
m
0
l
February 7, 2011 2:36:52 PM

Not really, you should be able to repair the boot sector with your original install disk. Grub probably got interrupted during the install of Fedora. Fix win 7 then try the fedora install again.
m
0
l
September 7, 2011 12:08:30 AM

Cyrixx said:
I got impatient and tried a different distro thinking maybe it would work better (Fedora) but now the boot loaders are conflicting I think because I get a error at boot screen saying no device found with a huge code then says grub rescue with a blinking cursor. Boot loader was on my c: drive with my main OS Win 7. Did I just nuke Win 7?

Cyrixx


Fedora doesn't automatically recognize other operating systems to automatically add them to the GRUB list, so you have to edit them manually. So it's better to install Fedora first, then Ubuntu, because Ubuntu will automatically fix the GRUB.
m
0
l
a b 5 Linux
September 7, 2011 1:10:01 AM

I remember oh so long ago when I did that with Fedora Core 3.

Good times. No probs not.

Silly silly...
m
0
l
!