public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jarek Poplawski <jarkao2@o2.pl>
To: Sid Boyce <g3vbv@blueyonder.co.uk>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: 2.6.19 and up to  2.6.20-rc2 Ethernet problems x86_64
Date: Thu, 4 Jan 2007 12:46:14 +0100	[thread overview]
Message-ID: <20070104114614.GB3175@ff.dom.local> (raw)
In-Reply-To: <459BDFA6.4070109@blueyonder.co.uk>

On Wed, Jan 03, 2007 at 04:53:58PM +0000, Sid Boyce wrote:
...
> It seems >=2.6.19 and the SuSEfirewall are incompatible.

Actually, many programs could be incomapatible with
newer kernel versions, so sometimes upgrades or at
least recompilations are needed. 
  
...
> There is still the problem where the ethernet doesn't get configured 
> with acpi=off which I shall post to the acpi devel list, but this is not 
> a showstopper for me. ifconfig eth0 192.168.10.5 returns SIOCSIFFLAGS: 

I don't know acpi enough but as far as I know
some mainboards can't work properly with acpi
off, so it's probably not a bug.

Cheers,
Jarek P. 

  reply	other threads:[~2007-01-04 11:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-28  3:23 2.6.19 and up to 2.6.20-rc2 Ethernet problems x86_64 Sid Boyce
2006-12-29  6:32 ` Jarek Poplawski
     [not found]   ` <4595CD1B.2020102@blueyonder.co.uk>
2007-01-02 11:50     ` Jarek Poplawski
2007-01-02 15:32       ` Sid Boyce
2007-01-03 10:48         ` Jarek Poplawski
2007-01-03 16:53           ` Sid Boyce
2007-01-04 11:46             ` Jarek Poplawski [this message]
2007-01-02 15:33       ` Sid Boyce
2007-01-02 15:39       ` Sid Boyce
  -- strict thread matches above, loose matches on Subject: below --
2007-01-02 15:24 Sid Boyce
2007-01-02 15:41 Sid Boyce
2007-01-02 16:59 ` Len Brown
2007-01-02 22:57   ` Sid Boyce
2007-01-03  6:17     ` Len Brown
2007-01-05  9:09       ` Sid Boyce

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070104114614.GB3175@ff.dom.local \
    --to=jarkao2@o2.pl \
    --cc=g3vbv@blueyonder.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox