Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 36894 - emerge --usepkg alsa-driver not good enough with newly built kernel
Summary: emerge --usepkg alsa-driver not good enough with newly built kernel
Status: RESOLVED INVALID
Alias: None
Product: [OLD] Docs-user
Classification: Unclassified
Component: Alsa Configuration Guide (show other bugs)
Hardware: All All
: High normal (vote)
Assignee: Tobias Scherbaum (RETIRED)
URL: http://www.gentoo.org/doc/en/alsa-gui...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-12-31 07:40 UTC by Rabbe Fogelholm
Modified: 2004-01-02 03:21 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rabbe Fogelholm 2003-12-31 07:40:11 UTC
In the Gentoo Linux ALSA Guide it is suggested that one can use the --buildpkg option when emerging alsa-driver for the first time, and --usepkg at subsequent occasions (when booting a newly built kernel).

This does not work for me. If I try

    [ boot a newly built kernel ]
    unmerge alsa-driver
    emerge --usepkg alsa-driver
    reboot

then the boot-up screen will say "modprobe: Can't locate module: snd-es18xx" (my on-board sound device is ES1869). If however I leave out the --usepkg option the alsa-driver is recompiled from sources, and the subsequent reboot is successful.

All in all the Gentoo ALSA guide is a great help, BTW. I have done ALSA configuration some times in the past on Red Hat boxes, using the official ALSA-HOWTO, and it was quite a bit more cumbersome as I remember it.
Comment 1 Tobias Scherbaum (RETIRED) gentoo-dev 2004-01-02 00:43:23 UTC
Have you changed your kernel sources after you've built the alsa-driver package?
Comment 2 Rabbe Fogelholm 2004-01-02 02:33:12 UTC
No, I was using the same kernel sources. The steps I did were

cd /usr/src/linux
make clean; make mrproper; make clean
cp {the-previous-config} .config
make menuconfig
{edit Makefile to set a new EXTRAVERSION}
make dep
make bzImage
make modules modules_install
cp arch/i386/boot/bzImage /boot/kernel-...
cp .config /boot/config-...
{create a new entry in grub.conf}
{reboot}

As expected this gave me a new kernel with non-functional ALSA sound. At this point `emerge unmerge alsa-driver; emerge --usepkg alsa-driver' did not work for me; the emerge completed nicely but after another reboot the ALSA sound would still not be functional. Doing `emerge unmerge alsa-driver; emerge alsa-driver' and yet another reboot cured the problem.
Comment 3 Tobias Scherbaum (RETIRED) gentoo-dev 2004-01-02 03:04:47 UTC
>{edit Makefile to set a new EXTRAVERSION}

I assume that this causes your problem. The alsa-modules are installed in
/lib/modules/${kernel-version}-EXTRAVERSION.

Your built package installs the modules in ${kernel-version}-OLD-EXTRAVERSION.
If you run 'emerge alsa-driver' the modules are placed in the correct
${kernel-version}-NEW-EXTRAVERSION directory.
Comment 4 Tobias Scherbaum (RETIRED) gentoo-dev 2004-01-02 03:09:54 UTC
I think the alsa-guide is clear enough at this point.
If a docdev can agree I'll mark this as INVALID.
Comment 5 Sven Vermeulen (RETIRED) gentoo-dev 2004-01-02 03:20:04 UTC
I can agree. When you recompile a kernel you don't have to change the EXTRAVERSION. Those are only needed when you want to distinguish several (different) kernel trees (different patches) iirc.
Comment 6 Tobias Scherbaum (RETIRED) gentoo-dev 2004-01-02 03:21:19 UTC
closed