[gentoo-user] Problem about rc-update
Hi,everybody, I got a very very strange problems. I have install gnome, and when I try to add xdm to default runlevel, use command rc-update add xdm default, it is normal and output of rc-update show is right but when I restart computer, the xdm doesn't auto start, when I log in the system, and exec /etc/init.d/xdm start, it is started normally There is no any information about xdm when the system starting..It is very strange...Could somebody help me... And NetworkManager and alsasound have the same problem. here is the ouput of rc-update show: procfs | boot modules | boot local | nonetwork default net.lo | boot alsasound | boot xdm |default swap | boot udev |sysinit savecache | shutdown mount-ro | shutdown termencoding | boot netmount |default dmesg |sysinit consolekit |default devfs |sysinit root | boot urandom | boot udev-postmount |default consolefont | boot hostname | boot NetworkManager |default vixie-cron |default fsck | boot syslog-ng |default sysctl | boot mtab | boot bootmisc | boot killprocs | shutdown localmount | boot hwclock | boot keymaps | boot And I am using operc-0.6.1-r1 and baselayout-2.0.1
[gentoo-user] lm_sensors show 2 different temp. for my CPU
hi, after i setup lm_sensors on my gentoo amd64, i ran sensors, and got the below output coretemp-isa- Adapter: ISA adapter Core 0: +61.0 C (high = +74.0 C, crit = +100.0 C) coretemp-isa-0001 Adapter: ISA adapter Core 1: +61.0 C (high = +74.0 C, crit = +100.0 C) atk0110-acpi-0 Adapter: ACPI interface Vcore Voltage: +1.14 V (min = +1.45 V, max = +1.75 V) +3.3 Voltage: +3.23 V (min = +3.00 V, max = +3.60 V) +5.0 Voltage: +4.84 V (min = +4.50 V, max = +5.50 V) +12.0 Voltage:+11.90 V (min = +11.20 V, max = +13.20 V) CPU FAN Speed:2556 RPM (min =0 RPM) CHASSIS FAN Speed: 0 RPM (min =0 RPM) POWER FAN Speed: 0 RPM (min =0 RPM) CPU Temperature: +49.0 C (high = +90.0 C, crit = +125.0 C) MB Temperature:+41.0 C (high = +30.0 C, crit = +90.0 C) at the top are my CPU temp. of the 2 cores, usually they should be the same. but at the bottom, there's another value, which is 49 in this instance. which one is the correct value? why they are different? -- Best Regards, Xi Shen (David) http://twitter.com/davidshen84/
[gentoo-user] bashcomp cannot work well with rsync
hi, after i enabled bash completion for rsync, i got this error when type TAB to auto complete the file name bash: _known_hosts_real: command not found it used to work very well. do i missed something? P.S. my system is gentoo amd64, 2.6.32-openvz-budarin.1 #2 SMP; rsync-3.0.7; gentoo-bashcomp-20100613 -- Best Regards, Xi Shen (David) http://twitter.com/davidshen84/
Re: [gentoo-user] bashcomp cannot work well with rsync
Xi Shen writes: after i enabled bash completion for rsync, i got this error when type TAB to auto complete the file name bash: _known_hosts_real: command not found it used to work very well. do i missed something? Maybe googling :) Does this help? http://bugs.gentoo.org/301632 Wonko
Re: [gentoo-user] bashcomp cannot work well with rsync
i always start a new session after i enable/disable an bash completion plug-in. it looks like the same issue, but the resolution does not work for me. actually, the bashcomp issue only occurs when using rsync. other auto completion works fine. On Wed, Aug 4, 2010 at 8:27 PM, Alex Schuster wo...@wonkology.org wrote: Xi Shen writes: after i enabled bash completion for rsync, i got this error when type TAB to auto complete the file name bash: _known_hosts_real: command not found it used to work very well. do i missed something? Maybe googling :) Does this help? http://bugs.gentoo.org/301632 Wonko -- Best Regards, Xi Shen (David) http://twitter.com/davidshen84/
[gentoo-user] nm-applet cannot remember password
Hello everybody, I just got the problem that nm-applet cannot remember any password, such as the password of wifi and password of my vpn when I input my password, nm-applet ask me to set a password for the default keyring, I just leave them blank, because I don't want to enter password, after I click use unsare storage, it is normal, but when I try to connect the network again, nm-applet ask for password again ( ask for the password of network not the keyring), it is just like the keyring didn't have any effect? I tried to delete all filed in .gnome2/keyring/, but it didn't work Could somebody help me...
[gentoo-user] mischievous elf...
hello list. i'm running ~amd64 on an intel i7. after syncing and updating world, i'm having some problems: acroread does not start, failing thus: (acroread:31925): Gtk-WARNING **: /usr/lib64/gtk-2.0/2.10.0/engines/libxfce.so: wrong ELF class: ELFCLASS64 also, trying to upgrade lilypond, compilation fails thus: /usr/lib64/libz.so: invalid ELF header Could not find the zlib library which is needed to understand WOFF google returned many hits, but i couldn't find anything helpful in my case. any hints? best, lj
Re: [gentoo-user] lm_sensors show 2 different temp. for my CPU
On Wed, Aug 4, 2010 at 6:14 AM, Xi Shen davidshe...@googlemail.com wrote: hi, after i setup lm_sensors on my gentoo amd64, i ran sensors, and got the below output coretemp-isa- Adapter: ISA adapter Core 0: +61.0 C (high = +74.0 C, crit = +100.0 C) coretemp-isa-0001 Adapter: ISA adapter Core 1: +61.0 C (high = +74.0 C, crit = +100.0 C) atk0110-acpi-0 Adapter: ACPI interface Vcore Voltage: +1.14 V (min = +1.45 V, max = +1.75 V) +3.3 Voltage: +3.23 V (min = +3.00 V, max = +3.60 V) +5.0 Voltage: +4.84 V (min = +4.50 V, max = +5.50 V) +12.0 Voltage: +11.90 V (min = +11.20 V, max = +13.20 V) CPU FAN Speed: 2556 RPM (min = 0 RPM) CHASSIS FAN Speed: 0 RPM (min = 0 RPM) POWER FAN Speed: 0 RPM (min = 0 RPM) CPU Temperature: +49.0 C (high = +90.0 C, crit = +125.0 C) MB Temperature: +41.0 C (high = +30.0 C, crit = +90.0 C) at the top are my CPU temp. of the 2 cores, usually they should be the same. but at the bottom, there's another value, which is 49 in this instance. which one is the correct value? why they are different? AFAIK, neither is wrong or correct, they are usually measuring different things. coretemp is typically a relative temperature based on some scale like 0-100, using the digital thermal sensor in the CPU. It's not necessarily actual temperature measurement but it's an approximation that should be near a real temperature on most CPU models. In the past the approximation formula has changed between kernel versions and suddenly people see a 15 degrees change in coretemp, but all that really changed is how it is calculated. So keep that in mind if you notice a large change in coretemp someday in the future after installing a new kernel but the motherboard CPU temp doesn't change. The CPU temperature in the bottom section is from your motherboard's sensors, which could be temperature very near the CPU if not inside the CPU itself like coretemp. Both values independently are useful for seeing any sudden change, but there's no real value in comparing them to each other. If you want actual temperature like a thermometer then the motherboard reading (lower number) is probably more accurate I would guess. Hope I didn't confuse you even more :)
Re: [gentoo-user] Problem about rc-update
On 08/04/2010 12:15 AM, Chen Huan wrote: Hi,everybody, I got a very very strange problems. I have install gnome, and when I try to add xdm to default runlevel, use command rc-update add xdm default, it is normal and output of rc-update show is right but when I restart computer, the xdm doesn't auto start, when I log in the system, and exec /etc/init.d/xdm start, it is started normally There is no any information about xdm when the system starting..It is very strange...Could somebody help me... And NetworkManager and alsasound have the same problem. here is the ouput of rc-update show: procfs | boot modules | boot local | nonetwork default net.lo | boot alsasound | boot xdm |default swap | boot udev |sysinit savecache | shutdown mount-ro | shutdown termencoding | boot netmount |default dmesg |sysinit consolekit |default devfs |sysinit root | boot urandom | boot udev-postmount |default consolefont | boot hostname | boot NetworkManager |default vixie-cron |default fsck | boot syslog-ng |default sysctl | boot mtab | boot bootmisc | boot killprocs | shutdown localmount | boot hwclock | boot keymaps | boot And I am using operc-0.6.1-r1 and baselayout-2.0.1 That is strange. I don't have the answer, but I could offer a suggestion. You might want to try rc-update del the services that are having trouble and then adding them back in. You might want to use rc-update -s -v for your runlevels and see if there's anything broken. They'll be reported at the top of the list. Good luck.
[gentoo-user] Re: lm_sensors show 2 different temp. for my CPU
On 08/04/2010 02:14 PM, Xi Shen wrote: hi, after i setup lm_sensors on my gentoo amd64, i ran sensors, and got the below output coretemp-isa- Adapter: ISA adapter Core 0: +61.0 C (high = +74.0 C, crit = +100.0 C) coretemp-isa-0001 Adapter: ISA adapter Core 1: +61.0 C (high = +74.0 C, crit = +100.0 C) This is the sensor inside the CPU. The kernel doesn't know how to interpret this value on non-mobile CPUs, and it's usually off by 10C to 15C on desktop CPUs. CPU Temperature: +49.0 C (high = +90.0 C, crit = +125.0 C) This is the sensor on your motherboard that resides directly under the CPU. This an accurate temp and the kernel knows exactly how to interpret the values.
Re: [gentoo-user] Problem about rc-update
Thanks I tried many times rc-update del the service and add them back in, it isn't work... here is the output of rc-update -s -v, I cannot find out there is anything error... fuse | crypto-loop | numlock | procfs | boot pydoc-3.1 | avahi-daemon | acpid | device-mapper | modules | boot local | nonetwork default net.lo | boot alsasound | boot lvm-monitoring | swclock | xdm |default dmeventd | swap | boot sshd | udev |sysinit staticroute | fbcondecor | savecache | shutdown mount-ro | shutdown net.eth0 | termencoding | boot udev-dev-tarball | netmount |default dmesg |sysinit network | consolekit |default devfs |sysinit root | boot urandom | boot xdm-setup | gpm | atieventsd | rsyncd | udev-postmount |default consolefont | boot hostname | boot sysfs | pciparm | NetworkManager |default pydoc-2.6 | esound | vixie-cron |default fsck | boot syslog-ng |default sysctl | boot mtab | boot dbus | ntpd | avahi-dnsconfd | bootmisc | boot killprocs | shutdown dhcpcd | ntp-client | udev-mount | localmount | boot hwclock | boot lvm | nscd | keymaps | boot ch-laptop ch # rc-update show procfs | boot modules | boot local | nonetwork default net.lo | boot alsasound | boot xdm |default swap | boot udev |sysinit savecache | shutdown mount-ro | shutdown termencoding | boot netmount |default dmesg |sysinit consolekit |default devfs |sysinit root | boot urandom | boot udev-postmount |default consolefont | boot hostname | boot NetworkManager |default vixie-cron |default fsck | boot syslog-ng |default sysctl | boot mtab | boot bootmisc | boot killprocs | shutdown localmount | boot hwclock | boot keymaps | boot 2010/8/4 Bill Longman bill.long...@gmail.com On 08/04/2010 12:15 AM, Chen Huan wrote: Hi,everybody, I got a very very strange problems. I have install gnome, and when I try to add xdm to default runlevel, use command
Re: [gentoo-user] Re: Progress made, not done yet Re: All of a sudden, no apache2. No clue why.
AddHandler cgi-script cgi py Thanks, Kyle, you've been getting me closer and closer. If I'm starting to get the new stuff, AddHandler declares certain extensions. Up until last month, extensions were not required, and in fact my CGI programs have never had them. It used to be enough to use ScriptAlias, and put an executable in the directory. If it was a script with a shebang, or a compiled ELF program all was well. If I were going to use extensions, it would be .py or possibly .python, not .cgi or .pl. I totally meant to have it be py instead of pl, I guess pounding away at perl all day yesterday warped my mind. -- Kyle
[gentoo-user] boot log
Is there a way to log the boot messages - dmesg after booting up doesnt show module load failures and they scroll off the screen and I can find what they are. BillK
Re: [gentoo-user] Re: lm_sensors show 2 different temp. for my CPU
On Wed, 2010-08-04 at 18:22 +0300, Nikos Chantziaras wrote: On 08/04/2010 02:14 PM, Xi Shen wrote: hi, after i setup lm_sensors on my gentoo amd64, i ran sensors, and got the below output coretemp-isa- Adapter: ISA adapter Core 0: +61.0 C (high = +74.0 C, crit = +100.0 C) coretemp-isa-0001 Adapter: ISA adapter Core 1: +61.0 C (high = +74.0 C, crit = +100.0 C) This is the sensor inside the CPU. The kernel doesn't know how to interpret this value on non-mobile CPUs, and it's usually off by 10C to 15C on desktop CPUs. CPU Temperature: +49.0 C (high = +90.0 C, crit = +125.0 C) This is the sensor on your motherboard that resides directly under the CPU. This an accurate temp and the kernel knows exactly how to interpret the values. This is windows specific but has lots on how Intel/AMD work. http://www.alcpu.com/CoreTemp/ This page seems to imply that Linux's use of coretemp is not as detailed as available to windoze users and if an unknown cpu will use a default value which may be incorrect. http://www.mjmwired.net/kernel/Documentation/hwmon/coretemp The lm_sensor temperatures (and voltages) are always highly suspect, usually being based on users experiments rather than manufacturer information which is usually not available. Also, I suspect variation even between motherboards of the same type as sometimes the supposed lm_sensors values for one of my systems (often cpu voltage) are not even close. BillK
[gentoo-user] laptop-mode
With recent update to laptop-mode I decided to rework the power saving on my sony vaio. Mostly ok, but it seems laptop-mode is exclusively grabbing acpi events somehow. I have modded /etc/acpi/default.conf to trap the function keys for screen brightness and then control the LCD. However laptop-mode seems to have taken over and default.conf is no longer processed by acpid on an event, or events are not getting there. How can I either get acpid to process events through the normal files, or some other method to allow manual control of screen brightness and still keep acpi access for laptop-mode? BillK
Re: [gentoo-user] Re: lm_sensors show 2 different temp. for my CPU
thanks to both of you. :) On Wed, Aug 4, 2010 at 11:22 PM, Nikos Chantziaras rea...@arcor.de wrote: On 08/04/2010 02:14 PM, Xi Shen wrote: hi, after i setup lm_sensors on my gentoo amd64, i ran sensors, and got the below output coretemp-isa- Adapter: ISA adapter Core 0: +61.0 C (high = +74.0 C, crit = +100.0 C) coretemp-isa-0001 Adapter: ISA adapter Core 1: +61.0 C (high = +74.0 C, crit = +100.0 C) This is the sensor inside the CPU. The kernel doesn't know how to interpret this value on non-mobile CPUs, and it's usually off by 10C to 15C on desktop CPUs. CPU Temperature: +49.0 C (high = +90.0 C, crit = +125.0 C) This is the sensor on your motherboard that resides directly under the CPU. This an accurate temp and the kernel knows exactly how to interpret the values. -- Best Regards, Xi Shen (David) http://twitter.com/davidshen84/
Re: [gentoo-user] boot log
On 8/4/2010 8:19 PM, Bill Kenworthy wrote: Is there a way to log the boot messages - dmesg after booting up doesnt show module load failures and they scroll off the screen and I can find what they are. BillK /var/log/messages doesn't contain anything relevant? I thought that's where stuff like that got logged. Also, have you checked /var/log/kern.log? signature.asc Description: OpenPGP digital signature
Re: [gentoo-user] boot log
On Wed, 2010-08-04 at 21:10 -0400, Dakota wrote: On 8/4/2010 8:19 PM, Bill Kenworthy wrote: Is there a way to log the boot messages - dmesg after booting up doesnt show module load failures and they scroll off the screen and I can find what they are. BillK /var/log/messages doesn't contain anything relevant? I thought that's where stuff like that got logged. Also, have you checked /var/log/kern.log? messages has nothing but messages printed by modules after they successfully loaded - no failures. kern.log doesnt exist - there is a /var/log/kernel directory, but stuff in there is dated 2005 (!) Probably I need to turn on debug in the kernel somewhere - but what? BillK
Re: [gentoo-user] boot log
On 5/08/2010 11:10 AM, Dakota wrote: On 8/4/2010 8:19 PM, Bill Kenworthy wrote: Is there a way to log the boot messages - dmesg after booting up doesnt show module load failures and they scroll off the screen and I can find what they are. BillK /var/log/messages doesn't contain anything relevant? I thought that's where stuff like that got logged. Also, have you checked /var/log/kern.log? You'd possibly find that /var/log/everything/current is the Gentoo logging location I have a symlink from there to /var/log/messages There is a backup of dmesg stored in /var/log/dmesg I use a combination of dmesg | less and /var/log/everything/current and lsmod for module testing (if they load and don't load)
Re: [gentoo-user] boot log
On Thu, 2010-08-05 at 12:47 +1000, Rod wrote: On 5/08/2010 11:10 AM, Dakota wrote: On 8/4/2010 8:19 PM, Bill Kenworthy wrote: Is there a way to log the boot messages - dmesg after booting up doesnt show module load failures and they scroll off the screen and I can find what they are. BillK /var/log/messages doesn't contain anything relevant? I thought that's where stuff like that got logged. Also, have you checked /var/log/kern.log? You'd possibly find that /var/log/everything/current is the Gentoo logging location I have a symlink from there to /var/log/messages There is a backup of dmesg stored in /var/log/dmesg I use a combination of dmesg | less and /var/log/everything/current and lsmod for module testing (if they load and don't load) /var/log/everything was replaced by /var/log/messages in 2005 (and this system dates from ~2001 and was dd'd from a dell to the sony - dont you luv linux!) so I have the directory but nothing actually current in there. There is a dmesg file, same content as given by the dmesg command I think most (or all) the modules that errored were not found (I do load most modules manually) as over the years there have been problems with both order and loading when needed. Maybe time to clear them out and see if autoloading actually works now ... it doesnt on my mythbox but this system is a lot simpler. BillK
