I tested out the LiveDVD beta, and used the GUI installer to successfully install Gentoo on my system. However, it apparently did not set up audio. I wish I could provide more information, but as I was testing the GUI installer, I don't really know what information would be helpful since it's not like a specific package broke on me (to my knowledge). I would definitely be happy to work with a developer or even allow them to ssh in and treat my machine like a test box. Reproducible: Always Steps to Reproduce: 1.Install with GUI. 2.Boot. 3.Play music or watch video. Actual Results: No sound! Expected Results: Yes sound! Using integrated audio, which works for other Linux distributions, including Sabayon which is based on Gentoo. Motherboard is an Asus A8R-MVP.
Did you tell the installer to install any of the alsa-* packages?
(In reply to comment #1) > Did you tell the installer to install any of the alsa-* packages? > I don't remember there being a checkbox in the installer to select alsa. I could have overlooked it I suppose, but I went through the installer more than once to be sure, and if I'd seen it I'd have known to select it since I know what alsa is and all that jazz. And shouldn't kde-meta should bring that in anyway since arts is dependent on alsa?
Well, since alsa is in the default USE, he should have gotten it pulled in. Are you sure that there's no audio? Have you tried to unmute the channels?
(In reply to comment #3) > Well, since alsa is in the default USE, he should have gotten it pulled in. > Are you sure that there's no audio? Have you tried to unmute the channels? > Yes, I raised to full volume all channels and unmuted the ones that were muted (even the microphone inputs and stuff, just to be thorough). I would be quite happy to let somebody ssh in and take a look to see for themselves, for maximum thoroughness. :)
Well, if your mixer was working, then alsa is installed and configured. If your particular setup requires more configuration, you'll have to do it yourself. The installer isn't going to do it.
(In reply to comment #5) > Well, if your mixer was working, then alsa is installed and configured. If your > particular setup requires more configuration, you'll have to do it yourself. > The installer isn't going to do it. > Who can whether or not the mixer was really working? Perhaps the installer did not configure alsa correctly, for all we know. There is no audio, and there should be. This bug should not be closed until the problem causing the lack of audio is identified, at the very least.
Well, then it's up to you to figure out what additional configuration needs to be done to get alsa working. Bugzilla is not for troubleshooting. I've already determined that the installer isn't doing anything "wrong". If you can point out something simple and generic that the installer can do that will work everywhere (or at least not break anyone's setup), reopen the bug and I'll add it. Until then, the installer is doing extactly what I intended it to do.
(In reply to comment #7) > Well, then it's up to you to figure out what additional configuration needs to > be done to get alsa working. Bugzilla is not for troubleshooting. I've already > determined that the installer isn't doing anything "wrong". > > If you can point out something simple and generic that the installer can do > that will work everywhere (or at least not break anyone's setup), reopen the > bug and I'll add it. Until then, the installer is doing extactly what I > intended it to do. > How can you say that the installer isn't doing anything wrong? It didn't set up working audio. What exactly is your intention with the installer if not to help users get a fully functional Gentoo setup? If you don't feel that this is an issue with your installer, then reassign it to the appropriate person. The point of beta testing is to find out stuff exactly like this and get it fixed before the main release. However, the bottom line is that audio is not working on a pretty common motherboard when the 2008.0 installer is used. I'm not interested in arguing about whether or not a problem exists, or whether not having audio counts as something deserving to be fixed. Audio was not set up. I mean, it's not really a matter of opinion. I've reported a major issue with audio on a pretty popular motherboard observed from testing the beta of 2008.0. I'm happy to work with anybody to solve this because I'd like to see the 2008.0 release to be free of any major issues, but I'm not a developer. If you'd like to get to the bottom of this before the major release, then just tell me what I need to do to provide you with more data. Or, like I said, I'm happy to let you ssh in to see for yourself as if it were a test machine. But yeah. I don't want to be a nag. I just wanted to report this so that I could feel like I tried to do my part instead of being silent and doing nothing, heh. I hope you change your mind and decide to look into this a little more, and if you reopen the bug like I hope you will, then like I said, I'll be around to help however I can! :)
The Gentoo Linux Installer does exactly that... it installs packages. It doesn't do configuration for you. It doesn't setup GDM to automatically start, even if you installed Gnome/GDM, unless you configure it. It simply isn't a part of the Installer's tasks to configure anything other than the very basic (disks, etc) stuff required to boot. As with all things Gentoo, once the install is done, you're on your own to configure your machine. Does audio work on the booted CD but not your live file-system? In most cases, audio should "just work" provided it needs no additional configuration, but we don't configure it in any way, nor do we plan on doing so. If it works with the out-of-box defaults, you get sound. Otherwise, you're supposed to follow the ALSA configuration guide to set it up. This will likely stay as a WONTFIX, since it isn't the Installer's job, but I could help you troubleshoot why sound isn't working. As I said, it should work out of the box for pretty much anybody.
(In reply to comment #9) > The Gentoo Linux Installer does exactly that... it installs packages. It > doesn't do configuration for you. It doesn't setup GDM to automatically start, > even if you installed Gnome/GDM, unless you configure it. It simply isn't a > part of the Installer's tasks to configure anything other than the very basic > (disks, etc) stuff required to boot. As with all things Gentoo, once the > install is done, you're on your own to configure your machine. > > Does audio work on the booted CD but not your live file-system? > > In most cases, audio should "just work" provided it needs no additional > configuration, but we don't configure it in any way, nor do we plan on doing > so. If it works with the out-of-box defaults, you get sound. Otherwise, > you're supposed to follow the ALSA configuration guide to set it up. > > This will likely stay as a WONTFIX, since it isn't the Installer's job, but I > could help you troubleshoot why sound isn't working. As I said, it should work > out of the box for pretty much anybody. > I booted from the liveDVD to see if sound worked there, and yes, it does. So whatever is generated to create the alsa configuration for the liveDVD is not doing it the same way for your installer. Most interesting! My email/jabber/googletalk contact is "squarebottle@gmail.com". Thank you for not just waving this away. I'm impressed by you!
Well, the LiveDVD doesn't actually do anything special. All that it does is set the volume controls and run /etc/init.d/alsasound. Can you try adding alsasound to your default runlevel and see if that resolves the issue?
(In reply to comment #11) > Well, the LiveDVD doesn't actually do anything special. All that it does is > set the volume controls and run /etc/init.d/alsasound. Can you try adding > alsasound to your default runlevel and see if that resolves the issue? > "rc-update: '/etc/init.d/alsasound' not found; aborting" Well, that's kind of interesting. According to eix (just searched for alsa), alsalib and gst-plugins-alsa are installed.
That's it. On the LiveCD/LiveDVD, we install alsa-utils, which provides the alsasound init script. However, alsa-utils isn't a dependency of... well... pretty much anything. Now, alsa-utils can be installed no your system and that should fix it. The "best" solution would likely be to add media-sound/alsa-utils to the list of extra packages. This would allow users to select alsa-utils, and also alsasound from the services page. Here's a diff: Index: src/GLIInstallProfile.py =================================================================== --- src/GLIInstallProfile.py (revision 1894) +++ src/GLIInstallProfile.py (working copy) @@ -610,6 +610,7 @@ 'Desktop': (_(u"Popular Desktop Applications"), {"media-sound/audacious": _(u"GTK+ music player"), "media-sound/easytag": _(u"A GTK+ tagging program for MP3, OGG, FLAC, and more"), + "media-sound/alsa-utils": _(u"Utilities for ALSA, useful for enabling sound"), "mail-client/evolution": _(u"A GNOME groupware application, a Microsoft Outlook workalike"), "net-im/gaim": _(u"GTK+ Instant Messenger client"), "net-ftp/gftp": _(u"GTK+ FTP Client"), So what do you think? Add it?
Done. This is in SVN
Emerged alsautils and rebooted, and there was still no sound. Checked the sound levels again to be sure, and indeed, they were up. Using tab completion to get to alsamixer in a terminal, I saw alsaconf and decided to give it a shot. Ran it, reboot it, and... Finally, there is audio! So, in addition to having it simply install alsautils, you may need to also have it do something with alsaconf. I know you said earlier that it's not the installers job to configure things, but it's really such a short and easy configuration script (I just had to press enter like three times), if there's any way that it could run right after alsautils gets installed, a lot of people would appreciate it. Or how about this as a compromise if that's truly unacceptable: The installer has helpful notes and tips on the side, so adding a note about how some people may need to run alsaconf as root would be great. Anyway, thank you both for your hard work and attention on the matter! I'm looking forward to final release!
Most people don't need alsaconf. All that they need is the correct driver loaded, which is all alsaconf does is show which driver to use. Can you attach the output of "lsmod" from the booted CD? Also, please attach /etc/modules.d/alsa (or /etc/modprobe.d) from your system. I'm betting the issue is simply that because the LiveCD/DVD run "hwsetup" which will load modules, the modules are being loaded on the CD and not on your running system until you used alsaconf, which sets up the /etc/modules.d/alsa file. For example, I have this line on my laptop that tells alsasound which module to load at boot: alias snd-card-0 snd-hda-intel
