I am tryinng to insert a module in BT3 in both formats(lzm and mo)
Which worked in BT2..
Some error occured while inserting module to live filesystem
bt ~ # /usr/bin/uselivemod libdevmapper_1_02_08.lzm
module file is stored inside the union, moving to /mnt/live/memory/modules first...
Cannot read module data. corrupted download?
error inserting module to live filesystem
Do I make a mistake or is BT3(startet from CD-ROM) not yet ready to insert modules?
Thank's a lot for any feedback!
Maybe it's a CR-RW with some kind of on the fly burning implemented. it's possible right?
I can't get any .lzm modules to load using uselivemod, but I can take the same modules and put them in the modules directory and they'll load at boot time. Putting the .lzm on a thumb drive or windows share gets rid of the "moving" message, but they still don't load.
I may be wrong, Probably, but that error relates to the command is incorrect.
Follow this guide carefully and let me know how it went
It's best to try, and google, then try, and google! and google more!
I am affraid, but Slax6 does definitely support inserting modules if the PC was booted from CD-ROM :-)
(and I hope the BT developpers will soon make that great feuture work in BT3)
if we have a look at dmesg you'll prob find stuff like these suspicious messages...
VFS: Can't find ext4 filesystem on dev loop37.
GFS2: not a GFS2 filesystem
GFS2: Unrecognized block device or mount point /dev/loop37
GFS2: gfs2 mount does not exist
As it turns out the mount option does not recognize that the .lzm files actually has a squashfs file system.
A rather nasty hack would be to edit /usr/lib/liblinuxlive
around line 346 something you'll find the mount command used...
mount -n -o $OPTIONS "$LOOPDEV" "$2" >/dev/null 2>&1
if this line is changed to:
mount -n -o $OPTIONS "LOOPDEV" "$2" -t squashfs >/dev/null 2>&1
loading modules will work, well it does for me.
BUT - this will probably BREAK everything else since it looks like that code is used for other things as well! -- Don't count on your computer booting with this line of code!
A new version of the live scrips would be a better solution or maybe there is a better way to use them?