public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: guorke <gourke@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: 2.6.12 can not support via rhine?
Date: Thu, 23 Jun 2005 12:17:58 +0800	[thread overview]
Message-ID: <d73ab4d005062221176e77a960@mail.gmail.com> (raw)

hi
when i reboot use 2.6.11,it's ok.
but when i use 2.6.12 kernel, i get this:

via rhine device dose not seem to be present , delaying eth0 initialzation..
but in 2.6.11, it's say ok, I must say i have add via rhine support.
this following is difference output demsg :
diff -y dmesg_2.6.11 dmesg_2.6.12

VFS: Mounted root (ext3 filesystem) readonly.                   VFS:
Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 220k freed                      |
Freeing unused kernel memory: 224k freed
kjournald starting.  Commit interval 5 seconds                <
EXT3 FS on hda1, internal journal                               EXT3
FS on hda1, internal journal
Adding 265064k swap on /dev/hda2.  Priority:-1 extents:1        Adding
265064k swap on /dev/hda2.  Priority:-1 extents:1
via-rhine.c:v1.10-LK1.2.0-2.6 June-10-2004 Written by Donald  <
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 12             <
PCI: setting IRQ 12 as level-triggered                        <
ACPI: PCI interrupt 0000:00:09.0[A] -> GSI 12 (level, low) -> <
eth0: VIA Rhine II at 0x1e800, 00:05:5d:fb:7d:29, IRQ 12.     <
eth0: MII PHY found at address 8, status 0x782d advertising 0 <
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1               <

like no via rhine.

Thanks

             reply	other threads:[~2005-06-23  4:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-23  4:17 guorke [this message]
2005-06-23  4:21 ` 2.6.12 can not support via rhine? guorke
2005-06-23  5:04   ` guorke
2005-06-23 18:09 ` Bjorn Helgaas

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=d73ab4d005062221176e77a960@mail.gmail.com \
    --to=gourke@gmail.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