Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 52939 - baselayout-1.9.4 causes ALSA to no longer work
Summary: baselayout-1.9.4 causes ALSA to no longer work
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Unspecified (show other bugs)
Hardware: x86 Linux
: High critical
Assignee: Aron Griffis (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-06-03 20:30 UTC by Robert Brinson
Modified: 2004-06-05 20:42 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 Robert Brinson 2004-06-03 20:30:40 UTC
I emerged the new baselayout with 'emerge -uvD system'. I ran etc-update and modified all of my important config files. Upon reboot, there are no sounds from ALSA, and yes, it was working before. The pcspkr module works. I use the intel8x0 module. The baselayout package was the only one that was emerged.

Reproducible: Always
Steps to Reproduce:
1. emerge sync
2. emerge -upvD system
3. emerge -uvD system
4. etc-update
5. update important configs, like /etc/fstab
6. reboot; no sound from ALSA

Actual Results:  
No sound from ALSA

Expected Results:  
The modules should have been loaded giving me sound.

Portage 2.0.50-r7 (default-x86-2004.0, gcc-3.3.2, glibc-2.3.2-r9, 2.6.5-gentoo-r1)
=================================================================
System uname: 2.6.5-gentoo-r1 i686 Intel(R) Pentium(R) 4 CPU 2.40GHz
Gentoo Base System version 1.4.15
Autoconf: sys-devel/autoconf-2.59-r3
Automake: sys-devel/automake-1.8.3
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-O2 -march=pentium4 -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
COMPILER="gcc3"
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config
/usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config
/var/qmail/control"CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O2 -march=pentium4 -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs ccache sandbox"
GENTOO_MIRRORS="http://open-systems.ufl.edu/mirrors/gentoo
http://mirror.datapipe.net/gentoo ftp://ftp.gtlib.cc.gatech.edu/pub/gentoo
http://mirrors.tds.net/gentoo ftp://ftp.ussg.iu.edu/pub/linux/gentoo"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="3dnow X acpi aim alsa apache2 avi berkdb bonobo cdr crypt cups dga directfb
doc dvd encode esd foomaticdb gd gdbm gif gnome gphoto2 gpm gtk gtk2 gtkhtml
imagemagick imlib innodb jabber java joystick jpeg junit ldap libg++ libwww mad
mikmod mmx motif mozilla moznoirc moznomail mpeg msn mysql ncurses nls odbc
oggvorbis opengl oss pam pcmcia pda pdflib perl png pnp ppds python quicktime
readline sdl slang spell sse ssl svga tcpd tiff truetype usb videos x86 xml2
xmms xv yahoo zlib"
Comment 1 Robert Brinson 2004-06-03 22:42:16 UTC
This new baselayout seems to be causing other problems as well. I could no longer mount my cdrom drive. /dev/cdroms no longer existed. As far as the sound issue goes, there is apparently a problem with loading the modules. I modified /etc/init.d/alsasound at around line 110 with the following lines:

/sbin/insmod /lib/modules/2.6.5-gentoo-r1/kernel/drivers/input/gameport/gameport.ko
        #/sbin/insmod /lib/modules/2.6.5-gentoo-r1/kernel/sound/core/snd-rawmidi.ko
        #/sbin/insmod /lib/modules/2.6.5-gentoo-r1/kernel/sound/core/snd-timer.ko
        #/sbin/insmod /lib/modules/2.6.5-gentoo-r1/kernel/sound/core/snd.ko
        #/sbin/insmod /lib/modules/2.6.5-gentoo-r1/kernel/sound/drivers/mpu401/snd-mpu401-uart.ko
        #/sbin/insmod /lib/modules/2.6.5-gentoo-r1/kernel/sound/pci/ac97/snd-ac97-codec.ko
        #/sbin/insmod /lib/modules/2.6.5-gentoo-r1/kernel/sound/pci/snd-intel8x0.ko

This made ALSA work again, but it's an ugly hack. The issue with my cdrom drive was far more serious. So, I've downgraded my baselayout.
Comment 2 Robert Brinson 2004-06-03 22:43:37 UTC
Sorry. Those comments before the /sbin/insmod lines should not be there. I have commented the lines out in my file since I downgraded.
Comment 3 Surakshan Mendis 2004-06-04 02:20:03 UTC
sys-apps/module-init-tools-3.0-r2 is required with the new baselayout baselayout-1.9.4


HOWEVER module-init-tools-3.0-r2 is maskd ~ in x86.
I got it working my emergeing module-init-tools-3.0-r2
that is

ACCEPT_KEYWORDS="~x86" emerge module-init-tools
After this, restart alsasound /etc/init.d/alsasound restart

and set your volumes again in alsamixer...

Should work!
The deps may need to be modified in the baselayout ebuild, and module-init-tools-3.0-r2 marked stable for x86 if that is possible
Comment 4 Cyril Jaquier 2004-06-04 08:17:49 UTC
I also have problems since I upgrade to the latest baselayout :( My wireless interface becomes eth1 but was wlan0 before. Seems like an alias problem !!!

I strace modprobe and it seems to look for /etc/modprobe.conf which in my case is empty. Seems like modules-update only populate /etc/modules.conf.

A temporary fix : generate-modprobe.conf >> /etc/modprobe.conf
Comment 5 Daniel Westermann-Clark 2004-06-05 10:40:40 UTC
This is fixed for me with the baselayout-1.9.4-r1 and module-init-tools-3.0-r2.
Comment 6 Robert Brinson 2004-06-05 20:42:23 UTC
Apparently, baselayout-1.9.4 really needed module-init-tools-3.0-r2, which was still ~x86 when the new baselayout was released. The recent unmasking of this version of module-init-tools and the emerging of both module-init-tools and baselayout has fixed the issues I was having with ALSA and my cdrom drive not being able to mount. So, I am marking this bug as FIXED.