patch allowing lrm builds against custom kernels

Bug #77064 reported by Matt Price on 2006-12-24
10
Affects Status Importance Assigned to Milestone
linux-restricted-modules-2.6.20 (Ubuntu)
Wishlist
Unassigned
linux-restricted-modules-2.6.24 (Ubuntu)
Undecided
Unassigned

Bug Description

The attached patch adds a few variables to debian/rules allowing users to build l-r-m against a custom kernel. I also provide a new file, debian/control.stub.custom, which replaces debian/control.stub.in when a custom flavour is indicted If maintainers are interested in this patch I will also write a README.CustomKernels file explaining how to use the new variables, which are:

CUSTOM_ABI : allows users to set the abi version
CUSTOM_FLAVOUR: name of custom flavour
SKIP_UDEBS: allow users to skip building udebs

I'd like to also autogenerate the "Maintainers" lines in debian/control so that bug requests aren't sent to kernel-team, but I'm not sure how to do that. Can set to ubuntu-users if that seems desirable.

this is debian/control.stub.custom, required by custom_rules.patch

Matt Price (matt-price) wrote :

didn't upload last time

Kyle McMartin (kyle) on 2007-01-16
Changed in linux-restricted-modules-2.6.20:
importance: Undecided → Wishlist
Matt Price (matt-price) wrote :

any responses to this imperfect patch? A suggestion for a better method would be welcome.

matt

Hi Matt,

This bug was opened a while ago but there hasn't been any recent activity. Is this still an issue against the current Hardy Heron 8.04 Alpha release that you would like to see addressed? http://www.ubuntu.com/testing . Please let us know. We'll keep this report open against the actively developed kernel but against 2.6.20 this will be closed. Thanks.

Changed in linux-restricted-modules-2.6.20:
status: New → Won't Fix
Changed in linux-restricted-modules-2.6.24:
status: New → Incomplete

This bug report is being closed because we received no response to the last inquiry for information. Please reopen it if this is still an issue in the current Ubuntu release. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks.

Changed in linux-restricted-modules-2.6.24:
status: Incomplete → Invalid

Reopening task after having chatted with Daniel (subscribed to report) about this being closed. We'll wait until after the final Hardy Heron 8.04 release to give everyone time to upgrade and test. Thanks.

Changed in linux-restricted-modules-2.6.24:
status: Invalid → New
Matt Price (matt-price) wrote :

hi leanne,

sorry not to respond earlier -- had some email troubles & didn't notice this one. i haven't built a kernel for a while so i'm not really qualified to comment anymore. but i still think it'd be better to have a procedure in place that makes building custom kernels easier for users. this makes it easier to test new features (in my case, mostly tuxonice) without disrupting the main ubuntu installation, and ultimately can provide some real-world testing for new features which might later make their way into the standard ubuntu kernel.

daniel, would love to hear back if this issue is one that's still being discussed by the kernel team. thanks!

matt

Alex Karpenko (alexkarpenko) wrote :

I've been trying to build restricted modules for a custom hardy kernel, and after a lot of pain editing rules and control stub it seemed to work. However, after I installed my custom restricted modules package nvidia drivers were still not being loaded, and I gave up.

Something that would allow me to easily pull in restricted modules to a custom kernel would definitely be greatly appreciated.

On Fri, 2008-05-16 at 04:28 +0000, Alex Karpenko wrote:
> I've been trying to build restricted modules for a custom hardy kernel,
> and after a lot of pain editing rules and control stub it seemed to
> work. However, after I installed my custom restricted modules package
> nvidia drivers were still not being loaded, and I gave up.
>
> Something that would allow me to easily pull in restricted modules to a
> custom kernel would definitely be greatly appreciated.
>

lrm is now set up analogously to the main kernel git tree. have you
tried editing the control stub files in the lum git tree? sorry in a
rush right now don't have the url, write back if you have a chance.

of course, i would also rather have a really straightforward way of
doing just as you suggest.

matt

--
Matt Price
<email address hidden>

Alex Karpenko (alexkarpenko) wrote :

Hi Matt,

I've used the old fashioned debian way to compile the kernel, outlined here: https://help.ubuntu.com/community/Kernel/Compile
I'm not sure what you mean as I'm a bit new to this. If you have a better resource/more detailed instructions, please do let me know :)

Bryce Harrington (bryce) wrote :

Hi matt-price,

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with the latest development release of Ubuntu? (ISOs are available from cdimage.ubuntu.com)

If it remains an issue, could you also attach a new /var/log/Xorg.0.log?
Thanks in advance.

The output of lspci -vvnn would also be worth having.

Changed in linux-restricted-modules-2.6.24:
status: New → Incomplete
Bryce Harrington (bryce) wrote :

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.

Changed in linux-restricted-modules-2.6.24:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers