public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Justin Ekis" <j_ekis@adelphia.net>
To: <speakup@braille.uwo.ca>
Subject: Re: kernel stuff
Date: Mon, 5 May 2003 10:20:20 -0700	[thread overview]
Message-ID: <00da01c3132a$9d91ad30$0300a8c0@xpcomputer> (raw)
In-Reply-To: <3.0.6.32.20030505122226.00838dc0@mail.earthlink.net>

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



  reply	other threads:[~ UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 jack mendez
 ` Justin Ekis [this message]
   ` jack mendez
     ` Steve Holmes
       ` jack mendez
         ` Buddy Brannan
       ` jack mendez
 ` Adam Myrow

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='00da01c3132a$9d91ad30$0300a8c0@xpcomputer' \
    --to=j_ekis@adelphia.net \
    --cc=speakup@braille.uwo.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
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).