[prev in list] [next in list] [prev in thread] [next in thread] 

List:       lids-user
Subject:    Re: [lids-user] installing/inserting lids module fails...
From:       "Sander Klein" <lids () roedie ! nl>
Date:       2006-02-28 15:08:14
Message-ID: 59414.212.127.161.162.1141139294.squirrel () www ! roedie ! nl
[Download RAW message or body]

Hey,

just for the record, could you try this using kernel 2.6.14? The lidspatch
was meant for that kernel.

Regards,

Sander Klein

On Tue, February 28, 2006 6:45, Hasan Rezaul-CHR010 said:
> Hello,
>
> I am a brand-new LIDS user. I am using a Linux 2.6.10 kernel that is
> almost the same as the vanilla kernel.
>
> I successfully applied the  lids-2.2.2-2.6.14.patch  to my kernel.
>
> Then I ran linux.menuconfig, and deselected SELinux, and deselcted the
> Default Linux Capabilities. I selected SHA256 in the Cryptographic API
> options, and also under the Security Menu, I selected LIDS, and chose
> LIDS to be a module, and selected all the submenus of LIDS.
>
> Then I successfully rebuilt my kernel (with LIDS), built the filesystem,
> and nfsmounted my kernel image onto a Board running on a PQIII 8548
> processor.
>
> The card boots up fine, and I even see the  lids.ko  module present in
> one of the module directories.
> (/lib/modules/kernel/security/lids/lids.ko)
>
> But when I try to insert the LIDS module (insmod lids.ko), module
> insertion fails with a segmentation fault, and I get the following error
> message(s) in my 'dmesg' :
>
>
> LIDS: Initializing...
> LIDS_ERR: failed
> Oops: kernel access of bad area, sig: 11 [#1]
> NIP: C0024EB0 LR: D102A67C SP: CF6E9DB0 REGS: cf6e9d00 TRAP: 0300    Not
> tainted
> MSR: 00029000 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 00
> DAR: 00000004, DSISR: 00000000
> TASK = c0716480[990] 'insmod' THREAD: cf6e8000
> Last syscall: 128
> GPR00: 00100100 CF6E9DB0 C0716480 00000000 C01B5DBC 00000000 00661B60
> 00000000
> GPR08: 00000004 D1030000 CFBAFE9C 00200200 00005000 1009680C 00000012
> 00000000
> GPR16: 00000000 D1032F4C 00000000 D1032F40 D101EA28 D11E9000 D101EEB0
> 0000001C
> GPR24: 0000001D D1014000 C01F0000 C0250000 D1032F40 00000000 00000000
> C01F4094
> Call trace: [d102a67c]  [d102c770]  [d11e9090]  [c00394a8]  [c00021c8]
>
> Any hints, suggestions, of what I may be doing wrong, or what I can do
> to correct this problem ?...
>
> Thanks in advance,
>
> - Rezaul.
>




-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd_______________________________________________
lids-user mailing list
lids-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lids-user

[prev in list] [next in list] [prev in thread] [next in thread]