Not sure if this is related or if I am doing something wrong, but this looks like it is also present in Lucid. I built a custom kernel to add PPS support. The first version went well, however re-building with newer (or older) source from the Git repos yields '/proc/version_signature' to lie.
My first build was with 2.6.32-33.66; version sig is correct, was also running native 2.6.32-33.66 at the time. The next was with 2.6.32-33.72; version sig still says 2.6.32-33.66, running 2.6.32-33.66 w/PPS patch at the time. Last test was with 2.6.32-28.55; version sig still says 2.6.32-33.66, running 2.6.32-33.72 w/PPS patch at the time. Tried on two systems...any one have any ideas why this is happening? The kernels work fine otherwise. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/794698 Title: hardy custom binary kernels have incorrect version reported in /proc/version_signature To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/794698/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
