We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
Hello Lieven.
From:
http://www.debian.org/releases/stable/amd64/ch03s01.html.en
The installer software, debian-installer, is the primary concern of this
manual. It detects hardware and loads appropriate drivers, uses dhcp-client to
set up the network connection, runs debootstrap to install the
Hello Lieven.
From:
http://www.debian.org/releases/stable/amd64/ch03s01.html.en
The installer software, debian-installer, is the primary concern of this
manual. It detects hardware and loads appropriate drivers, uses dhcp-client to
set up the network connection, runs debootstrap to install the
Thanks for your reply.
It surely is a change from previous releases. However, the beginning of this
problem is already noticeable in Jaunty.
When creating a custom Jaunty live-cd (with remastersys for example), you have
to include network-manager or the live-cd won't boot (it gets stuck at
Sorry, but since when do I have to configure my network?
The only thing I do is selecting dhcp during installation.
That should configure the network automatically, as it has always done before.
So, simply put, I didn't use any of both.
--
No more network after removing network-manager
your network always has to be configured, though it sounds like you are
used to it being autoconfigured. I suspect that the network in general
is autoconfed at least with network-manager and by the installer. If
you don't use network-manager to configure your network, then
It is possible (I can't deny or confirm) that it's not a network-manager
problem.
But the question remains: Which package then, is responsible for this problem?
I don't know.
The strange thing is, as said earlier: A command line install without
network-manager is working just fine,
but a full
did you use /etc/interfaces to configure your network, or did you use
network manager?
--
No more network after removing network-manager
https://bugs.launchpad.net/bugs/407302
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
how could that be a problem with network-manager if the package is not
installed?. the bug needs to be reassigned.
** Package changed: network-manager (Ubuntu) = ubuntu
** Tags added: needs-reassignment
--
No more network after removing network-manager
https://bugs.launchpad.net/bugs/407302
Just tried the alternate-install-cd of Karmic and installed just a
command-line-system, and indeed network-manager was not installed.
Strange enough, I had a good functioning network connection. So, I don't
get it anymore... Seems like a command line install of just more than
200 MB without
After that, got to system, tools, network diagnostics and saw the IPv4 was
0.0.0.0
Will now check if the problem also occurs on the full installation of the
alternate-install-cd.
--
No more network after removing network-manager
https://bugs.launchpad.net/bugs/407302
You received this bug
Well, I wasn't able to check because of bug #407767.
--
No more network after removing network-manager
https://bugs.launchpad.net/bugs/407302
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
13 matches
Mail list logo
