Re: epic100 aka smc etherpower II

2001-04-01 Thread Francois Romieu

Daniel Nofftz <[EMAIL PROTECTED]> écrit :
[...]
> i can`t get my smc etherpower ii working with the 2.4.3 kernel.
> now i have downgraded to 2.4.2 and it works again ...
> does anyone have a suggestion, what the problem is ?
[...]
> Mar 31 19:23:29 hyperion kernel: eth0: Setting half-duplex based on MII
> xcvr 3 register read of 0001.
> Mar 31 19:23:29 hyperion kernel: Real Time Clock Driver v1.10d
> Mar 31 19:23:29 hyperion kernel: eth0: Setting full-duplex based on MII #3
> link partner capability of 45e1.
> Mar 31 19:24:31 hyperion kernel: NETDEV WATCHDOG: eth0: transmit timed out

How does it behave if you give it the following args:
options=4
full_duplex=4

> lspci output:
[...]

No USB controller ?

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



Re: epic100 aka smc etherpower II

2001-04-01 Thread Francois Romieu

Daniel Nofftz [EMAIL PROTECTED] crit :
[...]
 i can`t get my smc etherpower ii working with the 2.4.3 kernel.
 now i have downgraded to 2.4.2 and it works again ...
 does anyone have a suggestion, what the problem is ?
[...]
 Mar 31 19:23:29 hyperion kernel: eth0: Setting half-duplex based on MII
 xcvr 3 register read of 0001.
 Mar 31 19:23:29 hyperion kernel: Real Time Clock Driver v1.10d
 Mar 31 19:23:29 hyperion kernel: eth0: Setting full-duplex based on MII #3
 link partner capability of 45e1.
 Mar 31 19:24:31 hyperion kernel: NETDEV WATCHDOG: eth0: transmit timed out

How does it behave if you give it the following args:
options=4
full_duplex=4

 lspci output:
[...]

No USB controller ?

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



Re: epic100 aka smc etherpower II

2001-03-31 Thread Arnd Bergmann

Daniel Nofftz <[EMAIL PROTECTED]> wrote:

> i can`t get my smc etherpower ii working with the 2.4.3 kernel.
> now i have downgraded to 2.4.2 and it works again ...
> does anyone have a suggestion, what the problem is ?

Looks to me like the problem I had in Febuary, see the thread
"epic100 in current -ac kernels" at 
http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg28523.html
After I had upgraded my BIOS, the problems were gone and I stopped
looking into it. The DMA mapping code first introduced in 2.4.0-ac2
(smallest diff here) originally triggered the bug, which had different
symptoms depending on the configuration of the chipset.
Note that I have a VIA VT8363 (KT133) chipset while this is a VT82C595 
(VP2) chipset, so it is appearantly not limited to one very specific 
configuration.

Arnd <><


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



Re: epic100 aka smc etherpower II

2001-03-31 Thread Arnd Bergmann

Daniel Nofftz [EMAIL PROTECTED] wrote:

 i can`t get my smc etherpower ii working with the 2.4.3 kernel.
 now i have downgraded to 2.4.2 and it works again ...
 does anyone have a suggestion, what the problem is ?

Looks to me like the problem I had in Febuary, see the thread
"epic100 in current -ac kernels" at 
http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg28523.html
After I had upgraded my BIOS, the problems were gone and I stopped
looking into it. The DMA mapping code first introduced in 2.4.0-ac2
(smallest diff here) originally triggered the bug, which had different
symptoms depending on the configuration of the chipset.
Note that I have a VIA VT8363 (KT133) chipset while this is a VT82C595 
(VP2) chipset, so it is appearantly not limited to one very specific 
configuration.

Arnd 


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