This isn't really an alpha-specific question, as the modprobe stuff is
the same whatever debian platform you use...
Ok sorry, you are right. But I put the question to the alpha port, because
the tulip cards are older ones and no more used by x86 systems. If it was
a
tulip spezific problem - I
Something is not working.
You can simply put:
options tulip options=5
in any (new) file under /etc/modprobe.d/ (I'd suggest
/etc/modprobe.d/tulip)
I created the tulip file in /etc/modprobe.d/ :
options tulip options=5
But dmesg say's:
On Thu, May 31, 2007 at 12:34:13PM +0200, [EMAIL PROTECTED] wrote:
You can simply put:
options tulip options=5
in any (new) file under /etc/modprobe.d/ (I'd suggest
/etc/modprobe.d/tulip)
I created the tulip file in /etc/modprobe.d/ :
options tulip options=5
Is there any reason in your
On Thu 31 May 2007, [EMAIL PROTECTED] wrote:
I created the tulip file in /etc/modprobe.d/ :
options tulip options=5
If you have more than one NIC that's driven by tulip, then perhaps you
need options=5,5 or something like that...
BTW, I use de4x5, not tulip. That works better for me.
If you have more than one NIC that's driven by tulip, then perhaps you
need options=5,5 or something like that...
Ok this works fine for modprobe. This sytax is exactly what I was looking
for.
But we have found out, that my tulip driver is loaded with initrd.
Any idear how to put the options
On Thu 31 May 2007, [EMAIL PROTECTED] wrote:
If you have more than one NIC that's driven by tulip, then perhaps you
need options=5,5 or something like that...
Ok this works fine for modprobe. This sytax is exactly what I was looking
for.
But we have found out, that my tulip driver is
No... that's why I never use initrd, too much hassle to modify trivial
things.
Ok, I've solved the problem.
I created a the file tulip in /etc/modprobe.d like Paul suggested:
options tulip options=5,5
After that both nic's where configured correctly by running
modprobe tulip
Perhaps
Hello,
I'm proudly using Etch on my two Alpha Server 4100 (Rawhide) for about
2 Month now.
There is only one thing I can't solve. My network card in the originally
NIC DEC 21xxx
using the tulip.ko module with 2.6.18-4-alpha-generic .
The driver is loaded and the network is running too, but with
On Fri 25 May 2007, [EMAIL PROTECTED] wrote:
So I made a test :
rmmod tulip
modprobe tulip options=5
The driver is loaded with 100 FDX and the performance is as expected.
Now I want to give the option value to the driver at boot time.
I was suprised that I couldn't find a
9 matches
Mail list logo
