From: Joel Soete <soete.joel@tiscali.be>
To: Joel Soete <soete.joel@tiscali.be>
Cc: "M. Grabert" <xam@cs.ucc.ie>, parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] C110 builtin nic slow?
Date: Fri, 21 Nov 2003 22:37:26 +0000 [thread overview]
Message-ID: <3FBE93A6.9010008@tiscali.be> (raw)
In-Reply-To: <3FBE8732.2050705@tiscali.be>
Hi all,
Joel Soete wrote:
> Hi all,
>
>
> Joel Soete wrote:
>
>>
>>
>> M. Grabert wrote:
>>
>>> Sorry to reply myself,
>>
>>
> this is me now ;)
Again, apologies
>
> A small follow-up: I exchange my 3com with another hp nic (the same as
> the first one).
>
> The pb now, is that the new one become eth0 (and works fine) but the old
> one (which would be eth1) is not any-more usable (no means to configure
> to setup and configure it):
> # cat /proc/pci
> [...]
> Bus 0, device 11, function 0:
> Ethernet controller: Hewlett-Packard Company J2585B HP 10/100VG PCI
> LAN Ada
> ter (rev 0).
> IRQ 9.
> Master Capable. Latency=64. Min Gnt=8.Max Lat=32.
> I/O at 0xe000 [0xe0ff].
> Non-prefetchable 32 bit memory at 0xeb000000 [0xeb001fff].
> Bus 0, device 12, function 0:
> Ethernet controller: Hewlett-Packard Company J2585B HP 10/100VG PCI
> LAN Ada
> ter (#2) (rev 0).
> IRQ 10.
> Master Capable. Latency=64. Min Gnt=8.Max Lat=32.
> I/O at 0xe400 [0xe4ff].
> Non-prefetchable 32 bit memory at 0xeb002000 [0xeb003fff].
> [...]
>
> Any idea?
>
I found: ether=9,0,eth0 ether=10,0,eth1 as additional bootparam.
It works but I am confused:
at the office I also have two nic (well of tulip model) on my b2k but I
never have to add any bootparam to make recognise the second card?
Is it linked with the model capability?
Thanks,
Joel
PS: ft problem seems to be solved :)
hmm this 3com works perfectly with 10BT-hd at the office but connected
this time to a hub (10BT capable) :0
next prev parent reply other threads:[~2003-11-21 22:37 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-10 11:10 [parisc-linux] C110 builtin nic slow? Joel Soete
2003-11-10 12:31 ` Joel Soete
2003-11-10 14:00 ` Joel Soete
2003-11-10 17:35 ` Grant Grundler
2003-11-11 12:54 ` Joel Soete
2003-11-12 3:22 ` Grant Grundler
2003-11-15 19:41 ` Joel Soete
2003-11-15 22:56 ` M. Grabert
2003-11-15 23:22 ` [parisc-linux] Dual NICs on 9000/715, anyone? buggz
2003-11-15 23:34 ` Matthew Wilcox
2003-11-15 23:50 ` buggz
2003-11-16 1:51 ` Grant Grundler
2003-11-16 4:16 ` Shane G. Brodie
2003-11-16 4:32 ` Grant Grundler
2003-11-15 23:58 ` [parisc-linux] C110 builtin nic slow? M. Grabert
2003-11-16 17:00 ` Joel Soete
2003-11-21 21:44 ` Joel Soete
2003-11-21 22:37 ` Joel Soete [this message]
2003-11-16 16:53 ` Joel Soete
2003-11-10 17:37 ` Grant Grundler
2003-11-10 19:23 ` Joel Soete
2003-11-10 20:38 ` Joel Soete
2003-11-11 1:31 ` M. Grabert
2003-11-11 11:45 ` Joel Soete
-- strict thread matches above, loose matches on Subject: below --
2003-10-26 16:49 Joel Soete
2003-10-26 17:25 ` Grant Grundler
2003-10-26 20:40 ` Joel Soete
2003-10-26 21:10 ` Joel Soete
2003-10-27 19:39 ` Grant Grundler
2003-10-27 20:13 ` Matthew Wilcox
2003-10-28 8:39 ` Joel Soete
2003-10-28 19:32 ` Joel Soete
2003-10-28 19:34 ` Matthew Wilcox
2003-10-29 6:43 ` Joel Soete
2003-11-10 4:36 ` Grant Grundler
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=3FBE93A6.9010008@tiscali.be \
--to=soete.joel@tiscali.be \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=xam@cs.ucc.ie \
/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