14 Feb
2003
14 Feb
'03
10:16 p.m.
Hello
I'm almost as new to Debian and Linux as I am to DeMuDi, so I've kind of
dropped myself in at the deep end I guess.
I've successfully installed the demudi-2.4.18 kernel, which I must say was
remarkably smooth i.e. my system still works jus as well as it did before I
installed the new kernel. Well done to whoever packaged that up!
However, when I get to the point of configuring demudi-base it comes up with:
modprobe: Nothing to load ???
Specify at least a module or a wildcard like \*
and then it hangs. I'm confused. Where should I specify these modules?
Also my system can't find any opti92x module does this mean I have to go
find/download one? I've been running the bluepoint/OPTi soundcard with mad16
semi-succesfully up to this point. modprobe won't load seq-oss either which
makes me suspect I have conflicts with my modules (?) :-/
I will admit to being only about half-way through all the available
documentation, which _is_ mighty, _especially_ if I was compiling it.
I don't suppose anything like a straightforward demudi install HOWTO exists
just yet (I guess you're all flat out with current developments).
My eyes are going familiarly wiggly with on-screen reading, so I thought I'd
dash off a quick email just to see if the list could give me any obvious
pointers.
forgive me if I'm being an utter twink here. If so, even a brief RTFM
response would probably give me a significant clue. I include the results of
my most recent lsmod & dmesg just to illustrate the point.
yours hopefully
tim hall
tim(a)glastonburymusic.org.uk
********************************************************************************
Module Size Used by Not tainted
parport_pc 22056 1 (autoclean)
lp 6336 0 (autoclean)
parport 22976 1 (autoclean) [parport_pc lp]
serial 44064 0 (autoclean)
opl3 11112 0 (unused)
smc-ultra 5024 0 (unused)
8390 5920 0 [smc-ultra]
ipv6 123424 -1
mad16 7392 0 (unused)
ad1848 20896 0 [mad16]
isa-pnp 28168 0 [serial smc-ultra ad1848]
sb_lib 32480 0 [mad16]
uart401 6080 0 [mad16 sb_lib]
sound 52620 0 [opl3 mad16 ad1848 sb_lib uart401]
soundcore 3492 5 [sb_lib sound]
af_packet 11528 0 (unused)
rtc 5528 0 (autoclean)
ext2 30784 3 (autoclean)
ide-disk 6624 4 (autoclean)
ide-probe-mod 8080 0 (autoclean)
ide-mod 130892 4 (autoclean) [ide-disk ide-probe-mod]
ext3 56864 0 (autoclean)
jbd 35272 0 (autoclean) [ext3]
unix 13316 44 (autoclean)
Linux version 2.4.18-586-demudi (free@leporello) (gcc version 2.95.4 20011002
(Debian prerelease)) #1 Tue Oct 15 11:19:17 CEST 2002
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 0000000003000000 (usable)
BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
On node 0 totalpages: 12288
zone(0): 4096 pages.
zone(1): 8192 pages.
zone(2): 0 pages.
Kernel command line: BOOT_IMAGE=demudi ro root=301
Initializing CPU#0
Detected 133.637 MHz processor.
Console: colour VGA+ 80x25
Calibrating delay loop... 266.24 BogoMIPS
Memory: 43976k/49152k available (808k kernel code, 4792k reserved, 196k data,
192k init, 0k highmem)
Dentry-cache hash table entries: 8192 (order: 4, 65536 bytes)
Inode-cache hash table entries: 4096 (order: 3, 32768 bytes)
Mount-cache hash table entries: 1024 (order: 1, 8192 bytes)
Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes)
Page-cache hash table entries: 16384 (order: 4, 65536 bytes)
CPU: Before vendor init, caps: 000001bf 00000000 00000000, vendor = 0
Intel Pentium with F0 0F bug - workaround enabled.
CPU: After vendor init, caps: 000001bf 00000000 00000000 00000000
CPU: After generic, caps: 000001bf 00000000 00000000 00000000
CPU: Common caps: 000001bf 00000000 00000000 00000000
CPU: Intel Pentium 75 - 200 stepping 0c
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
PCI: PCI BIOS revision 2.10 entry at 0xfb210, last bus=0
PCI: Using configuration type 1
PCI: Probing hardware on bus (00:00)
Limiting direct PCI/PCI transfers.
Activating ISA DMA hang workarounds.
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapd
VFS: Diskquotas version dquot_6.4.0 initialized
Detected PS/2 Mouse Port.
pty: 256 Unix98 ptys configured
block: 128 slots per queue, batch=32
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
Cronyx Ltd, Synchronous PPP and CISCO HDLC (c) 1994
Linux port (c) 1998 Building Number Three Ltd & Jan "Yenya" Kasprzak.
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 4096 bind 4096)
Linux IP multicast router 0.06 plus PIM-SM
RAMDISK: cramfs filesystem found at block 0
RAMDISK: Loading 2580 blocks [1 disk] into ram disk...
|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/done.
Freeing initrd memory: 2580k freed
VFS: Mounted root (cramfs filesystem).
Freeing unused kernel memory: 192k freed
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
Journalled Block Device driver loaded
Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
PIIX3: IDE controller on PCI bus 00 dev 39
PIIX3: chipset revision 0
PIIX3: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0x9000-0x9007, BIOS settings: hda:pio, hdb:pio
ide1: BM-DMA at 0x9008-0x900f, BIOS settings: hdc:pio, hdd:pio
hda: ST31720A, ATA DISK drive
hdc: FX800S, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: 3331852 sectors (1706 MB), CHS=3305/16/63
Partition check:
hda: [PTBL] [826/64/63] hda1 hda2 < hda5 hda6 hda7 >
ext3: No journal on filesystem on ide0(3,1)
Adding Swap: 98748k swap-space (priority -1)
Real Time Clock Driver v1.10e
isapnp: Scanning for PnP cards...
isapnp: Card 'SMC EtherEZ (8416)'
isapnp: 1 Plug & Play card detected total
ad1848/cs4248 codec driver Copyright (C) by Hannu Savolainen 1993-1996
ad1848: No ISAPnP cards found, trying standard ones...
MAD16 audio driver Copyright (C) by Hannu Savolainen 1993-1996
CDROM Disabled.
Joystick port enabled.
IPv6 v0.8 for NET4.0
IPv6 over IPv4 tunneling driver
smc-ultra.c: Presently autoprobing (not recommended) for a single card.
smc-ultra.c: ISAPnP reports SMC EtherEZ (8416) at i/o 0x240, irq 10.
smc-ultra.c:v2.02 2/3/98 Donald Becker (becker(a)cesdis.gsfc.nasa.gov)
eth0: SMC EtherEZ at 0x240, 00 00 C0 D1 23 E0,assigned IRQ 10 programmed-I/O
mode.
YM3812 and OPL-3 driver Copyright (C) by Hannu Savolainen, Rob Hooft 1993-1996
Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI
ISAPNP enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at 0x02f8 (irq = 3) is a 16550A
15 Feb
15 Feb
5:16 a.m.
On Sat, Feb 15, 2003 at 02:08:53AM +0000, tim hall wrote:
I'm almost as new to Debian and Linux as I am to
DeMuDi, so I've kind of
dropped myself in at the deep end I guess.
I've successfully installed the demudi-2.4.18 kernel, which I must say was
remarkably smooth i.e. my system still works jus as well as it did before I
installed the new kernel. Well done to whoever packaged that up!
However, when I get to the point of configuring demudi-base it comes up with:
modprobe: Nothing to load ???
Specify at least a module or a wildcard like \*
You cannot do modprobe \*, you
always have to modprobe a specific
modulename.
and then it hangs. I'm confused. Where should I
specify these modules?
In /etc/modules you can specify those modules you want to be
loaded at
boot time. I put modules in there like my scsi host controller and the
module of my soundcard (snd-card-...) and the OSS emulation module
(snd-pcm-oss I think). Because the module system knows its dependencies,
automatically all the needed modules are loaded.
Also my system can't find any opti92x module does
this mean I have to go
find/download one? I've been running the bluepoint/OPTi soundcard with mad16
semi-succesfully up to this point. modprobe won't load seq-oss either which
makes me suspect I have conflicts with my modules (?) :-/
If you just installed a new kernel, you probably don't have the alsa
modules for that kernel installed (look for a alsa-modules-2.4.18-...
package). Once you install that, look for all the snd-card-*.o modules in
/lib/modules/2.4.18/alsa/ and use the one referring to your sound card
to modprobe, eg. modprobe snd-card-fm801 (without the .o).
Modules are specific to a kernel version.
I will admit to being only about half-way through all
the available
documentation, which _is_ mighty, _especially_ if I was compiling it.
I don't suppose anything like a straightforward demudi install HOWTO exists
just yet (I guess you're all flat out with current developments).
I don't
know of one yet.
One useful place to look for docs is in /usr/share/doc/*, all
distributions put the docs for all packages in there.
Useful sites: http://www.djcj.org/LAU/guide/index.php,
http://www.mstation.org/ and of course google with the right keywords ;)
forgive me if I'm being an utter twink here. If so,
even a brief RTFM
response would probably give me a significant clue. I include the results of
my most recent lsmod & dmesg just to illustrate the point.
Feel free to ask more
questions if the need arises.
best regards,
Vincent
10:26 p.m.
On Saturday 15 February 2003 09:08, Frank Barknecht wrote:
tell that to demudi-base, that was the error message I received. It makes no
sense to me either.
...and I'm still getting it *gnash*
[...]
These are the OSS/Free kernel drivers. You need to get
rid of them ;)
by installing alsa-modules-2.4.18 and configuring the modules.
www.alsa-project-org/alsa-doc has detailed instructions for this. On
Debian, modules configuration takes place under /etc/modutils. With
modconf you can install or deinstall the kernel-modules. ALSA has
alsaconf to help with configuring the alsa-modules, but last time I
looked, this was broken.
It appears to work, but for ALSA-0.5 only
You might be better of by creating a file
/etc/modutils/alsa as described on alsa-project.org and run
update-modules as root by hand.
interestingly enough alsaconf updated /etc/alsa/modutils/0.5
I have a file next door to it called ./0.9-demudi, which is much easier to
read.
I tried applying some appropriate looking values to this file, but I'm not
sure how to activate it. update-modules does not appear to touch this file.
I'm also not sure that I should be putting my soundcard details in
/etc/modutils as that duplicates the values in /etc/alsa/modutils.
On Saturday 15 February 2003 09:10, Vincent wrote:
On Sat, Feb 15, 2003 at 02:08:53AM +0000, tim hall
wrote:
[...]
However, when I
get to the point of configuring demudi-base it comes up
with: modprobe: Nothing to load ???
Specify at least a module or a wildcard like \*
You cannot do modprobe \*, you always have to modprobe a specific
modulename.
If you just installed a new kernel, you probably don't have the alsa
modules for that kernel installed (look for a alsa-modules-2.4.18-...
package). Once you install that, look for all the snd-card-*.o modules in
/lib/modules/2.4.18/alsa/ and use the one referring to your sound card
to modprobe, eg. modprobe snd-card-fm801 (without the .o).
yep done all that
My system appears to be having trouble recognising the soundcard &/ driver
(both in different instances). It is possible that I should be using
snd-opti9xx instead of snd-opti92x or something similar, so I shall try that
next. It is also possible that I have the soundcard in the wrong slot. Do I
understand right that it will probably want to be in the top available slot
in my tower case?
Either that or I have a dodgy soundcard :-] (Bluepoint/OPTi 82c931) I have a
cs4232 in the drawer, which I might try instead as I know it works.
anyone had any experience of using these cards under ALSA?
Thanks for all the useful references to various bits of documentation. And
thanks just for replying, it helps me to work out whether I'm just being
plain dim or whether my hardware isn't right. I generally find that once I
get to the point of list-mailing it's due to broken / badly set up hardware.
take care & take it often
tim hall
16 Feb
16 Feb
11:51 a.m.
Hallo,
tim hall hat gesagt: // tim hall wrote:
Delete this, if you don't use ALSA 0.5 and you really shouldn't do
that as well, 0.5 is way obsolete.
You might be
better of by creating a file
/etc/modutils/alsa as described on alsa-project.org and run
update-modules as root by hand.
interestingly enough alsaconf updated /etc/alsa/modutils/0.5 I have a file next door to it called ./0.9-demudi,
which is much easier to
read.
I tried applying some appropriate looking values to this file, but I'm not
sure how to activate it. update-modules does not appear to touch this file.
I'm also not sure that I should be putting my soundcard details in
/etc/modutils as that duplicates the values in /etc/alsa/modutils.
They may already be the same file, i.e. one is a link to the other
like here:
$ ls -l /etc/modutils/
total 21
lrwxrwxrwx 1 root root 22 Aug 12 2002 alsa -> /etc/alsa/modutils/0.9
It is important, that you have one under /etc/modutils/.
update-modules collects everything under this directory to build the
'real' module configuration, which is in /etc/modules.conf. This last
file gets overwritten everytime you or an installaton script calls
update-modules.
ciao
--
Frank Barknecht _ ______footils.org__
12:45 p.m.
Thanks Frank, that's probably the information I need :-)
my only problem now, is that when I try to 'modprobe snd-opti92x-ad1848' I
get 'no OPTi 82C92x soundcard found'.
Which is strange because I'm sure I put one in the case :~]
The soundcard is one that is theoretically PnP but in actuality is not
recognised by the BIOS.
I think I'm close
tim hall
On Sunday 16 February 2003 15:43, Frank wrote:
Hallo,
tim hall hat gesagt: // tim hall wrote:
Delete this, if you don't use ALSA 0.5 and you really shouldn't do
that as well, 0.5 is way obsolete.
You might
be better of by creating a file
/etc/modutils/alsa as described on alsa-project.org and run
update-modules as root by hand.
interestingly enough alsaconf updated /etc/alsa/modutils/0.5 I have a file next door to it called
./0.9-demudi, which is much easier
to read.
I tried applying some appropriate looking values to this file, but I'm
not sure how to activate it. update-modules does not appear to touch this
file. I'm also not sure that I should be putting my soundcard details in
/etc/modutils as that duplicates the values in /etc/alsa/modutils.
They may already be the same file, i.e. one is a link to the other
like here:
$ ls -l /etc/modutils/
total 21
lrwxrwxrwx 1 root root 22 Aug 12 2002 alsa ->
/etc/alsa/modutils/0.9
It is important, that you have one under /etc/modutils/.
update-modules collects everything under this directory to build the
'real' module configuration, which is in /etc/modules.conf. This last
file gets overwritten everytime you or an installaton script calls
update-modules.
ciao
9:37 p.m.
On Monday 17 February 2003 10:08, I wrote:
I think I'm close
Sadly I was wrong
However I have narrowed it down to the fact that the kernel (?) won't
recognise any soundcard even if the BIOS does - it's exactly the same with my
cs4232 or OPTi82C930.
I despair
I _really_ hope I'm overlooking something stupidly obvious.
tim hall
15 Feb
15 Feb
5:16 a.m.
Hallo,
tim hall hat gesagt: // tim hall wrote:
I'm almost as new to Debian and Linux as I am to
DeMuDi, so I've kind of
dropped myself in at the deep end I guess.
You should read some general Debian documents. I only have links to
german pages right now, but debian.org should give some pointers.
Also my system can't find any opti92x module does
this mean I have to go
find/download one? I've been running the bluepoint/OPTi soundcard with mad16
semi-succesfully up to this point. modprobe won't load seq-oss either which
makes me suspect I have conflicts with my modules (?) :-/
If you want do to anything remotely serious with audio you need to
install the ALSA drivers for your soundcards and libasound2.
mad16 7392 0 (unused)
ad1848 20896 0 [mad16]
isa-pnp 28168 0 [serial smc-ultra ad1848]
sb_lib 32480 0 [mad16]
uart401 6080 0 [mad16 sb_lib]
sound 52620 0 [opl3 mad16 ad1848 sb_lib uart401]
These are the OSS/Free kernel drivers. You need to get rid of them ;)
by installing alsa-modules-2.4.18 and configuring the modules.
www.alsa-project-org/alsa-doc has detailed instructions for this. On
Debian, modules configuration takes place under /etc/modutils. With
modconf you can install or deinstall the kernel-modules. ALSA has
alsaconf to help with configuring the alsa-modules, but last time I
looked, this was broken. You might be better of by creating a file
/etc/modutils/alsa as described on alsa-project.org and run
update-modules as root by hand.
ciao
--
Frank Barknecht _ ______footils.org__
7953
days inactive
7955
days old
linux-audio-user@lists.linuxaudio.org
6 comments
3 participants
participants (3)
-
Frank Barknecht -
tim hall -
Vincent Touquet