From: "Kerry Hoath" <kerry@gotss.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: emu10k1 compilation problms.
Date: Tue, 5 Jun 2007 12:24:00 +0800 [thread overview]
Message-ID: <000301c7a729$5f868e60$2518a8c0@bouncy> (raw)
In-Reply-To: <000c01c7a728$ed521b20$6401a8c0@GRANDMA>
kernel uses alsa drivers these days,
modprobe snd_emu10k1
also cat /proc/asound/cards if it exists and use modprobe to load
dependancies.
----- Original Message -----
From: "Littlefield, Tyler" <compgeek13@gmail.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Tuesday, June 05, 2007 12:21 PM
Subject: Re: emu10k1 compilation problms.
>I don't see it in my modules dir, and I got the kernel image from apt,
> hoping once I got time, to patch speakup in, and go.
> Anyway, I can't modprobe emu10k1, it tells me that the file can't be
> found.
>
> Thanks,
> ~~TheCreator~~
> [My programs don't have bugs; just randomly added features]
> msn:
> compgeek13@gmail.com
> aim: st8amnd2005
> skype: st8amnd127
> vertigo head coder
> web: tysdomain.com
> ----- Original Message -----
> From: "Zachary Kline" <Z_kline@hotmail.com>
> To: "Speakup is a screen review system for Linux."
> <speakup@braille.uwo.ca>
> Sent: Monday, June 04, 2007 10:09 PM
> Subject: Re: emu10k1 compilation problms.
>
>
>> Hello,
>> The kernel sources themselves contain the Emu10K driver, do they not?
>> At least that's been my experience whenever I've needed a sound card
>> configured.
>> Thanks,
>> Zack.
>>
>> ----- Original Message -----
>> From: "Littlefield, Tyler" <compgeek13@gmail.com>
>> To: "Speakup is a screen review system for Linux."
> <speakup@braille.uwo.ca>
>> Sent: Monday, June 04, 2007 9:04 PM
>> Subject: emu10k1 compilation problms.
>>
>>
>> > Hello list,
>> > Well, I wanted to accomplish something and be able to say I didn't need
>> > help.
>> > Unfortunately, that plan was shattered.
>> > I found the emu10k1 driver on sourceforge, coppied in my .config and
>> > set
>> > the kernel source path.
>> > When I type make, here's the problem I get.
>> > Anyone able to suggest a fix?
>> > make[1]: Entering directory `/usr/src/emu10k1-v0.20a/scripts'
>> > cc -I/usr/src/linux/include get_version.c -o get_version
>> > get_version.c: In function 'main':
>> > get_version.c:5: error: 'UTS_RELEASE' undeclared (first use in this
>> > function)
>> > get_version.c:5: error: (Each undeclared identifier is reported only
> once
>> > get_version.c:5: error: for each function it appears in.)
>> > make[1]: *** [get_version] Error 1
>> > make[1]: Leaving directory `/usr/src/emu10k1-v0.20a/scripts'
>> > make: *** [opts] Error 2
>> > Any help is appriciated,
>> > Thanks,
>> > ~~TheCreator~~
>> > [My programs don't have bugs; just randomly added features]
>> > msn:
>> > compgeek13@gmail.com
>> > aim: st8amnd2005
>> > skype: st8amnd127
>> > vertigo head coder
>> > web: tysdomain.com
>> > _______________________________________________
>> > 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
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
Littlefield, Tyler
` Zachary Kline
` Littlefield, Tyler
` Kerry Hoath [this message]
` Buddy Brannan
` Littlefield, Tyler
` Kerry Hoath
` Littlefield, Tyler
` Doug Smith
` Littlefield, Tyler
` Doug Smith
` Littlefield, Tyler
` Kerry Hoath
` Alex Snow
` Littlefield, Tyler
` Buddy Brannan
` Littlefield, Tyler
` Kerry Hoath
` Littlefield, Tyler
` Alex Snow
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='000301c7a729$5f868e60$2518a8c0@bouncy' \
--to=kerry@gotss.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).