Re: [gentoo-amd64] Problem with pam-0.78
On Friday 2005-03-04 20:04, Nuitari wrote: > >> Esben Mose Hansen <[EMAIL PROTECTED]> wrote: > >>> Revert to binutils-2.15.90.*, and all it well. At least, that did it > >>> for me. > >> > >> Hmm, this is strange, because I'm sure I just upgraded to PAM-0.78, with > >> binutils 2.15.90.2-r4, and did it successfully. > >> > >> I can't quite remember exactly how I did it (there were some problems), > >> but they involved something like recompiling cracklib, and symlinking a > >> library in /usr/lib64 to /usr/lib. Yes, my symlinks are borked because > >> of an intemperate xorg 6.8.2 upgrade, but I am living with it ... :) > > > > Only some compiles have problems with 2.15.92.*. > > Wouldn't adding -fPIC to the cracklib ebuild fix it ? Maybe, but it will not fix every ebuild that cannot compile. As I said, it is a gcc bug. IMHO (as stated in the Gentoo bug) 2.15.92.* should be ~amd64, or even masked, as a lot of things break with that version. -- regards. Esben -- gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] Problem with pam-0.78
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 >>> I am updating a system and when compiling pam it fails with this error: >>> >>> >>> gcc -shared -L/var/tmp/portage/pam-0.78/work/Linux-PAM-0.78/lib -o >>> pam_cracklib.so dynamic/pam_cracklib.o -lc -Wl,-Bstatic -Wl,-lcrack >>> -Wl,-Bdynamic -lcrypt -lc -L../pammodutil -lpammodutil >>> -L../../libpam -lpam >>> /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.3/../../../../x86_64-pc-linux- >>> gnu/bin/ld: /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.3/../../../../lib/ >>> libcrack.a(fascist.o): relocation R_X86_64_32S against `a local >>> symbol' can not be used when making a shared object; recompile with >>> -fPIC >>> /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.3/../../../../lib/libcrack.a: >>> could not read symbols: Bad value >>> collect2: ld returned 1 exit status This problem is known already, and a fix is found, too. But I have no access to base-system packages and need to wait for azarah to apply them. Danny - -- Danny van Dyk <[EMAIL PROTECTED]> Gentoo/AMD64 Project, Gentoo Scientific Project -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFCKfP+aVNL8NrtU6IRAlFoAJ9pRrqIm2OFFQRC9EM3ACZR1hdogACfWNtu mVAjTO4wEo1hWMjR12yYgUQ= =R0NU -END PGP SIGNATURE- -- gentoo-amd64@gentoo.org mailing list
[gentoo-amd64] Re: [ACPI] Re: ACPI vs Asus A8v
Sergey Vlasov wrote: On Fri, 04 Mar 2005 17:22:11 + Hamie wrote: I have an athlon64 in an Asus A8V motherboard, running gentoo with kernel 2.6.11 (Also tried with 2.6.9 and 2.6.10). Although it works, and cool&quiet kicks in before boot, I can get no thermal or fan information from acpi... [skip] What sort of info & control SHOULD I be able to see out of this motherboard? How can I get the level of control that Asus offer with their windoze applications? You should try to use lm_sensors - there are some success reports about this board: http://archives.andrew.net.au/lm-sensors/msg29514.html In fact, most desktop machines do not support access to thermal or fan information via ACPI (because the code for this is not present in DSDT); and even if it is supported, the capabilities compared to lm_sensors are reduced (e.g., most hardware monitoring chips support voltage monitoring, which is not available through ACPI interfaces). Thanks for that. I guess I've been spoilt by using laptops mostly. lm_sensors finds the readings fine... Now all I have to do is work out which is which :) Hamish. -- gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] Re: [ACPI] Re: ACPI vs Asus A8v
strangely enough, I can never get lm-sensors to work on my K8V. It keeps saying that it can't find the the devices and to make the device files with mknod. But this shouldn't be necessary with udev, surely. Is there any way of finding out whether the system is detecting the sensors at all? On 06/03/2005, at 9:51 AM, Hamie wrote: Sergey Vlasov wrote: On Fri, 04 Mar 2005 17:22:11 + Hamie wrote: I have an athlon64 in an Asus A8V motherboard, running gentoo with kernel 2.6.11 (Also tried with 2.6.9 and 2.6.10). Although it works, and cool&quiet kicks in before boot, I can get no thermal or fan information from acpi... [skip] What sort of info & control SHOULD I be able to see out of this motherboard? How can I get the level of control that Asus offer with their windoze applications? You should try to use lm_sensors - there are some success reports about this board: http://archives.andrew.net.au/lm-sensors/msg29514.html In fact, most desktop machines do not support access to thermal or fan information via ACPI (because the code for this is not present in DSDT); and even if it is supported, the capabilities compared to lm_sensors are reduced (e.g., most hardware monitoring chips support voltage monitoring, which is not available through ACPI interfaces). Thanks for that. I guess I've been spoilt by using laptops mostly. lm_sensors finds the readings fine... Now all I have to do is work out which is which :) Hamish. -- gentoo-amd64@gentoo.org mailing list -- gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] Re: [ACPI] Re: ACPI vs Asus A8v
NY Kwok wrote: strangely enough, I can never get lm-sensors to work on my K8V. It keeps saying that it can't find the the devices and to make the device files with mknod. But this shouldn't be necessary with udev, surely. Is there any way of finding out whether the system is detecting the sensors at all? On 06/03/2005, at 9:51 AM, Hamie wrote: My K8V has a Winbond 83697 chip. Worked out of the box when compiling this into the kernel. Well, all except that it only sees one fan... Running a ~amd64 system. Run sensors from the command line to see some basic output. Scott. -- gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] Problem with pam-0.78
I was previously seeing the same problem. I downleveled cracklib from sys-libs/cracklib-2.8_pre1-r1 to sys-libs/cracklib-2.7-r10, and pam compiled cleanly for me. -- gentoo-amd64@gentoo.org mailing list
[gentoo-amd64] USB Works! Now just my sound card...
Thanks all for your help with the USB suggestions last week. Making the USB stuff modules took care of it. The only remaining issue I think is sound. I have a SoundBlaster PCI512. I chose the emu10k1 device driver, since that's mentioned on the card's specs. I have it and all the related sound drivers configured as modules also. So far, I'm not getting any sound though. Any tips you might have for that? -- Mark Creamer - You can help the poorest of the poor Matthew 25: Ministries http://www.m25m.org -- gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] USB Works! Now just my sound card...
Mark Creamer <[EMAIL PROTECTED]> wrote: > Thanks all for your help with the USB suggestions last week. Making the USB > stuff modules took care of it. > > The only remaining issue I think is sound. I have a SoundBlaster PCI512. I > chose the emu10k1 device driver, since that's mentioned on the card's specs. > I have it and all the related sound drivers configured as modules also. So > far, I'm not getting any sound though. Any tips you might have for that? Probably you want to do "rc-update add alsasound boot" and "/etc/init.d/alsasound start". Also, ALSA sound is muted by default. You need to use a mixer program to unmute it. ROX Volume Control (rox-base/volume) the one I like best (it may be masked for AMD64, but it works). There are also alsamixer, alsamixergui, aumix, kmix, etc. pgpjsgWe2bQSW.pgp Description: PGP signature
Re: [gentoo-amd64] USB Works! Now just my sound card...
Barry, that was it. I had to configure alsa and add my mixer. Now it works great. Thanks so much and have a great weekend! Mark On Saturday 05 March 2005 10:21 pm, [EMAIL PROTECTED] wrote: > Mark Creamer <[EMAIL PROTECTED]> wrote: > > Thanks all for your help with the USB suggestions last week. Making the > > USB stuff modules took care of it. > > > > The only remaining issue I think is sound. I have a SoundBlaster PCI512. > > I chose the emu10k1 device driver, since that's mentioned on the card's > > specs. I have it and all the related sound drivers configured as modules > > also. So far, I'm not getting any sound though. Any tips you might have > > for that? > > Probably you want to do "rc-update add alsasound boot" and > "/etc/init.d/alsasound start". Also, ALSA sound is muted by default. > You need to use a mixer program to unmute it. ROX Volume Control > (rox-base/volume) the one I like best (it may be masked for AMD64, but > it works). There are also alsamixer, alsamixergui, aumix, kmix, etc. -- Mark Creamer - You can help the poorest of the poor Matthew 25: Ministries http://www.m25m.org -- gentoo-amd64@gentoo.org mailing list
