/dev/rob0 wrote:
> On Sat, 11 Sep 2004 16:07:42 +0000, rg wrote:
>
>>>>So ... would uninstalling and reinstalling the Alsa package work.
>>>
>>>Yes, thats the easiest way to get your alsa modules back.
>
>
> No, that does not work when you've built a custom kernel.

Yes, you are right about this. Live and learn

>
>
>>OK, I uninstalled ALSA (driver,lib,oss,utils). Then reinstalled them.
>>I verified that the ALSA sound modules were installed under
>>/lib/modules/2.4.26/kernel/sound
>>
>>ls -l /lib/modules/2.4.26/kernel/sound/isa
>>-rw-r--r-- 1 root root 10885 2004-06-13 20:39 snd-als100.o
>
>
> On 2004/June/13 you built a custom kernel with the $VERSION string of
> "2.4.26". You ran the Makefile "modules_install" target at 20:39 your
> time. These are not the Slackeware modules. The Slackware modules are
> gzipped.

You are right again, they were gzipped when I reinstalled and checked.
However, I thought maybe the
installpkg hadn't worked correctly. So i decompressed everything under
/lib/modules/2.4.26/kernel/sound,
hence the snd*.o listing above.


>
>
>>So far so good. I then ran "alsaconf". It probed and found: snd-opl3sa2.o
>
>
> Or was it snd-opl3sa2.o.gz?
>

See above.

>
>># modprobe snd-opl3sa2
>>/lib/modules/2.4.26/kernel/sound/acore/snd.o: unresolved symbol
>>request_module
>>[snip]
>>So, something is sill not right. Maybe something needs to be selected
>>when configuring the kernel
>
>
> Yes, it's a misconfigured kernel. Start with the Slackware .config and
> work from there.
>
>
>>I built a custom 2.4.26 kernel for bluetooth and ipaq. I used my 2.4.24
>>config file.
>
>
> Then it's hard to say what went wrong, but the error quoted above
> suggests that your custom kernel lacks support for loading modules.
>
Yeah, you're right its hard to figure out what went wrong. However, I
know my
custom kernel is configured to support loading modules.
I'm using OSS modules in the listing below and they work perfectly.

$ lsmod
Module Size Used by Not tainted
opl3 12868 0 (unused)
opl3sa2 8368 2
ad1848 24396 0 [opl3sa2]
isa-pnp 32496 0 [opl3sa2 ad1848]
mpu401 20868 0 [opl3sa2]
sound 58248 2 [opl3 opl3sa2 ad1848 mpu401]
usb-storage 26480 0 (unused)
uhci 25884 0 (unused)
usbcore 61996 1 [usb-storage uhci]
tulip 42048 1
crc32 2880 0 [tulip]
ipt_limit 888 7
ipt_mac 632 0 (unused)
ipt_state 536 36
ipt_LOG 3448 12
ip_conntrack_ftp 4144 0 (unused)
ip_conntrack 20036 1 [ipt_state ip_conntrack_ftp]
iptable_filter 1740 1
ip_tables 12960 5 [ipt_limit ipt_mac ipt_state ipt_LOG
iptable_filter]
sd_mod 11180 0 (unused)
sr_mod 14104 0 (unused)
sg 27996 0 (unused)
ide-scsi 10288 0
scsi_mod 56600 5 [usb-storage sd_mod sr_mod sg ide-scsi]
agpgart 29536 0 (unused)

>
>>I would like to get this working *without* installing drivers from the
>>Alsa web-site, if at all possible.
>
>
> In general you should plan on recompiling third-party kernel modules
> for each custom kernel. That may not ALWAYS be necessary, but IME it
> usually is.
>

Yes ... I agree, this seems to be the best way at this point. I guess I
need to check
to see what the installation of those drivers will do to my OSS modules.
I don't want those blown
away and not have any sound at all.

>
>>Any ideas, comments or advice would be very welcome.
>
>
> A good trick when you're building a kernel of the same version as you
> got from the distro is to add something to the $VERSION string in the
> top-level Makefile. (EXTRAVERSION is provided for this purpose.) That
> way your custom modules don't conflict with the Slackware ones.

Great trick ... I have been building custom kernels for quite a while
now and have never used this
A very handy thing to know.

Thanks for responding !!!!!

dev wrote :

>>>>So ... would uninstalling and reinstalling the Alsa package work.
>>>
>>> Yes, thats the easiest way to get your alsa modules back.
>
> No, that does not work when you've built a custom kernel.

Yes it will. Its still the same kernel version, all rg did was adding
bluetooth and IPAQ support to the kernel. You'll only have to compile
ALSA yourself if you has upgraded the kernel to a never version.
--
Thomas O.

This area is designed to become quite warm during normal operation.

On Sat, 11 Sep 2004 20:02:12 +0000, rg wrote:
>>>>>So ... would uninstalling and reinstalling the Alsa package work.
>>>>
>>>>Yes, thats the easiest way to get your alsa modules back.
>>
>> No, that does not work when you've built a custom kernel.
>
> Yes, you are right about this. Live and learn

Well, maybe not. In theory Thomas is right; on the same kernel source
tree and with compatible configuration settings it should work. I bet
the kicker is the latter: you must have changed something which broke
it.

> need to check to see what the installation of those drivers will
> do to my OSS modules. I don't want those blown
> away and not have any sound at all.

ALSA drivers won't affect OSS at all. The only thing is you can't have
2 drivers running the same card. I bet with 2 sound cards you could
have OSS on one and ALSA on the other ... testing ... oops, can't test
on this machine, my OSS module isn't there. (Not that it matters, just
a curiosity.)

> Thanks for responding !!!!!

Glad to help.
--
/dev/rob0 - preferred_email=i$((28*28+28))@softhome.net
or put "not-spam" or "/dev/rob0" in Subject header to reply

Thomas Overgaard wrote:
> dev wrote :
>
>
>>>>>So ... would uninstalling and reinstalling the Alsa package work.
>>>>
>>>>Yes, thats the easiest way to get your alsa modules back.
>>
>>No, that does not work when you've built a custom kernel.
>
>
> Yes it will. Its still the same kernel version, all rg did was adding
> bluetooth and IPAQ support to the kernel. You'll only have to compile
> ALSA yourself if you has upgraded the kernel to a never version.

Thomas,
Turns out you were right after all. Uninstalling and reinstalling the
Slackware packages works.

The difference as I suspected, was in my custom kernel config file. So I
compared it with the bare.i
config. The difference ? I set "Code Maturity" to "y" which adds the
line CONFIG_EXPERIMENTAL=y
in the config file. I also set CONFIG_KMOD=y.

Once I set this, I compiled and installed the kernel. I didn't run make
modules or make modules_install
as I hadn't added any additional modules, plus as we know this wipes out
the ALSA sound modules

Also, with XMMS I haven't noticed any sound improvement over the OSS
drivers. I didn't expect any,
as I have pretty standard consumer grade sound hardware. I'll probably
give the ALSA plugin for XMMS a go
and see if that makes any difference. But other than that everything works.

Anyway, maybe this will help someone using a custom 2.4.26 kernel with
ALSA and Slackware 10.

Thanks for your responses.

RG