<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-15"
http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Matt Price escreveu:
<blockquote cite="mid1164828130.5495.10.camel@localhost" type="cite">
<pre wrap="">On Wed, 2006-29-11 at 18:55 +0000, Paulo da Silva wrote:
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">On 11/28/06, Trent Lloyd <a class="moz-txt-link-rfc2396E" href="mailto:lathiat@bur.st"><lathiat@bur.st></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">AIUI, Nigel has given up trying to get suspend2 merged, as the current
suspend maintainer doesn't want to merge it and wants to wait until
he implements uswsusp instead.
</pre>
</blockquote>
</blockquote>
<pre wrap="">Why isn't there a script or at least a decent howto to let users
to choose/patch/compile their own kernels and restricted drivers,
even if not supported anymore by ubuntu?
For each release of ubuntu/kubuntu I managed to compile
my own kernel. One of the reasons is just the suspend2 that
works pretty fine with my computer. But I always needed to find
a tricky way to do that. For example for the edgy, after following
and changing an howto, I needed to install nvidia-drivers not
using the kubuntu/debian way. I think there should be additional
documentation to recompile the kernel and handle restricted
drivers. The lack of it is the main reason why I still didn't adopt
kubuntu for my production system.
</pre>
</blockquote>
<pre wrap=""><!---->There is actually an excellent howto as regards compiling kernels:
<a class="moz-txt-link-freetext" href="https://wiki.ubuntu.com/KernelCustomBuild">https://wiki.ubuntu.com/KernelCustomBuild</a> . </pre>
</blockquote>
When Edgy came out, I tried to follow that howto. It did'n work!.<br>
I don't remember now what was the problem, but there's something<br>
to do with the way to get the appropriate sources. I turned it<br>
around anyway. The problem is that the process was different from<br>
the one I used in the previous release. What's next? I need<br>
a "stable" way to do things or at least a per release doc. So,<br>
when a new version come out I just do the update, being it<br>
a simple or complex method. The same for a new version<br>
of the kernel.<br>
<br>
<blockquote cite="mid1164828130.5495.10.camel@localhost" type="cite">
<pre wrap="">If you want to justdo it
the Debian Way, then installing linux-source-2.6.19 also works well; you
can patch it straightforwardly enough with
bzcat /path/to/suspend2-2.2.9 | patch -p1
and build with just
make menuconfig
make-kpkg --initrd --append-to-version=suspend2 --rootcmd fakeroot \
kernel-image
</pre>
</blockquote>
I am not sure this works. At least it didn't for dapper.<br>
<br>
<blockquote cite="mid1164828130.5495.10.camel@localhost" type="cite">
<pre wrap="">
BUt , as you doubtless already know, the problem is in building
restricted-modules. I found this particularly frustrating as I needed
the ipw3945 restricted firmware and daemon, which are packaged with
l-r-m but is of course not a module.
Anyway I know Ben intended to write up a guide to building l-r-m
packages when he wrote that wiki guide, but I haven't seen it anywhere.
It may be pretty complicated to do, I don't know.
</pre>
</blockquote>
Don't think so! I don't believe developers don't have an easy way<br>
to pack these things whenever a new kernel or driver is released.<br>
But I may be wrong ...<br>
<blockquote cite="mid1164828130.5495.10.camel@localhost" type="cite">
<pre wrap="">I agree it would be nice if these were a little easier.
Matt
</pre>
</blockquote>
<br>
</body>
</html>