[Bug 72565] Re: Swapped nforce4 boards - now no eth0

2007-11-26 Thread Rob Hughes
OK, then why is only the forcedeth and skge driver listed, if this is so important? I removed everything from iftab, and the network comes up fine. Also, even though forcedeth is listed as being permanetly assigned eth0, it was not assigned the name eth0. After swapping boards, it was named eth1 un

[Bug 72565] Re: Swapped nforce4 boards - now no eth0

2007-11-26 Thread Scott James Remnant
This is a Won't Fix, because this is Expected Behaviour. Names of ethernet devices are allocated based on static information about the device, such as its MAC address. Adding a new device will result in it being given a new name, which it will then be assigned permanently. Removing a device will

[Bug 72565] Re: Swapped nforce4 boards - now no eth0

2007-11-24 Thread Rob Hughes
So, with access to the source code and control over the install scripts, you can't fix it? O_o Or you won't fix it? -- Swapped nforce4 boards - now no eth0 https://bugs.launchpad.net/bugs/72565 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact fo

[Bug 72565] Re: Swapped nforce4 boards - now no eth0

2007-11-24 Thread fishor
Unfortunately we can't fix it, because it is a feature. ** Changed in: udev (Ubuntu) Sourcepackagename: None => udev Status: New => Invalid -- Swapped nforce4 boards - now no eth0 https://bugs.launchpad.net/bugs/72565 You received this bug notification because you are a member of Ubuntu B

[Bug 72565] Re: Swapped nforce4 boards - now no eth0

2007-11-03 Thread Rob Hughes
One other important point, I did not hard code the MAC, so I disagree with your statement that this is not easily reproducable. And so I'm moving it back to new. This is something done by the install process, not the user. I also dug back through some old threads, and found that the solution was to

[Bug 72565] Re: Swapped nforce4 boards - now no eth0

2007-11-03 Thread Rob Hughes
Sorry, I'd forgotten about this. Someone was able to clue me in to the fact that the MAC address of the old NIC was hard coded in a file, though I can't remember which one now. Once I removed it from there, I again had eth0. Sorry, I know that's probably not much help. -- Swapped nforce4 boards -

[Bug 72565] Re: Swapped nforce4 boards - now no eth0

2007-11-03 Thread SEAQ - Andres Mujica
Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. Also i don't think it could be easily reproducible. So it's been marked as invalid. But if you in someway can reproduce it in ord