From: Kalin KOZHUHAROV <kalin@thinrope.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Very strange Marvell/Yukon Gigabit NIC networking problems
Date: Tue, 13 Sep 2005 01:01:39 +0900 [thread overview]
Message-ID: <dg48qi$p96$1@sea.gmane.org> (raw)
In-Reply-To: <dg1s37$kd4$1@sea.gmane.org>
Kalin KOZHUHAROV wrote:
> Daniel Drake wrote:
>
>> Hi,
>>
>> Steve Kieu wrote:
>>
>>> If run 2.6.13 and up the NIC, it is working. Shuttdown or
>>> reboot using /sbin/halt (means power completely off and on)
>>> or /sbin/reboot all other OSs failed to enable the NIC except
>>> 2.6.13.
>>>
>>> to restore the normal working of the NIC, boot 2.6.13 and do
>>> a hot power reset. (press the reset button)
>>
>>
>>
>> Stephen recently posted a patch which looks like it might solve
>> this issue.
>>
>> Steve, maybe you could test it out? I have attached it to this
>> Gentoo bug:
>>
>> http://bugs.gentoo.org/100258
>>
>> Stephen, thanks for your hard work!
>
>
> I will try this one on a problematic ASUS board than now runs on
> 2.11.11 with sk98lin-8.18.2.2.patch.
>
> Applied the patch from #100258 to 2.6.13.1 successfully (some
> lines offset) and recompiled. Will try it tomorrow when I am at
> the machine.
Well, I did test it, but skge didn't even find the hardware :-(
No device was created, no dmesg output on load.
Instead I am running 2.6.13.1 with sk98lin-8.23.1.3.patch
The MB is ASUS P5GDC-V-Deluxe and the the on-board NIC:
# lspci -v -s 02:00.0
0000:02:00.0 Ethernet controller: Marvell Technology Group Ltd.
88E8053 Gigabit Ethernet Controller (rev 15)
Subsystem: ASUSTeK Computer Inc. Marvell 88E8053 Gigabit
Ethernet Controller (Asus)
Flags: bus master, fast devsel, latency 0, IRQ 17
Memory at cfffc000 (64-bit, non-prefetchable) [size=16K]
I/O ports at d800 [size=256]
Expansion ROM at cffc0000 [disabled] [size=128K]
Capabilities: [48] Power Management version 2
Capabilities: [50] Vital Product Data
Capabilities: [5c] Message Signalled Interrupts: 64bit+
Queue=0/1 Enable-
Capabilities: [e0] #10 [0011]
I am not sure it is supposed to be used with the skge driver, but I
thought it will work... Some ASUS boards apparently have problems
with the VPD being broken, but I am not sure how to check that.
> BTW, is this patch submitted to the Linus or -mm tree already?
??
Kalin.
--
|[ ~~~~~~~~~~~~~~~~~~~~~~ ]|
+-> http://ThinRope.net/ <-+
|[ ______________________ ]|
next prev parent reply other threads:[~2005-09-12 16:06 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-30 8:35 Very strange Marvell/Yukon Gigabit NIC networking problems Steve Kieu
2005-08-30 9:56 ` Daniel Drake
2005-08-30 9:58 ` Steve Kieu
2005-08-30 10:18 ` Daniel Drake
2005-08-30 10:24 ` Steve Kieu
2005-08-30 10:52 ` Steve Kieu
2005-08-30 11:54 ` Daniel Drake
2005-08-30 12:29 ` Steve Kieu
2005-08-30 13:31 ` Daniel Drake
2005-08-30 20:18 ` Jesse Brandeburg
2005-08-30 20:39 ` Stephen Hemminger
2005-08-30 20:50 ` Steve Kieu
2005-08-30 21:05 ` Stephen Hemminger
2005-08-30 21:49 ` Steve Kieu
2005-08-30 22:29 ` Stephen Hemminger
2005-08-31 0:09 ` Steve Kieu
2005-09-01 17:59 ` Stephen Hemminger
2005-08-31 9:56 ` Daniel Drake
2005-09-01 18:09 ` Stephen Hemminger
2005-09-01 21:21 ` Steve Kieu
2005-09-01 21:45 ` Howard Chu
2005-09-11 15:24 ` Daniel Drake
2005-09-11 18:12 ` Kalin KOZHUHAROV
2005-09-12 16:01 ` Kalin KOZHUHAROV [this message]
2005-09-12 16:50 ` Daniel Drake
2005-09-12 17:34 ` Kalin KOZHUHAROV
2005-09-12 0:02 ` Steve Kieu
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='dg48qi$p96$1@sea.gmane.org' \
--to=kalin@thinrope.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.