I screwed up my rootserver. It was running fine with Debian Woody,
kernel 2.4.26. Some weeks ago I upgraded to Sarge, all was fine. I
never rebooted the system at that time.

Now I wanted the 2.6 kernel, so I installed kernel-image-2.6.8-2-868
and module-init-tools. I put the new boot option as default in
lilo.conf and also added the initrd line. Run lilo, all looked fine.
After reboot, I had no access to the server anymore.

No problem, I thought, booted the remote recue system, mounted the
partitions and proc, chrooted into the system and put the old kernel
as default again. Reran lilo, unmounted partitions and rebooted again.
This is where the pain began: still no network access! When I look
into kern.log, it seems that the network driver is loaded ok, but eth0
never gets an ip address. /etc/network/interfaces is ok too and was
not changed in the process.

I can still reboot into the rescue system. Any ideas?
Eggert

Eggert Ehmke wrote:
> I screwed up my rootserver. It was running fine with Debian Woody,
> kernel 2.4.26. Some weeks ago I upgraded to Sarge, all was fine. I
> never rebooted the system at that time.
>
> Now I wanted the 2.6 kernel, so I installed kernel-image-2.6.8-2-868
> and module-init-tools. I put the new boot option as default in
> lilo.conf and also added the initrd line. Run lilo, all looked fine.
> After reboot, I had no access to the server anymore.
>
> No problem, I thought, booted the remote recue system, mounted the
> partitions and proc, chrooted into the system and put the old kernel
> as default again. Reran lilo, unmounted partitions and rebooted again.
> This is where the pain began: still no network access! When I look
> into kern.log, it seems that the network driver is loaded ok, but eth0
> never gets an ip address. /etc/network/interfaces is ok too and was
> not changed in the process.
>
> I can still reboot into the rescue system. Any ideas?
> Eggert


A few things you might want to check and/or post here:


Does lsmod mention your network driver? Do you get any messages when you
remove and reload the driver? (rmmod, modprobe)

What kind of network card do you have? What's the name of the driver?

What information does ifconfig give?

Do you get any messages when you bring eth0 down and up again? (ifdown ifup)

Is tcp/ip working ok? (ping localhost)


-- Bastian

bastian eendt <unbastian320@melvex.xs4all.nl> schrieb:

>Eggert Ehmke wrote:
>> I screwed up my rootserver. It was running fine with Debian Woody,
>> kernel 2.4.26. Some weeks ago I upgraded to Sarge, all was fine. I
>> never rebooted the system at that time.
>>
>> Now I wanted the 2.6 kernel, so I installed kernel-image-2.6.8-2-868
>> and module-init-tools. I put the new boot option as default in
>> lilo.conf and also added the initrd line. Run lilo, all looked fine.
>> After reboot, I had no access to the server anymore.

>Does lsmod mention your network driver? Do you get any messages when you
>remove and reload the driver? (rmmod, modprobe)
>
>What kind of network card do you have? What's the name of the driver?
>
>What information does ifconfig give?
>
>Do you get any messages when you bring eth0 down and up again? (ifdown ifup)
>
>Is tcp/ip working ok? (ping localhost)

It turned out that the routing table was empty. Changing from static
to dhcp did help, at least with the 2.4 kernel. Still unclear to me:
what in the process of upgrading to sarge confused my routing? It was
definitely working with static ip before, even after the upgrade
(until the reboot).
The 2.6 problem seems to be a module/initrd problem, I will
investigate that. Thanks for your hints. There are some homepages
hosted on the server, I cannot reboot it all the time.
Eggert

Eggert Ehmke writes:
> Still unclear to me: what in the process of upgrading to sarge confused
> my routing?

IIRC there was some sort of a change in 2.6 in the order in which labels
are assigned to interfaces.

Look at ifrename.
--
John Hasler