Apparently, the bug is fixed in kernel version 2.6.32-rc8. I have
recompiled kernels before in Slackware, but never in my preferred
distro, (k)ubuntu. I've tried doing it in ubunutu, but the package
build failed, and I can't figure out why.
So, my question is, is there a distro that has this bug fixed in their
distributed kernel, or has a working (for me) kernel in their package
manager.
If all else fails, I'll put Slackware on for a month or two until the
fixed bug does make it into a distributed kernel, but I'd rather not.
I liked Slackware, but IMHO it needs more customizing than I have time
for.
Thanks,
Mark
Did you use the kernel-package for building the kernel?
This should be the preferred way to build kernel-packages in all
debian-based distros.
> So, my question is, is there a distro that has this bug fixed in their
> distributed kernel, or has a working (for me) kernel in their package
> manager.
>
> If all else fails, I'll put Slackware on for a month or two until the
> fixed bug does make it into a distributed kernel, but I'd rather not.
> I liked Slackware, but IMHO it needs more customizing than I have time
> for.
>
> Thanks,
> Mark
Klaus
--
Klaus Zerwes
http://www.zero-sys.net
Everything worked as expected, up to this point:
>To build the kernel, execute these two commands:
>
>make-kpkg clean
>fakeroot make-kpkg --initrd --append-to-version=-custom kernel_image
>kernel_headers
The 'make-kpkg clean' seemed to work, but it ended with an error
message I don't recall (I tried this a week or two ago), and there
were no .deb files to install.
The error message could be of some help to figure out whats wrong.
And I do assume that you do not need the headers, just build the image.
Maybe you should try a make bzimage in the kernel source tree to see if
this step would be working at least.
> mark.russe...@gmail.com wrote:
>> I want to run Linux on my new pavilion laptop, but there's a bug
>> <http://bugzilla.kernel.org/show_bug.cgi?id=13449#c12> in the mainline
>> kernel (after recovering from sleep, the battery is not seen), that
>> makes the machine impractical for my desired use.
>>
>> Apparently, the bug is fixed in kernel version 2.6.32-rc8. I have
>> recompiled kernels before in Slackware, but never in my preferred
>> distro, (k)ubuntu. I've tried doing it in ubunutu, but the package
>> build failed, and I can't figure out why.
>
> Did you use the kernel-package for building the kernel?
> This should be the preferred way to build kernel-packages in all
> debian-based distros.
But there probably is no kernel package for the -rc kernel that the OP needs.
Debian and derived distros add their own patches to the kernel, so a plain
vanilla kernel may have issues.
Yet another reason why I use Slackware. I always build my own kernel on Slack.
-Joe
A package containing a kernel would be a linux-image. Kernel-package is
a tool for building kernels the Debian way:
Package: kernel-package
Description: A utility for building Linux kernel related Debian packages.
This package provides the capability to create a Debian kernel image
package by just running make-kpkg kernel_image in a kernel source
directory tree. It can also package the relevant kernel headers into
a kernel-headers package. In general, this package is very useful if
you need to create a custom kernel, if, for example, the default
kernel does not support some of your hardware, or you wish a leaner,
meaner kernel. It also scripts the steps that need be taken to
compile the kernel, which is quite convenient (forgetting a crucial
step once was the initial motivation for this package). Please look at
/usr/share/doc/kernel-package/Rationale.gz for a full list of advantages
of this package.
> Debian and derived distros add their own patches to the kernel, so a
> plain vanilla kernel may have issues.
I've never had any problems using upstream kernels on Debian. However,
the OP should not need to do so:
toncho/~ apt-cache search "2.6.32-rc8"
linux-headers-2.6.32-rc8-486 - Header files for Linux 2.6.32-rc8-486
linux-headers-2.6.32-rc8-686-bigmem - Header files for Linux 2.6.32-rc8-686-bigmem
linux-headers-2.6.32-rc8-686 - Header files for Linux 2.6.32-rc8-686
linux-headers-2.6.32-rc8-all-i386 - All header files for Linux 2.6.32
linux-headers-2.6.32-rc8-all - All header files for Linux 2.6.32
linux-headers-2.6.32-rc8-amd64 - Header files for Linux 2.6.32-rc8-amd64
linux-headers-2.6.32-rc8-common - Common header files for Linux 2.6.32-rc8
linux-image-2.6.32-rc8-486 - Linux 2.6.32-rc8 for old PCs
linux-image-2.6.32-rc8-686-bigmem - Linux 2.6.32-rc8 for PCs with 4GB+ RAM
linux-image-2.6.32-rc8-686 - Linux 2.6.32-rc8 for modern PCs
linux-image-2.6.32-rc8-amd64 - Linux 2.6.32-rc8 for 64-bit PCs
linux-support-2.6.32-rc8 - Support files for Linux 2.6.32-rc8
linux-tree-2.6.32 - Linux kernel source tree for building Debian kernel images
--
John Hasler
jha...@newsguy.com
Dancing Horse Hill
Elmwood, WI USA
> Apparently, the bug is fixed in kernel version 2.6.32-rc8. I have
> recompiled kernels before in Slackware, but never in my preferred
> distro, (k)ubuntu. I've tried doing it in ubunutu, but the package
> build failed, and I can't figure out why.
Gentoo do have rc kernels in it's portage.
--
//Aho
The description page is at;
<https://wiki.ubuntu.com/KernelTeam/MainlineBuilds?action=show&redirect=KernelMainlineBuilds>
and the archive itself is at;
<http://kernel.ubuntu.com/~kernel-ppa/mainline/>
Thanks to everybody for their help.
Mark