From: "Tom Sightler" <ttsig@tuxyturvy.com>
To: "Chris Meadors" <clubneon@hereintown.net>,
"Andrew Morton" <akpm@zip.com.au>
Cc: "linux-kernel" <linux-kernel@vger.kernel.org>
Subject: Re: 3c556 basicly not working.
Date: Sun, 4 Nov 2001 08:51:51 -0500 [thread overview]
Message-ID: <008201c16537$e0176200$3a01a8c0@zeusinc.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0111040418050.28366-100000@clubneon.clubneon.com>
> On Sat, 3 Nov 2001, Andrew Morton wrote:
>
> > I've never seen a satisfactory explanation for this one. Usually
> > it's fixed by altering the `PnP OS' setting in the BIOS.
>
> Well I just looked, it is as I feared. There is not PnP OS or
> Windows/Other setting in the BIOS of this laptop.
>
> Anything else you can think of?
I experienced some similar problems when I first received my Dell Latitude
C810 which has the same card. In my case the card worked fine after
upgrading to the latest BIOS from Dell.
Interestingly, the card has a similar problem in Windows ME in that it's
won't initialize properly on first boot, but if I remove and reinstall the
driver it comes right up.
I think the problem is that the BIOS fails to initialize the PCI bridge
properly, but this is a total guess.
Anyway, my suggestion would be to verify that you have the most current BIOS
for your system, and select any options at all that would indicate a legacy
system. Also, another stupid suggestion is to try ACPI in the kernel, a
friend of mine insist that his card started working after he simply compiled
in ACPI, he thinks the bridge was brought up in standby mode and somehow
ACPI fixed this (I'm skeptical, but it is just a suggestion).
Later,
Tom
next prev parent reply other threads:[~2001-11-04 18:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-04 3:33 3c556 basicly not working Chris Meadors
2001-11-04 4:10 ` Andrew Morton
2001-11-04 9:20 ` Chris Meadors
2001-11-04 9:30 ` Andrew Morton
2001-11-04 13:51 ` Tom Sightler [this message]
2001-11-04 21:01 ` Chris Meadors
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='008201c16537$e0176200$3a01a8c0@zeusinc.com' \
--to=ttsig@tuxyturvy.com \
--cc=akpm@zip.com.au \
--cc=clubneon@hereintown.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.