6:46 p.m.
I just did a fresh install of F14-RC1 (i.e. the gold version, x86_64)
with default options and have no network. My F13 system on the same h/w
and net had no problems. This is a bog-standard wired Ethernet using
DHCP to a Belkin hub. The net itself is fine as other machines can
connect, but F14 is dead. The "Edit Connections" dialogue is completely
normal, IPv4, DHCP for everything etc.
The LAN interface is an onboard Intel e1000. The kernel module is
loaded. Running "ifup eth0" (after "ifdown") times out after 90
seconds.
Attempting to run nm-applet gives a mysterious message about "Could not
get the session bus". It then dumps core.
This is about as uncomplicated a setup as it's possible to imagine, and
yet it doesn't work out of the box. Suggestions would be welcome.
poc
PS Sending from my F13 netbook on the exact same network.
7:07 p.m.
On Sun, 31 Oct 2010, Patrick O'Callaghan wrote:
...
connect, but F14 is dead. The "Edit Connections" dialogue is completely
normal, IPv4, DHCP for everything etc.
The LAN interface is an onboard Intel e1000. The kernel module is
loaded. Running "ifup eth0" (after "ifdown") times out after 90
seconds.
It sounds as if the system isn't getting a DHCP reply for some reason. If
I was having the problem I would use ifconfig -a to find out what state
the network was in, and would try service iptables stop service ip6tables
stop and setenforce 0 before trying again (disable IPv4 and IPv6 firewalls
and disable selinux which might each be interfering with the DHCP
process).
Michael Young
7:46 p.m.
On Mon, 2010-11-01 at 00:07 +0000, M A Young wrote:
On Sun, 31 Oct 2010, Patrick O'Callaghan wrote:
> ...
> connect, but F14 is dead. The "Edit Connections" dialogue is completely
> normal, IPv4, DHCP for everything etc.
>
> The LAN interface is an onboard Intel e1000. The kernel module is
> loaded. Running "ifup eth0" (after "ifdown") times out after 90
seconds.
It sounds as if the system isn't getting a DHCP reply for some reason. If
I was having the problem I would use ifconfig -a to find out what state
the network was in, and would try service iptables stop service ip6tables
stop and setenforce 0 before trying again (disable IPv4 and IPv6 firewalls
and disable selinux which might each be interfering with the DHCP
process).
Michael Young
Thanks. I did all that and the network came up. Now to figure out which
is the critical part, but at least it means that it's not the driver,
which I was afraid of.
BTW the Live CD has exactly the same problem. I don't understand why
people aren't screaming about this. It's a very ordinary machine with
very standard hardware.
I'm doing a "yum update" right now and hoping it will magically fix
itself.
poc
12:26 p.m.
On Sun, 2010-10-31 at 20:16 -0430, Patrick O'Callaghan wrote:
BTW the Live CD has exactly the same problem. I don't understand
why
people aren't screaming about this. It's a very ordinary machine with
very standard hardware.
Just in case subsequent discussion didn't render it obvious, people
mostly aren't screaming because this bug isn't a general one. On most
systems, networking works fine. This has some hardware- or
configuration-specific element to it.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net
2:53 p.m.
On Mon, Nov 1, 2010 at 12:56 PM, Adam Williamson <awilliam(a)redhat.com>wrote:
On Sun, 2010-10-31 at 20:16 -0430, Patrick O'Callaghan wrote:
> BTW the Live CD has exactly the same problem. I don't understand why
> people aren't screaming about this. It's a very ordinary machine with
> very standard hardware.
Just in case subsequent discussion didn't render it obvious, people
mostly aren't screaming because this bug isn't a general one. On most
systems, networking works fine. This has some hardware- or
configuration-specific element to it.
Clearly. I'm just trying to understand what it might be given that the
identical hardware (a very common Intel LAN chip on an Intel mobo) on the
identical network had no problems with any previous version of Fedora
including F13, and I'm using a fresh install of the default Desktop profile
of F14 with no changes whatsoever. It's particularly worrying that nm-applet
gives a message complaining about not connecting to "the session bus"
(presumably Dbus) followed by a core dump. I realize that it's not practical
to test every possible combination of hardware and network before release,
but given that the problem is real and reproducible I'm looking for
suggestions to resolve it.
I've not yet reported this to BZ, mainly because copying the various
messages and log files is going to have to be done the hard way, but I'll
try and get round to it after work.
poc
3:25 a.m.
2010/11/1 Patrick O'Callaghan <pocallaghan(a)gmail.com>
I just did a fresh install of F14-RC1 (i.e. the gold version,
x86_64)
with default options and have no network. My F13 system on the same h/w
and net had no problems. This is a bog-standard wired Ethernet using
DHCP to a Belkin hub. The net itself is fine as other machines can
connect, but F14 is dead. The "Edit Connections" dialogue is completely
normal, IPv4, DHCP for everything etc.
The LAN interface is an onboard Intel e1000. The kernel module is
loaded. Running "ifup eth0" (after "ifdown") times out after 90
seconds.
Attempting to run nm-applet gives a mysterious message about "Could not
get the session bus". It then dumps core.
This is about as uncomplicated a setup as it's possible to imagine, and
yet it doesn't work out of the box. Suggestions would be welcome.
poc
PS Sending from my F13 netbook on the exact same network.
may be related:
https://bugzilla.redhat.com/show_bug.cgi?id=642596
7:35 a.m.
On Sun, 31 Oct 2010 19:16:28 -0430
"Patrick O'Callaghan" <pocallaghan(a)gmail.com> wrote:
I just did a fresh install of F14-RC1 (i.e. the gold version,
x86_64)
with default options and have no network. My F13 system on the same
h/w and net had no problems. This is a bog-standard wired Ethernet
using DHCP to a Belkin hub. The net itself is fine as other machines
can connect, but F14 is dead. The "Edit Connections" dialogue is
completely normal, IPv4, DHCP for everything etc.
The LAN interface is an onboard Intel e1000. The kernel module is
loaded. Running "ifup eth0" (after "ifdown") times out after 90
seconds.
Attempting to run nm-applet gives a mysterious message about "Could
not get the session bus". It then dumps core.
This is about as uncomplicated a setup as it's possible to imagine,
and yet it doesn't work out of the box. Suggestions would be welcome.
poc
PS Sending from my F13 netbook on the exact same network.
HI,
I have the same problem, only slightly different system.
Interesting may be that dmesg |grep eth0 comes up with
"no ipv6 routers found"
Googling gave no insight.
Is this a kernel error message?
Henk
12:25 p.m.
On Mon, 2010-11-01 at 13:35 +0100, net wrote:
HI,
I have the same problem, only slightly different system.
Interesting may be that dmesg |grep eth0 comes up with
"no ipv6 routers found"
Googling gave no insight.
Is this a kernel error message?
Henk
It's a normal message and not the source of your problem. Anyone who
isn't on an IPv6-capable network (which is most people) gets that
message.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net
4935
days inactive
4936
days old
7 comments
5 participants
participants (5)
-
Adam Williamson -
cornel panceac -
Henk Breimer -
M A Young -
Patrick O'Callaghan