Urgent pleeease help! stuck!

Naresh Mehta nareshtechs at gmail.com
Thu Feb 18 13:09:09 UTC 2010

Hi Praseen,

I generally create a separate partition and file system for doing these kind
of things. You can read more at:

Sorry for not being specific but the moto should always be to never mess
around with the working/production partition, FS and kernel. You can also do
things inside a Virtual Machine if you really need to sandbox your system. I
would prefer Virtual Box but have seen some XEN action as well.

BR; Naresh

On Thu, Feb 18, 2010 at 1:38 PM, Praseen Preman <praseen.preman at gmail.com>wrote:

> Hi guys,
> I am currently stuck up with a few issues while inserting some rudimentary
> modules into the linux kernel and recompiling and running it, there after.
> I am currently using the Ubuntu Hardy Heron 8.04 LTS, kernel version
> 2.6.24-26. I wanted to insmod and modprobe a few of my own hand written
> rudimentary modules into the kernel. I succeeded in my above venture,
> but with a few unwanted side effects.
> The kernel version 2.6.24-26 shipped with the Ubuntu Heron LTS was not
> allowing me to insert a module compiled from the 2.6.24
> kernel source tree.
> So I recompiled the sources for the 2.6.24 kernel
> sources and booted into it using grub.This time around I was successful in
> inserting the kernel
> modules, but *modprobe failed *though.
> The issue I was facing was that, my nVidia drivers and
> creative sound card drivers failed to work at first for the 2.6.24
> version kernel and soon for the shipped 2.6.24-26 kernel too it failed
> to work. Following this X windows too ceased to work properly for both
> the kernels.
> What  isthe best way to solve and avoid such a scenario.
> I have a hunch that the since both the compiled 2.6.24 kernel and the
> shipped 2.6.24-26 kernel used the same file system when they load ,the
> 2.6.24 kernel corrupted the udev configuration when it loaded and this
> corrupted udev created problems for the 2.6.24-26 kernel when it loaded
> too. Please let me know the right approach to such a scenario and how
> to solve it.
> Does creating seperate ext3 filesystems for the multiple versions of the
> kernel
> help solve this issue? What is the suggested system configuration for
> kernel/ driver developers.
> Thanks and Regards,
> Praseen
> --
> kernel-team mailing list
> kernel-team at lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/kernel-team
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/kernel-team/attachments/20100218/33a68795/attachment.html>

More information about the kernel-team mailing list