On Thursday 23 January 2003 22:03, David Bolin wrote:
> OK, I admit to my mistake. It is not the acip that needs to be disabled,
> it is apci. Once I corrected myself the recompiled kernel works correctly
> with the USB and the VIA-Rhine devices. Sorry about my mis-information.
>
This is most i
OK, I admit to my mistake. It is not the acip that needs to be disabled,
it is apci. Once I corrected myself the recompiled kernel works correctly
with the USB and the VIA-Rhine devices. Sorry about my mis-information.
>> John Allen wrote:
>>
>>>On Thursday 23 January 2003 12:19, Chmouel Boudjn
> John Allen wrote:
>
>>On Thursday 23 January 2003 12:19, Chmouel Boudjnah wrote:
>>
>>
>>>John Allen <[EMAIL PROTECTED]> writes:
>>>
>>>
The via-rhine driver loads fine, and ifstatus says there is a link
heartbeat, but no traffic ever goes through the interface.
>>>via-rhine wo
John Allen wrote:
On Thursday 23 January 2003 12:19, Chmouel Boudjnah wrote:
John Allen <[EMAIL PROTECTED]> writes:
The via-rhine driver loads fine, and ifstatus says there is a link
heartbeat, but no traffic ever goes through the interface.
via-rhine works fine, are you sure you h
On Thursday 23 January 2003 12:19, Chmouel Boudjnah wrote:
> John Allen <[EMAIL PROTECTED]> writes:
> > The via-rhine driver loads fine, and ifstatus says there is a link
> > heartbeat, but no traffic ever goes through the interface.
>
> via-rhine works fine, are you sure you have your network prop
John Allen <[EMAIL PROTECTED]> writes:
> The via-rhine driver loads fine, and ifstatus says there is a link heartbeat,
> but no traffic ever goes through the interface.
via-rhine works fine, are you sure you have your network properly
configured ?
The via-rhine driver loads fine, and ifstatus says there is a link heartbeat,
but no traffic ever goes through the interface.
The onboard lan is a VIA-RHINE 6102.
--
John Allen, Email: mailto:[EMAIL PROTECTED]