From: Mikhail Kshevetskiy <kl@laska.dorms.spbu.ru>
To: linux-kernel@vger.kernel.org
Subject: e100, eepro100 modules -- can't up an interface (2.6.13-rc3 and above)
Date: Sun, 7 Aug 2005 06:12:10 +0400 [thread overview]
Message-ID: <20050807061210.6e97265b@laska> (raw)
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
reply other threads:[~2005-08-07 2:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050807061210.6e97265b@laska \
--to=kl@laska.dorms.spbu.ru \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®