Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#37057 - [linux] PLEASE ENTER SUMMARY

Attached to Project: Arch Linux
Opened by William Trivett (willtriv) - Wednesday, 25 September 2013, 14:33 GMT
Last edited by Dave Reisner (falconindy) - Wednesday, 25 September 2013, 15:02 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
after upgrading from linux 3.11.1-1 to 3.11.1-2 the kernel does not upgrade properly. It seems there is something wrong with the pkgbuild because after upgrading my system is still trying to use 3.11.1-1 and it does not load any modules. I could not force my ethernet modules to load and was forced to downgrade to an older kernel sitting in my cache because I was left without the ability to load modules on the new kernel.

Additional info:
* package version(s): 3.11.1-2
* config and/or log files etc.: all defaults


Steps to reproduce:
upgrade from 3.11.1-1 to 3.11.1-2 and see your modules all fail to load (because it's looking for 3.11.1-1 stuff still)
This task depends upon

Closed by  Dave Reisner (falconindy)
Wednesday, 25 September 2013, 15:02 GMT
Reason for closing:  Not a bug
Additional comments about closing:  Not a packaging bug
Comment by Dave Reisner (falconindy) - Wednesday, 25 September 2013, 14:45 GMT
There's nothing wrong with the package -- did you forget to mount /boot for the upgrade or not copy the kernel to your EFI partition?
Comment by William Trivett (willtriv) - Wednesday, 25 September 2013, 14:47 GMT
I'm using MBR grub2. My boot partition is always mounted.
Comment by Dave Reisner (falconindy) - Wednesday, 25 September 2013, 15:02 GMT
You'll need to figure out what you've done wrong. I just booted a VM on the new package and have no problems like the ones you describe:

$ uname -r; pacman -Q linux; lsmod | wc -l
3.11.1-2-ARCH
linux 3.11.1-2
56

Loading...