Hi,

I've not been having much luck with the kernels I've compiled so far.

The first kernel panic'd on boot saying it needed pentium+ even though I
chose 386 in the config.

The second kernel fixed this by enabling unsync'd tsc support (I think
this is what fixed it, I think I changed some other stuff too...), but
it wouldn't load any modules - I think I forgot to make mrproper before
recompiling or something similar.

The third kernel won't load modules either, complaining of unknown
symbols ("insmod slhc" can't find kmalloc, kfree, or printk, "insmod
slip" prints out about 20 unknown symbols).

This is all with a vanilla 2.4.29 kernel, because the current uClibc
buildroot uses that version. Should I try with a different kernel version?

The procedure I used to install was to "make modules_install" on my FC3
box, then tarball up the installed modules directory for the kernel
version, and copy to a floppy along with the bzImage, then unpack the
modules and copy the bzImage to /boot. I did notice that "make
modules_install" on the FC3 box couldn't find depmod.old when making
System.map - is that what is causing the unknown symbol errors?

Maybe SLIP is overkill, all I need to do is transfer files - is it
possible to transfer files over a null-modem cable without having to
recompile the kernel for SLIP?

Thanks for your help,


Claude

tak_cc wrote:

>Hey,
>Just to say that you don't need to compile the kernel in the uClibc
>build environment. All you need to do is compile it on FC3 and copy
>the bzImage across and replace it with the one in /boot. There are a
>few special parameters that you need to set, this page should help:
>http://www-128.ibm.com/developerworks/linux/library/l-lwl1/
>You shouldn't need to recompile the kernel for you big box, just
>modprobe slip and the module should load.
>Good luck
>James
>
>
>--- In smalllinux@yahoogroups.com, ClaudiusMaximus
><gloriousclaudiusmaximus@y...> wrote:
>
>
>>tak_cc wrote:
>>
>>
>>
>>>Hi, glad you managed to get it to work, sorry there hasn't been much
>>>additional development recently.
>>>I had a look at your posting on socialgeek, a few (useful :) )
>>>corrections. Small linux before the 0.9.0 series was based on libc5
>>>however is now based on uClibc. it is pretty easy to compile programs.
>>>Go to www.uclibc.org and grab the build image, mount it and then
>>>chroot in and then compile a program.
>>>
>>>
>>>
>>Ok, I just checked what I have on my 386sx, and it seems I
>>have both uClibc and libc5 installed, but the libc5 file is dated
>>1997 so I guess that came from one of the various Slackware 3.3
>>packages I installed on top of smalllinux2/0.9.0.2 - probably
>>binutils or gcc? I should have written it down at the time...
>>
>>I'll add that correction to the socialgeeks thread.
>>
>>
>>
>>>If you look on the sourceforge
>>>site i have compiled various programs such as links, thy and ncftp.
>>>
>>>
>>>
>>>
>>Yes, I noticed those, I've got links from there installed and working :)
>>
>>
>>
>>>To get slip working i you are going to need to recompile the kernel,
>>>
>>>
>>>
>>>
>>Ah. I've only successfully compiled a kernel under debian,
>>my attempts on redhat9 failed miserably, but hopefully the
>>uClibc buildroot will make things easier.
>>
>>I will get a vanilla 2.4.22 kernel source and try building it in
>>the uClibc chroot.
>>
>>Do I need to compile a kernel for my FC3 box too?
>>
>>
>>
>>>and then follow this guide:
>>>
>>>
>http://www.superant.com/cgi-bin/smalllinux.pl?Slip_Networking
>
>
>>>
>>>
>>>
>>>
>>Hmm, that site seems to be down at the moment, but this
>>mirror seems to work:
>>http://smalllinux.sourceforge.net/slip01.html
>>
>>
>>
>>>anything else just shout :)
>>>james
>>>
>>>
>>>
>>>
>>Many thanks for the tips, and you can bet I'll run into trouble
>>and come crying for more help :-)
>>
>>
>>Claude
>>--
>>http://claudiusmaximus.tk
>>
>>
>>
>>>--- In smalllinux@yahoogroups.com, ClaudiusMaximus
>>><gloriousclaudiusmaximus@y...> wrote:
>>>
>>>
>>>
>>>
>>>>Hi all,
>>>>
>>>>I got smalllinux2 0.9.0.2 working on a 386sx with 4MB RAM, see this
>>>>thread for full details:
>>>>http://forums.socialgeeks.com/index.php?showtopic=1418
>>>>
>>>>I want to transfer files between minimus (the 386) and maximus (my
>>>>
>>>>
>main
>
>
>>>>computer running Fedora Core 3) over a null-modem cable. I think
>>>>
>>>>
>SLIP
>
>
>>>>is the way to go, but I'm unsure of the steps needed to get this
>>>>
>>>>
>>>>
>>>>
>>>working
>>>
>>>
>>>
>>>
>>>>(I've never used SLIP before).
>>>>
>>>>I think I need to get kernel modules for SLIP, but do I need any
>>>>
>>>>
>other
>
>
>>>>networking kernel modules?
>>>>
>>>>Do I need to create something in /dev for the serial port? At the
>>>>moment there is just the following (on minimus):
>>>>crw-r--r-- 1 root root 5, 1 May 27 2002 console
>>>>crw-r--r-- 1 root root 29, 0 May 27 2002 fb0
>>>>brw-r--r-- 1 floppy floppy 2, 0 May 27 2002 fd0
>>>>brw-r--r-- 1 root root 3, 0 May 27 2002 hda
>>>>brw-r--r-- 1 root root 3, 1 May 27 2002 hda1
>>>>brw-r--r-- 1 root root 3, 2 May 27 2002 hda2
>>>>brw-r--r-- 1 root root 3, 3 May 27 2002 hda3
>>>>brw-r--r-- 1 root root 3, 4 May 27 2002 hda4
>>>>crw-r--r-- 1 root root 1, 2 May 27 2002 kmem
>>>>crw-r--r-- 1 root root 1, 1 May 27 2002 mem
>>>>crw-r--r-- 1 root root 1, 3 May 27 2002 null
>>>>brw-r--r-- 1 root root 1, 0 May 27 2002 ram0
>>>>crw-r--r-- 1 root root 5, 0 Apr 22 20:43 tty
>>>>crw-r--r-- 1 root root 4, 0 May 27 2002 tty0
>>>>crw------- 1 claude claude 4, 1 Apr 22 21:12 tty1
>>>>crw------- 1 claude claude 4, 2 Apr 22 20:43 tty2
>>>>crw-r--r-- 1 root root 4, 3 May 27 2002 tty3
>>>>crw-r--r-- 1 root root 4, 4 May 27 2002 tty4
>>>>crw-r--r-- 1 root root 4, 5 May 27 2002 tty5
>>>>crw-r--r-- 1 root root 1, 9 May 27 2002 urandom
>>>>
>>>>Thanks for any help you can provide,
>>>>
>>>>
>>>>Claude
>>>>--
>>>>http://claudiusmaximus.tk
>>>>
>>>>