This is what I did to compile the kernel. # taxzpvf linux-2.4.19.tar.gz
Made a check-up on the upgrading pre-requistes based on : http://www.freeos.com/articles/3579/ follow this until the last page "Edit your lilo.conf...") >From then on, the Suse linux 7.3 deviates slightly from the article as Suse put the >kernel in the /usr/include directory and use silo.conf instead of lilo.conf. I >decided to follow the typical way and downloaded the linux 2.4.19 from kernel.org and >put it in /usr/src. Tne Ultralinux FAQ (www.ultralinux.org) is the best bet from here >on. # make clean # make xconfig => changed nothing apart from windows file system and IPv6 support # make dep # make # make bzvmlinux => make bzImage didn't work but this did # make modules install The kernel wouldn't compile if the following links did not exist (errors appeared at the end of make dep). I created a symbolic links as follows : # cd /usr/src # ln -s /usr/include/linux-2.4.19 linux # cd /usr/include # ln -s /usr/src/linux/include/linux linux The links look bizarre but that's how linux is and what I found after two days search on the net. The kernel wouldn't boot if vmlinux wasn't moved from /usr/src to / (and update the silo.conf accordingly) For some reason the system couldn't find the vmlinux, doing this solved the problem. Eivan -----Original Message----- From: Joshua Uziel [mailto:[EMAIL PROTECTED]] Sent: 10 September 2002 12:43 To: Nick Thompson Cc: CERASI Eivan; [EMAIL PROTECTED] Subject: Re: [suse-sparc] Does SUSE sparc Kernel 2.4 work on Sparc10 ? * Nick Thompson <[EMAIL PROTECTED]> [020905 19:58]: > I thought NONE of the 2.4 kernels ran on the sparc32 processors? > > Did someone get 2.4 running consistently on the Sun4m (sparc32) processor? Yes, a few of us put some time into fixing things for 2.4.19 on sparc32 systems. Both sun4c and sun4m systems should work fine, but no promise with the sun4d systems. The biggest remaining issues are the ss5/170 flakiness (but that's nothing new) and a segfault when you run swapon(1) on an SMP machine (but it's harmless as it seems to otherwise work). -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
