e100, eepro100 modules -- can't up an interface (2.6.13-rc3 andabove)

[Mikhail Kshevetskiy]

Hi, all.

I can't up my network interface. This problem appear in 2.6.13-rc3 and
still exist. This is the part of strace for "ifconfig eth0 <ip> netmask
<mask>".
==========================================================================
uname({sys="Linux", node="laska", ...}) = 0 access("/proc/net",
R_OK)               = 0 access("/proc/net/unix", R_OK)          = 0
socket(PF_FILE, SOCK_DGRAM, 0)          = 3
socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 4
access("/proc/net/if_inet6", R_OK)      = -1 ENOENT (No such file or
directory) access("/proc/net/ax25", R_OK)          = -1 ENOENT (No such
file or directory) access("/proc/net/nr", R_OK)            = -1 ENOENT
(No such file or directory) access("/proc/net/ipx", R_OK)           = -1
ENOENT (No such file or directory) access("/proc/net/appletalk",
R_OK)     = -1 ENOENT (No such file or directory) access("/proc/net/x25",
R_OK)           = -1 ENOENT (No such file or directory) ioctl(4,
SIOCSIFADDR, 0xbfa53de0)       = 0 ioctl(4, SIOCGIFFLAGS,
0xbfa53d10)      = 0 ioctl(4, SIOCSIFFLAGS, 0xbfa53d10)      = -1 ENOSYS
(Function not implemented) dup(2)                                  = 5
fcntl64(5, F_GETFL)                     = 0x2 (flags O_RDWR)
fstat64(5, {st_mode=S_IFCHR|0720, st_rdev=makedev(136, 0), ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)
= 0xb7f35000 _llseek(5, 0, 0xbfa53b9c, SEEK_CUR)     = -1 ESPIPE (Illegal
seek) write(5, "SIOCSIFFLAGS: Function not imple"..., 39) = 39
close(5)                                = 0
munmap(0xb7f35000, 4096)                = 0
ioctl(4, SIOCSIFNETMASK, 0xbfa53de0)    = 0
exit_group(0)                           = ?
============================================================================
PS: I have 2 ethernet cards: e100 and via-rhine. The problem appear only
for e100.

PPS: please CC me, as I am not in list

Mikhail Kshevetskiy
-
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/