From: Andrew Morton <akpm@zip.com.au>
To: Rahul Karnik <rahul@genebrew.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 3Com 556B Tornado not working
Date: Fri, 22 Mar 2002 14:06:00 -0800 [thread overview]
Message-ID: <3C9BAAC8.15580DE@zip.com.au> (raw)
In-Reply-To: <3C9822CD.47ED9565@zip.com.au> <58299.165.89.84.249.1016832733.squirrel@porsche.genebrew.com>
Rahul Karnik wrote:
>
> Andrew,
>
> > And try another you-know-which operating system. If that works OK then
> > we know the hardware's good.
>
> Finally bit the bullet and installed Windows 2000 on the laptop. Now the
> card works fine. This means the hardware is good (Thank God!), and that the
> vortex driver needs to be fixed.
>
> By the way, I contacted some of the other people who noted similar behavior
> with this card on the vortex mailing list and they confirmed that their
> problems continue. Being a developer, I would really like to ditch the
> Windows install; how can I help debug this problem?
Well, please work off current 2.4.18/2.4.19-pre kernels.
Apply http://www.zip.com.au/~akpm/3c59x.patch so that
we're in sync.
Have a BIOS fiddle - disable any power management options,
disable APM/ACPI in kernel config, etc.
Then please go through the steps in the final section of
vortex.txt and send me all the output.
The 556 and 556B documentation has never been sighted,
but it's probably something silly. Also please send
me the `lspci -vvvxxx' output when the card is fully
initialised, so I can compare it with my 556b.
Thanks.
-
prev parent reply other threads:[~2002-03-22 22:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-20 3:19 3Com 556B Tornado not working Rahul Karnik
2002-03-20 5:49 ` Andrew Morton
2002-03-21 15:50 ` Rahul Karnik
2002-03-22 21:32 ` Rahul Karnik
2002-03-22 22:06 ` Andrew Morton [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=3C9BAAC8.15580DE@zip.com.au \
--to=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=rahul@genebrew.com \
/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