* kernel stuff @ jack mendez ` Justin Ekis ` Adam Myrow 0 siblings, 2 replies; 8+ messages in thread From: jack mendez @ UTC (permalink / raw) To: speakup 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 ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: kernel stuff kernel stuff jack mendez @ ` Justin Ekis ` jack mendez ` Adam Myrow 1 sibling, 1 reply; 8+ messages in thread From: Justin Ekis @ UTC (permalink / raw) To: speakup 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@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@braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: kernel stuff ` Justin Ekis @ ` jack mendez ` Steve Holmes 0 siblings, 1 reply; 8+ messages in thread From: jack mendez @ UTC (permalink / raw) To: speakup 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@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@braille.uwo.ca >> http://speech.braille.uwo.ca/mailman/listinfo/speakup > > >_______________________________________________ >Speakup mailing list >Speakup@braille.uwo.ca >http://speech.braille.uwo.ca/mailman/listinfo/speakup > ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: kernel stuff ` jack mendez @ ` Steve Holmes ` jack mendez ` jack mendez 0 siblings, 2 replies; 8+ messages in thread From: Steve Holmes @ UTC (permalink / raw) To: speakup 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@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@braille.uwo.ca > >> http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > > > >_______________________________________________ > >Speakup mailing list > >Speakup@braille.uwo.ca > >http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > > > > _______________________________________________ > Speakup mailing list > Speakup@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 ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: kernel stuff ` Steve Holmes @ ` jack mendez ` Buddy Brannan ` jack mendez 1 sibling, 1 reply; 8+ messages in thread From: jack mendez @ UTC (permalink / raw) To: speakup thanks a ton for the info when i do make bzImage it says unsupported compression type or something and failes to boot At 12:13 PM 5/5/03 -0700, you wrote: >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@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@braille.uwo.ca >> >> http://speech.braille.uwo.ca/mailman/listinfo/speakup >> > >> > >> >_______________________________________________ >> >Speakup mailing list >> >Speakup@braille.uwo.ca >> >http://speech.braille.uwo.ca/mailman/listinfo/speakup >> > >> >> >> >> _______________________________________________ >> Speakup mailing list >> Speakup@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 > >_______________________________________________ >Speakup mailing list >Speakup@braille.uwo.ca >http://speech.braille.uwo.ca/mailman/listinfo/speakup > ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: kernel stuff ` jack mendez @ ` Buddy Brannan 0 siblings, 0 replies; 8+ messages in thread From: Buddy Brannan @ UTC (permalink / raw) To: speakup Just a guess, but do you have bzip2 and bunzip2 installed? (I believe, though can't swear to it) that you need these tools. bzip2 and the corresponding bunzip2 are compression tools very like gzip but with tighter compression. -- Buddy Brannan, KB5ELV/3 | "And if the ground yawned, Phone: (814) 455-7333 | I'd step to the side and say, Email: davros@ycardz.com | "Hey ground! I'm nobody's lunch!" http://www.ycardz.com/ | --Eddie From Ohio ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: kernel stuff ` Steve Holmes ` jack mendez @ ` jack mendez 1 sibling, 0 replies; 8+ messages in thread From: jack mendez @ UTC (permalink / raw) To: speakup i reconfigured the .config file i got the bzimage to be smaller and now i am having two problems first, when i atempt to do make modules i get all sorts of unresolved symbols, i think they only exist in the alsa modules so i am not sure weather i should do a make modules_install. the next i think had to do with the fact that i never did do make modules or make modules_install. i got the error mesage ebda to big. when atempting to boot from the bzImage but how do i solve the problem with the alsa modules? thanks Jack ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: kernel stuff kernel stuff jack mendez ` Justin Ekis @ ` Adam Myrow 1 sibling, 0 replies; 8+ messages in thread From: Adam Myrow @ UTC (permalink / raw) To: speakup On Mon, 5 May 2003, jack mendez wrote: > make mrproper > make oldconfig > make dep > make zImage > make modules > make modules install I see three problems here. The "make mrproper" wipes out any configuration files, so you wouldn't want to do "make oldconfig" after that. "Make oldconfig" is for using an existing configuration and answering only new questions. If you really want to use it, either don';t do the "make mrproper," or copy the .config file somewhere else and back again after the "make mrproper." The second problem is that you should use "make bzImage" to build the kernel. That is case-sensitive which means you have to capitalize the I. Lastly, the command is "make modules_install." Good luck. Once you've got a custom kernel that you are satisfied with, copy the ".config" file from the kernel source tree to a safe place so you can re-use it if needed. ^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~ UTC | newest]
Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
kernel stuff jack mendez
` Justin Ekis
` jack mendez
` Steve Holmes
` jack mendez
` Buddy Brannan
` jack mendez
` Adam Myrow
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).