Re: [PATCH] Gigabit Ethernet support for forcedeth

[Manfred Spraul]

Tim Waugh wrote:

> On Fri, Jul 30, 2004 at 06:52:15PM +0200, Manfred Spraul wrote:
>
>  
>
> > The log is very odd - why are there two lines with
> >
> >    
> >
> > > forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.28.
> > >      
> > Did you rmmod/insmod the driver twice?
> >    
>
> I think it's just the way that ifup works.  I'm not entirely sure why
> the line appears twice.
>
>  
>
> > Could you manually insmod the driver, wait for two seconds and then call 
> > ifup?
> >    
>
> Aha.  That works fine.
>
> So here is how to make it fail:
>
> /sbin/modprobe forcedeth; \
> /sbin/ip link set dev eth0 up
>
> All subsequent runs of 'ethtool eth0' show:
>
> Settings for eth0:
>        Supports Wake-on: g
>        Wake-on: d
>        Link detected: no
>
> regardless of how long I leave it.
>
> So is this a driver problem or a problem with the way /sbin/ifup
> works?
>
>  
Driver problem.
The driver assumes that the nic generates an NVREG_IRQ_LINK interrupt 
with NvRegMIIStatus & NVREG_MIISTAT_LINKCHANGE on a link change. It 
seems your nic doesn't generate that.

Could you try modprobe forcedeth;sleep 5;ip link set dev eth0 up. Then 
pull out the network cable and check if the driver noticed that with 
ethtool. Plug in back in and check again. With dprintk enabled. Then 
send me the kernel log and the ethtool output.

And add the lspci -vxx -s 00:05.0. Probably I'll make the timer 
dependant on nForce 1-3 and exclude the nForce 3 Gb nics: they don't 
need it.

--
   Manfred
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/