Eric,
Thanks for the help. I followed your instructions in a previous post on
building the minimum packages after a kernel build: modules, initrd,
and root.lrp. ipsec was also built/packaged from the same kernel.
Today I tried beta 2.3:
1. Downloaded linux-2.4.29.upx (renamed to linux), initrd_ide (renamed
to initrd), root, modules; copied to the root of my compact flash drive
C:\.
2. Changed leaf.cfg to reflect above packages + my original etc and
config and no more.
3. Tried to boot but got stuck at:
RAMDISK: Compressed image found at block 0
After giving up on Beta 2.3, I then I copied all minimum packages
(including etc and config) from the 2.2.2 ISO along with kernel. No
changes made. leaf.cfg:
LRP=modules,root,config,etc
Booted up just fine... I then went inside /tmp and created a file
called "mii" (mii.o is in /lib/modules):
foobar# touch mii
foobar# insmod mii
Using mii
insmod: error reading ELF header: Success
insmod: Could not load the module: Success
So this behavior has been there for some time?
-cpu
Eric Spakman wrote:
>Cpu,
>
>>Eric,
>>
>>It looks like it's trying to load /lib/ipsec/ipsec (the shell
>>script).
>>Does insmod default to the current directory? Perhaps the ipsec
>>scripts
>>are being run from within /lib/ipsec.
>
>
>No insmod shouldn't default to the current directory, just tested it
>myself and ipsec is loaded by the ipsec script without problems.
>
>About the 'if test ! -f $ipsecversion' tested multiple times: first
>it tries just to insmod it (which should work, see above), if that
>fails it tests if the kernel is modulair and tries to insmod it from
>within the modules directory and finally if that doesn't work it
>exits. The test is just to see if ipsec is loaded.
>
>>Everywhere else it loads fine:
>>
>>foobar# insmod ipsec
>>Using /lib/modules/ipsec.o
>>
>>Here are some of the changes I've made:
>>
>>- added USB keyboard support: input.o/hid.o/keybdev.o
>>
>>- NTFS, UDF support. All modules. I also splurrged on NCP support
>>
>>- changed the processor to VIA-C3-2 (not too useful right now, but a
>> backport of the PadLock cryptography engine to 2.4.x is around
>> the corner, figured I'd kick the tires around).
>>
>>- selected "Video mode selection support" in console drivers so I
>>can
>>
>> choose different text modes (vga=x in syslinux.cfg 80x30,
>>etc...).
>>
>>
>>That's about it for the kernel. Maybe a couple of other things.
>>
>>I also did a lot of package consolidation. Basically, I rollup
>>several
>>packages in one (where it seems appropriate). Now that I think
>>about, I
>>never did build etc.lrp using buildtool...still using etc from
>>2.2.2,
>>could that be a problem? I will go ahead and test using the official
>>builds regardless, if this really seems like a problem on my end.
>>Despite this, everything appears to be working okay. -cpu
>
>
>Using the 2.2.2 etc file shouldn't be the problem, but merging and
>changing packages could very well be a problem. The packages are
>carefully tuned to be correct (f.e. for backup) and contents.
>Changing that kind of things can easely lead to strange problems,
>like it appears with ipsec.
>
>Also changing processor type without recompiling kernel related
>packages or modules could lead to problems (if not done absolutely
>right).
>
>You should know exactly what you are doing when changing kernel setup
>and packages, a lot of things are thightly coupled.
>
>Eric
>
>
__________________________________
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
------------------------------------------------------------------------
leaf-user mailing list: [email protected]
https://lists.sourceforge.net/lists/listinfo/leaf-user
SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
