Kernel 3.12.6

[sbp]

Hi

I have also found problems with 3.12.6, where I'm unable to read from a file which IS present.

But as I really would like the I2S-DAC support. Therefore, I have been trying to build a piCore5.1 on kernel 3.10.25 (which also have the I2S support) - this is strictly for use in the piCorePlayer.

I'm having a problem.
My version boots:

Code: [Select]

Booting Core 5.1
Running Linux Kernel 3.10.25-piCore.
Checking boot options... Done.
Starting udev daemon for hotplug support... Done
BUT then it won't go further - the cursor just stays blinking....

Does anybody know what it is trying to load next?
And how I can troubleshoot?

Steen

[Paul_123]

I've not had problems with file access yet.   So far it is working for me......other than having to recompile one of the wifi drivers.

Do you think the problems with 3.12.6 are possibly with the cross-compiled kernel?   I noticed you changed to the new linaro toolchain...... around the same time we stared playing with this kernel.

I know the kernel is different, as I built using the same .config, and not all natively compiled modules would not work with the linaro built kernel.

[bmarkus]

Don't think it is toolchain related. New linaro is the native toolchain which is not used for kernel compilation. Kernel crosscompiled and cross toolchain not changed. Simply, using the same config file for 3.12.1 and 3.12.6 and the same toolchain 3.12.1 works, 3.12.6 doesn't.

[bmarkus]

In 3.12.7 the issues of 3.12.6 with memory allocation, killed tasks and loop mounts fixed, it works fine.

[sbp]

Hi bela

That is good to hear.
For me version 3.12.7 is also working fine, I haven't found any problems yet.

Steen

[bmarkus]

Thanks Steen.

[sbp]

Hi Béla

I noticed that the modules you make now are in the format like snd-bcm2835.ko.gz instead of when I compile I get snd-bcm2835.ko.

1. How do you get them in the gz format when you compile?
2. Can I for now simply compress my already made .ko files to the gz format?

Steen

[bmarkus]

Hi Béla

I noticed that the modules you make now are in the format like snd-bcm2835.ko.gz instead of when I compile I get snd-bcm2835.ko.

1. How do you get them in the gz format when you compile?
2. Can I for now simply compress my already made .ko files to the gz format?

Steen

Hi Steen

Kernel compilation results .ko modules which are simply gzipped after the compilation out of kernel compilation process. You can script it or do it manually. You can mix .ko and gzipped .ko in the system. What is important you must run depmod command always when you are changing modules or module format to make system aware of changes and update support files.

[sbp]

Thanks

I wont be needing Depmod for the two changes I make.

The first I change is the snd-bcm2835.ko with my own version that allows 192 kHz playback via HDMI (whereas the original only allow max 48 kHz)
And the other is the 8192cu.ko.gz with my own version where power saving has been disabled (as suggested by Paul)

So I simply change two files which are already present in the Alsa-package and the Wifi package.

Steen

[Paul_123]

Does zipping the modules use less RAM space on the ram drive?   is there a benefit to do this.

You can gzip them all after "installing" the modules.   Go into your temp installation directory and run

find . -name *.ko | xargs gzip

Is there really a reason to run depmod?   doesn't depmod run during boot anyway?   I struggle with running depmod outside the normal path.

[bmarkus]

Does zipping the modules use less RAM space on the ram drive?   is there a benefit to do this.

Modules in base are loaded in RAM as all other files, gzipping them saves some RAM.

gzipping modules in .tcz reduces tcz size by cca. 10%.

depmod is executed at boot, I referred to case when one is changing modules online in a running system. Also in initrd dep file must be in sync with modules in initrd.

[Paul_123]

Modules in base are loaded in RAM as all other files, gzipping them saves some RAM.

gzipping modules in .tcz reduces tcz size by cca. 10%.

depmod is executed at boot, I referred to case when one is changing modules online in a running system. Also in initrd dep file must be in sync with modules in initrd.

When I built my kernel, I just used the dep that was in the installed modules directory .....so all of the lines referred to the .ko extension, I did gz the modules.   It did work fine.   But I would rather do it the right way.

After building the kernel and installing the modules to /tmp/modules, and gzipping and re-running depmod, All I get is a zero length modules.dep file

Code: [Select]

cd /tmp/modules
find . -name *.ko | xargs gzip
sudo depmod -a -b /tmp/modules 3.12.7-piCore+

This is being done on my cross-compiler system which is an debian wheezy-amd64 based system.....

[tinypoodle]

A simple approach could be to use the gzip extension which has a "recursive" option.

[Paul_123]

Interesting that not all versions of depmod work with modules that are gzipped.

Seems the busybox implementation is one that does.   But only if you compile busybox with the "simplified modutils" turned off.