Tiny Core Linux
Tiny Core Base => Raspberry Pi => Topic started by: sbp on May 04, 2014, 11:13:43 AM
-
Hi
From time to time I'm struggling when I try to build a new kernel - it is often when the kernel is jumping from 3.12 to 3.13 or something similar. But right now I have problems going from a 3.14.1 to 3.14.2.
I don't know what the problem is.
I usually use the .config file from one of bmarkus build piCore like 3.14.1 then I change the path for my cross-compiler and that is usually the only change.
This time it build the kernel without problems
I unsquashed the *.gz file - changed the directory name from lib/modules/3.14.1-piCore+ to lib/modules/3.14.2-piCore+ (and it is the correct name of the kernel)
Then changed all the content in the subdirectories with content from the newly build modules.
Then I squashed it again.
Copied them to the root of the SD-card
Changed the content of config.txt and cmdline.txt file (so it loads the correct kernel and used the correct size).
I also build the:
alsa-modules-3.14.2-piCore+.tcz and md5checksum file
and the
wireless-3.14.2-piCore+.tcz and the md5checksum file
Then I booted and it completely booted - but it complain when I try to modprobe anything.
It says that any module I try to use is "not found in depmod.dep"
Can anybody see where my error is?
Steen
-
Without having the image hard to say anything.
-
Would you have time to have a look?
Steen
-
Send it
-
Thanks
you got mail.
The reason for my interest in this kernel is that in the last two days the USB driver was improved considerable and the version I build using 3.14.1 was reported to fix many of the USB-audio problems that we had before.
But when I tried to build 3.14.2 I run into these problems.
STeen
-
Problem is that
/lib/modules/3.14.2-piCore+/kernel.tclocal
points to
/usr/local/lib/modules/3.14.1-piCore+
instead of
/usr/local/lib/modules/3.14.2-piCore+
It will work after fixing it :)
-
Thank you very much for taking your time to help.
That was a missing point in my knowledge, so hopefully I can build new kernels without these problems in the future.
Steen
-
OK, now I'm back home and wanting to fix my bug.
first I deleted the /picoreplayer/3.14.2/moduler/lib/modules/3.14.2-piCore+/kernel.tclocal
the tried to make a new link
ln -sf /picoreplayer/3.14.2/moduler/usr/local/lib/modules/3.14.2-piCore+ /picoreplayer/3.14.2/moduler/lib/modules/3.14.2-piCore+/kernel.tclocal
However, this results in the creation of a /picoreplayer/3.14.2/moduler/lib/modules/3.14.2-piCore+/kernel.tclocal/ directory which is linked to the correct path, whereas I need the creation of a /picoreplayer/3.14.2/moduler/lib/modules/3.14.2-piCore+/kernel.tclocal file
/Steen
Edit: I managed to fix it using winscp - right click on file and change the link path.
However, I would like to know the correct way to do it (if it is possible on a cross-compile computer??) using cli
-
Hi bmarkus
Just another question when building a new kernel.
I'm almost finished building kernel based on the latest 3.14.4 as there have been a few fixes on the USB and HDMI handling which I probably need for my piCorePlayer.
However there is something I don't quite understand.
I extracted your 3.14.4 kernel (140519.gz) and started replacing all the content in "lib/modules/3.14.4-piCore+/kernel with my newly build modules.
(I simply use WinSCP for that)
However, I noticed that the two files in the fs/fuse/ directory actually links to another place
"/picoreplayer/3.14.4/moduler/lib/modules/3.14.4-piCore+/kernel/fs/fuse/cuse.ko.gz"
links to
/tmp/tcloop/filesystems-3.14.4-piCore+/usr/local/lib/modules/3.14.4-piCore+/kernel/fs/fuse/cuse.ko.gz
and
"/picoreplayer/3.14.4/moduler/lib/modules/3.14.4-piCore+/kernel/fs/fuse/fuse.ko.gz"
links to
/tmp/tcloop/filesystems-3.14.4-piCore+/usr/local/lib/modules/3.14.4-piCore+/kernel/fs/fuse/fuse.ko.gz"
How do I manage this? For now I simply let your files in place as we both are using 3.14.4-piCore+ but when we are at different kernel numbers there might be a problem.
So how do I manage this problem?
I seem to have a problem dealing with these link files when updating the kernel (see the post right above also).
What is your method of updating the kernel modules?
Steen