Re: Where to put module option in Etch?
On Thu, May 31, 2007 at 12:34:13PM +0200, Steffen.Pelzetter@nexans.com 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 configuration that the tulip module would be
loaded from an initramfs, instead of from the root file system? (You can
check this with zcat /boot/initrd.img-$version | cpio -t | grep tulip) Is
this dmesg output the result of boot-time loading of the module, or from
loading it with 'modprobe tulip'?
> But dmesg say's:
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Linux Tulip driver version 1.1.13-NAPI (May 11, 2002)
> tulip0: EEPROM default media type Autosense.
> tulip0: Index #0 - Media 10baseT (#0) described by a 21142 Serial PHY (2)
> block.
> tulip0: Index #1 - Media 10baseT-FDX (#4) described by a 21142 Serial PHY
> (2) block.
> tulip0: Index #2 - Media 100baseTx (#3) described by a 21143 SYM PHY (4)
> block.
> tulip0: Index #3 - Media 100baseTx-FDX (#5) described by a 21143 SYM PHY
> (4) block.
> eth0: Digital DS21143 Tulip rev 48 at fffffcf980008400, 00:00:F8:10:86:80,
> IRQ 20.
> tulip1: EEPROM default media type Autosense.
> tulip1: Index #0 - Media MII (#11) described by a 21140 MII PHY (1)
> block.
> tulip1: MII transceiver #5 config 0000 status 784b advertising 01e1.
> eth1: Digital DS21140 Tulip rev 34 at fffffcfb80008800, 00:06:2B:00:22:E3,
> IRQ 42.
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> Both nic's running in autosense mode.
>
> If I do a
>
> modprobe tulip options=5
>
> I got:
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Linux Tulip driver version 1.1.13-NAPI (May 11, 2002)
> tulip0: Transceiver selection forced to 100baseTx-FDX.
> tulip0: EEPROM default media type Autosense.
> tulip0: Index #0 - Media 10baseT (#0) described by a 21142 Serial PHY (2)
> block.
> tulip0: Index #1 - Media 10baseT-FDX (#4) described by a 21142 Serial PHY
> (2) block.
> tulip0: Index #2 - Media 100baseTx (#3) described by a 21143 SYM PHY (4)
> block.
> tulip0: Index #3 - Media 100baseTx-FDX (#5) described by a 21143 SYM PHY
> (4) block.
> eth0: Digital DS21143 Tulip rev 48 at fffffcf980008400, 00:00:F8:10:86:80,
> IRQ 20.
> tulip1: EEPROM default media type Autosense.
> tulip1: Index #0 - Media MII (#11) described by a 21140 MII PHY (1)
> block.
> tulip1: MII transceiver #5 config 1000 status 786f advertising 01e1.
> eth1: Digital DS21140 Tulip rev 34 at fffffcfb80008800, 00:06:2B:00:22:E3,
> IRQ 42.
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> So tulip0 is 100FDX but tulip1 is still autosense mode.
> What's going wrong?
> I need tulip1 at least configured in 100FDX.
Well, for one thing, I've never found that passing options to modprobe
actually /works/; I guess it's documented in the current manpage as being
possible, but I know in the not-so-distant past I've tried to do this and
had modprobe not honor options passed on the commandline. But I guess at
least in this case it's working for you.
The other thing, though, is that most kernel hardware drivers take their
hardware-related options as an array of options, one for each device they're
driving. So if you want both tulip0 and tulip1 to be brought up with
100FDX, then the correct syntax would be
modprobe tulip options=5,5
and under /etc/modprobe.d,
options tulip options=5,5
Cheers,
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
vorlon@debian.org http://www.debian.org/
Reply to: