E100 Driver

[Christopher Chan]

On Sunday, November 07, 2010 12:00 AM, Tom H wrote:
> On Sat, Nov 6, 2010 at 8:10 AM, Christopher Chan
> <christopher.chan at bradbury.edu.hk>  wrote:
>> On Saturday, November 06, 2010 05:00 PM, Tom H wrote:
>>> On Sat, Nov 6, 2010 at 3:27 AM, Christopher Chan
>>> <christopher.chan at bradbury.edu.hk>    wrote:
>>>> On Saturday, November 06, 2010 03:20 PM, Joshua Wambua wrote:
>>>>> Output of dmesg | grep e100, cat /etc/modprobe.conf, mii-tool
>>>>>
>>>>> 1. dmesg | grep e100
>>>>>         [    0.223241] pci 0000:02:08:0 Firmware left e100 interrupts
>>>>> enabled; disabling
>>>>>         [    1.243888] e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI
>>>>>         [    1.243892] e100: Copyright(x) 1999-2006 Intel Corporation
>>>>>         [    1.243928] e100 0000:02:08.0: PCI INT A ->      GSI 20 (level, low)
>>>>> ->      IRQ 20
>>>>>         [    1.271516] e100 0000:02:08.0: PME# disabled
>>>>>         [    1.278460] e100: eth0: e100_probe: addr 0xf0101000, irq 20, MAC
>>>>> addr 00:1b:38:93:dc:71
>>>>>
>>>>> 2. cat /etc/modprobe.conf
>>>>>         cat: /etc/modprobe.conf: No such file or directory
>>>>>
>>>>> 3. mii-tool
>>>>>         eth0: negotiated 100baseTx-FD flow-control, link ok
>>>>
>>>> Boy...that means everything checks out...
>>>>
>>>> How is it configured on the Windows side? dhcp? static?
>>>>
>>>> What do you get from ifconfig -a, route -n, cat /etc.resolv.conf?
>>>
>>> Not quite."/etc/modprobe.conf" is deprecated. Joshua should grep for
>>> e100 in "/etc/modprobe.d" as an alternative.
>>
>> /me cringes at his /etc/modprobe.conf file...
>
> Soon, nothing'll be when it used to be. :)
>
> Thinking about it, given the output of "dmesg | grep e100", it's
> loading so checking modprode's no longer necessary.
>

Yeah, I was just wondering whether there were any options set for the 
driver. Especially options related to auto negotiation but since 
mii-tool's report checked out...