Am 06.08.2011 18:27, schrieb Myra Nelson:

On Sat, Aug 6, 2011 at 10:58, Thomas Bächler wrote:

...

Hi,

please signoff the 3.0 series for both architectures.

Note: the upgrade path from 3.0-2 to 3.0.1-1 is not entirely smooth if you rely on the vmlinuz26 compat symlink. However, the upgrade path from core/kernel26 to this version is smooth.

Upstream changes: http://kernelnewbies.org/LinuxChanges

Arch Linux Changes: - Rename the package: kernel26 -> linux - Added necessary replaces=(...) - Removed old comments and vercmps from .install file - Removed old comments and replaces from PKGBUILD - added compatibility symlinks for the old kernel and initramfs filenames in order to not break existing bootloader entries (only affects upgrades, not new installations) - removed System.map file, not needed anymore as we provide /proc/kallsyms

I haven't upgraded from 3.0-2 to 3.0.1-1 yet, but thought I would get some clarification. I'm assuming the reference to fixing your bootloader means having edited the kernel and initramfs lines to point to vmlinuz-linux and initramfs-linux.img and initramfs-fallback-linux.img. The reason for clarification is, we all know when one assumes something you make an "ass out of u and me".

If that's correct I should have it made, it's the first thing I did when I installed the new linux 3.0 kernel.

Myra

You are right.

On Sat, Aug 6, 2011 at 11:32, Thomas Bächler wrote:

Am 06.08.2011 18:27, schrieb Myra Nelson:

...

On Sat, Aug 6, 2011 at 10:58, Thomas Bächler wrote:

...

Hi,

please signoff the 3.0 series for both architectures.

Note: the upgrade path from 3.0-2 to 3.0.1-1 is not entirely smooth if you rely on the vmlinuz26 compat symlink. However, the upgrade path from core/kernel26 to this version is smooth.

Upstream changes: http://kernelnewbies.org/LinuxChanges

Arch Linux Changes: - Rename the package: kernel26 -> linux - Added necessary replaces=(...) - Removed old comments and vercmps from .install file - Removed old comments and replaces from PKGBUILD - added compatibility symlinks for the old kernel and initramfs  filenames in order to not break existing bootloader entries (only  affects upgrades, not new installations) - removed System.map file, not needed anymore as we provide  /proc/kallsyms

I haven't upgraded from 3.0-2 to 3.0.1-1 yet, but thought I would get some clarification. I'm assuming the reference to fixing your bootloader means having edited the kernel and initramfs lines to point to vmlinuz-linux and initramfs-linux.img and initramfs-fallback-linux.img. The reason for clarification is, we all know when one assumes something you make an "ass out of u and me".

If that's correct I should have it made, it's the first thing I did when I installed the new linux 3.0 kernel.

Myra

You are right.

It boots and everything seems to work fine. A check of dmesg doesn't show any problems. If you accept signoffs from users you have mine for x86_64. -- Life's fun when your sick and psychotic!

Am 06.08.2011 19:52, schrieb Tom Gundersen:

On Sat, Aug 6, 2011 at 5:58 PM, Thomas Bächler wrote:

...

please signoff the 3.0 series for both architectures.

Signoff x86_64.

"dmesg -k -l err" is empty, and the only mildly interesting output of "dmesg -k -l warn" I get is:

[ 7.268214] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared [ 8.495969] ACPI: Deprecated procfs I/F for battery is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared [ 9.577951] _regulator_get: 0000:15:00.2 supply vmmc not found, using dummy regulator

Maybe we should consider disabling ACPI_PROCFS_POWER for the next release, before it goes away?

I think you are right, we should. This has been kept enabled for legacy stuff like KDE 3, which is now gone.