emu10k1 problems

dtjohnst · 04-13-2004, 09:22 PM

Ok, I have no sound, I did some searching, found a lot of resources that said to download emu10k1. Before I did that, I tried doing a modprobe emu10k1, and sure enough, I have it, but I have errors.

Now, I don't know a lot about linux (like why users I create can't get Mozilla open, or why my X-Server won't shut down and I have to hard boot everytime I wanna reboot), so, I'm sure there's more information you'll need. Just let me know what it is, and I'll be sure to post a follow up.

What I have is an Audigy 2. And here's what my modprobe gave me:

Code:

modprobe emu10k1
/lib/modules/2.4.22/kernel/drivers/sound/emu10k1/emu10k1.o.gz: init_module: No such device
/lib/modules/2.4.22/kernel/drivers/sound/emu10k1/emu10k1.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.
      You may find more information in syslog or the output from dmesg
/lib/modules/2.4.22/kernel/drivers/sound/emu10k1/emu10k1.o.gz: insmod /lib/modules/2.4.22/kernel/drivers/sound/emu10k1/emu10k1.o.gz failed
/lib/modules/2.4.22/kernel/drivers/sound/emu10k1/emu10k1.o.gz: insmod emu10k1 failed

dmesg has on the very last line:

Code:

Creative EMU10K1 PCI Audio Driver, version 0.20, 18:39:42 Sep  2 2003

This is the only line that mentions anything about audio or creative. So, I don't know if maybe it's an issue of not detecting a device.

In Gnome 2.4, when I click on the volume, I get the error:

Code:

Couldn't open mixer device /dev/sound/mixer

Any ideas?

cybrjackle · 04-13-2004, 09:53 PM

1. Do you use swaret?

2. Does "modprobe snd-emu10k1" work?

I have an audigy2 but I use a newer kernel and I also don't think your alsa packages are new enough, I would suggest using swaret or your local slackware mirror for:

alsa-driver-1.0.4-i486-1
alsa-lib-1.0.4-i486-1
alsa-oss-1.0.4-i486-1
alsa-utils-1.0.4-i486-1

Slackware Package Browser

If your still useing the default kernel, I would recommending updateing that too.

Slackware 2.4.25 Kernel

But, don't ever use "upgradepkg" on kernels, use "installpkg", just in case there is a problem you don't loose your bootable kernel. Don't forget to edit lilo and create a new entry and the old one and just point them to vmlinuz-ide-2.4.25 & .22

320mb · 04-13-2004, 09:58 PM

Code:

Couldn't open mixer device /dev/sound/mixer

that's odd, in my Slackware install the mixer location is in

/dev/mixer
have no idea why you show a seperate sound directory..........

cybrjackle · 04-13-2004, 10:02 PM

Just an FYI, I just booted into my "slackware" 2.4.25 and I have the latest "current" alsa packages on this box and

/sbin/modprobe snd-emu10k1

works just fine.

Also make sure your user is part of the "sys" group

Code:

# more /etc/group | grep sys
sys::3:root,bin,adm,justin

Guess my real name.

If the sound is muted,

Code:

chmod 660 /dev/dsp
alsamixer
alsactl store

cybrjackle · 04-13-2004, 10:04 PM

Quote:

Now, I don't know a lot about linux (like why users I create can't get Mozilla open, or why my X-Server won't shut down and I have to hard boot everytime I wanna reboot), so, I'm sure there's more information you'll need. Just let me know what it is, and I'll be sure to post a follow up.

For this stuff, create 2 differnet post so there easy to read by "subject"

You don't want to leave your system like that and need to fix it.

dtjohnst · 04-14-2004, 12:03 AM

Quote:

Originally posted by cybrjackle
For this stuff, create 2 differnet post so there easy to read by "subject"

You don't want to leave your system like that and need to fix it.

I agree. I have some hints on those already that I'm gonna test out before I come asking for more help though.

dtjohnst · 04-14-2004, 12:37 AM

Quote:

2. Does "modprobe snd-emu10k1" work?

Nope. Get the error:

Code:

modprobe: Can't locate module snd-emu10k1

Upgraded the drivers, utils, oss, and lib to the latest version, exact same errors.

Haven't upgraded my kernel yet. Might try that next.....any other ideas?

dtjohnst · 04-14-2004, 12:45 AM

Incidently...I had no /dev/snd/mixer, but I did have a /dev/mixer, which was just a link, so I made a copy of that and threw it in /dev/snd/mixer

dtjohnst · 04-14-2004, 12:51 AM

Quote:

Originally posted by cybrjackle

If your still useing the default kernel, I would recommending updateing that too.

Slackware 2.4.25 Kernel

But, don't ever use "upgradepkg" on kernels, use "installpkg", just in case there is a problem you don't loose your bootable kernel. Don't forget to edit lilo and create a new entry and the old one and just point them to vmlinuz-ide-2.4.25 & .22

I've uhhh....never updated my kernel. Kinda unsure how to go about that. Right now my lilo.conf file has:

Code:

# Start LILO global section
boot = /dev/hdb2
message = /boot/boot_message.txt
prompt
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
  reset
# VESA framebuffer console @ 1024x768x64k
vga = 791
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/hdb2
  label = Linux
  read-only
# Linux bootable partition config ends

You mention creating new sections and pointing them to vmlinuz-ide-2.4.25 & .22, where I'm confused is that it isn't pointing to vmlinuz-ide-2.4.22 already. Shouldn't it be?

cybrjackle · 04-14-2004, 08:01 AM

Grab those four kernel tgz's, and run installpkg kernel*.tgz on them.

kernel-ide-2.4.25-i486-2
kernel-modules-2.4.25-i486-2
kernel-headers-2.4.25-i386-2
kernel-source-2.4.25-noarch-2

Then make your lilo look like this

Code:

image = /boot/vmlinuz-ide-2.4.25
  root = /dev/hdb2
  label = 2.4.25
  read-only
image = /boot/vmlinuz-ide-2.4.22
  root = /dev/hdb2
  label = 2.4.22
  read-only
# Linux bootable partition config ends

Then run lilo and you should see the following:

Code:

# /sbin/lilo
Added 2.4.25 *
Added 2.4.22

You could also add this line to /etc/rc.d/rc.modules

Code:

vi /etc/rc.d/rc.modules

/sbin/modprobe snd-emu10k1

cybrjackle · 04-14-2004, 08:03 AM

Oh, the reason it doesn't show "vmlinuz-ide-2.4.22" is because in your /boot vmlinuz is linked to vmlinuz-ide-2.4.22. If you run "ls-la /boot" you will see what i mean.

Code:

ls -la /boot
total 10500
drwxr-xr-x   2 root root    4096 Apr 14 06:59 ./
drwxr-xr-x  16 root root     151 Apr 14 06:49 ../
lrwxrwxrwx   1 root root      21 Apr 13 08:02 System.map -> System.map-ide-2.4.25
-rw-r--r--   1 root root  975793 Apr 13 10:18 System.map-2.6.5
-rw-r--r--   1 root root  609166 Sep  2  2003 System.map-ide-2.4.22
-rw-r--r--   1 root root  620412 Feb 28 17:48 System.map-ide-2.4.25
-rw-------   1 root root  644781 Apr 13 07:44 System.map-xfs.s-2.4.25
-rw-r--r--   1 root root     512 Apr 13 02:13 boot.0300
-rw-r--r--   1 root root     179 Apr 13 02:13 boot_message.txt
-rw-r--r--   1 root root 1415946 Apr 13 07:43 bzImage-xfs
lrwxrwxrwx   1 root root      17 Apr 13 08:02 config -> config-ide-2.4.25
-rw-r--r--   1 root root   27514 Apr 13 10:18 config-2.6.5
-rw-r--r--   1 root root   38645 Sep  2  2003 config-ide-2.4.22
-rw-r--r--   1 root root   40856 Feb 28 17:48 config-ide-2.4.25
-rw-r--r--   1 root root   40700 Apr 13 07:43 config-xfs.s-2.4.25
-rw-------   1 root root   66560 Apr 14 06:59 map
lrwxrwxrwx   1 root root      18 Apr 13 08:02 vmlinuz -> vmlinuz-ide-2.4.25
-rw-r--r--   1 root root 2339997 Apr 13 10:18 vmlinuz-2.6.5
-rw-r--r--   1 root root 1226706 Sep  2  2003 vmlinuz-ide-2.4.22
-rw-r--r--   1 root root 1251881 Feb 28 17:48 vmlinuz-ide-2.4.25
-rw-r--r--   1 root root 1415946 Apr 13 07:43 vmlinuz-xfs.s-2.4.25

Kjetil4455 · 04-14-2004, 01:04 PM

Does that driver even support Audigy 2?

cybrjackle · 04-14-2004, 01:19 PM

If your talking about this:

/sbin/modprobe snd-emu10k1

with 2.4.25 & 1.0.4 alsa* stuff, then "YES"

SyphonPayne · 04-14-2004, 03:57 PM

I am using Mandrake Linux 9.1 Bamboo and I have managed to get snd-emu10k1 to work using HardDrake, but when I reboot or anything like that I lose those settings... how do I set it to rund snd-emu10k1 with the Audigy() driver automatically?

EDIT: oh crap, wrong forum... sorry

dtjohnst · 04-14-2004, 05:09 PM

Quote:

Originally posted by cybrjackle
Grab those four kernel tgz's, and run installpkg kernel*.tgz on them.

kernel-ide-2.4.25-i486-2
kernel-modules-2.4.25-i486-2
kernel-headers-2.4.25-i386-2
kernel-source-2.4.25-noarch-2

Then make your lilo look like this

Code:

image = /boot/vmlinuz-ide-2.4.25 root = /dev/hdb2 label = 2.4.25 read-only image = /boot/vmlinuz-ide-2.4.22 root = /dev/hdb2 label = 2.4.22 read-only # Linux bootable partition config ends

Then run lilo and you should see the following:

Code:

# /sbin/lilo Added 2.4.25 * Added 2.4.22

You could also add this line to /etc/rc.d/rc.modules

Code:

vi /etc/rc.d/rc.modules /sbin/modprobe snd-emu10k1

Doing that right now. Once that's done, assuming it works fine, should I remove the old kernel? And if so, how do I do that?