From: Grant on
Hi there,

Tries a couple times to install slack-13 to an old pIII box and the
installer fails to setup the Intel pro/100 NIC with e100 driver.

I also tried to manually setup the NIC but the response to the
ifconfig command was something like SIO??? device not found message.

modprobe works and lsmod shows the driver is loaded along with mii.

Another possibility is that the tiny e100 firmware blob is missing?
There's no sign of it under /lib/firmware.

Anyone seen this issue?

Hmm, try the huge.s?

Nope, it does the same thing after auto setup NIC:

# ifconfig eth0 192.168.3.22 up
ifconfig: SIOCSIFFLAGS: No such file or directory

lsmod correctly shows e100 + mii are loaded.

What went wrong here?

Grant.
From: Morten L on
Grant <omg(a)grrr.id.au> skrev 2010-03-11:
> Hi there,
>
> Tries a couple times to install slack-13 to an old pIII box and the
> installer fails to setup the Intel pro/100 NIC with e100 driver.
>
> I also tried to manually setup the NIC but the response to the
> ifconfig command was something like SIO??? device not found message.
>
> modprobe works and lsmod shows the driver is loaded along with mii.
>
> Another possibility is that the tiny e100 firmware blob is missing?
> There's no sign of it under /lib/firmware.
>
> Anyone seen this issue?
>
> Hmm, try the huge.s?
>
> Nope, it does the same thing after auto setup NIC:
>
> # ifconfig eth0 192.168.3.22 up
> ifconfig: SIOCSIFFLAGS: No such file or directory
>
> lsmod correctly shows e100 + mii are loaded.
>
> What went wrong here?
>
> Grant.

I have seen something similar with t.ex. the tg3 netcard.
The module loaded, but the interface did not work. The only
solution I found was to use an older kernel.


--
Morten L

From: Thrash Dude on
On Fri, 12 Mar 2010 07:25:45 +1100, Grant wrote:

> Hi there,
>
> Tries a couple times to install slack-13 to an old pIII box and the
> installer fails to setup the Intel pro/100 NIC with e100 driver.
>
> I also tried to manually setup the NIC but the response to the ifconfig
> command was something like SIO??? device not found message.
>
> modprobe works and lsmod shows the driver is loaded along with mii.
>
> Another possibility is that the tiny e100 firmware blob is missing?
> There's no sign of it under /lib/firmware.
>
> Anyone seen this issue?
>
> Hmm, try the huge.s?
>
> Nope, it does the same thing after auto setup NIC:
>
> # ifconfig eth0 192.168.3.22 up
> ifconfig: SIOCSIFFLAGS: No such file or directory
>
> lsmod correctly shows e100 + mii are loaded.
>
> What went wrong here?
>
> Grant.

Do you have to have a static IP?

dhcpcd eth0 works here.
From: Grant on
On 11 Mar 2010 22:39:47 GMT, Thrash Dude <thrashdude(a)nowhere.com> wrote:

>On Fri, 12 Mar 2010 07:25:45 +1100, Grant wrote:
>
>> Hi there,
>>
>> Tries a couple times to install slack-13 to an old pIII box and the
>> installer fails to setup the Intel pro/100 NIC with e100 driver.
>>
>> I also tried to manually setup the NIC but the response to the ifconfig
>> command was something like SIO??? device not found message.
>>
>> modprobe works and lsmod shows the driver is loaded along with mii.
>>
>> Another possibility is that the tiny e100 firmware blob is missing?
>> There's no sign of it under /lib/firmware.
>>
>> Anyone seen this issue?
>>
>> Hmm, try the huge.s?
>>
>> Nope, it does the same thing after auto setup NIC:
>>
>> # ifconfig eth0 192.168.3.22 up
>> ifconfig: SIOCSIFFLAGS: No such file or directory
>>
>> lsmod correctly shows e100 + mii are loaded.
>>
>> What went wrong here?
>>
>> Grant.
>
>Do you have to have a static IP?
>
>dhcpcd eth0 works here.

Hmm, the auto setup (installer offers to setup NIC) would've got an IP
from the localnet DHCP server, that didn't work, nor did the static IP
manual setup.

Grant.
From: Grant on
On 11 Mar 2010 20:36:40 GMT, Morten L <ml47sp11am(a)gspmailam.com> wrote:

>Grant <omg(a)grrr.id.au> skrev 2010-03-11:
>> Hi there,
>>
>> Tries a couple times to install slack-13 to an old pIII box and the
>> installer fails to setup the Intel pro/100 NIC with e100 driver.
>>
>> I also tried to manually setup the NIC but the response to the
>> ifconfig command was something like SIO??? device not found message.
>>
>> modprobe works and lsmod shows the driver is loaded along with mii.
>>
>> Another possibility is that the tiny e100 firmware blob is missing?
>> There's no sign of it under /lib/firmware.
>>
>> Anyone seen this issue?
>>
>> Hmm, try the huge.s?
>>
>> Nope, it does the same thing after auto setup NIC:
>>
>> # ifconfig eth0 192.168.3.22 up
>> ifconfig: SIOCSIFFLAGS: No such file or directory
>>
>> lsmod correctly shows e100 + mii are loaded.
>>
>> What went wrong here?
>>
>> Grant.
>
>I have seen something similar with t.ex. the tg3 netcard.
>The module loaded, but the interface did not work. The only
>solution I found was to use an older kernel.

Yeah, I don't think slack-13 was much good for older hardware,
I'll burn a DVD and try installing from that.

Grant.