Ok, I've opened a new bug: https://bugs.launchpad.net/ubuntu/+bug/108152
--
Feisty boot hangs on "Configuring network interfaces"
https://bugs.launchpad.net/bugs/102675
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bug
This bug isn't fixed. Please reopen it!
--
Mvh. Louis
Hjemmeside: www.louis.dk
Mail: [EMAIL PROTECTED]
MSN: [EMAIL PROTECTED]
Jabber: [EMAIL PROTECTED] (ikke en mailadresse)
Registreret Linuxbruger nr.: 405248
--
Feisty boot hangs on "Configuring network interfaces"
https://bugs.launchpad.net/b
Since Louis's problem is not related to the original one and isn't
compatible with the original bug description ('after today's upgrades'),
I suggest opening a new bug would be more appropriate. Louis, if you do
open a new report, be sure to include the particular wireless card in
the bug descripti
It doesn't matter if mine is plugged or unplugged, it still hangs.
On 4/11/07, doobiest <[EMAIL PROTECTED]> wrote:
>
> Workaround [decent]:
>
> Move networking further down in the boot process.
>
> I moved networking from rcs.d to rc2.d/rc3.d/... and gave it a priority
> one lower than GDM.
>
> In
This bug has status "Fix released", but you Louis still seem to have
this problem. If so, maybe the bug should be reopened.
--
Feisty boot hangs on "Configuring network interfaces"
https://bugs.launchpad.net/bugs/102675
You received this bug notification because you are a member of Ubuntu
Bugs, w
I've tryed Coon's trick and wov now Ubuntu boots fast.
I try I know why this problem exist.
The Network Manager have it's own network settings with wired or wireless
network, but that Upstarter don't know and it's try to set the network
interfaces up by the /etc/network/interfaces file? Have I r
I've the same problem.
I've a HP Pavilion dv9271 with a ipw3945 wireless card
My friend when also have a HP with a ipw3945 wireless card (not the same model
but it's match old.) have the same problem and now he switch back to Windows
and he will not use Linux again he says.
Please fix this proble
Workaround [decent]:
Move networking further down in the boot process.
I moved networking from rcs.d to rc2.d/rc3.d/... and gave it a priority
one lower than GDM.
In otherwords 'mv /etc/rcS.d/@##networking /etc/rc2.d/@14networking'
So now GDM boots, followed immediatley by networking. By time I
Confirmed; it was caused by the udev rules update that attempted to only
auto ifup/ifdown interfaces with physical hardware. A slight change to
the udev rule to behave as we intended (udev has a strange behaviour
with S!= rules) fixes this problem and the original problem
** Changed in: ifupdown
** Attachment added: "proposed debdiff"
http://librarian.launchpad.net/7237187/ifupdown_0.6.8ubuntu6.patch
--
Feisty boot hangs on "Configuring network interfaces"
https://bugs.launchpad.net/bugs/102675
You received this bug notification because you are a member of Ubuntu
Bugs, which is the b
I don't think this has anything to do with the contents of
/etc/network/interfaces, since ifup won't bother with devices that don't
exist.
This is far more likely to be caused to the recent ifupdown update that
adjusted the udev rules to try and stop it altering ppp devices, and has
uncovered a ud
** Changed in: netbase (Ubuntu)
Importance: Undecided => Medium
** Changed in: netbase (Ubuntu)
Target: None => ubuntu-7.04
--
Feisty boot hangs on "Configuring network interfaces"
https://bugs.launchpad.net/bugs/102675
You received this bug notification because you are a member of Ubu
Just in case you have disabled the networking script with "sudo update-
rc.d -f networking remove" and for some reason or another want to undo
this change, you can re-enable the script again with "sudo update-rc.d
networking start 40 S ."
--
Feisty boot hangs on "Configuring network interfaces"
h
I have this problem too. I would rather see a real fix, despite most of
the beta userbase being copasetic with kludges like blanking the
interfaces file.
--
Feisty boot hangs on "Configuring network interfaces"
https://bugs.launchpad.net/bugs/102675
You received this bug notification because you
I have this problem too :( takes very lonng now to boot
--
Feisty boot hangs on "Configuring network interfaces"
https://bugs.launchpad.net/bugs/102675
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing lis
Oh, and when I found the site saying to blank out that file to get WPA
to work with nm-applet, I was using Dapper. It's been there all along
if you knew to clear that file so that nm-applet has full control.
--
Feisty boot hangs on "Configuring network interfaces"
https://bugs.launchpad.net/bugs
Blanking out /etc/network/interfaces is the only way I've found to get
WPA-PSK to work with nm-applet. I spent a day trying to figure out then
found some site that said to do that, tried it, and that made it work.
--
Feisty boot hangs on "Configuring network interfaces"
https://bugs.launchpad.ne
Well, I guess I spoke out of turn. Cry yer pardon!
I blanked out /etc/network/interfaces as described, leaving just the lo
interface.
Then i rebooted (no hang, of course) and logged into gnome. I started
nm-applet, and it immediately saw my wireless AP (and a neighbor's). I
connected, and it a
Steve, these are workarounds and not really solutions, yes. However, in
most cases the networking script is not necessary because all network
interfaces that are marked as "auto" will be enabled by
/etc/udev/rules.d/85-ifupdown.rules as soon as they are detected. This
is the modern event-based sche
I've always considered blanking out /etc/network/interfaces to be a
normal configuration. The only way to get WPA support with Network
Manager is to do that.
Doing those things doesn't hurt anything if you aren't trying to do
anything really weird like bridge a connection or have 2 interfaces
goi
First of all, I can confirm this on Feisty, updated last night, with
kernel 2.6.20-14-generic (on x86, of course).
Second of all:
"sudo update-rc.d -f networking remove" == nasty hack.
blanking out /etc/network/interfaces == nasty hack.
These scripts are here for a reason -- so you don't have to
I Confirm this bug on my IBM R60 with ubuntu 7.04
and the /etc/network/interfaces fix work for me .
THX
--
Feisty boot hangs on "Configuring network interfaces"
https://bugs.launchpad.net/bugs/102675
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug c
I just told https://answers.launchpad.net/ubuntu/+ticket/4457 to do
what Tormod said (sudo update-rc.d -f networking remove), and seeing his
description along with what Thomas just said, and guessing this problem
and his are linked, could it be what that question-asker said? Maybe
it's trying to
Confirmed.
I'm running an HP Pavillion dv1000 laptop with centrino 1.7, 512mb ram,
and feisty.
auto lo
iface lo inet loopback
iface eth0 inet dhcp
auto eth1
iface eth1 inet dhcp
wireless-essid Virus Haven
wireless-key 1234567890abcdef1234567890
auto eth2
iface eth2 inet dhcp
auto ath0
iface
Confirmed. Boot delay seems related to DHCP timeout on eth1 (wireless)
for unknown reasons.
--
Feisty boot hangs on "Configuring network interfaces"
https://bugs.launchpad.net/bugs/102675
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubun
Quote: "sudo update-rc.d -f networking remove"
Works great!
THX!
--
Feisty boot hangs on "Configuring network interfaces"
https://bugs.launchpad.net/bugs/102675
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mail
Hello again.
Can someone explain me why, whitout any action from me (meaning I didn't change
anything at all) suddenly, after a goodnight sleep, the problem as gone.
That's right, Ubuntu Feisty recently upgraded boot normaly.
Any other case like this? explanation?
If happens again I'll let you k
Sorry, that should be -f and not -n...
--
Feisty boot hangs on "Configuring network interfaces"
https://bugs.launchpad.net/bugs/102675
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.u
The /etc/init.d/networking boot scripts hangs because "ifup -a" tries to start
many non-existing or not-connected network devices. For many setups/users this
script is not necessary at all, since network adapters are managed by
network-manager or by detection events. Another workaround is theref
Confirming bug with static IP. After commenting out to boot and setting
the static address the interfaces looks as:
auto lo
iface lo inet loopback
#auto eth0
#iface eth0 inet static
#address 192.168.1.100
#netmask 255.255.255.0
#gateway 192.168.1.1
#auto eth1
#iface eth1 inet dhcp
#auto eth2
#i
Oops, forgot to say in above that I'm using feisty x86.
--
Feisty boot hangs on "Configuring network interfaces"
https://bugs.launchpad.net/bugs/102675
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ub
Confirming bug with slightly different symptom. After the update, my
system hung on the "Configuring Network Interfaces" for at least 5
minutes, I think more like 10. I didn't know to try as
posted above.
This is a Gigabyte GA-965GM-S2, intel 965g chipset , of course with
Marvell 88E8056. Only on
Here is my /etc/network/interfaces after the update:
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet dhcp
auto eth1
iface eth1 inet dhcp
And this is how it boots up fast:
auto lo
iface lo inet loopback
#auto eth0
#iface eth0 inet dhcp
#auto eth1
#iface eth1 inet dhcp
Tough the up
David Rodrigues I had the same problem, to pass the "Configuring Network
Interfaces" I pressed Ctrl+Alt+Delete, just once, so it killed the
process and proceded with the boot sequence.
--
Feisty boot hangs on "Configuring network interfaces"
https://bugs.launchpad.net/bugs/102675
You received thi
By the way, I wouldn't say removing everything but lo is a "workaround".
My /etc/network/interfaces had nothing but lo until the update (cuz
network-manager kinda hates any other configuration), then all of a
sudden there was junk in there.
--
Feisty boot hangs on "Configuring network interfaces"
maco:
I rolled back to Feisty Herd 5 and wont do updates until this resolves.
I am looking at my interfaces file right now:
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet dhcp
auto eth1
iface eth1 inet dhcp
auto eth2
iface eth2 inet dhcp
auto ath0
iface ath0 inet dhcp
auto wlan0
if
that's strange about the sky2 driver. I've never had any problems with
it other than this. it's been running the Marvell 88E8053 PCI-E Gigabit
Ethernet Controller on this macbook since edgy beta without problems.
But watch, now that you said that I'll start having that long endless
nightmare.
--
I had that too...
boot with CD and mount your harddrive and then remove the network shares from
the fstab file.
worked for me.
--
Feisty boot hangs on "Configuring network interfaces"
https://bugs.launchpad.net/bugs/102675
You received this bug notification because you are a member of Ubuntu
B
Just upgrade Feisty and in my case the boot complety hangs on "Configuring
network interfaces".
I waited for more than one hour! I tried Safe mode and the same happened. (I´m
in windows XP right now)
I have a Core 2 duo 2.16, 1 Gb RAM, Nvidia Go 7300..
I really don´t know what to do.
Any suggest
hardyn, since Sokraates said that the problem stars after ifupdown is
updated, but rolling that update back doesn't fix it, I think what
happened is that when that was installed, it included directions or a
script to overwrite the /etc/network/interfaces with what we all have
(but rolling back didn
confirmed for Feisty on black macboook core duo.
sky2 eth0: enabling interface
[ 37.208000] sky2 eth0: ram buffer 48K
[ 38.356000] NET: Registered protocol family 17
[ 43.636000] applesmc: wait status failed: c != 18
[ 87.148000] CIFS VFS: Error connecting to IPv4 socket. Aborting operat
same problem here... will try the fix...
--
Feisty boot hangs on "Configuring network interfaces"
https://bugs.launchpad.net/bugs/102675
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
is that really the fix? to comment out the extra adaptors, or does that
just happen to work?
thanks.
--
Feisty boot hangs on "Configuring network interfaces"
https://bugs.launchpad.net/bugs/102675
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contac
Here is the interfaces file, both Ethernet controllers (wired and
wireless) are Intel.
** Attachment added: "interfaces"
http://librarian.launchpad.net/7170294/interfaces
--
Feisty boot hangs on "Configuring network interfaces"
https://bugs.launchpad.net/bugs/102675
You received this bug noti
I can also confirm the workaround/fix suggested above works. Thank you!
--
Feisty boot hangs on "Configuring network interfaces"
https://bugs.launchpad.net/bugs/102675
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bug
Confirmed here. The wait seems longer if I don't have an ethernet cable
connected, but that's just my gut feeling - I haven't timed it yet.
Toshiba L30-105 laptop running 32-bit Feisty.
09:02.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL-8139/8139C/8139C+ (rev 10)
09:04.0 Ethernet c
Confirm! My feisty install hands for 90 seconds during "configuring network
interfaces" - and that's with a 2GHz Core 2 Duo! Intel PRO/Wireless 3945ABG.
I will try deleting everything but lo and see if that improves it.
** Attachment added: "interfaces"
http://librarian.launchpad.net/7169089
Confirmed on Acer TravelMate C310. Putting the hardwired NIC in roaming
mode doesn't help. Can't tell you how long I gotta wait because I
generally hit CAD to make it skip the step.
--
Feisty boot hangs on "Configuring network interfaces"
https://bugs.launchpad.net/bugs/102675
You received this b
Here's mine in 3 states: normal (before update), yesterday (after
update), today (after cleaning it out)
How it normally looks
auto lo
iface lo inet loopback
#auto eth0
#iface eth0 inet dhcp
#auto eth1
#iface eth1 inet dhcp
How it looked yesterday with the slowness:
auto lo
iface lo inet loopba
Here's my interfaces attached file.
** Attachment added: "interfaces"
http://librarian.launchpad.net/7155416/interfaces
--
Feisty boot hangs on "Configuring network interfaces"
https://bugs.launchpad.net/bugs/102675
You received this bug notification because you are a member of Ubuntu
Bugs, w
Confirmed on an Abit KN8 SLI mainboard with onboard network.
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet dhcp
auto eth1
iface eth1 inet dhcp
auto eth2
iface eth2 inet dhcp
auto ath0
iface ath0 inet dhcp
auto wlan0
iface wlan0 inet dhcp
iface dsl-provider inet ppp
pre-up /sbin/i
Confirmed on a sony vaio vgn-s4hp with Nvidia 6200 Go and ipw2200
wireless.
--
Feisty boot hangs on "Configuring network interfaces"
https://bugs.launchpad.net/bugs/102675
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-
could everybody please attach their /etc/network/interfaces files
--
Feisty boot hangs on "Configuring network interfaces"
https://bugs.launchpad.net/bugs/102675
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs maili
The problem is that the update added a bunch of CRAP to
/etc/network/interfaces. I downgraded
module-init-tools
udev, volumeid, dmsetup
ifupdown
m-i-t AND ifupdown
None of those fixed it. None of those packages are the problem. The
problem is entirely that a bunch of crap was put in
/etc/netw
I downgraded this package to 0.6.8ubuntu3, the version it was on
4/3/07, and it didn't fix the problem, so the new version is not the
problem.
** Changed in: ifupdown (Ubuntu)
Status: Unconfirmed => Rejected
--
Feisty boot hangs on "Configuring network interfaces"
https://bugs.launchpad.
I've played around for a while, did a reinstall and tried the updates
bit by bit. It seems that the update to ifupdown is the culprit.
** Also affects: ifupdown (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
Feisty boot hangs on "Configuring network interfaces"
https://bugs.laun
Drats, forgot to add my specs:
HP nx6110
Broadcom 4318 rev2 (using ndiswrapper)
--
Feisty boot hangs on "Configuring network interfaces"
https://bugs.launchpad.net/bugs/102675
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ub
Confirmed here as well (wait of something like 30 seconds at configuring
network interfaces).
P$P800 Deluxe main board, built-in ethernet disabled, 2 external 100MBIT
ethernet cards
Started after updates of April 4
Worrying how things like this seem to regress so easily just before the RC
period
Bug confirmed !!!
Crucial and important bug.
The system now hangs for about 75 secs on "Configuring networks
interfaces" during boot up.
My system specs :
Ubuntu 7.04 beta (with latest updates)
HP TC4400 Tablet PC
Core 2 Duo
1.5 GB ram
Intel 945 GM chipset.
uname -a ==> 2.6.20-13-generic #2 S
can confirm on feisty i386 with intel 945GM and ipw3945
--
Feisty boot hangs on "Configuring network interfaces"
https://bugs.launchpad.net/bugs/102675
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ub
** Changed in: netbase (Ubuntu)
Sourcepackagename: None => netbase
--
Feisty boot hangs on "Configuring network interfaces"
https://bugs.launchpad.net/bugs/102675
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mail
** Changed in: Ubuntu
Status: Unconfirmed => Confirmed
--
Feisty boot hangs on "Configuring network interfaces"
https://bugs.launchpad.net/bugs/102675
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing l
Confirm also on feisty i386
--
Feisty boot hangs on "Configuring network interfaces"
https://bugs.launchpad.net/bugs/102675
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
h
confirm on feisty i386 with intel 2915 and marvell yukon on asus z71vp
--
Feisty boot hangs on "Configuring network interfaces"
https://bugs.launchpad.net/bugs/102675
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
I can confirm it in Feisty on amd64.
--
Feisty boot hangs on "Configuring network interfaces"
https://bugs.launchpad.net/bugs/102675
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.ubu
Output of lspci -vv
** Attachment added: "lspci.txt"
http://librarian.launchpad.net/7143594/lspci.txt
--
Feisty boot hangs on "Configuring network interfaces"
https://bugs.launchpad.net/bugs/102675
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug co
output of dmesg.
** Description changed:
After today's upgrades when I boot to feisty (both recovery and normal)
the system hangs for about 15-25 seconds on "Configuring network
interfaces."
- Here is the output of dmesg:
-
- ##DMESG START
- [0.00] Linux version 2.6.20-13-generi
Confirmed here too, Dell Insprion 510m.
Not a fix, but a workaround: delete everything in
/etc/network/interfaces except the lines defining "lo". As long as
NetworkManager can pick up your connection, everything will be fine and
your boot delay should disappear.
--
Feisty boot hangs on "Configur
Alex, you could've just put the output of those commands in files and
attatched them to the bug report instead. But I digress. I can confirm
that I'm having these problems too; the difference is that I'm waiting
2-3 minutes at the boot-up screen because of this problem.
--
Feisty boot hangs on "C
69 matches
Mail list logo
