Skip to contentSkip to conversation

2.4.16: "Address family not supported" on RH IBM T23

DISCUSSION Heikki Levanto 6 participants 6 messages Nov 27, 2001

lore
Share & tools
lore
#0 lore raw

Tried to compile 2.4.16 on my brand new IBM T23.

Small problem: Kernel panic at start, null pointer reference when initializing agp code. Disabled agp, and boots OK. Probably too new motherboard? Should I report what details?

Large problem: Network won't come up. Says:

Quoted 1 line

Cannot open netlink socket: Address family not supported by protocol

This happens both to lo and eth0, with a stock kernel, only option I changed was the agp (see above). Can boot past this, but no networking configured.

Invoking ifup by hand causes same behaviour.

Manually running ifconfig lo 127.0.0.1 and ifconfig lo up work. Same for eth0.

More digging pointed me to redhat's ifup script (7.2 with latest updates), in the function is_available, there is a line that tests 'ip -o link'. This is what gives the error messages in ifup (as well as when run by hand). Could not find much documentation for that /sbin/ip, redhat special?

Problem does not occur on redhat 7.2 default kernel 2.4.7-10, nor on the one their thing upgraded my box to, 2.4.9-13

Does this indicate a kernel problem, redhat problem, or my problem?

Thank you in advance

Heikki Levanto

P.S. I try to follow the list, but would still appreciate a direct cc if you have any comments, suggestions, or workarounds.

Signature · 1 line
Heikki Levanto            [email protected]            "In Murphy We Turst"
#1 lore raw
Quoted 5 lines

Large problem: Network won't come up. Says:

Quoted 1 line

Cannot open netlink socket: Address family not supported by protocol

Have you compiled the netlink device into the kernel?

Check this:
yk /usr/src/linux $ grep NETLINK .config
CONFIG_NETLINK=y

#2 lore raw
In reply to Heikki Levanto
Quoted 2 lines · In article <[email protected]> you wrote:

is what gives the error messages in ifup (as well as when run by hand). Could not find much documentation for that /sbin/ip, redhat special?

You need to enable the netlink config options

Quoted 1 line

Does this indicate a kernel problem, redhat problem, or my problem?

your problem; it's even mentioned in the releasenotes..

#4 lore raw
In reply to Heikki Levanto
Quoted 3 lines · On Tue, Nov 27, 2001 at 07:19:05PM +0000, [email protected] wrote:

You need to enable the netlink config options

your problem; it's even mentioned in the releasenotes..

It would be even better to mention it in the kernel documentation, since iproute2 is fairly standard now. I'm really not enough of a kernel hacker to change it, but the current Configure.help entry for CONFIG_NETLINK suggests that it is useful only for relatively obscure applications.

You need to say Y here to use the tools in the iproute2 package (<ftp://ftp.inr.ac.ru>).

And is CONFIG_RTNETLINK also necessary for ip?

Andrew

#5 lore raw

From: [email protected] (Andrew Pimlott)
Date: Tue, 27 Nov 2001 15:31:19 -0500

It would be even better to mention it in the kernel documentation, since iproute2 is fairly standard now. I'm really not enough of a kernel hacker to change it, but the current Configure.help entry for CONFIG_NETLINK suggests that it is useful only for relatively obscure applications.

That is changing soon, the config options are in fact going away and both will be on all the time if you have networking enabled at all.