Fitzcarraldo: Added note about incorporating the comment by user 'Thompson'.

2010-12-21T20:04:25Z

Added note about incorporating the comment by user 'Thompson'.

New page

I have got a suggestion for how to search which modules are installed for one's kernel version:
Instead of running

{{Console| <pre class="clear"> equo search <kernel-version> > kernel-upgrade.txt </pre>}}

''(BTW, the pipe is unnecessary. You can redirect the output of equo directly to another file.)''

run

{{Console| <pre class="clear"> equo query installed <kernel-version> > kernel-upgrade.txt </pre>}}

This way you will only see packages that are actually installed on your machine,
thus not having to search the text-file to find out, which kernel-modules are installed, and which
ones aren't. Be careful though, to really only update your kernel-modules!

E.g. I did an upgrade from '''2.6.35''' to '''2.6.36''', and in my '''kernel-upgrade.txt'''
there was also this package listed:

{{Console| <pre class="clear"> sys-apps/iproute2-2.6.35-r2 </pre>}}

This is '''NOT''' a kernel module! But if one reads the Description of the packages listed this is
quite easy to find out.

==================================================================================================

Good idea, but if you append "-sabayon" to the kernel version then you won't even get that one 'rogue' package you listed. For example, the following would do it:

{{Console| <pre class="clear">equo query installed 2.6.35-sabayon</pre>}}

resulting in:

{{Console| <pre class="clear"># equo query installed 2.6.35-sabayon
>> @@ Searching...
>> @@ Package: app-emulation/virtualbox-guest-additions-3.2.8#2.6.35-sabayon branch: 5, [__system__]
>> Installed: version: 3.2.8 ~ tag: 2.6.35-sabayon ~ revision: 2
>> Slot: 0,2.6.35-sabayon
>> Homepage: http://www.virtualbox.org/
>> Description: VirtualBox kernel modules and
>> user-space tools for Linux guests
>> License: GPL-2
>> @@ Package: net-wireless/broadcom-sta-5.60.48.36-r1#2.6.35-sabayon branch: 5, [__system__]
>> Installed: version: 5.60.48.36-r1 ~ tag: 2.6.35-sabayon ~ revision: 2
>> Slot: 0,2.6.35-sabayon
>> Homepage: http://www.broadcom.com/support/802.11/linux_sta.php
>> Description: Broadcom's IEEE 802.11a/b/g/n
>> hybrid Linux device driver.
>> License: Broadcom
>> @@ Package: net-wireless/ndiswrapper-1.56#2.6.35-sabayon branch: 5, [__system__]
>> Installed: version: 1.56 ~ tag: 2.6.35-sabayon ~ revision: 2
>> Slot: 0,2.6.35-sabayon
>> Homepage: http://ndiswrapper.sourceforge.net/
>> Description: Wrapper for using Windows drivers
>> for some wireless cards
>> License: GPL-2
>> @@ Package: x11-drivers/ati-drivers-10.8#2.6.35-sabayon branch: 5, [__system__]
>> Installed: version: 10.8 ~ tag: 2.6.35-sabayon ~ revision: 1
>> Slot: 1,2.6.35-sabayon
>> Homepage: http://www.ati.com
>> Description: Ati precompiled drivers for r600
>> (HD Series) and newer chipsets
>> License: AMD GPL-2 QPL-1.0 as-is
>> @@ Package: x11-drivers/nvidia-drivers-256.53#2.6.35-sabayon branch: 5, [__system__]
>> Installed: version: 256.53 ~ tag: 2.6.35-sabayon ~ revision: 1
>> Slot: 0,2.6.35-sabayon
>> Homepage: http://www.nvidia.com/
>> Description: NVIDIA X11 driver and GLX libraries
>> License: NVIDIA
>> @@ Package: x11-drivers/xf86-video-virtualbox-3.2.8#2.6.35-sabayon branch: 5, [__system__]
>> Installed: version: 3.2.8 ~ tag: 2.6.35-sabayon ~ revision: 2
>> Slot: 0,2.6.35-sabayon
>> Homepage: http://www.virtualbox.org/
>> Description: VirtualBox video driver
>> License: GPL-2
>> Keyword: 2.6.35-sabayon
>> Found: 6 entries</pre>}}

In fact, one could filter the package names out of that by using grep like so:

{{Console| <pre class="clear"># equo query installed 2.6.35-sabayon | grep '#'</pre>}}

For example:

{{Console| <pre class="clear"># equo query installed 2.6.35-sabayon | grep '#'
>> @@ Package: app-emulation/virtualbox-guest-additions-3.2.8#2.6.35-sabayon branch: 5, [__system__]
>> @@ Package: net-wireless/broadcom-sta-5.60.48.36-r1#2.6.35-sabayon branch: 5, [__system__]
>> @@ Package: net-wireless/ndiswrapper-1.56#2.6.35-sabayon branch: 5, [__system__]
>> @@ Package: x11-drivers/ati-drivers-10.8#2.6.35-sabayon branch: 5, [__system__]
>> @@ Package: x11-drivers/nvidia-drivers-256.53#2.6.35-sabayon branch: 5, [__system__]
>> @@ Package: x11-drivers/xf86-video-virtualbox-3.2.8#2.6.35-sabayon branch: 5, [__system__]</pre>}}

''Fitzcarraldo'', Mon Dec 20 03:44:55 GMT 2010

==================================================================================================

I have incorporated your suggestion, ''Thompson'', along with the filters I mentioned above. Thanks for taking the time to comment.

BTW, if you want to edit the article and make the examples consistent (they are for a hotchpotch of kernel versions at the moment) then please feel free. You might want to update the examples to cover e.g. originally-installed kernel is 2.6.35 and kernel to be installed is 2.6.36.

''Fitzcarraldo'', Tue Dec 21 20:01:41 GMT 2010

==================================================================================================

Talk:HOWTO: Upgrade kernel using Entropy - Revision history

Fitzcarraldo: Added note about incorporating the comment by user 'Thompson'.