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#26274 - [linux] linux-3.0.6-1 breaks mkinitcpio's memdisk hook

Attached to Project: Arch Linux
Opened by Roman Widmann (archme) - Wednesday, 05 October 2011, 13:23 GMT
Last edited by Tobias Powalowski (tpowa) - Friday, 07 October 2011, 12:35 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Thomas Bächler (brain0)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
linux-3.0.6-1 breaks mkinitcpio's memdisk hook.
The memdisk hook depends on the "phram" kernel module.
This module seems to be removed in linux-3.0.6-1
(http://projects.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/linux&id=de5775dd)

If possible please "reinclude" the phram module.
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Friday, 07 October 2011, 12:35 GMT
Reason for closing:  Fixed
Additional comments about closing:  3.0.6-2
Comment by Tobias Powalowski (tpowa) - Wednesday, 05 October 2011, 13:31 GMT
added for next rebuild.
Comment by Roman Widmann (archme) - Thursday, 06 October 2011, 12:24 GMT
First, thanks for the effort.
Second, when will be the "next rebuild" ?

Because i am somehow stuck with my current project, which uses archiso.
And archiso depends on a working memdisk hook.
Comment by Tobias Powalowski (tpowa) - Thursday, 06 October 2011, 12:27 GMT
next kernel release.
Comment by Roman Widmann (archme) - Thursday, 06 October 2011, 12:34 GMT
you do not plan a linux-3.0.6-2 ?
Comment by Tobias Powalowski (tpowa) - Thursday, 06 October 2011, 12:40 GMT
No if nothing serious comes up i don't plan a 3.0.6-2.
I guess 3.0.7 comes in a week or so, now that the kernel infrastructure will be restored soon.
Comment by Patrick Landry (landrypm) - Friday, 07 October 2011, 00:09 GMT
Is there a workaround? I am also working on a project which depends on archiso.
Thanks.
Comment by Tobias Powalowski (tpowa) - Friday, 07 October 2011, 07:06 GMT
recompile the kernel with the latest config from trunk.
Comment by Roman Widmann (archme) - Friday, 07 October 2011, 07:18 GMT
Unfortunatly, just recompiling kernel package is not enough to make archiso image creation work again :(
Archiso uses chroots and pacman for image creation.
Which means it always uses packages from repositories for creation (eg: linux-3.0.6-1)

The only workaround i could think of, would be with a "custom" repository.
imo, not worth the effort ;)
Comment by Thomas Bächler (brain0) - Friday, 07 October 2011, 08:29 GMT
Tobias, there seems to be quite some concern over this. Should we schedule a rebuild with the adjusted config (and also revert the cpufreq changes)? I can do it tonight or tomorrow if you are unavailable.

Loading...