The incorrect module is detected and loaded, unfortunately this bug has
existed for around 4+ years now.
Currently does not work on Ubuntu 11.04 (GNU/Linux 2.6.38-8-server
x86_64)
These are the same bug:
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/141343
r8169 does not work properly on 2.6.32-27-generic #49-Ubuntu SMP x86_64
GNU/Linux
Drops connection constantly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/221499
Title:
RTL8111/8168B does not
This bug is still occurring in Ubuntu 10.10 pre-release.
dmesg : http://pastebin.com/2Tz65xT6
lspci -t : http://pastebin.com/ZN8WuJnU
lspci -vvvnn : http://pastebin.com/zWMm4KCi
dmidecode : http://pastebin.com/krKserBN
--
RTL8111/8168B does not work in Hardy
** Changed in: linux (Ubuntu)
Status: Fix Released = Incomplete
** Changed in: linux (Ubuntu)
Status: Incomplete = Fix Released
--
RTL8111/8168B does not work in Hardy
https://bugs.launchpad.net/bugs/221499
You received this bug notification because you are a member of Ubuntu
As I wrote in here I had this Bug in Ubuntu 8.04 and 8.10 ALPHA. Since I
installed the official 8.10 release the bug disappeared for me. After I
installed 8.10 from CD my realtek wired lan adapter works out of box.
--
RTL8111/8168B does not work in Hardy
https://bugs.launchpad.net/bugs/221499
After all, this may be a motherboard bios configuration issue. I own a
Asrock ALiveDual-eSATA2 [1] : with the last bios update (version 1.40,
changelog Modify code for PCI function. [2]), it seems the issue
disappeared with ubuntu 8.10. This won't explain why the device worked
with different
I also own the Asrock ALiveDual-eSATA2 and i haven't problems with
kubuntu 8.10, but i had with kubuntu 8.04
--
RTL8111/8168B does not work in Hardy
https://bugs.launchpad.net/bugs/221499
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
2008/12/18 sfikas sfika...@yahoo.gr:
I also own the Asrock ALiveDual-eSATA2 and i haven't problems with
kubuntu 8.10, but i had with kubuntu 8.04
Nice to hear: I had problems with ubuntu 8.04 me too. I should test it
with the newer bios, to see if this fixed the problem or something
changed
2008/12/18 Francesco Pretto cez...@gmail.com:
I had problems with ubuntu 8.04 me too. I should test it
with the newer bios, to see if this fixed the problem or something
changed in ubuntu between 8.04 - 8.10. Will do it later.
Nope, the newer bios didn't fixed the ethernet in ubuntu 8.04.1
I went back and tested Fedora 10 and it was only wifi that worked so
they have the same problem.
The solution I found here is to set kernel parameter: pci=nomsi
which makes the network to function.
--
RTL8111/8168B does not work in Hardy
https://bugs.launchpad.net/bugs/221499
You received this
I can confirm this bug on my HP Pavilion DV7-1120EO.
The hard fix described in:
https://bugs.launchpad.net/ubuntu/+bug/208012
is not acceptable. How do I follow that procedure without a working network?
In order to compile I need to apt-get linux-headers (or whatever) but this is
impossible.
I don't agree that it is an acceptable solution to have to download and
compile your own driver, which I suppose will have to be redone for
every kernel update that is released.
The r8169 driver should normally be able to handle the r8168 interface,
which it does fine in Gutsy.
--
RTL8111/8168B
Problem solved with this guide:
https://bugs.launchpad.net/ubuntu/+bug/208012
(this is the same solution that was proposed by dariosicily on this site)
The Problem is a r8168 ethernet device is correctly found but the r8169
driver gets loaded, a driver that cannot handle the r8168 chip.
The
I am having this problem on BOTH freshly installed Ubuntu 8.04.1 AND a
freshly installed Ubuntu 8.10 Alpha 5. (both installed form the
corresponding normal 32 bit live CD). So from my point of view this bug
is NOT fixed.
It even seems to get stranger on the Alpha 5 instead better.
I bought a new
I'm having this problem and I just tried the pci=nomsi fix, but
unfortunately it doesn't work :-(
My wired network worked until two days ago and then it suddenly stopped
working with this exact problem. Has an update been sent out which might
introduce this problem? And is a fix forthcoming in
Hey guys, just to follow up.
Has there been a fix for this bug yet?
Im having the same problem here. What has everybody done as a temporary
resolve?
--
RTL8111/8168B does not work in Hardy
https://bugs.launchpad.net/bugs/221499
You received this bug notification because you are a member of
Ciao,
I did solve the problem follpwing the procedure you can read right above, the
original guide is in italian but if you need I can post something more accurate
in english.
It's been a while now I don't suffer the bug anymore.
Dario
--
RTL8111/8168B does not work in Hardy
Hello,
just to comunicate that I apparently solved the issue, installing module r8168
replacing r8169.
I followed a guide to download relevant module, unfolded it in my home
directory, and gave codes :
cd /home/dario/r8168-8.008.00
make clean modules
make
make install
depmod -a
insmod
Guys, just to alert that the bug is not solved, even with the pci=nomsi
procedure. As a matter of fact, I've been playing a bit with emerald,
now everything works fine but my internet connection I'm writing
thru Vista now, after 4 or 5 attempts to get connected by Ubuntu The
gedit still
That is not much to work with. Please gather the output of these comands:
dmesg
lspci -t
sudo lspci -vvnn
sudo dmidecode
Put them somewhere you can access with network and post them here.
--
RTL8111/8168B does not work in Hardy
https://bugs.launchpad.net/bugs/221499
You received this bug
Ok, sorry :
[EMAIL PROTECTED]:~$ lspci -t
-[:00]-+-00.0
+-01.0-[:04]00.0
+-1a.0
+-1a.1
+-1a.7
+-1b.0
+-1c.0-[:03]--
+-1c.2-[:02]00.0
+-1d.0
+-1d.1
+-1d.2
and the dmidecode one, don't know how to do it in one shot
** Attachment added: sudo dmidecode
http://launchpadlibrarian.net/16431901/sudo%20dmidecode
--
RTL8111/8168B does not work in Hardy
https://bugs.launchpad.net/bugs/221499
You received this bug notification because you are a
Using pci=nomsi is not a real solution.
Agreeed. Following are output of the commands you pointed.
--
RTL8111/8168B does not work in Hardy
https://bugs.launchpad.net/bugs/221499
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: lspci -t
http://launchpadlibrarian.net/16378383/lspci-t
--
RTL8111/8168B does not work in Hardy
https://bugs.launchpad.net/bugs/221499
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Attachment added: sudo dmidecode
http://launchpadlibrarian.net/16378379/dmidecode
--
RTL8111/8168B does not work in Hardy
https://bugs.launchpad.net/bugs/221499
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Attachment added: sudo lspci -vvnn
http://launchpadlibrarian.net/16378388/lspci-vvnn
--
RTL8111/8168B does not work in Hardy
https://bugs.launchpad.net/bugs/221499
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Thank you Francesco. Just to be bullet proof, your network works with the nomsi
option but not without.
And just as a bit more information from my side: the high IRQ number is not a
problem but just an indication that a device is using MSI instead of normal
interrupts. Which is not bad. You
** Attachment added: Text File
http://launchpadlibrarian.net/16386387/Text%20File
--
RTL8111/8168B does not work in Hardy
https://bugs.launchpad.net/bugs/221499
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
2008/7/29 Stefan Bader [EMAIL PROTECTED]:
Thank you Francesco. Just to be bullet proof, your network works with the
nomsi option but not without.
works with pci=nomsi, don't works without
The problem seems to be either the device (or some versions of that) or the
board which indicate with
Sorry if this is late but in response to Stefan asking for some diagnostic
output here's the output from sudo
dmidecode, lspci -t and sudo lspci -vvnn on my machine.
At this point I must also point out that I've temporarily installed a
borrowed LAN card (D-Link RTL8139 so I can use my network.
If that is no coincidence. This seems to be the common setup:
00:13.0 PCI bridge [0604]: ALi Corp. PCI Express Root Port [10b9:524d]
02:00.0 RTL8111/8168B PCIE Gb Ethernet ctrl. [10ec:8168] (rev 01)
SUB: ASRock Incorporation Unknown device [1849:8168]
Now the question
In response to Stefan, these are the outputs of those 3 commands in
kubuntu 8.04 with kernel from gutsy (2.6.22.14), where the problem
doesn't exist. Hope that this will help...
** Attachment added: Text File_gutsy
http://launchpadlibrarian.net/16412080/Text%20File_gutsy
--
RTL8111/8168B
Hi guys, I'm one more admist those who struggle with this bug
exactly the same problem, and the noly solution seems to be using Vista
and just silly playing with ubuntu till the enw version comes out
if you get to an end with it please let me know I'm so
disapopinted.
--
Something to try: pci=nomsi as a boot option
This might be a case where the card/bus claim to be able to use msi but
fail to do in reality.
--
RTL8111/8168B does not work in Hardy
https://bugs.launchpad.net/bugs/221499
You received this bug notification because you are a member of Ubuntu
Bugs,
pci=nomsi seems to work.
--
RTL8111/8168B does not work in Hardy
https://bugs.launchpad.net/bugs/221499
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Hey guys. I followed the instructions from http://forum.ubuntu-
it.org/index.php/topic,199308.0.html
setting pci=nomsi.
Apparently it's working, I'll keep monitoring
This should be solved, and sorry for my complaints
A big thanks anyway !
--
RTL8111/8168B does not work in
2008/7/28 Stefan Bader [EMAIL PROTECTED]:
Something to try: pci=nomsi as a boot option
This might be a case where the card/bus claim to be able to use msi but
fail to do in reality.
Eventually an help from a dev! (sorry Kjell, but I don't think your
playing with launchpad helped in solving
Using pci=nomsi is not a real solution. As many as there are with
problems, there are probably more that have none and would like this
enabled. But yes you all can help. As it seems to be certain
combinations of hardware that cause problems information needed (and a
bit of time to think about a
This is not a forum, but a bugtracker. For discussing please use the
ubuntuforums [1] or the mailinglists [2].
To repeat it: Fix released means that this issue does not occur in
intrepid anymore. Nominated for hardy means that this is still a issue
in hardy and someone (me included!) wants to see
For the record: Just using the sourcecode of the r8169 module in 2.6.26
and compiling it with the 2.6.24 kernel did not help.
--
RTL8111/8168B does not work in Hardy
https://bugs.launchpad.net/bugs/221499
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Kjell, you pointed out how to nominated bugs using the SRU procedure and
ironically you were the one to nominate this one for Hardy :)
Let's hope for a fix...just to repeat it for the umpteenth time: this is
*regression* . Gutsy worked flawlessly, as gentoo 2008.0, with a close kernel
(slightly
I am in a better situation than the others because i use kubuntu hardy
which is not an LTS edition, so i can wait for the kubuntu 8.10. But i
have to agree with the ubuntu users and their complaints, because ubuntu
suppose to be an LTS edition and for them is completely useless. So this
problem
So let me get this right. The bug is in the Hardy Kernel and the fix is to use
a new kernel from an unstable release? May be we should change it from LTS
to LTS except RTL8111/8168 users. I am sorry if I sound ironic but I was
waiting for Hardy LTS so that I could settle on one version for
Agreed with Mark, as this is clearly a regression. Ubuntu 7.10 worked
and Gentoo 2008 (has kernel 2.6.24) works.
--
RTL8111/8168B does not work in Hardy
https://bugs.launchpad.net/bugs/221499
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Mark, feel free to extract a patch which fixes this issue and provide it
as a debdiff, or wait until this bug is brought to attention to the
developers and they have an idea about how to fix this. The SRU
procedure does *not* say that we backport the whole 2.6.26 kernel, but
it says that we
I'm sorry but I have to agree with Mark that this is very poor. For me
this bug makes my machine unusable as I either have to take out my PCI
audio card so I can network with a PCI card or I can use the audio card
but have no networking (not room for both as the audio card has a
daughter card).
Confirmed. I may have further information: first, the card works
perfectly with Ubuntu 7.10.
The card binds to strange IRQs in 8.04 (where it's completely
unfunctional). This is from /proc/interrupts in 8.04:
...
220: 0 0 PCI-MSI-edge eth0
...
IRQ 220??? Isn't this
** Attachment added: /proc/interrupts from livecd ubuntu 7.10, eth0 works
http://launchpadlibrarian.net/16242159/interrupts-7.10
--
RTL8111/8168B does not work in Hardy
https://bugs.launchpad.net/bugs/221499
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Changed from Fix Released to Confirmed. Backporting 2.6.26 is not an
option for an LTS release!
** Changed in: linux (Ubuntu)
Status: Fix Released = Confirmed
--
RTL8111/8168B does not work in Hardy
https://bugs.launchpad.net/bugs/221499
You received this bug notification because you are
I am closing it because the bug has been fixed in the latest development
version of Ubuntu - the Intrepid Ibex.
If you need a fix for the bug in previous versions of Ubuntu, please do
steps 1 and 2 of the SRU Procedure [1] to bring the need to a
developer's attention.
[1]:
I can also confirm this problem with tis card at kubuntu hardy. Just see this:
https://bugs.launchpad.net/ubuntu/+bug/240865
p.s I didn't know that there was a post about this problem, so i made
one also
--
RTL8111/8168B does not work in Hardy
https://bugs.launchpad.net/bugs/221499
You received
I backported the current 2.6.26-2.6 kernel to hardy and the network card
works correctly.
** Changed in: linux (Ubuntu)
Status: Confirmed = Fix Released
--
RTL8111/8168B does not work in Hardy
https://bugs.launchpad.net/bugs/221499
You received this bug notification because you are a
** Description changed:
Ubuntu Hardy final release. My NIC RTL8111/8168B does not receive an IP
address. After starting the computer, icon of the NetworkManager is
animated. When it stops the wired network is reported as connected but
there are all zeros (IP address, gateway, etc.) I
2.6.24-19.33 does not work either. Will try to test 2.6.26 as soon as
possible.
** Description changed:
Ubuntu Hardy final release. My NIC RTL8111/8168B does not receive an IP
address. After starting the computer, icon of the NetworkManager is
animated. When it stops the wired network is
I can only add that I tried the recent Fedora 9 and OpenSuSE 11 releases
with 2.6.25 kernel and this network card worked correctly.
--
RTL8111/8168B does not work in Hardy
https://bugs.launchpad.net/bugs/221499
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Description changed:
Ubuntu Hardy final release. My NIC RTL8111/8168B does not receive an IP
address. After starting the computer, icon of the NetworkManager is
animated. When it stops the wired network is reported as connected but
there are all zeros (IP address, gateway, etc.) I
Marking as high importance as it is A problem with an essential
hardware component
** Tags added: regression
** Changed in: linux (Ubuntu)
Importance: Medium = High
--
RTL8111/8168B does not work in Hardy
https://bugs.launchpad.net/bugs/221499
You received this bug notification because you
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Ubuntu Kernel Team (ubuntu-kernel-team)
--
RTL8111/8168B does not work in Hardy
https://bugs.launchpad.net/bugs/221499
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Just to say that having just managed to install the 2.6.24-18 kernel
networking still doesn't work. I've also tried compiling Realteks
driver myself but this fails with shed loads of compilation errors
(function template mismatches plus missing constants)
So I can still only boot this box using
I too am unable to use networking with Hardy (kernel version 2-6-24-17)
on my machine which features an Asrock AliveDual-eSATA2 motherboard with
a Realtek RTL8111B/RTL8111C on board LAN controller.
However this hardware works fine if I boot from either a Feisty CD, a
Gutsy CD or a Knoppix 5.1 CD.
Hi
I would just like to add I have the same problem. In searching the bug
reports I have spotted more then one bug report that could be identical.
I have tried with kernels 2.6.24-16 and 2.6.24-17 with no success. The
gusty kernel (2.6.22-16) worked but I could not load the Nvidia graphics
In Hardy 8.04 kernel 2.6.24 Same chipset and same symptomsLAN receives
address alone ip some times and to every start of the PC once it works and once
no..
with live cd of 7.10 gutsy does not works .. :(
Good work to resolve !!
:)
--
RTL8111/8168B does not work in Hardy
I can confirm this.
This card worked in Feisty/Gutsy on this computer, but not in Hardy. Seems to
be related to the 2.6.24 kernel:
- When booting using the latest SystemRescueCD, choosing kernel 2.6.24, the
card does _not_ work (as in Hardy)
- When booting using the latest SystemRescueCD,
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
--
RTL8111/8168B does not work in Hardy
https://bugs.launchpad.net/bugs/221499
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Can confirm this on my friend's system. The same chipset, the same
symptoms: works in 2.6.22, does not work in 2.6.24. I'm working on
gathering the information meantioned in the KernelTeamBugPolicy.
** Changed in: linux (Ubuntu)
Status: New = Confirmed
--
RTL8111/8168B does not work in
** Attachment added: lspci-vvnn.log
http://launchpadlibrarian.net/13961116/lspci-vvnn.log
--
RTL8111/8168B does not work in Hardy
https://bugs.launchpad.net/bugs/221499
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Attachment added: dmesg.log
http://launchpadlibrarian.net/1396/dmesg.log
--
RTL8111/8168B does not work in Hardy
https://bugs.launchpad.net/bugs/221499
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Attachment added: version.log
http://launchpadlibrarian.net/13961108/version.log
--
RTL8111/8168B does not work in Hardy
https://bugs.launchpad.net/bugs/221499
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Attachment added: uname-a.log
http://launchpadlibrarian.net/13961103/uname-a.log
--
RTL8111/8168B does not work in Hardy
https://bugs.launchpad.net/bugs/221499
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Changed in: linux (Ubuntu)
Sourcepackagename: None = linux
--
RTL8111/8168B does not work in Hardy
https://bugs.launchpad.net/bugs/221499
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
70 matches
Mail list logo
