From: mike <mike@bristolreccc.co.uk>
To: Aristeu Sergio Rozanski Filho <aris@cathedrallabs.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: problem with sis900 driver 2.6.5 +
Date: Wed, 12 May 2004 11:19:06 +0100 [thread overview]
Message-ID: <1084357146.24569.13.camel@datacontrol> (raw)
In-Reply-To: <20040512005008.GA18347@cathedrallabs.org>
On Tue, 2004-05-11 at 21:50 -0300, Aristeu Sergio Rozanski Filho wrote:
> > In kernels 2.6.5 and above (may affect 2.6.4 as well) there seems to be
> > a problem with the sis900 eth driver
> >
> > I have a sis chipset with integrated ethernet sis900 driver which has
> > always worked perfectly up to and including 2.6.3 (fedora)
> >
> > Now with both fedora 2.6.5 kernel and vanilla 2.6.6 eth0 does not come
> > up
> >
> > relevant messages
> >
> > sis900 device eth0 does not appear to be present delaying initialisation
> >
> > and from dmesg eth0: cannot find ISA bridge
> >
> > 2.6.3 works fine
> >
> > lsmod shows sis and sis900 modules loaded fine
> I had the same problem, the patch attached is a dirty fix to get it
> running again. in newer kernels its isa bridge is listed with a different
> product id (0x0018). no idea why.
>
this works fine - thanks
> --
> Aristeu
>
prev parent reply other threads:[~2004-05-12 10:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-11 18:28 problem with sis900 driver 2.6.5 + mike
2004-05-11 18:41 ` Luiz Fernando N. Capitulino
2004-05-11 21:40 ` Daniele Venzano
2004-05-12 9:37 ` mike
2004-05-11 19:01 ` problem with sis900 Dominik Karall
2004-05-11 21:45 ` Daniele Venzano
2004-05-11 22:30 ` Dominik Karall
2004-05-13 15:17 ` Daniele Venzano
2004-05-13 18:02 ` Dominik Karall
2004-05-15 7:12 ` Daniele Venzano
2004-05-15 12:12 ` Dominik Karall
2004-05-15 16:56 ` Daniele Venzano
2004-05-16 11:21 ` Dominik Karall
2004-05-17 11:35 ` Dominik Karall
2004-05-12 0:50 ` problem with sis900 driver 2.6.5 + Aristeu Sergio Rozanski Filho
2004-05-12 10:18 ` mike
2004-05-12 10:19 ` mike [this message]
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=1084357146.24569.13.camel@datacontrol \
--to=mike@bristolreccc.co.uk \
--cc=aris@cathedrallabs.org \
--cc=linux-kernel@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