public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Brian Hall <brihall@pcisys.net>
To: Willy Tarreau <willy@w.ods.org>
Cc: Greg KH <greg@kroah.com>, Stephen Hemminger <shemminger@osdl.org>,
	Sergey Vlasov <vsu@altlinux.ru>, Brian Hall <brihall@pcisys.net>,
	Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org
Subject: Re: Help: DGE-560T not recognized by Linux
Date: Tue, 21 Feb 2006 20:51:00 -0700	[thread overview]
Message-ID: <20060222035100.GA6174@pcisys.net> (raw)
In-Reply-To: <20060220114341.GA7710@w.ods.org>

[-- Attachment #1: Type: text/plain, Size: 1414 bytes --]

On Mon, Feb 20, 2006 at 12:43:41PM +0100, Willy Tarreau wrote:
> Today, I had the *exact* same problem on one server equipped with the same
> card. I tried the patch above which did not change anything. However, I
> finally fixed it by simply enabling ACPI. Then it always works with and
> without the patch above. I could not test marvell's driver because it does
> not build on 2.6.16-rc4, but strangely my previous kernel on this machine
> was a 2.6.12-rc4-mm2 patched with marvell's driver and with ACPI disabled.
> 
> So it seems that marvell's driver on 2.6.12 was able to access config space
> even without ACPI while sky2 on 2.6.16-rc4 cannot. I have no idea why,
> unfortunately.
> 
> Just my 2 cents,
> Willy

Thanks for the input. As far as I can tell I do have ACPI enabled, and
sky2 still fails on 2.6.15, 2.6.16-rc3 or -rc4. See my attached dmesg
output and config.

Also, if you get the latest driver from Marvel it does apply to more
recent kernels (install-8_30.tar.bz2), 2.6.15 for sure.

I have the Marvell script generated patches for 2.6.15 and 
2.6.16-rc3 available, but they are 350K each compressed which seems
a bit large to email.

I made them available from my website if you are interested:

http://home.pcisys.net/~brihall/sk98lin_v8.30.2.3_2.6.15_patch.gz

http://home.pcisys.net/~brihall/sk98lin_v8.30.2.3_2.6.16_patch.gz

 
--
Brian Hall
Linux Consultant
http://pcisys.net/~brihall

[-- Attachment #2: config.gz --]
[-- Type: application/octet-stream, Size: 3747 bytes --]

[-- Attachment #3: 2.6.15-ck4.dmesg.txt.gz --]
[-- Type: application/octet-stream, Size: 5420 bytes --]

  parent reply	other threads:[~2006-02-22  3:51 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-18  5:27 Help: DGE-560T not recognized by Linux Brian Hall
2006-02-18  5:40 ` Randy.Dunlap
2006-02-18  6:24 ` Andrew Morton
2006-02-18  7:36   ` Brian Hall
2006-02-18  7:48     ` Andrew Morton
2006-02-18 15:54       ` Edgar Hucek
2006-02-18 17:01       ` Brian Hall
2006-02-18 19:29         ` Sergey Vlasov
2006-02-19  0:35           ` Stephen Hemminger
2006-02-19  1:04             ` Greg KH
2006-02-19 16:20               ` Brian Hall
2006-02-19 17:13                 ` Andi Kleen
2006-02-28 15:08                   ` Brian Hall
2006-02-20 11:43               ` Willy Tarreau
2006-02-20 12:56                 ` Sergey Vlasov
2006-02-22  3:51                 ` Brian Hall [this message]
2006-02-22 19:51                   ` Stephen Hemminger
2006-02-19  2:55       ` Brian Hall
2006-02-19  7:41         ` jerome lacoste

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=20060222035100.GA6174@pcisys.net \
    --to=brihall@pcisys.net \
    --cc=akpm@osdl.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shemminger@osdl.org \
    --cc=vsu@altlinux.ru \
    --cc=willy@w.ods.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