From: "Adam Myrow" <amyrow@midsouth.rr.com>
To: "'Speakup is a screen review system for Linux.'"
<speakup@braille.uwo.ca>
Subject: RE: kernel build issue
Date: Sat, 1 Apr 2006 09:30:33 -0600 [thread overview]
Message-ID: <000901c655a1$3808e340$6401a8c0@dell> (raw)
In-Reply-To: <20060401085321.10286.83682@rif.myfreedombox.com>
2.6 uses ".ko" as the module extension. You have to rebuild ALSA every time
you compile a new version of the kernel. Alsa is in the 2.6.X kernels, so I
tend to prefer that version to building it from source every time.
-----Original Message-----
From: speakup-bounces@braille.uwo.ca [mailto:speakup-bounces@braille.uwo.ca]
On Behalf Of tony seth
Sent: Saturday, April 01, 2006 2:53 AM
To: speakup@braille.uwo.ca
Subject: Re: kernel build issue
While we're on the jubject, I have a kernel question too. I'm currently
running slackware 10.1 and a 2.4 kernel. I rolled my own 2.6 kernel, and
although it mostly went as it should, all my modules seem to have a .ko
extention rather then the .o extention, and so, for example when my sound
card loads I get an error that the version is incorrect. How do I fix this,
I'm sure I'm doing something wrong, or forgetting something obvious, but
can't think what it is...
I tried it before and got everything to work before, but don't know I did
differently. Any help appreciated... thanks much.
Cheereo!
--
Email services by FreedomBox. Surf the Net at the sound of your voice.
www.freedombox.info
_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
tony seth
` Adam Myrow [this message]
` Gregory Nowak
` Kirk Reiser
` Igor Gueths
-- strict thread matches above, loose matches on Subject: below --
Juan Hernandez
` Kirk Reiser
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='000901c655a1$3808e340$6401a8c0@dell' \
--to=amyrow@midsouth.rr.com \
--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).