public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Luis Miguel García" <ktech@wanadoo.es>
To: a.verweij@student.tudelft.nl, linux-kernel@vger.kernel.org,
	acpi-devel@lists.sourceforge.net, akpm@digeo.com
Subject: acpi problem with nforce motherboards and ethernet
Date: Thu, 05 Feb 2004 18:41:12 +0100	[thread overview]
Message-ID: <40228038.1070003@wanadoo.es> (raw)

Hi:

Since Andrew Morton picked up latest acpi bk updates, nforce motherboards have problems, mainly with ethernet adapters. Reporters say that with acpi=off, the problm gets fixed, so we think the problem could be acpi. Some more useful info:



On Tue, 3 Feb 2004, [ISO-8859-1] Luis Miguel García wrote:


>> When I try to boot with latest mm series (such as actual rc3-mm1 or
>> rc2-mm2), my nforce ethernet device doesn't works. It worked in the past
>> with the forcedeth reverse engineered driver but now it keeps for 30 or
>> more seconds halted (at boot) and then the network device dosn't run.
>>
>> Here is the dmesg of rc3-mm1. Do you want for me to test something? Thanks!
>>
>> P.S.:   The ACPI related messages are larger that in rc3.
>  
>

My e100 on an nforce2 won't work in rc3-mm1.
The "acpi=off" boot parameter makes it go.


And for the record, I can boot with that kernel and save one dmesg for you if you want. Only send me a request and I'll send it to you.

P.S.: Sent any messages you want directly to me as i'm not subscribed to acpi-devel.

Thanks,

Luis Miguel García





>Which part of nforce support are you talking about luis?

>On Thu, 5 Feb 2004, Andrew Morton wrote:


>> Luis Miguel Garc?a <ktech@wanadoo.es> wrote:
>  
>
>>> >
>>> > Andrew Morton wrote:
>>> >
>>    
>>
>>>> > >
>>>      
>>>
>>>>> > >> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.2/2.6.2-mm1/
>>>>> > >>
>>>>> > >>
>>>>> > >>
>>>>> > >> - Merged some page reclaim fixes from Nick and Nikita.  These yield some
>>>>> > >>  performance improvements in low memory and heavy paging situations.
>>>>> > >>
>>>>> > >>
>>>>        
>>>>
>>> >
>>> > Andrew, do you know if this acpi pull down has nforce support fixed?
>>    
>>
>>
>> It doesn't appear that way.
>>
>  
>
>>> > Or perhaps it's even unnotified to the acpi team?
>>    
>>
>>
>> I do not know.  Sending them a bugzilla ID would help, if such a thing exists.
>>
>>
>>
>> -------------------------------------------------------
>> The SF.Net email is sponsored by EclipseCon 2004
>> Premiere Conference on Open Tools Development and Integration
>> See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
>> http://www.eclipsecon.org/osdn
>> _______________________________________________
>> Acpi-devel mailing list
>> Acpi-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/acpi-devel
>>
>>
>  
>

             reply	other threads:[~2004-02-05 17:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-05 17:41 Luis Miguel García [this message]
2004-02-05 18:41 ` [ACPI] acpi problem with nforce motherboards and ethernet Arjen Verweij

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=40228038.1070003@wanadoo.es \
    --to=ktech@wanadoo.es \
    --cc=a.verweij@student.tudelft.nl \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=akpm@digeo.com \
    --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