Alright, here's the story: I had slack 10.0 and then 10.2 installed for 4 months and it ran perfect thanks to alot of searching on here and a few posts. Now that harddrive is dead and i got a new one back. Now i cant get slack 10.2 to install right nor 10.

Alright, I've installed atleast 4 times from fresh and cant get my internet to work, sound card to work, and my video drivers to work(i know about riva, i just want the basics for now). I have a selection of files for u guys to look at.

For all of these i ran pci=biosirq and have plug and play turned off i think.
Any help would be greatly appreacated. Also i have a Linkysy BEFW11S4 and think im having trouble there.

root@zujin:~# alsamixer

alsamixer: function snd_ctl_open failed for default: No such device
root@zujin:~# lsmod
Module Size Used by Not tainted
snd-pcm-oss 36704 0 (unused)
snd-pcm 54504 0 [snd-pcm-oss]
snd-timer 13412 0 [snd-pcm]
snd-mixer-oss 12152 0 [snd-pcm-oss]
snd 31268 0 (autoclean) [snd-pcm-oss snd-pcm snd-timer snd-mixer-oss]
snd-page-alloc 4712 0 (autoclean) [snd-pcm snd-timer snd-mixer-oss snd]
soundcore 3396 0 (autoclean) [snd]
parport_pc 15044 1 (autoclean)
lp 6404 0 (autoclean)
parport 22824 1 (autoclean) [parport_pc lp]
ntfs 51232 1 (autoclean)
ide-scsi 9392 0
sis900 12780 0
crc32 2880 0 [sis900]
agpgart 45092 0 (unused)


From syslog:
Jul 27 01:13:34 zujin kernel: PCI: No IRQ known for interrupt pin A of device 00:0a.0. Please try using pci=biosirq.
Jul 27 01:13:34 zujin insmod: /lib/modules/2.4.29/kernel/sound/pci/emu10k1/snd-emu10k1.o.gz: init_module: No such device
Jul 27 01:13:34 zujin insmod: /lib/modules/2.4.29/kernel/sound/pci/emu10k1/snd-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
Jul 27 01:13:34 zujin insmod: /lib/modules/2.4.29/kernel/sound/pci/emu10k1/snd-emu10k1.o.gz: insmod snd-card-0 failed
Jul 27 01:13:34 zujin kernel: PCI: No IRQ known for interrupt pin A of device 00:0a.0. Please try using pci=biosirq.
Jul 27 01:13:34 zujin insmod: /lib/modules/2.4.29/kernel/sound/pci/emu10k1/snd-emu10k1.o.gz: init_module: No such device
Jul 27 01:13:34 zujin insmod: /lib/modules/2.4.29/kernel/sound/pci/emu10k1/snd-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
Jul 27 01:13:34 zujin insmod: /lib/modules/2.4.29/kernel/sound/pci/emu10k1/snd-emu10k1.o.gz: insmod snd-card-0 failed
Jul 27 01:13:34 zujin kernel: PCI: No IRQ known for interrupt pin A of device 00:0a.0. Please try using pci=biosirq.
Jul 27 01:13:34 zujin insmod: /lib/modules/2.4.29/kernel/sound/pci/emu10k1/snd-emu10k1.o.gz: init_module: No such device
Jul 27 01:13:34 zujin insmod: /lib/modules/2.4.29/kernel/sound/pci/emu10k1/snd-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
Jul 27 01:13:34 zujin insmod: /lib/modules/2.4.29/kernel/sound/pci/emu10k1/snd-emu10k1.o.gz: insmod sound-slot-0 failed


From dmesg:
Linux version 2.4.29 (root@midas) (gcc version 3.3.4) #6 Thu Jan 20 16:30:37 PST 2005
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 0000000027ffc000 (usable)
BIOS-e820: 0000000027ffc000 - 0000000027fff000 (ACPI data)
BIOS-e820: 0000000027fff000 - 0000000028000000 (ACPI NVS)
BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
639MB LOWMEM available.
On node 0 totalpages: 163836
zone(0): 4096 pages.
zone(1): 159740 pages.
zone(2): 0 pages.
Kernel command line: BOOT_IMAGE=Linux ro root=302 hdc=ide-scsi
ide_setup: hdc=ide-scsi
Initializing CPU#0
Detected 2550.036 MHz processor.
Console: colour dummy device 80x25
Calibrating delay loop... 5085.59 BogoMIPS
Memory: 645048k/655344k available (1831k kernel code, 9908k reserved, 607k data, 120k init, 0k highmem)
Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
Inode cache hash table entries: 65536 (order: 7, 524288 bytes)
Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer cache hash table entries: 65536 (order: 6, 262144 bytes)
Page-cache hash table entries: 262144 (order: 8, 1048576 bytes)
CPU: Trace cache: 12K uops, L1 D cache: 8K
CPU: L2 cache: 512K
CPU: After generic, caps: 3febfbff 00000000 00000000 00000000
CPU: Common caps: 3febfbff 00000000 00000000 00000000
CPU: Intel(R) Pentium(R) 4 CPU 2.26GHz stepping 04
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
mtrr: v1.40 (20010327) Richard Gooch (rgooch@atnf.csiro.au)
mtrr: detected mtrr type: Intel
PCI: PCI BIOS revision 2.10 entry at 0xf10c0, last bus=1
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
PCI: Using IRQ router default [1039/0963] at 00:02.0
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapd
VFS: Disk quotas vdquot_6.5.1
Journalled Block Device driver loaded
vesafb: framebuffer at 0xe0000000, mapped to 0xe880d000, size 1536k
vesafb: mode is 1024x768x8, linelength=1024, pages=3
vesafb: protected mode interface info at c000:d6a0
vesafb: scrolling: redraw
Console: switching to colour frame buffer device 128x48
fb0: VESA VGA frame buffer device
pty: 512 Unix98 ptys configured
Serial driver version 5.05c (2001-07-08) with HUB-6 MANY_PORTS MULTIPORT SHARE_IRQ SERIAL_PCI enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
Real Time Clock Driver v1.10f
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
RAMDISK driver initialized: 16 RAM disks of 7777K size 1024 blocksize
loop: loaded (max 8 devices)
Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
SIS5513: IDE controller at PCI slot 00:02.5
SIS5513: chipset revision 0
SIS5513: not 100% native mode: will probe irqs later
SIS5513: SiS 962/963 MuTIOL IDE UDMA133 controller
ide0: BM-DMA at 0xb400-0xb407, BIOS settings: hdaMA, hdbMA
ide1: BM-DMA at 0xb408-0xb40f, BIOS settings: hdcMA, hddMA
hda: WDC WD800JB-00JJA0, ATA DISK drive
hdb: WDC WD600JB-00CRA1, ATA DISK drive
blk: queue c03ad460, I/O limit 4095Mb (mask 0xffffffff)
blk: queue c03ad59c, I/O limit 4095Mb (mask 0xffffffff)
hdc: CREATIVE CD5233E-N, ATAPI CD/DVD-ROM drive
hdd: PHILIPS CDRW2412A, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: attached ide-disk driver.
hda: host protected area => 1
hda: 156301488 sectors (80026 MB) w/8192KiB Cache, CHS=9729/255/63, UDMA(100)
hdb: attached ide-disk driver.
hdb: host protected area => 1
hdb: setmax LBA 117231408, native 117229295
hdb: 117229295 sectors (60021 MB) w/8192KiB Cache, CHS=7297/255/63, UDMA(100)
hdd: attached ide-cdrom driver.
hdd: ATAPI 40X CD-ROM CD-R/RW drive, 8192kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.12
Partition check:
hda: hda1 hda2 hda3
hdb: hdb1
SCSI subsystem driver Revision: 1.00
kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
md: linear personality registered as nr 1
md: raid0 personality registered as nr 2
md: raid1 personality registered as nr 3
md: raid5 personality registered as nr 4
raid5: measuring checksumming speed
8regs : 2905.200 MB/sec
32regs : 1828.000 MB/sec
pIII_sse : 3283.200 MB/sec
pII_mmx : 2915.200 MB/sec
p5_mmx : 2862.800 MB/sec
raid5: using function: pIII_sse (3283.200 MB/sec)
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
LVM version 1.0.8(17/11/2003)
Initializing Cryptographic API
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 8192 buckets, 64Kbytes
TCP: Hash tables configured (established 262144 bind 65536)
Linux IP multicast router 0.06 plus PIM-SM
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
FAT: bogus logical sector size 0
UMSDOS: msdos_read_super failed, mount aborted.
FAT: bogus logical sector size 0
FAT: bogus logical sector size 0
reiserfs: found format "3.6" with standard journal
reiserfs: checking transaction log (device ide0(3,2)) ...
for (ide0(3,2))
ide0(3,2):Using r5 hash to sort names
VFS: Mounted root (reiserfs filesystem) readonly.
Freeing unused kernel memory: 120k freed
Adding Swap: 506036k swap-space (priority -1)
Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 564M
agpgart: Detected SiS 648 chipset
agpgart: AGP aperture is 128M @ 0xd0000000
sis900.c: v1.08.07 11/02/2003
PCI: Enabling device 00:04.0 (0004 -> 0007)
PCI: No IRQ known for interrupt pin A of device 00:04.0. Please try using pci=biosirq.
eth0: VIA 6103 PHY transceiver found at address 1.
eth0: Using transceiver found at address 1 as default
eth0: SiS 900 PCI Fast Ethernet at 0x9800, IRQ 0, 00:0c:6e:af:f9:88.
hdc: attached ide-scsi driver.
scsi0 : SCSI host adapter emulation for IDE ATAPI devices
Vendor: CREATIVE Model: CD5233E-N Rev: 0.20
Type: CD-ROM ANSI SCSI revision: 02
Attached scsi CD-ROM sr0 at scsi0, channel 0, id 0, lun 0
sr0: scsi3-mmc drive: 0x/52x cd/rw xa/form2 cdda tray
NTFS driver v1.1.22 [Flags: R/O MODULE]

If you added pci=biosirq, then why does the kernel command line from your dmesg not show it?

I'd figure the option would show on the kernel command line if you added it to your kernel booting options.

Did you add it to the append option of your lilo.conf file?
Did you re-run lilo after you made your changes?

For more information check out your local /usr/src/linux/Documentation/kernel-parameters.txt.

GL

well, i changed that and still no go on sound but i do have the net now :-D I also set IRQ's 3-5 as reserved in bios. I'm gonna try and reserve some more to see what happens.

you want plug and play on. (in bios and in slack)

do you have all the correct "drivers" in your kernel or modulated?

1st log in as root at the xserv prompt.
open a shell.

# aumix

adjust the sound.

If your drivers are good you should now have sound and let the music play.

if you don't have sound, compile the kernel according to the slackware offical manual, but see if your chipset is listed. ;^>


It sound like you are not using the proper driver for your chipset. snd-emu10k1.o.gz I dont think is sis.

if you recompile use old config option and change it around as needed.
Use offical slackware manual for instructions (long hand).

make oldconfig menuconfig
make dep
make bzImage
etc...

insert ramdisk into the kernel at default 16MB.
add binaries for a.out (and Freebsd binaries) and all used file system formats.
frame buffer vesa and 16bit just above it
raid.
scsi emulation and chipsets if you have it.
generic IDE and dma when possable.
chipsets !!!
auto mouning of modules.
usb if using it.

yada yada Yoda.

umm.



10.2?

Yea, that also caught my eye... strange, isn't? Wherever from??

But, anyway, here how Shilo on his page recommends setting sound for Slackware..
http://shilo.is-a-geek.com/slack/sound10.html

I know the /etc/slackware-version for current still says 10.1.0

Thought I'd jump in here because this thread is recent.

This is not just a Slackware problem; every distribution seems to be having this problem. It is more than likely either a SoundBlaster problem or a lame PnP problem.

I get the same exact message as the original question, bout the emu10k1 files and snd-emu10k1.o.gz: init_module: No such device

After playing around with various parts of Alsa, Arts, OSS, kmix, kmid, and all the other multimedia applications, and editing modules.conf, I had sound. However, not all sound.

Xmms, by the way, has a terrible black background display, but won't play midi files.

Okay, so I had everything going except midi. I erased the alsaconf portion of modules.conf and started over. This time, I got the send control problem. Before, I was able to open Arts tool | View | Midi Manager, but only had OSS stuff, whereas before I had all kinds of midi maps and stuff.

At one point, I could see VU's while playing Midi, but heard no sound.

The thing that seems to be wrong is the missing additional configuration in modules.conf

The VU's, apparently, are monitoring the input, with no view of the output. Based on the Amek board I'm using, and others I have used [MCI, Neve, etc..] VU should always be selectible as to what it is showing, Input, Output, Aux Buss, and so on. So these VU's show me I've had Input, but no Output.

This places it squarely on routing and enabling of the signal sends. In any good board, a single button "Sends" to any buss or channel you wish. Not so in four programs, Alsa, Arts, OSS, and Noatun.

With Plug and Play, the issue becomes confused at best.

There is no reason why reserved Legacy and Plug and Play should not both work, together. Since they do, in Windows and other programs, there is only one culprit; the Linux configuration.

And, as I said, the problem with SB Live or SoundBlaster in general is mostly the fault of SoundBlaster. Okay, so SoundBlaster is Creative Labs is Ensoniq; they are all the same company now. They have a terrible record of not working right.

E-mu was aboriginally a synthesizer, one you bought at a musical instrument store, I know, because I had one, just as I've had Ensoniq's, Korg's, and all the others. Basically, "emu" these days is anything based on the electronics of that long ago synthesizer.

It's basically just "Electronic Music."

And that implies "patching" and midi-maps, and all the stuff that was on that and other synthesizers. Somehow, this all got lost in "acronymia."

But on the synth, you'd call up a window in a little LCD area and connect the input to the output, called "Sends."

If you didn't send to an output, by programming the synth, you got no output.

Which is fairly much what is happening here.

When I had, in Midi Manager, Input: OSS MIdi Port and Output: Midi Map 0, I could simply select connect, and I'd have the Midi source sent to the Midi Map Controller, however, there was still no Midi sound.

MPU is similar; I'm just going to say that EMU is Electronics Music Unit and MPU is Music Processing Unit.

I can trace them both all the way back to Professor Moog at the Benjamin Franklin Institute in Philadelphia where all synthesizers, Midi itself, and these chips trace back to when they were tubes strung together by Professor Moog and his assistants. The same problems occurred; patches [cables back then] simply were not connected properly for sound output.

On the modern versions, microcircuits, there are busses, enable functions, and printed circuit lans that make up the patches. If not enabled, then certain outputs simply do not appear, or, in the audio world, get heard.

Aside from the DAC's [Digital to Analogue Converter] chips and the SAD [Serial Analogue to Digital] chips, the Inputs and Outputs must be both enable and routed.

Midi is generally "injected" before the the SAD chip and the Output of the SAD chip is enabled to produce a musical sound. This goes to a set of analogue amplifiers which produce the output, an analogue signal called music.

On the Input, usually an analogue signal is applied to the Input of a DAC chip to produce the digital representation of the analogue waves that constitute music. From there, the results of "sampling" the wave are stored in digital form, sometimes Midi, but now other forms.

So, any break in the chain, and there is no music.

Drivers are used to enable and route the signals. The failure of any driver also results in no music, or worse.

So, if your drivers can't patch and enable the signals and sound, the result is no Input, or, no Output, or both failures.

All of these depend on IRQ's, which is the basic function of Input/Output. the I/O section of any computer.

lsmod should tell you that the devices for emu10k1 exist. If they do, then snd failed in opening the device because it "could not find the path."

If modprobe snd-emu10k1 fails with No Such Device, then it is most likely the path dependencies of IRQ and IO, that is, the Interrupt Request Queue and the IOCW [Input/Ouput Control Word] called the Port or IO Address which is the stack/memory address where the IO Command is either stored or pointed to by an IRW [Indirect Reference Word], that is, in C, a pointer.

Hardware IRQ's are simpler, and much faster, while PnP IRQ's, needing to be rerouted through software, are more complex and much slower.

Any compiled object which does not account for both types, is bound to fail in 1 out of 2 cases, consistently.

So SoundBlaster, with its dedication to PnP, is prone to fail in about 1 out of every 2 installations, when Legacy IRQ's are reserved, or, when initialization of the PnP layer is incomplete.

Simplistically, the Default Settings for Alsa, Arts, OSS, and the others is incomplete, and to blame.

Restarting alsa with /etc/rc.d/rc.alsa restart
should reload the modules, however, this may not always be the case, since Linux, for some spooky "Windows developer infiltration" reason, seems to need to reboot. Perhaps it's just the update module dependencies. Linux should never need to reboot for anything!

In the end, it's a trial and error configuration for the Alsa portion of modules.conf

Adding these:

http://www.alsa-project.org/alsa-doc...owto/c1605.htm

worked, but rerunning alsaconf simply seems to add to these and result in, oftentimes, "no mixer elems found," whatever that poor programming error result statement means.

Any contributions to working on this problem will be considered.

Go to :

ftp://guest@musics.com/uploads/Linux/Sound/

and upload comments, suggestions. and don't forget to include contact information!

Directory creation format is YYYYMMDD_name, as in:

20050830_nicname

This organizes entries by date, then name, for automatic sorted display by date.

What is needed is better information on this problem, and some good alsa.conf examples.

There are 2 seperate Soundblaster Live! drivers. One for the standard version and one for an OEM version (Dell I think)
It could be alsaconf is getting confused between the 2 Unfortunately I can't remember which is which either
The readme in the ALSA source will have the names of the drivers, though. Or you could check on the ALSA website, much easier

Reburn slack10.2 to cdrw disks from diffrent mirror. reinstall.