[Bug 175333] Re: first eth device gets new number on resume

2012-05-29 Thread Curtis Hovey
** Changed in: linux (Ubuntu) Assignee: Registry Administrators (registry) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/175333 Title: first eth device gets new number on resume

[Bug 175333] Re: first eth device gets new number on resume

2011-06-15 Thread Joni Katajamäki
** Changed in: linux (Ubuntu) Status: Incomplete => Opinion -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/175333 Title: first eth device gets new number on resume To manage notifications abo

[Bug 175333] Re: first eth device gets new number on resume

2009-07-27 Thread Leann Ogasawara
Just want to try to keep this report up to date. Care to test and confirm this issue remains with the latest development release of Ubuntu (ie Karmic). ISO CD images are available from http://cdimage.ubuntu.com/releases/ . -- first eth device gets new number on resume https://bugs.launchpad.net/b

[Bug 175333] Re: first eth device gets new number on resume

2009-04-08 Thread Ricardo Gomez
I'm having this problem with ubuntu jaunty: r...@ubuntu:~# dmesg | grep eth [4.691544] forcedeth: Reverse Engineered nForce ethernet driver. Version 0.61. [4.691952] forcedeth :00:0a.0: PCI INT A -> Link[LMAC] -> GSI 20 (level, low) -> IRQ 20 [4.691957] forcedeth :00:0a.0: se

[Bug 175333] Re: first eth device gets new number on resume

2009-01-15 Thread Leann Ogasawara
Has anyone been able to confirm with Intrepid? Thanks. ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- first eth device gets new number on resume https://bugs.launchpad.net/bugs/175333 You received this bug notification because you are a member of Ubuntu Bugs, which is s

[Bug 175333] Re: first eth device gets new number on resume

2008-08-29 Thread Leann Ogasawara
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

[Bug 175333] Re: first eth device gets new number on resume

2008-07-27 Thread Lars G. Hanson
Unfortunately the reverse byte-ordering problem of the MAC address after suspend is still present in Hardy (forcedeth driver), although perhaps not in its original form. If I suspend or hibernate the usual way, all is good. I need wake-on- lan, however, and the net card must therefore first be put

[Bug 175333] Re: first eth device gets new number on resume

2008-04-25 Thread Richard Jonsson
I would just like to point out that sam tygiers bug is not the same as mine, but related ofcourse. >From sam tygiers dmesg: [5.752349] forcedeth :00:0a.0: Invalid Mac address detected: 00:00:00:00:00:00 This card don't read an address at all, whereas my card got it backwards. The patch I

[Bug 175333] Re: first eth device gets new number on resume

2008-04-25 Thread sam tygier
** Attachment added: "70-persistent-net.rules" http://launchpadlibrarian.net/13895202/70-persistent-net.rules -- first eth device gets new number on resume https://bugs.launchpad.net/bugs/175333 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 175333] Re: first eth device gets new number on resume

2008-04-25 Thread sam tygier
after another suspend it changes again eth10 Link encap:Ethernet HWaddr 00:00:6c:6b:a4:b0 -- first eth device gets new number on resume https://bugs.launchpad.net/bugs/175333 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubunt

[Bug 175333] Re: first eth device gets new number on resume

2008-04-25 Thread sam tygier
** Attachment added: "lspci-vv.txt" http://launchpadlibrarian.net/13895039/lspci-vv.txt -- first eth device gets new number on resume https://bugs.launchpad.net/bugs/175333 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-b

[Bug 175333] Re: first eth device gets new number on resume

2008-04-25 Thread sam tygier
I am seeing this in hardy on an aspire 7520. after reboot eth8 Link encap:Ethernet HWaddr 00:1b:38:68:92:6c after suspend eth9 Link encap:Ethernet HWaddr 00:00:6c:2b:83:26 i will attach dmesg and lspci -vv ** Changed in: linux (Ubuntu) Sourcepackagename: None => linux -- first eth

[Bug 175333] Re: first eth device gets new number on resume

2008-04-25 Thread sam tygier
** Attachment added: "dmesg.txt" http://launchpadlibrarian.net/13895034/dmesg.txt -- first eth device gets new number on resume https://bugs.launchpad.net/bugs/175333 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs ma

[Bug 175333] Re: first eth device gets new number on resume

2008-03-09 Thread Richard Jonsson
I hope I assigned this to the right identity. This bug should be easy to backport to a current gutsy kernel. Patch is provided at http://lkml.org/lkml/2008/1/3/418 ** Changed in: ubuntu Assignee: (unassigned) => Kernel Bugs (kernel-bugs) -- first eth device gets new number on resume https:/

[Bug 175333] Re: first eth device gets new number on resume

2008-03-09 Thread Lex Ross
New forcedeth version 0.61 that now ships with Hardy 8.04 Alpha 6 cured this problem on my nVidia nForce 610M chipset. Any chance of forcedeth driver updates to older kernels? -- first eth device gets new number on resume https://bugs.launchpad.net/bugs/175333 You received this bug notification b

[Bug 175333] Re: first eth device gets new number on resume

2008-01-07 Thread Richard Jonsson
Bug has been confirmed on LKML, and a patch has been provided there, for testing, which solves the issue in my case. See links below: For a complete discussion on LKML: http://lkml.org/lkml/2008/1/2/253 The provided patch: http://lkml.org/lkml/2008/1/3/418 ** Changed in: ubuntu Status: Ne

[Bug 175333] Re: first eth device gets new number on resume

2007-12-10 Thread Richard Jonsson
After some research it apperas that the forcedeth driver, which I use, has had issues with reverse mac addresses in other contexts. A guess is that the driver attempts to correct the address byte order on boot up, but fails to restore on suspend, and therefore reverses the corrected address on r

[Bug 175333] Re: first eth device gets new number on resume

2007-12-10 Thread Richard Jonsson
Just noticed in that dmesg output that the mac address has a revered byte-order. As I don't know what to do with that I'll leave the bug here. -- first eth device gets new number on resume https://bugs.launchpad.net/bugs/175333 You received this bug notification because you are a member of Ubuntu