netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarek Poplawski <jarkao2@gmail.com>
To: Dan McNaul <dmcnaul@hotmail.com>
Cc: netdev@vger.kernel.org, bugme-daemon@bugzilla.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [Bugme-new] [Bug 10201] New: Yum update of Kernel broke sis900 ethernet driver
Date: Thu, 13 Mar 2008 11:03:12 +0000	[thread overview]
Message-ID: <20080313110312.GA4764@ff.dom.local> (raw)
In-Reply-To: <20080311091928.GA5765@ff.dom.local>

On Tue, Mar 11, 2008 at 09:19:28AM +0000, Jarek Poplawski wrote:
> On 09-03-2008 00:50, Andrew Morton wrote:
> > On Sat,  8 Mar 2008 15:36:55 -0800 (PST) bugme-daemon@bugzilla.kernel.org wrote:
> > 
> >> http://bugzilla.kernel.org/show_bug.cgi?id=10201
> ...
> >> Problem Description:  After reboot following YUM update to new kernel - SiS 900
> >> PCI Fast Ethernet (driver sis900) can not ifconfig eth0.  Configuration fails
> >> with  message "SIOCSIFFLAGS: Invalid argument".  System does boot. [...]
...
> > What could cuase SIOCSIFFLAGS to newly return -EINVAL?

Second try: dev->validate_addr()?!

Dan, you don't have HW (MAC) address set on your card, and it's
verified since 2.6.23.

Check if it can be done in BIOS (if it's onboard card) or in some
Fedora config tool or file. To verify this idea try again in 2.6.24.3
something like this:

ifconfig eth0 hw ether 00:00:00:00:00:01
ifconfig eth0 192.168.0.108

Regards,
Jarek P.

  reply	other threads:[~2008-03-13 11:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-10201-10286@http.bugzilla.kernel.org/>
2008-03-08 23:50 ` [Bugme-new] [Bug 10201] New: Yum update of Kernel broke sis900 ethernet driver Andrew Morton
2008-03-11  9:19   ` Jarek Poplawski
2008-03-13 11:03     ` Jarek Poplawski [this message]
2008-03-13 11:37       ` Jarek Poplawski

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=20080313110312.GA4764@ff.dom.local \
    --to=jarkao2@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=dmcnaul@hotmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).