Bug 767278 - ethernet card not started by kernel
Summary: ethernet card not started by kernel
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 16
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-13 17:25 UTC by jirikon
Modified: 2011-12-13 18:57 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-13 18:57:26 UTC
Type: ---


Attachments (Terms of Use)
dmesg kernel-3.1.5-1.fc16.i686 (51.72 KB, text/plain)
2011-12-13 17:25 UTC, jirikon
no flags Details

Description jirikon 2011-12-13 17:25:07 UTC
Created attachment 546299 [details]
dmesg kernel-3.1.5-1.fc16.i686

Description of problem:
After upgrade from fedora 15 to 16, ethernet card don't start, and graphic resolution is in base.

How reproducible:
I have motherboard GIGABYTE 73PVM-S2H with nForce 630i.
I uppgrade fedora 15 to 16 by preupgrade-cli.

===after boot in old kernel-2.6.38.7-30.fc15.i686
stdin>dmesg | grep "ther"
stdout>[    8.197378] forcedeth: Reverse Engineered nForce ethernet driver. Version 0.64.
stdin>lspci |grep -i VGA
stdout>00:10.0 VGA compatible controller: nVidia Corporation C73 [GeForce 7100 / nForce 630i] (rev a2)
stdin>lsmod | grep nfor
stdout>
i2c_nforce2             5094  0 
i2c_core               21384  5 i2c_nforce2,nouveau,drm_kms_helper,drm,i2c_algo_bit


===after boot in new kernel-3.1.5-1.fc16.i686
stdin>dmesg | grep "ther"
nothing in stout
stdin>lspci |grep -i VGA
stdout>00:10.0 VGA compatible controller: nVidia Corporation C73 [GeForce 7100 / nForce 630i] (rev a2)
stdin>lsmod
stdout>Module                  Size  Used by

Comment 1 Josh Boyer 2011-12-13 17:58:25 UTC
[    7.350154] modprobe[352]: FATAL: Could not load /lib/modules/3.1.5-1.fc16.i686/modules.dep: No such file or directory

That seems to show that depmod didn't get run during the %posttrans install of
the kernel.  Can you see if that file is indeed missing on the rootfs?  If so,
you can probably run:

depmod -a 3.1.5-1.fc16.i686

and it will create the proper files.

While you're checking things, can you provide the output of:

ls -l /boot

I would like to verify the initramfs for 3.1.5-1.fc16 seems to be of the correct
size.  If depmod wasn't run during the install, then it is probably broken as
well.

Comment 2 jirikon 2011-12-13 18:40:15 UTC
When I was upgrading from F15 to F16 before reporting bug, the upgrade was finished in second time (after rebooting).


The file /lib/modules/3.1.5-1.fc16.i686/modules.dep is missing.
After
stdin>depmod -a 3.1.5-1.fc16.i686
the file /lib/modules/3.1.5-1.fc16.i686/modules.dep was created.

stdin>ls -l /boot
stdout>
total 27444
-rw-r--r--. 1 root root   120082 May 27  2011 config-2.6.38.7-30.fc15.i686
-rw-r--r--. 1 root root   124539 Dec  9 19:17 config-3.1.5-1.fc16.i686
drwxr-xr-x. 3 root root     4096 Jun  4  2009 efi
-rw-r--r--. 1 root root   178436 Mar  7  2011 elf-memtest86+-4.20
drwxr-xr-x. 2 root root     4096 Dec 13 15:16 grub
drwxr-xr-x. 3 root root     4096 Dec 13 15:34 grub2
-rw-r--r--. 1 root root 13808500 Jun  8  2011 initramfs-2.6.38.7-30.fc15.i686.img
-rw-r--r--. 1 root root  1585499 Dec 13 14:16 initrd-plymouth.img
drwx------. 2 root root    16384 Jun 26  2009 lost+found
-rw-r--r--. 1 root root   176760 Mar  7  2011 memtest86+-4.20
-rw-------. 1 root root  1852332 May 27  2011 System.map-2.6.38.7-30.fc15.i686
-rw-------. 1 root root  1823409 Dec  9 19:17 System.map-3.1.5-1.fc16.i686
-rwxr-xr-x. 1 root root  3803952 May 27  2011 vmlinuz-2.6.38.7-30.fc15.i686
-rwxr-xr-x. 1 root root  4506528 Dec  9 19:17 vmlinuz-3.1.5-1.fc16.i686

After reboot, system is running true with kernel-3.1.5-1.fc16.i686.
Thank you for help.

Comment 3 Josh Boyer 2011-12-13 18:57:26 UTC
OK.  This isn't really a kernel problem and we already have other bugs open against dracut/grubby to look at why things aren't getting completed.  I'm going to close this one out for now.  Thanks for the quick response.


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