Bug 726730 - with kernel-3.1.0-0.rc0.git9.1.fc17, network doesn't work
Summary: with kernel-3.1.0-0.rc0.git9.1.fc17, network doesn't work
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Josh Boyer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-29 15:54 UTC by Andre Robatino
Modified: 2011-07-29 21:20 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-07-29 21:20:56 UTC
Type: ---


Attachments (Terms of Use)

Description Andre Robatino 2011-07-29 15:54:00 UTC
Description of problem:
After applying the 20110729 Rawhide updates, network doesn't work when booting into the newest kernel. It does work when booting into the older (3.0.0-1.fc16.x86_64) kernel.

Version-Release number of selected component (if applicable):
kernel-3.1.0-0.rc0.git9.1.fc17.x86_64

How reproducible:
always

Additional info:
This is a VirtualBox 4.1.0 Rawhide x86_64 guest. Was not able to build the VirtualBox guest additions either for the new kernel, the following is the contents of vboxadd-install.log. Has something really basic changed with the new kernel which could cause both problems? I DO have the kernel, kernel-devel and kernel-headers packages for the new kernel.

/tmp/vbox.1/Makefile.include.header:94: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again.  Stop.

Comment 1 Andre Robatino 2011-07-29 16:51:24 UTC
With the new kernel, uname returns the wrong information. Even though I am currently running kernel-3.1.0-0.rc0.git9.1.fc17.x86_64, "uname -r" returns 3.0.1-0.rc0.git9.1.fc17.x86_64. This does not correspond to any of my 3 currently installed kernels, but appears to be the name of the latest kernel with "3.1.0" replaced by "3.0.1". That explains VirtualBox's confusion, anyway - the KERN_DIR variable depends on the value of `uname -r`.

Comment 2 Josh Boyer 2011-07-29 18:35:29 UTC
This build should have a fix for the uname issue when it completes:

http://koji.fedoraproject.org/koji/buildinfo?buildID=256250

It might also solve some of the networking issues you were seeing.  I built it locally and installed it in a KVM guest and networking was functional.

Comment 3 Andre Robatino 2011-07-29 20:59:32 UTC
(In reply to comment #2)
> This build should have a fix for the uname issue when it completes:
> 
> http://koji.fedoraproject.org/koji/buildinfo?buildID=256250
> 
> It might also solve some of the networking issues you were seeing.  I built it
> locally and installed it in a KVM guest and networking was functional.

With this build, all problems are solved. Networking works, uname output is correct, VirtualBox guest additions build and work.

Comment 4 Josh Boyer 2011-07-29 21:20:56 UTC
Thanks for testing!


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