|
Bugzilla – Full Text Bug Listing |
| Summary: | rcalsasound failed on first boot: alsactl/amixer: resmgr: unable to connect to resmgrd: No such file or directory | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Daniel Gollub <dgollub> |
| Component: | Installation | Assignee: | Takashi Iwai <tiwai> |
| Status: | RESOLVED FIXED | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Critical | ||
| Priority: | P5 - None | CC: | asklein, cheema, dkukawka, jsmeix, kontakt, lnussel, lslezak, tiwai |
| Version: | Beta 2 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | errormessages from /var/log/messages | ||
|
Description
Daniel Gollub
2006-01-26 18:09:05 UTC
Same here. Looks rather like a problem of resmgr or startpar. alsasound has 'Required-Start: $remote_fs resmgr', so resmgrd should run in prior. Judging my fresh install it looks like there are two unrelated bugs. 1. yast starts hal but not resmgr => hal cannot tell resmgr about hardware => resmgr starts up later and stays empty. 2. looks like there are no sound modules loaded. restarting hal and resmgr doesn't make them load. one has to run rcalsasound start. rcalsasound works just fine without resmgr as it runs as root anyways. There is no need for resmgr. 1) although one could blame yast for that I'll add a check into the resmgr init script to register hardware at resmgr if hal was already running as that is useful anyways. 2) takashi's part. rcresmgr done alsasound script is fixed now, hopefully yast2-sound works well. *** Bug 147623 has been marked as a duplicate of this bug. *** *** Bug 147909 has been marked as a duplicate of this bug. *** *** Bug 146289 has been marked as a duplicate of this bug. *** *** Bug 144525 has been marked as a duplicate of this bug. *** *** Bug 148332 has been marked as a duplicate of this bug. *** *** Bug 148261 has been marked as a duplicate of this bug. *** *** Bug 144468 has been marked as a duplicate of this bug. *** This is present in Beta4 after installation. But not only for alsactl. There are also errormessages for y2base. In which point did you get these messages (I assume you got exactly same errors). Could you check wether any snd-* modules are loaded while this happens (by switching to console and see lsmod output)? Created attachment 69378 [details]
errormessages from /var/log/messages
This is the part of /var/log/messages. This happend at the end of the installation process. After reboot the machine work correct, no error messages
And did the module exist _before_ reboot? Sorry, I rebooted the machine befor this report and found the messages in the log while report the other bug. I simply don't know if the modules exist before reboot OK, then I need the corresponding yast log to see what command yast2 issued. see atachment in bug 152262 Hm, these messages might be harmless. I'll fix alsa-lib not to call resmgr if the device really doesn't exist. Did the sound basically work without touching anything (before reboot, too)? I don't know. I rebootet the machine before I did any test. If the info is really needed, I must reinstall the machine. The fact it worked after the second boot means that the main problem was already fixed. The messages are just annoyance (and fixed in the latest alsa package). So, I close this bug. Let's see whether all pieces are put correctly on beta5 :) |