Jesse Brandeburg <[EMAIL PROTECTED]> wrote:
> On 7/14/05, Mikhail Kshevetskiy <[EMAIL PROTECTED]> wrote:
> > On Wed, 13 Jul 2005 23:28:15 -0700
> > Jesse Brandeburg <[EMAIL PROTECTED]> wrote:
> >
> > > On 7/13/05, Mikhail Kshevetskiy <[EMAIL PROTECTED]> wrote:
> > > > symptom
> > > > ===
> >
On 7/14/05, Mikhail Kshevetskiy <[EMAIL PROTECTED]> wrote:
> On Wed, 13 Jul 2005 23:28:15 -0700
> Jesse Brandeburg <[EMAIL PROTECTED]> wrote:
>
> > On 7/13/05, Mikhail Kshevetskiy <[EMAIL PROTECTED]> wrote:
> > > symptom
> > > ===
> > > modprobe e100
> > > ifconfig eth0 netmask
> > >
> > > r
Jesse Brandeburg <[EMAIL PROTECTED]> wrote:
> On 7/13/05, Mikhail Kshevetskiy <[EMAIL PROTECTED]> wrote:
> > symptom
> > ===
> > modprobe e100
> > ifconfig eth0 netmask
> >
> > result:
> > ===
> > SIOCADDRT: Network is unreachable
> >
> > There were no such error in 2.6.13-rc2
> odd, b
On Wed, 13 Jul 2005 23:28:15 -0700, Jesse Brandeburg <[EMAIL PROTECTED]> wrote:
>On 7/13/05, Mikhail Kshevetskiy <[EMAIL PROTECTED]> wrote:
>> symptom
>> ===
>> modprobe e100
>> ifconfig eth0 netmask
>>
>> result:
>> ===
>> SIOCADDRT: Network is unreachable
>>
>> There were no such err
On 7/13/05, Mikhail Kshevetskiy <[EMAIL PROTECTED]> wrote:
> symptom
> ===
> modprobe e100
> ifconfig eth0 netmask
>
> result:
> ===
> SIOCADDRT: Network is unreachable
>
> There were no such error in 2.6.13-rc2
odd, both e100 and eepro100 are broken? This might indicate something
wie