Bug 190847 - no network connections with kernel 2.6.16-1.2107_FC5 on a Thinkpad T42p
no network connections with kernel 2.6.16-1.2107_FC5 on a Thinkpad T42p
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Dave Jones
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2006-05-05 13:43 EDT by Daniel Hammer
Modified: 2015-01-04 17:27 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-05-05 14:14:41 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Daniel Hammer 2006-05-05 13:43:58 EDT
Description of problem:
I run a notebook IBM Thinkpad T42p with installed FC5 + all available updates.
When updating kernel from 2.6.16-1.2096_FC5 to 2.6.16-1.2107_FC5 no network
connections are posiible anymore.
I've tested a number of applications yum, ssh, firefox etc. and had ethereal run
at the destination machine. In case of ssh no keyexchange works anymore.
There are no special entries in /var/log/messages. Restarting the network,
stoping iptables do not have any effect.
SELinux is disabled on the machine.

Version-Release number of selected component (if applicable):
kernel package 2.6.16-1.2107_FC5

How reproducible:
Install kernel 2.6.16-1.2107_FC5 and try to connect somewhere

Steps to Reproduce:
1. install kernel 2.6.16-1.2107_FC5
2. reboot
3. try to connect somewhere
Actual results:
No connection over no network possible

Expected results:
Network connection should be possible to establish as they did for all FC5
kernel versions prior to 2.6.16-1.2107_FC5

Additional info:
Comment 1 Dave Jones 2006-05-05 14:14:41 EDT
2107 was horribly broken. this is very likely fixed in 2111 which just got
pushed out.
Comment 2 Daniel Hammer 2006-05-05 16:10:16 EDT
Okay, we'll see ;-)

Note You need to log in before you can comment on or make changes to this bug.