https://bugzilla.redhat.com/show_bug.cgi?id=649570
Just an update for the archives: the problem appears to have been in
dhclient and not the e1000e driver. dhclient-4.2.0-14.P1.fc14 fixes it.
poc
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/
On Tue, Nov 2, 2010 at 3:42 PM, Patrick O'Callaghan
wrote:
> On 11/1/10 10:34 PM, Patrick O'Callaghan wrote:
>
>> This just in: the problem fixed itself magically, Must be because
>> yesterday was Halloween since I have no other explanation, rational or
>> otherwise. What happened was this:
>>
>>
On 11/1/10 10:34 PM, Patrick O'Callaghan wrote:
> This just in: the problem fixed itself magically, Must be because
> yesterday was Halloween since I have no other explanation, rational or
> otherwise. What happened was this:
>
> Despite no net, I wanted to recover some files from my backup NAS,
This just in: the problem fixed itself magically, Must be because yesterday
was Halloween since I have no other explanation, rational or otherwise. What
happened was this:
Despite no net, I wanted to recover some files from my backup NAS, so I
booted with the F13 (note, not F14) rescue disk, which
On Mon, 2010-11-01 at 14:58 -0600, Michal Jaegermann wrote:
> On Sun, Oct 31, 2010 at 11:06:53PM -0430, Patrick O'Callaghan wrote:
> > On Sun, 2010-10-31 at 19:46 -0600, Michal Jaegermann wrote:
> >
> > > The first "sanity check" is to configure your network interface
> > > static to make sure tha
On Sun, Oct 31, 2010 at 11:06:53PM -0430, Patrick O'Callaghan wrote:
> On Sun, 2010-10-31 at 19:46 -0600, Michal Jaegermann wrote:
>
> > The first "sanity check" is to configure your network interface
> > static to make sure that the basic hardware/driver are healthy.
> > One thing at a time.
>
>
On Mon, Nov 1, 2010 at 12:56 PM, Adam Williamson 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.
>
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, peopl
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
On Sun, 31 Oct 2010 19:16:28 -0430
"Patrick O'Callaghan" 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 Belk
On Sun, 2010-10-31 at 23:43 -0400, Gregory Woodbury wrote:
> From:
> Gregory Woodbury
>
>To:
> For testers of Fedora development
> releases
>
> Subject:
> Re
2010/11/1 Patrick O'Callaghan
> 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
On Sun, Oct 31, 2010 at 11:38 PM, Patrick O'Callaghan wrote:
> On Sun, 2010-10-31 at 23:36 -0400, Gregory Woodbury wrote:
> > Does the driver happen to be the e1000e intel driver?
>
> Yes.
>
> > I have an instability problem with that one.
>
> That's odd because F13 has never given me any trouble
On Sun, 2010-10-31 at 23:36 -0400, Gregory Woodbury wrote:
> Does the driver happen to be the e1000e intel driver?
Yes.
> I have an instability problem with that one.
That's odd because F13 has never given me any trouble. What kind of
instability and is there a fix?
poc
--
test mailing list
t
On Sun, 2010-10-31 at 19:46 -0600, Michal Jaegermann wrote:
> On Sun, Oct 31, 2010 at 08:57:14PM -0430, Patrick O'Callaghan wrote:
> > On Sun, 2010-10-31 at 18:15 -0600, Michal Jaegermann wrote:
> > > You should have a better chance for some meaningfull feedback if you
> > > will look at /var/log/m
On Sun, Oct 31, 2010 at 5:42 PM, Patrick O'Callaghan 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 h
On Sun, Oct 31, 2010 at 08:57:14PM -0430, Patrick O'Callaghan wrote:
> On Sun, 2010-10-31 at 18:15 -0600, Michal Jaegermann wrote:
> > You should have a better chance for some meaningfull feedback if you
> > will look at /var/log/messages and/or try 'nmcli'.
>
> nmcli just says it's not connected.
On Sun, 2010-10-31 at 18:15 -0600, Michal Jaegermann wrote:
> On Sun, Oct 31, 2010 at 05:12:33PM -0430, Patrick O'Callaghan wrote:
> >
> > Attempting to run nm-applet gives a mysterious message about "Could not
> > get the session bus". It then dumps core.
>
> It appears that for whatever reasons
On Mon, 2010-11-01 at 00:07 +, 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 mod
On Sun, Oct 31, 2010 at 05:12:33PM -0430, Patrick O'Callaghan wrote:
>
> Attempting to run nm-applet gives a mysterious message about "Could not
> get the session bus". It then dumps core.
It appears that for whatever reasons your dbus is not running.
Core dumping is a clear bug which is worthy o
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 af
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 d
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 d
23 matches
Mail list logo
