kernel modules

kernel modules

[David Kesselring]

Can someone please confirm that loading and unloading of kernel modules is
functioning in the  2.4 release?

When I try to load a wlan module that I compiled (with mipsel-*) I get
relocation errors. I used the same options as I did to compile the kernel
(for MIPS Malta board). If you have any ideas, please let me know.


David Kesselring
Atmel MMC
dkesselr@mmc.atmel.com
919-462-6587

Re: kernel modules

[David Daney]

David Kesselring wrote:

>Can someone please confirm that loading and unloading of kernel modules is
>functioning in the  2.4 release?
>
>When I try to load a wlan module that I compiled (with mipsel-*) I get
>relocation errors. I used the same options as I did to compile the kernel
>(for MIPS Malta board). If you have any ideas, please let me know.
>
>  
>
Works for me.

Using gcc 3.3.1 to compile modules, I had to upgrade to modutils-2.4.25 
and apply this patch to them:


On Thu, 16 Oct 2003 14:09:24 -0700, 
David Daney <ddaney@avtrex.com> wrote:

>>Anyhow, I encountered a small problem trying to load a module compiled 
>>with gcc-3.3.1.  The module has dwarf debugging info and could not be 
>>loaded by insmod.  This patch causes MIPS_DWARF sections to be treated 
>>in the same manner as MIPS_DEBUG sections.
>>
>>Also there was a fall through in the case statement that caused error 
>>messages to be printed twice for "Unhandled section header type".
>  
>

Thanks.   I already have an equivalent patch in my development tree
(from Alvaro Martinez Echevarria).  It is waiting for me to get some
time to release modutils 2.4.26.

Index: 25.5/obj/obj_mips.c
--- 25.5/obj/obj_mips.c Fri, 01 Mar 2002 11:39:06 +1100 kaos (modutils-2.4/c/10_obj_mips.c 1.4 644)
+++ 26.2(w)/obj/obj_mips.c Sat, 05 Apr 2003 08:36:33 +1000 kaos (modutils-2.4/c/10_obj_mips.c 1.5 644)
@@ -74,7 +74,8 @@ arch_load_proc_section(struct obj_sectio
     {
     case SHT_MIPS_DEBUG:
     case SHT_MIPS_REGINFO:
-      /* Actually these two sections are as useless as something can be ...  */
+    case SHT_MIPS_DWARF:
+      /* Ignore debugging sections  */
       sec->contents = NULL;
       break;
 
@@ -83,10 +84,10 @@ arch_load_proc_section(struct obj_sectio
     case SHT_MIPS_GPTAB:
     case SHT_MIPS_UCODE:
     case SHT_MIPS_OPTIONS:
-    case SHT_MIPS_DWARF:
     case SHT_MIPS_EVENTS:
       /* These shouldn't ever be in a module file.  */
       error("Unhandled section header type: %08x", sec->header.sh_type);
+      return -1;
 
     default:
       /* We don't even know the type.  This time it might as well be a

David Daney

Re: kernel modules

[David Daney]

David Kesselring wrote:

>Can someone please confirm that loading and unloading of kernel modules is
>functioning in the  2.4 release?
>
>When I try to load a wlan module that I compiled (with mipsel-*) I get
>relocation errors. I used the same options as I did to compile the kernel
>(for MIPS Malta board). If you have any ideas, please let me know.
>
>  
>
Modules also require compiling with -mlong-calls in addition to the 
"normal" kernel options.

David Daney.

Re: kernel modules

[Ralf Baechle]

On Mon, Oct 20, 2003 at 10:32:08AM -0400, David Kesselring wrote:

> Can someone please confirm that loading and unloading of kernel modules is
> functioning in the  2.4 release?
> 
> When I try to load a wlan module that I compiled (with mipsel-*) I get
> relocation errors. I used the same options as I did to compile the kernel
> (for MIPS Malta board). If you have any ideas, please let me know.

You're _not_ using the same options as the kernel's Makefile does for
building modules.

  Ralf

Re: kernel modules

[Zhang Haitao]

On Mon, Oct 20, Ralf Baechle wrote:
>
> 
> You're _not_ using the same options as the kernel's Makefile does for
> building modules.
> 
>   Ralf
> 
Hi, modules compiled using these parameters are working on my 2.4.21 SMP 
kernel:

	CFLAGS="-I .../include/asm/gcc -D__KERNEL__ -I.../include -Wall 
-Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer 
-fno-strict-aliasing -fno-common -G 0 -mno-abicalls -fno-pic -mcpu=XX 
-mips2 -Wa,--trap -pipe -DMODULE -mlong-calls"

XX = your chip style

Zhang Haitao

Re: kernel modules

[David Kesselring]

Thanks for your responses. I will try your suggestions.

David Kesselring
Atmel MMC
dkesselr@mmc.atmel.com
919-462-6587

Re: kernel modules

[Jonas Malaco]

Hi Mike,

On Thu, Feb 23, 2023 at 10:30:24PM +0000, mike mccool wrote:
> hello,
> 
> i am using lm-sensors/sensors on an AMD AM4 motherboard w/ 5700G APU
> and ubuntu 22.04
> 
> i added kernel module 'drivetemp' to get temp data from the 10 SATA
> drives on this box. i would like to filter-out(ignore) the drivetemp
> output from /usr/bin/sensors but cannot. the keyword 'chip' does not
> work so 'ignore' statements have no effect.
> 
> please add a new keyword, eg, 'module', so that it would be possible
> to craft filters like this:
> 
> module "drivetemp-scsi-0-*"
>    ignore temp1
> 
> or
> 
> module "k10temp-pci-00c3"
>    ignore Tctl
> 
> or
> 
> module "nvme-pci-2600"
>    ignore Sensor 1
>    ignore Sensor 2
> 
> regards

Is the error you're seeing "Undeclared bus id referenced"?

If that's the case, there are a couple of issues already open on GitHub
for that problem:

- <https://github.com/lm-sensors/lm-sensors/issues/230>
- <https://github.com/lm-sensors/lm-sensors/issues/369>

and I have a patch that addresses it:

- <https://github.com/lm-sensors/lm-sensors/pull/371.patch>

Please let me know if you give it a try.

Alternatively, either:

    chip drivetemp-scsi-*-*
        ignore temp1

or:

    chip drivetemp-*
        ignore temp1

might work even without the patch. And they should be enough since you
don't actually need to identify each drive individually.

Finally, yet another alternative is to not load (or build) the drivetemp
driver.

Jonas

kernel modules

[mike mccool]

hello,

i am using lm-sensors/sensors on an AMD AM4 motherboard w/ 5700G APU
and ubuntu 22.04

i added kernel module 'drivetemp' to get temp data from the 10 SATA
drives on this box. i would like to filter-out(ignore) the drivetemp
output from /usr/bin/sensors but cannot. the keyword 'chip' does not
work so 'ignore' statements have no effect.

please add a new keyword, eg, 'module', so that it would be possible
to craft filters like this:

module "drivetemp-scsi-0-*"
   ignore temp1

or

module "k10temp-pci-00c3"
   ignore Tctl

or

module "nvme-pci-2600"
   ignore Sensor 1
   ignore Sensor 2

regards

Re: Kernel Modules

[Felix Blanke]

Well, the mail still says the truth :)

On 7/10/11 11:57 AM, Helmut Hullen wrote:
> Hallo, Felix,
>
> Du meintest am 10.07.11:
>
>> I'll be quiet about this topic now. I've to admit that I was a little
>> bit drunk yesterday. Sorry again!
>
> Don't drink and write!
>
> Viele Gruesse!
> Helmut
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Kernel Modules

[Helmut Hullen]

Hallo, Felix,

Du meintest am 10.07.11:

> I'll be quiet about this topic now. I've to admit that I was a little
> bit drunk yesterday. Sorry again!

Don't drink and write!

Viele Gruesse!
Helmut

Re: Kernel Modules

[Felix Blanke]

You don't understood me. Ofc the developer need bug reports and all that 
stuff. But it's the way youre doing it. Imho a lot of your mails sounds 
like the only goal of them are to punish btrfs.

Maybe I'm the only one who feels this way, then I'm sorry. I'll be quite 
about this topic now. I've to admit that I was a little bit drunk 
yesterday. Sorry again!

Regards,
Felix

On 7/10/11 3:29 AM, Helmut Hullen wrote:
> Hallo, Felix,
>
> Du meintest am 10.07.11:
>
>> Did you ever say something positive about btrfs? :D All I read from
>> in the last months is complaining about btrfs.
>
> I use it, since many months.
> But it's still an adventure, I won't use it for valuable data.
>
>> I'm sorry but it seems that 90% for your comments are useless and
>> they sound like you only want to say something bad about btrfs.
>
> Do you really mean that this is a mailing list where everybody has to
> tell "it works!"?
>
> The most mailing list where I'm subscribed mostly have threads starting
> with "Houston, we've got a problem".
>
> -----------------------------
>
> By the way: I'm writing programs since more than 40 years, I know that
> nearly every program contains errors which the programmer didn't wish or
> expect. The programmer needs the reactions of the users.
>
> Viele Gruesse!
> Helmut
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Kernel Modules

[Goffredo Baroncelli]

On 07/09/2011 07:28 PM, CACook@quantum-sci.com wrote:
> On Saturday 9 July, 2011 10:12:43 you wrote:
>> If your btrfs lives on two or more devices you will have to run
>> 'btrfs device scan' prior to mount or give all devices as arguments
>> to mount.btrfs.
> 
> Ohhh, I'd added a disk drive without modifying fstab.  Thanks.
> 
> Where would you put a device scan to happen at boot?

The more recent distro put the scanning logic in the initrd. This should
be the right place.


> On another subject, I guess there are two ways to remove old snapshot
> directories: - btrfs subvolume delete - rm -rf

with rm -rf you can remove only the subvolume contents, but you cannot
delete a subvoulume.

> 
> I understand that snapshots are cumulative for files and do not
> duplicate, but is it necessary to use the subvolume delete command to
> preserve the integrity of remaining snapshots?

No. Apart removing the subvolume entry, "rm -rf" and "btrfs subvolume
delete" reach the same result. The latter is only a lot more efficient.

> And also, about once a week KDE locks up on me after a suspend, and I
> have to power-cycle it.  Is there any maintenance I should do on a
> btrfs part when this happens?

Normally you don't do anything. In any case you are not able to do
anything because there no is a tool like fsck available :-)


> 
> -- To unsubscribe from this list: send the line "unsubscribe
> linux-btrfs" in the body of a message to majordomo@vger.kernel.org 
> More majordomo info at  http://vger.kernel.org/majordomo-info.html .
> 

Re: Kernel Modules

[Helmut Hullen]

Hallo, Felix,

Du meintest am 10.07.11:

> Did you ever say something positive about btrfs? :D All I read from
> in the last months is complaining about btrfs.

I use it, since many months.
But it's still an adventure, I won't use it for valuable data.

> I'm sorry but it seems that 90% for your comments are useless and
> they sound like you only want to say something bad about btrfs.

Do you really mean that this is a mailing list where everybody has to  
tell "it works!"?

The most mailing list where I'm subscribed mostly have threads starting  
with "Houston, we've got a problem".

-----------------------------

By the way: I'm writing programs since more than 40 years, I know that  
nearly every program contains errors which the programmer didn't wish or  
expect. The programmer needs the reactions of the users.

Viele Gruesse!
Helmut

Re: Kernel Modules

[Felix Blanke]

Did you ever say something positive about btrfs? :D All I read from in 
the last months is complaining about btrfs.
In this case it was his fault because he forget to update the fstab. Im 
pretty sure it was also your fault when you screwed up your 2.6.38.5 
kernel...
I'm sorry but it seems that 90% for your comments are useless and they 
sound like you only want to say something bad about btrfs.

Regards,
Felix

On 7/9/11 1:33 PM, Helmut Hullen wrote:
> Hallo, Cacook,
>
> Du meintest am 09.07.11:
>
>> Just compiled a custom kernel, but unable to mount a btrfs partition.
>>   It essentially says 'unrecognized filesystem'.  What could be
>> missing?
>
> Perhaps you only need a newer kernel. Sounds funny, but  some days ago I
> had a similar problem, with kernel 2.6.38.5
>
> Then I compiled kernel 2.6.39.2 - all worked as well as (about) a week
> ago.
>
> Maybe I can't reproduce this behaviour, but I don't want to see it again
> - restoring more than 4 TByte is no fun.
>
> Viele Gruesse!
> Helmut
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Kernel Modules

[Hugo Mills]

[-- Attachment #1: Type: text/plain, Size: 2042 bytes --]

On Sat, Jul 09, 2011 at 10:28:03AM -0700, CACook@quantum-sci.com wrote:
> On Saturday 9 July, 2011 10:12:43 you wrote:
> > If your btrfs lives on two or more devices you will have to run 'btrfs
> > device scan' prior to mount or give all devices as arguments to mount.btrfs.
> 
> Ohhh, I'd added a disk drive without modifying fstab.  Thanks.
> 
> Where would you put a device scan to happen at boot?

   This is distribution dependent, but I do know that Debian will put
it in your initrd for you if you install Debian's btrfs-tools package.
If you have your root FS on btrfs, you *must* put the scan in an
initrd (or specify all the root devices as mount options in your
kernel command-line).

   If you don't use an initrd, then add the scan to your startup
scripts anywhere before the point that filesystems are mounted, and
anywhere after the point that block devices are detected (typically
when udev is started).

> On another subject, I guess there are two ways to remove old snapshot directories:
> - btrfs subvolume delete
> - rm -rf
> 
> I understand that snapshots are cumulative for files and do not duplicate, but is it necessary to use the subvolume delete command to preserve the integrity of remaining snapshots?

   No, effectively each snapshot is independent of the others (by the
magic of copy-on-write). When items from a snapshot are deleted, the
filesystem automatically cleans up by updating the extent reference
counts.

> And also, about once a week KDE locks up on me after a suspend, and
> I have to power-cycle it.  Is there any maintenance I should do on a
> btrfs part when this happens?

   No, if the storage stack from filesystem all the way down to the
drive platter handles barriers correctly, then btrfs should always be
in a consistent state, even over a power-cycle.

   Hugo.

-- 
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
  PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
              --- Welcome to Rivendell,  Mr Anderson... ---              

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 190 bytes --]

Re: Kernel Modules

[Helmut Hullen]

Hallo, Cacook,

Du meintest am 09.07.11:

> Just compiled a custom kernel, but unable to mount a btrfs partition.
>  It essentially says 'unrecognized filesystem'.  What could be
> missing?

Perhaps you only need a newer kernel. Sounds funny, but  some days ago I  
had a similar problem, with kernel 2.6.38.5

Then I compiled kernel 2.6.39.2 - all worked as well as (about) a week  
ago.

Maybe I can't reproduce this behaviour, but I don't want to see it again  
- restoring more than 4 TByte is no fun.

Viele Gruesse!
Helmut

Re: Kernel Modules

[CACook]

On Saturday 9 July, 2011 10:12:43 you wrote:
> If your btrfs lives on two or more devices you will have to run 'btrfs
> device scan' prior to mount or give all devices as arguments to mount.btrfs.

Ohhh, I'd added a disk drive without modifying fstab.  Thanks.

Where would you put a device scan to happen at boot?


On another subject, I guess there are two ways to remove old snapshot directories:
- btrfs subvolume delete
- rm -rf

I understand that snapshots are cumulative for files and do not duplicate, but is it necessary to use the subvolume delete command to preserve the integrity of remaining snapshots?


And also, about once a week KDE locks up on me after a suspend, and I have to power-cycle it.  Is there any maintenance I should do on a btrfs part when this happens?

Re: Kernel Modules

[Andreas Philipp]

On 09.07.2011 18:19, CACook@quantum-sci.com wrote:
> Just compiled a custom kernel, but unable to mount a btrfs partition.  It essentially says 'unrecognized filesystem'.  What could be missing?
>
> # File systems
> #
> CONFIG_EXT2_FS=y
> CONFIG_EXT2_FS_XATTR=y
> CONFIG_EXT2_FS_POSIX_ACL=y
> CONFIG_EXT2_FS_SECURITY=y
> # CONFIG_EXT2_FS_XIP is not set
> CONFIG_EXT3_FS=y
> CONFIG_EXT3_DEFAULTS_TO_ORDERED=y
> CONFIG_EXT3_FS_XATTR=y
> CONFIG_EXT3_FS_POSIX_ACL=y
> CONFIG_EXT3_FS_SECURITY=y
> CONFIG_EXT4_FS=y
> CONFIG_EXT4_FS_XATTR=y
> # CONFIG_EXT4_FS_POSIX_ACL is not set
> # CONFIG_EXT4_FS_SECURITY is not set
> # CONFIG_EXT4_DEBUG is not set
> CONFIG_JBD=y
> # CONFIG_JBD_DEBUG is not set
> CONFIG_JBD2=y
> # CONFIG_JBD2_DEBUG is not set
> CONFIG_FS_MBCACHE=y
> # CONFIG_REISERFS_FS is not set
> CONFIG_JFS_FS=y
> # CONFIG_JFS_POSIX_ACL is not set
> # CONFIG_JFS_SECURITY is not set
> # CONFIG_JFS_DEBUG is not set
> # CONFIG_JFS_STATISTICS is not set
> # CONFIG_XFS_FS is not set
> # CONFIG_GFS2_FS is not set
> # CONFIG_OCFS2_FS is not set
> CONFIG_BTRFS_FS=y
> CONFIG_BTRFS_FS_POSIX_ACL=y
> # CONFIG_NILFS2_FS is not set
> CONFIG_FS_POSIX_ACL=y
> CONFIG_FILE_LOCKING=y
> CONFIG_FSNOTIFY=y
> CONFIG_DNOTIFY=y
> CONFIG_INOTIFY_USER=y
> # CONFIG_FANOTIFY is not set
> CONFIG_QUOTA=y
> CONFIG_QUOTA_NETLINK_INTERFACE=y
> CONFIG_PRINT_QUOTA_WARNING=y
> # CONFIG_QUOTA_DEBUG is not set
> CONFIG_QUOTA_TREE=m
> # CONFIG_QFMT_V1 is not set
> CONFIG_QFMT_V2=m
> CONFIG_QUOTACTL=y
> CONFIG_QUOTACTL_COMPAT=y
> CONFIG_AUTOFS4_FS=y
> CONFIG_FUSE_FS=y
> CONFIG_CUSE=y
> CONFIG_GENERIC_ACL=y
If your btrfs lives on two or more devices you will have to run 'btrfs
device scan' prior to mount or give all devices as arguments to mount.btrfs.

Andreas

Kernel Modules

[CACook]

Just compiled a custom kernel, but unable to mount a btrfs partition.  It essentially says 'unrecognized filesystem'.  What could be missing?

# File systems
#
CONFIG_EXT2_FS=y
CONFIG_EXT2_FS_XATTR=y
CONFIG_EXT2_FS_POSIX_ACL=y
CONFIG_EXT2_FS_SECURITY=y
# CONFIG_EXT2_FS_XIP is not set
CONFIG_EXT3_FS=y
CONFIG_EXT3_DEFAULTS_TO_ORDERED=y
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y
CONFIG_EXT4_FS=y
CONFIG_EXT4_FS_XATTR=y
# CONFIG_EXT4_FS_POSIX_ACL is not set
# CONFIG_EXT4_FS_SECURITY is not set
# CONFIG_EXT4_DEBUG is not set
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_JBD2=y
# CONFIG_JBD2_DEBUG is not set
CONFIG_FS_MBCACHE=y
# CONFIG_REISERFS_FS is not set
CONFIG_JFS_FS=y
# CONFIG_JFS_POSIX_ACL is not set
# CONFIG_JFS_SECURITY is not set
# CONFIG_JFS_DEBUG is not set
# CONFIG_JFS_STATISTICS is not set
# CONFIG_XFS_FS is not set
# CONFIG_GFS2_FS is not set
# CONFIG_OCFS2_FS is not set
CONFIG_BTRFS_FS=y
CONFIG_BTRFS_FS_POSIX_ACL=y
# CONFIG_NILFS2_FS is not set
CONFIG_FS_POSIX_ACL=y
CONFIG_FILE_LOCKING=y
CONFIG_FSNOTIFY=y
CONFIG_DNOTIFY=y
CONFIG_INOTIFY_USER=y
# CONFIG_FANOTIFY is not set
CONFIG_QUOTA=y
CONFIG_QUOTA_NETLINK_INTERFACE=y
CONFIG_PRINT_QUOTA_WARNING=y
# CONFIG_QUOTA_DEBUG is not set
CONFIG_QUOTA_TREE=m
# CONFIG_QFMT_V1 is not set
CONFIG_QFMT_V2=m
CONFIG_QUOTACTL=y
CONFIG_QUOTACTL_COMPAT=y
CONFIG_AUTOFS4_FS=y
CONFIG_FUSE_FS=y
CONFIG_CUSE=y
CONFIG_GENERIC_ACL=y

Re: Kernel modules

[Chuck Kamas]

Koen,

Thanks, I'll give that a try.

Chuck


-----Original Message-----
From: openembedded-devel-bounces@lists.openembedded.org
[mailto:openembedded-devel-bounces@lists.openembedded.org] On Behalf Of
Koen Kooi
Sent: Sunday, May 17, 2009 11:27 AM
To: openembedded-devel@openembedded.org
Subject: Re: [oe] Kernel modules

On 17-05-09 20:13, Chuck Kamas wrote:
> Thanks,  I add a rrecommends for each kernel module I have in my
.config.
>
> BTW, is there a way to have OE scan the kernel .config and
automatically pull in all the kernel modules?

RRECOMMENDS = "kernel-modules"

regards,

Koen


_______________________________________________
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

Re: Kernel modules

[Koen Kooi]

On 17-05-09 20:13, Chuck Kamas wrote:
> Thanks,  I add a rrecommends for each kernel module I have in my .config.
>
> BTW, is there a way to have OE scan the kernel .config and automatically pull in all the kernel modules?

RRECOMMENDS = "kernel-modules"

regards,

Koen

Re: Kernel modules

[Tom Rini]

On Sun, May 17, 2009 at 09:24:51AM +0200, Koen Kooi wrote:
> On 16-05-09 23:38, Cliff Brake wrote:
>> On Sat, May 16, 2009 at 5:21 AM, G. Eismann<g.eismann@gmx.net>  wrote:
>>
>>> BTW, is there any way to install the modules but not the kernel image?
>>> I have the kernel in a separate partition, so I don't need it into the rootfs.
>>
>> One way is to put the following in the kernel recipe:
>>
>> FILES_kernel-image_<machine_name>  = ""
>
> Please don't do that, it breaks all sorts of things, one of which is  
> field upgrades.

If and only if it's what your distro wants, of course.

-- 
Tom Rini

Re: Kernel modules

[Chuck Kamas]

Thanks,  I add a rrecommends for each kernel module I have in my .config.
 
BTW, is there a way to have OE scan the kernel .config and automatically pull in all the kernel modules?
 
Chuck
 

________________________________

From: openembedded-devel-bounces@lists.openembedded.org on behalf of Koen Kooi
Sent: Sat 5/16/2009 1:55 AM
To: openembedded-devel@openembedded.org
Subject: Re: [oe] Kernel modules



On 16-05-09 01:22, Chuck Kamas wrote:
> Hi all,
>
> I am trying to compile a very small kernel.  To do this I have a few
> kernel modules I would like in the root file system.  But when I load OE
> I see that there are no kernel modules in the fs.  I found a way to
> include them by adding a RDEPENDS line with kernel-module-i2c-core.

And it can't be said enough:

NEVER use rdepends to drag in kernelmodules, use rrecommends instead


_______________________________________________
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

Re: Kernel modules

[Graeme Gregory]

Ihar Hrachyshka wrote:
> On Sun, May 17, 2009 at 10:24 AM, Koen Kooi <k.kooi@student.utwente.nl> wrote:
>   
>> On 16-05-09 23:38, Cliff Brake wrote:
>>     
>>> On Sat, May 16, 2009 at 5:21 AM, G. Eismann<g.eismann@gmx.net>  wrote:
>>>
>>>       
>>>> BTW, is there any way to install the modules but not the kernel image?
>>>> I have the kernel in a separate partition, so I don't need it into the
>>>> rootfs.
>>>>         
>>> One way is to put the following in the kernel recipe:
>>>
>>> FILES_kernel-image_<machine_name>  = ""
>>>       
>> Please don't do that, it breaks all sorts of things, one of which is field
>> upgrades.
>>     
>
> Your suggestion?
>
>   
As nothing depends on kernel-image other than kernel I would suggest
breaking this dependency. Then if you want the image of the kernel on
your rootfs you can explicitly depend on kernel-image in a task.

Graeme

Re: Kernel modules

[Ihar Hrachyshka]

On Sun, May 17, 2009 at 10:24 AM, Koen Kooi <k.kooi@student.utwente.nl> wrote:
> On 16-05-09 23:38, Cliff Brake wrote:
>>
>> On Sat, May 16, 2009 at 5:21 AM, G. Eismann<g.eismann@gmx.net>  wrote:
>>
>>> BTW, is there any way to install the modules but not the kernel image?
>>> I have the kernel in a separate partition, so I don't need it into the
>>> rootfs.
>>
>> One way is to put the following in the kernel recipe:
>>
>> FILES_kernel-image_<machine_name>  = ""
>
> Please don't do that, it breaks all sorts of things, one of which is field
> upgrades.

Your suggestion?

>
> regards,
>
> Koen
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>

Re: Kernel modules

[Koen Kooi]

On 16-05-09 23:38, Cliff Brake wrote:
> On Sat, May 16, 2009 at 5:21 AM, G. Eismann<g.eismann@gmx.net>  wrote:
>
>> BTW, is there any way to install the modules but not the kernel image?
>> I have the kernel in a separate partition, so I don't need it into the rootfs.
>
> One way is to put the following in the kernel recipe:
>
> FILES_kernel-image_<machine_name>  = ""

Please don't do that, it breaks all sorts of things, one of which is 
field upgrades.

regards,

Koen

Re: Kernel modules

[G. Eismann]

On Sábado 16 Mayo 2009 23:38:20 Cliff Brake escribió:
> On Sat, May 16, 2009 at 5:21 AM, G. Eismann <g.eismann@gmx.net> wrote:
> > BTW, is there any way to install the modules but not the kernel image?
> > I have the kernel in a separate partition, so I don't need it into the
> > rootfs.
>
> One way is to put the following in the kernel recipe:
>
> FILES_kernel-image_<machine_name> = ""

Thanks for the response. I'll try it.
-- 
  - Eismann -

Re: Kernel modules

[Cliff Brake]

On Sat, May 16, 2009 at 5:21 AM, G. Eismann <g.eismann@gmx.net> wrote:

> BTW, is there any way to install the modules but not the kernel image?
> I have the kernel in a separate partition, so I don't need it into the rootfs.

One way is to put the following in the kernel recipe:

FILES_kernel-image_<machine_name> = ""

Cliff

-- 
=======================
Cliff Brake
http://bec-systems.com

Re: Kernel modules

[G. Eismann]

On Sábado 16 Mayo 2009 09:31:24 Marcin Juszkiewicz escribió:
> Dnia sobota, 16 maja 2009 o 01:22:46 Chuck Kamas napisał(a):
> > Hi all,
> >
> > I am trying to compile a very small kernel.  To do this I have a few
> > kernel modules I would like in the root file system.  But when I load
> > OE I see that there are no kernel modules in the fs.  I found a way
> > to include them by adding a RDEPENDS line with
> > kernel-module-i2c-core. This places it in the rootfs.  My question is
> > there a better, automatic way, to have all kernel modules included in
> > the rootfs?
>
> "kernel-modules" package depends on all packages with kernel modules.
>

BTW, is there any way to install the modules but not the kernel image?
I have the kernel in a separate partition, so I don't need it into the rootfs.

Regards
-- 
  - Eismann -

Re: Kernel modules

[Koen Kooi]

On 16-05-09 01:22, Chuck Kamas wrote:
> Hi all,
>
> I am trying to compile a very small kernel.  To do this I have a few
> kernel modules I would like in the root file system.  But when I load OE
> I see that there are no kernel modules in the fs.  I found a way to
> include them by adding a RDEPENDS line with kernel-module-i2c-core.

And it can't be said enough:

NEVER use rdepends to drag in kernelmodules, use rrecommends instead

Re: Kernel modules

[Marcin Juszkiewicz]

Dnia sobota, 16 maja 2009 o 01:22:46 Chuck Kamas napisał(a):
> Hi all,
>
> I am trying to compile a very small kernel.  To do this I have a few
> kernel modules I would like in the root file system.  But when I load
> OE I see that there are no kernel modules in the fs.  I found a way
> to include them by adding a RDEPENDS line with
> kernel-module-i2c-core. This places it in the rootfs.  My question is
> there a better, automatic way, to have all kernel modules included in
> the rootfs?

"kernel-modules" package depends on all packages with kernel modules.

Regards, 
-- 
JID:      hrw@jabber.org
Website:  http://marcin.juszkiewicz.com.pl/
LinkedIn: http://www.linkedin.com/in/marcinjuszkiewicz

Kernel modules

[Chuck Kamas]

Hi all,

I am trying to compile a very small kernel.  To do this I have a few
kernel modules I would like in the root file system.  But when I load OE
I see that there are no kernel modules in the fs.  I found a way to
include them by adding a RDEPENDS line with kernel-module-i2c-core.
This places it in the rootfs.  My question is there a better, automatic
way, to have all kernel modules included in the rootfs?

Chuck

kernel Modules.

[Kevin Smith]

[-- Attachment #1: Type: text/plain, Size: 227 bytes --]

If I find I need or want a particular module that I didn't choose when I
first compiled the Kernel, can I compile said module w/o having to recompile
the entire kernel?

Im using RH 7.3, Kernel 2.4.22 with the newest POM. 
Kev

[-- Attachment #2: winmail.dat --]
[-- Type: application/ms-tnef, Size: 1520 bytes --]

Re: kernel modules

[Arnaldo Carvalho de Melo]

Em Tue, Nov 20, 2001 at 12:35:19PM -0800, Lee Chin escreveu:

> I know that if you write a kernel module, and dont modify any kernel
> source to get the module written, then you dont have to open the source
> for your module... but what if you include header files with in line
> functions?

Well, most probably all the binary only drivers use inline functions in
kernel headers, but as Alan says, talk to your lawyer 8)

- Arnaldo

kernel modules

[Lee Chin]

Hi,
I know that if you write a kernel module, and dont
modify any kernel source to get the module written,
then you dont have to open the source for your
module... but what if you include header files with in
line functions?

Thanks
Lee

__________________________________________________
Do You Yahoo!?
Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month.
http://geocities.yahoo.com/ps/info1