I just upgraded my kernel to 2.6.1, and learned there's now an ALSA driver for my sound card (Aureal Vortex, driver snd-au8820). I installed ALSA, (I use debian unstable), and I can insert 3 out of 4 of the modules. snd-au8820, snd-pcm-oss, and snd-mixer-oss work fine. But when I try to modprobe snd-seq-oss, it says:
FATAL: Error inserting snd_seq_oss (/lib/modules/2.6.1-blarg-24Jan2004/kernel/sound/acore/seq/oss/snd-seq-oss.ko): Device or resource busy
I have OSS enabled in my kernel (I found out about the ALSA driver after I recompiled). Could this have anything to do with it?
The web page for installing the ALSA driver is:
http://www.alsa-project.org/alsa-doc/doc-php/template.php?company=Aureal&card=Generic&chip=AU8820&module=au8820
AdamZ
01-30-2004, 09:57 PM
well, I got the module to install, but when I try to run alsamixer, it gives me this error:
alsamixer: function snd_ctl_open failed for default: No such device
Did you compile Alsa yourself? It looks like whoever compiled it didn't include support for your sound card when they specified --with-cards=<list>. See the output of ./configure --help from the alsa-driver source, but you'll probably want to specify --with-oss=yes --with-sequencer=yes --with-cards=au8820 (at least; maybe more arguments to --with-cards depending on your hardware, and maybe add --with-isapnp=no).
You will need your kernel sources installed.
Or maybe you don't really have an au8820 card? (hey, you never know...) Try lspci or (better yet) pcimodules to double check.
AdamZ
01-31-2004, 01:33 AM
Originally posted by bwkaz
Did you compile Alsa yourself? It looks like whoever compiled it didn't include support for your sound card when they specified --with-cards=<list>. See the output of ./configure --help from the alsa-driver source, but you'll probably want to specify --with-oss=yes --with-sequencer=yes --with-cards=au8820 (at least; maybe more arguments to --with-cards depending on your hardware, and maybe add --with-isapnp=no).
You will need your kernel sources installed.
Or maybe you don't really have an au8820 card? (hey, you never know...) Try lspci or (better yet) pcimodules to double check.
I definitely have an au8820. I downloaded packages for alsa, and compiled the driver from the source. I used the options --with-cards=au8820 --with-sequencer=yes. I'll try using the other options you suggested.
EDIT: I tried that, and it didn't work. I still get the same error.
here's the output of lsmod by the way:
After you load the modules, is there anything near the tail end of the output of dmesg that looks ilke an error?
</last-ditch effort...>
AdamZ
01-31-2004, 02:36 PM
Originally posted by bwkaz
After you load the modules, is there anything near the tail end of the output of dmesg that looks ilke an error?
</last-ditch effort...>
here's the output of dmesg. Lots of errors related to modules.
Linux version 2.6.1-blarg.30Jan2004 (root@blarg.dyndns.org) (gcc version 3.3.3 20040110 (prerelease) (Debian)) #2 Fri Jan 30 17:30:27 PST 2004
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 0000000007ffc000 (usable)
BIOS-e820: 0000000007ffc000 - 0000000007fff000 (ACPI data)
BIOS-e820: 0000000007fff000 - 0000000008000000 (ACPI NVS)
BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
127MB LOWMEM available.
On node 0 totalpages: 32764
DMA zone: 4096 pages, LIFO batch:1
Normal zone: 28668 pages, LIFO batch:6
HighMem zone: 0 pages, LIFO batch:1
DMI 2.3 present.
Building zonelist for node : 0
Kernel command line: BOOT_IMAGE=linux-new ro root=302
Local APIC disabled by BIOS -- reenabling.
Found and enabled local APIC!
Initializing CPU#0
PID hash table entries: 512 (order 9: 4096 bytes)
Detected 451.020 MHz processor.
Using tsc for high-res timesource
Console: colour VGA+ 80x25
Memory: 125592k/131056k available (2297k kernel code, 4928k reserved, 829k data, 168k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay loop... 890.88 BogoMIPS
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU: After generic identify, caps: 0383fbff 00000000 00000000 00000000
CPU: After vendor identify, caps: 0383fbff 00000000 00000000 00000000
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 512K
CPU: After all inits, caps: 0383fbff 00000000 00000000 00000040
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU: Intel Pentium III (Katmai) stepping 03
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
enabled ExtINT on CPU#0
ESR value before enabling vector: 00000000
ESR value after enabling vector: 00000000
Using local APIC timer interrupts.
calibrating APIC timer ...
..... CPU clock speed is 450.0949 MHz.
..... host bus clock speed is 100.0210 MHz.
NET: Registered protocol family 16
PCI: PCI BIOS revision 2.10 entry at 0xf08b0, last bus=1
PCI: Using configuration type 1
mtrr: v2.0 (20020519)
Linux Plug and Play Support v0.97 (c) Adam Belay
PnPBIOS: Scanning system for PnP BIOS support...
PnPBIOS: Found PnP BIOS installation structure at 0xc00fc310
PnPBIOS: PnP BIOS version 1.0, entry 0xf0000:0xc340, dseg 0xf0000
pnp: 00:0f: ioport range 0x290-0x297 has been reserved
pnp: 00:0f: ioport range 0xe400-0xe43f has been reserved
pnp: 00:0f: ioport range 0xe800-0xe83f has been reserved
PnPBIOS: 14 nodes reported by PnP BIOS; 14 recorded by driver
drivers/usb/core/usb.c: registered new driver usbfs
drivers/usb/core/usb.c: registered new driver hub
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
PCI: Address space collision on region 7 of bridge 0000:00:04.3 [e400:e43f]
PCI: Address space collision on region 8 of bridge 0000:00:04.3 [e800:e81f]
PCI: Using IRQ router PIIX/ICH [8086/7110] at 0000:00:04.0
aty128fb: Rage128 BIOS located at dffe0000
aty128fb: Rage128 RF (AGP) [chip rev 0x2] 16M 128-bit SDR SGRAM (1:1)
fb0: ATY Rage128 frame buffer device on Rage128 RF (AGP)
aty128fb: Rage128 MTRR set to ON
SBF: Simple Boot Flag extension found and enabled.
SBF: Setting boot flags 0x1
apm: BIOS version 1.2 Flags 0x0b (Driver version 1.16ac)
udf: registering filesystem
Initializing Cryptographic API
Limiting direct PCI/PCI transfers.
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Console: switching to colour frame buffer device 80x30
pty: 256 Unix98 ptys configured
request_module: failed /sbin/modprobe -- parport_lowlevel. error = -16
lp: driver loaded but no devices found
ppdev: user-space parallel port driver
Linux agpgart interface v0.100 (c) Dave Jones
[drm] Initialized r128 2.5.0 20030725 on minor 0
parport0: PC-style at 0x378 [PCSPP,TRISTATE]
parport0: cpp_daisy: aa5500ff(98)
parport0: assign_addrs: aa5500ff(98)
parport0: Printer, HEWLETT-PACKARD DESKJET 810C
lp0: using parport0 (polling).
Using anticipatory io scheduler
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
loop: loaded (max 8 devices)
ne2k-pci.c:v1.03 9/22/2003 D. Becker/P. Gortmaker
http://www.scyld.com/network/ne2k-pci.html
PCI: Found IRQ 5 for device 0000:00:09.0
PCI: Sharing IRQ 5 with 0000:00:04.2
eth0: RealTek RTL-8029 found at 0xb000, IRQ 5, 00:50:BA:C4:5F:7F.
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
hda: Maxtor 91360U4, ATA DISK drive
hdc: DVD-ROM DDU220E, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: max request size: 128KiB
hda: 26588016 sectors (13613 MB) w/2048KiB Cache, CHS=26377/16/63
hda: hda1 hda2 hda3
hdc: ATAPI DVD-ROM drive, 512kB Cache
Uniform CD-ROM driver Revision: 3.12
Console: switching to colour frame buffer device 80x30
drivers/usb/host/uhci-hcd.c: USB Universal Host Controller Interface driver v2.1
PCI: Found IRQ 5 for device 0000:00:04.2
PCI: Sharing IRQ 5 with 0000:00:09.0
uhci_hcd 0000:00:04.2: UHCI Host Controller
uhci_hcd 0000:00:04.2: irq 5, io base 0000b400
uhci_hcd 0000:00:04.2: new USB bus registered, assigned bus number 1
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
mice: PS/2 mouse device common for all mice
input: PC Speaker
PCI: Found IRQ 10 for device 0000:00:0b.0
input: Analog 4-axis 4-button joystick at pci0000:00:0b.0/gameport0 [ADC port]
gameport at pci0000:00:0b.0 speed 1657 kHz
serio: i8042 AUX port at 0x60,0x64 irq 12
input: PS/2 Generic Mouse on isa0060/serio1
serio: i8042 KBD port at 0x60,0x64 irq 1
input: AT Translated Set 2 keyboard on isa0060/serio0
NET: Registered protocol family 2
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 8192 bind 16384)
ip_conntrack version 2.1 (1023 buckets, 8184 max) - 160 bytes per conntrack
ip_tables: (C) 2000-2002 Netfilter core team
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
NET: Registered protocol family 15
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 168k freed
hub 1-0:1.0: new USB device on port 2, assigned address 2
version 0 swap is no longer supported. Use mkswap -v1 /dev/hda3
snd: no version for "struct_module" found: kernel tainted.
request_module: failed /sbin/modprobe -- snd-card-1. error = 256
version 0 swap is no longer supported. Use mkswap -v1 /dev/hda3
request_module: failed /sbin/modprobe -- char-major-4-64. error = 256
request_module: failed /sbin/modprobe -- snd-card-1. error = 256
request_module: failed /sbin/modprobe -- char-major-4-64. error = 256
request_module: failed /sbin/modprobe -- net-pf-10. error = 256
atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
request_module: failed /sbin/modprobe -- net-pf-10. error = 256
request_module: failed /sbin/modprobe -- net-pf-10. error = 256
request_module: failed /sbin/modprobe -- net-pf-10. error = 256
request_module: failed /sbin/modprobe -- net-pf-10. error = 256
request_module: failed /sbin/modprobe -- sound-slot-0. error = 256
request_module: failed /sbin/modprobe -- sound-slot-0. error = 256
request_module: failed /sbin/modprobe -- sound-slot-0. error = 256
atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
request_module: failed /sbin/modprobe -- net-pf-10. error = 256
atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
request_module: failed /sbin/modprobe -- net-pf-10. error = 256
atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
request_module: failed /sbin/modprobe -- net-pf-10. error = 256
request_module: failed /sbin/modprobe -- net-pf-10. error = 256
request_module: failed /sbin/modprobe -- net-pf-10. error = 256
request_module: failed /sbin/modprobe -- net-pf-10. error = 256
request_module: failed /sbin/modprobe -- net-pf-10. error = 256
request_module: failed /sbin/modprobe -- net-pf-10. error = 256
request_module: failed /sbin/modprobe -- net-pf-10. error = 256
request_module: failed /sbin/modprobe -- net-pf-10. error = 256
request_module: failed /sbin/modprobe -- net-pf-10. error = 256
request_module: failed /sbin/modprobe -- net-pf-10. error = 256
request_module: failed /sbin/modprobe -- net-pf-10. error = 256
request_module: failed /sbin/modprobe -- net-pf-10. error = 256
request_module: failed /sbin/modprobe -- net-pf-10. error = 256
request_module: failed /sbin/modprobe -- net-pf-10. error = 256
request_module: failed /sbin/modprobe -- net-pf-10. error = 256
request_module: failed /sbin/modprobe -- net-pf-10. error = 256
request_module: failed /sbin/modprobe -- net-pf-10. error = 256
request_module: failed /sbin/modprobe -- net-pf-10. error = 256
request_module: failed /sbin/modprobe -- net-pf-10. error = 256
request_module: failed /sbin/modprobe -- net-pf-10. error = 256
request_module: failed /sbin/modprobe -- net-pf-10. error = 256
request_module: failed /sbin/modprobe -- net-pf-10. error = 256
request_module: failed /sbin/modprobe -- net-pf-10. error = 256
request_module: failed /sbin/modprobe -- net-pf-10. error = 256
request_module: failed /sbin/modprobe -- net-pf-10. error = 256
request_module: failed /sbin/modprobe -- net-pf-10. error = 256
request_module: failed /sbin/modprobe -- net-pf-10. error = 256
request_module: failed /sbin/modprobe -- net-pf-10. error = 256
request_module: failed /sbin/modprobe -- net-pf-10. error = 256
request_module: failed /sbin/modprobe -- net-pf-10. error = 256
request_module: failed /sbin/modprobe -- net-pf-10. error = 256
request_module: failed /sbin/modprobe -- net-pf-10. error = 256
request_module: failed /sbin/modprobe -- net-pf-10. error = 256
request_module: failed /sbin/modprobe -- net-pf-10. error = 256
request_module: failed /sbin/modprobe -- net-pf-10. error = 256
request_module: failed /sbin/modprobe -- net-pf-10. error = 256
request_module: failed /sbin/modprobe -- char-major-4-64. error = 256
request_module: failed /sbin/modprobe -- net-pf-10. error = 256
request_module: failed /sbin/modprobe -- net-pf-10. error = 256
request_module: failed /sbin/modprobe -- net-pf-10. error = 256
request_module: failed /sbin/modprobe -- net-pf-10. error = 256
request_module: failed /sbin/modprobe -- net-pf-10. error = 256
request_module: failed /sbin/modprobe -- net-pf-10. error = 256
request_module: failed /sbin/modprobe -- net-pf-10. error = 256
request_module: failed /sbin/modprobe -- net-pf-10. error = 256
request_module: failed /sbin/modprobe -- net-pf-10. error = 256
request_module: failed /sbin/modprobe -- net-pf-10. error = 256
request_module: failed /sbin/modprobe -- net-pf-10. error = 256
kevinalm
02-01-2004, 10:05 PM
Afaik, the alsa driver for au88x0 doesn't work with kernel 2.6.x yet. The primary developer is working on a3d and wt support for the vortex and is staying with 2.4 kernels for now. There may be some patches floating around for 2.6, but use at your own risk. Here's a link to the main developement site.
http://savannah.nongnu.org/projects/openvortex
I recommend subscribing to the devopement mailing list to keep abreast of the current state of the driver.
Also, here's Manuel Jander's website:
http://galadriel.mat.utfsm.cl/~mjander/aureal/
He's primarily responsible for the fantastic job of reverse engineering this driver. There are some downloads and lots of interesting info here.
bwkaz
02-01-2004, 11:05 PM
That would explain it. :)
As for those errors, yeah, a lot of them are module-related, but most of them aren't sound module related (except the one about no version in struct_module in the "snd" module, that taints your kernel).
The vast majority of them are for IPv6 (net-pf-10 is networking, protocol family 10, which is IPv6). You probably don't have an ipv6 module, and also don't have it compiled into your kernel. No big deal though; the Internet is currently almost exclusively IPv4 so you're OK.
You can add a line reading install net-pf-10 /bin/true to your /etc/modprobe.conf to turn off those errors (run depmod -ae afterward).
AdamZ
02-02-2004, 12:15 AM
thanks both for your responses.
I think I'll just wait until the vortex code makes it into the kernel. I don't really need sound at the moment. The net-pf-10 error didn't go away, but that's fine by me (I don't read my logs all that much). Just curious, if I enable ipv6 in my kernel next time I recompile, does it actually do something, or does my ISP have to support ipv6?
bwkaz
02-02-2004, 07:57 PM
You have to be on an IPv6 network, yeah. Normal TCP/IP uses IPv4 for the moment, though there is a way to transport IPv6 packets in an IPv4 tunnel (and the other way around).
kevinalm
02-03-2004, 05:48 PM
On the openvortex-dev mailing list today mjander released a patch for alsa-driver-1.0.1 with is supposed to work with kernel 2.6 .
Also, I thought i'd mention that according to the kernel docs ipv6 is fully backward compatable. In other words, ipv6 autosenses whether 6 or 4 is available and sets up accordingly. So having it compiled into your kernel is no problem even if your isp is only ipv4.
AdamZ
03-11-2004, 02:08 AM
OK, now I have a new problem. I recompiled, kernel 2.4.25, and now when I try to insert the modules it says:
$sudo modprobe snd-au8820
/lib/modules/2.4.25/kernel/sound/pci/au88x0/snd-au8820.o: init_module: No such device
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.25/kernel/sound/pci/au88x0/snd-au8820.o: insmod /lib/modules/2.4.25/kernel/sound/pci/au88x0/snd-au8820.o failed
/lib/modules/2.4.25/kernel/sound/pci/au88x0/snd-au8820.o: insmod snd-au8820 failed
here's the relevant part of lspci output:
00:0b.0 Multimedia audio controller: Aureal Semiconductor Vortex 1 (rev 02)
Subsystem: Aureal Semiconductor AU8820 Vortex Digital Audio Processor
Flags: bus master, medium devsel, latency 32, IRQ 10
Memory at de000000 (32-bit, non-prefetchable) [size=128K]
I/O ports at a400 [size=8]
I/O ports at a000 [size=8]
Capabilities: [dc] Power Management version 1
I enabled sound support, but not anything else. Do I have to enable ALSA support, even though the card's driver isn't included in the kernel(I think)?
kevinalm
03-11-2004, 02:34 AM
No. The only kernel option for sound should be sound support as a module, nothing else. (This creates the soundcore module) Then download and compile alsa-libs, alsa-utils, and alsa-driver. At least version 1.0.2, and alsa-driver-1.0.2c . The current stable should be fine. Expand the tarballs, cd in and for:
alsa-libs:
./configure
make
make install
At this point do:
ldconfig
alsa-utils:
./configure
make
make install
alsa driver:
./configure --with-oss=yes --with-sequencer=yes --with-cards=au8820
make
make install
Then run:
alsaconf
It would be a good idea to have rebooted into your new kernel before doing this. Alsaconf can be a little cranky. Sometimes you have to try several times. ldconfig and the make installs require su to root.
bwkaz
03-11-2004, 09:31 PM
You're going to need to install alsa-driver BEFORE alsa-lib, and alsa-lib before alsa-utils.
kevinalm
03-11-2004, 10:14 PM
Originally posted by bwkaz
You're going to need to install alsa-driver BEFORE alsa-lib, and alsa-lib before alsa-utils.
You sure about that? I thought that alsa-driver was just the kernel module code. At least I've never noticed that dependancy. Oh well, something else I've learned today.
The main thing is to use alsa-driver >= 1.0.2c instead of the vortex chip modules in the 2.6 kernel source. The driver is rapidly evolving and due to lead time conciderations, the code for the au88x0 chips imported into the 2.6 kernel source is _way_ behind.
bwkaz
03-11-2004, 11:04 PM
Yes, alsa-driver is the kernel module code. But it also puts some headers in /usr/include/sound that alsa-lib needs, IIRC.
And even though I don't have one of those AU* cards, I do agree that 1.0.2c (or whatever the newest release is) would be a good one for just about any relatively new card, or any card whose drivers are being worked on fervently.
kevinalm
03-12-2004, 12:34 AM
Originally posted by bwkaz
Yes, alsa-driver is the kernel module code. But it also puts some headers in /usr/include/sound that alsa-lib needs, IIRC.
And so it would appear, judging by the file date/timestamps. I did not know that. I always seem to learn new things on these boards. Regards. :)
AdamZ
03-12-2004, 02:47 AM
OK, I did everything, didn't work, rebooted, didn't work... I really hate this sound card. Here's all relevant output I could think of:
adam@blarg:~$ sudo modprobe snd-au8820
/lib/modules/2.4.25/kernel/sound/pci/au88x0/snd-au8820.o: init_module: No such device
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.25/kernel/sound/pci/au88x0/snd-au8820.o: insmod /lib/modules/2.4.25/kernel/sound/pci/au88x0/snd-au8820.o failed
/lib/modules/2.4.25/kernel/sound/pci/au88x0/snd-au8820.o: insmod snd-au8820 failed
adam@blarg:~$ cat /proc/asound/cards
--- no soundcards ---
00:04.0 ISA bridge: Intel Corp. 82371AB/EB/MB PIIX4 ISA (rev 02)
Flags: bus master, medium devsel, latency 0
00:04.1 IDE interface: Intel Corp. 82371AB/EB/MB PIIX4 IDE (rev 01) (prog-if 80 [Master])
Flags: bus master, medium devsel, latency 32
I/O ports at b800 [size=16]
00:04.2 USB Controller: Intel Corp. 82371AB/EB/MB PIIX4 USB (rev 01) (prog-if 00 [UHCI])
Flags: bus master, medium devsel, latency 32, IRQ 5
I/O ports at b400 [size=32]
00:0a.0 Communication controller: Conexant HCF 56k Data/Fax Modem (rev 08)
Subsystem: Diamond Multimedia Systems: Unknown device 0abe
Flags: bus master, medium devsel, latency 32, IRQ 3
Memory at de800000 (32-bit, non-prefetchable) [size=64K]
I/O ports at a800 [size=8]
Capabilities: [40] Power Management version 2
00:0b.0 Multimedia audio controller: Aureal Semiconductor Vortex 1 (rev 02)
Subsystem: Aureal Semiconductor AU8820 Vortex Digital Audio Processor
Flags: bus master, medium devsel, latency 32, IRQ 10
Memory at de000000 (32-bit, non-prefetchable) [size=128K]
I/O ports at a400 [size=8]
I/O ports at a000 [size=8]
Capabilities: [dc] Power Management version 1
01:00.0 VGA compatible controller: ATI Technologies Inc Rage 128 RF/SG AGP (prog-if 00 [VGA])
Subsystem: ATI Technologies Inc Magnum/Xpert128/X99/Xpert2000
Flags: bus master, stepping, 66Mhz, medium devsel, latency 64, IRQ 11
Memory at e0000000 (32-bit, prefetchable) [size=64M]
I/O ports at d800 [size=256]
Memory at df000000 (32-bit, non-prefetchable) [size=16K]
Expansion ROM at dffe0000 [disabled] [size=128K]
Capabilities: [50] AGP version 2.0
Capabilities: [5c] Power Management version 1
mdwatts
03-12-2004, 12:00 PM
Originally posted by blargety
adam@blarg:~$ sudo modprobe snd-au8820
/lib/modules/2.4.25/kernel/sound/pci/au88x0/snd-au8820.o: init_module: No such device
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.25/kernel/sound/pci/au88x0/snd-au8820.o: insmod /lib/modules/2.4.25/kernel/sound/pci/au88x0/snd-au8820.o failed
/lib/modules/2.4.25/kernel/sound/pci/au88x0/snd-au8820.o: insmod snd-au8820 failed
adam@blarg:~$ cat /proc/asound/cards
This is a PCI soundcard and you've ensured PnP OS is disabled in the bios? Not having PnP OS disabled is sometimes the cause of those errors.
kevinalm
03-12-2004, 03:30 PM
What happened when you ran alsaconf? Also, does /dev/snd exist (and contain a large number device files, about a hundred plus iirc)? There is a sounddevices script in the alsa-driver source that will create the alsa device files.
AdamZ
03-12-2004, 05:07 PM
Originally posted by kevinalm
What happened when you ran alsaconf? Also, does /dev/snd exist (and contain a large number device files, about a hundred plus iirc)? There is a sounddevices script in the alsa-driver source that will create the alsa device files.
When I ran alsaconf, it asked me which soundcard (au8820 was one of 2 choices, the other being something that didn't seem right(probe legacy ISA devices). Then it asked me whether it should change /etc/alsa/modutils/0.9 (I'll edit this post when I get home) I said yes, then it did stuff, finished, and I tried the soundcard, didn't work.
It took a while while it said "Setting default volume..."
I used sudo when trying alsamixer, and my normal user is in the audio group, so that shouldn't be the problem.
PnP OS is set to no in the BIOS
kevinalm
03-12-2004, 07:07 PM
Ok, all the alsa /dev files seem to be there. That's not it.
That also sounds about right for alsaconf. Except that it's probably modifying /etc/modules.conf (for kernels 2.4.x). Try running alsaconf again, paying particular attention to whether there are any error messages. Also, you might try:
alsactl store
and report any errors.
Also to verify the version of alsa-util that is actually running:
alsactl --version
What I suspect is that previous attempts have left one of the alsa configuration files in a bad state. For example, /etc/asound.state (the mixer settings file) or perhaps one of the files in /usr/share/alsa. A possible solution would be to rename and run alsaconf again. For example,
adam@blarg:~$ sudo alsactl --version
alsactl version 1.0.3
adam@blarg:~$ sudo alsactl store
alsactl: save_state:1061: No soundcards found...
/etc/asound.state doesn't exist. Neither does /etc/alsa/asound.state
kevinalm
03-12-2004, 09:17 PM
Hmmm, alsaconf is supposed to create /etc/asound.state. That suggests that you didn't have sufficient authority when you ran alsaconf. It probably wasn't able to update modules.conf for the same reason. Try:
su
<yourrootpassword>
alsaconf
if you did it as a normal user or by sudo. I thought sudo should work but I've never used it. I don't even have sudo on my system so I can't try and verify. I updated my alsa to the 1.0.3 versions and they do work on my au8830 with a 2.4.23 kernel.
AdamZ
03-13-2004, 01:35 AM
OK, I did it in a console this time, so I could copy & paste the results. After all the dialogs, this is what I got:
Running update-modules...
Loading driver...
Setting default volumes...
Saving the mixer setup used for this in /etc/asound.state.
/usr/sbin/alsactl: save_state:1061: No soundcards found...
Would the fact that I'm running gnome have anything to do with this? Also, here are the configure options I used when compiling alsa-driver:
For alsa-lib and alsa-util, I didn't use any options. Those were the only packages I compiled.
kevinalm
03-13-2004, 03:08 AM
What order did you install? Alsa-driver, alsa-lib, and then alsa-ulil. If you did in the order I originally suggested (lib,utils,driver) there might be a problem as bwkaz pointed out a dependancy of which I was unaware. If you leave alsa-driver alone and recompile lib and then util that possibility should be eliminated. Then run alsaconf again as root.
Your configure options should be fine, as long as you have no isa slots on your mb. Gnome shouldn't be a problem, especially if you exit to rl 3 or <control><alt>Fn to a true console. The only potential problem in doing all this in an x console would be that alsaconf needs to stop the sound server iirc.
I actually did have this same "no cards found" error once. I kept fiddling around trying different things and suddenly it started working. I never really figured out what I did right. I'm pretty sure it has to do with alsa's configuration and not the compiled kernel modules.
AdamZ
03-17-2004, 04:20 PM
I compiled drier, then libs, then util. I have (I believe) some ISA slots on my mb, but the sound card is not an ISA (even if I do have ISA slots, I don't have any ISA cards).
kevinalm
03-17-2004, 07:31 PM
If you have isa slots it would be a very good idea to compile in support for isa, even if you don't use them. It is possible that could be part of the problem. That's just a guess. ;)
How is your card currently behaving? Any success at all?
AdamZ
03-17-2004, 08:52 PM
Originally posted by kevinalm
If you have isa slots it would be a very good idea to compile in support for isa, even if you don't use them. It is possible that could be part of the problem. That's just a guess. ;)
How is your card currently behaving? Any success at all?
OK. I did make uninstall; make clean in the 3 dirs, then compiled, same options except without the --with-isapnp=no. drivers, lib, utils. tried the card, same response.
BTW, the /etc/alsa/modutils/0.9 thing is a link from /etc/modutils/alsa. alsaconf runs update-modules which concats all the files together, creating /etc/modules.conf. There is one section that seems strange, though:
### DEBCONF MAGIC
# This file was automatically generated by alsa-base's debconf stuff
alias /dev/dsp* snd-pcm-oss
alias snd-slot-0 snd-card-0
The rest of the sound section follows
This I assume was left over when I uninstalled alsa-base(I tried using debian packages before this.) Could this be part of the problem? If I comment these lines out, do I have to reboot, or can I just try to modprobe again?
kevinalm
03-17-2004, 09:06 PM
I don't believe you need to reboot. (reasonably certain). It's a good possibility that those earlier entries are causing trouble. I am posting the alsa section of my modules.conf for your reference. Bear in mind I have an au8830.
# --- BEGIN: Generated by ALSACONF, do not edit. ---
# --- ALSACONF verion 1.0.3 ---
alias char-major-116 snd
alias char-major-14 soundcore
alias sound-service-0-0 snd-mixer-oss
alias sound-service-0-1 snd-seq-oss
alias sound-service-0-3 snd-pcm-oss
alias sound-service-0-8 snd-seq-oss
alias sound-service-0-12 snd-pcm-oss
alias snd-card-0 snd-au8830
alias sound-slot-0 snd-au8830
# --- END: Generated by ALSACONF, do not edit. ---
AdamZ
03-20-2004, 04:23 PM
Originally posted by kevinalm
I don't believe you need to reboot. (reasonably certain). It's a good possibility that those earlier entries are causing trouble. I am posting the alsa section of my modules.conf for your reference. Bear in mind I have an au8830.
# --- BEGIN: Generated by ALSACONF, do not edit. ---
# --- ALSACONF verion 1.0.3 ---
alias char-major-116 snd
alias char-major-14 soundcore
alias sound-service-0-0 snd-mixer-oss
alias sound-service-0-1 snd-seq-oss
alias sound-service-0-3 snd-pcm-oss
alias sound-service-0-8 snd-seq-oss
alias sound-service-0-12 snd-pcm-oss
alias snd-card-0 snd-au8830
alias sound-slot-0 snd-au8830
# --- END: Generated by ALSACONF, do not edit. ---
I commented out those lines, still the same result (I even tried rebooting anyway)
The alsa section in my modules.conf is exactly the same, except the last 2 lines say au8820 instead of au8830.
lsmod, modprobe snd-au8820, and the /proc files still all return the same results.
kevinalm
03-20-2004, 09:33 PM
And I imagine there is still no /etc/asound.state file. I am not entirely sure what is wrong. What should work is to install:
alsa-driver
alsa-lib
alsa-utils
then alsaconf. The make installs and alsaconf as root. Alsaconf modifies modprobe.conf/modules.conf (for 2.6 and 2.4 kernels respectively) and creates the asound.state which is mainly a default mixer settings file. There are some other alsa configuration files located in /usr/share/alsa. I don't know a lot about those as they are supposed to be automatically setup in the install process. Possibly something is wrong there. You might have a look around.
Another possibility is some kind of resource conflilt. irq's ports dmas, that sort of thing.
What seems to be the immediate problem is that the userland alsa tools, alsamixer, alsctl and the like, are unaware of your card. I don't know enough about how that part of the alsa system works. Maybe someone else can help out here?
justlinux.com
Copyright Internet.com Inc. All Rights Reserved.