From: Steve Kieu <haiquy@yahoo.com>
To: Daniel Drake <dsd@gentoo.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Very strange Marvell/Yukon Gigabit NIC networking problems
Date: Tue, 30 Aug 2005 20:52:09 +1000 (EST) [thread overview]
Message-ID: <20050830105210.11849.qmail@web53602.mail.yahoo.com> (raw)
In-Reply-To: <43143258.5080208@gentoo.org>
> Can you test the new skge driver instead? If that
> one is broken then we
Tested , not broken, working now but the same problem,
that is if I reboot to winXP or 2.6.12, 2.6.11, the
NIC is unusaeble. In XP it always says link is down,
or media disconnected (from ipconfig command output in
XP)
is it because the firmware of NIC has changed or any
reason?
I noticed warning messages only with 2.6.13
PCI: Failed to allocate mem resource #10:2000000@0 for
0000:02:01.0
and modem device in 2.6.13 IRQ is disabled.
ACPI: PCI Interrupt Link [LKMO] enabled at IRQ 20
ACPI: PCI Interrupt 0000:00:06.1[B] -> Link [LKMO] ->
GSI 20 (level, low) -> IRQ
17
ACPI: PCI interrupt for device 0000:00:06.1 disabled
not sure if it gives more information.
skge addr 0xfeaf8000 irq 19 chip Yukon-Lite rev 9
skge eth0: addr 00:11:d8:f2:1f:18
ACPI: PCI Interrupt 0000:02:01.0[A] -> Link [LNKB] ->
GSI 18 (level, low) -> IRQ
16
Yenta: CardBus bridge found at 0000:02:01.0
[1043:1987]
skge eth0: enabling interface
skge eth0: Link is up at 10 Mbps, half duplex, flow
control none
Not sure how can I restore this thing back to normal
(sigh)
Thanks
> probably have more chance of getting it fixed :)
>
> Thanks,
> Daniel
>
S.KIEU
Send instant messages to your online friends http://au.messenger.yahoo.com
next prev parent reply other threads:[~2005-08-30 10:52 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-30 8:35 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 [this message]
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
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=20050830105210.11849.qmail@web53602.mail.yahoo.com \
--to=haiquy@yahoo.com \
--cc=dsd@gentoo.org \
--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
Powered by JetHome