When compiling the kernel itself, use 'make bzImage, not zImage. That will create a .bz2 compression of the kernel image. I don't think zImage will ever work again; they should probably get rid of it. If I were you, I would read all possible docs you can find about kernel compilation. You're basically on track for compiling a kernel but as for getting a current version of speakup going, do the following: get a new source of the kernel from ftp.kernel.org and download linux-2.4.20.tar.gz; untar it into /usr/src and make a symbolic link linux to point to linux-2.4.20 created by the tar extraction. On the side, get the checkout script from lnx-speakup.org and run it from an outside directory; I personally run it from my root home directory, /root. Run checkout and answer the prompts and speakup should be patched into your kernel source. I should backup a moment and urge you to save your kernel comfiguration from prior good compiles and copy that file back into your /usr/src/linux source tree and be sure it is called .config. Then do a 'make oldconfig'. Any new options introduced with 2.4.19 and 2.4.20 will be presented and you should answer them to the best of your desires and abilities:). Save this file back for future use. Then compile as usual the kernel and you should have a talking kernel when done. the 'make modules_install will place the modules in /lib/2.4.20/kernel/..... Oh, don't forget to do lilo and assuming you have that set up the way you want. If you're not familiar with lilo, read the man page (more than once if necessary) to understand your options. HTH <Steve> On Mon, May 05, 2003 at 02:20:05PM -0400, Jack Mandez wrote: > okay here is my problem > my kernel does not support bzimage or it says that it can uncompress the > bzimage how do i fix this > when i try to use zimage it says the image is too big and to use zimage or > modules. > i think, most of the stuff i have in the kernel are loaded as modules anyway. > At 10:20 AM 5/5/03 -0700, you wrote: > >I see your problem now. Same mistake I made the first time. > >Do make modules_install note the underline character between the words > >modules and install. > > > >With alsa, do make install once the modules are built. This will place them > >where they belong. > > > >Justin > > > > > >"jack mendez" <wiler1 at earthlink.net> writes: > > > >> a few questions > >> so my system is back running 2.4.18 > >> someone mentioned reading the documentation for 2.4.20 > >> well, i read the README looked at the Changes file and i didn't find > >> anything about the new kernel or where the modules are stored. > >> so i am back to a fresh system > >> make mrproper > >> make oldconfig > >> make dep > >> make zImage > >> make modules > >> make modules install > >> i assume that is what i need to do > >> > >> as far as backing up my old vmlinuz file can i just rename it? > >> how is that done > >> > >> this all assumes that speakup and the modifications from wpi are patched > >> properly which they did the last time. > >> in adition i compiled alsa-driver-0.9.3 and it appeared to create modules > >> for individual cards in a sperate directory, do i just copy these into > >> /lib/modules/2.4.x/kernel/driver/what-goes-here? > >> > >> > >> thanks for all your help so far. > >> Jack > >> > >> > >> > >> > >> _______________________________________________ > >> Speakup mailing list > >> Speakup at braille.uwo.ca > >> http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > > > >_______________________________________________ > >Speakup mailing list > >Speakup at braille.uwo.ca > >http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > > > > _______________________________________________ > Speakup mailing list > Speakup at braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup -- Please avoid sending me Word or PowerPoint attachments. See http://www.fsf.org/philosophy/no-word-attachments.html
