SliTaz Forum
You are not logged in.
Pages: 1
I built an iso out of V3 (in VM) using tazlito. Custom kernel made via make tazpkg and it boots. But had module format problem. No depmod installed!?
Within second ISO I added module-init-tools and depmod as on first run I saw modules not loading. Many reboots later I am still seeing a few modules that fail to load due to not being recognized in gz format.
Attempted fixes:
tazpkg recharge
tazpkg upgrade. (from forum, didnt work) offered to replace my custom kernel for stock one.... how to I lock my custom kernel??
Also tried running:
depmod
sync
wait ten minutes
tazusb writefs gzip /dev/hda1
sync when done
wait 5 minutes
reboot
same problem.
I have this in a 256mb ram tablet computer with a 500mb flash on 44pin ata module. Other odd things I notice is that autologin wont work as in I have to manually call slim. After xorg was set I did run slim from root prompt and writefs’d it to save it. I set autologin in /home/boot/extlinux/extlinux.conf as well as /home/boot/extlinux/en.conf. boot lines on each file are the same:
(indicating additions only)
Append=vga=788 autologin lang=en kmap=us home=/dev/hda1 modprobe=penmount acpi=force
Any tips would be appreciated
Offline
The v3 modules are compressed with *lzma* (and have a .gz suffix) and depmod & co come from busybox, see http://hg.slitaz.org/wok/file/efca0feeb58e/busybox/stuff/busybox-1.12.0-zmodules.u#l92
Hope it helps...
Offline
That explains why running depmod and then writefs are not fixing. But it does not explain how to fix or avoid.
Busybox is installed so that then makes this a bug report. Why do images made with tazlito not load some modules with bad format errors ?
Offline
Went back in to this install and issued:
/bin/busybox depmod
it finished
/bin/busybox modprobe snd-cs5535audio
Error..... Invalid modue format
modprobe snd-cs5535audio
Error ..... Invalid module format.
My guess is that the script that made
make tazpkg
within kernel source folder did not allow depmod to finish before moving on to next step. I say this because all other special things I add to kernel are there with exception to the sound which i I am not mistaken is near the bottom of the tree. Last items to compile. If I have most modules loading and not the last of which, sound, I would think that the script that made kernel “make tazpkg” cut the depmod action off short. If I wanted to redo this is there a way I can ensure that all modules are built and in recognizable format before moving on?
Offline
Are you mixing slitaz v3 v4 and v5 ?
- busybox v3 depmod knows v3 modules
- kmod v5 depmod knows v5 modules
Offline
Would be hard to. I have a vm set up for each version. Tazlito conf is setup to append v3 to v3iso’s v4->v4 etc. I us gftp to move to nas and then to a windows machine where i use Lili version 2 to write to usb. I use folders to separate iso’s. There is no way I could mix packages.
There is one rouge thing I have to do that I did not mention but its on v4 only. I use old syslinux from v3 and move syslinux and exra package in to packages folder before adjusting disro-packages.list to include. I have not gotten v4 to work on tablets yet, only v3. So in v3 the syslinux version should align and that would not be an issue. Syslinux v4 will not boot hardware. Slitaz v4 with old syslinux will not produce a gui for me. There are no errors in X. So for now I try to make kernel in V5 but tools fail. When it does I work on v3 some more. I have v3 installed on hardware and this is where I get a mix of usable and unusble modules. No cross pollenation.
In theory I should be able to writefs after a depmod and it should be fixed but I feel that the lower part of the module tree was corrupted somehow. I use 8192mb in vm and v3 is not installed. I run it as live iso and make sure to update tazpkg and recharge before building.
Come to think of it I start with kernel and then go to tazlito. On V5 I have not exported any iso’s yet because I cant get tools to make a tazpkg of the kernel. I tried v5 stock iso but it wont boot due to newer syslinux than I can use.
Offline
This morning I deleted vm and started over. Gave 12gb ram and an 8gb drive but have not installed. Running live.
Upon booting I recharge tazpkg. Update and install slitaz-toolchain, ncurses—dev, perl and bc. I confirm that I need to use bash part way through the install of toolchain. I get kernel source and watch a few more packages come in. I make kernel through menuconfig and this time I ran depmod again after it completed. on V4 make tazpkg gets most of the way through but at end when its linking and about to compress it I get makefile error now and a number. On v3 this finishes but I get below results after I move it in to a tazlito directory for building in to iso.
I have tried this on v3 and v4 yesterday in to last night. I still get some kernel modules that load and some that indicate bad module format. Same exact ones too. My soundcard is not loading due to format. I added penmount and atlas_btns from input drivers and thee take each and every time. Only the last of the modules to build get corrupted somehow. New usb sticks were bought yesterday and used. Two different sets of hardware and two ram levels but both show the same result with the modules.
Once there I run depmod and modprobe again but problem persists.
Offline
This is solved.
Thinking on how to apologize upon my own errors....
I did not put deprecated PATA stuff in to kernel as built in and left as module to load. This is now allowing all ko.gz drivers to load at boot. This is great! I first tested with i486 processor and am now rebuilding slimmer and as geode specific. Narrow it down.
My apologies for thinking this was Slitaz script related. Needed to start with huge style kernel again and retrace. .
I look forward to learning more about your tools and hopefully coming more current on your distro while still building newer images with older syslinux. Aldo on to fonts for xvkbd!
Offline
Building all needed modules as * or built in to the kernel and not as a loadable module has solved this
Offline
Pages: 1
[ Generated in 0.017 seconds, 7 queries executed - Memory usage: 1.55 MiB (Peak: 1.77 MiB) ]