Ubuntu

udev: renamed network interface hangs boot

Asked by Vincen Collins

What rule do I need to change to fix this?

[ 21.571926] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
[ 21.572018] HDA Intel 0000:00:1b.0: setting latency timer to 64
[ 21.605652] hda_codec: Unknown model for ALC880, trying auto-probe from BIOS...
[ 21.653397] udev: renamed network interface wlan0 to eth1
[ 559.321397] lp: driver loaded but no devices found
[ 559.419844] apm: BIOS not found.
[ 559.548999] Adding 2048276k swap on /dev/sda2. Priority:-1 extents:1 across:2048276k
[ 560.089007] EXT3 FS on sda3, internal journal

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
Steven Danna
Solved:
Last query:
Last reply:
Revision history for this message
Steven Danna (ssd7) said : 		#1

Can you do the following and paste the output here?

1) Open a terminal (Applications->Accessories->Terminal)
2) run the command: cat /etc/udev/rules.d/70-persistent-net.rules

Revision history for this message
Best Steven Danna (ssd7) said : 		#2

Actually rather than editing the udev rules, it is probably easier to just allow them to be recreated. Try the following:

1) Open a terminal
2) Run the following commands:

sudo cp /etc/udev/rules.d/70-persistent-net.rules ./70-persistent-net.rule.backup
sudo rm /etc/udev/rules.d/70-persistent-net.rules

3) Reboot.
4) Reboot again. If the boot still hangs on the second reboot than go ahead and follow the directions in my first post. If it seems fixed, go ahead and delete the backup of the rules file that we made in your home directory.

Revision history for this message
Vincen Collins (vincencollins) said : 		#3

Thanks Steven Danna, that solved my question.

Revision history for this message
Vincen Collins (vincencollins) said : 		#4

Thanks! That worked great.

This also solved another problem of even when I did get booted up there were numerous udev daemon (udevd) hogging the CPU, upwards of a 100% utilization. I ended up having to killall to get my computer to be usable. That issue has also been resolved.