LKML Archive on
help / color / mirror / Atom feed
From: "Piszcz, Justin Michael" <>
To: "Justin Piszcz" <>,
Subject: RE: Linux 2.6.5 emu10k1 module FAILS, built-in OK.
Date: Mon, 17 May 2004 11:23:37 -0400	[thread overview]
Message-ID: <> (raw)

Does creative still help maintain this module?
Is there an #include <string-something.h> missing in the module (WHEN
COMPILED W/SMP support, or?)
jpiszcz@slack91:/usr/src/linux/Documentation$ find .|grep -i emu101k
jpiszcz@slack91:/usr/src/linux/Documentation$ find .|grep -i emu101
jpiszcz@slack91:/usr/src/linux/Documentation$ grep emu101k -r *
grep: networking/netif-msg.txt: Permission denied
grep: scsi/ChangeLog.megaraid: Permission denied

(2.6.5 kernel)

-----Original Message-----
[] On Behalf Of Justin Piszcz
Sent: Saturday, May 15, 2004 6:08 PM
Subject: Re: Linux 2.6.5 emu10k1 module FAILS, built-in OK.

Let me remind all; this is with _SMP_ kernel only, with a regular kernel
it makes the module and loads it fine.

Anyone aware of this problem?

On Sat, 15 May 2004, Justin Piszcz wrote:

> Script started on Sat May 15 14:47:08 2004
> # modprobe emu10k1
> FATAL: Error inserting emu10k1
> (/lib/modules/2.6.5/kernel/sound/oss/emu10k1/emu10k1.ko): Unknown
> in module, or unknown parameter (see dmesg)
> root@war:~# dmesg | tail -n 1
>  emu10k1: Unknown symbol strcpy
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
the body of a message to
More majordomo info at
Please read the FAQ at

             reply	other threads:[~2004-05-17 15:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-17 15:23 Piszcz, Justin Michael [this message]
2004-05-17 17:16 ` Randy.Dunlap
  -- strict thread matches above, loose matches on Subject: below --
2004-05-18 13:18 Piszcz, Justin Michael
2004-05-15 19:32 Justin Piszcz
2004-05-15 22:07 ` Justin Piszcz
2004-05-16  2:57 ` Stan Bubrouski
2004-05-16  8:20   ` Justin Piszcz
2004-05-16 15:27     ` Stan Bubrouski

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:

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

  git send-email \ \ \ \ \
    --subject='RE: Linux 2.6.5 emu10k1 module FAILS, built-in OK.' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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 NNTP newsgroup(s).