mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steve Kieu <haiquy@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: Very strange Marvell/Yukon Gigabit NIC networking problems
Date: Tue, 30 Aug 2005 18:35:12 +1000 (EST)	[thread overview]
Message-ID: <20050830083512.39846.qmail@web53603.mail.yahoo.com> (raw)


Hi all,

Ok it sound wierd enough to assume that the latest
kernel 2.6.13 ethernet driver has done something wrong
with the NIC and sustain the condition after reboot or
turn off the machine.

Here is my configuration.

Laptop Asus A4500d. dmesg shows:

eth0: Yukon Gigabit Ethernet 10/100/1000Base-T Adapter

It is working as normal with 2.6.12 and winXP before.
Today I did upgrade the kernel to 2.6.13 and it still
works. The problem is now I switch to the older kernel
that is 2.6.12.5 and .6  it no longer works. dmesg
shows like this:
     
eth0: Yukon Gigabit Ethernet 10/100/1000Base-T Adapter
      PrefPort:A  RlmtMode:Check Link State


Boot window XP now, and the link always shows that
media disconnected. So the NIC is unuseable with
WinXP, 2.6.12  __but__ still works with 2.6.13. and
power off the machine does not restore the NIC. 

Now of course I am forced to use not only linux but
version 2.6.13 :-) in order to have the NIC working!
Unfortuneately the HSF module with 2.6.13 is not
working because of unresolve symbol so the modem is
dead (I rarely usemodem anyway)

Please help me to recover my NIC back as normal. Thank
you very much indeed. If any other information is
needed pls ask.

Cheers,




S.KIEU

Send instant messages to your online friends http://au.messenger.yahoo.com 

             reply	other threads:[~2005-08-30  8:35 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-30  8:35 Steve Kieu [this message]
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
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=20050830083512.39846.qmail@web53603.mail.yahoo.com \
    --to=haiquy@yahoo.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

Powered by JetHome