SuSE is wireless happy. They insist on adding all sorts of wireless functionality to a server.

We might have to take this over to the Novell people. At least I have a support contract with them!

I found what was causing the error, in 'ifup' @ line 1033 it calls 'ip link ..." which fails.

# ip link set up dev lo
RTNETLINK answers: Invalid argument

Have not been able to discover the reason for the failure. This line is suppose to bring up the interface. 'ifconfig $INTERFACE up' will also bring up the interface.

Until I get a real fix for 'ip link set ...", I have changed the following starting at line 1033 in /sbin/ifup

         #if ! ip link set up dev $INTERFACE \
         #        ${LLADDR:+address $LLADDR} $LINK_OPTIONS; then
         # 'ip link set' is broken using ifconfig SB
         if ! ifconfig $INTERFACE up; then

This gets me a lo and starts eth0 at the proper location. (Eth0 was also failing initially, then kick-started in the DHCP section a bit later.)

In setting up eth0 there is one other location that "ip ..." will fail. But it is not currently causing me an issue so I will not look into that until later.

I going to be submitting a ticket with Linode to get this looked at, I believe it is a problem specific to the linode build as I do not see the issue on other systems that I have with SUSE 11.0 on them.

This seems to be an issue with the 'Latest 2.6 Series (2.6.18.8-linode10)' kernel.

Mike from Linode support suggested that I try rebooting with '2.6.27.4-linode14' as the kernel selected. With this kernel, startup scripts look to be working as expected.

No other issues around the different kernel?

BTW good find there.

I switched kernels and rebooted and lo came up perfectly. Thanks for sharing that info!

BTW: I like how if you launch the ajax console before booting you can watch the boot process.

You should be able to do that as well if you ssh to your linodeIDHERE@HOSTXX.linode.com