From: Roy Dragseth <royd@cc.uit.no>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Re: Re: disabling nics using boot options.
Date: Thu, 09 Jan 2003 21:23:11 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590709805662@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805661@msgid-missing>
On Thursday 09 January 2003 21:48, Bill Nottingham wrote:
> Are there any error messages from the driver?
I find this in /var/log/messages
Jan 9 20:09:51 compute-1-1 kernel: Error seeking in /dev/kmem
Jan 9 20:09:51 compute-1-1 kernel: Symbol #tg3, value 001bc000
Jan 9 20:09:51 compute-1-1 kernel: Error adding kernel module table entry.
and this in dmesg:
tg3.c:v0.99 (Jun 11, 2002)
PCI: Found IRQ 56 for device 20:02.0
divert: allocating divert_blk for eth1
eth1: Tigon3 [partno(BCM95700A6) rev 0105 PHY(5701)] (PCI:66MHz:64-bit)
10/100/1
000BaseT Ethernet 00:30:6e:38:99:07
PCI: Found IRQ 65 for device 80:01.0
divert: allocating divert_blk for eth2
eth2: Tigon3 [partno(A6825-60101) rev 0105 PHY(5701)] (PCI:66MHz:64-bit)
10/100/
1000BaseT Ethernet 00:30:6e:2b:cc:05
eth2: Link is up at 1000 Mbps, full duplex.
eth2: Flow control is off for TX and off for RX.
ACPI: Power Button (FF) [PWRF]
ACPI: Sleep Button (FF) [SLPF]
eth2: Link is up at 1000 Mbps, full duplex.
eth2: Flow control is off for TX and off for RX.
I don't really know if these are real error messages.
r.
--
The Computer Center, University of Tromsø, N-9037 TROMSØ, Norway.
phone:+47 77 64 41 07, fax:+47 77 64 41 00
Roy Dragseth, High Performance Computing System Administrator
Direct call: +47 77 64 62 56. email: royd@cc.uit.no
next prev parent reply other threads:[~2003-01-09 21:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-09 20:48 [Linux-ia64] Re: Re: disabling nics using boot options Bill Nottingham
2003-01-09 21:23 ` Roy Dragseth [this message]
2003-01-10 21:39 ` Roy Dragseth
2003-01-11 0:06 ` Grant Grundler
2003-01-12 19:53 ` Roy Dragseth
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=marc-linux-ia64-105590709805662@msgid-missing \
--to=royd@cc.uit.no \
--cc=linux-ia64@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