Tiny Core Extensions > TCE Tips & Tricks
Compiling kernel and modules on TC
kerpob:
Well on my 4th attempt I have succeeded! I am posting this from tcl 2.6.28.6 on the eee. Only the wireless is called wlan0 instead of ath0 now for some reason.
My first 3 attempts got as far as a frozen jwm, although I could drop to cli and connect to the internet there. Only succeeded when I just copied the existing tcl .config file and then got rid of non eee stuff and enabled the atheros wireless driver.
EDIT: Still need the wireless tools tce to get wireless up.
kerpob:
Couple of problems I'm having. Hope someone can help.
1. I have modified bootlocal.sh with 3 lines to get the wireless working (ifconfig wlan0 up then iwconfig wlan0 essid any then udhcpc -i wlan0). Doesn't seem to work at boot, but does if I run it after boot (by simply clicking on it in Rox file manager.
2. No sound. Have installed oss and also tried alsa, but soundon and alsaconf commands aren't recognised. Now my new kernel doesn't allow modules - does that matter or is it something else?
Actually - while typing this I've realised that I ran the boot command home=sda2 but forgot to add it permanently in grub, so local copies going missing may solve either or both of the above. Will edit this with a, possibly, shamefaced update in a few moments... :-[
curaga:
1. It probably needs to wait some secs to allow the wireless to initialize. For example "sleep 5" right before the ifconfig
2. Both the OSS and ALSA extensions have the support in modules; if your kernel doesn't support modules, the relevant driver can't be loaded.
To get over this you'd need to compile the relevant module into the kernel, which is only currently possible for ALSA.
kerpob:
--- Quote from: curaga on February 22, 2009, 05:36:59 PM ---1. It probably needs to wait some secs to allow the wireless to initialize. For example "sleep 5" right before the ifconfig
2. Both the OSS and ALSA extensions have the support in modules; if your kernel doesn't support modules, the relevant driver can't be loaded.
To get over this you'd need to compile the relevant module into the kernel, which is only currently possible for ALSA.
--- End quote ---
1. No joy - put sleep before and after. Must be something else. Is there a way to run the commands after jwm is active?
2. Thanks - I can't remember if I had the drivers compiled into the kernel or not. Just have to wade through menuconfig to find out
Juanito:
--- Quote from: kerpob on February 22, 2009, 05:44:23 PM ---2. Thanks - I can't remember if I had the drivers compiled into the kernel or not. Just have to wade through menuconfig to find out
--- End quote ---
If I remember correctly, the "soundcore" module is not enabled in the default tc config - this is required for alsa to work.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version