The current issue with renaming after an upgrade to jaunty is being
tracked as bug #329106
--
[Gutsy] broken 70-persistent-net.rules
https://bugs.launchpad.net/bugs/145382
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs m
my network card was listed as eth2, i just changed it to eth0...fix
worked for me
--
[Gutsy] broken 70-persistent-net.rules
https://bugs.launchpad.net/bugs/145382
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing li
Seems to be worse in jaunty. I upgraded from hardy to intrepid with no
networking difficulties, but I just upgraded the same machine from intrepid to
jaunty and had no network, because udev renamed eth0 to eth1. I removed
70-persistent-net.rules and rebooted, and that fixed the problem.
(See als
I've just experienced a similar issue on intrepid my eth0 was reported
as eth8 it may be because this systems been rebuilt and moved between
pc's a few times over the years and had several different network cards
hopefully renaming eth8 eth0 and deleting the other entries cures the
issue (it seem t
I realized after my previous message that this bug relates to Gutsy in
general, and not just the JeOS version..
My comment was specific to the JeOS build, which operates in a
fundamentally different environment as a Virtual Machine, which leads to
issues with the virtual NIC devices being a lot mo
Aside from the busybox issue..Isn't the udev net persistence feature
going to cause a lot more problems than it solves?
As I understand it, it is recording the MAC address of the NIC, and
associating that with an ethernet interface. So, that if the order the
NICs are initialized in changes,
** Tags added: iso-testing
--
[Gutsy] broken 70-persistent-net.rules
https://bugs.launchpad.net/bugs/145382
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubu
Oh sorry! Then i did falsely dupe it. I thought they were the same
issues leading to no working network. Please un-dupe 153727 then.
--
[Gutsy] broken 70-persistent-net.rules
https://bugs.launchpad.net/bugs/145382
You received this bug notification because you are a member of Ubuntu
Bugs, which i
Bug 153727 has been marked duplicate of this bug, and this bug is marked
Invalid. The issue in 153727 is same as Nego's issue, which Steve
indicates is a separate issue. The bug is very much present in Gutsy
Final (with all updates). Why was 153727 marked as a duplicate of this
bug then?
Should I
I've had the same problem after updating a Kubuntu desktop machine to
Gutsy last night. This morning, after rebooting, the single ethernet
card with a static address had "disappeared". Over the telephone I
confirmed that there was one "SUBSYSTEM=="net", DRIVERS=="?*"... line
(don't know if it con
It is a hack work around found through google, but it solved the problem
with the adapter changing on each reboot... when using a static IP.
Remove all lines of various eth0, eth1, eth2 and so on and replace them
with this line:
SUBSYSTEM=="net", DRIVERS=="forcedeth", NAME="eth0"
Adjust your dri
Look for
IRQ 16
Oct 4 20:27:06 NEGA kernel: [ 24.812477] PCI: Setting latency timer of
device :00:02.0 to 64
Oct 4 20:27:06 NEGA kernel: [ 24.812480] ohci_hcd :00:02.0: OHCI Host
Controller
Oct 4 20:27:06 NEGA kernel: [ 24.812677] ohci_hcd :00:02.0: new USB bus
r
Good I show the information of my file here
70-persistent-net.rules
# This cases out was automatically generated by the /lib/udev/write_net_rules
# program, probably run by the persistent-net-generator.rules rules cases out.
#
# You dog modify it, ace long ace you keep each rule on to single line
First, I request excuses by the badly English.
It is translation of google.
The problem in my case related to the connection of the network devices,
is that in each resumption the card that this connected changes its
name. the file 70-persistent-net.rules adds a 1 to him to the name
This implies
Jan - This bug's state is one of Fix Released meaning that the bug is
fixed and that you should not see it on a daily build of the server ISO
images nor on the RC image when it comes out.
--
[Gutsy] broken 70-persistent-net.rules
https://bugs.launchpad.net/bugs/145382
You received this bug notifi
On Wed, Oct 10, 2007 at 01:35:51PM -, Jan Kunder wrote:
> NEGO:
> Pls escribe en inglés (básico es bastante:)
> Si no hablar inglés ningún pequeño pedacito:
> Escribirlo en español (como)
> uso: http://www.google.com/translate_t?langpair=es |en
> y GOMA del copy en IGUAL comenta. Agradece:)
I'
Workaround/HINT::
1. comment EVERYTHING in /etc/udev/rules.d/70-persistent-net.rules
2. add:
## PCI device ONBOARD intel 10/100
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:bb:05:14:85:56",
NAME="eth0"
# PCI device 0x8086:0x1229 (e100)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:a
Hi.
I vote this to be nominated for RC(!) Gutsy release.
This is very dangerous, annoying 95% (or more) of installer, and I think&hope -
easy to repair. It IS working on other distros: feisty, Etch, Sarge, FC5+6+7 ...
Thanks much anyone.
--
[Gutsy] broken 70-persistent-net.rules
https://bugs.lau
HASAN::
IMHO yes:: delete "your lines".
And add these:
## PCI device ONBOARD intel 10/100
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:bb:05:14:85:56",
NAME="eth0"
# PCI device 0x8086:0x1229 (e100)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:a0:cc:d0:00:43",
NAME="eth1"
##xyz b
NEGO:
Pls write in English (basic is enough :)
If do NOT speak english any little bit:
Write it in Spanish (as you did)
use: http://www.google.com/translate_t?langpair=es|en
and COPY PASTE it in the SAME comment. Thanks :)
**
NEGO:
Pls escribe en inglés (básico es bastante:)
Si no hablar i
I can confirm this bug in Gutsy 7.10 server beta when installing it in a
VmWare virtual machine running over a GSX server.
--
[Gutsy] broken 70-persistent-net.rules
https://bugs.launchpad.net/bugs/145382
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
What does this section of /etc/udev/rules.d/70-persistent-net.rules do?
=
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="", NAME="eth0"
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="", NAME="eth0"
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="", NAME="eth0"
SUBSYSTEM=="ne
** Changed in: udev (Ubuntu)
Target: ubuntu-7.10-rc => None
--
[Gutsy] broken 70-persistent-net.rules
https://bugs.launchpad.net/bugs/145382
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu
fixed in busybox, marking as invalid for udev.
The last followup in Spanish seems to report an unrelated bug, since it
states that it affects desktop installs and happens after each reboot,
not just at install time.
** Changed in: udev (Ubuntu)
Status: Confirmed => Invalid
--
[Gutsy] bro
Bueno yo de ingles nada pero la compilacion del 1 de octubre y este error se
viene arrastrando desde el beta 5
No solo para la version server tambien para la version Desktop.
Al reiniciar el sistema reasigna nombre del dispositivo de red.
Esto implica tener que correr el pppoeconf para conectarse
busybox (1:1.1.3-5ubuntu5) gutsy; urgency=low
* Move test and friends to /bin (LP: #145382).
-- Colin Watson <[EMAIL PROTECTED]> Tue, 02 Oct 2007 19:52:41 +0100
** Changed in: busybox (Ubuntu)
Status: Confirmed => Fix Released
--
[Gutsy] broken 70-persistent-net.rules
https://bugs.
Apparently I misunderstood and the problem is that [ is in /usr/bin.
Reopening busybox task.
** Changed in: busybox (Ubuntu)
Status: Won't Fix => Confirmed
--
[Gutsy] broken 70-persistent-net.rules
https://bugs.launchpad.net/bugs/145382
You received this bug notification because you are a
I can confirm the bug.
It happend 28.09.07 10:18 GMT.
On my "new" P233MMX proxy and (SJ36=MM) 1GHz Celeron+256MB + i815E +
onboard_100Mbit + intelPCI_100Mbit.
I was lucky I was nearby all of the machines. I landed with Gutsy.beta1 on both
of them without any ethX (respectively with eth2+eth3) (et
Scott, I'm not going to build [ into busybox's /bin/sh (there's no
support for this in busybox at the moment and the one relevant
configuration option is far too invasive for this - it affects all
busybox applets). Please change udev-udeb to use a full PATH rather than
just /lib/udev.
** Changed i
Thanks Jim,
the patch for /etc/udev/rules.d/70-persistent-net.rules fixed the problem for
me. I used the alternate CD to install a command based distribution on an old
computer.
--
[Gutsy] broken 70-persistent-net.rules
https://bugs.launchpad.net/bugs/145382
You received this bug notification b
[EMAIL PROTECTED]:~# diff /etc/udev/rules.d/70-persistent-net.rules
70-persistent-net.rules
13c13
< SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:16:ec:6e:e1:fd",
NAME="eth0"
---
> SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:16:ec:6e:e1:fd",
> NAME="eth1"
and
[EMAIL PROTECTED]
I can confirm this happens on a gutsy server beta install here.
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="", NAME="eth0"
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="", NAME="eth0"
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="", NAME="eth0"
SUBSYSTEM=="net", DRIVERS=="?*", A
This is caused by the installer's busybox /bin/sh not having the [
built-in, so the write_net_rules shell script doesn't actually work
properly
** Also affects: busybox (Ubuntu)
Importance: Undecided
Status: New
--
[Gutsy] broken 70-persistent-net.rules
https://bugs.launchpad.net/bugs/
We use static network settings, and after installation the 70
-persistent-net.rules has seven lines like this:
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="", NAME="eth0"
and no line with a MAC-address. The computer only has one interface. If
I remove those lines, the network is brought up o
** Changed in: udev (Ubuntu)
Importance: Undecided => High
Target: None => ubuntu-7.10-rc
--
[Gutsy] broken 70-persistent-net.rules
https://bugs.launchpad.net/bugs/145382
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Lars Wirzenius had a similar issue with Ubuntu Alternate.
Described as comment here :
https://bugs.edge.launchpad.net/ubuntu/+source/network-manager/+bug/134496
--
[Gutsy] broken 70-persistent-net.rules
https://bugs.launchpad.net/bugs/145382
You received this bug notification because you are a m
36 matches
Mail list logo
