I am wondering if the patch described by "attikon (Ion)" is actually in
fact still working in Ubuntu 9.10? Can someone confirm or deny..thanks.
--
Ethernet (nVidia MCP55) not working [ gutsy, hardy, interpid ]
https://bugs.launchpad.net/bugs/136836
You received this bug notification because you a
Not as lucky as Black Silver, I still have this problem on Ubuntu 9.04 and 9.10
on a Asus P5N32-E SLI MotherBoard.
Hopefully the patch describe by "attikon (Ion)" is still working.
--
Ethernet (nVidia MCP55) not working [ gutsy, hardy, interpid ]
https://bugs.launchpad.net/bugs/136836
You receiv
I don't have the problem anymore. I've installed 9.10 a few days ago and
everything on that mainboard (including Front Mic) worked right out of the box
:)
Things I haven't tested yet are the surround output at the back as well as the
2nd network jack. I don't think there's any difference betwee
This problem is still relevant in Ubuntu 8.04 and Kubuntu 9.10. I am
using an Asus P5N32E Sli Plus Motherboard and the networks refuse to
work. I have to add an old networking card to access updates etc. Is
there any chance of a permanent fix appearing?
--
Ethernet (nVidia MCP55) not working [ gu
On a fresh installed 8.10, i had the same problem. Tried the same with
the msi=0 msix=0 but this didn't made any changes.
I decided to blame something else for this issue and so i started to
search on my 'Message too large' problem, which i was getting when using
'dhclient eth0'.
To solve my prob
I take back what I've said... things seem ok...
--
Ethernet (nVidia MCP55) not working [ gutsy, hardy, interpid ]
https://bugs.launchpad.net/bugs/136836
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-
I followed attikon's instructions step by step (twice), but when I
reboot, it doesn't work anymore, I have to do the manip' again (I'm on
Ubuntu 8.10 Interpid).
I have no idea what could be the issue here...
--
Ethernet (nVidia MCP55) not working [ gutsy, hardy, interpid ]
https://bugs.launchpad
Thanks a lot lad for posting and attikon for compiling this all together.
I've been trying for a long-long time to get my network working after suspend.
Finally it's working!!
--
Ethernet (nVidia MCP55) not working [ gutsy, hardy, interpid ]
https://bugs.launchpad.net/bugs/136836
You received t
##
Networking Solution for nVIDIA MCP55 Ethernet - Ubuntu 8.10 Interpid
##
Step 1, open a terminal.
a) become superuser
$ sudo su
b) remove forcedeth kernel module (it's the ethernet's driver)
# rmmod forcedeth
c
Hello friends,
Im new to this launchpad. I have similar problem, with Asus Motherboard,
and have been trying to fix it for so long. As few people has mentioned
in the forum, its really annoying to fix this problem. Ive tried alot,
and very very tired of it. Its really terrible, to switch between U
I agree that a mechanism for detecting functionality with different
values would be superior to the quirk workaround. I added that on the
assumption that this was a one-time problem which was caused by a BIOS
bug on the Asus P5N32-SLI Premium. Since different potentially related
occurrences have su
For people reading this bug report: I have a similar issue that only
happens after suspend:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/312144
For me networking works just fine, except for suspending, so I don't
think any defaults should be modified, unless those defaults would fix
the su
I confirm this problem with Ubuntu 8.10, 64 bit, on an EVGA motherboard
with an nforce 680i SLI chipset. The workaround using the forcedeth
parameters and update-initramfs works.
How about you chaps ship that as the default kernel parameter for that
module?
--
Ethernet (nVidia MCP55) not working
Thanks for your solution. It works by me too.
To Andreas Petlund: I have had the same network problem with an ASUS M2N-SLI
Deluxe motherboard.
Strange is that this problem came forward after upgrade ubuntu 8.10 and I
wasn't met it with 8.04.
I submit any aditional info what you need.
--
Etherne
After looking into the problem, I'm convinced that my problem (with the
P5N32-SLI Premium mobo), is caused by a buggy BIOS. I also have the same
PCI bridge and NIC on another Asus motherboard, where it works
flawlessly (for small and large data transfers). I have submitted a
kernel patch where msi
I was having problems with large data transfers. My PC's intergrated
ethernet port used to go down & come up in a few seconds by itself. The
solution given above resolved my problem. Though my hardware is
differnet, this seems to be a general issue with forcedeth drivers on
Ubuntu standard kerne
Thanks for the feedback. I'm primarily trying to find out if this is
P5N32-SLI-specific, so a clarification of the above question is: Are
there anybody (in addition to me) who still experiences the network
problems after upgrading to 2.6.27+ and has other motherboards than the
Asus P5N32-SLI Premiu
I have "286: 206342002 PCI-MSI-edge eth0".
My motherboard is gigabyte GA-M57SLI-S4 (because it allegedly can run
openbios, not that I've tried that).
Remember, all my problems were fixed by upgrading to the upstream-linux-
gregkh 2.6.27.
--
Ethernet (nVidia MCP55) not working [ gutsy, h
I got no suggestions/feedback when posting this question on the netdev-
list, but I have done some experimenting with msi disabling for affected
devices in order to produce a (preliminary) patch. What I would like to
know is if there are other motherboards than the Asus P5N32-SLI Premium
which are
I've tested the current development kernel (2.6.28-rc3) on my computer
(Asus P5N32-SLI Premium motherboard), and the problem is still present.
I can take this to the mailing lists to try to find a reasonable
solution.
--
Ethernet (nVidia MCP55) not working [ gutsy, hardy]
https://bugs.launchpad.n
I'm not sure how to install a new kernel on Ubuntu, so I'm afraid I
cannot provide you with more information in that regard. I will try and
read up a bit on how that's done this weekend, but I suspect it won't be
easy for a novice like me.
Unfortunately the command you gave only disabled the nm ap
For the MSI problem probably the best way to proceed would be to try out
the latest vanilla kernel and if that fails as well go and open an
upstream bug. Unfortunately MSI can break on various levels (IO-APIC -
pci bridge - card), so it can work for some and still fail for others.
The second probl
Hi, thanks for the speedy reply. I'm currently using a fresh install of
8.10, but it would still seek for network connection in vain.The "msi=0
msix=0 "fix still works. However, it appears that I'm suffering a memory
leak problem now, which may be related to the networkmanager. Please
refer to bug
This is not taken lightly but the original problem (MSI(X)) seemed to be
solved in more recent kernels and there was a work-around for the older
ones. By saying the problem is still there, it is not clear to me
whether it is the MSI problem. Can you use the driver with "msi=0
msix=0"?
--
Ethernet
Stefan Bader wrote on 2008-10-16: (permalink)
>Based on the last comment (and the previous ones that indicated this
has been improved in 2.6.27) I close this bug as fixed for Intrepid.
>For Hardy and Gutsy this has to be worked around by disabling MSI(X).
Nope, the problem is still there and t
Hi,
i have the same problem with the same motherboard (Asus P5N32-SLI Premium).
But the workaround does not work for me!
--
Ethernet (nVidia MCP55) not working [ gutsy, hardy]
https://bugs.launchpad.net/bugs/136836
You received this bug notification because you are a member of Ubuntu
Bugs, which
Just a recap of my experience to help anyone who is trying to figure out
whether the problem is fixed or not.
I had a problem which had similar or identical symptoms to the problems
other people reported. The problem happened reliably.
I did not try the workaround of passing "msi=0 msix=0".
I d
P.S. In case this isn't clear, a pretty good Next Step for someone who
wants to debug this problem might be to try the Linux-GregKH-official-
Linus-2.6.27.x kernel instead of the Ubuntu-2.6.27 kernel. I haven't
checked, but I presume that the Ubuntu kernel is not precisely the same
as the officia
Hi,
Jonathan Perryman also has this issue on Ubuntu 8.10.
Take a look at https://answers.launchpad.net/ubuntu/+question/49556 for
details.
Regards,
Mark Rijckenberg
--
Ethernet (nVidia MCP55) not working [ gutsy, hardy]
https://bugs.launchpad.net/bugs/136836
You received this bug notification
I just installed Ubuntu 8.10, and I'm afraid I have the same problem, so
this bug is not solved.
--
Ethernet (nVidia MCP55) not working [ gutsy, hardy]
https://bugs.launchpad.net/bugs/136836
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Based on the last comment (and the previous ones that indicated this has
been improved in 2.6.27) I close this bug as fixed for Intrepid. For
Hardy and Gutsy this has to be worked around by disabling MSI(X).
** Changed in: linux (Ubuntu Intrepid)
Status: Incomplete => Fix Released
--
Ethe
On Oct 16, 2008, at 10:05 AM, Matt Zimmerman wrote:
> It has been stated that this is expected to be fixed in 2.6.27, which
> would mean that it's fixed with Intrepid.
>
> Could someone affected by the bug either upgrade to Intrepid or boot
> from the live CD to test?
The problem has gone away fo
It has been stated that this is expected to be fixed in 2.6.27, which
would mean that it's fixed with Intrepid.
Could someone affected by the bug either upgrade to Intrepid or boot
from the live CD to test?
The ISOs are available at http://releases.ubuntu.com/8.10/
--
Ethernet (nVidia MCP55) no
kieron
I expect this is stating the obvious but just in case - There is a typo
in Stefan Bader's message it should read
/etc/modprobe.d/forcedeth
not
/etc/fmodprobe.d/orcedeth
FWIW - I made this change back on April 15th (See earlier post) on my
system and it has run fine ever since. IIRC kern
>As it is I forgot to mention I'm dual booting ubuntu and having booted into
>windows and back into ubuntu
> I now have an internet connection! Either that has significance of some kind
> or my problem is
>inconsistent and intermittent.
Right this can unfortunately happen both ways. One driver
Thanks for such a swift response Stefan, naturally I appreciate what you
say about working around broken and/or strange hardware and I'm grateful
people such as yourself work on and contribute to fixing things for
people like me - my concern was that Linux will always stay in the
shadows of windows
kieron: I'm sorry to hear you are going back to Windows. Good luck!
Everyone: I upgraded my kernel to the upstream Linus-Torvalds-official
2.6.27 release candidate, and the problem went away. I was getting the
problem reliably until then, so I'm pretty sure one of the several
forcedeth patches i
I can understand your disappointment but please take into account that in Linux
it is the geeks and the users that have to work around broken or strange
hardware while for other OS the vendors care more.
For your problem: you could check whether the network card is running in the
wrong mode by l
I appreciate your workaround Stefan, and it worked for me for a few
days, however today it doesn't, /etc/fmodprobe.d/orcedeth is still there
with the options line and I tried rebuilding the initramfs again but no
go.
The only thing that's changed in the interim is I installed turboprint
(surprise
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the
upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would
appreciate it if you could please test this newer 2.6.27 Ubuntu kernel.
There are one of two ways you should be able to test:
1) If you are comfortable
To get this settings permanent create (as root)
/etc/fmodprobe.d/orcedeth (or update /etc/modprobe.d/config). Add the
line:
options forcedeth msi=0 msix=0
and save. Then rebuild the initramfs with
update-initramfs -u -k $(uname -r)
--
Ethernet (nVidia MCP55) not working [ gutsy, hardy]
https:/
Sorry about this but im really confused! I get the temporary fix and do
the following every time I log on
sudo su
rmmod forcedeth
modprobe forcedeth msi=0 msix=0
/etc/init.d/networking restart
However I need a permanent fix. I tried to make this run every time I
log in (This is is stored in a pla
I have this consistently. It takes a few hours to trigger, typically,
but when it does it locks up my linksys router (presumably the Linux
workstation is sending packets at such a rate that it overloads the
linksys, I dunno, but if I unplug the ethernet cable then the linksys
router comes back to
It is sure there. I did not really fix it. I rather disabled a setting
by default. And that was not a good fix. Actually it would be great if
you or anybody else could provide me with some data (dmesg working/non-
working and the lvpci -vvnn output).
--
Ethernet (nVidia MCP55) not working [ gutsy
** Tags removed: needs-reassignment
--
Ethernet (nVidia MCP55) not working [ gutsy, hardy]
https://bugs.launchpad.net/bugs/136836
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
h
Hi again !
Just a little message to say that i upgraded to latest
linux-image-2.6.24-19-generic_2.6.24-19.36_i386.deb (so it overwrote yours) and
after a reboot the problem was here again.
Just to point the fact that the problem still exists in the latest
ubuntu kernel update.
Hope you will man
** Changed in: linux (Ubuntu Intrepid)
Assignee: Ubuntu Kernel Team (ubuntu-kernel-team) => Stefan Bader
(stefan-bader-canonical)
Status: New => Incomplete
--
Ethernet (nVidia MCP55) not working [ gutsy, hardy]
https://bugs.launchpad.net/bugs/136836
You received this bug notification
On a second thought I think this was wrong thinking. Seems there is code
to try to enable msi or msix later. It would be great if someone could
supply a dmesg log for the non-working case.
--
Ethernet (nVidia MCP55) not working [ gutsy, hardy]
https://bugs.launchpad.net/bugs/136836
You received t
That was the hope. ;-) There are several places where msi and msix come
into place. One is the definitions per hardware in forcedeth but I
noticed in the lscpi output os some of you that posted that there is a
msi and msix enabled flag for the pci bus. The question is whether for
those that would h
I tried commenting the line "options forcedeth msi=0 msix=0" in my
/etc/modprobe.d/option
After a reboot it works too and i have exactly the same output doing a
dmesg | grep forcedeth (or cat /var/log/syslog | grep forcedeth) and lspci -vvnn
--
Ethernet (nVidia MCP55) not working [ gutsy, hardy]
In response to Stefan Bader's post :
I tried your linux-image-2.6.24-19-generic_2.6.24-19.35smb2_i386.deb
When i boot up it worked but i have to say that i added "options forcedeth
msi=0 msix=0" to my /etc/modprobe.d/options
Do you want me to test without this line ?
Here is my dmesg | grep force
Does someone care to try the Hardy kernel at
http://people.ubuntu.com/~smb/bug136836? This is a first try so maybe
this does not work out. In any case if you test it, please submit your
lspci -vvnn info for the ethernet and the debug lines that get printed
for msi_enabled/msix_enabled.
--
Etherne
I had this problem in Hardy, if it's somehow been marked as something
that doesn't need to be fixed the person doing the classifying is a
fool.
Gutsy -> Hardy users see this as a regression (at least I did, my on
board nvidia MCP55 worked fine in Gutsy) - a reformat and lots of
fiddling around lat
The above fixes worked great, have an Asus P5N32-E SLI Plus motherboard.
It's too bad this problem cannot be fixed for only the machines that are
having the problem through a system update without breaking things for
working machines. If only it was a bug that was clearly at fault so
that the fix
There's no need to disable MSI for the whole kernel, one can fix this
applying appropriate flags to a forcedeth module (see comment #11).
--
Ethernet (nVidia MCP55) not working [ gutsy, hardy]
https://bugs.launchpad.net/bugs/136836
You received this bug notification because you are a member of Ub
Fallen-Angel: The most important tenant of the SRU process is 'cause no
regressions in the current release'. The fact that this issue is a
regression from Gutsy to Hardy only makes it elegible for SRU scrutiny.
In this case, I cannot guarentee that disabling MSI for all cases won't
cause regression
Hello,
i find this bug a very critical one, since new {linux,ubuntu} users won't
search deeper if their network interface don't work.
They won't search in the launchpad or in google for a fix.
They may continue using ubuntu even if some application doesn't work in the way
they want it to, thinkin
The Hardy alternate setup told me it can not configure my Ethernet (via
DHCP) but I had a working DHCP network connection after logging into the
fresh installation. Hardware is the same as in the first post.
--
Ethernet (nVidia MCP55) not working [ gutsy, hardy]
https://bugs.launchpad.net/bugs/13
and intrepid?
** Changed in: linux (Ubuntu Intrepid)
Status: Won't Fix => New
--
Ethernet (nVidia MCP55) not working [ gutsy, hardy]
https://bugs.launchpad.net/bugs/136836
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubunt
This bug does not qualify for an SRU fix. The workaround is well known,
though I agree that it may not be obvious to most users.
** Changed in: linux (Ubuntu)
Status: Triaged => Won't Fix
--
Ethernet (nVidia MCP55) not working [ gutsy, hardy]
https://bugs.launchpad.net/bugs/136836
You rec
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
--
Ethernet (nVidia MCP55) not working [ gutsy, hardy]
https://bugs.launchpad.net/bugs/136836
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I had the same problem with embedded nForce NVIDIA network controller.
The fix consisting in putting "options forcedeth msi=0 msix=0" in in the
interface file (and then "sudo update-initramfs -u") worked for me as well.
thank you :)
--
Ethernet (nVidia MCP55) not working [ gutsy, hardy]
https://
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
Assignee: Nanley Chery (nanoman) => Ubuntu Kernel Team (ubuntu-kernel-team)
--
Ethernet (nVidia MCP55) not working [ gutsy, hardy]
https://bugs.launchpad.net/bugs/136836
You received this bug notification because you are a memb
This became a problem for me on one system (of three) I upgraded to
Hardy. The 'options forcedeth msi=0 msix=0' fix seems to be working on
Hardy. Never had an issue that I am aware of on Gutsy involving
forcedeth.
I seem to be able to reproduce a loss of network (using synaptic, for
example) wit
This was a problem for me in Ubuntu 8.04. Spent a good four hours
looking at the problem and trying various fixes; the post by Tom was
extremely helpful, but in no way would I have figured it out on my own.
I agree with the above poster; regular users will not spend this amount
of time trying to fi
Yeap, the command by Tom works miracle.
I hope they can fix this bug soon, because a network problem simply stops
people from trying out Ubuntu (and the problem seems to apply in Kubutu as
well) because they can't access support online easily if the network is down.
Not everyone has the patience
interesting, this might be why I can't, for the life of me, seem to get the
network going.
I'm using Asus P5N32- SLI motherboard.
It is strange, because the network problem seems to fail only with recent
version of Ubuntu,
I found an old CD and it seems to work ok...
I will update more once I t
Confirming on Hardy beta; indeed, it's a kernel (actually, forcedeth
driver) bug. Forcedeth driver is known to fail for some reason if
Message Signalled Interrupts (MSI) are enabled.
lspci -v:
00:11.0 Bridge: nVidia Corporation MCP55 Ethernet (rev a2)
Subsystem: ASUSTeK Computer Inc. Unkno
Setting to linux - this is a kernel problem isn't it?
** Changed in: linux (Ubuntu)
Sourcepackagename: None => linux
--
Ethernet (nVidia MCP55) not working [ gutsy, hardy]
https://bugs.launchpad.net/bugs/136836
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This worked for me
Add the following line to /etc/modprobe.d/options
options forcedeth msi=0 msix=0
Then rebuild initramfs like this
sudo update-initramfs -u
and remove any stuff you added to /etc/rc.local
Reboot.
NOTE: if the update-initramfs bit goes wrong it could stop your system
from bo
** Summary changed:
- Ethernet (nVidia MCP55) is not working on Gusty Tribe 5
+ Ethernet (nVidia MCP55) not working [ gutsy, hardy]
** Tags added: needs-reassignment
** Tags removed: gibbon gusty tribe5 ubuntu
--
Ethernet (nVidia MCP55) not working [ gutsy, hardy]
https://bugs.launchpad.net/bu
71 matches
Mail list logo
