From: Serguei Miridonov <mirsev@cicese.mx>
To: Damian Kolkowski <deimos@deimos.one.pl>
Cc: Grzegorz Jaskiewicz <gj@pointblue.com.pl>, linux-kernel@vger.kernel.org
Subject: Re: via-rhine strange behavior 2.4.21-rc8
Date: Fri, 13 Jun 2003 11:06:56 -0700 [thread overview]
Message-ID: <3EEA12C0.E15DBAF2@cicese.mx> (raw)
In-Reply-To: 20030613170426.GB573@deimos.one.pl
Are you sure that ACPI is the reason? Grzegorz Jaskiewicz wrote about generic
2.4.21-rc8 = 2.4.21 which does not have the new ACPI code.
Damian Kolkowski wrote:
> On Thu, Jun 12, 2003 at 12:27:02PM +0100, Grzegorz Jaskiewicz wrote:
> > I attached dmesg from one of my test toys (servers). I am not able to get
> > via-rhine card to work on it :/
>
> Hi I have via-rhine to on my ECS_L7VTA and whenever I use ACPId thet network
> card is not working.
>
> So.., remove ACPI form kernel :-)
>
> > Local APIC disabled by BIOS -- reenabling.
> > Found and enabled local APIC!
>
> Maby if we have some not integrated network card based on via-rhine we could
> heck it why ACPI locks via-rhine; but there in probably no via-rhine outside
> the main bord :-)
>
> --
> # Damian *dEiMoS* Ko³kowski # http://deimos.one.pl/ #
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Serguei Miridonov
next prev parent reply other threads:[~2003-06-13 17:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-12 11:27 via-rhine strange behavior 2.4.21-rc8 Grzegorz Jaskiewicz
2003-06-13 17:04 ` Damian Kolkowski
2003-06-13 18:06 ` Serguei Miridonov [this message]
2003-06-13 17:59 ` Damian Kołkowski
2003-06-14 5:11 ` Damian Kołkowski
2003-06-14 10:12 ` Grzegorz Jaskiewicz
2003-06-14 16:12 ` Damian Kołkowski
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=3EEA12C0.E15DBAF2@cicese.mx \
--to=mirsev@cicese.mx \
--cc=deimos@deimos.one.pl \
--cc=gj@pointblue.com.pl \
--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.