kernel-2.6.22.1-33.fc7 breaks "Determining IP info for eth0" at boot?

[NoSkill]

I've just updated to kernel-2.6.22.1-33.fc7. The bootup hangs at Determining IP information for eth0... and won't progress any further. I have to use CTRL-F1 to switch to a console and CTRL-ALT-DEL to restart the computer, but the problem still remains

If I use my previous kernel-2.6.22.1-27.fc7 then the bootup is fine and progresses normally.

Anyone else having the problem?

[edit: In case you're wondering, the eth0 is connected to my ADSL2 modem]

[SlowJet]

Did you do the other updates?

# rpm -qa dhc*
dhcdbd-2.7-5.fc7
dhcpv6_client-0.10-42.fc7
dhclient-3.0.5-38.fc7

If not those above then do
yum update dhc*

[gthill]

yes, I also have had a few issues since upgrading to kernel-2.6.22.1-27.fc7
My server should issue fixed ip addresses according to the mac address yet after upgrading my laptop sometimes it is gets an ip address in the open range or as has happened on a couple of occasions it gets an ip address in the 169.xxx.xxx.xxx range instead of the 192.168.1.7 as specified. My Desktops are rarely rebooted and I haven't updated them since kernel-2.6.21-1.3228.fc7 so I don't know if they will be affected. My home server is still fc5 and I just leave that alone, only monitoring intrusion attempts. It seems kind of weird but a service network restart usually fixes it plus I have a script to reconfigure ip addresses depending on the network I am using (for work I need a fixed 130.xxx address ). My server has issued faultlessly until this latest kernel upgrade on my laptop. But then this kernel has given me more niggling issues than I have ever had before, which is generally none.

My laptop
[root@lap1 ~]# rpm -qa | grep dhc
dhcdbd-2.7-5.fc7
dhclient-3.0.5-38.fc7
libdhcp6client-0.10-42.fc7
libdhcp-1.24-4.fc7
dhcpv6_client-0.10-42.fc7
libdhcp4client-3.0.5-38.fc7
[root@lap1 ~]#

[NoSkill]

Did you do the other updates?

# rpm -qa dhc*
dhcdbd-2.7-5.fc7
dhcpv6_client-0.10-42.fc7
dhclient-3.0.5-38.fc7

If not those above then do
yum update dhc*

I didn't have dhcpv6_client-0.10-42.fc7 installed, so I installed that. But unfortunately the problem remains

I suspect there was too little testing between the two kernel updates (less than a week?) and this is a fault that has been created after something else got fixed.

I haven't seen what happens if I don't connect the modem (should say something like "Check cable") but I'll have to wait till later on to find out.

For the moment, I have grub set to start my "older" 2.6.22.1-27,fc7 kernel first until this gets sorted out.

[NoSkill]

dhcdbd-2.7-5.fc7
dhclient-3.0.5-38.fc7
libdhcp6client-0.10-42.fc7
libdhcp-1.24-4.fc7
dhcpv6_client-0.10-42.fc7
libdhcp4client-3.0.5-38.fc7

Yep. Same list as mine. I'm a bit confused... Are you using kernel-2.6.22.1-33.fc7 or kernel-2.6.22.1-27.fc7?

The 33 breaks my rig, but 27 works fine.

[gthill]

I am updating to kernel...33.fc7 at this moment, I'll let you know if I still have problems after

[NoSkill]

I am updating to kernel...33.fc7 at this moment, I'll let you know if I still have problems after

Cheers, mate... So if I don't hear from you for a while, umm, I'll know what happened

[gthill]

I still have my desktop, I don't update that if I have any issues with my laptop update.

[lmaurin]

i have the same problem with 2.6.22.1-33.fc7

if you use static IP, this problem can be bypassed

[adrianx]

... the same 2.6.22.1-33.fc7 problem. For some reason, after updating nfts-3g, my fstab entries became invalid?

[NoSkill]

i have the same problem with 2.6.22.1-33.fc7

if you use static IP, this problem can be bypassed

Phew, so it is more that just my rig.

Use static IP. <- Now this is kind of stuff is new to me... How would I set that up? I know my modem uses 192.168.1.1 as the address my computer connects to it. But I don't (didn't) set that up - Fedora "finds" it (my modem) at that address when I boot up my system. (I'm guessing that's why it gets broken by the new kernel)

[NoSkill]

... the same 2.6.22.1-33.fc7 problem. For some reason, after updating nfts-3g, my fstab entries became invalid?

Well, I can tell you what the problem is with NTFS-3G

Here's the bug report and fix info:
https://bugzilla.redhat.com/bugzilla....cgi?id=249695

[lmaurin]

if you have a router, you probably have a private LAN, and you can probably use static IP

you first have to disable the DHCP client, and enter manually the IP, netmask, gateway and DNS addresses

but i suppose that the 2.6.22.1-33.fc7 will be fixed soon

[gthill]

Yes, ntfs-3g has failed too, but that will be updated soon enough. The previous one works so if you really need it you can boot your earlier kernel.
I don't have any problems with ip allocation on the first boot of kernel 33.
To set a static ip address with a router 192.168.1.1 would be something like this

ifconfig eth0 192.168.1.10 broadcast 192.168.1.255 netmask 255.255.255.0

But I would suggest either configuring you router to do that for you or do a search on ip configuration
first and know what you are doing. A good resource is Rute
http://linux.2038bug.com/rute-home.html
This is an awesome reference for most things linux
Download it, It's a free book.

chapter 25 for ip configuration and internet communication

[NoSkill]

if you have a router, you probably have a private LAN, and you can probably use static IP

you first have to disable the DHCP client, and enter manually the IP, netmask, gateway and DNS addresses

Ah, OK... So I would have to put the modem into "Bridge" mode and have Fedora manage the connection (through PPP)?

but i suppose that the 2.6.22.1-33.fc7 will be fixed soon

I haven't seen a bug report yet but I think that is because the kernel was only put up in the "updates" repository in the last few hours. If I don't see a bug submission in the next few hours, then I might do it myself.