[SuSE Linux] SIOCIFADDR: operation not permitted by device
After recompiling my kernel i see messages during boot up like: SIOCIFADDR: Operation not permitted by device Eth0: unknown interface SIOCIFBRDADDR: Operation not permitted by device Eth0: unknown interface SIOCIFNETMASK: Operation not permitted by device Eth0: unknown interface What does that mean? (It does not show up in /var/log/{messages,boot.log}! -- Hartelijke groet, Wybo Dekker ___________________Servalys Analytical Chemistry Services__________________ wybo@servalys.hobby.nl | Deilsedijk 60 | tel +31-345-652164 www.hobby.nl/~servalys | 4158 CH Deil, The Netherlands | fax +31-345-652383 - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archive at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>
SIOCIFADDR: Operation not permitted by device Eth0: unknown interface /var/log/messages should say something about installing
Wybo Dekker wrote: the NW-Card driver ... (at bootup) Afterwards, ifconfig should bind eth0 to the NW-Card. 1. Does the driver work? 2. Did you configure the NW (with YAST)? 3. Does your new Kernel support Networking? bye, -- jk | Johann S. Kappacher +--------+ <A HREF="http://surf.to/Kappacher"><A HREF="http://surf.to/Kappacher</A">http://surf.to/Kappacher</A</A>> | | Gellertgasse 21/4/19 | Hannes | voice: +43-1-6066763 | | A-1100 Wien/Vienna +--------+ GSM: +43-676-3743268 | +------- Registered: Linux#105444 PGP: <A HREF="http://pgp5.ai.mit.edu"><A HREF="http://pgp5.ai.mit.edu</A">http://pgp5.ai.mit.edu</A</A>> -------+ - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archive at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>
Wybo Dekker wrote:
After recompiling my kernel i see messages during boot up like:
SIOCIFADDR: Operation not permitted by device Eth0: unknown interface SIOCIFBRDADDR: Operation not permitted by device Eth0: unknown interface SIOCIFNETMASK: Operation not permitted by device Eth0: unknown interface
What does that mean? (It does not show up in /var/log/{messages,boot.log}!
-- Hartelijke groet, Wybo Dekker ___________________Servalys Analytical Chemistry Services__________________ wybo@servalys.hobby.nl | Deilsedijk 60 | tel +31-345-652164 www.hobby.nl/~servalys | 4158 CH Deil, The Netherlands | fax +31-345-652383 - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archive at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>
Glad you asked! You're not the only one - I got the same thing when I compiled the 2.2.1 kernel and tried to run it. I certainly hope someone responds to this. Did you know that you also have to replace referenes to your /dev/cua devices by references to /dev/ttyS devices? (Doing so doesn't affect this problem, though.) Paul - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archive at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>
On Wed, 3 Mar 1999, Paul W. Abrahams wrote in response to Wybo Dekker:
Glad you asked! You're not the only one - I got the same thing when I compiled the 2.2.1 kernel and tried to run it. I certainly hope someone responds to this.
Did you know that you also have to replace referenes to your /dev/cua devices by references to /dev/ttyS devices? (Doing so doesn't affect this problem, though.)
Paul, I gathered from earlier postings that you have the 5.3 distribution. Did you have to upgrade your versions of libc, ppp, binutils, etc as described in the CHANGES document that comes with the kernel? If so, where did you get the upgrades? What particular directories etc. at the SuSE site if you got any there? I recently downloaded a number of upgrades from the 6.0 and 6.0 evaluation directories at the SuSE ftp site and installed them at one fell swoop in preparation for upgrading to 2.2.1. I couldn't boot afterwards so I have since uninstalled them and replaced them with the versions on my 5.1 CD. I'd like to try again, upgrading one utility/set of libraries at a time this time around <g> so if anything breaks isolating and replacing the offending upgrade will be easier. Thanks, Jesse - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archive at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>
Jesse McDonnell wrote:
On Wed, 3 Mar 1999, Paul W. Abrahams wrote in response to Wybo Dekker:
Glad you asked! You're not the only one - I got the same thing when I compiled the 2.2.1 kernel and tried to run it. I certainly hope someone responds to this.
Did you know that you also have to replace referenes to your /dev/cua devices by references to /dev/ttyS devices? (Doing so doesn't affect this problem, though.)
Paul, I gathered from earlier postings that you have the 5.3 distribution. Did you have to upgrade your versions of libc, ppp, binutils, etc as described in the CHANGES document that comes with the kernel? If so, where did you get the upgrades? What particular directories etc. at the SuSE site if you got any there?
I recently downloaded a number of upgrades from the 6.0 and 6.0 evaluation directories at the SuSE ftp site and installed them at one fell swoop in preparation for upgrading to 2.2.1. I couldn't boot afterwards so I have since uninstalled them and replaced them with the versions on my 5.1 CD.
I'd like to try again, upgrading one utility/set of libraries at a time this time around <g> so if anything breaks isolating and replacing the offending upgrade will be easier.
I knew about the upgrades mentioned in CHANGES, but I decided to try the kernel anyway without them - and your experience suggests I did the right thing. I too wondered where to find them, but never put much effort into getting the answer. Right now I'm set up with the 2.2.1 kernel listed in Lilo but not as the default. My system runs fine with the older kernel, but I'm sure I'd gain benefits from moving to the new one. What concerns me about the libc upgrade et al is that it might not work with the older kernel, so one I do it I'm committed (and possibly stuck). I'll probably wait until SuSE 6.1 comes out and then upgrade. That way at least I know I can fix everything at once. Paul - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archive at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>
On Thu, 4 Mar 1999, Paul W. Abrahams wrote:
Jesse McDonnell wrote:
I gathered from earlier postings that you have the 5.3 distribution. Did you have to upgrade your versions of libc, ppp, binutils, etc as described in the CHANGES document that comes with the kernel? If so, where did you get the upgrades? What particular directories etc. at the SuSE site if you got any there?
I knew about the upgrades mentioned in CHANGES, but I decided to try the kernel anyway without them - and your experience suggests I did the right thing. I too
I think so, you certainly didn't break anything. I may try to compile the 2.2.1 kernel and see how it functions with my existing libs and utils etc. Good Luck, Jesse - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archive at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>
Hi, On Wed, 3 Mar 1999, Wybo Dekker wrote:
After recompiling my kernel i see messages during boot up like:
SIOCIFADDR: Operation not permitted by device Eth0: unknown interface SIOCIFBRDADDR: Operation not permitted by device Eth0: unknown interface SIOCIFNETMASK: Operation not permitted by device Eth0: unknown interface
What does that mean? (It does not show up in /var/log/{messages,boot.log}!
These messages seem to come from the network configuration script. Hmm, ist it really "Eth0"? It should be "eth0", this is case sensitive. Better check /etc/rc.config and /etc/route.conf for correct spelling. Bye, LenZ -- ------------------------------------------------------------------ Lenz Grimmer SuSE GmbH <A HREF="mailto:grimmer@suse.de">mailto:grimmer@suse.de</A> Schanzaeckerstr. 10 <A HREF="http://www.suse.de/~grimmer"><A HREF="http://www.suse.de/~grimmer</A">http://www.suse.de/~grimmer</A</A>> 90443 Nuernberg, Germany - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archive at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>
Problem solved! A friend came by and found out that I had compiled a networking thing (the card?) as a module, which apparently could not be loaded at boot time, while it should. Thanks for all help! -- Hartelijke groet, Wybo Dekker ___________________Servalys Analytical Chemistry Services__________________ wybo@servalys.hobby.nl | Deilsedijk 60 | tel +31-345-652164 www.hobby.nl/~servalys | 4158 CH Deil, The Netherlands | fax +31-345-652383 - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archive at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>
participants (5)
-
abrahams＠valinet.com -
grimmer＠suse.de -
jmcdonne＠apollotrust.com -
Kappacher＠gmx.net -
wybo＠servalys.hobby.nl