Re: [gentoo-user] Problem emerging alsa-utils-1.0.20-r4
On Friday 14 August 2009, Alan McKinnon wrote: On Friday 14 August 2009 22:23:14 Mick wrote: Obviously, the existence of /etc/modules.d/alsa does not allow emerge to continue. I think you must merge alsa file to alsa.conf and then delete alsa. Perhaps I'm too tired to understand the message ... is it telling to move file /etc/modules.d/alsa to /etc/modprobe.d/alsa.conf by hand? Yes. /etc/modules.d/ is a kernel 2.4 thing. kernel 2.6 uses /etc/modprobe.d/ and the modprobe utilities will automatically search it for config files, which makes /etc/modprobe.conf and modules-update obsolete. Someone has obviously taken the brave step and put a stake in the sane with a signpost saying 2.4 is not supported. Thank you all, job's done. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Problem emerging alsa-utils-1.0.20-r4
2009/8/15 Mick michaelkintz...@gmail.com I seem to have the same problem like this bug report: http://bugs.gentoo.org/show_bug.cgi?id=281434 which I am not sure why it has been marked as resolved/invalid. This is what happens: Emerging (1 of 1) media-sound/alsa-utils-1.0.20-r4 * alsa-utils-1.0.20.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ...[ ok ] * checking miscfile checksums ;-) ... [ ok ] * Obsolete config /etc/modules.d/alsa found. * * ERROR: media-sound/alsa-utils-1.0.20-r4 failed. * Call stack: * ebuild.sh, line 49: Called pkg_setup * alsa-utils-1.0.20-r4.ebuild, line 34: Called die * The specific snippet of code: * die Move /etc/modules.d/alsa to /etc/modprobe.d/alsa.conf. * The die message: * Move /etc/modules.d/alsa to /etc/modprobe.d/alsa.conf. * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/log/portage/media-sound:alsa-utils-1.0.20-r4:20090814-200133.log'. * The ebuild environment file is located at '/var/tmp/portage/media-sound/alsa-utils-1.0.20-r4/temp/die.env'. Have you had such a problem? What's the fix? I have both files mentioned: # ls -la /etc/modules.d/alsa -rw-r--r-- 1 root root 202 Jan 5 2009 /etc/modules.d/alsa # ls -la /etc/modprobe.d/alsa.conf -rw-r--r-- 1 root root 1028 Jul 4 09:27 /etc/modprobe.d/alsa.conf -- Regards, Mick Obviously, the existence of /etc/modules.d/alsa does not allow emerge to continue. I think you must merge alsa file to alsa.conf and then delete alsa.
Re: [gentoo-user] Problem emerging alsa-utils-1.0.20-r4
On Friday 14 August 2009, DPX-Infinity wrote: 2009/8/15 Mick michaelkintz...@gmail.com I seem to have the same problem like this bug report: http://bugs.gentoo.org/show_bug.cgi?id=281434 which I am not sure why it has been marked as resolved/invalid. This is what happens: Emerging (1 of 1) media-sound/alsa-utils-1.0.20-r4 * alsa-utils-1.0.20.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * Obsolete config /etc/modules.d/alsa found. * * ERROR: media-sound/alsa-utils-1.0.20-r4 failed. * Call stack: * ebuild.sh, line 49: Called pkg_setup * alsa-utils-1.0.20-r4.ebuild, line 34: Called die * The specific snippet of code: * die Move /etc/modules.d/alsa to /etc/modprobe.d/alsa.conf. * The die message: * Move /etc/modules.d/alsa to /etc/modprobe.d/alsa.conf. * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/log/portage/media-sound:alsa-utils-1.0.20-r4:20090814-200133.log'. * The ebuild environment file is located at '/var/tmp/portage/media-sound/alsa-utils-1.0.20-r4/temp/die.env'. Have you had such a problem? What's the fix? I have both files mentioned: # ls -la /etc/modules.d/alsa -rw-r--r-- 1 root root 202 Jan 5 2009 /etc/modules.d/alsa # ls -la /etc/modprobe.d/alsa.conf -rw-r--r-- 1 root root 1028 Jul 4 09:27 /etc/modprobe.d/alsa.conf -- Regards, Mick Obviously, the existence of /etc/modules.d/alsa does not allow emerge to continue. I think you must merge alsa file to alsa.conf and then delete alsa. Perhaps I'm too tired to understand the message ... is it telling to move file /etc/modules.d/alsa to /etc/modprobe.d/alsa.conf by hand? -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Problem emerging alsa-utils-1.0.20-r4
On Aug 14, 2009, at 3:09 PM, Mick wrote: * The specific snippet of code: * die Move /etc/modules.d/alsa to /etc/modprobe.d/ alsa.conf. * The die message: * Move /etc/modules.d/alsa to /etc/modprobe.d/alsa.conf. Have you had such a problem? What's the fix? I have both files mentioned: # ls -la /etc/modules.d/alsa -rw-r--r-- 1 root root 202 Jan 5 2009 /etc/modules.d/alsa # ls -la /etc/modprobe.d/alsa.conf -rw-r--r-- 1 root root 1028 Jul 4 09:27 /etc/modprobe.d/alsa.conf On one system I just had I had to copy the contents of /etc/modules.d/ alsa to /etc/modprobe.d/alsa.conf, while on another system to remove / etc/modules.d/alsa (it's contents were already in /etc/modprobe.d/ alsa.conf). Hint, keep a backup of /etc/modules.d/alsa until after you have verified the upgrade is working. HTH, Roy
Re: [gentoo-user] Problem emerging alsa-utils-1.0.20-r4
2009/8/15 Mick michaelkintz...@gmail.com On Friday 14 August 2009, DPX-Infinity wrote: 2009/8/15 Mick michaelkintz...@gmail.com I seem to have the same problem like this bug report: http://bugs.gentoo.org/show_bug.cgi?id=281434 which I am not sure why it has been marked as resolved/invalid. This is what happens: Emerging (1 of 1) media-sound/alsa-utils-1.0.20-r4 * alsa-utils-1.0.20.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * Obsolete config /etc/modules.d/alsa found. * * ERROR: media-sound/alsa-utils-1.0.20-r4 failed. * Call stack: * ebuild.sh, line 49: Called pkg_setup * alsa-utils-1.0.20-r4.ebuild, line 34: Called die * The specific snippet of code: * die Move /etc/modules.d/alsa to /etc/modprobe.d/alsa.conf. * The die message: * Move /etc/modules.d/alsa to /etc/modprobe.d/alsa.conf. * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/log/portage/media-sound:alsa-utils-1.0.20-r4:20090814-200133.log'. * The ebuild environment file is located at '/var/tmp/portage/media-sound/alsa-utils-1.0.20-r4/temp/die.env'. Have you had such a problem? What's the fix? I have both files mentioned: # ls -la /etc/modules.d/alsa -rw-r--r-- 1 root root 202 Jan 5 2009 /etc/modules.d/alsa # ls -la /etc/modprobe.d/alsa.conf -rw-r--r-- 1 root root 1028 Jul 4 09:27 /etc/modprobe.d/alsa.conf -- Regards, Mick Obviously, the existence of /etc/modules.d/alsa does not allow emerge to continue. I think you must merge alsa file to alsa.conf and then delete alsa. Perhaps I'm too tired to understand the message ... is it telling to move file /etc/modules.d/alsa to /etc/modprobe.d/alsa.conf by hand? -- Regards, Mick Yes. As I can see, these files are identical in sytax. Just add information from alsa to alsa.conf if any and them rm alsa.
Re: [gentoo-user] Problem emerging alsa-utils-1.0.20-r4
On Friday 14 August 2009 22:23:14 Mick wrote: Obviously, the existence of /etc/modules.d/alsa does not allow emerge to continue. I think you must merge alsa file to alsa.conf and then delete alsa. Perhaps I'm too tired to understand the message ... is it telling to move file /etc/modules.d/alsa to /etc/modprobe.d/alsa.conf by hand? Yes. /etc/modules.d/ is a kernel 2.4 thing. kernel 2.6 uses /etc/modprobe.d/ and the modprobe utilities will automatically search it for config files, which makes /etc/modprobe.conf and modules-update obsolete. Someone has obviously taken the brave step and put a stake in the sane with a signpost saying 2.4 is not supported. -- alan dot mckinnon at gmail dot com
