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#20887 - modprobe stops working after upgrade to the 2.6.35 kernel

Attached to Project: Arch Linux
Opened by David (dsr) - Saturday, 18 September 2010, 19:54 GMT
Last edited by Ionut Biru (wonder) - Thursday, 23 September 2010, 12:14 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To No-one
Architecture x86_64
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: modprobe fails to work after kernel upgrade on my ThinkPad T400. This kills access to X, the hardware clock, and a bunch of other useful luxuries.

Additional info:
The last working version of the kernel that I have tried is 2.6.34.2-2. The attached log file is for 2.6.35.4-2, but the same thing happened with 2.6.35.2-1 and 2.6.35.3-1.

lines 1 to 568 of the log file were generated by booting the inoperable kernel 2.6.35.4-2, and lines 567 to the end were generated by booting the working kernel 2.6.34.2-2.

Steps to reproduce:
Upgrade to a kernel in the 2.6.35 line and attempt to boot. You might need a ThinkPad T400.
   messages-kernel-2.6.35.log (107.6 KiB)
This task depends upon

Closed by  Ionut Biru (wonder)
Thursday, 23 September 2010, 12:14 GMT
Reason for closing:  Not a bug
Comment by Ike Devolder (BlackEagle) - Tuesday, 21 September 2010, 10:21 GMT
dunno what youre doing to boot but it states on line 3 youre using:
Linux version 2.6.34-ARCH (tobias@T-POWA-LX) (gcc version 4.5.0 20100610 (prerelease) (GCC) ) #1 SMP PREEMPT Mon Jul 5 22:12:11 CEST 2010

so your image is still there but the kernel is no longer installed

you use a read only boot or something

so if you have 2.6.35 installed its very normal you cant load modules from 2.6.34-ARCH since there is nothing left there
Comment by David (dsr) - Thursday, 23 September 2010, 02:41 GMT
Thanks! I had been using lilo as my bootloader since I used to use my Slackware partition a lot more, but I kept my Slackware's /boot directory separate from my Arch's /boot directory. So here I guess I forgot to copy the kernel and initrd from Arch's /boot to the /boot partition that lilo uses. Now I've just switched over to grub, and everything's working. Apologies for my own forgetfulness and thanks for noticing that the problem was that the computer still tried to boot 2.6.34.

Loading...